CXChassis2-MIB: View SNMP OID List / Download MIB

VENDOR: MEMOTEC COMMUNICATIONS


 Home MIB: CXChassis2-MIB
Download as:   
SNMPv2-CONF, CXProduct-SMI, SNMPv2-TC, SNMPv2-SMI

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 cxChassIfAdmGroup 1.3.6.1.4.1.495.2.1.9.5
     cxChassLogIfAdmTable 1.3.6.1.4.1.495.2.1.9.5.2 no-access
A table containing mappings from ifIndex to CPU, type and logical channel.
         cxChassLogIfAdmEntry 1.3.6.1.4.1.495.2.1.9.5.2.1 no-access
Row representing a mapping entry of ifIndex to CPU, type and logical channel.
             cxChassLogIfAdmCpuIndex 1.3.6.1.4.1.495.2.1.9.5.2.1.1 integer read-only
The 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'.
             cxChassLogIfAdmIfType 1.3.6.1.4.1.495.2.1.9.5.2.1.2 integer read-write
The type of interface to be created.
             cxChassLogIfAdmChannelIndex 1.3.6.1.4.1.495.2.1.9.5.2.1.3 integer read-only
The 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.
             cxChassLogIfAdmIfIndex 1.3.6.1.4.1.495.2.1.9.5.2.1.4 integer read-write
The 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.
             cxChassLogIfAdmRowStatus 1.3.6.1.4.1.495.2.1.9.5.2.1.5 rowstatus read-write
Used to create and deleted rows in this table.
 ifMIB 1.3.6.1.4.1.495.2.1.9.6
     ifMIBObjects 1.3.6.1.4.1.495.2.1.9.6.1
         ifStackTable 1.3.6.1.4.1.495.2.1.9.6.1.2 no-access
The 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.
             ifStackEntry 1.3.6.1.4.1.495.2.1.9.6.1.2.1 no-access
Information 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.
                 ifStackHigherLayer 1.3.6.1.4.1.495.2.1.9.6.1.2.1.1 integer read-only
The 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.
                 ifStackLowerLayer 1.3.6.1.4.1.495.2.1.9.6.1.2.1.2 integer read-only
The 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.
                 ifStackStatus 1.3.6.1.4.1.495.2.1.9.6.1.2.1.3 rowstatus read-write
The 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.