Table Of Contents
Configuring IPX Multilayer Switching
Finding Feature Information
Contents
Prerequisites for Configuring IPX Multilayer Switching
Restrictions for Configuring IPX Multilayer Switching
General Configuration Restrictions and Guidelines
External Router Restrictions and Guidelines
Access List Restrictions
Interaction of IPX MLS with Other Features
Maximum Transmission Unit Size Restrictions
Information About IPX Multilayer Switching
How to Configure IPX MLS
Assigning an IPX MLS Interface to a VTP Domain
Prerequisite
Enabling Multilayer Switching Protocol (MLSP) on the Router
Assigning a VLAN ID to a Router Interface
Enabling IPX MLS on a Router Interface
Specifying a Router Interface As a Management Interface
Verifying IPX MLS on the Router
Monitoring and Maintaining IPX MLS on the Router
Troubleshooting Tips for Configuring IPX MLS
Configuration Examples for IPX MLS
IPX MLS Network Topology: Example
Operation Before IPX MLS: Example
Operation After IPX MLS: Example
Switch A Configuration: Example
Switch B Configuration: Example
Switch C Configuration: Example
MLS-RP Configuration: Example
Additional References
Related Documents
Standards
MIBs
RFCs
Technical Assistance
Feature Information for Configuring IPX MLS
Configuring IPX Multilayer Switching
This module describes how to configure IPX Multilayer Switching (MLS).
Note
This module is a brief summary of the information contained in the Catalyst 5000 Series Multilayer Switching User Guide. The commands and configurations described in this guide apply only to the devices that provide routing services. Commands and configurations for Catalyst 5000 series switches are documented in the Catalyst 5000 Series Multilayer Switching User Guide and the Catalyst 5000 Series Software Configuration Guide. For configuration information for the Catalyst 6000 series switch, see Configuring and Troubleshooting IP MLS on Catalyst 6500/6000 Switches with an MSFC document or see the "Configuring IP Multilayer Layer 3 Switching" chapter in the Catalyst 6500 Series Switch Cisco IOS Software Configuration Guide.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Configuring IPX MLS" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for Configuring IPX Multilayer Switching
•
Restrictions for Configuring IPX Multilayer Switching
•
Information About IPX Multilayer Switching
•
How to Configure IPX MLS
•
Troubleshooting Tips for Configuring IPX MLS
•
Additional References
•
Feature Information for Configuring IPX MLS
Prerequisites for Configuring IPX Multilayer Switching
The following prerequisites must be met before IPX MLS can function:
•
A VLAN interface must be configured on both the switch and the router. For information on configuring inter-VLAN routing on the Route Switch Module (RSM) or an external router, see the Catalyst 5000 Series Software Configuration Guide or the Catalyst 6500 Series Switch Cisco IOS Software Configuration Guide.
•
IPX MLS must be configured on the switch. For more information, see the Catalyst 5000 Series Software Configuration Guide, the Catalyst 6500 Series Switch Cisco IOS Software Configuration Guide, the Catalyst 5000 Family Command Reference or the Catalyst 6500 Series Command Reference.
•
IPX MLS must be enabled on the router. The minimal configuration steps are described in the "How to Configure IPX MLS" section in this module. For more details on configuring IPX routing, see the "Configuring Novell IPX" module of the Cisco IOS Novell IPX Configuration Guide.
Restrictions for Configuring IPX Multilayer Switching
This section describes the following restrictions and guidelines:
•
General Configuration Restrictions and Guidelines
•
External Router Restrictions and Guidelines
•
Access List Restrictions
•
Interaction of IPX MLS with Other Features
•
Maximum Transmission Unit Size Restrictions
General Configuration Restrictions and Guidelines
Be aware of the following restrictions:
•
You must configure the Catalyst switch for IPX MLS to work.
•
When you enable IPX MLS, the RSM or externally attached router continues to handle all non-IPX protocols, while offloading the switching of IPX packets to the MLS-SE.
•
Do not confuse IPX MLS with NetFlow switching supported by Cisco routers. IPX MLS requires both the RSM or directly attached external router and the MLS-SE, but not NetFlow switching on the RSM or directly attached external router. Any switching path on the RSM or directly attached external router will function (process, fast, optimum, and so on).
External Router Restrictions and Guidelines
When using an external router, use the following guidelines:
•
Use one directly attached external router per switch to ensure that the MLS-SE caches the appropriate flow information from both sides of the routed flow.
•
Use Cisco high-end routers (Cisco 4500, 4700, 7200, and 7500 series) for IPX MLS when they are externally attached to the switch. Make the attachment with multiple Ethernet connections (one per subnet) or by using Fast or Gigabit Ethernet with Inter-Switch Link (ISL) or IEEE 802.1Q encapsulation.
•
Connect end hosts through any media (Ethernet, Fast Ethernet, ATM, and FDDI), but connect the external router and the switch only through standard 10/100 Ethernet interfaces, ISL, or IEEE 802.1Q links.
Access List Restrictions
The following restrictions apply when you use access lists on interfaces that participate in IPX MLS:
•
Input access lists—Router interfaces with input access lists cannot participate in IPX MLS. If you configure an input access list on an interface, no packets inbound or outbound for that interface are Layer 3 switched, even if the flow is not filtered by the access list. Existing flows for that interface are purged, and no new flows are cached.
Note
You can translate input access lists to output access lists to provide the same effect on the interface.
•
Output access lists—When an output access list is applied to an interface, the IPX MLS cache entries for that interface are purged. Entries associated with other interfaces are not affected; they follow their normal aging or purging procedures.
Applying access lists that filter according to packet type, source node, source socket, or destination socket prevents the interface from participating in IPX MLS.
Applying access lists that use the log option prevents the interface from participating in IPX MLS.
•
Access list impact on flow masks—Access lists impact the flow mask mode advertised to the MLS-SE by an MLS-RP. If no access list has been applied on any MLS-RP interface, the flow mask mode is destination-ipx (the least specific) by default. If an access list that filters according to the source IPX network has been applied, the mode is source-destination-ipx by default.
Interaction of IPX MLS with Other Features
IPX MLS affects other Cisco IOS software features as follows:
•
IPX accounting—IPX accounting cannot be enabled on an IPX MLS-enabled interface.
•
IPX EIGRP—MLS is supported for EIGRP interfaces if the Transport Control (TC) maximum is set to a value greater than the default (16).
Maximum Transmission Unit Size Restrictions
In IPX, the two endpoints of communication negotiate the maximum transmission unit (MTU) to be used. MTU size is limited by media type.
Information About IPX Multilayer Switching
The IPX MLS feature provides high-performance, hardware-based, Layer 3 switching for LAN switches. IPX data packet flows are switched between networks, off loading processor-intensive packet routing from network routers.
Whenever a partial or complete switched path exists between two hosts, packet forwarding occurs on Layer 3 switches. Packets without such a partial or complete switched path are still forwarded by routers to their destinations. Standard routing protocols such as RIP, Enhanced IGRP, and NetWare Link Services Protocol (NLSP) are used for route determination.
IPX MLS also allows you to debug and trace flows in your network. Use MLS explorer packets to identify which switch is handling a particular flow. These packets aid you in path detection and troubleshooting.
For conceptual information about IPX Multilayer Switching, see the "Multilayer Switching Overview" module.
How to Configure IPX MLS
To configure one or more routers for IPX MLS, perform the tasks described in the following sections. The number of tasks you perform depends on your particular configuration.
•
Assigning an IPX MLS Interface to a VTP Domain (Optional)
•
Enabling Multilayer Switching Protocol (MLSP) on the Router (Required)
•
Assigning a VLAN ID to a Router Interface (Optional)
•
Enabling IPX MLS on a Router Interface (Required)
•
Specifying a Router Interface As a Management Interface (Required)
•
Verifying IPX MLS on the Router (Optional)
•
Monitoring and Maintaining IPX MLS on the Router (Optional)
Assigning an IPX MLS Interface to a VTP Domain
Prerequisite
Determine which router interfaces you will use as IPX MLS interfaces and add them to the same VTP domain as the switches.
To view the VTP configuration and its domain name on the switch, enter the show mls rp vtp-domain EXEC command at the switch Console> prompt.
To assign an MLS interface to a specific VTP domain on the MLS-RP, complete the following steps.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface type number
4.
mls rp vtp-domain domain-name
5.
end
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
interface type number
Example:
Router(config)# interface fastethernet 2/0.1
|
Selects an interface and enters interface configuration mode.
• Enter the interface type and interface number.
|
Step 4
|
mls rp vtp-domain domain-name
Example:
Router(config-if)# mls rp vtp-domain
Engineering
|
Adds an IPX MLS interface to a VTP domain.
• Enter the domain name.
|
Step 5
|
end
Example:
Router(config-if)# end
|
Exits interface configuration mode.
|
DETAILED STEPS
Enabling Multilayer Switching Protocol (MLSP) on the Router
To enable MLSP on the router, complete the following steps.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
mls rp ipx
4.
end
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
mls rp ipx
Example:
Router(config)# mls rp ipx
|
Globally enables MLSP on the router. MLSP is the protocol that runs between the MLS-SE and MLS-RP.
|
Step 4
|
end
Example:
Router(config)# end
|
Exits global configuration mode.
|
DETAILED STEPS
Assigning a VLAN ID to a Router Interface
Note
This task is not required for RSM VLAN interfaces (virtual interfaces), ISL-encapsulated interfaces, or IEEE 802.1Q-encapsulated interfaces.
To assign a VLAN ID to an IPX MLS interface, complete the following steps.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface type number
4.
mls rp vlan-id vlan-id-number
5.
end
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
interface type number
Example:
Router(config)# interface fastethernet2/0.1
|
Selects an interface and enters interface configuration mode.
• Enter the interface type and interface number.
|
Step 4
|
mls rp vlan-id vlan-id-number
Example:
Router(config-if)# mls rp vlan-id 23
|
Assigns a VLAN ID to an IPX MLS interface. The assigned IPX MLS interface must be either an Ethernet or Fast Ethernet interface with no subinterfaces.
• Enter the VLAN number.
|
Step 5
|
end
Example:
Router(config-if)# end
|
Exits interface configuration mode.
|
DETAILED STEPS
Enabling IPX MLS on a Router Interface
To enable IPX MLS on a router interface, complete the following steps.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface type number
4.
mls rp ipx
5.
end
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
interface type number
Example:
Router(config)# interface fastethernet2/0.1
|
Selects an interface and enters interface configuration mode.
• Enter the interface type and interface number.
|
Step 4
|
mls rp ipx
Example:
Router(config-if)# mls rp ipx
|
Enables a router interface for IPX MLS.
|
Step 5
|
end
Example:
Router(config-if)# end
|
Exits interface configuration mode.
|
DETAILED STEPS
Specifying a Router Interface As a Management Interface
To specify a router interface as the management interface, complete the following steps.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface type number
4.
mls rp management-interface
5.
end
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
interface type number
Example:
Router(config)# interface fastethernet 2/0.1
|
Configures an interface and enters interface configuration mode.
• Enter the interface type and interface number.
|
Step 4
|
mls rp management-interface
Example:
Router(config-if)# mls rp management-interface
|
Specifies an interface as the management interface. MLSP packets are sent and received through the management interface. Select only one IPX MLS interface connected to the switch.
|
Step 5
|
end
Example:
Router(config-if)# end
|
Exits interface configuration mode.
|
DETAILED STEPS
Verifying IPX MLS on the Router
To verify that you have correctly installed IPX MLS on the router, complete the following steps:
Step 1
Enter the show mls rp ipx EXEC command.
Step 2
Examine the output to learn if the VLANs are enabled.
Step 3
Examine the output to learn if the switches are listed by MAC address, indicating they are recognized by the MLS-RP.
Monitoring and Maintaining IPX MLS on the Router
To monitor and maintain IPX MLS on the router, use one or more of the following commands.
SUMMARY STEPS
1.
enable
2.
mls rp locate ipx
3.
show mls rp interface type number
4.
show mls rp ipx
5.
show mls rp vtp-domain domain-name
6.
end
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
mls rp locate ipx
Example:
Router# mls rp locate ipx
|
Displays information about all switches currently shortcutting for the specified IPX flow(s).
|
Step 3
|
show mls rp interface type number
Example:
Router# show mls rp interface fastethernet 2/0.1
|
Displays MLS details for a specific interface.
• Enter the interface type and interface number.
|
Step 4
|
show mls rp ipx
Example:
Router# show mls rp ipx
|
Displays details for all IPX MLS interfaces on the router, such as the following:
• MLS status (enabled or disabled) for switch interfaces and subinterfaces.
• Flow mask required when creating Layer 3 switching entries for the router.
• Current settings for the keepalive timer, retry timer, and retry count.
• MLSP-ID used in MLSP messages.
• List of interfaces in all VTP domains enabled for MLS.
|
Step 5
|
show mls rp vtp-domain domain-name
Example:
Router# show mls rp vtp-domain engineering
|
Displays details about IPX MLS interfaces for a specific VTP domain.
• Enter the domain name.
|
Step 6
|
end
Example:
Router# end
|
Exits privileged EXEC mode.
|
DETAILED STEPS
Troubleshooting Tips for Configuring IPX MLS
If you entered either the mls rp ipx command or the mls rp management-interface command on the interface before assigning it to a VTP domain, the interface will be in the null domain, instead of the VTP domain.
To remove the interface from the null domain and add it to a new VTP domain, complete the following steps.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface type number
4.
no mls rp ipx
5.
no mls rp management-interface
6.
no mls rp vtp-domain domain-name
7.
mls rp vtp-domain domain-name
8.
end
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
interface type number
Example:
Router(config)# interface fastethernet 2/0.1
|
Configures an interface and enters interface configuration mode.
• Enter the interface type and interface number.
|
Step 4
|
no mls rp ipx
Example:
Router(config-if)# no mls rp ipx
|
Disables MLS IPX on a router interface.
|
Step 5
|
no mls rp management-interface
Example:
Router(config-if)# no mls rp management-interface
|
Removes an interface as the management interface.
|
Step 6
|
no mls rp vtp-domain domain-name
Example:
Router(config-if)# no mls rp vtp-domain Engineering
|
Removes a VTP domain.
• Enter the domain name.
|
Step 7
|
mls rp vtp-domain domain-name
Example:
Router(config-if)# mls rp vtp-domain Development
|
Adds the interface to a new VTP domain.
• Enter the domain name.
|
Step 8
|
end
Example:
Router(config-if)# end
|
Exits interface configuration mode.
|
DETAILED STEPS
Configuration Examples for IPX MLS
Note
This, even though switch commands are not documented in this module. See the Catalyst 5000 Family Command Reference or the Catalyst 6500 Series Command Reference for more information.
This example consists of the following sections:
•
IPX MLS Network Topology: Example
•
Operation Before IPX MLS: Example
•
Operation After IPX MLS: Example
•
Switch A Configuration: Example
•
Switch B Configuration: Example
•
Switch C Configuration: Example
•
MLS-RP Configuration: Example
•
Router with No Access Lists Configuration: Example, page 16
•
Configuring a Router with a Standard Access List: Example, page 17
IPX MLS Network Topology: Example
Figure 1 shows an IPX MLS network topology consisting of three Catalyst 5000 series switches and a Cisco 7505 router—all interconnected with ISL trunk links.
Figure 1 Example Network: IPX MLS with Cisco 7505 over ISL
The network is configured as follows:
•
There are four VLANs (IPX networks):
–
VLAN 1 (management VLAN), IPX network 1
–
VLAN 10, IPX network 10
–
VLAN 20, IPX network 20
–
VLAN 30, IPX network 30
•
The MLS-RP is a Cisco 7505 router with a Fast Ethernet interface (interface fastethernet2/0)
•
The subinterfaces on the router interface have the following IPX network addresses:
–
fastethernet2/0.1-IPX network 1
–
fastethernet2/0.10-IPX network 10
–
fastethernet2/0.20-IPX network 20
–
fastethernet2/0.30-IPX network 30
•
Switch A, the MLS-SE VTP server, is a Catalyst 5509 switch with Supervisor Engine III and the NFFC II.
•
Switch B and Switch C are VTP client Catalyst 5505 switches.
Operation Before IPX MLS: Example
Before IPX MLS is implemented, when the source host NC1 (on VLAN 10) sends traffic destined for destination server NS2 (on VLAN 30), Switch B forwards the traffic (based on the Layer 2 forwarding table) to Switch A over the ISL trunk link. Switch A forwards the packet to the router over the ISL trunk link.
The router receives the packet on the VLAN 10 subinterface, checks the destination IPX address, and routes the packet to the VLAN 30 subinterface. Switch A receives the routed packet and forwards it to Switch C. Switch C receives the packet and forwards it to destination server NS2. This process is repeated for each packet in the flow between source host NC1 and destination server NS2.
Operation After IPX MLS: Example
After IPX MLS is implemented, when the source host NC1 (on VLAN 10) sends traffic destined for destination server NS2 (on VLAN 30), Switch B forwards the traffic (based on the Layer 2 forwarding table) to Switch A (the MLS-SE) over the ISL trunk link. When the first packet enters Switch A, a candidate flow entry is established in the MLS cache. Switch A forwards the packet to the MLS-RP over the ISL trunk link.
The MLS-RP receives the packet on the VLAN 10 subinterface, checks the destination IPX address, and routes the packet to the VLAN 30 subinterface. Switch A receives the routed packet (the enabler packet) and completes the flow entry in the MLS cache for the destination IPX address of NS2. Switch A forwards the packet to Switch C, where it is forwarded to destination server NS2.
Subsequent packets destined for the IPX address of NS2 are multilayer switched by the MLS-SE based on the flow entry in the MLS cache. For example, subsequent packets in the flow from source host NC1 are forwarded by Switch B to Switch A (the MLS-SE). The MLS-SE determines that the packets are part of the established flow, rewrites the packet headers, and switches the packets directly to Switch C, bypassing the router.
Switch A Configuration: Example
This example shows how to configure Switch A (MLS-SE):
SwitchA> (enable) set vtp domain Corporate mode server
VTP domain Corporate modified
SwitchA> (enable) set vlan 10
Vlan 10 configuration successful
SwitchA> (enable) set vlan 20
Vlan 20 configuration successful
SwitchA> (enable) set vlan 30
Vlan 30 configuration successful
SwitchA> (enable) set port name 1/1 Router Link
SwitchA> (enable) set trunk 1/1 on isl
Port(s) 1/1 trunk mode set to on.
Port(s) 1/1 trunk type set to isl.
SwitchA> (enable) set port name 1/2 SwitchB Link
SwitchA> (enable) set trunk 1/2 desirable isl
Port(s) 1/2 trunk mode set to desirable.
Port(s) 1/2 trunk type set to isl.
SwitchA> (enable) set port name 1/3 SwitchC Link
SwitchA> (enable) set trunk 1/3 desirable isl
Port(s) 1/3 trunk mode set to desirable.
Port(s) 1/3 trunk type set to isl.
SwitchA> (enable) set mls enable ipx
IPX Multilayer switching is enabled.
SwitchA> (enable) set mls include ipx 10.1.1.1
IPX Multilayer switching enabled for router 10.1.1.1.
SwitchA> (enable) set port name 3/1 Destination D2
SwitchA> (enable) set vlan 20 3/1
---- -----------------------
Switch B Configuration: Example
This example shows how to configure Switch B:
SwitchB> (enable) set port name 1/1 SwitchA Link
SwitchB> (enable) set port name 3/1 Source S1
SwitchB> (enable) set vlan 10 3/1
---- -----------------------
Switch C Configuration: Example
This example shows how to configure Switch C:
SwitchC> (enable) set port name 1/1 SwitchA Link
SwitchC> (enable) set port name 3/1 Destination D1
SwitchC> (enable) set vlan 30 3/1
---- -----------------------
SwitchC> (enable) set port name 4/1 Source S2
SwitchC> (enable) set vlan 30 4/1
---- -----------------------
MLS-RP Configuration: Example
This example shows how to configure the MLS-RP:
interface fastethernet 2/0
mls rp vtp-domain Engineering
interface fastethernet2/0.1
ipx address 10.1.1.1 255.255.255.0
mls rp management-interface
interface fastethernet2/0.10
interface fastethernet2/0.20
interface fastethernet2/0.30
This example shows how to configure the RSM VLAN interfaces with no access lists. Therefore, the flow mask mode is destination.
Building configuration...
ipx routing 0010.0738.2917
ip address 10.5.5.155 255.255.255.0
mls rp vtp-domain Engineering
mls rp management-interface
ip address 10.2.2.155 255.255.255.0
mls rp vtp-domain Engineering
Building configuration...
ip address 10.2.2.155 255.255.255.0
mls rp vtp-domain Engineering
access-list 800 deny 1111 2222
access-list 800 permit FFFFFFFF FFFFFFFF
Additional References
The following sections provide references related to configuring IPX multilayer switching.
Related Documents
Standards
Standard
|
Title
|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
|
—
|
MIBs
MIB
|
MIBs Link
|
No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature.
|
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
http://www.cisco.com/go/mibs
|
RFCs
RFC
|
Title
|
No new or modified RFCs are supported by this feature, and support for existing standards has not been modified by this feature.
|
—
|
Technical Assistance
Description
|
Link
|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.
To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.
Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.
|
http://www.cisco.com/cisco/web/support/index.html
|
Feature Information for Configuring IPX MLS
Table 1 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release. Unless noted otherwise, subsequent releases of that Cisco IOS software also support that feature.
Table 1 Feature Information for Configuring IPX MLS
Feature Name
|
Releases
|
Feature Information
|
This table is intentionally left blank because no features were introduced or modified in Cisco IOS Release 12.2(1) or later. This table will be updated when feature information is added to this module.
|
—
|
—
|
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0910R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2008 Cisco Systems, Inc. All rights reserved.