CTRON-FDDI-FNB-MIB :: ctFDDIMuxConfig

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CTRON-FDDI-FNB-MIB › ctFDDIMuxConfig

ctFDDIMuxConfig

Module: CTRON-FDDI-FNB-MIB

OID (symbolic): CTRON-FDDI-FNB-MIB::ctFDDIMuxConfig

OID (numeric): 1.3.6.1.4.1.52.4.1.2.5.1.3.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 specific connections are in groups of four where each group defines a specific connection configuration. The terms of the connection group are defined as follows:

1st - Resource ID. The value is the same as ctFDDIResourceID for a specific resource entry.

2nd - Instance of the resource. This has a value in the range of 1 to ctFDDIResourceNumbInstance.

3rd - Path of the resource as input to the multiplexor. Paths are specified as 1 for the primary ring and 2 for the secondary.

4th - This is the multiplexor output channel that this resource comes out of the multiplexor. This value is the same as a value of ctFDDIMuxOutID.

5th - Ring Connectivity. This sub-identifier describes if the given mux-in resource (sub-identifiers 1-3) is inserted into the backplane FNB ring. Valid values are 0 for no 1 for yes.

So for example a value of 1.1.1.1.0.2.2.2.2.1 is resource 1, instance 1 (primary) is on mux-out 1 and it's not inserted; resource 2, instance 2 (secondary) is on mux-out 2 and is inserted into the backplane.

If a valid configuration is no connections then this object will have a value of '0.0.0.0.0'

What is ctFDDIMuxConfig?

This is an encoded ASCII string specifying the connection state of every multiplexor resource instance for a specific mux configuration option, laid out in groups of four. Like its Network Module table counterpart, this is a machine-parseable encoding rather than a human-friendly description. For example, comparing the encoded strings for two different mux config IDs reveals which output ports get remapped between them.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.52.4.1.2.5.1.3.1.1.3
snmpwalk -v2c -c public <target> CTRON-FDDI-FNB-MIB::ctFDDIMuxConfig

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.52.4.1.2.5.1.3.1.1.3.1
snmpget -v2c -c public <target> CTRON-FDDI-FNB-MIB::ctFDDIMuxConfig.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::ctFDDIMuxConfig 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 OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.52cabletronCabletron-MIB
1.3.6.1.4.1.52.4mibsCT-PRIORITY-QUEUING
1.3.6.1.4.1.52.4.1ctronCTRON-MIB-NAMES
1.3.6.1.4.1.52.4.1.2ctDataLinkCTRON-MIB-NAMES
1.3.6.1.4.1.52.4.1.2.5ctFDDICTRON-MIB-NAMES
1.3.6.1.4.1.52.4.1.2.5.1ctFDDIFnbCTRON-MIB-NAMES
Numeric OIDNameModule
1.3.6.1.4.1.52.4.1.2.5.1.3ctFDDIMuxCTRON-FDDI-FNB-MIB
1.3.6.1.4.1.52.4.1.2.5.1.3.1ctFDDIMuxCapTableCTRON-FDDI-FNB-MIB
1.3.6.1.4.1.52.4.1.2.5.1.3.1.1ctFDDIMuxCapEntryCTRON-FDDI-FNB-MIB
1.3.6.1.4.1.52.4.1.2.5.1.3.1.1.3ctFDDIMuxConfigCTRON-FDDI-FNB-MIB