CXChassis2-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for CXChassis2-MIB.
16
Objects
Active
Status
2
Dependencies
Imported Objects
Objects
16 total| Object Name |
|---|
cxChassIfAdmGroup OBJECT IDENTIFIER .1.3.6.1.4.1.495.2.1.9.5 |
IMPORTS Unknown .1.3.6.1.4.1.495.2.1.9.5 |
cxChassLogIfAdmTableA table containing mappings from ifIndex to CPU, type and logical channel. SEQUENCE OF CxChassLogIfAdmEntry .1.3.6.1.4.1.495.2.1.9.5.2 |
cxChassLogIfAdmEntryRow representing a mapping entry of ifIndex to CPU, type and logical channel. CxChassLogIfAdmEntry .1.3.6.1.4.1.495.2.1.9.5.2.1 |
cxChassLogIfAdmCpuIndexThe CPU number which corresponds to the slot number in the chassis. For example, a row for CPU in slot 2 will use value '2'. For single CPU chassis, the value to be used is '1'.ro INTEGER .1.3.6.1.4.1.495.2.1.9.5.2.1.1 |
cxChassLogIfAdmIfTypeThe type of interface to be created.rw IANAifType SYNTAX INTEGER .1.3.6.1.4.1.495.2.1.9.5.2.1.2 |
cxChassLogIfAdmChannelIndexThe channel number belonging to a port in the IO card in a CPU. If the port is not channelized, then it will have only one entry in the table with this object set to value '1'.
Within our system, a channel will be associated with its own service access point, thus requiring the use of a service access point control block. This object therefore takes on the sap control block identification. Due to the internal sap control block numbering limitation, this object will be restricted in range from 1 to 255, but may be expanded when the internal limitations are lifted.ro INTEGER .1.3.6.1.4.1.495.2.1.9.5.2.1.3 |
cxChassLogIfAdmIfIndexThe Interface index which corressponds to the ifIndex in the ifTable. If this value is specified, then it is the registered ifIndex used for the interface, otherwise the ifIndex will be obtained from the ifTable.rw INTEGER .1.3.6.1.4.1.495.2.1.9.5.2.1.4 |
cxChassLogIfAdmRowStatusUsed to create and deleted rows in this table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.495.2.1.9.5.2.1.5 |
ifMIB OBJECT IDENTIFIER .1.3.6.1.4.1.495.2.1.9.6 |
ifMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.495.2.1.9.6.1 |
ifStackTableThe table containing information on the relationships between the multiple sub-layers of network interfaces. In particular, it contains information on which sub-layers run 'on top of' which other sub-layers. Each sub-layer corresponds to a conceptual row in the ifTable. SEQUENCE OF IfStackEntry .1.3.6.1.4.1.495.2.1.9.6.1.2 |
ifStackEntryInformation on a particular relationship between two sub-layers, specifying that one sub-layer runs on 'top' of the other sub-layer. Each sub-layer corresponds to a conceptual row in the ifTable. IfStackEntry .1.3.6.1.4.1.495.2.1.9.6.1.2.1 |
ifStackHigherLayerThe value of ifIndex corresponding to the higher sub-layer of the relationship, i.e., the sub-layer which runs on 'top' of the sub-layer identified by the corresponding instance of ifStackLowerLayer. If there is no higher sub-layer (below the internetwork layer), then this object has the value 0.ro INTEGER .1.3.6.1.4.1.495.2.1.9.6.1.2.1.1 |
ifStackLowerLayerThe value of ifIndex corresponding to the lower sub-layer of the relationship, i.e., the sub-layer which runs 'below' the sub-layer identified by the corresponding instance of ifStackHigherLayer. If there is no lower sub-layer, then this object has the value 0.ro INTEGER .1.3.6.1.4.1.495.2.1.9.6.1.2.1.2 |
ifStackStatusThe status of the relationship between two sub-layers.
Changing the value of this object from 'active' to 'notInService' or 'destroy' will likely have consequences up and down the interface stack. Thus, write access to this object is likely to be inappropriate for some types of interfaces, and many implementations will choose not to support write-access for any type of interface.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.495.2.1.9.6.1.2.1.3 |