CTRON-FDDI-FNB-MIB: View SNMP OID List / Download MIB

VENDOR: ENTERASYS NETWORKS INC.


 Home MIB: CTRON-FDDI-FNB-MIB
Download as:   
SNMPv2-CONF, SNMPv2-SMI, SNMPv2-TC, CTRON-MIB-NAMES

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
 ctFDDIResource 1.3.6.1.4.1.52.4.1.2.5.1.1
     ctFDDIResourceTable 1.3.6.1.4.1.52.4.1.2.5.1.1.1 no-access
This table specifies the physical resources associated with the FNB and general FNB operation for a particular module in a particular slot.
         ctFDDIResourceEntry 1.3.6.1.4.1.52.4.1.2.5.1.1.1.1 no-access
Defines a specific physical resource entry
             ctFDDIResourceSlotID 1.3.6.1.4.1.52.4.1.2.5.1.1.1.1.1 integer read-only
A specific instance of a slot as defined by chSlotID as defined in the chassis MIB.
             ctFDDIResourceID 1.3.6.1.4.1.52.4.1.2.5.1.1.1.1.2 integer read-only
A unique index that defines a specific physcial resource for which this relationship exists. The value of this is as defined by chResourceID in the chassis MIB.
             ctFDDIResourceType 1.3.6.1.4.1.52.4.1.2.5.1.1.1.1.3 object identifier read-only
Defines the type of resource. This is the same value as chResourceType in the chassis MIB.
             ctFDDIResourceNumbInstance 1.3.6.1.4.1.52.4.1.2.5.1.1.1.1.4 integer read-only
This object defines the number of instances of a physical resource. Specific resource instances are physically located from top-to-bottom on a particular module. If there are multiple 'columns' of a resource from the top to the bottom, then the numbering will start from the left side and proceed top-to-bottom in each column. For instance, the first FNB ring will be instance 1 (top in the chassis) while the second FNB ring is instance 2 (below FNB 1 in the backplane).
 ctFDDINonMux 1.3.6.1.4.1.52.4.1.2.5.1.2
     ctFDDINonMuxCapTable 1.3.6.1.4.1.52.4.1.2.5.1.2.1 no-access
This table describes all possible capabilities/configurations for all non-muxed FDDI configurations within the chassis.
         ctFDDINonMuxCapEntry 1.3.6.1.4.1.52.4.1.2.5.1.2.1.1 no-access
Describes a particular capability/configuration entry.
             ctFDDINMSlot 1.3.6.1.4.1.52.4.1.2.5.1.2.1.1.1 integer read-only
The slot within the chassis for which this configuration information is defined.
             ctFDDINMConfigID 1.3.6.1.4.1.52.4.1.2.5.1.2.1.1.2 integer read-only
The instance of a particular configuration.
             ctFDDINMConfig 1.3.6.1.4.1.52.4.1.2.5.1.2.1.1.3 displaystring read-only
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'
             ctFDDINMConfigDesc 1.3.6.1.4.1.52.4.1.2.5.1.2.1.1.4 displaystring read-only
This object contains a textual description of a valid connection configuration. This is a more user-friendly representation of the configuration than the ctFDDINMConfig object.
     ctFDDINonMuxCapEnableTable 1.3.6.1.4.1.52.4.1.2.5.1.2.2 no-access
This table describes the currently enabled configuration for each module.
         ctFDDINonMuxCapEnableEntry 1.3.6.1.4.1.52.4.1.2.5.1.2.2.1 no-access
Describes a specific configuration enable entry.
             ctFDDINMEnableSlot 1.3.6.1.4.1.52.4.1.2.5.1.2.2.1.1 integer read-only
A specific slot for which this configuration enable pertains.
             ctFDDINMCapEnable 1.3.6.1.4.1.52.4.1.2.5.1.2.2.1.2 integer read-write
A specific configuration that is enabled. Enabling a configuration is done by writing the value of ctFDDINMConfigID for a specific configuration to this object. This object, when read, will return the value of ctFDDINMConfigID for the presently enabled configuration.
     ctFDDINonMuxConnectionTable 1.3.6.1.4.1.52.4.1.2.5.1.2.3 no-access
This table defines specific information for each defined FDDI/FNB connection. This maps the third sub identifier of ctFDDINMConfig to a particular SMT and MAC instance in the 1512 FDDI MIB.
         ctFDDINonMuxConnectionEntry 1.3.6.1.4.1.52.4.1.2.5.1.2.3.1 no-access
Defines a specific configuration connection entry.
             ctFDDINMConnectionSlot 1.3.6.1.4.1.52.4.1.2.5.1.2.3.1.1 integer read-only
A specific slot for which this connection entry is defined.
             ctFDDINMConnectionID 1.3.6.1.4.1.52.4.1.2.5.1.2.3.1.2 integer read-only
Describes a specific connection identifier. Valid connection identifiers are defined by the third sub-identifier in ctFDDINMConfig as identified by ctFDDINMCapEnable.
             ctFDDINMSMT 1.3.6.1.4.1.52.4.1.2.5.1.2.3.1.3 integer read-only
A specific instance of SMT for which this entry pertains.
             ctFDDINMMAC 1.3.6.1.4.1.52.4.1.2.5.1.2.3.1.4 integer read-only
A specific MAC that this connection entry pertains.
             ctFDDINMBytes 1.3.6.1.4.1.52.4.1.2.5.1.2.3.1.5 integer read-only
The bandwidth utilization in bytes per second.
             ctFDDINMFrames 1.3.6.1.4.1.52.4.1.2.5.1.2.3.1.6 integer read-only
The bandwidth utilization in frames per second.
     ctFDDINonMuxInterfaceTable 1.3.6.1.4.1.52.4.1.2.5.1.2.4 no-access
This table describs the number of interfaces defined by each non multiplexing FDDI FNB module.
         ctFDDINonMuxInterfaceEntry 1.3.6.1.4.1.52.4.1.2.5.1.2.4.1 no-access
A specfic non multiplexing module interface definition.
             ctFDDINMInterSlot 1.3.6.1.4.1.52.4.1.2.5.1.2.4.1.1 integer read-only
A specific slot for which this inteface entry is defined.
             ctFDDINMNumbInterfaces 1.3.6.1.4.1.52.4.1.2.5.1.2.4.1.2 integer read-only
The number of interfaces defined on this particular module.
 ctFDDIMux 1.3.6.1.4.1.52.4.1.2.5.1.3
     ctFDDIMuxCapTable 1.3.6.1.4.1.52.4.1.2.5.1.3.1 no-access
This table describes all possible configuration/capabilities defined for a FDDI multiplexing module.
         ctFDDIMuxCapEntry 1.3.6.1.4.1.52.4.1.2.5.1.3.1.1 no-access
Describes a specfic FDDI multiplexor capability/configuration entry.
             ctFDDIMuxSlot 1.3.6.1.4.1.52.4.1.2.5.1.3.1.1.1 integer read-only
Defines the slot within the chassis for which this multiplexed capability/configuration entry pertains.
             ctFDDIMuxConfigID 1.3.6.1.4.1.52.4.1.2.5.1.3.1.1.2 integer read-only
The instance of a particular configuration.
             ctFDDIMuxConfig 1.3.6.1.4.1.52.4.1.2.5.1.3.1.1.3 displaystring read-only
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'
             ctFDDIMuxConfigDesc 1.3.6.1.4.1.52.4.1.2.5.1.3.1.1.4 displaystring read-only
This object contains a textual description of a valid connection configuration. This is a more user-friendly representation of the configuration than the ctFDDIMuxConfig object.
     ctFDDIMuxCapEnableTable 1.3.6.1.4.1.52.4.1.2.5.1.3.2 no-access
This table describes the currently enabled configuration for each module.
         ctFDDIMuxCapEnableEntry 1.3.6.1.4.1.52.4.1.2.5.1.3.2.1 no-access
Describes a specific configuration enable entry.
             ctFDDIMuxEnableSlot 1.3.6.1.4.1.52.4.1.2.5.1.3.2.1.1 integer read-only
A specific slot for which this configuration enable pertains.
             ctFDDIMuxCapEnable 1.3.6.1.4.1.52.4.1.2.5.1.3.2.1.2 integer read-write
A specific instance of the configuration that is enabled. Setting this object with a specific value of ctFDDIMuxConfigID enabled that configuration. A request of the value of this object will return the value of ctFDDIMuxConfigID for the presently enabled configuration.
             ctFDDIMuxMasterPortAssignmentChange 1.3.6.1.4.1.52.4.1.2.5.1.3.2.1.3 counter read-only
Depicts the number of changes to the master port to multiplexor output mapping.
     ctFDDIMuxOutTable 1.3.6.1.4.1.52.4.1.2.5.1.3.3 no-access
Describes the multiplexor outputs for each of the FNB multiplexor modules. This maps the multiplexor output to a specific instance of MAC and SMT in the FDDI MIB.
         ctFDDIMuxOutEntry 1.3.6.1.4.1.52.4.1.2.5.1.3.3.1 no-access
Describes a particular multiplexor output.
             ctFDDIMuxOutSlot 1.3.6.1.4.1.52.4.1.2.5.1.3.3.1.1 integer read-only
The given slot for which this multiplexor output information pertains.
             ctFDDIMuxOutID 1.3.6.1.4.1.52.4.1.2.5.1.3.3.1.2 integer read-only
The specific instance of the multiplexor output. Instances of this object are used by the values of ctFDDIMuxConfig.
             ctFDDIMuxOutMACIndex 1.3.6.1.4.1.52.4.1.2.5.1.3.3.1.3 integer read-only
The MAC instance of this multiplexor output. If this this object has a value greater than 0, then this value is the same as fddimibMACIndex. If this object has the value of 0, the given mux-out does not have a MAC.
             ctFDDIMuxOutSMTIndex 1.3.6.1.4.1.52.4.1.2.5.1.3.3.1.4 integer read-only
Identifies the instance of SMT as defined within the FDDI MIB.
             ctFDDIMuxBytes 1.3.6.1.4.1.52.4.1.2.5.1.3.3.1.5 integer read-only
The bandwidth utilization in bytes per second.
             ctFDDIMuxFrames 1.3.6.1.4.1.52.4.1.2.5.1.3.3.1.6 integer read-only
The bandwidth utilization in frames per second.
     ctFDDIMuxMasterPortTable 1.3.6.1.4.1.52.4.1.2.5.1.3.4 no-access
A list of entries that define master ports as they are defined for the given multiplexed FDDI connection.
         ctFDDIMuxMasterPortEntry 1.3.6.1.4.1.52.4.1.2.5.1.3.4.1 no-access
A specific FDDI-FNB multiplexed master port definition.
             ctFDDIMuxMasterPortSlotID 1.3.6.1.4.1.52.4.1.2.5.1.3.4.1.1 integer read-only
A specific instance of a slot as defined by chSlotID.
             ctFDDIMuxMasterPortID 1.3.6.1.4.1.52.4.1.2.5.1.3.4.1.2 integer read-only
A unique identifier for this specific master port.
             ctFDDIMuxMasterPortAssignment 1.3.6.1.4.1.52.4.1.2.5.1.3.4.1.3 integer read-write
Provides the masterport to multiplexor output mapping. This is as defined by ctFDDIMuxOutMacAssignment.
             ctFDDIMuxMasterPortIndex 1.3.6.1.4.1.52.4.1.2.5.1.3.4.1.4 integer read-only
Defines a specific port within the FDDI MIBs fddimibPORTTable.
 ctFDDISerialConfig 1.3.6.1.4.1.52.4.1.2.5.1.4
     ctFDDINumbModules 1.3.6.1.4.1.52.4.1.2.5.1.4.1 integer read-only
Describes the number of modules that are present configurable thru the serial control portion of this MIB. This directly reflects the number of rows found within the ctFDDISerialConfigTable.
     ctFDDISerialConfigTable 1.3.6.1.4.1.52.4.1.2.5.1.4.2 no-access
This table describes the adminstrative control over each of the FNB serial control modules.
         ctFDDISerialConfigEntry 1.3.6.1.4.1.52.4.1.2.5.1.4.2.1 no-access
Describes the controls over a single FNB serial control entry.
             ctFDDISerialSlotID 1.3.6.1.4.1.52.4.1.2.5.1.4.2.1.1 integer read-only
Defines the slot that this FNB serial control module is in. This is an instance of chSlotID as defined in the chassis MIB.
             ctFDDISerialAdminStatus 1.3.6.1.4.1.52.4.1.2.5.1.4.2.1.2 integer read-write
Describes the adminstrative desired state for this FNB serial control module. insertFNB1(1) - The serial controlled module should be inserted into FNB-1 and bypass FNB-2. insertFNB2(2) - The serial contolled module should be inserted into FNB-2 and bypass FNB-1. insertFNB1FNB2(3) - Insert the serial controlled module on both FNBs. bypass(4) - Bypass the connection to both FNBs. hwControlFNB1(5) - Use hardware settings for FNB-1. hwControlFNB2(6) - Use hardware settings for FNB-2. hwControl(7) - Use the hardware settings for both FNBs. Enumeration: 'insertFNB1FNB2': 3, 'insertFNB2': 2, 'insertFNB1': 1, 'hwControlFNB1': 5, 'bypass': 4, 'hwControlFNB2': 6, 'hwControl': 7.
             ctFDDISerialOperStatus 1.3.6.1.4.1.52.4.1.2.5.1.4.2.1.3 integer read-only
Describes the operational status of this FDDI serial controlled module. insertFNB1(1) - The serial controlled module is inserted into FNB-1 and bypassed from FNB-2. insertFNB2(2) - The serial controlled module is bypassed from FNB-1 and inserted into FNB-2. insertFNB1FNB2(3) - The serial controlled module is inserted into both FNB-1 and FNB-2. bypass(4) - The serial controlled module is bypassed from both FNB-1 and FNB-2. Enumeration: 'insertFNB1FNB2': 3, 'bypass': 4, 'insertFNB2': 2, 'insertFNB1': 1.
     ctFDDIModuleFPIMTable 1.3.6.1.4.1.52.4.1.2.5.1.4.3 no-access
This table describes the FPIMs that are on the front panel of each FDDI serial control module, if that module supports FPIMs.
         ctFDDIModuleFPIMEntry 1.3.6.1.4.1.52.4.1.2.5.1.4.3.1 no-access
Describes a single FDDI FPIM on a module.
             ctFddiFPIMSlotID 1.3.6.1.4.1.52.4.1.2.5.1.4.3.1.1 integer read-only
Defines the slot in which this module exists. This is an instance of chSlotID as found in the chassis MIB.
             ctFddiFPIM 1.3.6.1.4.1.52.4.1.2.5.1.4.3.1.2 integer read-only
Defines the instance of the port for which this definition is made. Ports are physically located from top-to-bottom on a particular module. If there are multiple 'columns' of ports from the top to the bottom, then the numbering will start from the left side and proceed top-to-bottom in each column.
             ctFddiFPIMStatus 1.3.6.1.4.1.52.4.1.2.5.1.4.3.1.4 integer read-only
Describes the link status of the given FPIM. A value of link(1) states that a link is present. A value of noLink(2) states that no link is present. A value of notSupported(3) means that link status is not supported by this port and is unknown. Enumeration: 'notSupported': 3, 'link': 1, 'noLink': 2.
             ctFddiFPIMType 1.3.6.1.4.1.52.4.1.2.5.1.4.3.1.5 object identifier read-only
Describes the type of FPIM as found in ctron-oids.