Cisco Systems EA6500 Manual De Usuario

For complete syntax and usage information for the commands used in this chapter, refer to the 
Catalyst 6500 Series Switch Cisco IOS Command Reference publication and the Release 12.1 
publications at this URL:

Release 12.1(13)E and later releases support configuration of 4,096 Layer 3 VLAN interfaces.

We recommend that you configure a combined total of no more than 2,000 Layer 3 VLAN 
interfaces and Layer 3 ports on an MSFC2 with either Supervisor Engine 1 or Supervisor 
Engine 2.

We recommend that you configure a combined total of no more than 1,000 Layer 3 VLAN 
interfaces and Layer 3 ports on an MSFC.

With releases earlier than Release 12.1(13)E, an MSFC2 with either Supervisor Engine 1 or 
Supervisor Engine 2 supports a combined maximum of 1,000 Layer 3 VLAN interfaces and Layer 3 
ports.

With releases earlier than Release 12.1(13)E, an MSFC with Supervisor Engine 1 supports a 
maximum of 256 Layer 3 VLAN interfaces.

To support VLAN interfaces, create and configure VLANs and assign VLAN membership to 
Layer 2 LAN ports. For more information, see 

Catalyst 6500 series switches support Layer 3 trunks only on the 4-port Gigabit Ethernet WAN 
modulea (OSM-4GE-WAN and OSM-2+4GE-WAN+). You cannot configure subinterfaces or use 
the encapsulation keyword on LAN ports. Catalyst  6500 series switches support Layer  2 trunks and 
Layer 3 VLAN interfaces, which provide equivalent capabilities for LAN ports. See 

 and the 

With Release 12.1(11b)E and later, when you are in configuration mode you can enter EXEC 
mode-level commands by entering the do keyword before the EXEC mode-level command.

For complete information and procedures, refer to these publications:

Cisco IOS IP and IP Routing Configuration Guide, Release 12.1, at this URL:

Cisco IOS IP and IP Routing Command Reference, Release 12.1, at this URL:

For information about the maximum paths command in Release 12.1 E, refer to the Catalyst 6500 
Series Switch Cisco IOS Command Reference publication. 

The Policy Feature Card 2 (PFC2) and any Distributed Feature Cards (DFCs) provide hardware support 
for policy-based routing (PBR) for route-map sequences that use the match ip address and set ip 
next-hop keywords. 

With Release 12.1(11b)E and later, the PFC2 and any DFCs provide hardware support for the ip default 
next-hop PBR keywords.