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-BOT-MIB » Objects

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

Wellfleet-BOT-MIB file content

Object view of Wellfleet-BOT-MIB:

Scalar Object
wfBotDelete .1.3.6.1.4.1.18.3.5.18.1.1
Create/Delete parameter. Default is created. User perform an SNMP SET operation on this object in order to create/delete BOT
wfBotDisable .1.3.6.1.4.1.18.3.5.18.1.2
Enable/Disable parameter. Default is enabled. User perform an SNMP SET operation on this object in order to enable/disable BOT
wfBotState .1.3.6.1.4.1.18.3.5.18.1.3
The current state of BOT
wfBotInterfaceEntry .1.3.6.1.4.1.18.3.5.18.2.1
An entry in wfBotInterfaceTable
wfBotPeerEntry .1.3.6.1.4.1.18.3.5.18.3.1
An entry in wfBotPeerTable
wfBotCUEntry .1.3.6.1.4.1.18.3.5.18.4.1
An entry in wfBotCUTable
Tabular Object
wfBotInterfaceSlotNumber .1.3.6.1.4.1.18.3.5.18.2.1.4
Slot number on which this interface is running
wfBotInterfaceCctNumber .1.3.6.1.4.1.18.3.5.18.2.1.3
The circuit from which the connection attempt is received that initiates a translation session.
wfBotInterfaceDelete .1.3.6.1.4.1.18.3.5.18.2.1.1
Create/Delete attribute. Default is Created Users perform SNMP SET operation on this object in order to create/delete a translation interface record
wfBotInterfaceDisable .1.3.6.1.4.1.18.3.5.18.2.1.2
Enables/Disables this mapping entry Setting of this attribute to DISABLED will disconnect all active sessions pertaining to this interface entry
wfBotInterfaceState .1.3.6.1.4.1.18.3.5.18.2.1.5
The current state of the Interface
wfBotInterfaceType .1.3.6.1.4.1.18.3.5.18.2.1.6
If this interface is point-to-point, i.e. no splitting occours we can straight away deliver BSC frame to designated TCP circuit, without looking into the CU address
wfBotInterfaceAttachedTo .1.3.6.1.4.1.18.3.5.18.2.1.7
Information that this interface is attached to the Primary or secondary BSC station
wfBotInterfacePktCnt .1.3.6.1.4.1.18.3.5.18.2.1.8
Interface packet count ...
wfBotKeepaliveInterval .1.3.6.1.4.1.18.3.5.18.2.1.9
Idle session timeout period, in seconds. If an established TCP connection remains inactive for this interval, KEEPALIVE messages will be sent to the peer (if the Keepalive Timer is non-zero). Setting the Idle Timer to zero disables the keepalive feature.
wfBotKeepaliveRto .1.3.6.1.4.1.18.3.5.18.2.1.10
KEEPALIVE retransmit timeout period, in seconds. This is the interval at which unacknowledged KEEPALIVE messages will be retransmitted. If the Idle Timer is set to zero, this timer ignored. If the Idle Timer is non-zero and this timer IS zero, no KEEPALIVEs are sent and the session is terminated upon expiration of the Idle Timer.
wfBotKeepaliveMaxRetry .1.3.6.1.4.1.18.3.5.18.2.1.11
Number of unacknowledged KEEPALIVE messages retransmitted before the TCP session is terminated. If this count is set to zero, only one KEEPALIVE message will be sent.
wfBotPeerSlotNumber .1.3.6.1.4.1.18.3.5.18.3.1.3
Slot number on which this peer entry is configured
wfBotPeerCctNumber .1.3.6.1.4.1.18.3.5.18.3.1.4
The circuit from which the connection attempt is received that initiates a translation session.
wfBotPeerRemoteIpAddr .1.3.6.1.4.1.18.3.5.18.3.1.5
IP Address of the remote host with which this translation session is established.
wfBotPeerLocalTcpListenPort .1.3.6.1.4.1.18.3.5.18.3.1.7
Based on the field wfBotConnOriginator, SiteManager will allow user to configure only one of following two fields: if Originator = SELF then through SiteManager ask user to enter PeerTcpListenPort# else through SiteManager ask user to enter LocalTcpListenPort# So, in any case one of the two fields will have NULL_VALUE.
wfBotPeerRemoteTcpListenPort .1.3.6.1.4.1.18.3.5.18.3.1.8
Peer listen port for TCP connection
wfBotConnOriginator .1.3.6.1.4.1.18.3.5.18.3.1.6
Upon start up, based on the configuration either partner is going to initiate TCP conn. or myself
wfBotPeerEntryDelete .1.3.6.1.4.1.18.3.5.18.3.1.1
Create/Delete attribute. Default is Created Users perform SNMP SET operation on this object in order to create/delete a peer record
wfBotPeerEntryDisable .1.3.6.1.4.1.18.3.5.18.3.1.2
Enables/Disables this mapping entry Setting of this attribute to DISABLED will disconnect all active sessions pertaining to this interface entry
wfBotPeerLocalTcpPort .1.3.6.1.4.1.18.3.5.18.3.1.9
When TCP connection is established, we will have other TCP port number available which is assigned by the system from the available pool. We will fill in this information here in this READ_ONLY variable. Again, based on Originator only one of the following two fields will have valid value. if Originator = SELF then fill in LocalTcpPort field inside the BOT module else fill in PeerTcpPort field inside the BOT module In short, ========= For Originator = SELF PeerTcpListenPort and LocalTcpPort entries are valid For Originator = PARTNER LocalTcpListenPort and PeerTcpPort entries are valid
wfBotPeerRemoteTcpPort .1.3.6.1.4.1.18.3.5.18.3.1.10
Peer TCP port of the connection
wfBotCUSlotNumber .1.3.6.1.4.1.18.3.5.18.4.1.3
slot number used as an index
wfBotCUCctNumber .1.3.6.1.4.1.18.3.5.18.4.1.4
The circuit from which the connection attempt is CCT number for easy link between peer table and cu table
wfBotCURemoteIpAddr .1.3.6.1.4.1.18.3.5.18.4.1.5
IP Address of the remote host with which this translation session is established.
wfBotCULocalTcpListenPort .1.3.6.1.4.1.18.3.5.18.4.1.6
As mentioned earlier only one of following two field will have a valid value, while other will be NULL_VAL, based on who is the ConnOriginator
wfBotCURemoteTcpListenPort .1.3.6.1.4.1.18.3.5.18.4.1.7
field from the peer table entry
wfBotCUAddrReachable .1.3.6.1.4.1.18.3.5.18.4.1.8
In BISYNC controller addresses range from 0-31. In MDL currently there is no way to represent the integer range. As lower bound is zero, here we specify only max possible
wfBotCUEntryDelete .1.3.6.1.4.1.18.3.5.18.4.1.1
Create/Delete attribute. Default is Created Users perform SNMP SET operation on this object in order to create/delete a peer record
wfBotCUEntryDisable .1.3.6.1.4.1.18.3.5.18.4.1.2
Enables/Disables this cu entry Setting of this attribute to DISABLED will disconnect active TCP conn. pertaining to the peer entry
Table
wfBotInterfaceTable .1.3.6.1.4.1.18.3.5.18.2
Interface table which lists all BISYNC line entries and other line related information
wfBotPeerTable .1.3.6.1.4.1.18.3.5.18.3
Peer table lists all TCP connections this router will have with its peers
wfBotCUTable .1.3.6.1.4.1.18.3.5.18.4
CU table lists all CUs reachable from this router on all TCP connections listed in PEER_TABLE
Object Identifier
wfBot .1.3.6.1.4.1.18.3.5.18.1