Routed Ports - Cisco Catalyst 3560-X Software Configuration Manual
Hide thumbs
Also See for Catalyst 3560-X:
- Command reference manual (1188 pages) ,
- Software configuration manual (1438 pages) ,
- Manual (276 pages)
Table of Contents
Advertisement
Interface Types
Trunk Ports
A trunk port carries the traffic of multiple VLANs and by default is a member of all VLANs in the VLAN
database. These trunk port types are supported:
•
•
Although by default, a trunk port is a member of every VLAN known to the VTP, you can limit VLAN
membership 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 possible VLANs (VLAN ID 1
to 4094) are in the allowed list. A trunk port can become a member of a VLAN only if VTP knows of
the VLAN and if the VLAN is in the enabled state. If VTP learns of a new, enabled VLAN and the VLAN
is in the allowed list for a trunk port, the trunk port automatically becomes a member of that VLAN and
traffic is forwarded to and from the trunk port for that VLAN. If VTP learns of a new, enabled VLAN
that is not in the allowed list for a trunk port, the port does not become a member of the VLAN, and no
traffic for the VLAN is forwarded to or from the port.
For more information about trunk ports, see
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 same VLAN number. 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 are
IEEE 802.1Q-tagged with the customer VLANs are encapsulated with another layer of an IEEE 802.1Q
tag (called the metro tag), which contains 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, also a tunnel port,
the metro tag is removed, and the original VLAN numbers from the customer network are retrieved.
Tunnel ports cannot be trunk ports or access ports and must belong to a VLAN unique to each customer.
For more information about tunnel ports, see
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 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 DTP and STP.
Catalyst 3750-X and 3560-X Switch Software Configuration Guide
1-4
In an ISL trunk port, all received packets are expected to be encapsulated with an ISL header, and
all transmitted packets are sent with an ISL header. Native (non-tagged) frames received from an
ISL trunk port are dropped.
An IEEE 802.1Q trunk port supports simultaneous tagged and untagged traffic. 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.
Chapter 1
Chapter 1, "Configuring VLANs."
Chapter 1, "Configuring IEEE 802.1Q and Layer 2
Configuring Interface Characteristics
OL-25303-03
Advertisement
Table of Contents
Troubleshooting
