Use SNMP Traps

Last updated
Save as PDF

When something of interest happens on an individual device in the overlay network, the device reports the event in the following ways:

Send a notification to the vManage NMS. The vManage NMS filters the event notifications and correlates related events, and it consolidates major and critical events into alarms.
Send an SNMP trap to the configured trap target. For each SNMP trap that a device generates, the device also generates a corresponding notification message.
Generate a system logging (syslog) message and place it in a syslog file in the /var/log directory on the local device and, if configured, on a remote device.

SNMP traps are asynchronous notifications that a Viptela device sends to an SNMP management server. Traps notify the management server of events, whether normal or significant, that occur on the Viptela device. By default, SNMP traps are not sent to an SNMP server. Note that for SNMPv3, the PDU type for notifications ie either SNMPv2c inform (InformRequest-PDU) or trap (Trapv2-PDU).

Configure SNMP Traps

To configure SNMP traps, you define the traps themselves and you configure the SNMP server that is to receive the traps. To configure these from vManage NMS, use the SNMP feature configuration template.

From the CLI, to configure groups of traps to be collected on a Viptela device, use the trap group command:

Viptela(config-snmp)# trap group group-name
Viptela(config-group)# trap-type level severity

The group-name is a name of your choosing. A single trap group can contain multiple trap types. In the configuration, specify one trap type per line, and each trap type can have one, two, or three severity levels. See the configuration example below for an illustration of the configuration process.

The trap-type can be one of those listed in the table below. The severity can be critical, major, or minor.

From the CLI to configure the SNMP server to receive the traps, use the trap target command:

Viptela(config-snmp)# trap target vpn vpn-id ipv4-address udp-port
Viptela(config-target)# group-name name
Viptela(config-target)# community-name community-name
Viptela(config-target)# source-interface interface-name

For each SNMP server, specify the identifier of VPN where the server is located, the server's IPv4 address, and the UDP port on the server to connect to. When configuring the trap server's address, you must use an IPv4 address. You cannot use an IPv6 address.

In the group-name command, associate a previously configured trap group with the server. The traps in that group are sent to the SNMP server.

In the community-name command, associate a previously configure SNMP community with the SNMP server.

In the source-interface command, configure the interface to use to send traps to the SNMP server that is receiving the trap information. This interface cannot be a subinterface.

SNMP Traps

The following table lists the SNMP traps by severity level. For each SNMP trap that a Viptela device generate, the device generates a notification message.

Trap Type	Critical	Major	Minor
all	All critical traps listed below.	All major traps listed below.	All minor traps listed below.
app-route		SLA_Change
bfd		BFD_State_Change
bridge		Bridge_Interface_State_Change	Bridge_Creation Bridge_Deletion Max_MAC_Reached
control	No_Active_vBond No_Active_vSmart	Connection_Auth_Fail Connection_State_Change Connection_TLOC_IP_Change vBond_State_Change	Control_vEdge_List_Request
dhcp		Server_State_Change	Address_Assigned Address_Released Address_Renewed Request_Rejected
hardware		EMMC_Fault Fan_Fault FanTray_Fault Flash_Fault PEM_Fault PEM_State_Change PIM_Fault PIM_State_Change SDCard_Fault SFP_State_Change TempSensor_Fault TempSensor_State USB_State_Change	SFP_Support_State
omp		Data_Policy Number_of_vSmarts_Change Peer_State_Change Policy State_Change TLOC_State_Change
policy		Access_List_Association_Status Data_Policy_Association_Status SLA_Violation_Pkt_Drop	SLA_Violation
routing		BGP_Peer_State_Change OSPF_Interface_State_Change OSPF_Neighbor_State_Change PIM_Interface_State_Change PIM_Neighbor_State_Change PIM_TUnnel_Change PIM_Tunnel_State_Change
security		Certificate_Expired Clear_Installed_Certificate Device_Template_Missing Reject_vEdge_COnnection Root_Cert_Chain_Uninstalled vEdge_Entry_Added vEdge_Entry_Removed vEdge_Serial_File_Uploaded vSmart_Entry_Added vSmart_Entry_Removed vSmart_Serial_File_Uploaded	Certificate_Installed Device_Template_Attached_During_ZTP New_CSR_Generated Root_Cert_Chain_Installed Service_GRE_State_Update Tunnel_IPSec_Manual_Rekey Tunnel_IPSec_Rekey vManage_Connection_Preference_Changed
system		AAA_Admin_Pwd_Change AAA_Login_Fail App_DPI_Flow_Out_Of_Memory APP_DPI_Flow_Write_Failed_vEdge Disk_Usage Memory_Usage Process_Down Process_Restart Pseudo_Commit_Status Reboot_Aborted Reboot_Complete	Domain_ID_Change Org_Name_Change Reboot_Issued Site_ID_Change Software_Install_Status System_Commit System_IP_Change System_Login_Change System_Logout_Change
vpn		CloudExpress_Max_Local_Exit_Exceeded CloudExpress_Score_Change If_BW_Update Interface_Admin_State_Change Interface_PCS_Fault_Detected Interface_State_Change VRRP_Group_State_Change	CloudExpress_Application_Change FIB_Update Route_Install_Fail Tunnel_Install_Fail
wwan		Bearer_Change Domain_State_Change Reg_State_Change SIM_State_Change

Additional Information

Monitor Alarms
Monitor Event Notifications
Use Syslog Messages