APPIAN-SYSTEM-MIB: View SNMP OID List / Download MIB

Appian Communications Services MIB definitions file containing configuration and statistics control for system related services. These services include Configuration Management, Event Logging, Statistics Collection, Alarms and Thresholds configuration, OSAP discovery and topology protocol.

Table for configuring community strings and community access rights.

Entry of community table.

Unique identification number of this node within an Appian ring.

Number that uniquely identifies a community.

The administrative status. See AcAdminStatus for the semantics.

String that uniquely identifies a community.

Community access rights. See AcAccessRights for the semantics.

Table that specifies valid SNMP request source IP addresses and/or subnets for the different communities.

Entry that specifies a valid SNMP request source IP address or subnet for a given community.

Unique identification number of this node within an Appian ring.

Number that uniquely identifies a community.

Valid source IP address for SNMP requests of this community. All source IP addresses are valid for a given community if there are no entries in acCommMgrSourceAddrTable for this community with acCommMgrSourceAddrAdminStatus equal to activate

Subnet mask for valid source IP subnet for SNMP requests of this community.

The administrative status. See AcAdminStatus for the semantics.

A table of statistics manager configuration parameters which is indexed by AcNodeId.

The configuration and status parameters controlling the Statistics Manager service on this specific node.

The unique node identification number assigned by the EMS system to uniquely identify this node within an Appian ring of OSAP's.

The administrative status. See AcAdminStatus for the semantics.

The event log is over 90% full and wrapping is not enabled.

The security log is over 90% full and wrapping is not enabled.

The regular log file couldn't be closed.

The security log file couldn't be closed.

A table of configuration parameters controlling the event manager. The event manager is responsible for logging security and application state changes generated on a node. These events are stored in non-volitile memory and may be sent as traps to the EMS system.

The configuration and status parameters controlling the Event Logging Manager service on this specific node.

The unique node identification number assigned by the EMS system to uniquely identify this node within an Appian ring of OSAP's.

The administrative status. See AcAdminStatus for the semantics.

There are two kinds of logs in OSAP: regular log, and security log. This is the attribute to control the mode of operation of the regular event log. The regular event log can be configured to write to flash, or it can be disabled. When disabled, the event manager will keep a record of events in memory, which are available to the local CLI/TL1 but are not persistant. Enumeration: 'off': 1, 'flash-only': 2.

The size of the regular event log on the file system measured in k-bytes.

The current size of the regular event log measured in k-bytes.

The name of the binary regular log file.

When set to true, tells the event log manager to wrap the regular event log file when it has reached the maximum size. Oldest log entries are overwritten first when a wrap condition is reached.

There are two kinds of logs in OSAP: regular log, and security log. This is the attribute to control the mode of operation of the security event log. The security event log can be configured to write to flash, or it can be disabled. When disabled, the event manager will keep a record of events in memory, which are available to the local CLI/TL1 but are not persistant. Enumeration: 'off': 1, 'flash-only': 2.

The size of the regular security log on the file system measured in k-bytes.

The current size of the security event log measured in k-bytes.

The name of the binary security log file.

When set to true, tells the event log manager to wrap the security event log file when it has reached the maximum size. Oldest log entries are overwritten first when a wrap condition is reached.

When set to true, events that originate in slot 1 and would otherwise be displayed on the global standard output (console or telnet session) of slot 1, will instead be displayed on the global standard output of the master switch.

When set to true, events that originate in slot 2 and would otherwise be displayed on the global standard output (console or telnet session) of slot 2, will instead be displayed on the global standard output of the master switch.

This table provides configuration on a per agent basis for the handling of event messages from each agent. This table is automatically created by the system and does not need to be generated by the EMS.

A row per entity which allows for configuration settings on how eventlog messages generated by this entity are stored and reported for the EMS.

A unique node identification number which uniquely identifies a node within an Appian ring of OSAPs.

The acEventMgrAgentId identifies the agent which will be logging events within the event manager subsystem. The enumeration list of these well known ID's are published and used by the EMS in decoding the event log information for which agent has recorded an event. Enumeration: 'kernel': 1, 'qos': 35, 'mgmtapi': 30, 'temux': 34, 'ds3Net': 16, 'cfgmgr': 7, 'mlc': 37, 'modmgr': 39, 'enetagg': 44, 'ppp': 18, 'enetIME': 13, 'ds1Tdm': 14, 'lpta': 31, 'tta': 19, 'scmctrl': 32, 'serial': 26, 'eventmgr': 45, 'rdp': 47, 'service': 36, 'snmp': 24, 'system': 12, 'appiandcc': 28, 'statsmgr': 27, 'excep': 29, 'msgsvc': 3, 'asrt': 20, 'clisvc': 9, 'tlsmgr': 6, 'fr': 21, 'scpplt': 40, 'sntp': 22, 'telnet': 25, 'iasmgr': 5, 'ds3Tdm': 15, 'almmgr': 8, 'clkdrv': 41, 'hdlc': 38, 'fwdmgr': 4, 'mach': 43, 'bpm': 23, 'mgmtrem': 46, 'enetaccess': 11, 'oc3Net': 17, 'loader': 48, 'sonet': 33, 'common': 2, 'tl1svc': 10, 'plc': 42.

An ASCII name of the well known agent, sutible for display.

The administrative status. See AcAdminStatus for the semantics.

The logging level at which this entity will generate events destined for the event log manager. Currently this value is a bit mask allowing the user to select which types of events to store in the log. The bit mask values are selected as follows based on the position of the bit: critical(1), -- Critical means needs immediate attn. major(2), -- The resources may be exhausted soon. minor(4), -- Early indication of resource exhaustion. warning(8), -- Warnings, non-fatal. info(16), -- Informational event. debug(32), -- Used for debugging only. cleared(64), -- An alarm is being cleared. security-critical(128), -- Security log - Critical means needs immediate attn. security-major(256), -- Security log - The resources may be exhausted soon. security-minor(512), -- Security log - Early indication of resource exhaustion. security-warning(1024), -- Security log - Warnings, non-fatal. security-info(2048), -- Security log - Informational event. security-debug(4096), -- Security log - Used for debugging only. security-cleared(8192) -- Security log - An alarm is being cleared. The mask is generated as a logical OR of the values defined above.

The total number of events this entity has generated on this slot.

The last event ID which was generated by this entity on this slot.

The number of times the last event ID has been generated on this slot. Helpful in keeping a running count of the last event in the case of repeating errors.

The slot number where the configuration of this row will be applied.

Specifies what types of events originated by this entity will be displayed on the standard global output as traces. Currently this value is a bit mask allowing the user to select which types of events to display. The bit mask values are selected as follows based on the position of the bit: critical(1), -- Critical means needs immediate attn. major(2), -- The resources may be exhausted soon. minor(4), -- Early indication of resource exhaustion. warning(8), -- Warnings, non-fatal. info(16), -- Informational event. debug(32), -- Used for debugging only. cleared(64), -- An alarm is being cleared. security-critical(128), -- Security log - Critical means needs immediate attn. security-major(256), -- Security log - The resources may be exhausted soon. security-minor(512), -- Security log - Early indication of resource exhaustion. security-warning(1024), -- Security log - Warnings, non-fatal. security-info(2048), -- Security log - Informational event. security-debug(4096), -- Security log - Used for debugging only. security-cleared(8192) -- Security log - An alarm is being cleared. The mask is generated as a logical OR of the values defined above.

The configuration file couldn't be closed.

The configuration manager configuration parameters in a table which is indexed by a unique AcNodeId.

Single record per node which contains the configuration parameters for the configuration manager agent. This row is automatically created by the agent upon system initialization.

A unique number assigned by the EMS which uniquely identifies a node within an Appian ring of OSAP's.

The administrative status. See AcAdminStatus for the semantics.

The numeric revision number for the configuration file. This number is Appian specific and not an RCS type revision for the file, but instead an internal software revision of the file format.

The name of the configuration file. When the system boots, this config file is expected to be on the file system and will be the file that the system uses for normal operation.

The number of seconds after a provisioning change when the config file is updated with the current state of configuration for this node. The acConfigMgrAutoSaveEnable flag must be set to true(1) for auto-save to take place.

When set to true(1), the configuration manager will perform an update operation on the configuration file after 'n' seconds from the last provisioning change, specified by acConfigMgrAutoSaveInterval. Enabling this feature allows the EMS to assume the platform is in sync with a recent dynamic provisioning change, vs. sending down a new configuration file.

The last time the configuration file was updated automatically.

When set to true(1), the configuration manager will perform an update operation on the configuration file immediately.

This attribute indicates the configuration file save status when acConfigMgrSaveConfig is set. Enumeration: 'failed': 2, 'succeeded': 1, 'writing': 3.

The SNTP Client is unable to communicate with the NTP Server which has been configured.

The difference in time between client and peer exceeds the configured variance.

The SNTP Client was unable to read or write the hardware clock.

The SNTP Manager is responsible for controlling the SNTP client agent on the SCP. The SNTP client will peer with a time server which itself may peer with a higher stratum clock or a radio receiver.

A configuration record for the SNTP client agent.

A unique identifier assigned by the EMS which uniquely identifies a node within an Appian ring of OSAP's.

Attribute allowing enable/disabling control of the SNTP agent for provisioning changes. Refer to AcAdminStatus definition in appian-smi.mib.

Attribute which describes the current operational status of the SNTP client agent. Refer to AcOpStatus definition in appian-smi.mib.

If an error is reported in acSntpMgrOpStatus, this attribute will contain a detailed error code which can be referenced to determine the cause of a problem. The eventlog will also contain the failure reason.

The configured IP Address in dotted notation which SNTP uses to perform NTP queries against. The peer should be a Stratum-2 or greater clock.

The interval expressed in the number of seconds between NTP Query requests.

The number of query attempts the SNTP client should perform before reporting that the SNTP client cannot communicate with the peer.

The variance expressed as the number of milliseconds between client and peer which will trigger an alarm. This is useful in determining if the historical data recorded in NOVRAM for statistics trending or timestamps used for traps is outside the configured variance parameter.

The amount of time expressed as the number of milliseconds delta between client and peer.

Used to enable or disable variance threshold alarms.

The time zone this node is currently located in, expressed as an integer ranging from 0 to 23, representing the 24 hr time- zones starting at UTC which is equal to 0 and proceeding in the positive westerly direction. ie: Boston = 5, California=8. Note: Daylight savings time is not automatically calculated.

It specifies if daylight saving time is applicable.

Access denied due to a Logon Authentication failure.

The maximum number of authentication failure attempts has been exceeded. Access has been denied.

Successful logon by user.

The Authentication Manager is responsible for tracking who is logged into the system and how many success or failure events have occured for a unique user. As users log off the system they will be removed from the table.

A single row within the authentication table tracking a single user session which can be via telnet, serial, rlogin or ftp.

A unique number within an Appian Ring identifying the node for which the user is logged into.

A unique identifier within an Appian node which is used to identify the user currently attempting to gain access to the system.

A unique identifier within an Appian node which is used to identify the user currently attempting to gain access to the system.

The current access method for this user. Enumeration: 'unknown': 0, 'serial': 1, 'ftp': 4, 'telnet': 2, 'rlogin': 3.

The logon time this user was given access.

The total number of logon attempts for a user who was given access to the system and who is currently still logged in, or the failure attempts for a user who attempted to gain access but did not.

This field will read true(1) when the max number of failures has been reached for an attempted logon using the user name listed in this row.

Used to delete rows in this table.

Table that specifies trap destination IP addresses for the different communities.

Entry that specifies, for a given community, an IP address to send traps to.

Unique identification number of this node within an Appian ring.

Number that uniquely identifies a community.

IP address to send traps to.

The administrative status. See AcAdminStatus for the semantics.

Table that lists, for the different communities, the traps that these communities don't want to receive.

This entry specifies a trap type (by OID) that the specified community is not interested in receiving.

Unique identification number of this node within an Appian ring.

Number that uniquely identifies a community.

Number that, for the given node and community, uniquely identifies this filter.

The administrative status. See AcAdminStatus for the semantics.

Object identifier that identifies the trap type that will not be sent to the given community.

Table that allows a management system to request traps to be resent. Only the last 100 traps generated by the OSAP will be stored.

Setting this entry triggers the specified traps to be resent to the destination IP address specified.

Unique identification number of this node within an Appian ring.

The administrative status. See AcAdminStatus for the semantics.

Beginning of trap sequence number interval of traps to resend.

End of trap sequence number interval of traps to resend. If acTrapMgrResendToSeqId is the same as acTrapMgrResendFromSeqId, then only 1 trap is sent.

The file transfer operation failed.

The file transfer operation completed.

This table contains file transfer operation information. This table is created during the initialization of the system. The EMS does not create new rows in it.

Each row in this table indicates a file transfer operation.

A unique node identification number which uniquely identifies a node within an Appian ring of OSAPs.

The acFileXferMgrRowId identifies the row index of the table.

The administrative status. See AcAdminStatus for the semantics.

The operation type. The upload and download indicate the direction of the file transfer from the perspective of the OSAP. A download is an ftp get from the ftp server, and an upload is an ftp put to the ftp server. Enumeration: 'download': 2, 'upload': 1.

This attribute indicates whether a binary image, or a binary event log, a textual configuration file or any other file is being transferred. Enumeration: 'generic': 4, 'image': 1, 'config': 3, 'eventlog': 2.

This attribute indicates what type of file it is. Enumeration: 'namedbootimage': 2, 'regularlog': 3, 'none': 5, 'primaryimage': 1, 'securitylog': 4.

The IP Address of the ftp server from where the file is being transferred.

The user name to be used for the ftp login authentication. This is optional. If not supplied, the default value is used.

The password to be used for the ftp login authentication. This is optional. If not supplied, the default value is used, which is the chassis name of the OSAP. When supplied, the password is in the clear-text form.

The name of the source directory for the file transfer operation.

The name of the source file for the file transfer operation.

The name of the destination directory for the file transfer operation.

The name of the destination file for the file transfer operation.

This attribute indicates the mode of the transfer: ascii or binary. Enumeration: 'binary': 2, 'ascii': 1.

This attribute indicates whether the file transfer operation has been successful, or failed, or in progress. Enumeration: 'failed': 2, 'inprogress': 3, 'succeeded': 1.

The ring map obtained by RDP has changed.

There are two nodes in the ring with the same node Id.

This table contains general Appian ring information discovered through the Ring Discovery Protocol (RDP).

General Appian ring information discovered through RDP by the node specified by the index acRdpMgrNodeId.

Identifies the node where the Appian ring information was gathered.

State of the RDP Finite State Machine. Possible values: - isolated: the node is isolated. - discovery: the node is not isolated and is in the process of gathering Appian ring information. - master: the Appian ring information has been gathered and this node plays the role of master in the Ring Discovery Protocol (node with lowest Appian DCC MAC in the ring). - pleb: the Appian ring information has been gathered and this node does not play the role of master in the Ring Discovery Protocol (there is a node with a lower Appian DCC MAC in the ring). Enumeration: 'pleb': 3, 'master': 2, 'isolated': 0, 'discovery': 1.

MAC address of RDP master node in the Appian ring.

Appian ring topology. Possible values: - unknown: there is not enough information available to determine whether this node is part of an open or closed ring. - open: two of the nodes in the ring are configured as End Systems. - closed: all nodes in the ring are configured as Intermediate Systems. Enumeration: 'unknown': 0, 'open': 1, 'closed': 2.

Appian ring state: - unknown: there is not enough information available to determine whether the Appian ring is complete or incomplete. - complete: the ring map obtained contains all nodes in the ring. - incomplete: the ring map obtained does not contain all nodes in the ring. This may be due to a broken optical link or to misconfiguration of any of the nodes in the ring (wrong acChassisNodeArchitecture). Enumeration: 'unknown': 0, 'complete': 1, 'incomplete': 2.

Number of nodes in the Appian ring. The special value -1 means the ring size is unknown.

Current version of the Ring Discovery Protocol (RDP)

This table contains information about the different nodes in the Appian DCC ring that this node is part of. The first entry in this table corresponds to this node. Each entry in the table corresponds to the East neighbor of the node referred to by the previous entry.

Each row in this table contains information about a node in the Appian DCC ring.

A unique node identification number which uniquely identifies this node within an Appian ring of OSAPs.

Index that identifies this row in the table.

Node Id of node represented by this entry in the table.

IP address assigned to the Appian DCC management access interface of the node represented by this entry in the table.

Appian DCC MAC address of the node represented by this entry in the table.

RDP node configuration. Possible values: - unknown: the node configuration is unknown. - is: Intermediate System. The node is expected to have both an East and a West neighbor node in the Appian DCC ring. - ese: End System East. The node is expected to only have a West neighbor node in the Appian DCC ring. - esw: End System West. The node is expected to only have an East neighbor node in the Appian DCC ring. Enumeration: 'esw': 3, 'unknown': 0, 'is': 1, 'ese': 2.

Specifies whether RDP is active (there is light and we are receiving RDP packets) on the East interface.

Specifies whether RDP is active (there is light and we are receiving RDP packets) on the West interface.

Node architecture.