Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Panel

In this section:

Table of Contents
maxLevel4

 

This page describes the Simple Network Management Protocol (SNMP) Management Information Base (MIB) entries and Traps supported by VX. SNMP is UDP-based network protocol for monitoring network devices.

For more information about configuring VX for SNMP, see Configuring SNMP.

SNMP MIBs Supported by VX

Standard MIBs

Standard MIBs are authored by persons associated with IETF. VX implements the following standard MIB groups complying with

Rfc
1213
1213
.

  • system group
  • interfaces group
  • ip group
  • icmp group
  • tcp group
  • udp group
  • snmp group

VX also implements 'ifName' and 'ifAlias' MIBs of extended interface table (ifXTable) to partially support

Rfc
2233
2233
. Refer to Ethernet Adapter configuration section of 'VXbuilder user guide' for configuring 'ifName', 'ifAlias' and 'ifDesc' MIBs.

VX MIBs

VX MIBs are authored by NET and are organized under NET's enterprise OID (1.3.6.1.4.1.177) assigned by the Internet Assigned Number Authority (IANA).

The following sections provide a categorized list of VX MIBs with their definitions

Port level and Channel level Call Statistics related MIBs

  • TotalCalls – Total number of calls placed on this port or channel irrespective of success or failure
  • ConnectedCalls – Total number of calls that were successfully established and connected through this port or channel
  • RefusedCalls – Number of calls on this port or channel that failed to connect due to no route or far end reject or peer reject
  • ErroredCalls – Number of calls on this port or channel that failed do to VX error or unexpected error
  • ConnectedTime – Total amount of time in seconds this channel or port was utilized. This statistics gets updated at the end of the call
  • IVRTime – Total amount of time in seconds this channel or port has been in the IVR state
  • EgressCallAttempts – Total number of calls attempts on this port or channel in the outbound direction
  • EgressCallsAccepted – Total number of calls on this port or channel in the outbound direction that were successfully routed and ringing at the far end
  • EgressCallsCompleted – Total number of calls that were successfully established and connected on this port or channel in the outbound direction
  • EgressCallsRejected --Number of calls on this port or channel in the outbound direction that failed to connect due to no route or far end reject or reject from peer
  • EgressCallsRequiringPreemption – Number of calls on this port or channel in the outbound direction that were dropped as they were preempted by high priority calls
  • IngressCallAttempts – Total number of calls attempts on this port or channel in the outbound direction
  • IngressCallsAccepted – Total number of calls on this port or channel in the outbound direction that were successfully routed and ringing at the far end
  • IngressCallsCompleted – Total number of calls that were successfully established and connected on this port or channel in the inbound direction
  • IngressCallsRejected --Number of calls on this port or channel in the inbound direction that failed to connect due to no route or far end reject or reject from peer

Call statistics related MIBs that applies to port level statistics only

  • CurrentCalls – Total number of calls that are active on this port at this time
  • CurrentIVRCalls – Total number of calls active on this port at this time that are in IVR state
  • portHour1, portHour2,... portHour24 – Last 24 hour aggregated hourly statistics of calls on this port for the respective hour. Hours are represented in circular 24 hour format. If current hour is 3:15pm then 'Hour16' represent the statistics of calls from the start of 3pm today till now, same way 'Hour1' represent calls placed between 12am - 12:59am this morning and 'Hour21' represent calls placed between yesterday 8pm – 8:59pm.

IBP MIBs

  • ibpInReceives – The total number of input datagrams received from interfaces, including those received in error
  • ibpInUnknownVers - The number of input datagrams discarded due to an unknown IBP protocol version in the header
  • ibpInUnknownProtos - The number of locally-addressed datagrams received successfully but discarded because of an unknown or unsupported protocol
  • ibpInBadChecksums - The number of input datagrams discarded due to an invalid checksum in the header
  • ibpInAddrErrors - The number of input datagrams discarded because the node ID in the IBP header was not a valid address to be received at this entity. This counter includes datagrams discarded because the destination node ID was not the local node ID
  • ibpInDiscards - The number of input datagrams for which no problems were encountered to prevent their continued processing, but which were discarded (e.g., for lack of buffer space)
  • ibpInDelivers - The total number of input datagrams successfully delivered to IBP user-protocols (including BCMP)
  • ibpOutRequests - The total number of IBP datagrams which local IBP user-protocols (including BCMP) supplied to IBP in requests for transmission
  • ibpOutDiscards - The number of output IBP datagrams for which no problem was encountered to prevent their transmission to their destination, but which were discarded (e.g., for lack of buffer space)
  • ibpOutNoRoutes - The number of IBP datagrams discarded because no route could be found to transmit them to their destination. Note that this includes any datagarms which a host cannot route because all of its default gateways are down

Link Quality Management related MIBs

The following LQM related MIBs are implemented to monitor peer nodes

  • lqmState – State of Peer - up(1) or down(2)
  • lqmPeerIBPVersion - IBP version of the peer. 0 is Unknown, 1 =IBPVersion1, 2 =IBPVersion2
  • lqmPeerLastTimeUp - Time when peer came up last. From the time system came up
  • lqmPeerLastTimeDown - Time when peer went down last. From the time system came up
  • lqmPeerTransitions - Number of times Peer changed state between Up and Down
  • lqmPeerLastTimePingSent - Time when last ping packet was sent to this peer. From the time system came up
  • lqmPeerLastTimePingRecv - Time when last ping packet was received from this peer. From the time system came up
  • lqmPingInitial - Number of initial Ping packets sent to the peer
  • lqmPingSent - Number of ping packets sent to this peer
  • lqmPingSentNoReply - Number of ping packets sent for which reply is not received
  • lqmPingRecv - Number of ping response received from this peer
  • lqmPingLost - Number of ping packets lost
  • lqmPercentPingLost - Percent ping packets lost
  • lqmAverageRTT - Average Round Trip Time with this peer, measured in unit of 100 microsecond. 10 means 1 millisecond
  • lqmMinRTT - Minimum Round Trip Time with this peer, measured in unit of 100 microsecond. 10 means 1 millisecond
  • lqmMaxRTT - Maximum Round Trip Time with this peer, measured in unit of 100 microsecond. 10 means 1 millisecond
  • lqmLastTimeFailCall - Last Time when a call failed with peer, measure from the time system came up
  • lqmFailCallsInRow - Number of calls failed in a Row with this peer. Resets to 0, if call succeeds

Peer related MIBs

Peer Tables are available for monitoring via SNMP, with the following MIBs defined

  • peerType – This is type of Peer: BSP(1),ICMP(2) or SIP-OPTIONS(3)
  • peerNodeID – The node ID of the peer in dotted decimal IPAddress format. Valid only for BSP peers
  • peerIpAddress – IpAddress of the peer
  • peerFQDN – FQDN of the peer
  • interface – Interface to reach the peer
  • peerPing – This suggests, if Ping to peer is enabled/disabled
  • peerPingInterval – This is time interval in seconds between ping packet sent to the peer. If peerPing is disabled, this will be 0
  • boostMultiplier – Boost multiplier for the failed call
  • failureHoldOff – Failure Hold off time in milliseconds
  • vtpTimeOut – vtpTimeOut in milliseconds
  • diffServLevel – DiffServ Level configured in the VX peer table
  • peerTransportType --The transport type of SIP-OPTIONS Peer

VX Chassis identification MIBs

Chassis type of the VX node can be identified using the standard MIB 'sysObjectID'. It points to one of the following MIBs:

  • vxDevelopment - chassis type internal to NET use
  • vx900AB
  • vx900AD
  • vx1800

SNMP Traps Supported by VX

The following SNMP Trap Codes are defined in 'VX_traps.my' and they use the MIBs defined under the 'configuration2' identifier to detail the trap events

  • routeEventMsg – Notification of a call routing event
  • routeOverflow - Trap generated when route overflow occurs
  • routeOverflowClear - Trap generated when a route overflow gets cleared
  • callReroute - Trap generated when a call gets re-routed
  • routeOverflowClearReconfig - Trap generated when config change occurs on a route table. Any overflowing route entry in that route table will be marked 'cleared'
  • newPeerEntry - Trap generated when a new peer is added in the system. Hence a new entry will be added in the peer table. It gives information about the new peer added to the system
  • shutDownReason – Reason for VX shutdown
  • matchingCallRouteEntries - Gives the Previous matching call route entry and Next matching call route entry
  • systemShutDown - Trap generated when VX service is shutdown with shutdown reason
  • userLoggedIn – Notification of user login to VX
  • userLoggedOut – User logout from VX notification userAuthenticationFailed - rap is generated when a user fails authentication during attempt to log into VX, indicating possiblity of misuse
  • userPasswordChanged – password change notification
  • userAccountLocked – rap is generated when a user is locked out due to more than permitted failed attempts to login
  • userPasswdExpired - Trap is generated when a user is disabled due to expiry of password
  • userUserExpired - Trap is generated to inform that user has not been used for long time

For alarms generated by VX, the system will also generate a generic trap indicating the severity of the alarm. The trap will include the complete text of the alarm for human evaluation. The following severities are used

  • vxAlarmNormal --Alarm notification Normal level
  • vxAlarmInfo – Info level Alarm notification
  • vxAlarmWarn – Warning level Alarm notification
  • vxAlarmErr – Error level Alarm notification
  • vxAlarmCrit – Critical level Alarm notification
  • vxAlarmAlert – Alert level Alarm notification
  • vxAlarmEmerg – Emergency level alarm notification