Routed Ports; Switch Virtual Interfaces; Etherchannel Port Groups - Cisco IE-4000 Software Configuration Manual

Configuring Interfaces
Understanding Interface Types
Note: IEEE 802.1Q tunneling is only supported when the switch is running the IP Services license.
Tunnel ports cannot be trunk ports or access ports and must belong to a VLAN unique to each customer.

Routed Ports

A routed port is a physical port that acts like a port on a router; it does not have to be connected to a router. A routed
port is not associated with a particular VLAN, as is an access port. A routed port behaves like a regular router interface,
except that it does not support VLAN subinterfaces. Routed ports can be configured with a Layer 3 routing protocol. A
routed port is a Layer 3 interface only and does not support Layer 2 protocols, such as STP.
Configure routed ports by putting the interface into Layer 3 mode with the no switchport interface configuration
command. Then assign an IP address to the port, enable routing, and assign routing protocol characteristics by using the
ip routing and router protocol global configuration commands.
Note: Entering a no switchport interface configuration command shuts down the interface and then re-enables it, which
might generate messages on the device to which the interface is connected. When you put an interface that is in Layer
2 mode into Layer 3 mode, the previous configuration information related to the affected interface might be lost.
The number of routed ports that you can configure is not limited by software. However, the interrelationship between this
number and the number of other features being configured might impact CPU performance because of hardware
limitations. See Configuring Layer 3 Interfaces, page 42
limitations are reached.
Note: For full Layer 3 routing, you must have the IP services image installed on the switch

Switch Virtual Interfaces

A switch virtual interface (SVI) represents a VLAN of switch ports as one interface to the routing or bridging function in
the system. Only one SVI can be associated with a VLAN, but you need to configure an SVI for a VLAN only when you
wish to route between VLANs or to provide IP host connectivity to the switch. By default, an SVI is created for the default
VLAN (VLAN 1) to permit remote switch administration. Additional SVIs must be explicitly configured.
Note: You cannot delete interface VLAN 1.
SVIs provide IP host connectivity only to the system; in Layer 3 mode, you can configure routing across SVIs.
Although the switch supports a total of 1005 VLANs (and SVIs), the interrelationship between the number of SVIs and
routed ports and the number of other features being configured might impact CPU performance because of hardware
limitations. See Configuring Layer 3 Interfaces, page 42
limitations are reached.
SVIs are created the first time that you enter the vlan interface configuration command for a VLAN interface. The VLAN
corresponds to the VLAN tag associated with data frames on an IEEE 802.1Q encapsulated trunk or the VLAN ID
configured for an access port. Configure a VLAN interface for each VLAN for which you want to route traffic, and assign
it an IP address. For more information, see
Note: When you create an SVI, it does not become active until it is associated with a physical port.
SVIs support routing protocols.
Note: Routed ports (or SVIs) are supported only when the IP services image is installed on the switch.

EtherChannel Port Groups

EtherChannel port groups treat multiple switch ports as one switch port. These port groups act as a single logical port
for high-bandwidth connections between switches or between switches and servers. An EtherChannel balances the
traffic load across the links in the channel. If a link within the EtherChannel fails, traffic previously carried over the failed
link changes to the remaining links. You can group multiple trunk ports into one logical trunk port, group multiple access
for information about what happens when hardware resource
for information about what happens when hardware resource
Manually Assigning IP Information to SVIs, page
20
71.