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 » Wellfleet » Wellfleet-MODULE-MIB » Objects

Wellfleet-MODULE-MIB.mib object view, vendor Wellfleet

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

Wellfleet-MODULE-MIB file content

Object view of Wellfleet-MODULE-MIB:

Scalar Object
wfHwModuleEntry .1.3.6.1.4.1.18.3.1.4.1.1
Hardware specific information about a slot.
wfModuleEntry .1.3.6.1.4.1.18.3.1.4.2.1
Hardware specific information about a slot.
Tabular Object
wfHwModuleSlot .1.3.6.1.4.1.18.3.1.4.1.1.1
A unique value for each slot. Its value ranges between 1 and 4.
wfHwModuleModule .1.3.6.1.4.1.18.3.1.4.1.1.2
This value ranges between 1 and 4
wfHwModuleModIdOpt .1.3.6.1.4.1.18.3.1.4.1.1.3
Module IDs for the net modules modules
wfHwModuleModRev .1.3.6.1.4.1.18.3.1.4.1.1.4
The revision level of the module. High byte is in upper 2 bytes.
wfHwModuleModSerialNumber .1.3.6.1.4.1.18.3.1.4.1.1.5
The serial number of the module.
wfHwModuleArtworkRev .1.3.6.1.4.1.18.3.1.4.1.1.6
The Artwork Revision number of the module
wfHwModuleMemorySize1 .1.3.6.1.4.1.18.3.1.4.1.1.7
Size (in bytes) of memory #1.
wfHwModuleMemorySize2 .1.3.6.1.4.1.18.3.1.4.1.1.8
Size (in bytes) of memory #2.
wfHwModuleDaughterBdIdOpt .1.3.6.1.4.1.18.3.1.4.1.1.9
Daughterboard IDs that may be attached to net modules
wfHwModuleLEDStatus1 .1.3.6.1.4.1.18.3.1.4.1.1.10
Bit mask representing the status of the LEDs on the module. Each LED is represented by 2 bits. LED #1 status is indicated by the 2 least significant bits. LED #16 status is indicated by the 2 most significant bits. How this bit mask is interpreted depends on the module ID. For example, some modules use this value to report what color the LED is currently set to ('00' off, '01' yellow, '10' green). This value can be used by a NMS that needs to know this information for whatever reason. Some modules may not support this value in which case it should be set to zero.
wfHwModuleLEDState1 .1.3.6.1.4.1.18.3.1.4.1.1.11
Bit mask representing the state of the LEDs on the module. Each LED is represented by 2 bits. LED #1 state is indicated by the 2 least significant bits. LED #16 state is indicated by the 2 most significant bits. How this bit mask is interpreted depends on the module ID. For example, some modules use this value to indicate a LED is flashing (value of '01') or a solid color (value of '00'). This value can be used by a NMS that needs to know this information for whatever reason. Some modules may not support this value in which case it should be set to zero.
wfHwModuleLEDStatus2 .1.3.6.1.4.1.18.3.1.4.1.1.12
Bit mask representing the status of the LEDs on the module. Each LED is represented by 2 bits. LED #17 status is indicated by the 2 least significant bits. LED #32 status is indicated by the 2 most significant bits. How this bit mask is interpreted depends on the module ID. For example, some modules use this value to report what color the LED is currently set to ('00' off, '01' yellow, '10' green). This value can be used by a NMS that needs to know this information for whatever reason. Some modules may not support this value in which case it should be set to zero.
wfHwModuleLEDState2 .1.3.6.1.4.1.18.3.1.4.1.1.13
Bit mask representing the state of the LEDs on the module. Each LED is represented by 2 bits. LED #17 state is indicated by the 2 least significant bits. LED #32 state is indicated by the 2 most significant bits. How this bit mask is interpreted depends on the module ID. For example, some modules use this value to indicate a LED is flashing (value of '01') or a solid color (value of '00'). This value can be used by a NMS that needs to know this information for whatever reason. Some modules may not support this value in which case it should be set to zero.
wfHwModuleLEDStatus3 .1.3.6.1.4.1.18.3.1.4.1.1.14
Bit mask representing the status of the LEDs on the module. Each LED is represented by 2 bits. LED #33 status is indicated by the 2 least significant bits. LED #48 status is indicated by the 2 most significant bits. How this bit mask is interpreted depends on the module ID. For example, some modules use this value to report what color the LED is currently set to ('00' off, '01' yellow, '10' green). This value can be used by a NMS that needs to know this information for whatever reason. Some modules may not support this value in which case it should be set to zero.
wfHwModuleLEDState3 .1.3.6.1.4.1.18.3.1.4.1.1.15
Bit mask representing the state of the LEDs on the module. Each LED is represented by 2 bits. LED #33 state is indicated by the 2 least significant bits. LED #48 state is indicated by the 2 most significant bits. How this bit mask is interpreted depends on the module ID. For example, some modules use this value to indicate a LED is flashing (value of '01') or a solid color (value of '00'). This value can be used by a NMS that needs to know this information for whatever reason. Some modules may not support this value in which case it should be set to zero.
wfModuleSlot .1.3.6.1.4.1.18.3.1.4.2.1.2
A unique value for each slot. Its value ranges between 1 and 14. There are products in this family that contain 1, 5, and 14 slots.
wfModuleDelete .1.3.6.1.4.1.18.3.1.4.2.1.1
create/delete parameter
wfModuleTimerFrequency .1.3.6.1.4.1.18.3.1.4.2.1.3
This value determines the frequency for the buffer balance algorithm to run
wfModuleBufferBalance .1.3.6.1.4.1.18.3.1.4.2.1.4
Enable/Disable buffer balancing algorithm selectively
wfModuleFddiWeight .1.3.6.1.4.1.18.3.1.4.2.1.5
This value determines the weight of the fddi line for the buffer balancing algorithm
wfModuleTokenRingWeight .1.3.6.1.4.1.18.3.1.4.2.1.6
This value determines the weight of the token-ring for the buffer balancing algorithm
wfModuleCsmacdWeight .1.3.6.1.4.1.18.3.1.4.2.1.7
This value determines the weight of the csmacd line for the buffer balancing algorithm
wfModuleSyncWeight .1.3.6.1.4.1.18.3.1.4.2.1.8
This value determines the weight of the sync line for the buffer balancing algorithm
wfModuleFreeBufferCredits .1.3.6.1.4.1.18.3.1.4.2.1.9
This attribute indicates the number of buffers available to line drivers but not used by them
wfModuleTotalBufferCredits .1.3.6.1.4.1.18.3.1.4.2.1.10
This attribute indicates the total number of buffers available to line drivers
wfModuleRestart .1.3.6.1.4.1.18.3.1.4.2.1.11
This attribute should be touched after the queue lengths are configured in the line-records
wfModuleCsmacd100Weight .1.3.6.1.4.1.18.3.1.4.2.1.12
This value determines the weight of the csmacd 100MB line for the buffer balancing algorithm
wfModuleBisyncWeight .1.3.6.1.4.1.18.3.1.4.2.1.13
This value determines the weight of the bisync line for the buffer balancing algorithm
wfModuleHssiWeight .1.3.6.1.4.1.18.3.1.4.2.1.14
This value determines the weight of the hssi line for the buffer balancing algorithm
Table
wfHwModuleTable .1.3.6.1.4.1.18.3.1.4.1
Hardware Module Table Filled in by the Module Driver. Read by SNMP to build the driver load records
wfModuleTable .1.3.6.1.4.1.18.3.1.4.2
This table is used by the module driver for Barracuda