Wellfleet-BOT-MIB: View SNMP OID List / Download MIB
VENDOR: WELLFLEET
Home | MIB: Wellfleet-BOT-MIB | |||
---|---|---|---|---|
Download as: |
Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
|
|||
Object Name | OID | Type | Access | Info |
wfBot | 1.3.6.1.4.1.18.3.5.18.1 | |||
wfBotDelete | 1.3.6.1.4.1.18.3.5.18.1.1 | integer | read-write |
Create/Delete parameter. Default is created. User perform an SNMP SET operation on this object in order to create/delete BOT Enumeration: 'deleted': 2, 'created': 1. |
wfBotDisable | 1.3.6.1.4.1.18.3.5.18.1.2 | integer | read-write |
Enable/Disable parameter. Default is enabled. User perform an SNMP SET operation on this object in order to enable/disable BOT Enumeration: 'disabled': 2, 'enabled': 1. |
wfBotState | 1.3.6.1.4.1.18.3.5.18.1.3 | integer | read-only |
The current state of BOT Enumeration: 'down': 2, 'init': 3, 'up': 1, 'notpresent': 4. |
wfBotInterfaceTable | 1.3.6.1.4.1.18.3.5.18.2 | no-access |
Interface table which lists all BISYNC line entries and other line related information |
|
1.3.6.1.4.1.18.3.5.18.2.1 | no-access |
An entry in wfBotInterfaceTable |
||
wfBotInterfaceDelete | 1.3.6.1.4.1.18.3.5.18.2.1.1 | integer | read-write |
Create/Delete attribute. Default is Created Users perform SNMP SET operation on this object in order to create/delete a translation interface record Enumeration: 'deleted': 2, 'created': 1. |
wfBotInterfaceDisable | 1.3.6.1.4.1.18.3.5.18.2.1.2 | integer | read-write |
Enables/Disables this mapping entry Setting of this attribute to DISABLED will disconnect all active sessions pertaining to this interface entry Enumeration: 'disabled': 2, 'enabled': 1. |
wfBotInterfaceCctNumber | 1.3.6.1.4.1.18.3.5.18.2.1.3 | integer | read-only |
The circuit from which the connection attempt is received that initiates a translation session. |
wfBotInterfaceSlotNumber | 1.3.6.1.4.1.18.3.5.18.2.1.4 | integer | read-only |
Slot number on which this interface is running |
wfBotInterfaceState | 1.3.6.1.4.1.18.3.5.18.2.1.5 | integer | read-only |
The current state of the Interface Enumeration: 'down': 2, 'init': 3, 'up': 1. |
wfBotInterfaceType | 1.3.6.1.4.1.18.3.5.18.2.1.6 | integer | read-write |
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 Enumeration: 'singledrop': 1, 'multidrop': 2. |
wfBotInterfaceAttachedTo | 1.3.6.1.4.1.18.3.5.18.2.1.7 | integer | read-write |
Information that this interface is attached to the Primary or secondary BSC station Enumeration: 'primary': 1, 'secondary': 2. |
wfBotInterfacePktCnt | 1.3.6.1.4.1.18.3.5.18.2.1.8 | counter | read-only |
Interface packet count ... |
wfBotKeepaliveInterval | 1.3.6.1.4.1.18.3.5.18.2.1.9 | integer | read-write |
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 | integer | read-write |
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 | integer | read-write |
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. |
wfBotPeerTable | 1.3.6.1.4.1.18.3.5.18.3 | no-access |
Peer table lists all TCP connections this router will have with its peers |
|
1.3.6.1.4.1.18.3.5.18.3.1 | no-access |
An entry in wfBotPeerTable |
||
wfBotPeerEntryDelete | 1.3.6.1.4.1.18.3.5.18.3.1.1 | integer | read-write |
Create/Delete attribute. Default is Created Users perform SNMP SET operation on this object in order to create/delete a peer record Enumeration: 'deleted': 2, 'created': 1. |
wfBotPeerEntryDisable | 1.3.6.1.4.1.18.3.5.18.3.1.2 | integer | read-write |
Enables/Disables this mapping entry Setting of this attribute to DISABLED will disconnect all active sessions pertaining to this interface entry Enumeration: 'disabled': 2, 'enabled': 1. |
wfBotPeerSlotNumber | 1.3.6.1.4.1.18.3.5.18.3.1.3 | integer | read-only |
Slot number on which this peer entry is configured |
wfBotPeerCctNumber | 1.3.6.1.4.1.18.3.5.18.3.1.4 | integer | read-only |
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 | ipaddress | read-only |
IP Address of the remote host with which this translation session is established. |
wfBotConnOriginator | 1.3.6.1.4.1.18.3.5.18.3.1.6 | integer | read-only |
Upon start up, based on the configuration either partner is going to initiate TCP conn. or myself Enumeration: 'partner': 2, 'self': 1. |
wfBotPeerLocalTcpListenPort | 1.3.6.1.4.1.18.3.5.18.3.1.7 | integer | read-only |
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 | integer | read-only |
Peer listen port for TCP connection |
wfBotPeerLocalTcpPort | 1.3.6.1.4.1.18.3.5.18.3.1.9 | integer | read-only |
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 | integer | read-only |
Peer TCP port of the connection |
wfBotCUTable | 1.3.6.1.4.1.18.3.5.18.4 | no-access |
CU table lists all CUs reachable from this router on all TCP connections listed in PEER_TABLE |
|
1.3.6.1.4.1.18.3.5.18.4.1 | no-access |
An entry in wfBotCUTable |
||
wfBotCUEntryDelete | 1.3.6.1.4.1.18.3.5.18.4.1.1 | integer | read-write |
Create/Delete attribute. Default is Created Users perform SNMP SET operation on this object in order to create/delete a peer record Enumeration: 'deleted': 2, 'created': 1. |
wfBotCUEntryDisable | 1.3.6.1.4.1.18.3.5.18.4.1.2 | integer | read-write |
Enables/Disables this cu entry Setting of this attribute to DISABLED will disconnect active TCP conn. pertaining to the peer entry Enumeration: 'disabled': 2, 'enabled': 1. |
wfBotCUSlotNumber | 1.3.6.1.4.1.18.3.5.18.4.1.3 | integer | read-only |
slot number used as an index |
wfBotCUCctNumber | 1.3.6.1.4.1.18.3.5.18.4.1.4 | integer | read-only |
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 | ipaddress | read-only |
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 | integer | read-only |
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 | integer | read-only |
field from the peer table entry |
wfBotCUAddrReachable | 1.3.6.1.4.1.18.3.5.18.4.1.8 | integer | read-only |
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 Enumeration: 'address': 254. |