APPIAN-CHASSIS-MIB
AI MIB Summary
The APPIAN-CHASSIS-MIB facilitates monitoring of Appian OSAP hardware chassis by exposing real-time configuration parameters and operational state indicators, including power supply status, fan module health, and system temperature sensors.
Appian OSAP Chassis MIB which defines the current hardware configuration and state information.
Main OID:
acChassis.1.3.6.1.4.1.2785.2.1
57
Objects
Active
Status
3
Dependencies
Imported Objects
Objects
57 total| Object Name |
|---|
acChassisAppian OSAP Chassis MIB which defines the current hardware configuration and state information. MODULE-IDENTITY .1.3.6.1.4.1.2785.2.1 |
acChassisTraps OBJECT IDENTIFIER .1.3.6.1.4.1.2785.2.1.0 |
acChassisCfgMismatchTrapThe user configured chassis model does not match the actual chassis model generated by this trap. NOTIFICATION-TYPE .1.3.6.1.4.1.2785.2.1.0.1 |
acChassisTemperatureTrapThe temperature for this chassis has exceeded or fallen below the normal operational range. NOTIFICATION-TYPE .1.3.6.1.4.1.2785.2.1.0.2 |
acChassisFanFailureTrapThe fan shelf subsystem is reporting a failure of one or more fans. NOTIFICATION-TYPE .1.3.6.1.4.1.2785.2.1.0.3 |
acChassisTemperatureClearTrapThe temperature for this chassis has returned back to the normal operational range. NOTIFICATION-TYPE .1.3.6.1.4.1.2785.2.1.0.4 |
acChassisFanFailureClearTrapThe fan shelf subsystem that reported a failure of one or more fans has returned back to normal. NOTIFICATION-TYPE .1.3.6.1.4.1.2785.2.1.0.5 |
acGlobals OBJECT IDENTIFIER .1.3.6.1.4.1.2785.2.1.1 |
acNodeIdA unique node identifier assigned by the EMS to uniquely identify a node within an Appian ring. This must be set before setting other MIB objects that used NodeId as part of the index.rw AcNodeId (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.1.1.1 |
acChassisTableA table of configuration and statistics parameters for an Appian Communications chassis's within an Appian ring. SEQUENCE OF AcChassisEntry .1.3.6.1.4.1.2785.2.1.2 |
acChassisEntryA single node's chassis parameters. The index to this record is AcNodeId which is a unique identifier assigned by the EMS system. AcChassisEntry .1.3.6.1.4.1.2785.2.1.2.1 |
acChassisNodeIdA unique node identifier assigned by the EMS to uniquely identify a node within an Appian ring.ro AcNodeId (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.1.2.1.1 |
acChassisAdminStatusThis field is used by the administrator to ensure only one client can configure the chassis record at a time. The field is set to locked when a client is performing administrative operations and available when it is free.rw AcAdminStatus (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.1.2.1.2 |
acChassisOpStatusThe state field is used to identify the current operational state of the chassis.ro AcOpStatus (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.1.2.1.3 |
acChassisCfgTypeThis field describes the type of physical chassis as defined by the AppianVista EMS. The model number is a simple enumeration type for an Appian Communications chassis.rw Enumeration .1.3.6.1.4.1.2785.2.1.2.1.4 |
acChassisModelNumberThis field defines the type of physical chassis. The model number is a simple enumeration type for an Appian Communications chassis.ro Enumeration .1.3.6.1.4.1.2785.2.1.2.1.5 |
acChassisSerialNumberDisplay string containing the serial number which is read from the chassis backplane prom.ro DisplayString .1.3.6.1.4.1.2785.2.1.2.1.6 |
acChassisProductionDateThe date code when this chassis was manufactured. This field is read-only and set by manufacturing in the I2C prom. The format used is YYWW; with YY = year and WW = week.ro DisplayString .1.3.6.1.4.1.2785.2.1.2.1.7 |
acChassisRevisionThe revision of the chassis expressed as an integer monotonically increasing from 0 to 255.ro INTEGER .1.3.6.1.4.1.2785.2.1.2.1.8 |
acChassisTemperatureThe current temperature state for the chassis as reported by the fan and temperature controller card. If the temperature is too hot, it is possible that the input filter is blocked, which is reported in the acChassisFanStatus attribute.ro Enumeration .1.3.6.1.4.1.2785.2.1.2.1.9 |
acChassisFanSpeedThe desired fan speed.rw AcFanStatus .1.3.6.1.4.1.2785.2.1.2.1.10 |
acChassisFan1StatusFAN 1 status.ro AcFanStatus .1.3.6.1.4.1.2785.2.1.2.1.11 |
acChassisFan2StatusFAN 2 status.ro AcFanStatus .1.3.6.1.4.1.2785.2.1.2.1.12 |
acChassisFan3StatusFAN 3 status.ro AcFanStatus .1.3.6.1.4.1.2785.2.1.2.1.13 |
acChassisFan4StatusFAN 4 status.ro AcFanStatus .1.3.6.1.4.1.2785.2.1.2.1.14 |
acChassisFan5StatusFAN 5 status.ro AcFanStatus .1.3.6.1.4.1.2785.2.1.2.1.15 |
acChassisFan6StatusFAN 6 status.ro AcFanStatus .1.3.6.1.4.1.2785.2.1.2.1.16 |
acChassisPowerAStatusThe current state of the power supply subsystem.ro AcOpStatus (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.1.2.1.17 |
acChassisPowerBStatusThe current state of the power supply subsystem.ro AcOpStatus (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.1.2.1.18 |
acChassisContactThe identification and contact information of the person responsible for this managed node. This field is mapped to the MIB-II sysContact field.rw DisplayString .1.3.6.1.4.1.2785.2.1.2.1.19 |
acChassisNameAn administratively assigned name for this managed node. This field is mapped to MIB-II sysName field.rw DisplayString .1.3.6.1.4.1.2785.2.1.2.1.20 |
acChassisLocationThe physical location of this node. The field is mapped to the MIB-II sysLocation field.rw DisplayString .1.3.6.1.4.1.2785.2.1.2.1.21 |
acChassisDescriptionA description of the node indicating the type of Appian Communications equipment. This field is mapped to the MIB-II sysDescr attribute.ro DisplayString .1.3.6.1.4.1.2785.2.1.2.1.22 |
acChassisMaxSlotsThe maximum number of slots within this chassis.ro INTEGER .1.3.6.1.4.1.2785.2.1.2.1.23 |
acChassisSysUpTimeThe time in hundredths of a second since the network management portion of the system was last reinitialized. The acChassisSysUpTime field is mapped to the MIB-II sysUptime field. Note: The value of acChassisSysUpTime will not be reset when an Active to Standby failover occurs on the Switch Control Processor(s). The acChassisSysUpTime value will only be reset when the whole system has been reset.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.2785.2.1.2.1.24 |
acChassisCurrentTimeA string containing the current time and date as read from the active Switch Control Processor (SCP) NovRam. The format is defined by DateAndTime syntax.rw DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.2785.2.1.2.1.25 |
acChassisMaxSerialPortsIdentifies the total number of serial interface ports on the OSAP chassis.ro INTEGER .1.3.6.1.4.1.2785.2.1.2.1.26 |
acChassisRingIdA unique Ring Identification number which is assigned by the EMS system to uniquely identify the Appian Ring supported by this node.rw AcRingId (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.1.2.1.27 |
acChassisRingNameA user defined string assigned to the Ring Id which uniquely identifies the Appian Ring supported by this node.rw DisplayString .1.3.6.1.4.1.2785.2.1.2.1.28 |
acChassisMibVersionA ASCII string which identifies the Appian MIB version which is currently supported by the active switch control processor.ro AcMibVersion (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.1.2.1.29 |
acChassisNodeArchitectureNode architecture.rw AcNodeArchitecture (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.1.2.1.30 |
acChassisNodePollThis object returns a concise summary of the system state. It contains information on the system operational status, mib revision, fan status, power supply status, and other status information. The value is in compacted binary format: Element Size Value Description ----------------------------------------------------------------------- poll version 1 0x01 Node poll version operational status 1 acChassisOpStatus overall system status mib version 4 software version 4 chassis temperature 1 actual temperature? maybe it should be in module? fan status, each fan status is encoded as: 0xA1 - FAN status IE 0x01 - FAN #1 0x01 - operational power supply status, with each power supply status encoded as: 0xA2 - power status IE 0x02 - power supply #2 0x01 - operationalro OCTET STRING .1.3.6.1.4.1.2785.2.1.2.1.31 |
acChassisModulePollThis object returns a concise summary of the module cards in the system. For each module card present, it includes card slot, card configured type and actual type, card operational status, redundancy status, and possibly LED information. slot - 1 byte representing the physical slot number. number - 1 byte representing the module number. configured type - 1 byte value from AcModuleType. actual type - 1 byte value from AcModuleType. operStatus - 1 byte representing an AcOpStatus. redundancy - 1 byte to indicate it's active or standby number of LEDs - 1 byte, indicates how many LED status follows LED states - 1 byte for each LED to represent: green, red, yellow, off. with high bit on as ing.ro OCTET STRING .1.3.6.1.4.1.2785.2.1.2.1.32 |
acChassisPortPollThis object returns a concise summary of the module cards in the system. For each module card present, it includes card slot, card configured type and actual type, card operational status, redundancy status, possibly LED information, and port information. slot - 1 byte representing the physical slot number. configured type - 1 byte value from AcModuleType. actual type - 1 byte value from AcModuleType. operStatus - 1 byte representing an AcOpStatus. media slot - 1 byte, valid only number of LEDs - 1 byte, indicates how many LED status follows LED states - 1 byte for each LED to represent: green, red, yellow, off. with high bit on as ing. number of ports - 1 byte, indicates how many physical ports on the card port info - for each port, it includes operStatus and service status. Take a system with the following configuration as an example: slot 1 - a single port OC3 slot 2 - a single port OC3 slot 3 - a switching control card slot 5 - an ethernet media card slot 6 - an ethernet media card, currently backing up slot 5 slot 11 - an 8-port ethernet PHY card driven by slot 5 slot 12 - an 8-port ethernet PHY card driven by slot 5. The poll would resemble this: 0x01 - the first poll version 0xA3 - this indicates a card information element 0x01 - card slot 1 0x13 - configured card type: oc3-sr-1 0x13 - actual card type: oc3-sr-1 0x01 - card operational status: operational ox00 - media slot, not applicable 0x00 - # of LEDs, 0 means no LED information included 0x01 - # of ports 0x01 - port status: up 0x00 - no services on this port 0xA3 - this indicates a card information element 0x02 - card slot 2 0x13 - configured card type: oc3-sr-1 0x13 - actual card type: oc3-sr-1 0x01 - card operational status: operational ox00 - media slot, not applicable 0x00 - # of LEDs, 0 means no LED information included 0x01 - # of ports 0x01 - port status: up 0x00 - no services on this port 0xA3 - this indicates a card information element 0x03 - card slot 3 0x03 - configured card type: sw-1 0x03 - actual card type: sw-1 0x01 - card operational status: operational ox00 - media slot, not applicable 0x00 - # of LEDs, 0 means no LED information included 0x00 - # of ports 0xA3 - this indicates a card information element 0x05 - card slot 5 0x04 - configured card type: 16-port fast ethernet 0x04 - actual card type: 16-port fast ethernet 0x01 - card operational status: operational ox00 - media slot, not applicable 0x00 - # of LEDs, 0 means no LED information included 0x00 - # of ports - defer port status to PHY cards? 0xA3 - this indicates a card information element 0x0B - card slot 11 0x05 - configured card type: fe8-tx-io (8-port phy card) 0x05 - actual card type: fe8-tx-io (8-port phy card) 0x01 - card operational status: operational ox05 - media slot: currently driven by media card in slot 5 0x00 - # of LEDs, 0 means no LED information included 0x08 - info for 8 ports follows 0x01 0x?? - port 1, up and service status? 0x02 0x?? - port 2, down and service status? ... 1 byte can be used to represent 4 service status, with 2 bits each? 0xA3 - this indicates a card information element 0x0C - card slot 11 0x05 - configured card type: fe8-tx-io (8-port phy card) 0x05 - actual card type: fe8-tx-io (8-port phy card) 0x01 - card operational status: operational ox05 - media slot: currently driven by media card in slot 5 0x00 - # of LEDs, 0 means no LED information included 0x08 - info for 8 ports follows 0x01 0x?? - port 1, up and service status? 0x02 0x?? - port 2, down and service status? ... 1 byte can be used to represent 4 service status, with 2 bits each?ro OCTET STRING .1.3.6.1.4.1.2785.2.1.2.1.33 |
acChassisResetSetting this object to true causes the entire system to reset.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2785.2.1.2.1.34 |
acChassisTdmAccessRedundancyModeThis value describes how backup TDM Access cards are used to provide redundancy for active TDM Access cards in the system. n-to-one: One backup card will provide redundancy for all other similar type TDM Access cards. one-to-one: Each backup card will be assigned to provide redundancy for at most one TDM Access card.rw Enumeration .1.3.6.1.4.1.2785.2.1.2.1.35 |
acMgmtAccessTableThis table contains the configuration parameters which define the method used for management of the OSAP via a remote EMS such as the AppianVista platform. The table contains the IP Address, gateway and subnet for in-band and OOB access to the OSAP. SEQUENCE OF AcMgmtAccessEntry .1.3.6.1.4.1.2785.2.1.3 |
acMgmtAccessEntryA configuration record defining a single nodes in-band and oob access methods and interfaces. This entry must be created by the EMS or CLI and is not by default automatically instantiated. AcMgmtAccessEntry .1.3.6.1.4.1.2785.2.1.3.1 |
acMgmtAccessNodeIdA unique node identifier assigned by the EMS to uniquely identify a node within an Appian ring.ro AcNodeId (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.1.3.1.1 |
acMgmtAccessIndexUnique identifier of management access interface in this node.ro INTEGER .1.3.6.1.4.1.2785.2.1.3.1.2 |
acMgmtAccessInterfaceTypeThis attribute defines what type of management access port is being configured. The Ethernet(1) interface refers to the OOB Ethernet port on the switch controller and is used for both master and slave switch controllers, only one of which is active at a time. Frame-Relay(4) and PPP(5) refer to In-Band access interface. Appian-DCC(2) is used as an extended LAN and needs to be configured for each node within an Appian SONET Ring.rw Enumeration .1.3.6.1.4.1.2785.2.1.3.1.3 |
acMgmtAccessAdminStatusThis field is used by the administrator to ensure only one client can perform configuration operations on the chassis record at a time. The field is set to locked when a client is performing administrative operations and available when it is free. The field is also used to enable or disable a specific management access port. Setting the value to inactivate(1) will cause the interface to be disabled. Setting the state to activate(2) will enable the management interface.rw AcAdminStatus (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.1.3.1.4 |
acMgmtAccessOpStatusThis attribute is used to determine the current state of the management access agent. Refer to the appian-smi.mib for defintion details of the AcOpStatus attribute.ro AcOpStatus (APPIAN-SMI-MIB) .1.3.6.1.4.1.2785.2.1.3.1.5 |
acMgmtAccessIpAddressThe IP Address in dotted notation which is used by the AppianVista EMS system or for telnet, tftp, rlogin or ftp access to the network element. This IP address may be bound to a frame-relay trunk/dlci or could be bound to a TLS trunk running PPP.rw IpAddress .1.3.6.1.4.1.2785.2.1.3.1.6 |
acMgmtAccessIpSubnetThe IP Subnet address in dotted notation used for the primary in-band access interface. If no value is entered, the management agent will assume the natural mask.rw IpAddress .1.3.6.1.4.1.2785.2.1.3.1.7 |
acMgmtAccessTrunkIf the access type is either frame relay or PPP, this object has the trunk number of the trunk being used for inband management. If the access type is not frame relay nor PPP, this object has value of 0 and is not applicable.rw INTEGER .1.3.6.1.4.1.2785.2.1.3.1.8 |
acMgmtAccessFrDlciThe Frame-Relay DLCI number used for in-band management access to the network element when the access interface uses a frame-relay trunk.rw INTEGER .1.3.6.1.4.1.2785.2.1.3.1.9 |