All MIBs › CTRON-FDDI-FNB-MIB › ctFDDINMConfig
ctFDDINMConfig
Module: CTRON-FDDI-FNB-MIB
OID (symbolic): CTRON-FDDI-FNB-MIB::ctFDDINMConfig
OID (numeric): 1.3.6.1.4.1.52.4.1.2.5.1.2.1.1.3
Node type: OBJECT-TYPE
Type: DisplayString
Access: read-only
Description: This object defines a specific valid connection configuration. It will specify the connection state of all resource instances. If an instance of a resource is not specified, then it is disconnected.
Each valid configuration is encoded in an ascii string, using a specified format for interpretation. The connection specifications are in groups of four where each group defines a specific connection configuration. The terms of a connection group is defined as follows:
1st - The resource ID as defined by ctFDDIResourceID.
2nd - A specific instance of the physical resource. This will be a value between 1 and ctFDDIResourceNumbInstance for the particular resource ID in the first term. If a resource ID has more than one specific resource instance, but the whole resource can be connected, then this term will have the value '0' to signify all instances of the resource.
3rd - The connection ID for this specific physical resource. This value is the same as ctFDDINMConnectionID, and through the ctFDDINonMuxConnectionTable maps to a specific instance of SMT and MAC.
For example if the value of this object is '1.1.2.2.1.1', then it states that resource 1, instance 1 is connected to connection ID 2 and resource 2, instance 1 is connected to connection ID 1 and is inserted into its FDDI ring.
If a valid configuration is no connections then this object will have a value of '0.0.0'
What is ctFDDINMConfig?
This is an encoded ASCII string precisely specifying the connected or disconnected state of every resource instance on this module for a specific configuration option, laid out in groups of four. It is the machine-parseable form used internally to represent a wiring layout, rather than something an admin would read directly. For example, comparing the encoded strings for config ID 1 versus config ID 2 reveals they differ in how the FNB rings are cross-connected internally.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.52.4.1.2.5.1.2.1.1.3 snmpwalk -v2c -c public <target> CTRON-FDDI-FNB-MIB::ctFDDINMConfig
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.52.4.1.2.5.1.2.1.1.3.1 snmpget -v2c -c public <target> CTRON-FDDI-FNB-MIB::ctFDDINMConfig.1
Start monitoring Cabletron FDDI concentrator/hub (FNB backplane) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CTRON-FDDI-FNB-MIB::ctFDDINMConfig OID value, configure state conditions and alerts, and monitor any Cabletron FDDI concentrator/hub (FNB backplane) from a single console.
OID Breakdown
Upper-level ancestors (12 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.52 | cabletron | Cabletron-MIB |
| 1.3.6.1.4.1.52.4 | mibs | CT-PRIORITY-QUEUING |
| 1.3.6.1.4.1.52.4.1 | ctron | CTRON-MIB-NAMES |
| 1.3.6.1.4.1.52.4.1.2 | ctDataLink | CTRON-MIB-NAMES |
| 1.3.6.1.4.1.52.4.1.2.5 | ctFDDI | CTRON-MIB-NAMES |
| 1.3.6.1.4.1.52.4.1.2.5.1 | ctFDDIFnb | CTRON-MIB-NAMES |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.52.4.1.2.5.1.2 | ctFDDINonMux | CTRON-FDDI-FNB-MIB |
| 1.3.6.1.4.1.52.4.1.2.5.1.2.1 | ctFDDINonMuxCapTable | CTRON-FDDI-FNB-MIB |
| 1.3.6.1.4.1.52.4.1.2.5.1.2.1.1 | ctFDDINonMuxCapEntry | CTRON-FDDI-FNB-MIB |
| 1.3.6.1.4.1.52.4.1.2.5.1.2.1.1.3 | ctFDDINMConfig | CTRON-FDDI-FNB-MIB |