Supported Platforms
Configuring System Log Messages and SNMP Traps for LSPs
Whenever an LSP makes a transition from up to down, or down to up, and whenever an LSP switches from one active path to another, the ingress router generates a system log message and sends an SNMP trap. The following shows a sample system log message:
MPLS lsp sheep1 up on primary(any) Route 192.168.1.1 192.168.1.2 192.168.1.3 MPLS lsp sheep1 change on primary(any) Route 192.168.1.1 192.168.1.2 192.168.1.3 MPLS lsp sheep1 down on primary(any) MPLS lsp sheep1 up on secondary(any) Route 192.168.1.1 192.168.1.2 192.168.1.3 MPLS lsp sheep1 change on secondary(any) to primary(any), Route 192.168.1.1 192.168.1.2 192.168.1.3
For information about the MPLS SNMP traps and the proprietary MPLS MIBs, see the Network Management Configuration Guide.
To generate system log messages for LSPs, include the syslog option to the log-updown statement:
To generate SNMP traps for LSPs, include the trap option to the log-updown statement:
To generate SNMP traps whenever an LSP path goes down, include the trap-path-down option to the log-updown statement:
To generate SNMP traps whenever an LSP path comes up, include the trap-path-up option to the log-updown statement:
To disable the generation of system log messages, include the no-syslog option to the log-updown statement:
To disable the generation of SNMP traps, include the no-trap statement:
You can include this statement at the following hierarchy levels:
- [edit protocols mpls log-updown]
- [edit logical-systems logical-system-name protocols mpls log-updown]
For scalability reasons, only the ingress router generates SNMP traps. By default, MPLS issues traps for all configured LSPs. If you have many LSPs, the number of traps can become quite large. To disable the generation of SNMP traps, configure the no-trap statement.
The no-trap statement also includes the following options which allow you to block certain categories of MPLS SNMP traps:
- mpls-lsp-traps—Blocks the MPLS LSP traps defined in the jnx-mpls.mib, but allows the rfc3812.mib traps.
- rfc-3812-traps—Blocks the traps defined in the rfc3812.mib, but allows the MPLS LSP traps defined in the jnx-mpls.mib.
