Wellfleet-BOT-MIB

File: Wellfleet-BOT-MIB.mib (16881 bytes)

Imported modules

RFC1155-SMI RFC-1212 Wellfleet-COMMON-MIB

Imported symbols

IpAddress Counter OBJECT-TYPE
wfBotGroup

Defined Types

WfBotInterfaceEntry  
SEQUENCE    
  wfBotInterfaceDelete INTEGER
  wfBotInterfaceDisable INTEGER
  wfBotInterfaceCctNumber INTEGER
  wfBotInterfaceSlotNumber INTEGER
  wfBotInterfaceState INTEGER
  wfBotInterfaceType INTEGER
  wfBotInterfaceAttachedTo INTEGER
  wfBotInterfacePktCnt Counter
  wfBotKeepaliveInterval INTEGER
  wfBotKeepaliveRto INTEGER
  wfBotKeepaliveMaxRetry INTEGER

WfBotPeerEntry  
SEQUENCE    
  wfBotPeerEntryDelete INTEGER
  wfBotPeerEntryDisable INTEGER
  wfBotPeerSlotNumber INTEGER
  wfBotPeerCctNumber INTEGER
  wfBotPeerRemoteIpAddr IpAddress
  wfBotConnOriginator INTEGER
  wfBotPeerLocalTcpListenPort INTEGER
  wfBotPeerRemoteTcpListenPort INTEGER
  wfBotPeerLocalTcpPort INTEGER
  wfBotPeerRemoteTcpPort INTEGER

WfBotCUEntry  
SEQUENCE    
  wfBotCUEntryDelete INTEGER
  wfBotCUEntryDisable INTEGER
  wfBotCUSlotNumber INTEGER
  wfBotCUCctNumber INTEGER
  wfBotCURemoteIpAddr IpAddress
  wfBotCULocalTcpListenPort INTEGER
  wfBotCURemoteTcpListenPort INTEGER
  wfBotCUAddrReachable INTEGER

Defined Values

wfBot 1.3.6.1.4.1.18.3.5.18.1
OBJECT IDENTIFIER    

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
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER created(1), deleted(2)  

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
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

wfBotState 1.3.6.1.4.1.18.3.5.18.1.3
The current state of BOT
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER up(1), down(2), init(3), notpresent(4)  

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
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    WfBotInterfaceEntry

wfBotInterfaceEntry 1.3.6.1.4.1.18.3.5.18.2.1
An entry in wfBotInterfaceTable
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  WfBotInterfaceEntry  

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
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER created(1), deleted(2)  

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
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

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.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

wfBotInterfaceSlotNumber 1.3.6.1.4.1.18.3.5.18.2.1.4
Slot number on which this interface is running
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

wfBotInterfaceState 1.3.6.1.4.1.18.3.5.18.2.1.5
The current state of the Interface
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER up(1), down(2), init(3)  

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
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER singledrop(1), multidrop(2)  

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
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER primary(1), secondary(2)  

wfBotInterfacePktCnt 1.3.6.1.4.1.18.3.5.18.2.1.8
Interface packet count ...
Status: mandatory Access: read-only
OBJECT-TYPE    
  Counter  

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.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 0..86400  

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.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 0..600  

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.
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER 0..99  

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
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    WfBotPeerEntry

wfBotPeerEntry 1.3.6.1.4.1.18.3.5.18.3.1
An entry in wfBotPeerTable
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  WfBotPeerEntry  

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
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER created(1), deleted(2)  

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
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

wfBotPeerSlotNumber 1.3.6.1.4.1.18.3.5.18.3.1.3
Slot number on which this peer entry is configured
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

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.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

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.
Status: mandatory Access: read-only
OBJECT-TYPE    
  IpAddress  

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
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER self(1), partner(2)  

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.
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1000..9999  

wfBotPeerRemoteTcpListenPort 1.3.6.1.4.1.18.3.5.18.3.1.8
Peer listen port for TCP connection
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1000..9999  

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
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1000..9999  

wfBotPeerRemoteTcpPort 1.3.6.1.4.1.18.3.5.18.3.1.10
Peer TCP port of the connection
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1000..9999  

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
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    WfBotCUEntry

wfBotCUEntry 1.3.6.1.4.1.18.3.5.18.4.1
An entry in wfBotCUTable
Status: mandatory Access: not-accessible
OBJECT-TYPE    
  WfBotCUEntry  

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
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER created(1), deleted(2)  

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
Status: mandatory Access: read-write
OBJECT-TYPE    
  INTEGER enabled(1), disabled(2)  

wfBotCUSlotNumber 1.3.6.1.4.1.18.3.5.18.4.1.3
slot number used as an index
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

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
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER  

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.
Status: mandatory Access: read-only
OBJECT-TYPE    
  IpAddress  

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
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1000..9999  

wfBotCURemoteTcpListenPort 1.3.6.1.4.1.18.3.5.18.4.1.7
field from the peer table entry
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER 1000..9999  

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
Status: mandatory Access: read-only
OBJECT-TYPE    
  INTEGER address(254)