Console> (enable) set vlan 5/12 VLAN modified VLAN modified VLAN Mod/Ports −−−− −−−−−−−−−−−−−−−−−−−−−−−− 5/11−12 Activate the VLAN with the command set vlan Console> (enable) set vlan Vlan configuration successful The show vlan command will now indicate that VLAN2 is active and contains two ports: 5/11 and 5/12 Console> (enable) sh vlan VLAN Name −−−− −−−−−−−− VLAN0002 VLAN −−−− VLAN −−−− Type −−−− enet SAID −−−−−− 100002 Status −−−−−− active MTU Parent −−−− −−−−−− 1500 − AREHops −−−−−−− STEHops −−−−−−− RingNo −−−−−− − BrdgNo −−−−−− − Mod/Ports, Vlans −−−−−−−−−−−−−−−− 5/11−12 Stp −−− − BrdgMode −−−−−−−− − Trans1 −−−−−− Trans2 −−−−−− Backup CRF −−−−−−−−−− The VLAN status can also be displayed using the show vlan command We see that all of the other Ethernet ports still reside in the default VLAN Console> (enable) sh vlan VLAN Name −−−− −−−−−−−−−−−−−−−−−−−−−−− default VLAN −−−− 1002 1003 1004 1005 VLAN −−−− 1003 Status −−−−−− active VLAN0002 1002 fddi−default 1003 token−ring−default 1004 fddinet−default 1005 trnet−default Type −−−− enet enet fddi trcrf fdnet trbrf SAID −−−− 100001 100002 101002 101003 101004 101005 MTU −−−− 1500 1500 1500 1500 1500 1500 AREHops −−−−−−− Parent −−−−−− − − − − − STEHops −−−−−−− Mod/Ports, Vlans −−−−−−−−−−−−−−−− 2/1−2 3/1−24 5/1−10 7/1−24 10/1−24 5/11−12 active active active active active RingNo −−−−−− − − 0x0 0x0 − − BrdgNo −−−−−− − − − − 0x0 0x0 12/1−16 Stp −−− − − − − ieee ibm BrdgMode −−−−−−−− − − − − − − Trans1 −−−−−− 0 0 0 Trans2 −−−−−− 0 0 0 Backup CRF −−−−−−−−−− off We can verify that VLAN is active by connecting to RouterA and trying to ping RouterB at IP address 192.1.1.2 We see from the output below that the ping was successful RouterA and RouterB are now both on VLAN RouterA#ping 192.1.1.2 685 Type escape sequence to abort Sending 5, 100−byte ICMP Echos to 192.1.1.2, timeout is seconds: !!!!! Success rate is 100 percent (5/5), round−trip min/avg/max = 4/7/8 ms Lab #93: ISL Trunk with Routing Between VLANs Equipment Needed The following equipment is needed to perform this lab exercise: • Two Cisco routers with Ethernet interfaces • One Cisco router with a 100−Mbps Ethernet interface • A Catalyst switch • Three Ethernet cables • A Cisco rolled cable for console port connection to the routers • A straight−through cable for console port connection to the Catalyst switch Configuration Overview This lab will demonstrate how to route between two VLANs As shown in Figure 20−8, RouterA will reside in VLAN and RouterB will reside in VLAN Both VLAN and VLAN reside in different IP networks Since the Catalyst is a layer switch, it is unable to route between the two VLANs A layer router is needed to perform this function The solution is to define a high−speed trunk between the Catalyst switch and a router This trunk is referred to as an Interswitch Link (ISL) and runs over a 100−Mbps Ethernet interface Figure 20−8: Routing between two VLANs Note Cisco makes many models of LAN switches Although this lab was done using a Catalyst 5500 switch, there are other LAN switches in the Cisco product line that could be used For example, the Catalyst 1924 Enterprise Edition is a low−cost switch that is capable of doing VLANs and can also have a 100−Mbps ISL trunk Note The Catalyst does not use the same IOS as a Cisco router You will notice that the command set is very different Many items that are taken for granted on the router, such as being able to use the tab key to complete a command, are not available on the Catalyst switch Note Catalyst ports are referred to by slot and port number For example, in this lab we are connected to the 11th and 12th port of Card The Catalyst will refer to these ports as 5/11 and 5/12, respectively Router Configuration The configurations for the three routers in this example are as follows 686 RouterA Current configuration: ! version 11.2 no service password−encryption no service udp−small−servers no service tcp−small−servers ! hostname RouterA ! interface Ethernet0/0 ip address 192.1.1.1 255.255.255.0 ← Define the IP address for the interface connected to the Catalyst switch ! router rip network 192.1.1.0 ! no ip classless ! line line aux line vty exec−timeout 30 login ! end RouterB Current configuration: ! version 11.2 no service password−encryption no service udp−small−servers no service tcp−small−servers ! hostname RouterB ! ! ! interface Ethernet0/0 ip address 193.1.1.1 255.255.255.0 ← Define the IP address for the interface connected to the Catalyst switch ! router rip network 193.1.1.0 ! no ip classless ! line line aux line vty exec−timeout 30 login ! end RouterC Current configuration: ! version 11.2 no service password−encryption no service udp−small−servers 687 no service tcp−small−servers ! hostname RouterC ! interface FastEthernet1/0 ← This 100Mbps interface connects to the Catalyst trunk port no ip address no logging event subif−link−status ! interface FastEthernet1/0.1 ← This subinterface accepts traffic from VLAN encapsulation isl ← Define ISL encapsulation and accept traffic from VLAN ip address 192.1.1.10 255.255.255.0 ← IP address for this subinterface no ip redirects ! interface FastEthernet1/0.2 ← This subinterface accepts traffic from VLAN encapsulation isl ← Define ISL encapsulation and accept traffic from VLAN ip address 193.1.1.10 255.255.255.0 ← IP address for this subinterface no ip redirects ! router rip ← We need to dynamically route between VLAN and VLAN Our routes will be learned via RIP network 192.1.1.0 ← Propagate RIP for the network on VLAN network 193.1.1.0 ← Propagate RIP for the network on VLAN ! no ip classless ! ! line line aux line vty login ! end Monitoring and Testing the Configuration Let's start by setting the Catalyst 5500 to its factory default setting with the clear config all command Remember from the previous chapter that after the Catalyst has been reset, all of the Ethernet ports will be assigned to VLAN Console> (enable) clear config all This command will clear all configuration in NVRAM This command will cause ifIndex to be reassigned on the next system startup Do you want to continue (y/n) [n]? y System configuration cleared Since we will be assigning Catalyst ports to multiple VLANs, we must set the VTP domain name of the switch with the set vtp domain command Console> (enable) set vtp domain CCIE_LAB VTP domain CCIE_LAB modified Port 5/12 is in VLAN for this lab We not need to enter any commands to place port 5/12 into VLAN since this is the default state of the Catalyst switch Port 5/11 will be assigned to VLAN for this lab To assign port 5/11 to VLAN 2, we use the set vlan 5/11 command Console> (enable) set vlan 5/11 688 Vlan configuration successful VLAN modified VLAN modified VLAN Mod/Ports −−−− −−−−−−−−−−−−−−−−−−−−−−−−−− 5/10−11 Enable VLAN with the set vlan command Console> (enable) set vlan Vlan configuration successful Port 5/10 will be the trunk port for this lab Port 5/10 will connect to our Cisco router We will see shortly that port 5/10 will transmit all VLAN traffic to the Cisco router The Cisco router will then be able to route between our two VLANs We need to set port 5/10 to trunk mode with the set trunk 5/10 on command Console> (enable) set trunk 5/10 on Port(s) 5/10 trunk mode set to on The status of port 5/10 can be viewed with the show port 5/10 command We see that the port is active and is now defined as a trunk port Notice that the port is running at 100−Mbps full duplex (The a− before the full duplex and 100 Mb indicates that these settings were autosensed by the Catalyst switch.) Console> (enable) sh port 5/10 Port Name Status Vlan −−−− −−−− −−−−−−−−− −−−−− 5/10 connected trunk Secure−Src−Addr −−−−−−−−−−−−−−− Level −−−−−− normal Duplex −−−−−− a−full Last−Src−Addr −−−−−−−−−−−−− Speed −−−−− a−100 Type −−−−−−−−−−−−− 10/100 BaseTX Shutdown −−−−−−−− No Trap −−−−−−−− disabled Port −−−− 5/10 Security −−−−−−−− disabled Port −−−− 5/10 Port −−−− 5/10 Broadcast−Limit −−−−−−−−−−−−−−− − Status Channel mode −−−−−−−−− −−−−−−− connected auto Port −−−− 5/10 Align−Err −−−−−−−−− FCS−Err −−−−−−− Xmit−Err −−−−−−−− Rcv−Err −−−−−−− UnderSize −−−−−−−−− Port −−−− 5/10 Single−Col −−−−−−−−−− Multi−Coll −−−−−−−−−− Late−Coll −−−−−−−−− Excess−Col −−−−−−−−−− Carri−Sen −−−−−−−−− Broadcast−Drop −−−−−−−−−−−−− − Channel Neighbor status device −−−−−−−−−−− −−−−−−−− not channel Neighbor port −−−−−−−− Runts −−−−− Giants −−−−−− − Last−Time−Cleared −−−−−−−−−−−−−−−−−−−−−−−−− Sun May 16 1999, 02:25:04 Verify that the ports connected to RouterA and RouterB (5/12 and 5/11) are connected Notice that port 5/11 (RouterB) is in VLAN 2, while port 5/12 (RouterA) is in VLAN Console> (enable) sh port 5/11 Port Name Status Vlan −−−− −−−− −−−−−−−−− −−−− 5/11 connected Level −−−−−− normal Duplex −−−−−− a−half Speed −−−−− a−10 Type −−−−−−−−−−−− 10/100BaseTX Console> (enable) sh port 5/12 Port Name Status Vlan −−−− −−−− −−−−−−−−− −−−− 5/12 connected Level −−−−−− normal Duplex −−−−−− a−half Speed −−−−− a−10 Type −−−−−−−−−−−− 10/100BaseTX 689 The show trunk command gives us specific information on our trunk, showing us what VLANs are allowed on the trunk (by default, all VLAN's are allowed on a trunk) and what VLANs are active on the trunk We see that in our case, all traffic from all VLANs is allowed on trunk 5/10 Console> (enable) sh trunk Port Mode Status −−−− −−−− −−−−−−−− 5/10 on trunking Port −−−− 5/10 Vlans allowed on trunk −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−− 1−1005 Port −−−− 5/10 Vlans allowed and active in management domain −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−− 1−2,1003,1005 Port −−−− 5/10 Vlans in spanning tree forwarding state and not pruned −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−− 1−2,1003,1005 Now let's connect to RouterA and view the routing table with the show ip route command We see that we are learning a route to the 193.1.1.0 network The 193.1.1.0 network connects RouterB to the Catalyst switch on VLAN The routing table on RouterA tells us that RouterC is working properly and is routing between two VLANs RouterA#sh Codes: C − D − N1− E1− i − U − ip route connected, S − static, I − IGRP, R − RIP, M − mobile, B − BGP EIGRP, EX − EIGRP external, O − OSPF, IA − OSPF inter area OSPF NSSA external type 1, N2 − OSPF NSSA external type OSPF external type 1, E2 − OSPF external type 2, E − EGP IS−IS, L1− IS−IS level−1, L2 − IS−IS level−2, * − candidate default per−user static route, o − ODR Gateway of last resort is not set C R 192.1.1.0/24 is directly connected, Ethernet0/0 193.1.1.0/24 [120/1] via 192.1.1.10, 00:00:26, Ethernet0/0 Make sure that we have end−to−end connectivity by trying to ping RouterA at IP address 193.1.1.1 The ping should be successful RouterA#ping 193.1.1.1 Type escape sequence to abort Sending 5, 100−byte ICMP Echos to 193.1.1.1, timeout is seconds: !!!!! Success rate is 100 percent (5/5), round−trip min/avg/max = 4/4/4 ms Now let's connect to RouterB View the routing table on RouterB with the show ip router command We see that RouterB has learned a route to RouterA via RIP RouterB#sh Codes: C − D − N1− E1− i − U − ip route connected, S − static, I − IGRP, R − RIP, M − mobile, B − BGP EIGRP, EX − EIGRP external, O − OSPF, IA − OSPF inter area OSPF NSSA external type 1, N2 − OSPF NSSA external type OSPF external type 1, E2 − OSPF external type 2, E − EGP IS−IS, L1− IS−IS level−1, L2 − IS−IS level−2, * − candidate default per−user static route, o − ODR Gateway of last resort is not set R C 192.1.1.0/24 [120/1] via 193.1.1.10, 00:00:10, Ethernet0/0 193.1.1.0/24 is directly connected, Ethernet0/0 690 Make sure that we can ping RouterA at IP address 192.1.1.1 RouterB#ping 192.1.1.1 Type escape sequence to abort Sending 5, 100−byte ICMP Echos to 192.1.1.1, timeout is seconds: !!!!! Success rate is 100 percent (5/5), round−trip min/avg/max = 4/6/8 ms Now connect to RouterC and view its routing table with the show ip route command We see that RouterC has two directly connected networks Each of these networks is coming into RouterC on the same physical 100−Mbps Ethernet circuit The Ethernet circuit has defined two subinterfaces, VLAN is associated with subinterface FastEthernet 1/0.1 and VLAN is assigned to subinterface FastEthernet 1/0.2 RouterC#sh Codes: C − D − N1− E1− i − U − ip route connected, S − static, I − IGRP, R − RIP, M − mobile, B − BGP EIGRP, EX − EIGRP external, O − OSPF, IA − OSPF inter area OSPF NSSA external type 1, N2 − OSPF NSSA external type OSPF external type 1, E2 − OSPF external type 2, E − EGP IS−IS, L1− IS−IS level−1, L2 − IS−IS level−2, * − candidate default per−user static route, o − ODR Gateway of last resort is not set C C 192.1.1.0/24 is directly connected, FastEthernet1/0.1 193.1.1.0/24 is directly connected, FastEthernet1/0.2 From RouterC, ping RouterA and RouterB to verify that the circuit is active RouterC#ping 192.1.1.1 Type escape sequence to abort Sending 5, 100−byte ICMP Echos to 192.1.1.1, timeout is seconds: !!!!! Success rate is 100 percent (5/5), round−trip min/avg/max = 4/4/4 ms RouterC#ping 193.1.1.1 Type escape sequence to abort Sending 5, 100−byte ICMP Echos to 193.1.1.1, timeout is seconds: !!!!! Success rate is 100 percent (5/5), round−trip min/avg/max = 1/3/4 ms Troubleshooting {show version} The show version command displays important system−level information, including the version of system firmware, firmware level, and serial number for each card installed in the switch, system memory, and uptime statistics Console> (enable) show ver WS−C5500 Software, Version Copyright (c) 1995−1997 by NMP S/W compiled on Dec 31 MCP S/W compiled on Dec 31 McpSW: 3.1(1) NmpSW: 3.1 Cisco Systems 1997, 18:36:38 1997, 18:33:15 System Bootstrap Version: 3.1(2) Hardware Version: 1.3 Module −−−−−− Ports −−−−− 24 Model: WS−C5500 Model −−−−−−−− WS−X5530 WS−X5224 Serial #: 069028115 Serial # −−−−−−−−− 008167898 008161402 691 Hw −−− 1.8 1.3 Fw −−−−−−− 3.1 3.1 Fw1 −−−−−− 4.1 Sw −−− 3.1 3.1 10 12 Module −−−−−− 12 24 24 16 DRAM Total −−−−−− 32640K WS−X5203 WS−X5224 WS−X5224 WS−X5030 Used −−−−−− 11854K 008451509 008161009 008161288 007380744 FLASH Total −−−−− 8192K Free −−−−−− 20786K 1.1 1.3 1.3 1.0 3.1 3.1 3.1 1.0(117 Used −−−−− 3224K 2.2(4) NVRAM Total −−−−− 512K Free −−−−− 4968K 3.1 3.1 3.1 3.1 Used −−−− 106K Free −−−− 406K Uptime is days, 20 hours, 14 minutes {show module} The show module command shows what type of card is inserted into each slot of the Catalyst switch Burned−in MAC address information is also displayed for each card Console> (enable) Mod Module−Name −−−−−−−−−−−−−−− 10 12 Mod −−− 10 12 Mod −−− 2 show module Ports Module−Type −−−−− −−−−−−−−−−−−−−−−−−−−−− 10/100 BaseTX Supervis 24 10/100 BaseTX Ethernet 12 10/100 BaseTX Ethernet 24 10/100 BaseTX Etherne 24 10/100 BaseTX Ethernet 16 Token Ring Model −−−−−−−− WS−X5530 WS−X5224 WS−X5203 WS−X5224 WS−X5224 WS−X5030 MAC−Address(es) −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−− 00−90−f2−a7−c1−00 thru 00−90−f2−a7−c4−ff 00−10−7b−2e−ca−e8 thru 00−10−7b−2e−ca−ff 00−10−7b−09−9a−50 thru 00−10−7b−09−9a−5b 00−10−7b−3d−be−f0 thru 00−10−7b−3d−bf−07 00−10−7b−3d−be−c0 thru 00−10−7b−3d−be−d7 00:05:77:05:86:42 thru 00:05:77:05:86:52 Sub−Type −−−−−−−− EARL 1+ uplink Sub−Model −−−−−−−−− WS−F5520 WS−U5531 Sub−Serial −−−−−−−−−− 0008157389 0008577601 Hw −−− 1.8 1.3 1.1 1.3 1.3 1.0 Serial−Num Status −−−−−−−−−−−−−−−− 008167898 ok 008161402 ok 008451509 ok 008161009 ok 008161288 ok 007380744 ok Fw −−− 3.1(2) 3.1(1) 3.1(1) 3.1(1) 3.1(1) 1.0(117 Sw −−−−−− 3.1(1) 3.1(1) 3.1(1) 3.1(1) 3.1(1) 3.1(1) Sub−Hw −−−−−− 1.1 1.1 {show mac} The show mac command displays detailed statistics on traffic passing through the Catalyst switch The following output has been truncated to just show the statistics for three ports on a Catalyst switch Notice the detailed reporting statistics for each port, including total received and transmitted frames; multicast, unicast, and broadcast statistics; error statistics; and total octets transmitted and received Console> (enable) show mac MAC Rcv−Frms Xmit−Frms −−− −−−−−−−− −−−−−−−−− 5/10 30948 251858 5/11 44490 166061 5/12 43857 166409 Rcv−Multi −−−−−−−−− 14649 4953 4438 Xmit−Multi −−−−−−−−−− 251758 145105 145408 Rcv−Broad −−−−−−−−− 08 96 15 Xmit−Broad −−−−−−−−−− 5774 5823 MAC −−−− 5/10 5/11 5/12 Dely−Exced −−−−−−−−−− 0 In−Discard −−−−−−−−−− 38 61 73 Lrn−Discrd −−−−−−−−−− 0 In−Lost −−−−−−− 0 Out−Lost −−−−−−−− 0 Port −−−− 5/10 5/11 5/12 Rcv−Unicast −−−−−−−−−−− 16192 39441 39405 MTU−Exced −−−−−−−−− 0 Rcv−Multicast −−−−−− −−−−−− 14649 4953 4438 Rcv−Broadcast −−−−−−−−−−−−− 108 96 15 692 Port −−−− 5/10 5/11 5/12 Xmit−Unicast −−−−−−−−−−−− 100 15182 15178 Xmit−Multicast −−−−−−−−−−−−−− 251764 145107 145410 Port −−−− 5/10 5/11 5/12 Rcv−Octet −−−−−−−−− 3183207 20334264 20290059 Xmit−Broadcast −−−−−−−−−−−−−− 5774 5823 Xmit−Octet −−−−−−−−−− 23975586 27851660 27865755 Last−Time−Cleared −−−−−−−−−−−−−−−−−−−−−−−−− Sun May 16 1999, 02:25:04 {clear config all} The clear config all command causes the switch to be reset to its factory default state In this state, all ports reside in VLAN and the Catalyst acts as a large switching hub Console> (enable) clear config all This command will clear all configuration in NVRAM This command will cause ifIndex to be reassigned on the next system startup Do you want to continue (y/n) [n]? y System configuration cleared {show port} The show port command displays statistics on port−level configuration on the Catalyst switch The Catalyst can automatically sense speed and duplex on each port of the switch For example, we see in the output below that ports 5/11 and 5/12 have been automatically configured Their status is connected, they are both in VLAN 1, and they are both running 10−Mbps half−duplex Ethernet Console> (enable) sh Port Name −−−− −−−−−−−−−−−− 5/1 5/2 5/3 5/4 5/5 5/6 5/7 5/8 5/9 5/10 5/11 5/12 port Status −−−−−−−−−− notconnect notconnect notconnect notconnect notconnect notconnect notconnect notconnect notconnect notconnect connected connected Vlan −−−− 1 1 1 1 1 1 Level −−−−−− normal normal normal normal normal normal normal normal normal normal normal normal Duplex −−−−−− auto auto auto auto auto auto auto auto auto auto a−half a−half Speed −−−−− auto auto auto auto auto auto auto auto auto auto a−10 a−10 Type −−−−−−−−−−−−− 10/100 BaseTX 10/100 BaseTX 10/100 BaseTX 10/100 BaseTX 10/100 BaseTX 10/100 BaseTX 10/100 BaseTX 10/100 BaseTX 10/100 BaseTX 10/100 BaseTX 10/100 BaseTX 10/100 BaseTX {show port slot/port} More detailed port status is available by adding the port number after the show port command In the example below, we see that additional data such as MAC−level security information and Ethernet collision and error statistics are listed for the specified port Console> (enable) Port Name −−−−− −−−− 5/11 sh port 5/11 Status Vlan −−−−−−−−− −−−− connected Level −−−−−− normal Port Secure−Src−Addr Last−Src−Addr Security 693 Duplex −−−−−− a−half Speed −−−−− a−10 Shutdown Type −−−−−−−−−−−−− 10/100 BaseTX Trap −−−− 5/11 −−−−−−−− disabled Port −−−− 5/11 Port Broadcast−Limit −−−−−−−−−−−−−−− − Status Channel mode −−−−−−−−− −−−−−−− connected auto −−−− 5/11 −−−−−−−−−−−−−−− −−−−−−−−−−−−− −−−−−−−− No Broadcast−Drop −−−−−−−−−−−−−− Channel Neighbor status device −−−−−−−−−−− −−−−−−−− not channel −−−−−−−− disabled Neighbor port −−−−−−−− Port Align−Err −−−−− −−−−−−−−− 5/11 FCS−Err −−−−−−− Xmit−Err −−−−−−−− Rcv−Err −−−−−−− UnderSize −−−−−−−−− Port −−−− 5/11 Multi−Coll −−−−−−−−−− Late−Coll −−−−−−−−− Excess−Col −−−−−−−−−− Carri−Sen −−−−−−−−− Single−Col −−−−−−−−−− Runts −−−−− Giants −−−−−− Last−Time−Cleared −−−−−−−−−−−−−−−−−−−−−−−−− Sun May 16 1999, 02:25:04 {show cam dynamic} The show cam dynamic command displays connected host MAC addresses that have been learned by the switch Console> (enable) show cam dynamic VLAN Dest MAC/Route Des Destination Ports or VCs −−−− −−−−−−−−−−−−−−−−−− −−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−− 00−e0−1e−9c−8e−b0 5/10 00−e0−1e−9c−8e−b0 5/10 00−10−7b−06−c2−c1 5/11 00−e0−1e−5b−27−61 5/12 00−00−ff−ff−ff−fb 1/4 Total Matching CAM Entries Displayed = {show system} The show system command displays system contacts, current and peak traffic utilization, uptime, and thermal information Console> (enable) show PS1−Status PS2−Status −−−−−−−−−− −−−−−−−−−− ok none PS1−Type −−−−−−−− WS−C5508 PS2−Type −−−−−−−− none system Fan−Status −−−−−−−−−− ok Modem −−−−−− disable System Name −−−−−−−−−−−−−−−−−−−−−−− Baud −−−− 9600 Temp−Alarm Sys−Status −−−−−−−−−− −−−−−−−−− off ok Traffic −−−−−−− 0% Peak −−−− 0% System Location −−−−−−−−−−−−−−−−−−−−−−− Uptime d,h:m:s −−−−−−−−−−−−−− 5,20:14:10 Logout −−−−−− 20 Peak−Time −−−−−−−−−−−−−−−−−−−−−−−−− Sun May 16 1999, 02:25:04 System Contact −−−−−−−−−−−−−−−−−−−−−−− {set interface} The set interface command is used to set the IP address for inband access to the switch Console> (enable) set interface sc0 192.1.1.3 Interface sc0 IP address set {show interface} The show interface command is used to display the internal Catalyst IP addresses for inband access and SLIP access Console> (enable) sh interface sl0: flags=51 slip 0.0.0.0 dest 128.73.35.160 sc0: flags=63 vlan inet 192.1.1.3 netmask 255.255.255.0 broadcast 192.1.1.255 694 hostname RouterD ! enable password cisco ! source−bridge ring−group 100 dlsw local−peer peer−id 135.2.15.77 dlsw remote−peer tcp 135.2.15.81 dlsw remote−peer tcp 135.2.15.73 dlsw remote−peer tcp 135.2.15.85 dlsw bridge−group ! interface Loopback0 ip address 135.2.13.1 255.255.255.0 ! interface Ethernet0/0 ip address 135.2.15.77 255.255.255.252 bridge−group ! interface Serial0/0 ip address 135.2.15.70 255.255.255.252 encapsulation ppp ! router ospf 64 network 135.2.0.0 0.0.255.255 area ! no ip classless ! bridge protocol ieee ! line line aux line vty password cisco login ! end Monitoring and Testing the Configuration Let's start by connecting to RouterA We see from the show dlsw peer command that RouterA has three connected DLSW peers Notice that the peer type is listed as configured (conf) for each of the three peers This tells us that RouterA's peers have been explicitly defined in the router configuration RouterA# show dlsw peer Peers: state TCP 135.2.15.77 CONNECT TCP 135.2.15.81 CONNECT TCP 135.2.15.85 CONNECT pkts_rx 3669 5099 453 pkts_tx 3505 3448 537 type conf conf conf drops ckts TCP uptime 1d02h 1d02h 01:44:40 The show dlsw capabilities command verifies the status and capabilities of each remote peer RouterA# show dlsw capabilities DLSw: Capabilities for peer 135.2.15.77(2065) ← Remote peer 135.2.15.77 vendor id (OUI) : '00C' (cisco) version number : release number : init pacing window : 20 unsupported saps : none num of tcp sessions : loop prevent support : no icanreach mac−exclusive: no icanreach netbios−excl.: no reachable mac addresses: none reachable netbios names: none cisco version number : 759 peer group number : border peer capable : no peer cost : biu−segment configured : no local−ack configured : yes priority configured : no peer type : conf version string : Cisco Internetwork Operating System Software IOS (tm) 3600 Software (C3620−JS−M), Version 11.2(20)P, RELEASE SOFTWARE (fc1) Copyright (c) 1986−1999 by Cisco Systems, Inc Compiled Mon 11−Oct−99 21:14 by jaturner DLSw: Capabilities for peer 135.2.15.81(2065) ← Remote peer 135.2.15.81 vendor id (OUI) : '00C' (cisco) version number : release number : init pacing window : 20 unsupported saps : none num of tcp sessions : loop prevent support : no icanreach mac−exclusive: no icanreach netbios−excl.: no reachable mac addresses: none reachable netbios names: none cisco version number : peer group number : border peer capable : no peer cost : biu−segment configured : no local−ack configured : yes priority configured : no peer type : conf version string : Cisco Internetwork Operating System Software IOS (tm) 3600 Software (C3620−JS−M), Version 11.2(20)P, RELEASE SOFTWARE (fc1) Copyright (c) 1986−1999 by Cisco Systems, Inc Compiled Mon 11−Oct−99 21:14 by jaturner DLSw: Capabilities for peer 135.2.15.85(2065) ← Remote peer 135.2.15.85 vendor id (OUI) : '00C' (cisco) version number : release number : init pacing window : 20 unsupported saps : none num of tcp sessions : loop prevent support : no icanreach mac−exclusive: no icanreach netbios−excl.: no reachable mac addresses: none reachable netbios names: none cisco version number : peer group number : border peer capable : no peer cost : biu−segment configured : no local−ack configured : yes priority configured : no peer type : conf version string : Cisco Internetwork Operating System Software IOS (tm) 3600 Software (C3620−JS−M), Version 11.2(20)P, RELEASE SOFTWARE (fc1) Copyright (c) 1986−1999 by Cisco Systems, Inc Compiled Mon 11−Oct−99 21:14 by jaturner The show dlsw capabilities local command can similarly be used to verify the DLSW capabilities of the local peer RouterA# show dlsw capabilities local 760 DLSw: Capabilities for local peer vendor id (OUI) : '00C' (cisco) version number : release number : init pacing window : 20 unsupported saps : none num of tcp sessions : loop prevent support : no icanreach mac−exclusive: no icanreach netbios−excl.: no reachable mac addresses: none reachable netbios names: none cisco version number : peer group number : border peer capable : no peer cost : biu−segment configured : no current border peer : none version string : Cisco Internetwork Operating System Software IOS (tm) 3600 Software (C3620−JS−M), Version 11.2(20)P, Copyright (c) 1986−1999 by Cisco Systems, Inc Compiled Mon 11−Oct−99 21:14 by jaturner RELEASE SOFTWARE (fc1) Now connect to RouterB Use the show dlsw peer command to verify that RouterB has established a DLSW peer to RouterA, RouterB, and RouterC RouterB# show dlsw peer Peers: state TCP 135.2.15.73 CONNECT TCP 135.2.15.81 CONNECT TCP 135.2.15.77 CONNECT pkts_rx 537 453 454 pkts_tx 453 330 418 type conf conf conf drops ckts TCP uptime 01:44:53 01:43:47 01:43:18 The show dlsw reach command will display the NetBIOS names that have been locally cached Notice that RouterB has seen System1, System3, and System4 These are the three workstations that are connected to RouterA, RouterC, and RouterD RouterB# show dlsw reach DLSw Local MAC address reachability cache list Mac Addr status Loc port DLSw Remote MAC Mac Addr 0008.d296.2e0c 000a.204b.a17b 000a.204b.e39e 000b.0396.4663 rif address reachability cache list status Loc Peer FOUND REMOTE 135.2.15.73(2065) FOUND REMOTE 135.2.15.77(2065) FOUND REMOTE 135.2.15.81(2065) FOUND REMOTE 135.2.15.81(2065) DLSw Local NetBIOS Name reachability cache list NetBIOS Name status Loc port rif DLSw Remote NetBIOS Name reachability cache list NetBIOS Name status Loc Peer System1 FOUND REMOTE 135.2.15.73(2065) System3 FOUND REMOTE 135.2.15.81(2065) System4 FOUND REMOTE 135.2.15.77(2065) RouterC and RouterD should also be checked to verify that they each have three DLSW peers The output of the show dlsw peer command for RouterC and RouterD is shown here: RouterC# show dlsw peer Peers: state TCP 135.2.15.77 CONNECT TCP 135.2.15.73 CONNECT TCP 135.2.15.85 CONNECT pkts_rx 4918 3449 330 pkts_tx 6879 5101 453 761 type conf conf conf drops ckts TCP uptime 0 1d02h 1d02h 01:44:06 RouterD# show dlsw peer Peers: state TCP 135.2.15.81 CONNECT TCP 135.2.15.73 CONNECT TCP 135.2.15.85 CONNECT pkts_rx 6880 3507 419 pkts_tx 4919 3671 455 type conf conf conf drops ckts TCP uptime 0 1d02h 1d02h 01:43:50 The configuration can also be verified by viewing the entire network neighborhood on any of the four workstations Each workstation should see the other three workstations Lab #104: DLSW Border Peers Equipment Needed The following equipment is needed to perform this lab exercise: • Two Cisco routers with serial interfaces and Ethernet interface • Two Cisco routers with serial interface and Ethernet interface • Three Cisco crossover cables If a Cisco crossover cable is not available, then you can use a Cisco DTE cable connected to a Cisco DCE cable • Four workstations running NetBEUI • Four Ethernet crossover cables • A Cisco rolled cable for console port connection to the routers • A Cisco IOS image that supports DLSW Configuration Overview This lab will demonstrate DLSW border peers Border peers are a method of reducing the full mesh requirements of DLSW The four routers are physically connected as shown in Figure 24−6 The four routers are logically connected as shown in Figure 24−7 Notice the difference between the logical connectivity of this lab and the logical connectivity of our previous lab (DLSW full mesh) The border peer capability allows us to reduce our DLSW peering requirements to the following: 762 Figure 24−6: DLSW border peers Figure 24−7: DLSW logical connectivity • Each router within a peer group peers to its DLSW border peer router • Each border peer router peers to every other border peer router 763 In this lab, RouterA and RouterB are in peer group 51, with RouterB being the border peer RouterC and RouterD are in peer group 1, with RouterC being the border peer Our peer requirements are as follows: • RouterA must peer with RouterB (A router peers with its border peer) • RouterB must peer with RouterC (Border peer routers must peer) • RouterC must peer with RouterB (Border peer routers must peer) • RouterD must peer with RouterC (A router peers with its border peer) Thus, we need a total of remote peer statements This contrasts with 12 remote peer statements required in the previous lab Note For instructions on how to configure a workstation to run NetBEUI, see the section at the end of this chapter Router Configuration The configurations for the four routers in this example are as follows Key border peer commands are highlighted in bold RouterA Current configuration: ! version 11.2 no service password−encryption no service udp−small−servers no service tcp−small−servers ! hostname RouterA ! enable password cisco ! source−bridge ring−group 100 dlsw local−peer peer−id 135.2.15.73 group 51 promiscuous ← Accept a peer connection from any neighbor dlsw remote−peer tcp 135.2.15.85 ← Peer with our Border Peer (RouterB) dlsw bridge−group ! interface Loopback0 ip address 135.2.10.1 255.255.255.0 ! interface Ethernet0/0 ip address 135.2.15.73 255.255.255.252 bridge−group ! interface Serial0/0 ip address 135.2.15.34 255.255.255.224 encapsulation ppp clockrate 800000 ! router ospf 64 network 135.2.0.0 0.0.255.255 area ! no ip classless ! bridge protocol ieee ! line line aux line vty password cisco login 764 ! end RouterB Current configuration: ! version 11.2 no service password−encryption service udp−small−servers service tcp−small−servers ! hostname RouterB ! enable password cisco ! source−bridge ring−group 100 dlsw local−peer peer−id 135.2.15.85 group 51 border promiscuous ← Define this router as a Border Peer for Peer Group 51 dlsw remote−peer tcp 135.2.15.81 ← Peer with the other Border Peer (RouterC) dlsw bridge−group ! interface Loopback0 ip address 135.2.12.1 255.255.255.0 ! interface Ethernet0/0 ip address 135.2.15.85 255.255.255.252 bridge−group ! interface Serial0/0 ip address 135.2.15.35 255.255.255.224 encapsulation ppp ! interface Serial0/1 ip address 135.2.15.65 255.255.255.252 encapsulation ppp ! router ospf 64 network 135.2.0.0 0.0.255.255 area ! no ip classless ! bridge protocol ieee ! line line aux line vty password cisco login ! end RouterC Current configuration: ! version 11.2 no service password−encryption no service udp−small−servers no service tcp−small−servers ! hostname RouterC ! 765 enable password cisco ! source−bridge ring−group 100 dlsw local−peer peer−id 135.2.15.81 group border promiscuous ← Define this router as a Border Peer for Peer Group dlsw remote−peer tcp 135.2.15.85 ← Peer with the other Border Peer (RouterB) dlsw bridge−group ! interface Loopback0 ip address 135.2.9.1 255.255.255.0 ! interface Ethernet0/0 ip address 135.2.15.81 255.255.255.252 no cdp enable bridge−group ! interface Serial0/0 ip address 135.2.15.69 255.255.255.252 encapsulation ppp no fair−queue clockrate 800000 no cdp enable ! interface Serial0/1 ip address 135.2.15.66 255.255.255.252 encapsulation ppp clockrate 800000 no cdp enable ! router ospf 64 network 135.2.0.0 0.0.255.255 area ! no ip classless ! bridge protocol ieee ! line line aux line vty password cisco login ! end RouterD Current configuration: ! version 11.2 no service password−encryption no service udp−small−servers no service tcp−small−servers ! hostname RouterD ! enable password cisco ! source−bridge ring−group 100 dlsw local−peer peer−id 135.2.15.77 group promiscuous ← Accept a peer connection from any neighbor dlsw remote−peer tcp 135.2.15.81 ← Peer with our border peer (RouterC) dlsw bridge−group ! 766 interface Loopback0 ip address 135.2.13.1 255.255.255.0 ! interface Ethernet0/0 ip address 135.2.15.77 255.255.255.252 bridge−group ! interface Serial0/0 ip address 135.2.15.70 255.255.255.252 encapsulation ppp ! router ospf 64 network 135.2.0.0 0.0.255.255 area ! no ip classless ! bridge protocol ieee ! line line aux line vty password cisco login ! end Monitoring and Testing the Configuration Let's start by connecting to RouterA We see from the show dlsw peer command that RouterA has two active peers Notice from the peer type that one of the peers is conf and one is pod Conf refers to a peer that is explicitly configured In the case of RouterA, 135.2.15.85 has been named as a remote peer and is shown as a conf peer type Pod refers to a Peer on Demand 135.2.15.77 (RouterD) is shown as a peer on demand This is because RouterD is not explicitly configured as a peer in RouterA's configuration The peer relationship is set up as necessary The promiscuous statement in RouterA's local peer command allows this to happen RouterA# show dlsw peer Peers: state TCP 135.2.15.77 CONNECT TCP 135.2.15.85 CONNECT pkts_rx 35 80721 pkts_tx 33 68834 type pod conf drops ckts TCP uptime 00:09:37 00:10:37 Connecting to RouterC also verifies that only the peer to RouterB (135.2.15.85) has been explicitly configured RouterC# show dlsw peer Peers: state TCP 135.2.15.77 CONNECT TCP 135.2.15.85 CONNECT pkts_rx 46 51528 pkts_tx 59 56845 type prom conf drops ckts TCP uptime 00:11:13 0 00:10:38 The show dlsw peer command on RouterD verifies that only the peer to RouterC (135.2.15.81) has been explicitly configured RouterD# show dlsw peer Peers: state TCP 135.2.15.81 CONNECT TCP 135.2.15.73 CONNECT TCP 135.2.15.85 CONNECT pkts_rx 71953 37 43 pkts_tx 37658 41 48 type conf pod pod drops ckts TCP uptime 0 00:12:01 0 00:10:13 00:10:09 Now connect to RouterB We see from the show dlsw peer command that only the peer to RouterC is a configured type peer The other two peers (to Router D and RouterA) are configured as necessary RouterB# show dlsw peer Peers: state TCP 135.2.15.81 CONNECT pkts_rx 56850 pkts_tx 51538 767 type conf drops ckts TCP uptime 0 00:11:13 TCP 135.2.15.77 TCP 135.2.15.73 CONNECT CONNECT 44 38 41 53 pod prom 0 1 00:09:56 00:11:00 The show dlsw reach command indicates that RouterB has learned about the workstations on each of the other LANs in our network We see that SYSTEM1, SYSTEM3, and SYSTEM4 have been cached RouterB# show dlsw reach DLSw Local MAC address reachability cache list Mac Addr status Loc port 000a.204b.cbb1 FOUND LOCAL TBridge−001 rif −−no rif−− DLSw Remote MAC address reachability cache list Mac Addr status Loc Peer 0008.d296.2e0c FOUND REMOTE 135.2.15.73(2065) 000a.204b.a17b FOUND REMOTE 135.2.15.77(2065) 000a.204b.e39e FOUND REMOTE 135.2.15.81(2065) 000b.0396.4663 FOUND REMOTE 135.2.15.81(2065) DLSw Local NetBIOS Name reachability cache list NetBIOS Name status Loc port rif SYSTEM2 FOUND LOCAL TBridge−001 −−no rif−− DLSw Remote NetBIOS Name reachability cache list NetBIOS Name status Loc Peer SYSTEM1 FOUND REMOTE 135.2.15.73(2065) SYSTEM3 FOUND REMOTE 135.2.15.81(2065) SYSTEM4 FOUND REMOTE 135.2.15.77(2065) This lab can be verified by making sure that each of the four workstations can see all of the other workstations via Windows networking Lab #105: DLSW Backup Peers Equipment Needed The following equipment is needed to perform this lab exercise: • One Cisco router with Token Ring interface and serial interfaces • Two Cisco routers with serial interface and Ethernet interface • Two Cisco crossover cables If a Cisco crossover cable is not available, then you can use a Cisco DTE cable connected to a Cisco DCE cable • Three Ethernet cables and an Ethernet hub • Two Token Ring cables and a Token Ring MAU • Two workstations running NetBEUI • A Cisco rolled cable for console port connection to the routers • A Cisco IOS image that supports bridging Configuration Overview This lab will demonstrate DLSW backup peers Backup peers allow a DLSW peering session to stay active when a remote peer fails This is accomplished by having a backup peer reestablish the DLSW session Configuring a DLSW backup peer is a bit tricky Referring to Figure 24−8, note that RouterA will have a primary peer and a backup peer We will first need to configure RouterA's primary remote peer (152.3.7.1) with the DLSW remote−peer statement Next, we will configure RouterA's backup peer (152.3.7.2) The three routers are connected as shown in Figure 24−8 768 Figure 24−8: DLSW backup peers Note For instructions on how to configure a workstation to run NetBEUI, see the section at the end of this chapter Router Configuration The configurations for the three routers in this example are as follows Key DLSW commands are highlighted in bold RouterA Current configuration: ! version 11.2 no service password−encryption no service udp−small−servers no service tcp−small−servers ! hostname RouterA ! source−bridge ring−group 169 ← Define a virtual ring for our DLSW configuration dlsw local−peer peer−id 152.3.8.1 ← Define our Token−Ring interface (T1/0) as our local DLSW peer ID dlsw remote−peer tcp 152.3.7.1 ← Define our remote peer dlsw remote−peer tcp 152.3.7.2 backup−peer 152.3.7.1 ← Define our backup peer ! interface Loopback0 ip address 152.3.3.1 255.255.255.0 ! interface Serial1/0 ip address 152.3.10.5 255.255.255.252 encapsulation ppp no fair−queue ! interface TokenRing1/0 ip address 152.3.8.1 255.255.255.240 ring−speed source−bridge 169 source−bridge spanning ! interface Serial1/1 ip address 152.3.10.1 255.255.255.252 encapsulation ppp ! router ospf 64 network 152.0.0.0 0.255.255.255 area ! no ip classless 769 ! ! line line aux line vty login ! end RouterB Current configuration: ! version 11.2 service timestamps debug uptime service timestamps log uptime no service password−encryption no service udp−small−servers no service tcp−small−servers ! hostname RouterB ! source−bridge ring−group 169 dlsw local−peer peer−id 152.3.7.1 promiscuous ← Only configure a DLSW local peer ID The promiscuous statement will allow RouterB to accept a DLSW peer from any remote peer dlsw bridge−group ← Associate bridge−group with the DLSW virtual ring 169 ! interface Loopback0 ip address 152.3.1.1 255.255.255.0 ! interface Ethernet0/0 ip address 152.3.7.1 255.255.255.192 bridge−group ! interface Serial1/0 ip address 152.3.10.6 255.255.255.252 encapsulation ppp clockrate 800000 ! router ospf 64 network 152.0.0.0 0.255.255.255 area ! ip classless ! ! ! bridge protocol ieee ! line line aux line vty login ! end RouterC Current configuration: ! version 11.2 no service password−encryption no service udp−small−servers 770 no service tcp−small−servers ! hostname RouterC ! source−bridge ring−group 169 dlsw local−peer peer−id 152.3.7.2 promiscuous dlsw bridge−group ! interface Loopback0 ip address 152.3.5.1 255.255.255.0 ! interface Ethernet1/0 ip address 152.3.7.2 255.255.255.192 bridge−group ! interface Serial1/1 ip address 152.3.10.2 255.255.255.252 encapsulation ppp clockrate 800000 ! router ospf 64 network 152.0.0.0 0.255.255.255 area ! no ip classless ! bridge protocol ieee ! line line aux line vty login ! end Monitoring and Testing the Configuration Let's start by connecting to RouterA and typing the show dlsw peer command Notice that peer 152.3.7.1 is in a connected state A DLSW−connected peer indicates that the peer is active and functional We see that there is transmit and receive traffic coming into and out of our peer RouterA#show dlsw peer Peers: state TCP 152.3.7.1 CONNECT TCP 152.3.7.2 DISCONN pkts_rx 1017 pkts_tx 714 type conf conf drops ckts TCP uptime 0 05:01:47 0 − − The show dlsw capabilities command will display information on the remote peer at address 152.3.7.1 Notice that the peer type of the remote peer is listed as being prom This indicates that 152.3.7.1 is a promiscuous peer Recall that we did configure our local peer on RouterB as a promiscuous peer RouterA#show dlsw capabilities DLSw: Capabilities for peer 152.3.7.1(2065) vendor id (OUI) : '00C' (cisco) version number : release number : init pacing window : 20 unsupported saps : none num of tcp sessions : loop prevent support : no icanreach mac−exclusive: no icanreach netbios−excl.: no reachable mac addresses: none reachable netbios names: none cisco version number : peer group number : border peer capable : no 771 peer cost : biu−segment configured : no local−ack configured : yes priority configured : no peer type : prom version string : Cisco Internetwork Operating System Software IOS (tm) 3600 Software (C3620−JS−M), Version 11.2(20)P, Copyright (c) 1986−1999 by Cisco Systems, Inc Compiled Mon 11−Oct−99 21:14 by jaturner RELEASE SOFTWARE (fc1) The show dlsw capabilities local command is used to query key information about the local DLSW peer RouterA#show dlsw capabilities local DLSw: Capabilities for local peer vendor id (OUI) : '00C' (cisco) version number : release number : init pacing window : 20 unsupported saps : none num of tcp sessions : loop prevent support : no icanreach mac−exclusive: no icanreach netbios−excl.: no reachable mac addresses: none reachable netbios names: none cisco version number : peer group number : border peer capable : no peer cost : biu−segment configured : no current border peer : none version string : Cisco Internetwork Operating System Software IOS (tm) 3600 Software (C3620−JS−M), Version 11.2(20)P, Copyright (c) 1986−1999 by Cisco Systems, Inc Compiled Mon 11−Oct−99 21:14 by jaturner RELEASE SOFTWARE (fc1) The show dlsw reachability command will display a list of cached NetBIOS names and MAC addresses Notice that our local workstations' NetBIOS name (SYSTEM1) and our remote workstations' NetBIOS name (SYSTEM2) have been learned and cached by RouterA RouterA#show dlsw reachability DLSw Local MAC address reachability cache list Mac Addr status Loc port 00a0.24fd.c6d0 FOUND LOCAL TokenRing1/0 DLSw Remote MAC Mac Addr 0000.612c.9f32 0007.78da.b08e rif 06B0.0012.0A90 address reachability cache list status Loc Peer FOUND REMOTE 152.3.7.1(2065) FOUND REMOTE 152.3.7.1(2065) DLSw Local NetBIOS Name reachability cache list NetBIOS Name status Loc port SYSTEM1 FOUND LOCAL TokenRing1/0 rif 06B0.0012.0A90 DLSw Remote NetBIOS Name reachability cache list NetBIOS Name status Loc Peer SYSTEM2 FOUND REMOTE 152.3.7.1(2065) max−lf(17800) Now switch to RouterB The show dlsw peer command indicates that we have a connected peer at address 152.3.8.1 This is RouterA Notice that the peer type is promiscuous This is because we did not configure a remote peer on RouterB We only configured RouterB with a local peer ID and the promiscuous option RouterB#show dlsw peer 772 Peers: TCP 152.3.8.1 state CONNECT pkts_rx 765 pkts_tx 1071 type prom drops ckts TCP uptime 05:05:18 The show dlsw reachability command on RouterB shows us that RouterB has learned and locally cached both of our workstations' NetBIOS names RouterB#show dlsw reachability DLSw Local MAC address reachability cache list Mac Addr status Loc port 0000.612c.9f32 FOUND LOCAL TBridge−002 rif −−no rif−− DLSw Remote MAC address reachability cache list Mac Addr status Loc Peer 00a0.24fd.c6d0 FOUND REMOTE 152.3.8.1(2065) max−lf(1500) DLSw Local NetBIOS Name reachability cache list NetBIOS Name status Loc port SYSTEM2 FOUND LOCAL TBridge−002 rif −−no rif−− DLSw Remote NetBIOS Name reachability cache list NetBIOS Name status Loc Peer SYSTEM1 FOUND REMOTE 152.3.8.1(2065) max−lf(1500) The show dlsw capabilities command shows the peer capabilities of our remote peer at IP address 152.3.8.1 Notice that our remote peer is a configured peer and not a promiscuous peer This is because we configured this peer with a remote peer statement RouterB#show dlsw capabilities DLSw: Capabilities for peer 152.3.8.1(2065) vendor id (OUI) : '00C' (cisco) version number : release number : init pacing window : 20 unsupported saps : none num of tcp sessions : loop prevent support : no icanreach mac−exclusive: no icanreach netbios−excl.: no reachable mac addresses: none reachable netbios names: none cisco version number : peer group number : border peer capable : no peer cost : biu−segment configured : no local−ack configured : yes priority configured : no peer type : conf version string : Cisco Internetwork Operating System Software IOS (tm) 3600 Software (C3620−JS−M), Version 11.2(20)P, Copyright (c) 1986−1999 by Cisco Systems, Inc Compiled Mon 11−Oct−99 21:14 by jaturner RELEASE SOFTWARE (fc1) Now connect to RouterC The show dlsw peer command indicates that there are no active DLSW peers This is due to the fact that RouterC has been configured as a backup peer Since the primary DLSW peer between RouterA and RouterB is still active, the backup peer has not been activated RouterC#show dlsw peer Peers: state pkts_rx pkts_tx type drops ckts TCP The show dlsw capabilities command confirms that there are no active remote peers RouterC#show dlsw capabilities 773 uptime ... udp−small−servers service tcp−small−servers ! hostname Cisco2 500 ! enable password cisco ← Enable password ! line password cisco ← Login password login line aux transport input all line vty login... udp−small−servers no service tcp−small−servers ! hostname Cisco3 620 ! enable password cisco ← Enable Password ! no ip classless ! line password cisco ← Login Password login line aux line vty login... Cisco Internetwork Operating System Software IOS (tm) 3600 Software (C3620−I−M), Version 11.3(8)T1, RELEASE SOFTWARE (fc1) Copyright (c) 198 6− 199 9 by cisco Systems, Inc Compiled Thu 11−Feb? ?99