AD | Application | AWS | Azure | Cloud | Database | Enterprise | Environmental | Event Log | File System | Infra | IoT | IT Service | Linux | Network/System | Performance | Protocol | SaaS | Security | Service Level | SNMP | Storage | VMware | VoIP | Web | Wireless

Crumbtrail

MonitorTools.com » Technical documentation » SNMP » MIB » Enterasys-Networks-Inc » CTRON-FDDI-FNB-MIB » Objects

CTRON-FDDI-FNB-MIB.mib object view, vendor Enterasys-Networks-Inc

Introduction

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

ActiveXperts Network Monitor 2024 can import MIB file CTRON-FDDI-FNB-MIB and use it to monitor vendor specific OID's.

CTRON-FDDI-FNB-MIB file content

Object view of CTRON-FDDI-FNB-MIB:

Scalar Object
ctFDDIResourceEntry .1.3.6.1.4.1.52.4.1.2.5.1.1.1.1
Defines a specific physical resource entry
ctFDDINonMuxCapEntry .1.3.6.1.4.1.52.4.1.2.5.1.2.1.1
Describes a particular capability/configuration entry.
ctFDDINonMuxCapEnableEntry .1.3.6.1.4.1.52.4.1.2.5.1.2.2.1
Describes a specific configuration enable entry.
ctFDDINonMuxConnectionEntry .1.3.6.1.4.1.52.4.1.2.5.1.2.3.1
Defines a specific configuration connection entry.
ctFDDINonMuxInterfaceEntry .1.3.6.1.4.1.52.4.1.2.5.1.2.4.1
A specfic non multiplexing module interface definition.
ctFDDIMuxCapEntry .1.3.6.1.4.1.52.4.1.2.5.1.3.1.1
Describes a specfic FDDI multiplexor capability/configuration entry.
ctFDDIMuxCapEnableEntry .1.3.6.1.4.1.52.4.1.2.5.1.3.2.1
Describes a specific configuration enable entry.
ctFDDIMuxOutEntry .1.3.6.1.4.1.52.4.1.2.5.1.3.3.1
Describes a particular multiplexor output.
ctFDDIMuxMasterPortEntry .1.3.6.1.4.1.52.4.1.2.5.1.3.4.1
A specific FDDI-FNB multiplexed master port definition.
ctFDDINumbModules .1.3.6.1.4.1.52.4.1.2.5.1.4.1
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.
ctFDDISerialConfigEntry .1.3.6.1.4.1.52.4.1.2.5.1.4.2.1
Describes the controls over a single FNB serial control entry.
ctFDDIModuleFPIMEntry .1.3.6.1.4.1.52.4.1.2.5.1.4.3.1
Describes a single FDDI FPIM on a module.
Tabular Object
ctFDDIResourceSlotID .1.3.6.1.4.1.52.4.1.2.5.1.1.1.1.1
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
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
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
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).
ctFDDINMSlot .1.3.6.1.4.1.52.4.1.2.5.1.2.1.1.1
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
The instance of a particular configuration.
ctFDDINMConfig .1.3.6.1.4.1.52.4.1.2.5.1.2.1.1.3
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
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.
ctFDDINMEnableSlot .1.3.6.1.4.1.52.4.1.2.5.1.2.2.1.1
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
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.
ctFDDINMConnectionSlot .1.3.6.1.4.1.52.4.1.2.5.1.2.3.1.1
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
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
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
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
The bandwidth utilization in bytes per second.
ctFDDINMFrames .1.3.6.1.4.1.52.4.1.2.5.1.2.3.1.6
The bandwidth utilization in frames per second.
ctFDDINMInterSlot .1.3.6.1.4.1.52.4.1.2.5.1.2.4.1.1
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
The number of interfaces defined on this particular module.
ctFDDIMuxSlot .1.3.6.1.4.1.52.4.1.2.5.1.3.1.1.1
Defines the slot within the chassis for which this multiplexed capability/configuration entry pertains.
ctFDDIMuxConfig .1.3.6.1.4.1.52.4.1.2.5.1.3.1.1.3
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'
ctFDDIMuxConfigID .1.3.6.1.4.1.52.4.1.2.5.1.3.1.1.2
The instance of a particular configuration.
ctFDDIMuxConfigDesc .1.3.6.1.4.1.52.4.1.2.5.1.3.1.1.4
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.
ctFDDIMuxEnableSlot .1.3.6.1.4.1.52.4.1.2.5.1.3.2.1.1
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
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
Depicts the number of changes to the master port to multiplexor output mapping.
ctFDDIMuxOutSlot .1.3.6.1.4.1.52.4.1.2.5.1.3.3.1.1
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
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
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
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
The bandwidth utilization in bytes per second.
ctFDDIMuxFrames .1.3.6.1.4.1.52.4.1.2.5.1.3.3.1.6
The bandwidth utilization in frames per second.
ctFDDIMuxMasterPortSlotID .1.3.6.1.4.1.52.4.1.2.5.1.3.4.1.1
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
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
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
Defines a specific port within the FDDI MIBs fddimibPORTTable.
ctFDDISerialSlotID .1.3.6.1.4.1.52.4.1.2.5.1.4.2.1.1
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
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.
ctFDDISerialOperStatus .1.3.6.1.4.1.52.4.1.2.5.1.4.2.1.3
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.
ctFddiFPIMSlotID .1.3.6.1.4.1.52.4.1.2.5.1.4.3.1.1
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
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
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.
ctFddiFPIMType .1.3.6.1.4.1.52.4.1.2.5.1.4.3.1.5
Describes the type of FPIM as found in ctron-oids.
Table
ctFDDIResourceTable .1.3.6.1.4.1.52.4.1.2.5.1.1.1
This table specifies the physical resources associated with the FNB and general FNB operation for a particular module in a particular slot.
ctFDDINonMuxCapTable .1.3.6.1.4.1.52.4.1.2.5.1.2.1
This table describes all possible capabilities/configurations for all non-muxed FDDI configurations within the chassis.
ctFDDINonMuxCapEnableTable .1.3.6.1.4.1.52.4.1.2.5.1.2.2
This table describes the currently enabled configuration for each module.
ctFDDINonMuxConnectionTable .1.3.6.1.4.1.52.4.1.2.5.1.2.3
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.
ctFDDINonMuxInterfaceTable .1.3.6.1.4.1.52.4.1.2.5.1.2.4
This table describs the number of interfaces defined by each non multiplexing FDDI FNB module.
ctFDDIMuxCapTable .1.3.6.1.4.1.52.4.1.2.5.1.3.1
This table describes all possible configuration/capabilities defined for a FDDI multiplexing module.
ctFDDIMuxCapEnableTable .1.3.6.1.4.1.52.4.1.2.5.1.3.2
This table describes the currently enabled configuration for each module.
ctFDDIMuxOutTable .1.3.6.1.4.1.52.4.1.2.5.1.3.3
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.
ctFDDIMuxMasterPortTable .1.3.6.1.4.1.52.4.1.2.5.1.3.4
A list of entries that define master ports as they are defined for the given multiplexed FDDI connection.
ctFDDISerialConfigTable .1.3.6.1.4.1.52.4.1.2.5.1.4.2
This table describes the adminstrative control over each of the FNB serial control modules.
ctFDDIModuleFPIMTable .1.3.6.1.4.1.52.4.1.2.5.1.4.3
This table describes the FPIMs that are on the front panel of each FDDI serial control module, if that module supports FPIMs.
Object Identifier
ctFDDIResource .1.3.6.1.4.1.52.4.1.2.5.1.1
ctFDDINonMux .1.3.6.1.4.1.52.4.1.2.5.1.2
ctFDDIMux .1.3.6.1.4.1.52.4.1.2.5.1.3
ctFDDISerialConfig .1.3.6.1.4.1.52.4.1.2.5.1.4