IBM and Cisco LAN Switching An Interoperability and Migration Guide How to add Cisco switches to existing IBM local area networks Examples to help you merge and migrate current networks Functional comparisons of IBM and Cisco solutions Harri Levanen Erik Bruun Flemming Schultze ibm.
SG24-5867-00 International Technical Support Organization IBM and Cisco LAN Switching An Interoperability and Migration Guide May 2000
Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix C, “Special notices” on page 129. First Edition (May 2000) This edition applies to IBM and Cisco networking hardware and software. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. HZ8 Building 678 P.O.
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v The team that wrote this redbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Comments welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Chapter 1. Planning interoperability and migration . 1.1 Migration methods . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.
Appendix A. IBM 8265 configuration for the MPOA test . . . . . . . . . . . 119 Appendix B. Cisco 5500 configuration listing for the MPOA test . . . 125 Appendix C. Special notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Appendix D. Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 D.1 IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 D.2 IBM Redbooks collections . . . . . . . . . . . . .
Preface In December 1999, regulatory authorities in the USA approved a strategic alliance between IBM and Cisco. Subsequently, authorities in other countries who investigated the terms of the alliance have also approved it. As a result, IBM Global Services will market Cisco networking products to complement IBM’s solution offerings. IBM’s current line of routers and Ethernet and ATM switches will be withdrawn gradually over the course of the following 12 months.
The team that wrote this redbook This redbook was produced by a team of specialists from around the world working at the International Technical Support Organization, Raleigh Center. Harri Levanen is an Advisory Campus LAN specialist at the International Technical Support Organization, Raleigh Center. He has six years of experience in the networking area. His areas of expertise includes ATM switches, LAN switches and Network Management.
Comments welcome Your comments are important to us! We want our Redbooks to be as helpful as possible. Please send us your comments about this or other Redbooks in one of the following ways: • Fax the evaluation form found in “IBM Redbooks review” on page 141 to the fax number shown on the form. • Use the online evaluation form found at http://www.redbooks.ibm.com/ • Send your comments in an Internet note to redbook@us.ibm.
viii IBM and Cisco LAN Switching: Interoperability and Migration Guide
Chapter 1. Planning interoperability and migration Migration takes place when moving from one technology to another, or from one generation of equipment to another, or from one brand of products to another. Most customer organizations have gone through several migrations of their network. Migration of networking technology is desirable to provide additional functions, increased capacity, or improved cost efficiency to meet business requirements. Migration is nothing new.
1.1 Migration methods There are several ways to migrate. Most organizations have experience with one or more of these methods. For reference, we will briefly review the most common methods for providing growth and additional functions to a network. 1.1.1 Step-by-step box addition or replacement As requirements for additional ports, capacity, or function arise, new equipment is inserted into the network.
1.1.2 Cutover migration The term cutover migration describes the case where all or almost all existing equipment is taken out at once, or over a brief period of time, and replaced with new equipment. See Figure 2. This method is sometimes referred to as forklift migration. A cutover migration may be staged, taking a piece of the network at a time. SD xxxx Li nk R cv 100 - 240 V 1 0. 4 -0 .
SD xxxx 100 - 240V 1 0. 4- 0. 2 A 50 - 6 0H z A UI 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 Li nk R cv 12 3 45 67 8 FD X Xm t 12 3 45 67 8 MD X I OK R ES E T M ana gem en t S D SD xx xx 100 - 240 V 1 0. 4 - 0 .2 A 50 - 6 0 H z Li nk R cv Xm t A UI 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8 xxxx I OK 12 345 67 8 FD X 100 - 240V 1 0.4 - 0.
By inserting an additional hierarchy of faster backbone switches, as shown in Figure 5, network topology is simplified and enabled for growth. Higher level functions will then have access to the faster backbone and can grow as needed. 7 155Mbps 155Mbps 6 1 2 155Mbps 155Mbps 622Mbps 100 622Mbps 622Mbps 400 155Mbps 10 622Mbps 8 155Mbps 200 622Mbps 155Mbps 3 300 155Mbps 155Mbps 5 4 155Mbps 9 Figure 5. Adding more levels: backbone bandwidth 1.
Tivoli product information is found at http://www.tivoli.com. IBM Global Services offer consulting and services to plan and implement Tivoli Enterprise products. See http://www.as.ibm.com/tivoli.html.
Chapter 2. Functional comparisons In this chapter, we first talk about features that are pertinent when selecting Ethernet and ATM switches from different vendors for interworking. We compare IBM networking hardware feature by feature with alternative products. As a consequence of the alliance between IBM and Cisco, we naturally look for Cisco equipment that is similar to and may supplement or substitute for IBM products. Both IBM and Cisco support industry standards.
• Auto-speed negotiation • Flow control • Spanning tree protocol • VLAN functions • Traffic prioritization • Link aggregation • Layer-3 routing In addition we make some general observations that were made during the course of interoperability testing as they relate to each of these criteria. Other functional characteristics such as modularity, scalability, management, number of MAC addresses, and performance are obviously relevant when choosing an Ethernet switch.
2.1.1.3 Spanning tree protocol The spanning tree protocol, part of the IEEE 802.1d specification, prevents loops in a meshed network of Ethernet switches (or bridges). Note Make sure that the higher performance switch is the root switch in networks with many switches. Our interoperability tests verified that either the IBM switch or the Cisco Catalyst switch could be the root bridge, and that either switch could be forced to become the root bridge.
bridges. The standard supports eight classes (priorities) of services (COS), and the LAN devices (switches/bridges), can have any number of transmission queues on each interface, all the way from one queue for all traffic to one queue for each transmission priority. High priority frames will be forwarded before low priority if cut-through mode is not used. A value of 0 means routing services with lowest (no) priority, and a value of 7 might be a time-critical traffic with highest priority.
are available on equipment selected to supplement an existing network of IBM products. Self-learning IP routing IBM 8275 Model 416 supports a simplified routing scheme called self-learning IP routing as its only layer-3 function. This function is also supported on IBM 8371 in addition to full-function layer-3 routing. Self-learning IP routing was first developed as a technology by Bay Networks, and this vendor supports it today on several of its current switch products.
IBM 8271-712 Cisco 2924M XL SNMP + RMON Yes Yes HTML Yes Yes ATM Uplink OC3 / OC12 OC3 OC3 UNI 3.0 / 3.1 / 4.0 3.0 / 3.1 3.0 / 3.1 FC LANE 1.0 / 2.0 1.0 1.0 1 No Spanning Tree support with ATM UFC. 2 Proprietary port-based VLAN. Table 2. IBM 8271-E12/24 12 IBM 8271-Exx Cisco 2820 IEEE802.3 10Base-T Yes 12/24 Yes 12/24 IEEE802.3 AUI Yes Yes IEEE802.3u 100Base-TX/FX Uplink Yes IEEE802.3z 1000Base-SX Uplink No IEEE802.3x FDX 10/100Base-T Yes Yes IEEE802.
1 LAG/ EtherChannel. Table 3. IBM 8271-F12/24 IBM 8271-F12/24 Cisco 2924M XL IEEE802.3 10Base-T Yes Yes IEEE802.3u 100Base-TX/FX Yes Yes IEEE802.3x FDX 10/100Base-T Yes Yes IEEE802.3z 1000BaseSX Uplink Yes IEEE802.3x Flow Control 100Base-T Yes Yes IEEE802.1d Spanning Tree Yes Yes IEEE802.1p Prioritization Yes No IEEE802.
IBM 8275-217/225 Cisco 2924XL IEEE802.1d Spanning Tree Yes Yes IEEE802.1p Prioritization No 1 No IEEE802.1Q VLAN Yes Yes Auto-sensing 10/100 Yes Yes Link Aggregation Yes EtherChannel SNMP + RMON Yes Yes HTML Yes Yes 1 802.1p Static Multicast filtering supported. Table 6. 8271-324 IBM 8275-324 Cisco 2924XL IEEE802.3 10Base-T Yes Yes IEEE802.3u 100Base-TX/FX Yes Yes IEEE802.3xFDX 10/100Base-T Yes Yes IEEE802.3xFlow Control 100Base-T Yes Yes IEEE802.
IBM 8275-3xx Cisco 4003 IEEE802.3x Flow Control 100Base-T Yes Yes IEEE802.1d Spanning Tree Yes Yes IEEE802.1p Prioritization No Yes IEEE802.1Q VLAN No 1 Yes Auto-sensing 10/100 Yes Yes Gigabit Uplink Yes Yes Link Aggregation Yes Yes Port Mirroring Yes Yes 3Com resilient links No No SNMP + RMON Yes Yes HTML Yes Yes 8275-318 switches provide 16 100Base-FX ports + two optional expansion slots. 8275-322 switches provide 12 10/100Base-TX ports + eight 100BaseFX ports.
IBM 8275-412 Cisco 2924XL Link Aggregation Yes EtherChannel Port Mirroring Yes Yes 3Com resilient links No Yes Self-Learning IP Yes No SNMP + RMON Yes Yes HTML Yes Yes IBM 8275-412 Version 1.2 firmware supports self-learning IP. Table 9. 8277-524 compared with Cisco 5505 16 IBM 8277-524 Cisco 5505 IEEE802.3 10Base-T Yes Yes IEEE802.3u 100Base-TX/FX Yes 1 Yes IEEE802.3x FDX 10/100Base-T Yes Yes IEEE802.3x Flow Control 100Base-T Yes Yes IEEE802.
IBM 8277-524 Cisco 5505 UNI 3.0 / 3.1 / 4.0 3.0 /3.1 3.0 / 3.1 FC LANE 1.0 / 2.0 1.0 1.0 / 2.0 RFC1577 CIP Yes Yes RFC1483 MPOA Yes Yes 1 100Base-FX uplink Table 10. IBM 8371-A16 compared to Cisco 5505 IBM 8371-A16 Cisco 5505 IEEE802.3 10Base-T Yes Yes IEEE802.3u 100Base-TX/FX Yes Yes IEEE802.3x FDX 10/100Base-T Yes Yes IEEE802.3x Flow Control 100Base-T Yes Yes IEEE802.1d Spanning Tree Yes Yes IEEE802.1p Prioritization Yes Yes IEEE802.
IBM 8371-A16 Cisco 5505 FC LANE 1.0 / 2.0 1.0 / 2.0 1.0 / 2.0 RFC1577 CIP Yes Yes RFC1483 MPOA Yes Yes IBM 8371 R2.0 supports four Link Aggregation Group (LAG) instances, with up to 10 physical Ethernet links in a LAG. The LAG function is not supported for ATM links. However, the LAG function is supported in conjunction with all of the layer-3 capabilities (routing, self-learning IP, MPC Client).The LAG implementation is interoperable with both Sun Microsystem’s Sun Trunking 1.
For these reasons, our general recommendation for a long-term strategy is to migrate the ATM LAN backbone to an Ethernet backbone. The periphery of an IBM 8265 backbone is frequently a mixture of Ethernet and token-ring because ATM and advanced LAN emulation were excellent technologies to provide a high-speed backbone for both of these media access technologies as well as to provide for integration between them.
For connection to a WAN, IBM 8265 supports many common standards-based interfaces such as: • • • • E1,DS1 and J1 E3 and DS3 OC-3/STM-1 with SONET or SDH STM-1 Inverse multiplexing of E1 or DS1 (IMA) 2.2.1.2 Interface signalling If it is desirable to add a backbone or workgroup switch of another brand to a network of IBM 8265 switches, customers must know which interface signalling they need support for.
• Constant bit rate (CBR) • Unspecified bit rate (UBR) • Variable bit rate (VBR) In the case of IBM 8265, VBR is supported as CBR. Traffic shaping and policing is required when interconnecting ATM switches over a public carrier where the contracted quality of service is less that the physical speed of the connection. 2.2.1.
NHRP and MPOA The Next Hop Resolution Protocol (NHRP) and Multiprotocol over ATM (MPOA) are extensions of LAN emulation to layer 3. Cisco IOS provides support for NHRP and MPOA, client as well as server. Clients are supported on most router and switch products with an ATM uplink. Only IP is supported by Cisco’s MPOA implementations, whereas IBM products support both IP and IPX. This means that IPX traffic cannot be shortcut routed between Cisco MPOA clients.
together with a similar function such as the broadcast limitation supported by the layer-3 engines of some Catalyst switches. 2.2.2 Comparison of IBM 8265-17A with Cisco 8540 Table 11. IBM 8265-A17 compared to Cisco 8540 IBM 8265-17A Cisco 8540 Redundant switching blade Yes Yes OC-3 Yes Yes OC-12 Yes Yes WAN T1/E1 to OC-3/ STM-1 Yes Yes T1/E1 IMA Yes Yes Frame Relay FRAIM Yes Yes Circuit Emulation Yes Yes ESCON Yes No IISP Yes Yes PNNI-1 Yes Yes UNI 3.0 / 3.1 / 4.
2.2.3 Comparison of IBM 8210 MSS Server with Cisco 7200 Table 12.
Chapter 3. Ethernet switch interoperability In this chapter we consider a basic, flat layer-2 switched Ethernet LAN. In the previous chapter we went through several of the characteristics of Ethernet switches that we should consider for interoperability in this environment. The size of a flat layer-2 Ethernet LAN is usually limited by the broadcast activity to a few hundred MAC addresses, but single broadcast domains of several thousand have been heard of.
to move them to fast Ethernet and switched ports, mostly because it is feasible and not very costly. 3.2 Scenario 2: Multiple subnets - growth environment In this generalized scenario the installation in question is in a growth environment and the owning organization is pursuing a strategy to implement advanced functions such as multimedia and telephony. Additionally, bandwidth requirements may be expected to grow considerably.
3.3 Basic Ethernet interoperability exercises In the following sections we describe our experiences during two test scenarios, and we show the configuration process in detail. The two scenarios are: 1. Port trunking or EtherChannel interoperability 2. IEEE 802.1Q VLAN interoperability We were left with the general impression that interoperability between the IBM and Cisco switches we sampled worked very well, in fact over expectation.
with a total capacity of 400 Mbps full duplex (100x2x2). The simplicity of this test is shadowed by the fact that the IBM 8275-322 does not support IEEE 802.1Q trunking nor Cisco’s ISL protocol. 3.3.1.2 Configuring the IBM 8275-322 Switch Figure 7. Logon screen to IBM 8275-322 Switch We begin this test with connecting a terminal to the service port on the IBM 8275-322 Switch. The purpose is to do the IP configuration so we can access the switch from a Web browser.
Figure 8. The 8275-322 Main Menu From the Main Menu, we choose Management Configuration to get access to the Networking Configuration menu. We have the options to configure Network Configuration, Trap Receiver Configuration and SNMP Community Configuration. But at this point in time we only need to set up IP parameters, so we choose Networking Configuration from the menu. Chapter 3.
Figure 9. Network Configuration From the Networking Configuration menu, we add the IP address, Subnet Mask and Default Gateway for the Ethernet LAN interface. We do not need to set up the SLIP parameters for this test.
Figure 10. System Reset Now we move back through the menus to the Main Menu and choose System Utility -> System Reset to activate our new IP configuration. Chapter 3.
Figure 11. Web access to the IBM 8275-322 With our browser, in this case Microsoft Internet Explorer, we access the switch through its new IP address, 161.44.41.11, and after login we see Figure 11. At the top of the window, there is a picture of the switch, with color status on ports etc. In the right pane we have the worksheet, and to the left the navigation tree.
Figure 12. Trunk Config From the navigation tree, we choose Trunking Port Management, to set up TRUNK1, and add ports 1.9 and 1.10 to the trunk as shown in Figure 12. The 8275-322 switch does not support trunking on ports 1.5, 1.6, 1.7 and 1.8. As all the ports are on the same VLAN, we can use the default configuration. The recommendation for interconnection switches is to set the ports to fixed values.
the first switch is set to fixed 10Mbps half duplex and the second switch is set to auto, the second switch may be automatically set to 10Mbps full duplex. Figure 13. Save the changes in trunk definitions At the bottom of the worksheet shown in Figure 13, we use the horizontal scroll bar to go to the far right of the Trunk Port Management window, where we can click the Apply button to save the changes we just made to port 1.9 and 1.10.
Figure 14. Trunking Port Management We will need to reset the switch before the changes in configuration will take effect (Figure 14). To perform a reset, we choose System Reset from the System Utility menu in the navigation tree shown in Figure 15 on page 36. Click the Apply button at the right, and the reset will take place. This is the end of performing the configuration of the IBM 8275-322 switch. Now we have all the ports in the same domain (or VLAN), and have port 1.9 and 1.
Figure 15. 8275-322 System Reset 3.3.1.3 Cisco 2924-XL configuration Now we go to the configuration of the Cisco 2924-XL Switch. As we intend to use the Web interface and run the configuration from our browser, we need to set up an IP address to access the switch. That can be done in several ways, but the easiest way is to use the Setup Program. We need to connect a terminal or emulator to the console port. The default is 9600 baud, 8 data bit, 1 stop bit and no parity.
--- System Configuration Dialog --At any point you may enter a question mark '?' for help. Use ctrl-c to abort configuration dialog at any prompt. Default settings are in square brackets '[]'. Continue with configuration dialog? [yes/no]: yes Enter IP address: 161.44.41.12 Enter IP netmask: 255.255.255.0 Would you like to enter a default gateway address? [yes]: yes IP address of default gateway: 161.44.41.
C2924-XL>enable Password: C2924-XL#config terminal C2924-XL(config)#line vty 0 6 C2924-XL(config)#ip telnet C2924-XL(config)#ip http server C2924-XL(config)#exit C2924-XL#write memory Building configuration... [OK] C2924-XL# Figure 17. Config telnet and http support Now we access the switch with our Web browser on IP 161.44.41.12, by typing http://161.44.41.12 to the Address line of the browser (Figure 18 on page 39).
Figure 18. Cisco System Access Page From the System Access Page in Figure 18, we choose Visual Switch Manager to manage the switch through the Web interface. This interface is only applicable to a subset of Cisco’s smaller switches, but is becoming more common. For further information about the CVSM interface and functionality, see the Cisco IOS Desktop Switching Software Configuration Guide, or Cisco’s Web site at http://www.cisco.com.
Figure 19. Visual Switch Manager Home The Cisco Visual Switch Manager (CVSM) menu bar is located at the top of the Web page (Figure 19). From here, you can choose to configure Port, System, Security, Device, VLAN, and Fault. We will look at the port configuration, port grouping, and VLAN management.
Figure 20. VLAN Membership page Click VLAN, and we enter the VLAN Membership page (Figure 20). All ports are assigned to the same VLAN, “VLAN1”, as default. In this test we leave all ports in that VLAN, but change the mode for port Fa0/7 and Fa0/8 from Static Access to 802.1Q Trunk to enable trunking. Static Access ports belong to one VLAN. Trunk Ports can belong to multiple VLANs. Even though the IBM 8275-322 does not support the 802.1Q standard, we need to set up the Cisco 2924XL as 802.
Figure 21. Port Configuration For port configuration, click Port -> Port Configuration (Figure 21). By default all ports are enabled and speed and duplex are set to AUTO. We will leave them as the default, and later see that Port 7 and 8 are using auto-speed and duplex mode. Note It is safer to always configure the trunk ports to fixed values, in this case to 100 Mbps and duplex mode.
Figure 22. Port Grouping To configure the EtherChannel and Port Group, from the CVSM Main Menu (Figure 21) we choose Port Grouping (EC). This brings us to the Port Group (EtherChannel) window shown in Figure 22. We add FastEthernet0/7 and FastEthernet0/8 ports to Group1 by selecting the port from the pull-down menu, which is shown in Figure 22. Chapter 3.
Figure 23. Port Grouping (EC) EtherChannel Figure 23 shows both FastEthernet0/7 and FastEthernet0/8 ports added to Group 1. Now we have an EtherChannel (Trunk).
Figure 24. Save configuration and reboot From the System Configuration Menu we choose Save Configuration, shown in Figure 24. This will force the switch to save the configuration to NVRAM for a future reboot of the system. A Reboot System is not required now since the changes have already been made to the running configuration. Now we connect port 1.9 from the 8275-322 Switch, to port 0/7 on the Cisco 2924-XL, and port 1.10 to port 0/8.
Figure 25. Port Fa0/7 and Fa0/8 The EtherChannel port Fa0/7 and Fa0/8 are operating 100 Mbps full duplex. 3.3.1.4 Lab 1 conclusions and verification of the configuration We performed a simple test at the end of this lab. We connected one workstation to each switch and started a ping from both to the other. When we broke part of the trunk, the trunk connection itself did not break. We preferred configuring both switches via the Web interface compared to the command-line interface. 3.3.
We use the same Cisco 2924-XL switch, but change to an IBM 8275-225, so both switches support IEEE 802.1Q trunking. In this test we will focus on the security between VLANs, tagging frames for trunking VLAN, and the VLAN trunk itself. Trunk VLAN 1/42/83 IBM8275-225 25 Cisco 2924XL 26 7 1 2 3 4 1 2 VLAN 1 VLAN 42 3 8 4 VLAN 42 VLAN 1 VLAN 83 VLAN 83 Lab2 Figure 26. Lab 2, physical connections and VLANs Figure 26 shows the physical connections and the VLAN ports for lab 2.
3.3.2.1 Configuring the IBM 8275-225 Switch Figure 27. Accessing IBM 8275-225 Switch We start by connecting a workstation running HyperTerminal to the service port on the 8275-225 switch. As the connection is established, we are prompted for a user name and a password as shown in Figure 27. The default user name is admin and no password.
Figure 28. 8275-225 Main Menu From the menu choose Management Setup and then Network Configuration to get to the Network Configuration Menu, shown in Figure 29 on page 50. Chapter 3.
Figure 29. Network Configuration Menu Network Interface 1 is the default. That means VLAN1 is management VLAN. We set IP address to 161.44.41.15, Subnet Mask to 255.255.255.0, and Default Gateway to 161.44.41.1. Save the changes and exit back to the Main Menu from where we enter the System Utility Menu to make a System Restart as shown in Figure 30 on page 51.
Figure 30. System Restart The switch must be restarted for the changes to take effect. After the switch is back online, we access it via the Web browser by typing http://161.44.41.15 on the address line of our Web browser, as shown in Figure 31 on page 52. Chapter 3.
Figure 31. IBM 8275-225 Web pages The Web interface of the IBM 8275-225 is divided into three parts. The top part is a status window, to the left is the navigating window, and the main part is the worksheet as shown in Figure 31.
Figure 32. Switch Port Control / Status: Port 1 From the navigation window, we choose Control and Port. That brings us to the Switch Port Control window shown in Figure 32. We select Port ID 1. Then we set the Port Name to 42-01, 42 as the VLAN ID, and 01 as port number 1. This is the first of two ports on VLAN 42. The speed and duplex are set to AUTO-NEGOTIATE by the default and were left unchanged in our test environment. See “Auto-speed negotiation” on page 8. Transmit pacing is set to DISABLE.
An access port is intended to connect to a network with untagged devices only. When a frame arrives at an access port, it becomes a member of the VLAN that is set by the default VLAN ID (or PVID). As the frame enters the switch, it is tagged with a VLAN tag with a value equal to the PVID of the port. This frame is then sent to other ports in the switch that belong to this VLAN. Hybrid ports are used for trunks.
Now we set up the second port, Figure 33. We set the port ID to 2 and its name to 42-02. The default VLAN ID is 42 and the 802.1Q type is Access. Long Frame Handling is set to ENABLE, which means that frames according to IEEE 802.3ac are supported. This support is required because of the VLAN tag, which will be added to the frames. Figure 34. Switch Port Control / Status: Port 3 The third port will be port ID 3. The Port Name is set to 83-01 and the default VLAN ID is 83. Chapter 3.
Figure 35. Switch Port Control / Status: Port 4 The fourth port has the Port ID 4 and Port Name 83-02 since it will become a member of the 83 VLAN. The IEEE 802.1Q Connection Type is Access as for the other ports.
Figure 36. Switch Port Control / Status: Port 25, TRUNK1 This port is different, as it will be part of the TRUNK1 between the two switches. The Port ID is 25 and the name is TRUNK1. IEEE 802.1Q Connection Type is changed to Hybrid. The Speed and Duplex field is now fixed to 100MBPS Full-Duplex. Chapter 3.
Figure 37. VLAN Registrar Administrative Control: VLAN0042 Now we move to the VLAN Registrar Administrative Control window. We select VLAN ID 42 (VLAN0042). As can be seen from the Port Members field, ports 1, 2 and 25 take part in VLAN0042.
Figure 38. VLAN Registrar Administrative Control: VLAN0083 As for VLAN0042 in Figure 37 on page 58, we can see the port members of VLAN0083. They are ports 3, 4 and 25. Chapter 3.
Figure 39. Trunk Group Configuration Now we join port 26 to TRUNK1 (port 25 already joined) to create a Trunk Group. The configuration of the switch 8275-225 is completed for this test.
3.3.2.2 Configure the Cisco C2924-XL Switch. Figure 40. CVSH Home Page As this switch is the same as the one used in the first Ethernet test in “Lab 1: Trunking IBM 8275-322 and Cisco 2924-XL” on page 27, the initial IP configuration procedure is the same. After it we are able to access the switch from our Web browser. We leave the ports at their defaults, auto-sense speed and duplex and go straight to the VLAN configuration by choosing VLAN from the menu shown in Figure 40. Chapter 3.
Figure 41. VLAN Configuration First we need to assign ports Fa0/1, Fa0/2, Fa0/3 and Fa0/4 to new VLANs (default is VLAN 1). Port Fa0/1 and Fa0/2 are assigned to VLAN ID 42, and ports Fa0/3 and Fa0/4 to VLAN ID 83.These IDs will be used when frames are tagged (labeled), and have to be equal to the VLANs we have already configured at the IBM Switch. All VLAN ports are left at Static Access Mode to know what VLAN the port is belonging to.
Figure 42. Trunk Configuration We add 42 and 83 into the allowed VLAN List, and click the Apply button to save the settings and close the window. We repeat the same for Port Fa0/8, to create the other half of our trunk. Chapter 3.
Figure 43. VLAN Membership Now that we have assigned the ports we want to use, we have to move back to the Port Group (EtherChannel) menu (Figure 23 on page 44), and add port Fa0/7 and Fa0/8 to Group 1, as we did in the earlier “Lab 2: VLAN and trunking on IBM 8275 and Cisco 2924” on page 46. Now we have configured the EtherChannel, and end the task by clicking Apply to apply the changes to the configuration. 3.3.2.
half of the EtherChannel Trunk, reconnected it, and did the same to the other half. We saw no breaks between VLANs, and no errors appeared. The tag function on both switches worked as specified in IEEE 802.1Q specification. Both the switches were easy to configure. There should be no problem in getting a configuration like this up and running, as long as the user is aware of the individual switches’ features and capabilities.
66 IBM and Cisco LAN Switching: Interoperability and Migration Guide
Chapter 4. ATM LAN backbone interoperability and migration In this chapter we consider a typical scenario of an installation based on an IBM 8265 ATM backbone. In all probability, this backbone operates well, there are no bottlenecks, and it scales well by adding more nodes and/or edge devices when more capacity is required. The ATM core of such a network is rarely saturated, and we may expect that the life of ATM switches will extend several years from today.
physical Ethernet and token-ring LANs, and not only attached to the ATM backbone. This does not affect the principles of our scenario. 8270 Before 8271 8270 8270 IBM 8265 MPEG,H.320 CES,CAS Video Telephony Special WAN Figure 44.
there is little traffic between the Ethernet and token-ring ELANs. This traffic is easily bridged or routed by the MSS. Token-ring was chosen and may continue to be the LAN technology of choice for workstation attachment. However, the market has chosen Ethernet, and technological developments have compensated for most of the earlier shortcomings of Ethernet. Economy and wider choices with Ethernet motivate this organization to start a migration to Ethernet.
Migration 2900 8270 8271 8270 8270 2900 Cisco Switch IBM 8265 MPEG,H.320 CES,CAS OC-12 Video Telephony Special WAN Figure 45. Overlay Ethernet backbone for migration There are several challenges in this migration phase. As we intuitively feel from looking at Figure 45, most of the challenges stem from the server connections. To make the entire process manageable, It would probably be a good idea to start by moving all or most of the servers to the Ethernet backbone.
we face the challenge that all the servers reside on Ethernet segments or VLANs, and all the workstations are on a token-ring. As the migration of the workstations may well extend over one or two years, our migration solution must provide ample bandwidth and capacity for bridging or routing between physical as well as emulated Ethernet and token-ring LANs. The developers at Cisco Systems had already anticipated this requirement.
IPX is not supported by the Catalyst MPOA client at this point in time. Therefore IPX traffic must be routed by an ATM router. Non-routable traffic obviously must be bridged. As mentioned, this is readily handled by the MSS or for example, a Cisco 7200. Tip Parallel bridges in an Ethernet environment can be used to provide redundancy. If more than one MSS or Cisco router provide translational bridging, the spanning tree protocol (STP) must be invoked to avoid loops or duplication of frames.
7200 8270 x Future 2900 2900 2900 Cisco Switch 2900 Video Telephony Special WAN Figure 46. Ethernet backbone Such replacement can now happen since we now have a solid Ethernet backbone capable of handling heavy volumes of traffic and we also have the functionality to prioritize and handle Quality of Service. In cases where it will not be cost effective to upgrade older equipment, keep the ATM backbone while the old, existing video equipment and switchboards are still in operation.
to get the latest information about the interoperability tests, and for instructions on submitting requests for new interoperability tests. 4.3 Example of adding a Catalyst 5500 to an IBM 8265 ATM backbone In our test configuration, we have an IBM 8265-based backbone with an IBM 8270 token-ring edge switch. We want to add a Catalyst 5500, with an ATM LANE module, configured with an emulated Ethernet LAN and using MPOA to create a shortcut route between a token-ring VLAN and an Ethernet VLAN.
DUAL-PHY OC-3 blade in the Catalyst 5500 switch implements the other MPOA client. In Appendix A, “IBM 8265 configuration for the MPOA test” on page 119, we have included displays of some show commands showing some of the configuration of the IBM 8265 switch. The IBM 8270 was attached to port 14.3, and the Catalyst 5500 was attached to port 16.3. The interoperability test consisted of the following four major steps: 1. Configuration of IBM 8265 MSS (MPOA Server) 2.
b. Joining the ELAN named “S1Ethernet”. The 5500 LEC can use ILMI to get the LECS address from the ATM switch. Thereafter go through validation with the LECS on the policy ELAN name to get the LES address, and finally join the LES/BUS for S1Ethernet. The IBM 8270 MSS Client must go through the same process to join the ELAN “S1TokenRing”. c. Enable multiple IP connections between both the token-ring and Ethernet workstations. d. MPOA.
. 826 0 IBM8265 1 2 3 4 5 6 SD 7 8 9 10 SD SD 11 12 13 SD 14 SD 15 16 SD SD 17 SD SD SD LE S DU T ATU MO S ROR E R OA D OL TI VE AC D F EE S TU S TA CT I VI A TY S TU TY S TA T I VI AC S TU TY S TA T I VI AC S TU TY S TA T I VI AC US TY I T IV AC S TU TY S TA T I VI AC AT S TA S TA TU TU TU S S S S S S S TU TU TU TU S TA S TA S TA TA S TA S S S TU TU TA R E SE RE RE SE SE SE T T T T T PO RT T SE SE PORT3 POR T SE RE RE RS 23
The MSS client in the 8270 token-ring switch can be configured in several ways. For this test, we created three domains, interconnected via an internal source route bridge. That forces the MSS client to create a RIF field. See Figure 47 on page 74 for the logical configuration and an overview of the test. The configuration of the involved devices can be done in several ways. For the MSS server and the MSS client, the IBM Configurator tool was used.
Tip The redbooks MSS Release 2.1 Including the MSS Client and Domain Client, SG24-5231, Layer 3 Switching Using MSS and MSS Release 2.2 Enhancements, SG24-5311-00 and ATM Configuration Examples, SG24-2126, are excellent sources of detailed information on the MSS products. Figure 50. MSS Configurator tree structure Figure 50 shows the MSS Configurator Navigation Window. The configurator is designed in a tree structure for easy navigating.
Figure 51. Configuration of MSS ESI address First the ATM interface is given an ESI address, and we used a locally administered address for easy recognition of the MSS services. On the Signalling tab, the interface is set for ATM Forum-compliant UNI 3.0. Although UNI 3.0 is used in this example, the recommended UNI version is UNI 3.1. Hereafter the LECS is created as shown in Figure 52.
Figure 52. LECS General The LECS needs a selector byte, which is generated to be 00. The LECS is assigned the ELAN name as policy and enabled as shown in Figure 53. Figure 53. LECS Assignment Policies Chapter 4.
The LECS has a security function. By creating the LECS/LES Interface, a LEC has to be validated by the LECS, to join a LES and become a member of the ELAN. The criteria for validation is the LES Policy. Figure 54. Creating LECS/LEC Security By creating this feature, we force both of the LECs to connect the LECS using the validation of the policy ELAN name (S1Ethernet and S1TokenRing).
Figure 55. Emulated LANs Configuration Now we create the two ELANs, S1Ethernet and S1TokenRing. Figure 55 shows the created ELANs and the General tab for S1Ethernet. S1TokenRing max frame size is set at the default value 4544. As long as the MSS will be doing the IP routing between the two ELANs, the MSS Server will do the fragmentation of frames coming from token-ring and routed to Ethernet. Later when the shortcut is established, the fragmentation will be done by the MPC client in the 8270 Switch.
Figure 56. LES/BUS End System Identifier (ESI) On the LES/BUS General tab the two ELANs are assigned a LES/BUS End System Identifier. We are using the locally administered address as shown in Figure 56. S1Ethernet is given the selector 03 and the ELAN identifier 2. S1TokenRing is given the selector 02 and the ELAN identifier 1.
Figure 57. Enabling access security In the Local LES/BUS Configuration window (Figure 57), we enable security, which forces the LECs to be validated by the LECS before they are able to join the ELAN. This security feature prevents a LEC from joining the LES directly without policy validation. Chapter 4.
Figure 58. Local LES Policy Configuration: S1TokenRing In Figure 58 we can enable LES policies. From the tabs, the individual policy types can be selected and enabled. For the test we assigned only the ELAN name; Figure 58 shows the ELAN name enabled. We enabled the policy value, wrote the ELAN name, and added the parameter to the LES. The same procedure was repeated for Ethernet ELAN S1Ethernet.
Figure 59. Creating a LEC Figure 59 shows the creation of a LEC interface. The MSS must act as a Router between the token-ring and the Ethernet ELANs, as well as provide the MPS services for our two ELANs. Thus we must add a LEC to each ELAN. Using 000000000001 as the ESI address, S1TokenRing is given a selector 04, and S1Ethernet selector 05. Again we chose to leave as many parameters as possible as the default, and went directly to the ELAN tab for defining the LEC as shown in Figure 60. Chapter 4.
Figure 60. LEC Interfaces: ELAN In Figure 60 we select the ELAN name for the LEC. From the pull-down menu we choose S1TokenRing or S1Ethernet respectively. Choose the ELAN type which sets the maximum frame size as the default for token-ring and Ethernet. Remember to click the Add button to set the new parameters before leaving this window.
Figure 61. MSS token-ring LEC IP address. In Figure 61 we assign the IP address to the token-ring ELAN, and enable the LEC as a router interface. Address 40.40.40.1 will be the Default Gateway for our token-ring Client during the test. Click Add to add the IP address. Chapter 4.
Figure 62. MSS Ethernet LEC IP Address Figure 62 shows adding 110.10.10.1 as the IP address for the Ethernet LEC. Now we have a router with a connection into the to ELAN. 110.10.10.1 will be the default gateway for the Ethernet. Only the two LECs are assigned IP addresses.
Figure 63. Enabling MPS and MSS. In Figure 63 we configure the MPS Server. By default both IP and IPX are enabled in the V2.2 MSS Configurator. We will test only the IP. Checking LECS configuration parameters accepted means that the default parameters may be replaced by parameters from the LECS. Chapter 4.
Figure 64. Configuring MPS ESI address and supported protocol Since the MPS function is now turned on, we will enable the services for the individual network interfaces. First we do it on the physical ATM interface using our ESI address with the selector value of 06. We enable MPS for IP. In Figure 65 and Figure 66 the MPS services is enabled on the LEC interface for our Ethernet and token-ring, and again the MPS for IP but not for IPX. Now the MSS Server configuration is completed. Figure 65.
Figure 66. MPS Ethernet interface 4.3.2 MSS client configuration As shown in Figure 67, the configuration of the 8270 Token-Ring Switch consist of three domains: an SRB bridge, MPC client and the ATM interface. The configuration of the legacy token-ring switch is not shown in this chapter, but like the 8265 it is considered basic. We created the three domains and assigned individual ports. All other definitions were left at their defaults.
In the Domain Indices window we first add token-ring interfaces to connect the MSS client to the domains already set up in the base switch. We create three interfaces knowing that the test would need only two domains to be configured. The hardware type is selected from the pull-down menu and the domain index is set equal to the domain index in the base configuration. The default domain is index 0. Figure 68.
Figure 69. Adding locally administered ESI In the ESI tab, we enable the locally administered ESI, and set it to 400082700004. In the Signalling tab, not shown here, we set the signalling protocol to UNI 3.0. The rest of the parameters were left at their defaults. Chapter 4.
Figure 70. Configuration of LEC interface From the Navigation Window (see Figure 50 on page 79) we chose LAN Emulation to set up the LEC. From the General tab we selected ATM device 0, using the ESI we chose for the ATM interface 400082700004 and generated selector 02. The new LEC was given a local MAC address 400082700005. In the ELAN tab we added the ELAN name and ELAN type leaving the max frame size as the default 4544. The ELAN name, S1TokenRing, is shown in Figure 70.
Figure 71. Device Interfaces In the Device Interfaces window, shown in Figure 71, each interface with a domain associated was given a MAC address: • Interface 2, Domain:1, Mac 408270000010 • Interface 3, Domain:2, Mac 408270000011 • Interface 4, Domain:3, Mac 408270000012 To test frames with a RIF field involved, both the domain interface and the LEC interface were enabled for end node source routing, as we activated the source route bridge in the MSS client. Chapter 4.
Figure 72. Configuring LEC Interfaces Source Routing To prevent the MSS client from starting to route IP, no IP addresses were assigned to the interfaces. Therefore we enabled the TCP/IP host services (shown in Figure 73) so we could communicate with the client via the IP host address 40.40.40.134. The default gateway was set to 40.40.40.1, which is the S1TokenRing IP address on the MSS Server. Figure 73.
Figure 74. Enabling MPC support on MSS client From the Navigation Window (see Figure 50 on page 79) click Protocol -> MPOA/NHRP -> MPOA Client . We enabled the client, plus MPC for IP. We used our locally administered ESI and generated selector 00. Since the shortcut was to be between token-ring and Ethernet, we needed a frame fragmentation, since the two types of frames have different MTU sizes. As long as the MSS server is doing the routing, it does the fragmentation as well.
Figure 75. Config of MPC client shortcut In Figure 75, we enabled LANE Shortcuts, and set the shortcut setup frame parameters. For this test, we set the Count to 1 and the Time to 2. Since we used the ping command during the test, we needed the shortcut to be established by pinging, with one packet in less than two seconds. Other timing parameters was left at the defaults.
Figure 76. Enabling bridging in MSS client In Figure 76, the internal SRB bridge in the MSS client is enabled. Chapter 4.
Figure 77. Internal virtual segment Since we have more than two segments, we need to configure an internal segment. This is done in the Bridging - General window, using the SRB tab. The bridge number is set to 1, since we do not have parallel bridges. Internal virtual segment is set to 408.
Figure 78. Adding segment numbers to bridge interfaces In Figure 78 we enable interfaces for SRB, and add a segment number to each. We enable interfaces 2, 3, 4, and 5, the last is our LEC. The segment numbers are set as follows: • interface 2 - segment number D21 • interface 3 - segment number D22 • interface 4 - segment D23 • interface 5 (the LEC) - segment F0D See Figure 79. Now the MSS client configuration is complete.
Figure 79. Adding segment numbers to the LEC 4.3.3 Configuring the Catalyst 5500 MPOA client Here is how we have configured the Ethernet MPOA client in the Catalyst 5500 to set up a shortcut route to the IBM 8270 token-ring switch. The configuration process has three major steps: 1. Creating a VLAN 2. Building the LAN Emulation Client 3. Configuring the MPOA client 4.3.3.1 Creating a VLAN A Catalyst switch always belongs to a VLAN Trunking Protocol (VTP) domain. We must name the VTP domain.
Cisco Systems Console Enter password: cat5500-sup enable Enter password: cat5500-sup (enable) set vtp domain cisco VTP domain cisco modified cat5500-sup (enable) show vtp domain Domain Name Domain Index VTP Version Local Mode Password ---------------------------- ------------ ----------- ----------- ---------cisco 1 2 server Vlan-count Max-vlan-storage Config Revision Notifications ---------- ---------------- --------------- ------------19 1023 13 disabled Last Updater V2 Mode Pruning PruneEligible on Vlans
cat5500-sup (enable) session 9 Trying ATM-9... Connected to ATM-9. Escape character is '^]'. mod9>enable mod9#config terminal Enter configuration commands, one per line. End with CNTL/Z. mod9(config)#interface atm0.11 multipoint mod9(config-subif)#lane client Ethernet 11 S1Ethernet mod9(config-subif)#end mod9#exit cat5500-sup (enable) Figure 82. Create LEC on Cisco 5500 4.3.3.
4.3.3.4 Verifying the Catalyst MPOA client configuration We may now display the LANE and MPC configurations by means of the show command. This provides useful information to verify the configuration and diagnose errors we may have made: mod9#show lane default-atm-addresses interface ATM0: LANE Client: 39.0102030405060708090AA102.00D0BB6BA080.** LANE Server: 39.0102030405060708090AA102.00D0BB6BA081.** LANE Bus: 39.0102030405060708090AA102.00D0BB6BA082.** LANE Config Server: 39.0102030405060708090AA102.
mod9#show mpoa default-atm-addresses interface ATM0: MPOA Server: 39.0102030405060708090AA102.00D0BB6BA084.** MPOA Client: 39.0102030405060708090AA102.00D0BB6BA085.** note: ** is the MPS/MPC instance number in hex mod9#show mpoa client MPC Name: mod9-mpc-01, Interface: ATM0, State: Up MPC actual operating address: 39.0102030405060708090AA102.00D0BB6BA085.00 1 Shortcut-Setup Count: 1, Shortcut-Setup Time: 1 Lane clients bound to MPC mod9-mpc-01: ATM0.11 Discovered MPS neighbours kp-alv vcd rxPkts txPkts 39.
4.3.4.1 MPS - MSS Server Connecting to the MSS server, we type TALK 5 -> Protocol MPOA -> MPS. We are now able to look at specific details, and start with the command Discovery. Both MPC Clients have been discovered.
5 CacheID 7 shows our Ethernet workstation 110.10.10.34. MPS >IMPOSITION-CACHE ENTRY 6 CacheId: 6 State: Active Elan-id: 1 I-MPS Addr: 40.40.40.1 Destination: 40.40.40.20 NextHop: 40.40.40.
In Figure 88: 1 Shows the connection to the MPS in the MSS. 2 Shows that the MPC in the 8270 MSS client is known and established. With the show mpoa client command shown in Figure 88, we verified that the Cisco MPC has discovered and is aware of the MPS and the 8270’s MPC. Although it is not shown, the command show mpoa client cache verified that a shortcut route to the 8270 MPC client was established after we started pinging between the workstations. 4.3.4.
MPC >MPC-BASE MPOA Client Base Console ======================== MPC Base>STATE MPOA Client State: ================== ATM Interface Number: State: Time Since Last State Change (h:m:s): Last (internal) error code: Network-layer protocols enabled: 0 MPC UP STATE 01:54:20 0 IP MPC Base>LIST-CONFIG MPOA Client Configuration: ========================= Status: ENABLED 1 Shortcut Setup Frame Count: 1 Shortcut Setup Frame Time: 2 (sec) Initial Retry Time: 5 (sec) Maximum Retry Time: 40 (sec) Hold Down Time: 160 (s
3 It is ready to do the LANE shortcut. MPC >NEIGHBOR-MPSs MPOA Client MPS Console ======================= MPC MPS>LIST List of Neighbor MPSs for MPOA Client (interface 0): ===================================================== 1) Control ATM: 39.01.02.03.04.05.06.07.08.09.0A.A1.02.00.00.00.00.00.01.06 1 1 MAC Address(es) Learnt For This MPS: 1) MAC Addr: x00.00.00.00.00.
4 VCI 449 to our Workstation 110.10.10.34, and the shortcut route is RESOLVED. That can be seen in Figure 91. MPC VCC>LIST-VCC VPI, Range 0..255 [0]? VCI, Range 0..65535 [0]? 448 VPI/VCI: 0/448 State: OPERATIONAL Calling Party: FALSE Hold Down Cause: N/A Cause Code: N/A Fwd/Bak SDU:1508/1508 Remote ATM Addr: 39.01.02.03.04.05.06.07.08.09.0A.A1.02.00.D0.BB.6B.A0.85.00 Conn Type: P2P VCC Type: B. EFFORT Encaps. Type: LLC 1483 H/W Path Valid: FALSE Ref.
MPC >INGRESS-CACHE MPOA Client Ingress Cache Console MPC INGRESS>LIST IP-Ingress Cache For MPC on ATM Interface 0 ======================================== Ingress Cache Entries for Direct Host Routes: -------------------------------------------1) IP Address: 110.10.10.
FALSE Local Shortcut 3 means that the 8270 switch can make a local shortcut but in this case, we are making a connection across an ATM network. 4 shows the target address is 110.10.10.34. MPC INGRESS>INGRESS-STATISTICS Ingress MPC Statistics For This MPC: -----------------------------------Frames forwarded to MPSs: 122 Total Resolution Requests Sent: 28 Total Refresh Res. Requests Sent: 2 Total Res. Rqst Retransmissions: 19 Total Res. Rqst Timeouts: 6 Total Res. Reply Successes: 3 Total Res.
Figure 94 shows the Egress Cache, with our 40.40.40.20 address and Encapsulation type TAG. MPC EGRESS>LIST-ENTRIES 40.40.40.20 Destination Protocol Address Mask [255.255.255.255]? Egress Cache Entries matching 40.40.40.20/255.255.255.255 : 1) Address/Mask: 40.40.40.20/255.255.255.255 Type: TAG LEC #: 5 Cache ID: x6 State: ACTIVE MPS: 39.01.02.03.04.05.06.07.08.09.0A.A1.02.00.00.00.00.00.01.06 Source: 39.01.02.03.04.05.06.07.08.09.0A.A1.02.00.D0.BB.6B.A0.85.
4.3.4.4 IBM 8265 VCCs 8265_C2> show signalling cross_connections port 14.3 In: slot.port vpi.vci type Out: slot.port vpi.vci type Conn Cat ------------------------------------------------------------------------------14.3 0.440 svc 7.1 0.123 svc p2p ubr 14.3 0.441 svc 7.1 0.124 svc p2m ubr 14.3 0.442 svc 7.1 0.125 svc p2p ubr 14.3 0.443 svc 7.1 0.126 svc p2m ubr 14.3 0.445 svc 7.1 0.128 svc p2p ubr 14.3 0.447 svc 7.1 0.130 svc p2p ubr 14.3 0.448 svc 16.3 0.169 svc p2p ubr 14.3 0.449 svc 16.3 0.
Appendix A. IBM 8265 configuration for the MPOA test The configuration of the IBM 8265 switch is listed for your reference. 8265_C2> show device 8265 ATM Control Point and Switch Module Name : 8265ATM Location : IBM LAB RTP For assistance contact : Manufacture id: 930 Part Number: 02L3457 EC Level: F12519 Boot EEPROM version: v.4.1.3 Flash EEPROM version: v.4.1.3 (PNNI)1 Flash EEPROM backup version: v.4.1.
Default Gateway : OK ------------------------------------------------------------------------------IP address: 10.10.10.1 ARP Server: ------------------------------------------------------------------------------ATM address: 39.99.99.99.99.99.99.00.00.99.99.33.01.08.00.5A.99.0D.54.00 Device configured for PNNI port capability. Device configured for Lan Emulation Servers. Dynamic RAM size is 32 MB. Migration: off. Diagnostics: enabled. Device defined as primary.
8265_C2> show port 7.1 verbose Type Mode Status Daughter Card Description -----------------------------------------------------------------------------7.01:UNI enabled UP A-MSS 3 (FC5403) UNI Type : Private Signalling Version : Auto > Oper Sig. Version : 3.0 ILMI status : UP ILMI vci : 0.16 RB Bandwidth : unlimited Signalling vci : 0.5 RB Admin weight : 5040 NRB Admin weight : 5040 VPI range admin. : 0-15 (4 bits) VCI range admin. : 0-1023 (10 bits) VPI range oper. : 0-7 (3 bits) VCI range oper.
8265_C2> show port 14.3 verbose Type Mode Status ------------------------------------------------------------------------------14.03: UNI enabled UP UNI Type : Private Signalling Version : Auto 1 > Oper Sig. Version : 3.0 2 ILMI status : UP ILMI vci : 0.16 RB Bandwidth : unlimited Police admin. : on Police oper. : on Signalling vci : 0.5 RB Admin weight : 5040 NRB Admin weight : 5040 VPI range admin. : 0-15 (4 bits) VCI range admin. : 0-1023 (10 bits) VPI range oper. : 0-7 (3 bits) VCI range oper.
8265_C2> show port 16.3 verbose Type Mode Status ------------------------------------------------------------------------------16.03: UNI enabled UP UNI Type : Private Signalling Version : Auto 1 > Oper Sig. Version : 3.1 2 ILMI status : UP ILMI vci : 0.16 RB Bandwidth : unlimited Police admin. : on Police oper. : on Signalling vci : 0.5 RB Admin weight : 5040 NRB Admin weight : 5040 VPI range admin. : 0-15 (4 bits) VCI range admin. : 0-1023 (10 bits) VPI range oper. : 0-3 (2 bits) VCI range oper.
124 IBM and Cisco LAN Switching: Interoperability and Migration Guide
Appendix B. Cisco 5500 configuration listing for the MPOA test The configuration of the Cisco 5500 MPOA client is given here as a reference. We will not discuss it in detail but only list the core configuration parameters required to run a MPC LEC. Please refer to the Cisco documentation at http://www.cisco.com for a more detailed description of the commands and configuration parameters used in this example.
#module 2 : 12-port 10/100BaseTX Ethernet (not used) ! OC12 Dual PHY MMF (not used) ! #module 4 : 2-port MM OC-3 Dual-Phy ATM (not used) ! #module 5 empty ! #module 6 empty ! module 7 : 24-port 10/100BaseTX Ethernet set module name 7 set modul enable 7 set vlan 1 7/4-9,7/23-24 set vlan 11 7/3,7/13 set port enable 7/1-24 set port level 7/1-24 normal set port speed 7/1-24 auto set port trap 7/1-24 disable set port name 7/1-24 set port security 7/1-24 disable set port broadcast 7/1-24 0 set portmembership 7/1-
#module 10 empty ! #module 11 empty ! #module 12 empty ! #module 13 empty ! cat5500-sup cat5500-sup (enable) session 9 Trying ATM-9... Connected to ATM-9. LEC - LANE modul configuration mod9>enable mod9#show config Using 911 out of 523258 bytes ! !Last configuration change at 10:09:39 UTC Fri Feb 4 2000 !NVRAM config last updated at 10:09:41 UTC Fri Feb 4 2000 ! version 12.
no login 128 IBM and Cisco LAN Switching: Interoperability and Migration Guide
Appendix C. Special notices This publication is intended to help users of IBM Ethernet and ATM switches plan growth and eventual migration of existing networks. The information in this publication is not intended as the specification of any programming interfaces that are provided by IBM Ethernet and ATM switches. See the PUBLICATIONS section of the IBM Programming Announcement for IBM Ethernet and ATM switches for more information about what publications are considered to be product documentation.
been reviewed by IBM for accuracy in a specific situation, there is no guarantee that the same or similar results will be obtained elsewhere. Customers attempting to adapt these techniques to their own environments do so at their own risk. Any pointers in this publication to external Web sites are provided for convenience only and do not in any manner serve as an endorsement of these Web sites.
countries. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and/or other countries. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States and/or other countries. PC Direct is a trademark of Ziff Communications Company in the United States and/or other countries and is used by IBM Corporation under license.
132 IBM and Cisco LAN Switching: Interoperability and Migration Guide
Appendix D. Related publications The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook. D.1 IBM Redbooks For information on ordering these publications see “How to get IBM Redbooks” on page 135. • MSS Release 2.
D.3 Other resources These publications are also relevant as further information sources: • CLSC Exam Certification Guide, ISBN 0-7357-0875-4 • CCIE Professional Development: Cisco LAN Switching, ISBN 1-57870-094-9 D.4 Referenced Web sites http://www.redbooks.ibm.com http://www.tivoli.com http://www.as.ibm.com/tivoli.html http://www.ibm.com/planetwide http://www.cisco.
How to get IBM Redbooks This section explains how both customers and IBM employees can find out about IBM Redbooks, redpieces, and CD-ROMs. A form for ordering books and CD-ROMs by fax or e-mail is also provided. • Redbooks Web Site http://www.redbooks.ibm.com/ Search for, view, download, or order hardcopy/CD-ROM Redbooks from the Redbooks Web site. Also read redpieces and download additional materials (code samples or diskette/CD-ROM images) from this Redbooks site.
IBM Redbooks fax order form Please send me the following: Title Order Number First name Quantity Last name Company Address City Postal code Country Telephone number Telefax number VAT number Card issued to Signature Invoice to customer number Credit card number Credit card expiration date We accept American Express, Diners, Eurocard, Master Card, and Visa. Payment by credit card not available in all countries. Signature mandatory for credit card payment.
Index Numerics 8265 Nways ATM switch 23 A ABR 20 ATM 72 backbone 21, 67 cell switching 18 switches 18 UFC 12 ATM switches comparison See comparison criteria ATM-25 19 Auto-speed negotiation 8 B backbone 67 ATM LAN 19 Ethernet 19 backbone switches 26 bandwidth requirements 26 broadcast management 22 broadcasts 68 BUS 21 C Call routing 19, 20 Catalyst 20 5000 series 11 5500 75 MPOA 104 6000 11 6500 21 MPOA IPX 72 CBR 21 Cisco 2820 12 Cisco 2924MXL 11, 13 Cisco 2924XL 13, 14, 15, 36 Cisco 4003 14 Cisco 5500
parallel 19 Ethernet switches 11 comparison See comparison criteria F Fast EtherChannel 18 fixed speed 8 flow control 8 full duplex 8 half-duplex 8 IEEE 802.
IP and IPX 19 Server 75 MPS 92 MSS 19, 21, 24 configuration tool 78 MSS client 67, 111 configuration 75, 93 Multilayer Switch Feature 11 multimedia 26 multimedia equipment 68 multi-mode fiber 19 Multi-protocol encapsulation 22 N Neighbor MPSs 113 NetFlow Feature Card 11 Network hierarchy 5 Network management 5 NHRP 22 number of MAC addresses 8 O OAR 71 OC-12 19, 21 OC-3 19, 75 one-armed router 71 OSPF 10 Overlaying network 3 P performance 8 PNNI 19, 20 Port trunking 27 Proprietary Port Based VLAN 12, 15
voice technology 3 VOID 20 VPC 20 VRRP 11 VTP 104 W WAN 20 140 IBM and Cisco LAN Switching: Interoperability and Migration Guide
IBM Redbooks review Your feedback is valued by the Redbook authors. In particular we are interested in situations where a Redbook "made the difference" in a task or problem you encountered. Using one of the following methods, please review the Redbook, addressing value, subject matter, structure, depth and quality as appropriate. • Use the online Contact us review redbook form found at ibm.
IBM and Cisco LAN Switching An Interoperability and Migration Guide (0.2”spine) 0.17”<->0.
® IBM and Cisco LAN Switching An Interoperability and Migration Guide How to add Cisco switches to existing IBM local area networks Examples to help you merge and migrate current networks Functional comparisons of IBM and Cisco solutions This IBM Redbook will help anyone who has an IBM campus/LAN network today.
