9-4
Cisco ME 3400 EthernetAccess Switch SoftwareConfiguration Guide
78-17058-01
Chapter9 Configuring Interface Characteristics
Understanding Interface Types
they are enabled. Dynamic access ports on the switch are assigned to a VLAN by a VLAN
Membership Policy Server (VMPS). The VMPS can be a Catalyst 6500 series switch; the Cisco ME
switch cannot be a VMPS server. Dynamic access ports for VMPS are only supported on UNIs.

Trunk Ports

An IEEE 802.1Q trunk port carries the traffic of multiple VLANs and by default is a member of all
VLANs in the VLAN database. A trunk port supports simultaneou s t agge d an d u nt agge d tr affic. An
IEEE 802.1Q trunk port is assigned a default Port VLAN ID (PVID), and all untagged traffic travels on
the port default PVID. All untagged traffic and tagged traffic with a NULL VLAN ID are assumed to
belong to the port default PVID. A packet with a VLAN ID equal to the outgoing port default PVID is
sent untagged. All other traffic is sent with a VLAN tag.
Although by default a trunk port is a member of multiple VLANs, you can limit VLAN me mbe rship by
configuring an allowed list of VLANs for each trunk port. The list of allowed VLANs does not affect
any other port but the associated trunk port. By default, all po ssible V LAN s ( VLA N I D 1 to 4094) a r e
in the allowed list. A trunk port can become a member of a VLAN only if the VLAN is in the enabled
state.
For more information about trunk ports, see Chapter 1 1, “Configu ring VLAN s.”

Tunnel Ports

Tunnel ports are used in IEEE 802.1Q tunneling to segregate the traffic of customers in a
service-provider network from other customers who are using the sam e V LAN n um ber. You configure
an asymmetric link from a tunnel port on a service-provider edge switch to an IEEE 802.1Q trunk port
on the customer switch. Packets entering the tunnel port on the edge switch, already
IEEE802.1Q-tagged with the customer VLANs, are encapsulated with another layer of an IEEE 802.1Q
tag (called the metro tag), containing a VLAN ID unique in the service-provider network, for each
customer. The double-tagged packets go through the service-provider network keeping the original
customer VLANs separate from those of other customers. At the outbound interface, al so a tunnel port,
the metro tag is removed, and the original VLAN numbers from the customer network are retrieved.
Note IEEE 802.1Q tunneling is only supported when the switch is run ning the metro IP access or metro access
image.
Tunnel ports cannot be trunk ports or access ports and must belong to a VLAN unique to each cu stomer.
For more information about tunnel ports, see Chapter 13, “ Configuring IE EE 802.1Q and Layer 2
Protocol Tunneling.”
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 a n access port. A routed port behaves
like a regular router interface, except that it does not support VLAN subinterface s . R outed ports can be
configured with a Layer 3 routing protocol. A routed port is a Layer 3 interface only and does not supp ort
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, enabl e ro ut ing, and assi gn rout ing
protocol characteristics by using the ip routing and router protocol global configuration commands.