Enabling the MPLS TE Trap Function

Procedure

• Configure the RSVP trap function.
  1. Run the system-view command to enter the system view.
  2. Run the snmp-agent trap enable feature-name mpls_rsvp [ trap-name trap-name ] command to enable the trap function for the RSVP module.

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

• Configure the alarm 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.

  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 rsvp-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 RSVP LSP usage.

     The parameters in this command are described as follows:

     • upper-limit-value specifies the upper threshold of alarms for RSVP LSP usage. An alarm is generated when the proportion of established RSVP LSPs to total supported RSVP LSPs reaches the upper limit.
     • lower-limit-value specifies the lower threshold of clear alarms for RSVP LSP usage. A clear alarm is generated when the proportion of established RSVP LSPs to total supported RSVP 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 RSVP LSP usage is 80%. The default lower limit of a clear alarm for RSVP LSP usage is 75%. Using the default upper limit and lower limit is recommended.

     

     • This command configures the alarm threshold for RSVP LSP usage. The alarm that the number of RSVP 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 RSVP LSP usage reaches the upper limit of the alarm threshold. The alarm that the number of RSVP 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 RSVP 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 RSVP LSPs reaches the upper limit, a limit-crossing alarm is generated.

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

  7. Run the mpls total-crlsp-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 CR-LSP usage.

     The parameters in this command are described as follows:

     • upper-limit-value specifies the upper threshold of alarms for total CR-LSP usage. An alarm is generated when the proportion of established CR-LSPs to total supported CR-LSPs reaches the upper limit.
     • lower-limit-value specifies the lower threshold of clear alarms for total CR-LSP usage. A clear alarm is generated when the proportion of established CR-LSPs to total supported CR-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 CR-LSP usage is 80%. The default lower limit of a clear alarm for total CR-LSP usage is 75%. Using the default upper limit and lower limit is recommended.

     

     • This command configures the alarm threshold for total CR-LSP usage. The alarm that the number of total CR-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 CR-LSP usage reaches the upper limit of the alarm threshold. The alarm that the number of total CR-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 CR-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 CR-LSPs reaches the upper limit, a limit-crossing alarm is generated.

       • If the total number of CR-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 rsvp-peer-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 RSVP neighbors.

     Note the following issues when configuring trigger conditions:

     • upper-limit-value: upper alarm threshold for the proportion of configured RSVP neighbors to all RSVP neighbors supported by a device.
     • lower-limit-value: lower alarm threshold for the proportion of configured RSVP neighbors to all RSVP neighbors 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.

     

     • The mpls rsvp-peer-number threshold-alarm 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_rsvp trap-name { hwrsvpteifnbrthresholdexceed | hwrsvpteifnbrthresholdexceedclear } command is run to enable the device to generate the RSVP neighbor threshold-reaching alarm and its clear alarm.

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

       • If the number of configured RSVP neighbors reaches the maximum number of RSVP neighbors supported by a device, a limit-reaching alarm is generated.

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

  4. Run the mpls bfd-te-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 TE.

     Note the following issues when configuring trigger conditions:

     • upper-limit-value: upper alarm threshold for the proportion of used TE resources to all TE resources supported by a device.
     • lower-limit-value: lower alarm threshold for the proportion of used TE resources to all TE 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 MPLS 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 TE resources reaches the maximum number of TE resources supported by a device, a limit-reaching alarm is generated.

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

  5. Run the mpls autobypass-tunnel-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 Auto bypass tunnel interfaces.

     Note the following issues when configuring trigger conditions:

     • upper-limit-value: upper alarm threshold for the proportion of used TE resources to all TE resources supported by a device.
     • lower-limit-value: lower alarm threshold for the proportion of used TE resources to all TE 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 MPLS 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 TE resources reaches the maximum number of TE resources supported by a device, a limit-reaching alarm is generated.

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