Comtech EF Data VMS v3.12.x Vipersat - Manual (Page 452)

Introduction MN/22156, rev 12
D-2 VMS User Guide
Using SNMP Traps
SNMP (Simple Network Management Protocol) along with the associated
Vipersat Management Information Base (MIB), provides trap-directed notifica-
tion of network changes.
VMS can be responsible for a large number of network parameters as defined in
the Vipersat MIB. It is impractical for VMS to poll or request information from
each device in a satellite network. Instead of each managed device generating its
own SNMP traps, the VMS detects network status changes and when an event
defined in the MIB occurs responds with a message called a trap.
After receiving a VMS generated trap, a high-level SNMP monitor can take
action based on the trap type, and its parameters.
Using the VMS SNMP traps results in substantial savings of network bandwidth
by eliminating the need for polling devices or having each device in the network
generate its own SNMP traps. The primary purpose of and SNMP trap is high-
order NMS notification.
SNMP Traps Available in VMS
The SNMP trap types available in VMS are:
• Subnet Alarm Trap - This trap is sent to the designated destinations
whenever a subnet’s alarm count or status in Subnet Manager is changed.
This trap contains two values: 1) subnetLabel, 2) subnetAlarmCount
• VMS Server Activated Trap - This trap is sent to the designated
destinations whenever a VMS server is activated (it’s services are started).
The IP address in the trap variable is the VMS server that has been
activated. This trap contains one value: redundancyMode
• VMS Active Server Failed - This trap is sent by a VMS server operating
in stand-by (non-active) mode whenever it has detected a failure of active
server. A vmsServerActivatedTrap will follow when the stand-by is
activated. This trap contains one value: redundancyMode
• Redundant Device Restored Trap - This trap is sent by VMS whenever
the VMS Redundancy Manager has detected a failed device, has shut
down the failed device, and has restored the failed unit with another
device. This trap has four variables.
Note: SNMP Traps relative to the operation of servers in an N:1 redundant
configuration only apply to a network which has the optional N:1 redun-
dant capability available, installed, and configured.
NOTE