Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) - Manual (Page 147)

Multi-Service IronWare Switching Configuration Guide 117
53-1003036-02
Migrating from a pre-03.7.00 LAG or LACP configuration
5
Per packet server LAG load sharing
Per packet LAG load balancing is a type of LAG that load balances traffic on a per-packet basis, as
compared to traditional server LAG load-balancing which balances traffic based on packet content
such as source or destination addresses. In per packet server LAG load balancing, the packet
processor (PPCR) on each module selects a port in the per packet server LAG to forward traffic in a
round-robin fashion. For example, if the first port of the per packet server LAG is currently selected,
the second port of the per-packet server LAG will be used next, and so on. Consequently, traffic is
evenly distributed among all of the ports that are configured in a per packet server LAG.
Traffic that can be forwarded out of a per-packet LAG includes Layer 2 switching traffic, Layer 3
routing traffic, L3VPN (2547) traffic, VLL and VPLS traffic.
Migrating from a pre-03.7.00 LAG or LACP configuration
If you are upgrading from a version of the Multi-Service IronWare software prior to 03.7.00 and
have either LAGs or LACP configured, the previous configuration will be automatically updated with
the new commands to form an LAG that is equivalent to the previous configuration. To accomplish
this, the old LAG and link-aggregation commands are maintained during startup configuration
parsing, but disabled during normal configurations.
The following process is followed during the conversion of the LAG and link-aggregation to the new
LAG commands.
1. For any static LAG configured using the LAG ethernet slot/port to slot/port command, the
following conversion procedure is followed.
a. A static LAG is created containing the port list specified in the LAG command. This LAG is
then automatically deployed.
b. The lowest-numbered port from the original LAG list is selected as the primary port of the
LAG.
c. An LAG config--ind command, such as port name, is converted to the corresponding LAG
commands.
d. The default load balancing scheme previously known as server is converted to the default
hash-based load balancing scheme. Any LAG configured using the scheme previously
known as per-packet-server is converted to the per-packet load balancing scheme.
e. The converted LAG is named “LAG_x”, where “x” is a unique number assigned by the
system starting from 1.
2. For any dynamic link aggregation (LACP) group configured using the port-level link-aggregate
commands, the following conversion procedure is followed.
a. A dynamic LAG is created by grouping all ports in the original configuration having the
same link-aggregation key.
b. If link-aggregate active/passive is configured originally, the converted dynamic LAG is
configured as deployed, otherwise is not be converted because such ports were originally
not operating under LACP.
c. If the original mode is passive, the converted dynamic LAG will be configured as deploy
passive. Otherwise active mode is the default.