AD | Application | AWS | Azure | Cloud | Database | Enterprise | Environmental | Event Log | File System | IoT | IT Service | Network/System | Infra | Performance | Protocol | SaaS | Security | Service Level | Storage | Linux | VMware | VoIP | Web | Wireless | SNMP

Crumbtrail

MonitorTools.com » Technical documentation » SNMP » MIB » Wellfleet » Wellfleet-SIP-MIB » Objects

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

Wellfleet-SIP-MIB file content

Object view of Wellfleet-SIP-MIB:

Scalar Object
wfSipL2Entry .1.3.6.1.4.1.18.3.4.14.1.1
per circuit SIP Level 2 objects - wfSipL2Index corresponds to Wellfleet circuit number
wfSipDs1PlcpEntry .1.3.6.1.4.1.18.3.4.14.2.1.1
per circuit DS1 PLCP objects - wfSipDs1PlcpIndex corresponds to Wellfleet circuit number
wfSipDs3PlcpEntry .1.3.6.1.4.1.18.3.4.14.2.2.1
per circuit DS3 PLCP objects - wfSipDs3PlcpIndex corresponds to Wellfleet circuit number
Tabular Object
wfSipL2Index .1.3.6.1.4.1.18.3.4.14.1.1.1
this corresponds to the Wellfleet circuit number
wfSipL2ReceivedCounts .1.3.6.1.4.1.18.3.4.14.1.1.2
total of unerrored received SIP L2 PDUs
wfSipL2SentCounts .1.3.6.1.4.1.18.3.4.14.1.1.3
total of unerrored SIP L2 PDU's sent across the SNI
wfSipHcsOrCRCErrors .1.3.6.1.4.1.18.3.4.14.1.1.4
total SIP L2 PDUs with HCS or CRC errors
wfSipL2PayloadLengthErrors .1.3.6.1.4.1.18.3.4.14.1.1.5
total SIP L2 PDUs with length errors
wfSipL2SequenceNumberErrors .1.3.6.1.4.1.18.3.4.14.1.1.6
total SIP L2 PDUs with unexpected sequence numbers
wfSipL2MidCurrentlyActiveErrors .1.3.6.1.4.1.18.3.4.14.1.1.7
number of SIP L2 PDUs with BOMs previously started
wfSipL2BomOrSSMsMIDErrors .1.3.6.1.4.1.18.3.4.14.1.1.8
number of SIP L2 PDUs with zero BOMs or SSMs not zero
wfSipL2EomsMIDErrors .1.3.6.1.4.1.18.3.4.14.1.1.9
number of SIP L2 PDUs with zero EOMs or EOMs without BOMs
wfSipDs1PlcpIndex .1.3.6.1.4.1.18.3.4.14.2.1.1.1
this corresponds to the Wellfleet circuit number
wfSipDs1PlcpSEFs .1.3.6.1.4.1.18.3.4.14.2.1.1.2
number of second intervals containing one or more severely errored seconds
wfSipDs1PlcpAlarmState .1.3.6.1.4.1.18.3.4.14.2.1.1.3
alarm state
wfSipDs1PlcpUASs .1.3.6.1.4.1.18.3.4.14.2.1.1.4
number of second intervals containing one or more unavailable seconds
wfSipDs3PlcpIndex .1.3.6.1.4.1.18.3.4.14.2.2.1.1
this corresponds to the Wellfleet circuit number
wfSipDs3PlcpSEFs .1.3.6.1.4.1.18.3.4.14.2.2.1.2
number of second intervals containing one or more severely errored seconds
wfSipDs3PlcpAlarmState .1.3.6.1.4.1.18.3.4.14.2.2.1.3
alarm state
wfSipDs3PlcpUASs .1.3.6.1.4.1.18.3.4.14.2.2.1.4
number of second intervals containing one or more unavailable seconds
Table
wfSipL2 .1.3.6.1.4.1.18.3.4.14.1
The SIP L2 Table
wfSipDs1Plcp .1.3.6.1.4.1.18.3.4.14.2.1
The SIP DS1 PLCP Table
wfSipDs3Plcp .1.3.6.1.4.1.18.3.4.14.2.2
The SIP DS3 PLCP Table
Object Identifier
wfSipPlcpGroup .1.3.6.1.4.1.18.3.4.14.2