ActiveXperts Network Monitor 2019##AdminFavorites

CTRON-SMARTTRUNK-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 2019 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 2019 can import MIB file CTRON-SMARTTRUNK-MIB and use it to monitor vendor specific OID's.

CTRON-SMARTTRUNK-MIB file content

Object view of CTRON-SMARTTRUNK-MIB:

Scalar Object
ctTrunkGlobalStatus .1.3.6.1.4.1.52.4.1.2.20.1.1.1
The state of Smart TRUNK capability for this entire managed entity. Default Value is True(1). If set to False(2) all smart trunks are put into ifAdminStatus down.
ctTrunkConfigEntry .1.3.6.1.4.1.52.4.1.2.20.1.1.3.1
Each table entry contains configuration information for one trunk interface.
ctTrunkConnectionEntry .1.3.6.1.4.1.52.4.1.2.20.1.1.4.1
Each table entry contains configuration information for one interface that is participating in a trunk.
ctTrunkLLAPRequirement .1.3.6.1.4.1.52.4.1.2.20.1.2.1
Indicates whether this managed entity requires the LLAP updates to perform the trunking function. Certain families of products require LLAP (decHuntGroup Protocol) order for the Smart TRUNK functionality to work. A value of 1 implies that LLAP is necessary for smart-trunking to work on this platform, a value of 2 indicates that it is not necessary.
ctTrunkMaxTrunks .1.3.6.1.4.1.52.4.1.2.20.1.2.2
The maximum number of trunks that can be configured on this managed entity.
ctTrunkFlowDiagnosticEntry .1.3.6.1.4.1.52.4.1.2.20.1.2.4.1
Each row refers to a specific smart trunk and port within that smart trunk.
Tabular Object
ctTrunkIndex .1.3.6.1.4.1.52.4.1.2.20.1.1.3.1.1
A value which uniquely identifies this conceptual row in the ctTrunkConfigTable. The Table allows sparse values. If the conceptual row identified by this value of ctTrunkIndex is recreated following an agent restart, the same value of ctTrunkIndex must be used to identify the recreated row. (However, the Interfaces table index associated with the client may change. ifAlias in ifXTable is used then to reassociate ifIndexes based on ifAlias. In the case of the SSR, Smart Trunks are manipulated as st.ctTrunkIndex
ctTrunkConfigName .1.3.6.1.4.1.52.4.1.2.20.1.1.3.1.2
The Trunk's Name, just for informational purposes. It may be changed regardless of the RowStatus value.
ctTrunkConfigProtocol .1.3.6.1.4.1.52.4.1.2.20.1.1.3.1.3
Trunking protocol in use. Once the row is active, it can not be changed.
ctTrunkConfigLoadBalance .1.3.6.1.4.1.52.4.1.2.20.1.1.3.1.4
The type of load balance algorithm applied to this trunk. Once Row is active, the agent may override this value with an implmentation specific default.
ctTrunkIfIndex .1.3.6.1.4.1.52.4.1.2.20.1.1.3.1.5
The ifIndex in ifTable, ifXTable that is associated with the trunk that is represented by this row.
ctTrunkRowStatus .1.3.6.1.4.1.52.4.1.2.20.1.1.3.1.6
This object lets network managers create and delete trunk interfaces, on systems that support this optional capability. It does not control the activation and deactivation of these interfaces; they are controlled by 'ifAdminStatus' in the ifTable. However, changing row state from active to notInService. will have the side effect of changing their 'ifAdminStatus' values to 'noPresent' or 'down', thus causing any active trunk connections to be terminated. When creating a trunk interface, it is up to the management station to determine a suitable 'ctTrunkIndex'. To facilitate interoperability, agents should not put any restrictions on the 'ctTrunkIndex' beyond the obvious ones that it be valid and unused. The Managed Objects that must be set in this table for a row to change from nonExistent/notReady to notInService/Active is simply an index. Ports can then be added to the Smart TRUNK via the ifStackTable. If you create a trunk interface via this object, it will initially have 'ifAdminStatus' = 'down' 'ifOperStatus' = 'down' when RowStatus is changed to active.
ctTrunkPortRemoteIfIndex .1.3.6.1.4.1.52.4.1.2.20.1.1.4.1.1
The ifIndex of the interface at the other end of this part of the trunk link. If this value is 0, then for some reason there is no interface on the other side of this link. This might be a temporary condition or it might represent a real problem. Note: this table is indexed by ifIndex. So the index is the local ifIndex value and ctTrunkPortRemoteIfIndex is the remote ifIndex.
ctTrunkFlowDiagnosticInstalledFlows .1.3.6.1.4.1.52.4.1.2.20.1.2.4.1.1
A counter of the flows installed on this port since it was first operational.
Table
ctTrunkConfigTable .1.3.6.1.4.1.52.4.1.2.20.1.1.3
A table describing all of the trunk interfaces implemented by this host. Each trunk has a row in the MIB-II/RFC 2233 Interfaces table (describing the structure of the trunk interface it presents to higher layers). Each trunk interface also has a row in this and other CTRON-SMARTTRUNK-MIB tables. Smart Trunks use ifType propMultiplexor(54). Counters represent the aggregate of all physcal links. Unlike hardware ports, trunk interfaces can be created by management. However, the RFC 2233 Interfaces table does not directly support row creation. Therefore, creating or deleting a row in the ctTrunkConfigTable is defined to have the side effect of creating or deleting corresponding rows in - the MIB-II / RFC 2233 Interfaces table, - any other dependent tables New Interfaces table rows for trunk intefaces always have 'ifAdminStatus' set to 'down' until the row state is becomes Active. Then administration of the interface uses normal ifTable ifAdminStatus to enabled it.
ctTrunkConnectionTable .1.3.6.1.4.1.52.4.1.2.20.1.1.4
This table describes how local interfaces that are participating in a trunk are connected to remote interfaces. With this table, a management entity can determine that (for example) local interfaces 3, 4, and 6 are connected to remote interfaces 10, 17, and 19. This table is useful to debug configuration errors with remote devices. If ifAdminStatus/ifOperState is up, and no corresponding row is found in this table, then a management station can assume a the remote end does not have the decHuntGroup protocol active. Note: this entire table is read-only. Rows are created and deleted from this table as a side effect of trunks being created and deleted. Note: a managment entity could determine (for example) that interface 3 was participating in trunk 3 by using the ifStackTable and ctTrunkIfIndex.
ctTrunkFlowDiagnosticTable .1.3.6.1.4.1.52.4.1.2.20.1.2.4
Provide a means to programmatically evaluate the load balancing of a smart trunk. Assumes that load balancing is done on a flow by flow basis.
Object Identifier
ctSmartTrunk .1.3.6.1.4.1.52.4.1.2.20.1
This mib module defines a portion of the SNMP enterprise MIBs under Cabletron enterprise OID pertaining to configuration of Smart TRUNK network links.
ctSmartTrunkConfig .1.3.6.1.4.1.52.4.1.2.20.1.1
ctSmartTrunkDebug .1.3.6.1.4.1.52.4.1.2.20.1.2
ctTrunkConformance .1.3.6.1.4.1.52.4.1.2.20.1.3
ctTrunkCompliances .1.3.6.1.4.1.52.4.1.2.20.1.3.1
ctTrunkGroups .1.3.6.1.4.1.52.4.1.2.20.1.3.2
Group
ctTrunkConfGroupV10 .1.3.6.1.4.1.52.4.1.2.20.1.3.2.1
A set of managed objects that make up version 1.0 of the CTRON-SMARTTRUNK-MIB.
ctTrunkFlowDiagnosticGroup .1.3.6.1.4.1.52.4.1.2.20.1.3.2.2
A collection of diagnostic information related to interfaces participating in SmartTrunks; specifically to interfaces on devices that use 'flows'.