CTRON-FDDI-FNB-MIB
- Registered at
- 1.3.6.1.4.1.52.4.1.2.5.1.11.3.6.1.4.1.52.4.1.2.5.1.21.3.6.1.4.1.52.4.1.2.5.1.31.3.6.1.4.1.52.4.1.2.5.1.4
- Namespace
- enterasys
- Source file
CTRON-FDDI-FNB-MIB- Digest
sha256:7a2707783968898d11d49e673ad04c19f002fdbab8617756c4196d2825f54ae1
Imports
| From | Symbols |
|---|---|
| CTRON-MIB-NAMES | ctFDDIFnb |
| SNMPv2-CONF | MODULE-COMPLIANCE, NOTIFICATION-GROUP |
| SNMPv2-SMI | Counter32, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, iso |
| SNMPv2-TC | DisplayString, TEXTUAL-CONVENTION |
Imported by
Nothing in this corpus imports this module.
Load order
Every file a consumer needs in order to load this module, dependencies first.
CTRON-FDDI-FNB-MIB CTRON-MIB-NAMES CTRON-OIDS SNMPv2-CONF SNMPv2-SMI SNMPv2-TC
Objects
| Name | OID | Syntax | Access | Status |
|---|---|---|---|---|
| ctFDDIResource OBJECT-IDENTITY | 1.3.6.1.4.1.52.4.1.2.5.1.1 | |||
| ctFDDIResourceTable OBJECT-TYPE This table specifies the physical resources associated with the FNB and general FNB operation for a particular module in a particular slot. | 1.3.6.1.4.1.52.4.1.2.5.1.1.1 | not-accessible | mandatory | |
| ctFDDIResourceEntry OBJECT-TYPE Defines a specific physical resource entry | 1.3.6.1.4.1.52.4.1.2.5.1.1.1.1 | not-accessible | mandatory | |
| ctFDDIResourceSlotID OBJECT-TYPE A specific instance of a slot as defined by chSlotID as defined in the chassis MIB. | 1.3.6.1.4.1.52.4.1.2.5.1.1.1.1.1 | INTEGER (1..255) | read-only | mandatory |
| ctFDDIResourceID OBJECT-TYPE 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. | 1.3.6.1.4.1.52.4.1.2.5.1.1.1.1.2 | INTEGER | read-only | mandatory |
| ctFDDIResourceType OBJECT-TYPE Defines the type of resource. This is the same value as chResourceType in the chassis MIB. | 1.3.6.1.4.1.52.4.1.2.5.1.1.1.1.3 | OBJECT IDENTIFIER | read-only | mandatory |
| ctFDDIResourceNumbInstance OBJECT-TYPE 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). | 1.3.6.1.4.1.52.4.1.2.5.1.1.1.1.4 | INTEGER | read-only | mandatory |
| ctFDDINonMux OBJECT-IDENTITY | 1.3.6.1.4.1.52.4.1.2.5.1.2 | |||
| ctFDDINonMuxCapTable OBJECT-TYPE This table describes all possible capabilities/configurations for all non-muxed FDDI configurations within the chassis. | 1.3.6.1.4.1.52.4.1.2.5.1.2.1 | not-accessible | mandatory | |
| ctFDDINonMuxCapEntry OBJECT-TYPE Describes a particular capability/configuration entry. | 1.3.6.1.4.1.52.4.1.2.5.1.2.1.1 | not-accessible | mandatory | |
| ctFDDINMSlot OBJECT-TYPE The slot within the chassis for which this configuration information is defined. | 1.3.6.1.4.1.52.4.1.2.5.1.2.1.1.1 | INTEGER (1..256) | read-only | mandatory |
| ctFDDINMConfigID OBJECT-TYPE The instance of a particular configuration. | 1.3.6.1.4.1.52.4.1.2.5.1.2.1.1.2 | INTEGER | read-only | mandatory |
| ctFDDINMConfig OBJECT-TYPE 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' | 1.3.6.1.4.1.52.4.1.2.5.1.2.1.1.3 | DisplayString | read-only | mandatory |
| ctFDDINMConfigDesc OBJECT-TYPE 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. | 1.3.6.1.4.1.52.4.1.2.5.1.2.1.1.4 | DisplayString | read-only | mandatory |
| ctFDDINonMuxCapEnableTable OBJECT-TYPE This table describes the currently enabled configuration for each module. | 1.3.6.1.4.1.52.4.1.2.5.1.2.2 | not-accessible | mandatory | |
| ctFDDINonMuxCapEnableEntry OBJECT-TYPE Describes a specific configuration enable entry. | 1.3.6.1.4.1.52.4.1.2.5.1.2.2.1 | not-accessible | mandatory | |
| ctFDDINMEnableSlot OBJECT-TYPE A specific slot for which this configuration enable pertains. | 1.3.6.1.4.1.52.4.1.2.5.1.2.2.1.1 | INTEGER | read-only | mandatory |
| ctFDDINMCapEnable OBJECT-TYPE 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. | 1.3.6.1.4.1.52.4.1.2.5.1.2.2.1.2 | INTEGER | read-write | mandatory |
| ctFDDINonMuxConnectionTable OBJECT-TYPE 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. | 1.3.6.1.4.1.52.4.1.2.5.1.2.3 | not-accessible | mandatory | |
| ctFDDINonMuxConnectionEntry OBJECT-TYPE Defines a specific configuration connection entry. | 1.3.6.1.4.1.52.4.1.2.5.1.2.3.1 | not-accessible | mandatory | |
| ctFDDINMConnectionSlot OBJECT-TYPE A specific slot for which this connection entry is defined. | 1.3.6.1.4.1.52.4.1.2.5.1.2.3.1.1 | INTEGER | read-only | mandatory |
| ctFDDINMConnectionID OBJECT-TYPE Describes a specific connection identifier. Valid connection identifiers are defined by the third sub-identifier in ctFDDINMConfig as identified by ctFDDINMCapEnable. | 1.3.6.1.4.1.52.4.1.2.5.1.2.3.1.2 | INTEGER | read-only | mandatory |
| ctFDDINMSMT OBJECT-TYPE A specific instance of SMT for which this entry pertains. | 1.3.6.1.4.1.52.4.1.2.5.1.2.3.1.3 | INTEGER | read-only | mandatory |
| ctFDDINMMAC OBJECT-TYPE A specific MAC that this connection entry pertains. | 1.3.6.1.4.1.52.4.1.2.5.1.2.3.1.4 | INTEGER | read-only | mandatory |
| ctFDDINMBytes OBJECT-TYPE The bandwidth utilization in bytes per second. | 1.3.6.1.4.1.52.4.1.2.5.1.2.3.1.5 | INTEGER | read-only | mandatory |
| ctFDDINMFrames OBJECT-TYPE The bandwidth utilization in frames per second. | 1.3.6.1.4.1.52.4.1.2.5.1.2.3.1.6 | INTEGER | read-only | mandatory |
| ctFDDINonMuxInterfaceTable OBJECT-TYPE This table describs the number of interfaces defined by each non multiplexing FDDI FNB module. | 1.3.6.1.4.1.52.4.1.2.5.1.2.4 | not-accessible | mandatory | |
| ctFDDINonMuxInterfaceEntry OBJECT-TYPE A specfic non multiplexing module interface definition. | 1.3.6.1.4.1.52.4.1.2.5.1.2.4.1 | not-accessible | mandatory | |
| ctFDDINMInterSlot OBJECT-TYPE A specific slot for which this inteface entry is defined. | 1.3.6.1.4.1.52.4.1.2.5.1.2.4.1.1 | INTEGER | read-only | mandatory |
| ctFDDINMNumbInterfaces OBJECT-TYPE The number of interfaces defined on this particular module. | 1.3.6.1.4.1.52.4.1.2.5.1.2.4.1.2 | INTEGER | read-only | mandatory |
| ctFDDIMux OBJECT-IDENTITY | 1.3.6.1.4.1.52.4.1.2.5.1.3 | |||
| ctFDDIMuxCapTable OBJECT-TYPE This table describes all possible configuration/capabilities defined for a FDDI multiplexing module. | 1.3.6.1.4.1.52.4.1.2.5.1.3.1 | not-accessible | mandatory | |
| ctFDDIMuxCapEntry OBJECT-TYPE Describes a specfic FDDI multiplexor capability/configuration entry. | 1.3.6.1.4.1.52.4.1.2.5.1.3.1.1 | not-accessible | mandatory | |
| ctFDDIMuxSlot OBJECT-TYPE Defines the slot within the chassis for which this multiplexed capability/configuration entry pertains. | 1.3.6.1.4.1.52.4.1.2.5.1.3.1.1.1 | INTEGER (1..256) | read-only | mandatory |
| ctFDDIMuxConfigID OBJECT-TYPE The instance of a particular configuration. | 1.3.6.1.4.1.52.4.1.2.5.1.3.1.1.2 | INTEGER | read-only | mandatory |
| ctFDDIMuxConfig OBJECT-TYPE 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' | 1.3.6.1.4.1.52.4.1.2.5.1.3.1.1.3 | DisplayString | read-only | mandatory |
| ctFDDIMuxConfigDesc OBJECT-TYPE 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. | 1.3.6.1.4.1.52.4.1.2.5.1.3.1.1.4 | DisplayString | read-only | mandatory |
| ctFDDIMuxCapEnableTable OBJECT-TYPE This table describes the currently enabled configuration for each module. | 1.3.6.1.4.1.52.4.1.2.5.1.3.2 | not-accessible | mandatory | |
| ctFDDIMuxCapEnableEntry OBJECT-TYPE Describes a specific configuration enable entry. | 1.3.6.1.4.1.52.4.1.2.5.1.3.2.1 | not-accessible | mandatory | |
| ctFDDIMuxEnableSlot OBJECT-TYPE A specific slot for which this configuration enable pertains. | 1.3.6.1.4.1.52.4.1.2.5.1.3.2.1.1 | INTEGER (1..256) | read-only | mandatory |
| ctFDDIMuxCapEnable OBJECT-TYPE 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. | 1.3.6.1.4.1.52.4.1.2.5.1.3.2.1.2 | INTEGER | read-write | mandatory |
| ctFDDIMuxMasterPortAssignmentChange OBJECT-TYPE Depicts the number of changes to the master port to multiplexor output mapping. | 1.3.6.1.4.1.52.4.1.2.5.1.3.2.1.3 | Counter | read-only | mandatory |
| ctFDDIMuxOutTable OBJECT-TYPE 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. | 1.3.6.1.4.1.52.4.1.2.5.1.3.3 | not-accessible | mandatory | |
| ctFDDIMuxOutEntry OBJECT-TYPE Describes a particular multiplexor output. | 1.3.6.1.4.1.52.4.1.2.5.1.3.3.1 | not-accessible | mandatory | |
| ctFDDIMuxOutSlot OBJECT-TYPE The given slot for which this multiplexor output information pertains. | 1.3.6.1.4.1.52.4.1.2.5.1.3.3.1.1 | INTEGER (1..255) | read-only | mandatory |
| ctFDDIMuxOutID OBJECT-TYPE The specific instance of the multiplexor output. Instances of this object are used by the values of ctFDDIMuxConfig. | 1.3.6.1.4.1.52.4.1.2.5.1.3.3.1.2 | INTEGER | read-only | mandatory |
| ctFDDIMuxOutMACIndex OBJECT-TYPE 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. | 1.3.6.1.4.1.52.4.1.2.5.1.3.3.1.3 | INTEGER (1..65535) | read-only | mandatory |
| ctFDDIMuxOutSMTIndex OBJECT-TYPE Identifies the instance of SMT as defined within the FDDI MIB. | 1.3.6.1.4.1.52.4.1.2.5.1.3.3.1.4 | INTEGER (1..65535) | read-only | mandatory |
| ctFDDIMuxBytes OBJECT-TYPE The bandwidth utilization in bytes per second. | 1.3.6.1.4.1.52.4.1.2.5.1.3.3.1.5 | INTEGER | read-only | mandatory |
| ctFDDIMuxFrames OBJECT-TYPE The bandwidth utilization in frames per second. | 1.3.6.1.4.1.52.4.1.2.5.1.3.3.1.6 | INTEGER | read-only | mandatory |
| ctFDDIMuxMasterPortTable OBJECT-TYPE A list of entries that define master ports as they are defined for the given multiplexed FDDI connection. | 1.3.6.1.4.1.52.4.1.2.5.1.3.4 | not-accessible | mandatory | |
| ctFDDIMuxMasterPortEntry OBJECT-TYPE A specific FDDI-FNB multiplexed master port definition. | 1.3.6.1.4.1.52.4.1.2.5.1.3.4.1 | not-accessible | mandatory | |
| ctFDDIMuxMasterPortSlotID OBJECT-TYPE A specific instance of a slot as defined by chSlotID. | 1.3.6.1.4.1.52.4.1.2.5.1.3.4.1.1 | INTEGER (1..255) | read-only | mandatory |
| ctFDDIMuxMasterPortID OBJECT-TYPE A unique identifier for this specific master port. | 1.3.6.1.4.1.52.4.1.2.5.1.3.4.1.2 | INTEGER (1..65535) | read-only | mandatory |
| ctFDDIMuxMasterPortAssignment OBJECT-TYPE Provides the masterport to multiplexor output mapping. This is as defined by ctFDDIMuxOutMacAssignment. | 1.3.6.1.4.1.52.4.1.2.5.1.3.4.1.3 | INTEGER | read-write | mandatory |
| ctFDDIMuxMasterPortIndex OBJECT-TYPE Defines a specific port within the FDDI MIBs fddimibPORTTable. | 1.3.6.1.4.1.52.4.1.2.5.1.3.4.1.4 | INTEGER (1..65535) | read-only | mandatory |
| ctFDDISerialConfig OBJECT-IDENTITY | 1.3.6.1.4.1.52.4.1.2.5.1.4 | |||
| ctFDDINumbModules OBJECT-TYPE 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. | 1.3.6.1.4.1.52.4.1.2.5.1.4.1 | INTEGER (0..14) | read-only | mandatory |
| ctFDDISerialConfigTable OBJECT-TYPE This table describes the adminstrative control over each of the FNB serial control modules. | 1.3.6.1.4.1.52.4.1.2.5.1.4.2 | not-accessible | mandatory | |
| ctFDDISerialConfigEntry OBJECT-TYPE Describes the controls over a single FNB serial control entry. | 1.3.6.1.4.1.52.4.1.2.5.1.4.2.1 | not-accessible | mandatory | |
| ctFDDISerialSlotID OBJECT-TYPE Defines the slot that this FNB serial control module is in. This is an instance of chSlotID as defined in the chassis MIB. | 1.3.6.1.4.1.52.4.1.2.5.1.4.2.1.1 | INTEGER | read-only | mandatory |
| ctFDDISerialAdminStatus OBJECT-TYPE 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. | 1.3.6.1.4.1.52.4.1.2.5.1.4.2.1.2 | INTEGER {insertFNB1(1), insertFNB2(2), insertFNB1FNB2(3), bypass(4), hwControlFNB1(5), hwControlFNB2(6), hwControl(7)} | read-write | mandatory |
| ctFDDISerialOperStatus OBJECT-TYPE 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. | 1.3.6.1.4.1.52.4.1.2.5.1.4.2.1.3 | INTEGER {insertFNB1(1), insertFNB2(2), insertFNB1FNB2(3), bypass(4)} | read-only | mandatory |
| ctFDDIModuleFPIMTable OBJECT-TYPE This table describes the FPIMs that are on the front panel of each FDDI serial control module, if that module supports FPIMs. | 1.3.6.1.4.1.52.4.1.2.5.1.4.3 | not-accessible | mandatory | |
| ctFDDIModuleFPIMEntry OBJECT-TYPE Describes a single FDDI FPIM on a module. | 1.3.6.1.4.1.52.4.1.2.5.1.4.3.1 | not-accessible | mandatory | |
| ctFddiFPIMSlotID OBJECT-TYPE Defines the slot in which this module exists. This is an instance of chSlotID as found in the chassis MIB. | 1.3.6.1.4.1.52.4.1.2.5.1.4.3.1.1 | INTEGER | read-only | mandatory |
| ctFddiFPIM OBJECT-TYPE 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. | 1.3.6.1.4.1.52.4.1.2.5.1.4.3.1.2 | INTEGER | read-only | mandatory |
| ctFddiFPIMStatus OBJECT-TYPE 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. | 1.3.6.1.4.1.52.4.1.2.5.1.4.3.1.4 | INTEGER {link(1), noLink(2), notSupported(3)} | read-only | mandatory |
| ctFddiFPIMType OBJECT-TYPE Describes the type of FPIM as found in ctron-oids. | 1.3.6.1.4.1.52.4.1.2.5.1.4.3.1.5 | OBJECT IDENTIFIER | read-only | mandatory |