request interface rebalance (Aggregated Ethernet for Subscriber Management)
Syntax
request interface rebalance interface interface-name
Description
Manually rebalance the subscribers on an aggregated Ethernet bundle with targeted distribution enabled. For example, when you add a new member link to an existing aggregated Ethernet interface, you might want to rebalance the subscribers across the new member link.
Options
interface-name |
Aggregated Ethernet logical interface number. |
Additional Information
The targeted-distribution statement in a dynamic profile automatically distributes subscribers to the aggregated Ethernet links associated with the profile. If you apply the profile and then bring up a single link on an aggregated Ethernet interface, all newly connected subscribers are located on that single, active link.
When you then bring up a second link on the aggregated Ethernet interface, you can use the request interface rebalance interface command to rebalance the existing subscribers so that some remain on the first link and others are redistributed to the second link.
In some cases, it might appear that rebalancing does not work. By default, the router rebalances the subscribers only when the difference in subscriber numbers on the member links is greater than 500. This number is the default threshold for subscriber granularity.
Consider the following cases with two member links on the interface:
Case 1—One link has 300 subscribers and the other link has 10 subscribers. Issuing the command does not rebalance the subscribers because the difference between the links is only 290.
Case 2—One link has 530 subscribers and the other link has 10 subscribers. The difference between the links is 520 subscribers. Issuing the command rebalances the subscribers so that 500 subscribers are on one link and 40 subscribers are on the other link.
You can modify the subscriber granularity with the rebalance-subscriber-granularity option at the [edit interfaces ae.interface-number aggregated-ether-options aggregated-ether-options] hierarchy level. For example, if you set the granularity to 1 subscriber, then rebalancing always takes place when the member links differ by 2 or more subscribers.
We recommend that you do not configure a low granularity value. A low value can have undesirable effects, such as the router running out of pseudo logical interfaces or an increase in the convergence time for rebalancing.
Leaving subscriber granularity at the default value of 500 subscribers is sufficient in most cases. Whenever more than one member link is active, targeted distribution places new subscribers on a link with fewer subscribers than other member links on the interface.
Required Privilege Level
view
Output Fields
When you enter this command, you are provided feedback on the status of your request. You can compare the output of the show interfaces targeting command before and after the request to view the effect of the rebalancing operation. .
Sample Output
- request interface rebalance (Adding a New Link)
- request interface rebalance (Rebalancing Two Existing Links)
request interface rebalance (Adding a New Link)
user@host >show interfaces targeting ae0 Aggregated interface: ae0 Targeting Type: Auto Redundancy mode: Link Level Redundancy Total number of distribution groups: 1 Total number of distributed interfaces: 1000 Distribution Group name: default Number of distributed interfaces: 1000 Physical interface: xe-0/2/0, Link status: Up Number of primary distributions: 1000 /*All subscribers are distributed on this active link*/ Number of backup distributions: 0 Physical interface: xe-0/2/1, Link status: Down /*This link is inactive*/ Number of primary distributions: 0 /*No subscribers*/ Number of backup distributions: 1000 user@host >request interface rebalance interface ae0 (After Link xe-0/2/1 is Activated) Rebalance operation on interface ae0 started user@host >show interfaces targeting ae0 Aggregated interface: ae0 Targeting Type: Auto Redundancy mode: Link Level Redundancy Total number of distribution groups: 1 Total number of distributed interfaces: 1000 Distribution Group name: default Number of distributed interfaces: 1000 Physical interface: xe-0/2/0, Link status: Up Number of primary distributions: 500 /*500 subscribers were redistributed from this link*/ Number of backup distributions: 500 Physical interface: xe-0/2/1, Link status: Up /*member link is now active*/ Number of primary distributions: 500 /*500 subscribers were redistributed to this newly active member link*/ Number of backup distributions: 500
request interface rebalance (Rebalancing Two Existing Links)
user@host >show interfaces targeting ae0 Aggregated interface: ae0 Targeting Type: Auto Redundancy mode: Link Level Redundancy Total number of distribution groups: 1 Total number of distributed interfaces: 540 Distribution Group name: default Number of distributed interfaces: 540 Physical interface: xe-0/2/0, Link status: Up Number of primary distributions: 530 /*This interface has 520 more subscribers than the other*/ Number of backup distributions: 10 Physical interface: xe-0/2/1, Link status: Up Number of primary distributions: 10 Number of backup distributions: 530 user@host >request interface rebalance interface ae0 Rebalance operation on interface ae0 started user@host >show interfaces targeting ae0 Aggregated interface: ae0 Targeting Type: Auto Redundancy mode: Link Level Redundancy Total number of distribution groups: 1 Total number of distributed interfaces: 540 Distribution Group name: default Number of distributed interfaces: 540 Physical interface: xe-0/2/0, Link status: Up Number of primary distributions: 500 /*30 subscribers were redistributed from this link*/ Number of backup distributions: 40 Physical interface: xe-0/2/1, Link status: Up Number of primary distributions: 40 /*30 subscribers were redistributed to the link with fewer subscribers*/ Number of backup distributions: 500
Release Information
Command introduced in Junos OS Release 11.2.