Users may see the message "Avoid normalization: not needed as already running with max-members" printed when there is only one active label-switched path (LSP) for the container LSP even though the container LSP is configured with " maximum-member-lsps 2 " or more.
maximum-member-lsps 2
This article explains that the message is expected when the container is running with configured max-members or with the required (minimum) members for the sampled aggregate bandwidth. Since this is expected behavior, no action needs to be taken.
The message "Avoid normalization: not needed as already running with max-members" gets printed when there is only one active LSP for the container LSP even though the container LSP is configured with " maximum-member-lsps 2 " or more (the sample below has 5).
protocols { mpls { container-label-switched-path container-test-lsp { splitting-merging { maximum-member-lsps 5; <<< Max LSPs for this container-lsp is 5. splitting-bandwidth 1g; merging-bandwidth 500m; normalization { normalize-interval 400; failover-normalization; normalization-retry-duration 50; normalization-retry-limits 3; } sampling { use-percentile 95; } } } ...
An example is given below:
router1 > show mpls container-lsp ingress name container-test-lsp extensive .. Container LSP name: container-test-lsp, State: Up, Member count: 1 <<< Currently only one member LSP is within this container-test-lsp. Normalization Min LSPs: 1, Max LSPs: 5 <<< Configured max-members as 5 Aggregate bandwidth: 1000kbps, Sampled Aggregate bandwidth: 1.16955kbps <<< Current bandwidth is 1000kbps; required/sampled bandwidth is only 1.16955kbps. NormalizeTimer: 400 secs, NormalizeThreshold: 10% Max Signaling BW: 1000Mbps, Min Signaling BW: 500Mbps, Splitting BW: 1000Mbps, Merging BW: 500Mbps <<< Splitting bandwidth 1Gbps Mode: incremental-normalization, failover-normalization Sampling: Outlier cut-off 0, Percentile 95 of Aggregate Normalization in 151 second(s) 9374 Sep 16 13:01:58.071 Clear history and statistics: on container (container-test-lsp) 9373 Sep 16 13:01:18.691 Avoid normalization: not needed as already running with max-members <<< Only 1 member LSP but the log is seen with the message "running with max-members." 9372 Sep 16 13:01:18.691 Normalize: normalization with aggregate bandwidth 1359 bps 9371 Sep 16 12:55:43.068 Clear history and statistics: on container (container-test-lsp) 9370 Sep 16 12:54:38.690 Avoid normalization: not needed as already running with max-members <<< Only 1 member LSP but the log is seen with the message "running with max-members." 9369 Sep 16 12:54:38.690 Normalize: normalization with aggregate bandwidth 2835 bps 9368 Sep 16 12:48:13.070 Clear history and statistics: on container (container-test-lsp) 9367 Sep 16 12:47:58.690 Avoid normalization: not needed as already running with max-members 9366 Sep 16 12:47:58.690 Normalize: normalization with aggregate bandwidth 839 bps ... 9327 Sep 16 09:07:59.020 Avoid normalization: not needed as already running with max-members <<< With over 5Gbps traffic, max-members 5*lsps reached (maximum-member-lsps 5;splitting-bandwidth 1g per configuration); expected. 9326 Sep 16 09:07:59.020 Normalize: normalization with aggregate bandwidth 5484239360 bps ... 10.190.248.6 From: 10.190.248.1, State: Up, ActiveRoute: 0, LSPname: container-test-lsp-1 <<< Current container member lsp: container-test-lsp-1 ActivePath: (primary) Node/Link protection desired LSPtype: Dynamic Configured, Penultimate hop popping LoadBalance: Random Autobandwidth MinBW: 1000kbps, MaxBW: 1000Mbps AdjustTimer: 300 secs AdjustThreshold: 20% Max AvgBW util: 1.1697kbps, Bandwidth Adjustment in 91 second(s). Overflow limit: 4, Overflow sample count: 0 Underflow limit: 4, Underflow sample count: 2, Underflow Max AvgBW: 1.1697kbps Encoding type: Packet, Switching type: Packet, GPID: IPv4 *Primary State: Up Priorities: 3 3 Bandwidth: 1000kbps OptimizeTimer: 450 SmartOptimizeTimer: 180 Reoptimization in 81 second(s). Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 500) 10.190.249.29 S Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID): 10.190.248.6(flag=0x20) 10.190.249.29(Label=0) OAM state : BFD session up LSP-ping up 393 Sep 16 12:59:39.610 CSPF: computation result ignored, new path no benefit[4 times] 392 Sep 16 12:34:10.617 Make-before-break: Cleaned up old instance: Hold dead expiry 391 Sep 16 12:32:46.158 Link-protection Up 390 Sep 16 12:32:44.893 Make-before-break: Switched to new instance 389 Sep 16 12:32:44.892 Link-protection Down 388 Sep 16 12:32:44.890 Self-ping ended successfully 387 Sep 16 12:32:44.177 Record Route: 10.190.248.6(flag=0x20) 10.190.249.29(Label=0) 386 Sep 16 12:32:44.177 Up 385 Sep 16 12:32:44.177 Automatic Autobw adjustment succeeded: BW changes from 500000000 bps to 1000000 bps <<< Member LSP bandwidth 1Mbps
The reason for the "Avoid normalization: not needed as already running with max-members" message to get printed could be either of the following:
The container LSP is already running with configured max-members.
OR
The container is already running with the required (minimum) members for the sampled aggregate bandwidth. In the above example, the container-test-lsp, which has one member LSP (container-test-lsp-1) with a bandwidth of 1000 kbps, is already running with the "required max-members" for the Sampled Aggregate bandwidth: 1.16955 kbps.
Since this is expected behavior, nothing needs to be done to clear the message. Users need not take any action.