vRouter supports specifying SNMP traps for each routing protocol in your configuration. Currently, this feature is supported for BGP, BFD, and OSPF protocols.
Note: SNMP traps for all protocols are disabled by default on the vRouter system. You must enable the SNMP traps by using the set service snmp notification command.
All notifications as defined in the supported MIBs for each routing protocol are enabled by using the keyword all in the command syntax.
In the following figure, the community string for R1 is defined as abc123. The traps from R1 are configured to be sent to the three SNMP Managers that are defined by the IP addresses of 176.16.0.15, 176.16.0.16, and 176.16.0.17, respectively. R1 is connected to R2 and R3 by using a routing protocol, such as BFD. The following configuration example shows how to specify BFD-specific SNMP traps for R1.
Note: The command to enable protocol-specific SNMP traps is similar for all routing protocols. Refer to the SNMP commands section for more information on the command syntax.
Figure 1. Specifying protocol-specific traps
Table 1. Specifying protocol-specific traps
Step
Command
Enable all SNMP traps for BFD on R1.
vyatta@R1# set service snmp notification bfd all
Commit the change.
vyatta@R1# commit
View the change.
vyatta@R1# show bfd
BFD ID: 00 Start Time:Thu Jan 1 00:00:16 1970
BFD Admin State: DOWN
Number of Sessions: 0
Slow Timer: 2000 Image type: MONOLITHIC
Echo Mode: Disabled BFD Notifications enabled
Next Session Discriminator: 1
vyatta@R1# show service snmp
service {
snmp {
community abc123 {
authorization ro
}
notification {
bfd {
all
}
}
}
ssh
}
