APPIAN-CHASSIS-MIB

All MIBs › APPIAN-CHASSIS-MIB

Organization: Appian Communications, Inc.

Last Updated: 2000-04-20

Category: Optical and WDM, Vendor: Appian

Description: Appian Communications optical networking chassis hardware inventory and slot management.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is APPIAN-CHASSIS-MIB?

APPIAN-CHASSIS-MIB is a vendor-specific module from Appian Communications for its OSAP optical networking chassis platform, defining the hardware configuration and state of the chassis and its slots. It exposes hardware inventory data (model number, serial number, production date, revision) alongside operational and administrative status and environmental readings. It is explicitly a hardware health/status MIB: acChassisAdminStatus and acChassisOpStatus report whether the chassis is administratively enabled and operationally functioning, while acChassisTemperature provides thermal monitoring, together giving a picture of whether the physical chassis is healthy. It is a self-contained enterprise MIB with dependency primarily on the vendor's own OID tree rather than external standards, and it is typically used alongside other Appian MIBs covering individual line cards and ports; loading APPIAN-CHASSIS-MIB into an MIB Browser first lets an operator quickly inspect the acChassisTable structure before configuring automated polling. It is deployed on Appian Communications optical networking chassis in telecom transport network environments.

IPNetwork Monitor allows you to monitor SNMP objects defined in APPIAN-CHASSIS-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Appian Communications OSAP optical networking chassis

Monitoring Examples

An operator would poll acChassisTable/acChassisEntry indexed by acChassisNodeId to check acChassisOpStatus against acChassisAdminStatus, confirming the chassis is both enabled and operating correctly, and read acChassisTemperature to watch for thermal drift. A mismatch where acChassisAdminStatus is up but acChassisOpStatus reports a fault, combined with a climbing acChassisTemperature reading, would indicate an overheating or failing chassis. acChassisSerialNumber and acChassisModelNumber let an inventory system confirm exactly which hardware unit is reporting the fault.

What Can Be Monitored

chassis admin/operational status
chassis temperature
chassis serial number and model
chassis configuration type/revision

Imported Objects

From APPIAN-SMI-MIB

AcAdminStatus
AcMibVersion
AcNodeArchitecture
AcNodeId
AcOpStatus
AcRingId
acOsap	OBJECT-IDENTITY

From SNMPv2-SMI

IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
TimeTicks

From SNMPv2-TC

DateAndTime
DisplayString
TEXTUAL-CONVENTION
TruthValue

How to Use in IPNetwork Monitor

Example using acChassisSysUpTime OID:

Select an Appian Communications OSAP SONET/optical access platform as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type acChassisSysUpTime into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. It reports how long the management portion of this chassis has been running since it was last reinitialized, in hundredths of a second. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a TimeTicks-type OID, Value bounds is the most useful condition here — trigger an alert if the value is unexpectedly low (e.g. under 10 minutes), since that indicates a recent, possibly unplanned, reboot. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
acChassis	1.3.6.1.4.1.2785.2.1			Appian OSAP Chassis MIB which defines the current hardware configuration and state information.
ACA acChassisAdminStatus	1.3.6.1.4.1.2785.2.1.2.1.2	AcAdminStatus	read-write	This 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.
NTF acChassisCfgMismatchTrap	1.3.6.1.4.1.2785.2.1.0.1			The user configured chassis model does not match the actual chassis model generated by this trap.
INT acChassisCfgType	1.3.6.1.4.1.2785.2.1.2.1.4	INTEGER	read-write	This 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.
STR acChassisContact	1.3.6.1.4.1.2785.2.1.2.1.19	DisplayString	read-write	The identification and contact information of the person responsible for this managed node. This field is mapped to the MIB-II sysContact field.
DAT acChassisCurrentTime	1.3.6.1.4.1.2785.2.1.2.1.25	DateAndTime	read-write	A string containing the current time and date as read from the active Switch Control Processor (SCP) NovRam. The format is defined by DateAndTime syntax.
STR acChassisDescription	1.3.6.1.4.1.2785.2.1.2.1.22	DisplayString	read-only	A description of the node indicating the type of Appian Communications equipment. This field is mapped to the MIB-II sysDescr attribute.
acChassisEntry	1.3.6.1.4.1.2785.2.1.2.1		not-accessible	A single node's chassis parameters. The index to this record is AcNodeId which is a unique identifier assigned by the EMS system.
ACF acChassisFan1Status	1.3.6.1.4.1.2785.2.1.2.1.11	AcFanStatus	read-only	FAN 1 status.
ACF acChassisFan2Status	1.3.6.1.4.1.2785.2.1.2.1.12	AcFanStatus	read-only	FAN 2 status.
ACF acChassisFan3Status	1.3.6.1.4.1.2785.2.1.2.1.13	AcFanStatus	read-only	FAN 3 status.
ACF acChassisFan4Status	1.3.6.1.4.1.2785.2.1.2.1.14	AcFanStatus	read-only	FAN 4 status.
ACF acChassisFan5Status	1.3.6.1.4.1.2785.2.1.2.1.15	AcFanStatus	read-only	FAN 5 status.
ACF acChassisFan6Status	1.3.6.1.4.1.2785.2.1.2.1.16	AcFanStatus	read-only	FAN 6 status.
NTF acChassisFanFailureClearTrap	1.3.6.1.4.1.2785.2.1.0.5			The fan shelf subsystem that reported a failure of one or more fans has returned back to normal.
NTF acChassisFanFailureTrap	1.3.6.1.4.1.2785.2.1.0.3			The fan shelf subsystem is reporting a failure of one or more fans.
ACF acChassisFanSpeed	1.3.6.1.4.1.2785.2.1.2.1.10	AcFanStatus	read-write	The desired fan speed.
STR acChassisLocation	1.3.6.1.4.1.2785.2.1.2.1.21	DisplayString	read-write	The physical location of this node. The field is mapped to the MIB-II sysLocation field.
INT acChassisMaxSerialPorts	1.3.6.1.4.1.2785.2.1.2.1.26	INTEGER	read-only	Identifies the total number of serial interface ports on the OSAP chassis.
INT acChassisMaxSlots	1.3.6.1.4.1.2785.2.1.2.1.23	INTEGER	read-only	The maximum number of slots within this chassis.
ACM acChassisMibVersion	1.3.6.1.4.1.2785.2.1.2.1.29	AcMibVersion	read-only	A ASCII string which identifies the Appian MIB version which is currently supported by the active switch control processor.
INT acChassisModelNumber	1.3.6.1.4.1.2785.2.1.2.1.5	INTEGER	read-only	This field defines the type of physical chassis. The model number is a simple enumeration type for an Appian Communications chassis.
OCT acChassisModulePoll	1.3.6.1.4.1.2785.2.1.2.1.32	OCTET STRING	read-only	This 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.
STR acChassisName	1.3.6.1.4.1.2785.2.1.2.1.20	DisplayString	read-write	An administratively assigned name for this managed node. This field is mapped to MIB-II sysName field.
ACN acChassisNodeArchitecture	1.3.6.1.4.1.2785.2.1.2.1.30	AcNodeArchitecture	read-write	Node architecture.
ACN acChassisNodeId	1.3.6.1.4.1.2785.2.1.2.1.1	AcNodeId	accessible-for-notify	A unique node identifier assigned by the EMS to uniquely identify a node within an Appian ring.
OCT acChassisNodePoll	1.3.6.1.4.1.2785.2.1.2.1.31	OCTET STRING	read-only	This 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 - operational
ACO acChassisOpStatus	1.3.6.1.4.1.2785.2.1.2.1.3	AcOpStatus	read-only	The state field is used to identify the current operational state of the chassis.
OCT acChassisPortPoll	1.3.6.1.4.1.2785.2.1.2.1.33	OCTET STRING	read-only	This 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?
ACO acChassisPowerAStatus	1.3.6.1.4.1.2785.2.1.2.1.17	AcOpStatus	read-only	The current state of the power supply subsystem.
ACO acChassisPowerBStatus	1.3.6.1.4.1.2785.2.1.2.1.18	AcOpStatus	read-only	The current state of the power supply subsystem.
STR acChassisProductionDate	1.3.6.1.4.1.2785.2.1.2.1.7	DisplayString	read-only	The 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.
T/F acChassisReset	1.3.6.1.4.1.2785.2.1.2.1.34	TruthValue	read-write	Setting this object to true causes the entire system to reset.
INT acChassisRevision	1.3.6.1.4.1.2785.2.1.2.1.8	INTEGER	read-only	The revision of the chassis expressed as an integer monotonically increasing from 0 to 255.
ACR acChassisRingId	1.3.6.1.4.1.2785.2.1.2.1.27	AcRingId	read-write	A unique Ring Identification number which is assigned by the EMS system to uniquely identify the Appian Ring supported by this node.
STR acChassisRingName	1.3.6.1.4.1.2785.2.1.2.1.28	DisplayString	read-write	A user defined string assigned to the Ring Id which uniquely identifies the Appian Ring supported by this node.
STR acChassisSerialNumber	1.3.6.1.4.1.2785.2.1.2.1.6	DisplayString	read-only	Display string containing the serial number which is read from the chassis backplane prom.
TIK acChassisSysUpTimeEx	1.3.6.1.4.1.2785.2.1.2.1.24	TimeTicks	read-only	The 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.
acChassisTable	1.3.6.1.4.1.2785.2.1.2		not-accessible	A table of configuration and statistics parameters for an Appian Communications chassis's within an Appian ring.
INT acChassisTdmAccessRedundancyMode	1.3.6.1.4.1.2785.2.1.2.1.35	INTEGER	read-write	This 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.
INT acChassisTemperature	1.3.6.1.4.1.2785.2.1.2.1.9	INTEGER	read-only	The 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.
NTF acChassisTemperatureClearTrap	1.3.6.1.4.1.2785.2.1.0.4			The temperature for this chassis has returned back to the normal operational range.
NTF acChassisTemperatureTrap	1.3.6.1.4.1.2785.2.1.0.2			The temperature for this chassis has exceeded or fallen below the normal operational range.
acChassisTraps	1.3.6.1.4.1.2785.2.1.0
acGlobals	1.3.6.1.4.1.2785.2.1.1
ACA acMgmtAccessAdminStatus	1.3.6.1.4.1.2785.2.1.3.1.4	AcAdminStatus	read-create	This 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.
acMgmtAccessEntry	1.3.6.1.4.1.2785.2.1.3.1		not-accessible	A 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.
INT acMgmtAccessFrDlci	1.3.6.1.4.1.2785.2.1.3.1.9	INTEGER	read-create	The Frame-Relay DLCI number used for in-band management access to the network element when the access interface uses a frame-relay trunk.
INT acMgmtAccessIndex	1.3.6.1.4.1.2785.2.1.3.1.2	INTEGER	accessible-for-notify	Unique identifier of management access interface in this node.
INT acMgmtAccessInterfaceType	1.3.6.1.4.1.2785.2.1.3.1.3	INTEGER	read-create	This 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.
IP acMgmtAccessIpAddress	1.3.6.1.4.1.2785.2.1.3.1.6	IpAddress	read-create	The 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.
IP acMgmtAccessIpSubnet	1.3.6.1.4.1.2785.2.1.3.1.7	IpAddress	read-create	The 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.
ACN acMgmtAccessNodeId	1.3.6.1.4.1.2785.2.1.3.1.1	AcNodeId	accessible-for-notify	A unique node identifier assigned by the EMS to uniquely identify a node within an Appian ring.
ACO acMgmtAccessOpStatus	1.3.6.1.4.1.2785.2.1.3.1.5	AcOpStatus	read-only	This 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.
acMgmtAccessTable	1.3.6.1.4.1.2785.2.1.3		not-accessible	This 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.
INT acMgmtAccessTrunk	1.3.6.1.4.1.2785.2.1.3.1.8	INTEGER	read-create	If 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.
ACN acNodeId	1.3.6.1.4.1.2785.2.1.1.1	AcNodeId	read-write	A 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.

FAQ

What does APPIAN-CHASSIS-MIB tell you about an Appian OSAP optical chassis?
It reports hardware inventory (model number, serial number, production date, revision) plus acChassisAdminStatus/acChassisOpStatus for whether the chassis is administratively enabled and operationally functioning, and acChassisTemperature for thermal monitoring — giving a quick picture of overall chassis health.

Would I use APPIAN-CHASSIS-MIB alone to manage an Appian optical transport node?
Typically not by itself — it's commonly loaded alongside other Appian MIBs covering individual line cards and ports, with APPIAN-CHASSIS-MIB giving the top-level chassis view first before configuring automated polling of card and port-level data.

RFC description

Appian chassis management MIB for Appian optical networking equipment.

Start monitoring Appian Communications OSAP SONET/optical access platform (legacy) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download APPIAN-CHASSIS-MIB