ActiveXperts Network Monitor 2019##AdminFavorites

CTRON-SFPS-BINDERY-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-SFPS-BINDERY-MIB and use it to monitor vendor specific OID's.

CTRON-SFPS-BINDERY-MIB file content

Object view of CTRON-SFPS-BINDERY-MIB:

Scalar Object
sfpsAgentBinderyConfigEntry .1.3.6.1.4.1.52.4.2.4.2.2.7.1.1
Each entry specifies the configuration for the bindery component.
sfpsAgentBinderyAPIVerb .1.3.6.1.4.1.52.4.2.4.2.2.7.2.1
The BinderyAPI is a flat MIB that can be used to enable/disable Bindery components, and to save the enable/disable info into Nvram. The next reboot/reset, each SFPSElement will check the NvramStatus and not start if disabled.
sfpsAgentBinderyAPIElementName .1.3.6.1.4.1.52.4.2.4.2.2.7.2.2
Enter in the dotted notation Bindery ID (xxx.yyy.zzz) of the SFPSElement you wish to perform the action.
sfpsAgentBinderyAPINVStatus .1.3.6.1.4.1.52.4.2.4.2.2.7.2.3
Displays the Current Admin Status of this Element in Nvram.
sfpsAgentBinderyAPIAdminStatus .1.3.6.1.4.1.52.4.2.4.2.2.7.2.4
Displays the Current AdminStatus of the SFPSElement.
sfpsAgentBinderyAPIOperStatus .1.3.6.1.4.1.52.4.2.4.2.2.7.2.5
Displays the Current OperStatus of the SFPSElement.
sfpsAgentBinderyAPINvSet .1.3.6.1.4.1.52.4.2.4.2.2.7.2.6
Total number of SFPSElements stored in NVRAM for persistence.
sfpsAgentBinderyAPINvTotal .1.3.6.1.4.1.52.4.2.4.2.2.7.2.7
Total number of SFPSElements allocated in NVRAM. The switch will always allocate enough space in NVRAM for the number of elements. That is, NvTotal will always be greater than or equal to NvSet.
sfpsAgentBinderyAPIDefaultStatus .1.3.6.1.4.1.52.4.2.4.2.2.7.2.8
Tabular Object
sfpsAgentBinderyConfigHashLeaf .1.3.6.1.4.1.52.4.2.4.2.2.7.1.1.1
NO hash, part of instance key.
sfpsAgentBinderyConfigHashIndex .1.3.6.1.4.1.52.4.2.4.2.2.7.1.1.2
NO Bucket index, part of instance key.
sfpsAgentBinderyConfigName .1.3.6.1.4.1.52.4.2.4.2.2.7.1.1.3
Elements Name.
sfpsAgentBinderyConfigType .1.3.6.1.4.1.52.4.2.4.2.2.7.1.1.4
Type of element.
sfpsAgentBinderyConfigOperStatus .1.3.6.1.4.1.52.4.2.4.2.2.7.1.1.5
Operational state of the entry.
sfpsAgentBinderyConfigAdminStatus .1.3.6.1.4.1.52.4.2.4.2.2.7.1.1.6
Administrative state of the entry.
sfpsAgentBinderyConfigStatusTime .1.3.6.1.4.1.52.4.2.4.2.2.7.1.1.7
Time tick of last OperStatus change.
sfpsAgentBinderyConfigNVStatus .1.3.6.1.4.1.52.4.2.4.2.2.7.1.1.8
Administrative state of the entry.
Table
sfpsAgentBinderyConfigTable .1.3.6.1.4.1.52.4.2.4.2.2.7.1
Soft Binding is implemented through a few new base classes, a small army of instances of the base classes plus a bindery table to tie the whole mess together.
Object Identifier
sfpsAgentBinderyAPI .1.3.6.1.4.1.52.4.2.4.2.2.7.2