Enabling the MPLS Trap Function

Procedure

• Configuring the trap function for LDP
  1. Run the system-view command to enter the system view.
  2. Run the snmp-agent trap enable feature-name ldp trap-name { session-down-mib | session-pvl | session-retry | session-up-mib } command to enable the trap function for the MPLS LDP module.

     By default, the trap function is disabled for the MPLS LDP module.

• Configure the trap function for LSPM.
  1. Run the system-view command to enter the system view.
  2. Run the snmp-agent trap enable feature-name mpls_lspm trap-name trapname command to enable the trap function for the LSPM module.

     By default, the trap function is disabled for the LSPM module.

     When performing the following steps to configure alarm thresholds, pay attention to the following points:

     • To configure the alarm function for dynamic label usage, specify hwMplsDynamicLabelThresholdExceed and hwMplsDynamicLabelThresholdExceedClear to enable the threshold exceeding alarm and clear alarm when configuring trap-name. When the usage of dynamic labels exceeds the upper threshold or falls below the lower threshold, the system generates a threshold exceeding alarm or clear alarm.

     • To configure the LSP usage alarm function, specify hwmplslspthresholdexceed and hwmplslspthresholdexceedclear to enable the threshold exceeding alarm and clear alarm when configuring trap-name. When the LSP usage exceeds the upper threshold or falls below the lower threshold, the system generates a threshold exceeding alarm or clear alarm.

  3. Run the snmp-agent trap suppress feature-name lsp trap-name { mplsxcup | mplsxcdown } trap-interval trap-interval [ max-trap-number max-trap-number ] command to set the interval for suppressing excess LSP traps.

     By default, the interval for suppressing the display of excessive LSP traps is 300 seconds, and a maximum of three LSP traps can be sent in the suppression interval.

  4. Run the mpls command to enter the MPLS view.
  5. Run the mpls dynamic-label-number threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value command to set alarm thresholds for dynamic label usage.

     You can set the following parameters:

     • upper-limit-value: a percent indicating the upper limit of dynamic labels. If dynamic label usage reaches the upper limit, an alarm is generated. An upper limit less than or equal to 95% is recommended.
     • lower-limit-value: a percent indicating the lower limit of dynamic labels. If dynamic label usage falls below the lower limit, an alarm is generated.
     • The value of upper-limit-value must be greater than that of lower-limit-value.

     By default, the upper limit is 80%, and the lower limit is 70%, which are recommended.

     

     • Each command only configures the trigger conditions for an alarm and its clear alarm. Although trigger conditions are met, the alarm and its clear alarm can be generated only after the snmp-agent trap enable feature-name mpls_lspm trap-name { hwMplsDynamicLabelThresholdExceed | hwMplsDynamicLabelThresholdExceedClear } command is run to enable the device to generate a dynamic label insufficiency alarm and its clear alarm.

     • After the snmp-agent trap enable feature-name mpls_lspm trap-name { hwMplsDynamicLabelTotalCountExceed | hwMplsDynamicLabelTotalCountExceedClear } command is run to enable the device to generate limit-reaching alarms and their clear alarms, the following situations occur:

       • If the number of dynamic labels reaches the maximum number of dynamic labels supported by a device, a limit-reaching alarm is generated.

       • If the number of dynamic labels falls below 95% of the maximum number of dynamic labels supported by the device, a clear alarm is generated.

  6. Run the mpls ldp-lsp-number [ ingress | transit | egress ] threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value command to configure the upper and lower thresholds of alarms for LDP LSP usage.

     The parameters in this command are described as follows:

     • upper-limit-value specifies the upper threshold of alarms for LDP LSP usage. An alarm is generated when the proportion of established LDP LSPs to total supported LDP LSPs reaches the upper limit.
     • lower-limit-value specifies the lower threshold of clear alarms for LDP LSP usage. A clear alarm is generated when the proportion of established LDP LSPs to total supported LDP LSPs falls below the lower limit.
     • The value of upper-limit-value must be greater than that of lower-limit-value.

     The default upper limit of an alarm for LDP LSP usage is 80%. The default lower limit of a clear alarm for LDP LSP usage is 75%. Using the default upper limit and lower limit is recommended.

     

     • This command configures the alarm threshold for LDP LSP usage. The alarm that the number of LSPs reached the upper threshold is generated only when the command snmp-agent trap enable feature-name mpls_lspm trap-name hwmplslspthresholdexceed is configured, and the actual LDP LSP usage reaches the upper limit of the alarm threshold. The alarm that the number of LSPs fell below the lower threshold is generated only when the command snmp-agent trap enable feature-name mpls_lspm trap-name hwmplslspthresholdexceedclear is configured, and the actual LDP LSP usage falls below the lower limit of the clear alarm threshold.

     • After the snmp-agent trap enable feature-name mpls_lspm trap-name { hwmplslsptotalcountexceed | hwmplslsptotalcountexceedclear } command is run to enable LSP limit-crossing alarm and LSP limit-crossing clear alarm, an alarm is generated in the following situations:

       • If the total number of LDP LSPs reaches the upper limit, a limit-crossing alarm is generated.

       • If the total number of LDP LSPs falls below 95% of the upper limit, a limit-crossing clear alarm is generated.

  7. Run the mpls bgp-lsp-number [ ingress | egress ] threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value command to configure the upper and lower thresholds of alarms for BGP LSP usage.

     The parameters in this command are described as follows:

     • upper-limit-value specifies the upper threshold of alarms for BGP LSP usage. An alarm is generated when the proportion of established BGP LSPs to total supported BGP LSPs reaches the upper limit.
     • lower-limit-value specifies the lower threshold of clear alarms for BGP LSP usage. A clear alarm is generated when the proportion of established BGP LSPs to total supported BGP LSPs falls below the lower limit.
     • The value of upper-limit-value must be greater than that of lower-limit-value.

     The default upper limit of an alarm for BGP LSP usage is 80%. The default lower limit of a clear alarm for BGP LSP usage is 75%. Using the default upper limit and lower limit is recommended.

     

     • This command configures the alarm threshold for BGP LSP usage. The alarm that the number of LSPs reached the upper threshold is generated only when the command snmp-agent trap enable feature-name mpls_lspm trap-name hwmplslspthresholdexceed is configured, and the actual BGP LSP usage reaches the upper limit of the alarm threshold. The alarm that the number of LSPs fell below the lower threshold is generated only when the command snmp-agent trap enable feature-name mpls_lspm trap-name hwmplslspthresholdexceedclear is configured, and the actual BGP LSP usage falls below the lower limit of the clear alarm threshold.

     • After the snmp-agent trap enable feature-name mpls_lspm trap-name { hwmplslsptotalcountexceed | hwmplslsptotalcountexceedclear } command is run to enable LSP limit-crossing alarm and LSP limit-crossing clear alarm, an alarm is generated in the following situations:

       • If the total number of BGP LSPs reaches the upper limit, a limit-crossing alarm is generated.

       • If the total number of BGP LSPs falls below 95% of the upper limit, a limit-crossing clear alarm is generated.

  8. Run the mpls bgpv6-lsp-number [ egress ] threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value command to configure the upper and lower thresholds of alarms for BGP IPv6 LSP usage.

     The parameters in this command are described as follows:

     • upper-limit-value specifies the upper threshold of alarms for BGP IPv6 LSP usage. An alarm is generated when the proportion of established BGP IPv6 LSPs to total supported BGP IPv6 LSPs reaches the upper limit.
     • lower-limit-value specifies the lower threshold of clear alarms for BGP IPv6 LSP usage. A clear alarm is generated when the proportion of established BGP IPv6 LSPs to total supported BGP IPv6 LSPs falls below the lower limit.
     • The value of upper-limit-value must be greater than that of lower-limit-value.

     The default upper limit of an alarm for BGP IPv6 LSP usage is 80%. The default lower limit of a clear alarm for BGP IPv6 LSP usage is 75%. Using the default upper limit and lower limit is recommended.

     

     • This command configures the alarm threshold for BGP IPv6 LSP usage. The alarm that the number of LSPs reached the upper threshold is generated only when the command snmp-agent trap enable feature-name mpls_lspm trap-name hwmplslspthresholdexceed is configured, and the actual BGP IPv6 LSP usage reaches the upper limit of the alarm threshold. The alarm that the number of LSPs fell below the lower threshold is generated only when the command snmp-agent trap enable feature-name mpls_lspm trap-name hwmplslspthresholdexceedclear is configured, and the actual BGP IPv6 LSP usage falls below the lower limit of the clear alarm threshold.

     • After the snmp-agent trap enable feature-name mpls_lspm trap-name { hwmplslsptotalcountexceed | hwmplslsptotalcountexceedclear } command is run to enable LSP limit-crossing alarm and LSP limit-crossing clear alarm, an alarm is generated in the following situations:

       • If the total number of BGP IPv6 LSPs reaches the upper limit, a limit-crossing alarm is generated.

       • If the total number of BGP IPv6 LSPs falls below 95% of the upper limit, a limit-crossing clear alarm is generated.

  9. Run the mpls total-lsp-number [ ingress | transit | egress ] threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value command to configure the upper and lower thresholds of alarms for total LSP usage.

     The parameters in this command are described as follows:

     • upper-limit-value specifies the upper threshold of alarms for total LSP usage. An alarm is generated when the proportion of established LSPs to total supported LSPs reaches the upper limit.
     • lower-limit-value specifies the lower threshold of clear alarms for total LSP usage. A clear alarm is generated when the proportion of established LSPs to total supported LSPs falls below the lower limit.
     • The value of upper-limit-value must be greater than that of lower-limit-value.

     The default upper limit of an alarm for total LSP usage is 80%. The default lower limit of a clear alarm for total LSP usage is 75%. Using the default upper limit and lower limit is recommended.

     

     • This command configures the alarm threshold for total LSP usage. The alarm that the number of LSPs reached the upper threshold is generated only when the command snmp-agent trap enable feature-name mpls_lspm trap-name hwmplslspthresholdexceed is configured, and the actual total LSP usage reaches the upper limit of the alarm threshold. The alarm that the number of LSPs fell below the lower threshold is generated only when the command snmp-agent trap enable feature-name mpls_lspm trap-name hwmplslspthresholdexceedclear is configured, and the actual total LSP usage falls below the lower limit of the clear alarm threshold.

     • After the snmp-agent trap enable feature-name mpls_lspm trap-name { hwmplslsptotalcountexceed | hwmplslsptotalcountexceedclear } command is run to enable LSP limit-crossing alarm and LSP limit-crossing clear alarm, an alarm is generated in the following situations:

       • If the total number of LSPs reaches the upper limit, a limit-crossing alarm is generated.

       • If the total number of LSPs falls below 95% of the upper limit, a limit-crossing clear alarm is generated.

• Configure MPLS resource threshold-related alarms.
  1. Run the system-view command to enter the system view.
  2. Run the mpls command to enter the MPLS view.
  3. Run the mpls bfd-ldp-number threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value command to configure the conditions that trigger the threshold-reaching alarm and its clear alarm for dynamic BFD sessions for LDP.

     Note the following issues when configuring trigger conditions:

     • upper-limit-value: upper alarm threshold of the proportion of used LDP resources to all LDP resources supported by a device.
     • lower-limit-value: lower alarm threshold for the proportion of used LDP resources to all LDP resources supported by a device.
     • The value of upper-limit-value must be greater than that of lower-limit-value.

     By default, the upper alarm threshold is 80%, and the lower alarm threshold is 75%, which are recommended.

     

     • Each command only configures the trigger conditions for an alarm and its clear alarm. Although trigger conditions are met, the alarm and its clear alarm can be generated only after the snmp-agent trap enable feature-name mpls_lspm trap-name { hwmplsresourcethresholdexceed | hwmplsresourcethresholdexceedclear } command is run to enable the device to generate an LDP resource insufficiency alarm and its clear alarm.

     • After the snmp-agent trap enable feature-name mpls_lspm trap-name { hwmplsresourcetotalcountexceed | hwmplsresourcetotalcountexceedclear } command is run to enable the device to generate limit-reaching alarms and their clear alarms, the following situations occur:

       • If the number of used LDP resources reaches the maximum number of LDP resources supported by a device, a limit-reaching alarm is generated.

       • If the number of used LDP resources falls below 95% of the maximum number of LDP resources supported by the device, a clear alarm is generated.

  4. Run the mpls remote-adjacency-number threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value command to configure the conditions that trigger the threshold-reaching alarm and its clear alarm for remote LDP adjacencies.

     Note the following issues when configuring trigger conditions:

     • upper-limit-value: upper alarm threshold of the proportion of used LDP resources to all LDP resources supported by a device.
     • lower-limit-value: lower alarm threshold for the proportion of used LDP resources to all LDP resources supported by a device.
     • The value of upper-limit-value must be greater than that of lower-limit-value.

     By default, the upper alarm threshold is 80%, and the lower alarm threshold is 75%, which are recommended.

     

     • Each command only configures the trigger conditions for an alarm and its clear alarm. Although trigger conditions are met, the alarm and its clear alarm can be generated only after the snmp-agent trap enable feature-name mpls_lspm trap-name { hwmplsresourcethresholdexceed | hwmplsresourcethresholdexceedclear } command is run to enable the device to generate an LDP resource insufficiency alarm and its clear alarm.

     • After the snmp-agent trap enable feature-name mpls_lspm trap-name { hwmplsresourcetotalcountexceed | hwmplsresourcetotalcountexceedclear } command is run to enable the device to generate limit-reaching alarms and their clear alarms, the following situations occur:

       • If the number of used LDP resources reaches the maximum number of LDP resources supported by a device, a limit-reaching alarm is generated.

       • If the number of used LDP resources falls below 95% of the maximum number of LDP resources supported by the device, a clear alarm is generated.