PXC sub-ports can be aggregated into a PXC LAG for increased capacity and card redundancy.A logical concept of a PXC LAG is shown in Figure 1.
Although the configuration allows for a mix of port-based PXCs and MAC-based PXCs in a LAG, the configuration should be used in a production network only during a short migration period when transitioning from one type of PXC to the other. Outside of the migration, the PXCs in a LAG should be of the same type, for example, a LAG should contain only port-based PXCs or only MAC-based PXCs but not both.
The LAGs on PXC ports must be configured in pairs as shown in this example:
MD-CLI
configure {
lag 1 {
description ‟lag in the up direction”
port pxc-1.a {
}
port pxc-2.a {
}
}
lag 2 {
description ‟lag in the down direction”
port pxc-1.b {
}
port pxc-2.b {
}
}
}
Within the router, the two sides of the PXC LAG (LAG 1 and LAG 2 in the example configuration) are not aware of their interconnection. As a result, the operational state of one side of the PXC LAG is not influenced by the state of the PXC LAG on the other side.
PXC sub-ports in a LAG must have the same properties (such as the same speed). Mixing PXC sub-ports and non-PXC ports is not allowed. The first port added to a LAG determines the type of LAG (PXC or non-PXC).
Statistics in the output of the show lag id statistics command represent combined traffic carried over the referenced lag id and its pair (lag 1 and lag 2 in the above example).