|
|
This chapter describes how to configure your network to perform IPX Multilayer Switching (MLS). For a complete description of the Multilayer Switching commands, see the chapter "Multilayer Switching Commands" in the Cisco IOS Switching Services Command Reference. For documentation of other commands that appear in this chapter, you can use the command reference master index or search online.
This chapter contains these sections:
 |
Note The information in this chapter 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. |
The following prerequisites must be met before IPX MLS can function:
IPX MLS must be enabled on the router. The minimal configuration steps are described in the section "IPX MLS Configuration Tasks." For more details on configuring IPX routing, refer to the Cisco IOS AppleTalk and Novell IPX Configuration Guide.
This section describes restrictions that apply to configuring IPX MLS on the router.
Be aware of the following:
When using an external router, use the following guidelines:
The following restrictions apply when you use access lists on interfaces that participate in IPX MLS:
|
Note You can translate input access lists to output access lists to provide the same effect on the interface. |
IPX MLS affects other Cisco IOS software features as follows:
In IPX the two endpoints of communication negotiate the maximum transmission unit (MTU) to be used. MTU size is limited by media type.
Perform the following tasks to configure one or more routers for IPX MLS. The number of tasks you perform depends on your particular configuration.
For examples of IPX MLS configurations, see the "Configuration Examples" section later in this document.
 |
Caution Perform this configuration task only if the switch connected to your router interfaces is in a VTP domain. Perform the task before you enter any other IPX MLS interface command---specifically the mls rp ipx or mls rp management-interface commands. If you enter these commands before adding the interface to a VTP domain, the interface will be automatically placed in a null domain. To place the IPX MLS interface into a domain other than the null domain, clear the IPX MLS interface configuration before you add the interface to another VTP domain. See the section "Configuration, Verification, and Troubleshooting Tips" and the Catalyst 5000 Software Configuration Guide, Release 5.1. |
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 command at the switch Console> prompt.
To assign an MLS interface to a specific VTP domain on the MLS-RP, use the mls rp vtp-domain command in interface configuration mode:
| Command | Purpose |
|---|---|
Router(config-if)# mls rp vtp-domain domain-name | Adds an IPX MLS interface to a Virtual Trunk Protocol (VTP) domain. |
To enable MLSP on the router, use the mls rp ipx command in global configuration mode:
| Command | Purpose |
|---|---|
Router(config)# mls rp ipx | Globally enables MLSP on the router. MLSP is the protocol that runs between the MLS-SE and MLS-RP. |
|
NoteThis 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, use the mls rp vlan-id command in interface configuration mode:
| Command | Purpose |
|---|---|
Router(config-if)# mls rp vlan-id vlan-id-number | Assigns a VLAN ID to an IPX MLS interface. Theassigned IPX MLS interface must be either an Ethernet or Fast Ethernet interface with no subinterfaces. |
To enable IPX MLS on a router interface, use the mls rp ipx command in interface configuration mode:
| Command | Purpose |
|---|---|
Router(config-if)# mls rp ipx | Enables a router interface for IPX MLS. |
To specify an interface as the management interface, use the mls rp management-interface command in interface configuration mode:
| Command | Purpose |
|---|---|
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. |
To verify that you have correctly installed IPX MLS on the router, perform the following steps:
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.
If you entered either the mls rp ipx command or the mls rp management-interface command on the interface before assigning it to a Virtual Trunk Protocol (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, use the following commands in interface configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | Router(config-if)# no mls rp ipx | Removes an interface from the null domain. |
Step2 | Router(config-if)# mls rp vtp-domain domain-name | Adds the interface to a new Virtual Trunk Protocol (VTP) domain. |
| Command | Purpose |
|---|---|
Router# mls rp locate ipx | Displays information about all switches currently shortcutting for the specified IPX flow(s). |
Router# show mls rp interface type number | Displays MLS details for a specific interface. |
Router# show mls rp ipx | Displays details for all IPX MLS interfaces on the router: 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; and list of interfaces in all Virtual Trunk Protocol (VTP) domains enabled for MLS. |
Router# show mls rp vtp-domain domain-name | Displays details about IPX MLS interfaces for a specific Virtual Trunk Protocol (VTP) domain. |
This section provides a complex IPX MLS network example: the Cisco 7505 switch over ISL. The example includes router and switch configurations, even though switch commands are not documented in this router publication. The section also includes sample configurations with no access lists and with standard access lists. Refer to the Catalyst 5000 Command Reference, Release5.1 for more information.
This example consists of the following sections:
Figure 34 shows an IPX MLS network topology consisting of three Catalyst5000 series switches and a Cisco7505 router---all interconnected with ISL trunk links.
The network is configured as follows:
Before IPX MLS is implemented, when the source host NC1 (on VLAN 10) sends traffic destined for destination server NS2 (on VLAN 30), SwitchB forwards the traffic (based on the Layer2 forwarding table) to SwitchA over the ISL trunk link. SwitchA 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. SwitchA receives the routed packet and forwards it to SwitchC. SwitchC 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.
After IPX MLS is implemented, when the source host NC1 (on VLAN 10) sends traffic destined for destination server NS2 (on VLAN 30), SwitchB forwards the traffic (based on the Layer2 forwarding table) to SwitchA (the MLS-SE) over the ISL trunk link. When the first packet enters SwitchA, a candidate flow entry is established in the MLS cache. SwitchA 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. SwitchA receives the routed packet (the enabler packet) and completes the flow entry in the MLS cache for the destination IPX address of NS2. SwitchA forwards the packet to SwitchC, 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 SwitchB to SwitchA (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 SwitchC, bypassing the router.
This example shows how to configure SwitchA (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
Port 1/1 name set.
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
Port 1/2 name set.
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
Port 1/3 name set.
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
Port 3/1 name set.
SwitchA> (enable) set vlan 20 3/1
VLAN 20 modified.
VLAN 1 modified.
VLAN Mod/Ports
---- -----------------------
20 3/1
SwitchA> (enable)
This example shows how to configure SwitchB:
SwitchB> (enable) set port name 1/1 SwitchA Link
Port 1/1 name set.
SwitchB> (enable) set port name 3/1 Source S1
Port 3/1 name set.
SwitchB> (enable) set vlan 10 3/1
VLAN 10 modified.
VLAN 1 modified.
VLAN Mod/Ports
---- -----------------------
10 3/1
SwitchB> (enable)
This example shows how to configure SwitchC:
SwitchC> (enable) set port name 1/1 SwitchA Link
Port 1/1 name set.
SwitchC> (enable) set port name 3/1 Destination D1
Port 3/1 name set.
SwitchC> (enable) set vlan 30 3/1
VLAN 30 modified.
VLAN 1 modified.
VLAN Mod/Ports
---- -----------------------
30 3/1
SwitchC> (enable) set port name 4/1 Source S2
Port 4/1 name set.
SwitchC> (enable) set vlan 30 4/1
VLAN 30 modified.
VLAN 1 modified.
VLAN Mod/Ports
---- -----------------------
30 3/1
4/1
SwitchC> (enable)
This example shows how to configure the Multilayer-Switching-Route Processor:
mls rp ipx interface fastethernet 2/0 full-duplex mls rp vtp-domain Engineering interface fastethernet2/0.1 encapsulation isl 1 ipx address 10.1.1.1 255.255.255.0 mls rp ipx mls rp management-interface interface fastethernet2/0.10 encapsulation isl 10 ipx network 10 mls rp ipx interface fastethernet2/0.20 encapsulation isl 20 ipx network 20 mls rp ipx interface fastethernet2/0.30 encapsulation isl 30 ipx network 30 mls rp ipx
This example shows how to configure the RSM VLAN interfaces with no access lists. Therefore, the flow mask mode is destination.
Building configuration... Current configuration: ! version 12.0 . . ipx routing 0010.0738.2917 mls rp ip mls rp ipx . . interface Vlan21 ip address 5.5.5.155 255.255.255.0 ipx network 2121 mls rp vtp-domain Engineering mls rp management-interface mls rp ip mls rp ipx ! interface Vlan22 ip address 2.2.2.155 255.255.255.0 ipx network 2222 mls rp vtp-domain Engineering mls rp ip mls rp ipx ! . . end
This example shows how to configure a standard access list on the RSM VLAN 3 interface. Therefore, the flow mask mode is destination-source.
Router#show run Building configuration... Current configuration: ! version 12.0 ! interface Vlan22 ip address 2.2.2.155 255.255.255.0 ipx access-group 800 out ipx network 2222 mls rp vtp-domain Engineering mls rp ip mls rp ipx ! . . ! ! ! access-list 800 deny 1111 2222 access-list 800 permit FFFFFFFF FFFFFFFF . . end
Posted: Mon Jul 17 16:58:35 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.