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

608 Multi-Service IronWare Switching Configuration Guide
53-1003036-02
About Multi-Chassis Trunk (MCT)
18
3. The primary port must be explicitly assigned using the primary-port command.
Brocade(config-lag-3)# primary-port 1/5
4. Deploy the LAG 3 as shown below.
Brocade(config-lag-3)# deploy
5. Assign a name to an individual port within a LAG.
Brocade(config-lag-2)# port-name lag-client-2:1/1 ethernet 1/5
Brocade(config-lag-2)# port-name lag-client-1:1/2 ethernet 1/4
Enable layer 2 switching
1. By default, Brocade devices support routing over layer 2 switching. You can enable layer 2
switching globally or on individual port using the no route-only command. The no route-only
and route-only commands prompts you for whether or not you want to change the “route-only”
behavior. You must enter y if you want to proceed or n if you do not. To enable Layer 2 switching
only on a specific interface, go to the interface configuration level for that interface, and add
the no route-only command.
NOTE
On the Brocade NetIron XMR and Brocade MLX series routers, route-only is the default
condition. Because route-only is the default condition, it will not be displayed in the
configuration. If you use no route-only to enable switching, the no route-only command will be
displayed in the configuration.
NOTE
On the Brocade NetIron CES and Brocade NetIron CER devices, route-only is disabled by
default. Therefore, if route-only is enabled on a Brocade NetIron CES or Brocade NetIron CER
device, it will be displayed in the configuration.
NOTE
In CES/CER, if route-only is configured on a tagged/dual-mode interface, the configuration
takes effect only when the interface becomes a strictly untagged interface. The following
warning message is dispalyed in this scenario. "Configuration is valid for a tagged/dual-mode
port when it becomes strictly untagged in regular vlan (in default esi)”.
Use commands such as the following to enable Layer 2 switching.
Brocade(config)# no route-only
Syntax: [no] route-only
Creating VLANs for client traffic
See
Figure 176 and “Creating LAG-1” for additional information on creating VLANs.
Creating VLANs for client traffic
1. At the global CONFIG level assign an ID to the VLAN.
Brocade(config)# vlan 2
2. Add the client ports to the VLAN as either tagged or untagged. In this example the client ports
are untagged.