- I expected that if we apply cir-rate of 4000000000 bps (Up to 4000 Mbits/Sec) to port-channel, the TX,RX limit of port-channel is 4000 Mbits/Sec.
- However, the TX,RX limit for this port-channel is 8000 Mbits/Sec.
Not sure if my previous response was clear. As mentioned, the port-channel configuration is a global configuration that both RB 1 and RB 2 are part of. However, each RB handles it’s traffic locally when it’s received.
For example, both RBs receives traffic, since each RB has a port which are part of PO 34, each will RX,TX max of 4000 Mbit/sec according to the cir-rate. If you have another port added which connect to RB1 or RB2, then it will be split among those ports which are locally on the same RB.
- If this is normal, we will apply a cir-rate of 2000000000 bps (Up to 2000 Mbits/Sec) to port-channel and expect a TX,RX limit of 4000 Mbits/Sec
If you are looking to limit only 2000 Mbits/Sec to each interface on PO 34 which only has 2 interfaces that are part of RB1 and RB2, then setting the cir-rate to 2000000000 bps is correct.
According to what you mentioned, there is no difference in the cir-rate limit depending on the protocol type of the port channel. (vLag, LACP)
For example, even if only port-channel protocol was changed to LACP in the configuration that I initially shared, the port-channel TX,RX limit would be 8000 Mbits/Sec just like vLag. (The TX,RX limit of the two physical interfaces is 4000 Mbits/Sec)
Is this understanding correct?
vLAG just means that the port-channel is connected/configured to multiple (different) R-Bridges. In this case, RB 1 and RB 2. Logically, RB 1 and RB 2 form the vLAG which talks LACP protocol for the port-channel. So, technically, you are already configured for both as a vLAG to use LACP protocol.
Hope that clears it up a bit.