Specifying an Egress Point for SNMP Traps
You can enable SNMP trap proxy, which allows you to specify a single SNMP agent
as the egress point for SNMP traps from all other virtual routers. This feature removes
the need to configure a network path from each virtual router to a single trap collector.
You can enable SNMP trap proxy from either SNMP or the CLI. Only one SNMP trap
proxy can exist for a physical router.
The SNMP trap proxy does not forward global traps that it receives from other virtual
routers. The corresponding SNMP agent handles global traps locally and does not
forward them to the SNMP trap proxy.
To configure the SNMP trap proxy:
1. Access the virtual router context.
2. Enable or disable the SNMP trap proxy.
snmp-server trap-proxy
■ Use to enable or disable the SNMP trap proxy.
■ Example
host1(config)#snmp-server trap-proxy enable
■ Use the no version to disable the SNMP trap proxy.
■ See snmp-server trap-proxy.
Configuring Trap Queues
You can control the SNMP trap egress rate, specify the method of handling a full
queue, and specify the maximum number of traps kept in the queue.
snmp-server host
Use to control the SNMP trap egress rate for the host that is receiving SNMP
traps. Use one or more of the following keywords:
■
■ drainRate—Specifies the maximum number of traps per second sent to the
host
■ full—Specifies the method for handling the queue full condition
■ size—Specifies the maximum number of traps kept in the queue
■ Example
host1(config)#snmp-server host 10.10.10.10 trapqueue drainrate 600 full
droplastin size 50
■ Use the no version to remove the SNMP host.
■ See snmp-server host.
174 ■ Configuring Traps
JUNOSe 11.1.x System Basics Configuration Guide