CTRON-FDDI-FNB-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for CTRON-FDDI-FNB-MIB.
70
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
70 total| Object Name |
|---|
ctFDDIResource OBJECT IDENTIFIER .1.3.6.1.4.1.52.4.1.2.5.1.1 |
RFC1213-MIB Unknown .1.3.6.1.4.1.52.4.1.2.5.1.1 |
ctFDDIResourceTableThis table specifies the physical resources
associated with the FNB and general FNB operation for a
particular module in a particular slot. SEQUENCE OF CtFDDIResourceEntry .1.3.6.1.4.1.52.4.1.2.5.1.1.1 |
ctFDDIResourceEntryDefines a specific physical resource entry CtFDDIResourceEntry .1.3.6.1.4.1.52.4.1.2.5.1.1.1.1 |
ctFDDIResourceSlotIDA specific instance of a slot as defined by chSlotID
as defined in the chassis MIB.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.1.1.1.1 |
ctFDDIResourceIDA 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.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.1.1.1.2 |
ctFDDIResourceTypeDefines the type of resource. This is the same value as
chResourceType in the chassis MIB.ro OBJECT IDENTIFIER .1.3.6.1.4.1.52.4.1.2.5.1.1.1.1.3 |
ctFDDIResourceNumbInstanceThis 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).ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.1.1.1.4 |
ctFDDINonMux OBJECT IDENTIFIER .1.3.6.1.4.1.52.4.1.2.5.1.2 |
ctFDDINonMuxCapTableThis table describes all possible capabilities/configurations
for all non-muxed FDDI configurations within the chassis. SEQUENCE OF CtFDDINonMuxCapEntry .1.3.6.1.4.1.52.4.1.2.5.1.2.1 |
ctFDDINonMuxCapEntryDescribes a particular capability/configuration entry. CtFDDINonMuxCapEntry .1.3.6.1.4.1.52.4.1.2.5.1.2.1.1 |
ctFDDINMSlotThe slot within the chassis for which this
configuration information is defined.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.2.1.1.1 |
ctFDDINMConfigIDThe instance of a particular configuration.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.2.1.1.2 |
ctFDDINMConfigThis 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'ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.52.4.1.2.5.1.2.1.1.3 |
ctFDDINMConfigDescThis object contains a textual description of a valid
connection configuration. This is a more user-friendly
representation of the configuration than the ctFDDINMConfig
object.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.52.4.1.2.5.1.2.1.1.4 |
ctFDDINonMuxCapEnableTableThis table describes the currently enabled configuration
for each module. SEQUENCE OF CtFDDINonMuxCapEnableEntry .1.3.6.1.4.1.52.4.1.2.5.1.2.2 |
ctFDDINonMuxCapEnableEntryDescribes a specific configuration enable entry. CtFDDINonMuxCapEnableEntry .1.3.6.1.4.1.52.4.1.2.5.1.2.2.1 |
ctFDDINMEnableSlotA specific slot for which this configuration enable
pertains.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.2.2.1.1 |
ctFDDINMCapEnableA 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.rw INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.2.2.1.2 |
ctFDDINonMuxConnectionTableThis 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. SEQUENCE OF CtFDDINonMuxConnectionEntry .1.3.6.1.4.1.52.4.1.2.5.1.2.3 |
ctFDDINonMuxConnectionEntryDefines a specific configuration connection entry. CtFDDINonMuxConnectionEntry .1.3.6.1.4.1.52.4.1.2.5.1.2.3.1 |
ctFDDINMConnectionSlotA specific slot for which this connection entry is
defined.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.2.3.1.1 |
ctFDDINMConnectionIDDescribes a specific connection identifier. Valid
connection identifiers are defined by the third
sub-identifier in ctFDDINMConfig as identified by
ctFDDINMCapEnable.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.2.3.1.2 |
ctFDDINMSMTA specific instance of SMT for which this entry pertains.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.2.3.1.3 |
ctFDDINMMACA specific MAC that this connection entry pertains.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.2.3.1.4 |
ctFDDINMBytesThe bandwidth utilization in bytes per second.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.2.3.1.5 |
ctFDDINMFramesThe bandwidth utilization in frames per second.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.2.3.1.6 |
ctFDDINonMuxInterfaceTableThis table describs the number of interfaces defined by
each non multiplexing FDDI FNB module. SEQUENCE OF CtFDDINonMuxInterfaceEntry .1.3.6.1.4.1.52.4.1.2.5.1.2.4 |
ctFDDINonMuxInterfaceEntryA specfic non multiplexing module interface definition. CtFDDINonMuxInterfaceEntry .1.3.6.1.4.1.52.4.1.2.5.1.2.4.1 |
ctFDDINMInterSlotA specific slot for which this inteface entry is
defined.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.2.4.1.1 |
ctFDDINMNumbInterfacesThe number of interfaces defined on this particular
module.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.2.4.1.2 |
ctFDDIMux OBJECT IDENTIFIER .1.3.6.1.4.1.52.4.1.2.5.1.3 |
ctFDDIMuxCapTableThis table describes all possible configuration/capabilities
defined for a FDDI multiplexing module. SEQUENCE OF CtFDDIMuxCapEntry .1.3.6.1.4.1.52.4.1.2.5.1.3.1 |
ctFDDIMuxCapEntryDescribes a specfic FDDI multiplexor capability/configuration
entry. CtFDDIMuxCapEntry .1.3.6.1.4.1.52.4.1.2.5.1.3.1.1 |
ctFDDIMuxSlotDefines the slot within the chassis for which this
multiplexed capability/configuration entry pertains.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.3.1.1.1 |
ctFDDIMuxConfigIDThe instance of a particular configuration.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.3.1.1.2 |
ctFDDIMuxConfigThis 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'ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.52.4.1.2.5.1.3.1.1.3 |
ctFDDIMuxConfigDescThis object contains a textual description of a valid
connection configuration. This is a more user-friendly
representation of the configuration than the ctFDDIMuxConfig
object.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.52.4.1.2.5.1.3.1.1.4 |
ctFDDIMuxCapEnableTableThis table describes the currently enabled configuration
for each module. SEQUENCE OF CtFDDIMuxCapEnableEntry .1.3.6.1.4.1.52.4.1.2.5.1.3.2 |
ctFDDIMuxCapEnableEntryDescribes a specific configuration enable entry. CtFDDIMuxCapEnableEntry .1.3.6.1.4.1.52.4.1.2.5.1.3.2.1 |
ctFDDIMuxEnableSlotA specific slot for which this configuration enable
pertains.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.3.2.1.1 |
ctFDDIMuxCapEnableA 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.rw INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.3.2.1.2 |
ctFDDIMuxMasterPortAssignmentChangeDepicts the number of changes to the master port to multiplexor
output mapping.ro Counter .1.3.6.1.4.1.52.4.1.2.5.1.3.2.1.3 |
ctFDDIMuxOutTableDescribes 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. SEQUENCE OF CtFDDIMuxOutEntry .1.3.6.1.4.1.52.4.1.2.5.1.3.3 |
ctFDDIMuxOutEntryDescribes a particular multiplexor output. CtFDDIMuxOutEntry .1.3.6.1.4.1.52.4.1.2.5.1.3.3.1 |
ctFDDIMuxOutSlotThe given slot for which this multiplexor output information
pertains.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.3.3.1.1 |
ctFDDIMuxOutIDThe specific instance of the multiplexor output. Instances
of this object are used by the values of ctFDDIMuxConfig.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.3.3.1.2 |
ctFDDIMuxOutMACIndexThe 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.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.3.3.1.3 |
ctFDDIMuxOutSMTIndexIdentifies the instance of SMT as defined within the
FDDI MIB.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.3.3.1.4 |
ctFDDIMuxBytesThe bandwidth utilization in bytes per second.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.3.3.1.5 |
ctFDDIMuxFramesThe bandwidth utilization in frames per second.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.3.3.1.6 |
ctFDDIMuxMasterPortTableA list of entries that define master ports as they are
defined for the given multiplexed FDDI connection. SEQUENCE OF CtFDDIMuxMasterPortEntry .1.3.6.1.4.1.52.4.1.2.5.1.3.4 |
ctFDDIMuxMasterPortEntryA specific FDDI-FNB multiplexed master port definition. CtFDDIMuxMasterPortEntry .1.3.6.1.4.1.52.4.1.2.5.1.3.4.1 |
ctFDDIMuxMasterPortSlotIDA specific instance of a slot as defined by chSlotID.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.3.4.1.1 |
ctFDDIMuxMasterPortIDA unique identifier for this specific master port.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.3.4.1.2 |
ctFDDIMuxMasterPortAssignmentProvides the masterport to multiplexor output mapping.
This is as defined by ctFDDIMuxOutMacAssignment.rw INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.3.4.1.3 |
ctFDDIMuxMasterPortIndexDefines a specific port within the FDDI MIBs fddimibPORTTable.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.3.4.1.4 |
ctFDDISerialConfig OBJECT IDENTIFIER .1.3.6.1.4.1.52.4.1.2.5.1.4 |
ctFDDINumbModulesDescribes 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.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.4.1 |
ctFDDISerialConfigTableThis table describes the adminstrative control over each
of the FNB serial control modules. SEQUENCE OF CtFDDISerialConfigEntry .1.3.6.1.4.1.52.4.1.2.5.1.4.2 |
ctFDDISerialConfigEntryDescribes the controls over a single FNB serial control
entry. CtFDDISerialConfigEntry .1.3.6.1.4.1.52.4.1.2.5.1.4.2.1 |
ctFDDISerialSlotIDDefines the slot that this FNB serial control module is in.
This is an instance of chSlotID as defined in the chassis MIB.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.4.2.1.1 |
ctFDDISerialAdminStatusDescribes 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.rw Enumeration .1.3.6.1.4.1.52.4.1.2.5.1.4.2.1.2 |
ctFDDISerialOperStatusDescribes 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.ro Enumeration .1.3.6.1.4.1.52.4.1.2.5.1.4.2.1.3 |
ctFDDIModuleFPIMTableThis table describes the FPIMs that are on the front panel of
each FDDI serial control module, if that module supports FPIMs. SEQUENCE OF CtFDDIModuleFPIMEntry .1.3.6.1.4.1.52.4.1.2.5.1.4.3 |
ctFDDIModuleFPIMEntryDescribes a single FDDI FPIM on a module. CtFDDIModuleFPIMEntry .1.3.6.1.4.1.52.4.1.2.5.1.4.3.1 |
ctFddiFPIMSlotIDDefines the slot in which this module exists. This
is an instance of chSlotID as found in the chassis MIB.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.4.3.1.1 |
ctFddiFPIMDefines 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.ro INTEGER .1.3.6.1.4.1.52.4.1.2.5.1.4.3.1.2 |
ctFddiFPIMStatusDescribes 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.ro Enumeration .1.3.6.1.4.1.52.4.1.2.5.1.4.3.1.4 |
ctFddiFPIMTypeDescribes the type of FPIM as found in ctron-oids.ro OBJECT IDENTIFIER .1.3.6.1.4.1.52.4.1.2.5.1.4.3.1.5 |