Brocade BigIron RX Series Configuration Guide - Manual (Page 376)

298 BigIron RX Series Configuration Guide
53-1002484-04
Configuring virtual routing interfaces
11
BigIron RX(config-vlan-3)# exit
BigIron RX(config)# interface ve 2
BigIron RX(config-ve-2)# ip address 10.1.1.1/24
BigIron RX(config-if-e1000-2/1)# exit
BigIron RX(config)# interface ve 3
BigIron RX(config-ve-3)# ip address 11.1.1.2/24
IP packets are bridged (switched) within the same protocol VLAN if they are on the same subnet;
they are routed if they are on a different VLAN.
Integrated Switch Routing (ISR)
Brocade Integrated Switch Routing (ISR) feature enables VLANs configured on the device to route
Layer 3 traffic from one protocol-based VLAN to another instead of forwarding the traffic to an
external router. The VLANs provide Layer 3 broadcast domains for the protocols, but do not in
themselves provide routing services. This is true even if the source and destination protocols are on
the same device.
ISR eliminates the need for an external router by allowing you to route between VLANs using virtual
routing interfaces (ves). You configure a separate virtual routing interface on each VLAN that you
want to use to route packets. For example, if you configure two IP protocol VLANs on a device, you
can configure a virtual routing interface on each of the IP protocol VLAN, then configure IP routing
parameters for the IP protocol VLAN. Thus, the device forwards IP broadcasts within each VLAN at
Layer 2 but routes Layer 3 traffic between the VLANs using the virtual routing interfaces.
NOTE
The device uses the lowest MAC address on the device (the MAC address of port 1/1) as the MAC
address for all ports within all virtual routing interfaces you configure on the device.
The routing parameters and the syntax for configuring them are the same as when you configure a
physical interface for routing (for example, interface ve 10). The logical interface allows the device
to internally route traffic between the protocol-based VLANs without using physical interfaces.
All the ports within a protocol-based VLAN must be in the same port-based VLAN. The
protocol-based VLAN cannot have ports in multiple port-based VLANs, unless the ports in the
port-based VLAN to which you add the protocol-based VLAN are 802.1q tagged.
You can configure multiple protocol-based VLANs within the same port-based VLAN. In addition, a
port within a port-based VLAN can belong to multiple protocol-based VLANs of the same type or
different types. For example, if you have a port-based VLAN that contains ports 1/1 – 1/10, you
can configure port 1/5 as a member of an AppleTalk protocol VLAN, an IP protocol VLAN, and an
IPX protocol VLAN, and so on.
If the router interface for IP is configured on physical ports, then routing occurs independent of the
Spanning Tree Protocol (STP). However, if the router interfaces are defined for IP VLAN, they are
virtual routing interfaces and are subject to the rules of STP.
If your backbone is consisted of virtual routing interfaces all within the same STP domain, it is a
bridged backbone, not a routed one. This means that the set of backbone interfaces that are
blocked by STP will be blocked for routed protocols as well. The routed protocols will be able to
cross these paths only when the STP state of the link is FORWARDING. This problem is easily
avoided by proper network design.