Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
  
[+] Expand All
[-] Collapse All

Related Documentation

  • SNMP Traps Overview
  • Event Traps
  • Decoding Trap Numbers for Raised Trap Actions
  • Decoding Trap Numbers for Clear Trap Actions

Defining SRC ACP Congestion Point Usage Trap Thresholds (SRC CLI)

Four alarms are used for the ACP congestion point usage trap (acpCPUsage): critical, major, minor, and clear trap. Critical, major, and minor traps are sent when the corresponding thresholds are exceeded. The clear trap is sent when the previous event is cleared. When the sampled value falls below a higher threshold but is still above a lower threshold, a clear trap is sent followed by a trap corresponding to the lower threshold.

Objects sent with the traps include the congestion point ID (congestion point DN plus instance ID, which is optional), the CP’s upstream bandwidth, downstream bandwidth, upstream bandwidth in use, and downstream bandwidth in use.

To avoid configuring thresholds for every congestion point, the threshold is defined as a percentage of in-use bandwidth, which is calculated with the following expression:

used bandwidth/(total bandwidth-background bandwidth)

Where, total bandwidth is usually the provisioned bandwidth of the congestion point but can be overridden if the ACP receives an update through L2C or RemoteUpdateInterface.

A congestion point’s upstream bandwidth and downstream bandwidth are evaluated with this expression and compared to the configured threshold separately. If either the upstream or downstream bandwidth of the congestion point exceeds a threshold, a trap corresponding to the threshold is generated. A clear trap is sent only when the usage of both the upstream and downstream bandwidth fall below the threshold. The same trap is not sent multiple times consecutively.

Use the following configuration statements to configure the acpCPUsage trap:

shared acp configuration snmp {selector [selector...];critical-threshold critical-threshold;major-threshold major-threshold;minor-threshold minor-threshold;}

To configure the acpCPUsage trap:

  1. From configuration mode, access the configuration statement that configures the acpCPUsage trap.
    user@host# edit shared acp configuration snmp
  2. (Optional) Configure Java regular expressions to match against congestion point DN. A congestion point is chosen for notification if its DN matches any one of the expressions. If not specified, all congestion points are selected.
    [edit shared acp configuration snmp] user@host# set selector selector;
  3. Configure the critical threshold for the congestion point usage trap. The threshold is a percentage of used bandwidth out of the total accessible bandwidth, which is the current bandwidth minus the background bandwidth of a congestion point.
    [edit shared acp configuration snmp] user@host# set critical-threshold critical-threshold ;
  4. Configure the major threshold for the congestion point usage trap. The threshold is a percentage of used bandwidth out of the total accessible bandwidth, which is the current bandwidth minus the background bandwidth of a congestion point.
    [edit shared acp configuration snmp] user@host# set major-threshold major-threshold ;
  5. Configure the minor threshold for the congestion point usage trap. The threshold is a percentage of used bandwidth out of the total accessible bandwidth, which is the current bandwidth minus the background bandwidth of a congestion point.
    [edit shared acp configuration snmp] user@host# set minor-threshold minor-threshold ;

Related Documentation

  • SNMP Traps Overview
  • Event Traps
  • Decoding Trap Numbers for Raised Trap Actions
  • Decoding Trap Numbers for Clear Trap Actions

Modified: 2017-08-03