Troubleshooting IBM

SDLC primaries and secondaries can be connected in four basic configurations:

Since its initial proposal, IBM has offered a new bridging standard to the IEEE 802 committee: the source-route transparent (SRT) bridging solution. SRT bridging eliminates pure SRBs entirely, proposing that the two types of LAN bridges be transparent bridges and SRT bridges. Although SRT bridging has support, SRBs are still widely deployed.

In most cases, the path contained in the first frame received will be used.

The fields of the RIF are as follows:

• The routing control field, which consists of the following subfields:

  • The type subfield in the RIF indicates whether the frame should be routed to a single node, a group of nodes that make up a spanning tree of the internetwork, or all nodes. The first type is called a specifically routed frame; the second type is called a spanning- tree explorer; and the third type is called an all-paths explorer. The spanning-tree explorer can be used as a transit mechanism for multicast frames. It can also be used as a replacement for the all-paths explorer in outbound route queries. In this case, the destination responds with an all-paths explorer.

  • The length subfield indicates the total length (in bytes) of the RIF.

  • The D bit indicates the direction of the frame (forward or reverse).

  • The largest field indicates the largest frame that can be handled along this route.

• The route descriptor field, of which there can be more than one. Each route descriptor field carries a ring number/bridge number pair that specifies a portion of a route. Routes, then, are simply alternating sequences of LAN and bridge numbers that start and end with LAN numbers.

Possible Problem	Solution
Ring number mismatch	A router interface configured for bridging fails to insert into a ring when it detects a ring number mismatch, and posts an error message to the console. Step 1 Get the ring number (specified in hexadecimal) from IBM SRBs (either by examining the configuration of other SRBs or from the system administrator). Step 2 Use the show running-config privileged exec command to view the configuration of routers configured as SRBs. Look for source-bridge interface configuration command entries that assign ring numbers (displayed in decimal) to the rings that are connected to the router's interfaces.1 For example, the following configuration entry shows the entry for local ring 10, bridge number 500, and remote ring 20: source-bridge 10 500 20 Note: Parallel bridges situated between the same two rings must have different bridge numbers. Step 3 Convert IBM SRB ring numbers to decimal and verify that the ring numbers configured on all internetworking nodes agree. Step 4 If the ring numbers do not agree, reconfigure the router interface or IBM SRBs so that the ring numbers match. Use the source-bridge command to make configuration changes; the syntax is as follows: source-bridge source-ring-number bridge-number target-ring-number [conserve-ring] Syntax Description: source-ring-number---Ring number for the interface's Token Ring or FDDI2 ring. It must be a decimal number in the range 1 to 4095 that uniquely identifies a network segment or ring within the bridged Token Ring or FDDI network
Ring number mismatch	bridge-number---Number that uniquely identifies the bridge connecting the source and target rings. It must be a decimal number in the range 1 to 15. target-ring-number---Ring number of the destination ring on this router. It must be unique within the bridged Token Ring or FDDI network. The target ring can also be a ring group. Must be a decimal number. conserve-ring---(Optional) Keyword to enable SRB over Frame Relay. When this option is configured, the SRB software does not add the ring number associated with the Frame Relay PVC3, the partner's virtual ring) to outbound explorer frames. This option is permitted for Frame Relay subinterfaces only. Example: In the following example, Token Rings 129 and 130 are connected via a router: interface tokenring 0 source-bridge 129 1 130 ! interface tokenring 1 source-bridge active 130 1 129
End system does not support RIF4	Step 1 Place a network analyzer on the same ring to which the end system is connected. Step 2 Look for RIF frames sent from the end system (RIF frames have the high-order bit of the source MAC5 address set to 1). Step 3 If no RIF frames are found, the end system does not support RIF and cannot participate in source routing. If the protocol is routable, you can route the protocol or configure transparent bridging. If you use transparent bridging, be careful not to create loops between the SRB and the transparent bridging domains. Step 4 If your environment requires SRB, contact your workstation or server vendor for SRB drivers or for information about setting up your workstation or server to support SRB.
Hop count exceeded	Use the show protocol route command to check the hop count values on routers and bridges in the path. Packets that exceed the hop count are dropped. Alternatively, you can enable the debug source event privileged exec command to see whether packets are being dropped because the hop count has been exceeded. Caution: Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, it is best to use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use. Increase the hop count if it is less than the default value, 7. Otherwise, the network must be redesigned so that no destination is more than 7 hops away.
Router is not configured to forward spanning explorers	Spanning explorer packets are equivalent to a single-route broadcast. Routers must therefore be configured to route them. Step 1 Use the show source-bridge exec command to determine whether the spanning explorer count is incrementing. Step 2 If the spanning explorer count is not incrementing, use the show running-config privileged exec command on routers to see whether the source-bridge spanning interface configuration command is configured. This command configures the router to forward spanning explorers. Step 3 If the command entry is not present in the configuration, add it to any router that is required to pass spanning explorers. The command syntax is as follows: source-bridge spanning bridge-group [path-cost path-cost] Syntax Description: bridge-group---Number in the range 1 to 9 that you choose to refer to a particular group of bridged interfaces. path-cost---(Optional) Path cost for a specified interface. path-cost---(Optional) Path cost for the interface. The valid range is 0 to 65535. Example: The following example adds Token Ring 0 to bridge group 1 and assigns a path cost of 12 to Token Ring 0: interface tokenring 0 source-bridge spanning 1 path-cost 12 Step 4 Use the show source-bridge exec command to determine whether explorers are being sent. Step 5 If explorers are not being sent, place a network analyzer on the same ring to which the end system is connected. Step 6 If you find spanning all-ring frames, use the show running-config privileged exec command to make sure the router is properly configured. If sessions still cannot be established over the SRB, contact your technical support representative for more assistance.

1Although you can enter the ring number in hexadecimal or decimal, it always appears in the configuration as a decimal number. 2FDDI = Fiber Distributed Data Interface 3PVC= permanent virtual circuit 4RIF = routing information field 5MAC = Media Access Control

Possible Problem	Solution
Routing problem	For detailed information on troubleshooting routing problems, refer to the chapters in this book that cover the routing protocols in question. For example, if you are running Novell IPX, see Chapter 8, "Troubleshooting Novell IPX."
Missing multiring command	Step 1 Use the show running-config privileged exec command on the router. Look for a multiring interface configuration command entry. This command enables the collection and use of RIF information on router interfaces. Step 2 If the multiring command is not present, add the command to the configuration using the following command: C4000(config-if)#multiring all
Incomplete ARP1 table	Step 1 Determine whether you can ping hosts. Step 2 If the host does not respond, use the show arp exec command to determine whether an entry for the host exists in the ARP table. Step 3 If an entry exists, there is probably a routing problem. Determine whether you have a source-route path to the destination hardware (MAC) address. Use the show rif exec command to match the RIF with the hardware address of the host. Step 4 If no entry exists, use a network analyzer to see whether ARP requests are getting through to the remote ring and to see whether replies come back.

1ARP = Address Resolution Protocol

Possible Problem	Solution
Missing or misconfigured source-bridge remote-peer command on the router	Step 1 Use the show source-bridge exec command to check for remote peers. If the output shows that peers are open, refer to the section "RSRB: Host Cannot Connect to Server (Peers Open)" later in this chapter. Step 2 If the output shows that peers are not open, use the show running-config privileged exec command to view the router configuration. Verify that there are two source-bridge remote-peer global configuration command entries present---one should point to the IP address of the local router and the other should point to the IP address of the remote router. Step 3 If either or both of the commands are missing or point to the wrong address, add or modify the commands as required. For detailed information about configuring routers for RSRB, see the Cisco IOS Bridging and IBM Networking Configuration Guide and Bridging and IBM Networking Command Reference.
No route to the remote peer	If you are using TCP1 or FST2 encapsulation between the local and remote SRB, follow these steps: Step 1 Test IP connectivity using the extended ping privileged exec command. Use the local peer ID as the source address and the remote peer ID as the destination address. Step 2 If the ping fails, use the show ip route exec command to view the IP routing table. Step 3 If the show ip route output does not show a route to the intended remote peer, there is probably an IP routing problem or a problem with the hardware or cabling in the path from the local to the remote SRB. For information on troubleshooting IP routing, refer to Chapter 7, "Troubleshooting TCP/IP." For information about troubleshooting hardware problems, see Chapter 3, "Troubleshooting Hardware and Booting Problems."
Serial link problem	If there is a direct connection between the local and remote SRB (that is, you are not using FST or TCP encapsulation), follow these steps: Step 1 Check to make sure that the next hop router is directly adjacent. Step 2 If the router is adjacent, perform other tests to ensure that the link is functioning properly. For more information, refer to Chapter 15, "Troubleshooting Serial Line Problems." Step 3 If the next hop is not directly adjacent, redesign your network so that it is.
End system not generating explorer traffic	Step 1 Use the show source-bridge privileged exec command to see whether the explorer count is incrementing. Step 2 If the explorer count is not incrementing, use the show running-config privileged exec command to view the router configuration. Check for a source-bridge spanning interface configuration command on the local and remote routers. Step 3 If the source-bridge spanning command is not configured on the routers, configure it on the interfaces connecting the local and remote SRBs. This command is required if the end system is using single-route explorers. The command syntax is as follows: source-bridge spanning bridge-group [path-cost path-cost] Syntax Description: bridge-group---Number in the range 1 to 9 that you choose to refer to a particular group of bridged interfaces. path-cost---(Optional) Path cost for a specified interface. path-cost---(Optional) Path cost for the interface. The valid range is 0 to 65535. Example: The following example adds Token Ring 0 to bridge group 1 and assigns a path cost of 12 to Token Ring 0: interface tokenring 0 source-bridge spanning 1 path-cost 12
Encapsulation mismatch	Step 1 Use the show interfaces exec command to verify that the interface and line protocol are up. If the status line indicates any other state, refer to Chapter 15, "Troubleshooting Serial Line Problems." Step 2 Verify that the configured encapsulation type matches the requirements of the network to which the serial interface is attached. For example, if the serial interface is attached to a leased line but the configured encapsulation type is Frame Relay, there is an encapsulation mismatch. Step 3 To resolve the mismatch, change the encapsulation type on the serial interface to the type appropriate for the attached network.
Hop count exceeded	Step 1 Use the show protocol route command to check the hop count values on routers and bridges in the path. Packets that exceed the hop count are dropped. Alternatively, you can enable the debug source event privileged exec command to see whether packets are being dropped because the hop count has been exceeded. Caution: Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, it is best to use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use. Step 2 Increase the hop count if it is less than the default value, 7. Otherwise, the network must be redesigned so that no destination is greater than 7 hops away.

1TCP = Transmission Control Protocol 2FST = Fast Sequenced Transport

Possible Problem	Solution
End system misconfiguration	Step 1 If the end system is on the ring local to the router, use the show lnm station privileged exec command on the local router. This command lists the stations on the local ring. The following is an example of the show lnm station command: show lnm station [address] Syntax Description: address---(Optional) Address of a specific LNM1 station. Sample Display: The following is sample output from the show lnm station command when a particular address (in this case, 1000.5abc15) has been specified: Router# show lnm station 1000.5a6f.bc15 isolating error counts station int ring loc. weight line inter burst ac abort 1000.5a6f.bc15 T1 0001 0000 00 - N 00000 00000 00000 00000 00000 Unique ID: 0000.0000.0000 NAUN: 0000.3000.abc4 Functional: C000.0000.0000 Group: C000.0000.0000 Physical Location: 00000 Enabled Classes: 0000 Allowed Priority: 00000 Address Modifier: 0000 Product ID: 00000000.00000000.00000000.00000000.0000 Ucode Level: 00000000.00000000.0000 Station Status: 00000000.0000 Last transmit status: 00
End system misconfiguration	Step 2 Check the command output for the MAC address of the workstation or server. If the MAC address is not present in the output, check the configuration of the end system. Step 3 If the problem persists, use a network analyzer to check network traffic generated by the end system. If you do not have a network analyzer, use the debug token-ring and the debug source-bridge commands. Caution: Using the debug token-ring and the debug source-bridge commands on a heavily loaded router is not advised. These commands can cause further network degradation or complete network failure if not used judiciously. Step 4 Check the output of the debug commands to see whether the end system is sending traffic to the correct MAC addresses or destination names (in the case of NetBIOS).
End system does not support RIF	Step 1 Place a network analyzer on the same ring to which the end system is connected. Step 2 Look for RIF frames sent from the end system (RIF frames have the high-order bit of the source MAC address set to 1). Step 3 If no RIF frames are seen, the end system does not support RIF and cannot participate in source routing. If the protocol is routable, you can route the protocol or configure transparent bridging. If you use transparent bridging, be careful not to create loops between the SRB and the transparent bridging domains. Step 4 If your environment requires SRB, contact your workstation or server vendor for SRB drivers or for information about setting up your workstation or server to support SRB.
Explorer traffic not reaching remote ring	Step 1 Using a network analyzer or the debug source-bridge command, watch network traffic to see whether explorers from the end system reach the remote ring. Step 2 If traffic reaches the remote ring successfully, check the configuration of the destination end system (for example, a server) to see why that station does not reply to the explorer traffic from the source. If traffic does not reach the remote ring, use the show source-bridge command to check ring lists. If information about the ring has not been learned, check router configurations. Step 3 If you are using NetBIOS, use the show netbios name-cache exec command to see whether traffic is passing through the network properly. If it is not, check router configurations. For detailed information about configuring routers for RSRB, refer to the Cisco  IOS Bridging and IBM Networking Configuration Guide and Bridging and IBM Networking Command Reference.

1LNM = LAN Network Manager

Possible Problem	Solution
Incorrect mapping of NetBIOS name cache server-to- client mapping	Step 1 For each router on which NetBIOS name caching is enabled, use the show rif exec command to determine whether the RIF entry shows the correct path from the router to both the client and the server. The following is an example of the show rif exec command: cantatrice#show rif Codes: * interface, - static, + remote Hardware Addr How Idle (min) Routing Information Field 5C02.0001.4322 rg5 - 0630.0053.00B0 5A00.0000.2333 TR0 3 08B0.0101.2201.0FF0 5B01.0000.4444 - - - 0000.1403.4800 TR1 0 - 0000.2805.4C00 TR0 * - 0000.2807.4C00 TR1 * - 0000.28A8.4800 TR0 0 - 0077.2201.0001 rg5 10 0830.0052.2201.0FF0 In this display, entries marked with an asterisk (*) are the router's interface addresses. Entries marked with a dash (-) are static entries. Entries with a number denote cached entries. If the RIF timeout is set to something other than the default, 15 minutes, the timeout is displayed at the top of the display. Step 2 Use the show running-config privileged exec command to view the router configuration. Make sure that the source-bridge proxy-explorer interface configuration command is included in the Token Ring configuration. Proxy explorers must be enabled on any interface that uses NetBIOS name caching. Step 3 Use the show netbios-cache exec command to see whether the NetBIOS cache entry shows the correct mappings of server and client names to MAC addresses.
Incorrect mapping of NetBIOS name cache server-to- client mapping	The following is an example of the show netbios-cache exec command: cantatrice#show netbios-cache HW Addr Name How Idle NetBIOS Packet Savings 1000.5a89.449a IC6W06_B TR1 6 0 1000.5a8b.14e5 IC_9Q07A TR1 2 0 1000.5a25.1b12 IC9Q19_A TR1 7 0 1000.5a25.1b12 IC9Q19_A TR1 10 0 1000.5a8c.7bb1 BKELSA1 TR1 4 0 1000.5a8b.6c7c ICELSB1 TR1 - 0 1000.5a31.df39 ICASC_01 TR1 - 0 1000.5ada.47af BKELSA2 TR1 10 0 1000.5a8f.018a ICELSC1 TR1 1 0 The following are the fields reported by the show netbios-cache command: show netbios---Cache field descriptions HW Addr---MAC address mapped to the NetBIOS name in this entry. Name---NetBIOS name mapped to the MAC address in this entry. How---Interface through which this information was learned. Idle---Period of time (in seconds) since this entry was last accessed. A hyphen in this column indicates that it is a static entry in the NetBIOS name cache. NetBIOS Packet Savings---Number of packets to which local replies were made (thus preventing transmission of these packets over the network). Step 4 Use the show running-config privileged exec command at each router to examine the mapping of addresses specified in netbios name-cache global configuration command entries. The following example shows a configuration in which the NetBIOS server is accessed remotely: source-bridge ring-group 2 rif 0110.2222.3333 0630.021.0030 ring group 2 netbios name-cache 0110.2222.3333 DEF ring-group 2
Misconfigured source-bridge command	Step 1 For each router on which NetBIOS name caching is enabled, use the show source-bridge command to obtain the version of the remote connection. The value specified should be 2 or 3. If the value is 1, connections will not get through, and you must modify your configuration. Example: The following is sample output from the show source-bridge command: Router# show source-bridge Local Interfaces: receive transmit srn bn trn r p s n max hops cnt cnt drops TR0 5 1 10 * * 7 39:1002 23:62923 Ring Group 10: This peer: TCP 150.136.92.92 Maximum output TCP queue length, per peer: 100 Peers: state lv pkts_rx pkts_tx expl_gn drops TCP TCP 150.136.92.92 - 2 0 0 0 0 0 TCP 150.136.93.93 open 2* 18 18 3 0 0 Rings: bn: 1 rn: 5 local ma: 4000.3080.844b TokenRing0 fwd: 18 bn: 1 rn: 2 remote ma: 4000.3080.8473 TCP 150.136.93.93 fwd: 36 Explorers: ------- input ------- ------- output ------- spanning all-rings total spanning all-rings total TR0 0 3 3 3 5 8 Router# Step 2 If the router is running a software release prior to Cisco IOS Release 10.0, specify either version 2 or version 3 in the source-bridge remote-peer interface configuration command. The syntax is as follows: source-bridge remote-peer ring-group tcp ip-address [lf size] [local-ack] [priority] [version number] If the router is running Cisco IOS Release 10.0 or later, the specification of a version is ignored. For more information, refer to the Cisco IOS Bridging and IBM Networking Configuration Guide and Bridging and IBM Networking Command Reference.

Possible Problem	Solution
Media problem	Verify the line using the show interfaces exec command. If the interface or line protocol is down, troubleshoot the media. For LAN media, refer to the chapter that covers your media type.
Ethernet-to-Token Ring address mapping is misconfigured	Step 1 Use the show bridge exec command to verify the existence of the Ethernet station. Ethernet and Token Ring addresses use opposite bit ordering schemes. The Token Ring address 0110.2222.3333 is equivalent to the Ethernet address 8008.4444.cccc.
Ethernet-to-Token Ring address mapping is misconfigured	Step 2 Use the show spanning exec command to determine whether the Ethernet port is in forwarding mode. Example: The following is sample output from the show span command: RouterA> show span Bridge Group 1 is executing the IBM compatible spanning tree protocol Bridge Identifier has priority 32768, address 0000.0c0c.f68b Configured hello time 2, max age 6, forward delay 4 Current root has priority 32768, address 0000.0c0c.f573 Root port is 001A (TokenRing0/0), cost of root path is 16 Topology change flag not set, detected flag not set Times: hold 1, topology change 30, notification 30 hello 2, max age 6, forward delay 4, aging 300 Timers: hello 0, topology change 0, notification 0 Port 001A (TokenRing0/0) of bridge group 1 is forwarding. Path cost 16 Designated root has priority 32768, address 0000.0c0c.f573 Designated bridge has priority 32768, address 0000.0c0c.f573 Designated port is 001B, path cost 0, peer 0 Timers: message age 1, forward delay 0, hold 0 Port 002A (TokenRing0/1) of bridge group 1 is blocking. Path cost 16 Designated root has priority 32768, address 0000.0c0c.f573 Designated bridge has priority 32768, address 0000.0c0c.f573 Designated port is 002B, path cost 0, peer 0 Timers: message age 0, forward delay 0, hold 0 Port 064A (spanRSRB) of bridge group 1 is disabled. Path cost 250 Designated root has priority 32768, address 0000.0c0c.f573 Designated bridge has priority 32768, address 0000.0c0c.f68b Designated port is 064A, path cost 16, peer 0 Timers: message age 0, forward delay 0, hold 0 A port (spanRSRB) is created with each virtual ring group. The port is disabled until one or more peers go into open state in the ring group.
Ethernet-to-Token Ring address mapping is misconfigured	Step 3 Use the show rif exec command to determine whether the target Token Ring station is visible on the internetwork. When configured for translational bridging, the router extracts the RIF of a packet received from the Token Ring network and saves it in a table. The router then transmits the packet on the Ethernet network. Later, the router reinserts the RIF when it receives a packet destined for the originating node on the Token Ring side. Example: The following is sample output from the show rif command: Router# show rif Codes: * interface, - static, + remote Hardware Addr How Idle (min) Routing Information Field 5C02.0001.4322 rg5 - 0630.0053.00B0 5A00.0000.2333 TR0 3 08B0.0101.2201.0FF0 5B01.0000.4444 - - - 0000.1403.4800 TR1 0 - 0000.2805.4C00 TR0 * - 0000.2807.4C00 TR1 * - 0000.28A8.4800 TR0 0 - 0077.2201.0001 rg5 10 0830.0052.2201.0FF0 Step 4 If Ethernet and Token Ring end systems are visible, statically configure any relevant server MAC addresses in the client configurations so that clients can listen to the server advertisements directly. One case in which static mapping is required is when bridging DEC LAT traffic over a translational bridge. LAT services on Ethernet are advertised on a multicast address that is mapped by some translational bridges to a broadcast address on the Token Ring side. Routers do not support this mapping.
Vendor code mismatch	Older Token Ring implementations require that the vendor code (OUI1 field) of the SNAP2 header be 000000. Cisco routers modify this field to be 0000F8 to specify that the frame was translated from Ethernet Version 2 to Token Ring. This can cause problems on older Token Ring networks. Specify the ethernet-transit-oui interface configuration command to force the router to make the vendor code field 000000. This change is frequently required when there are IBM 8209s (IBM Token Ring-to-Ethernet translating bridges) in the network. The following is an example of the ethernet-transit-oui command: ethernet-transit-oui [90-compatible | standard | cisco] Syntax Description: 90-compatible---OUI used 0000F8 by default, when talking to other Cisco routers. Provides the most flexibility. standard---OUI used 000000 when talking to IBM 8209 bridges and other vendor equipment. Does not provide for as much flexibility as the other two choices. cisco---OUI used 00000C, provided for compatibility with future equipment. Example: The following example specifies Cisco's OUI form: interface tokenring 0 ethernet-transit-oui cisco
Cisco and non-Cisco translational bridges in parallel	Step 1 Check for translational bridges in parallel with the Cisco translational bridge. If there are any parallel non-Cisco translational bridges, loops will probably be created. Step 2 Because implementing translational bridging defeats the spanning-tree mechanism of both transparent bridging and SRB environments, you must eliminate all loops caused by inserting the translational bridge. A transparent spanning tree and a source-bridge spanning tree cannot communicate with one another.
Trying to bridge protocols that embed MAC addresses in the Information field of the MAC frame (such as IP ARP3, Novell IPX, or AARP4)	If MAC addresses are embedded in the Information field of the MAC frame, bridges will be unable to read the address. Bridges will therefore be unable to forward the traffic. Step 1 If you are attempting to bridge this type of protocol, route the protocol instead. Step 2 If you still cannot communicate over the router, contact your technical support representative.

1OUI = organizational unique identifier 2SNAP = Subnetwork Access Protocol 3ARP = Address Resolution Protocol 4AARP = AppleTalk Address Resolution Protocol

Possible Problem	Solution
Trying to bridge frames containing RIF from Token Ring network to Ethernet network over an SRT bridge	Use translational bridging instead of SRT bridging to allow SRB-to-transparent bridging translation. Because SRT bridging works only between Ethernet and Token Ring, any packet containing a RIF is dropped when SRT bridging is used.
Attempting to transfer large frame sizes	Problems will occur if Token Ring devices transmit frames exceeding the Ethernet MTU1 of 1500 bytes. Configure hosts on the Token Ring to generate frame sizes less than or equal to the Ethernet MTU.
Trying to bridge protocols that embed the MAC address in the Information field of the MAC frame (such as IP ARP, Novell IPX, or AARP)	If MAC addresses are embedded in the Information field of the MAC frame, bridges will be unable to read the address. Bridges will therefore be unable to forward the traffic. Step 1 If you are attempting to bridge this type of protocol, route the protocol instead. Step 2 If you still cannot communicate over the router, contact your technical support representative.
Media problem	Verify the line using the show interfaces exec command. If the interface or line protocol is down, troubleshoot the media. For LAN media, refer to the chapter that covers your media type.

1MTU = maximum transmission unit

Possible Problem	Solution
Physical layer problem	Step 1 Use the show interfaces exec command to determine whether the interface and line protocol are up. Step 2 If the interface and line protocol are both up, troubleshoot link-layer problems as described later in this table. Step 3 If the output does not indicate up/up, make sure the device is powered on. Make sure all cabling is correct, securely connected, and undamaged. Make sure the cabling does not exceed the recommended length for the speed of the connection. Step 4 If the interface or line protocol is still down, use a breakout box to check the signals on the line.
Physical layer problem	Note: On some Cisco platforms, such as the Cisco 7000 running a recent Cisco IOS release, the output of the show interfaces command will indicate the state of line signals. If the router is full-duplex DCE1, check for DTR2 and RTS3. If these signals are not high, proceed to Step 5. If these signals are high, the interface should be up. If it is not, contact your technical support representative. On a Cisco 7000, if the breakout box shows that the DTR and DTS signals are high but the show interfaces command shows that they are not, check the router cabling. In particular, make sure that the 60-pin high-density cable is not plugged in to the router upside-down. If the router is half-duplex DCE, check for DTR. If DTR is not high, proceed to Step 5. If DTR is high, the interface should be up. If it is not, contact your technical support representative. Note: Half-duplex is not supported on Cisco 7000 series routers. If the router is full- or half-duplex DTE, check for CD. If CD is not high, proceed to Step 5. If CD is high, the interface should be up. If it is not, contact your technical support representative. Step 5 If the router is full-duplex DCE, make sure the device is configured for permanent RTS high. If the device does not allow you to configure permanent RTS, set the signal high by strapping DTR from the device side to RTS on the router side (see Figure 10-5). Step 6 If the router is DCE, it is typical to be required to provide clock to the device. Make sure the clock rate interface configuration command is present in the router configuration. Use the show running-config privileged exec command on the router to view the interface configuration. The following example shows the clock rate information for interface serial 0.
Physical layer problem	Example: The following example sets the clock rate on the first serial interface to 64000 bits per second: interface serial 0 clock rate 64000 If the router is DTE, it should get clock from an external device. Make sure that a device is providing clock properly. Make sure that the clocking source is the same for all devices.
Link-layer problem (router is primary)	Step 1 Use the debug sdlc privileged exec command4 to see whether the router is sending SNRMs.5 Caution: Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, it is best to use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use. Step 2 If the router is not sending SNRMs, check the physical layer (see the preceding problem in this table). If the router is sending SNRMs, the device should send UAs6 in reply. Step 3 If the device is not sending UAs, make sure the addresses of the router and device are correct. Step 4 If you are using a V.35 connection, make sure that the SCT/SCTE7 setting is correct on the interface. The router should use SCTE if the router is DCE, and SCT if the router is DTE. The SCT/SCTE setting might be changed with a jumper or with the software configuration command dce-terminal-timing enable, depending on the platform. Some platforms do not allow you to change this setting.
Link-layer problem (router is primary)	Example: The following example prevents phase shifting of the data with respect to the clock: interface serial 0 dce-terminal-timing enable Step 5 Make sure that the device and the router are using the same signal coding (NRZ8 or NRZI9). NRZ is enabled by default on the router. To enable NRZI encoding, use the nrzi-encoding interface configuration command. Example: In the following example, serial interface 1 is configured for NRZI encoding: interface serial 1 nrzi-encoding Step 6 Try reducing the line speed to 9600 bps using the clock rate interface configuration command. Use the clock rate interface configuration command to configure the clock rate for the hardware connections on serial interfaces such as NIMs10 and interface processors to an acceptable bit rate. Syntax: The following is the syntax of the clock rate command: clock rate bps Syntax Description: bps---Desired clock rate in bits per second: 1200, 2400, 4800, 9600, 19200, 38400, 56000, 64000, 72000, 125000, 148000, 250000, 500000, 800000, 1000000, 1300000, 2000000, 4000000, or 8000000. Example: The following example sets the clock rate on the first serial interface to 64,000 bits per second: interface serial 0 clock rate 64000 Step 7 Make sure that cabling is correct, securely attached, and undamaged.
Link-layer problem (router is secondary)	Step 1 Use the debug sdlc privileged exec command to see whether the router is receiving SNRMs. Caution: Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, it is best to use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use. Step 2 If the router is not receiving SNRMs, check the primary device. Make sure the physical layer is operational (see the problem "Physical layer problem" in this table). If the router is receiving SNRMs, it should send UAs in reply. Step 3 If the router is not sending UAs, make sure the addresses of the router and device are correct. Step 4 If you are using a V.35 connection, make sure that the SCT/SCTE setting is correct on the interface. The router should use SCTE if the router is DCE and SCT if the router is DTE. The SCT/SCTE setting might be changed with a jumper or with the software configuration command dce-terminal-timing enable, depending on the platform. Some platforms do not allow you to change this setting. Example: The following example prevents phase shifting of the data with respect to the clock: interface serial 0 dce-terminal-timing enable Step 5 Use a breakout box to check for CTS high on the line. Step 6 Make sure that both the device and the router are using the same signal coding (NRZ or NRZI). NRZ is enabled by default on the router. To enable NRZI encoding, use the nrzi-encoding interface configuration command.
Link-layer problem (router is secondary)	Example: In the following example, serial interface 1 is configured for NRZI encoding: interface serial 1 nrzi-encoding Step 7 Try reducing the line speed to 9600 bps using the clock rate interface configuration command. Use the clock rate interface configuration command to configure the clock rate for the hardware connections on serial interfaces such as NIMs and interface processors to an acceptable bit rate. Syntax: The following is the syntax of the clock rate command: clock rate bps Syntax Description: bps---Desired clock rate in bits per second: 1200, 2400, 4800, 9600, 19200, 38400, 56000, 64000, 72000, 125000, 148000, 250000, 500000, 800000, 1000000, 1300000, 2000000, 4000000, or 8000000. Example: The following example sets the clock rate on the first serial interface to 64000 bits per second: interface serial 0 clock rate 64000 Step 8 Make sure that cabling is correct, securely attached, and undamaged.

1DCE = full-duplex data communications 2DTR = data terminal ready 3RTS = request to send 4To reduce the amount of screen output produced by the debug sdlc command, configure the sdlc poll-pause-timer 1000 command to reduce the frequency at which the router sends poll frames. Remember to return this command to its original value (the default is 10 milliseconds). 5SNRM = send normal response mode 6UA = unnumbered acknowledgment 7SCT/SCTE = serial clock transmit/serial clock transmit external 8NRZ = nonreturn to zero 9NRZI = nonreturn to zero inverted 10NIM = network interface module

Possible Problem

Solution

SDLC timing problems

Step 1 Place a serial analyzer on the serial line attached to the source station and monitor packets. Step 2 If duplicate packets appear, check the router configuration using the show running-config privileged exec command. Check to see whether the local-ack keyword is present in the configuration. Step 3 If the local-ack keyword is missing, add it to the router configuration for SDLC interfaces. Step 4 Local acknowledgment parameters can be adjusted in the router, the attached device, or both. Adjust SDLC protocol parameters as appropriate. These parameters are used to customize SDLC transport over various network configurations. In particular, you might need to tune various LLC2 timer values. The following is a sample configuration using the local-ack command: interface Serial 1 mtu 4400 no ip address hold-queue 150 in encapsulation stun stun group 1 stun sdlc-role primary sdlc line-speed 19200 sdlc n1 35200 sdlc address 04 echo stun route address 4 tcp 156.28.11.1 local-ack clockrate 19200 For more information about configuring SDLC, refer to the Cisco IOS Bridging and IBM Networking Configuration Guide and Bridging and IBM Networking Command Reference.

Possible Problem	Solution
SDLC physical or data link-layer problem	Step 1 Use the show interface slot/port exec command to check the state of the connection with the SDLC device. Step 2 Look for USBUSY in the output, which indicates that the router is attempting to establish an LLC connection. If the router is not USBUSY, make sure that the physical and link layers are working properly. For more information, refer to the section "SDLC: Router Cannot Communicate with SDLC Device" earlier in this chapter. Step 3 If the router is USBUSY, proceed to the next problem in this table.
Router not sending test frames to FEP1	Step 1 With the debug sdllc and debug llc2 packet privileged exec commands enabled on the router, check whether the router is sending test frames to the FEP. Caution: Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, it is best to use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use. Step 2 If the router is sending test frames to the FEP, proceed to the next problem in this table. Step 3 If the router is not sending test frames to the FEP, use the show running-config privileged EXEC command to view the router configuration. Make sure that the sdllc partner interface configuration command is present. Step 4 If the sdlc partner command is not present, add it to the configuration. Make sure that it points to the hardware address of the FEP on the Token Ring. The following is the syntax for the sdlc partner command: sdlc partner mac-address sdlc-address Syntax Description: mac-address--- 48-bit MAC address of the Token Ring host. sdlc-address---SDLC address of the serial device that will communicate with the Token Ring host. The valid range is 1 to FE.
FEP on Token Ring not replying to test frames	Step 1 With the debug sdllc and debug llc2 packet privileged exec commands enabled on the router, check whether the FEP is replying to test frames sent by the router. Caution: Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, it is best to use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use. Step 2 If the FEP is responding, proceed to the next problem in this table. Step 3 If the FEP is not responding, check the MAC address of the router's partner (the FEP). Make sure that the address is correctly specified in the sdllc partner command entry on the router. The following is the syntax of the sdlc partner command: sdlc partner mac-address sdlc-address Syntax Description: mac-address---48-bit MAC address of the Token Ring host. sdlc-address---SDLC address of the serial device that will communicate with the Token Ring host. The valid range is 1 to FE. Step 4 Check whether RSRB peers are up. If the peers are not open, refer to the section "RSRB: Host Cannot Connect to Server (Peers Not Open)" earlier in this chapter. Step 5 If the RSRB peers are up, attach a network analyzer to the Token Ring with the FEP attached and make sure that the router's test frames are arriving on the ring and that the FEP is replying.
XID2 not sent by router	Step 1 With the debug sdllc and debug llc2 packet privileged exec commands enabled on the router, check whether the router is sending XID frames to the FEP. Caution: Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, it is best to use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use. Step 2 If the router is sending XID frames to the FEP, proceed to the next problem in this table. Step 3 If the router is not sending XID frames, use the show running-config privileged exec command to view the router configuration. Make sure there is an sdllc xid interface configuration command entry present. Step 4 If the sdllc xid command is not configured on the router, add it to the configuration. The following is the syntax for the sdlc xid command: sdlc xid address xid Syntax Description: address---Address of the SDLC station associated with this interface. xid---XID the Cisco IOS software will use to respond to XID requests the router receives. This value must be 4 bytes (8 digits) in length and is specified with hexadecimal digits. Example: The following example specifies an XID value of 01720002 at address C2: interface serial 0 sdlc xid c2 01720002
FEP not replying to XID	Step 1 With the debug sdllc and debug llc2 packet privileged exec commands enabled on the router, check to see whether the FEP is replying to XID frames from the router. Step 2 If the FEP is responding, proceed to the next problem in this table. Step 3 If the FEP is not responding, check the XID values configured by the sdllc xid command on the router. The values for IDBLK and IDNUM on the router must match the values in VTAM on the FEP. The following is the syntax for the sdlc xid command: sdlc xid address xid Syntax Description: address---Address of the SDLC station associated with this interface. xid---XID the Cisco IOS software will use to respond to XID requests the router receives. This value must be 4 bytes (8 digits) in length and is specified with hexadecimal digits. Example: The following example specifies an XID value of 01720002 at address C2: interface serial 0 sdlc xid c2 01720002 Step 4 Make sure that the XID information on the hosts is properly defined. If a 317X device is a channel-attached gateway, the XID must be 0000000 for IDBLK and IDNUM.
Host problem	Check for activation, application problems, VTAM and NCP misconfigurations, configuration mismatches, and other problems on the IBM host.

1FEP = front-end processor 2XID = exchange of identification

If the router sees an address that matches an assigned SDLLC LAA address, it automatically forwards that packet to the SDLLC process. This can result in packets being incorrectly forwarded to the SDLLC process and sessions never being established.

Possible Problem	Solution
Peers are not open	Step 1 Use the show stun exec command to see whether the peers are open. If the peers are open, one of the other problems in this table is probably the cause. The following is sample output from the show stun command: Router# show stun This peer: 131.108.10.1 Serial0 -- 3174 Controller for test lab (group 1 [sdlc]) state rx-pkts tx-pkts drops poll 7[ 1] IF Serial1 open 20334 86440 5 8P 10[ 1] TCP 131.108.8.1 open 6771 7331 0 all[ 1] TCP 131.108.8.1 open 612301 2338550 1005 In this display, the first entry reports that proxy polling is enabled for address 7 and serial 0 is running with modulus 8 on the primary side of the link. The link has received 20,334 packets, transmitted 86,440 packets, and dropped 5 packets. Step 2 If the peers are not open, use the debug stun command on the core router to see whether the peers are trying to open. Peers do not open if there is no traffic on the link. Caution: Do not enable debug commands on a heavily loaded router. Doing so can cause performance and connectivity problems. Use a protocol analyzer or show commands instead. Step 3 If you do not see the peers trying to open, use the show interface exec command to make sure the interface and line protocol are both up. If they are not both up, there could be a link problem. Proceed to the problem "SDLC physical or link-layer problem" later in this table. Step 4 If the peers are trying to open, use the show running-config privileged exec command to make sure that the stun route and other STUN configuration commands are configured correctly. Reconfigure the router if necessary. Step 5 Use the debug stun packet privileged exec command on the core router. Look for SNRMs or XIDs being sent. Step 6 If you do not see SNRMs or XIDs, there is probably a basic link problem. See the problem "SDLC physical or link-layer problem" later in this table. Step 7 Check to make sure that there are not other network problems occurring, such as interface drops, buffer misses, overloaded Frame Relay switches, and IP routing problems.
SNRMs or XIDs not sent	Step 1 Use the show stun command to see whether the peers are open. If the peers are not open, see the preceding problem in this table. Step 2 If the peers are open, use the debug stun packet privileged exec command on the remote end. Check for SNRMS or XIDs from the primary arriving as NDI packets. Step 3 If SNRMs or XIDs are arriving, proceed to the next problem in this table. Step 4 If SNRMS or XIDs are not arriving, use the debug stun packet command on the core router to see whether SNRMs or XIDs are being sent. Step 5 If the core router is not sending SNRMs or XIDs, make sure that the physical and link layers are operating properly. See the problem "SDLC physical or link-layer problem" later in this table. Step 6 If the core router is sending SNRMs or XIDs, use the show running-config privileged exec command to make sure the stun route command is properly configured on the router. Step 7 Check to make sure that there are not other network problems occurring, such as interface drops, buffer misses, overloaded Frame Relay switches, and IP routing problems.
No reply to SNRMs or XIDs	Step 1 Use the show stun command to see whether the peers are open. If the peers are not open, see the first problem in this table. Step 2 If the peers are open, use the debug stun packet privileged exec command on the remote end. Check for SNRMS or XIDs from the primary arriving as NDI packets. Step 3 If SNRMs or XIDs are not arriving, refer to the preceding problem in this table. Step 4 If SNRMs or XIDs are arriving, make sure that the core router is sending UA or XID responses as SDI packets. Step 5 If the router is not sending responses, there might be a link problem. Refer to the problem "SDLC physical or link-layer problem" later in this table.
No reply to SNRMs or XIDs	Step 6 If the router is sending responses, use the debug stun packet command to see whether the UA or XID responses are getting back to the primary as SDI packets. Step 7 If the responses are not getting back to the primary, use the show running-config privileged exec command to make sure that the stun route and other STUN configuration commands are properly configured on the remote router. The following is the syntax for the stun route command: stun route address address-number tcp ip-address [local-ack] [priority] [tcp-queue-max] Syntax Description: address-number---Number that conforms to TCP addressing conventions. ip-address---IP address by which this STUN peer is known to other STUN peers that are using the TCP as the STUN encapsulation. local-ack---(Optional) Enables local acknowledgment for STUN. priority---(Optional) Establishes the four levels used in priority queuing: low, medium, normal, and high. tcp-queue-max---(Optional) Sets the maximum size of the outbound TCP queue for the SDLC link. Example: In the following example, a frame with a source-route address of 10 is propagated using TCP encapsulation to a device with an IP address of 131.108.8.1: stun route address 10 tcp 131.108.8.1 Step 8 Check to make sure that there are not other network problems occurring, such as interface drops, buffer misses, overloaded Frame Relay switches, and IP routing problems. Step 9 If packets are passed end-to-end in both directions, check end station configurations, duplex settings, configurations, and so forth.
SDLC physical or link-layer problem	Step 1 Use the show interfaces exec command on the link connecting to the primary device. Make sure that the interface and line protocol are both up. Step 2 If the interface or line protocol is not up, make sure the devices are powered up and connected correctly. Check the line to make sure it is active. Check for clocking, address misconfigurations, correct NRZ or NRZI specifications, and so forth. Step 3 Try slowing the clock rate of the connection. Use the clock rate interface configuration command to configure the clock rate for the hardware connections on serial interfaces such as NIMs and interface processors to an acceptable bit rate. The following is the syntax of the clock rate command: clock rate bps Syntax Description: bps---Desired clock rate in bits per second: 1200, 2400, 4800, 9600, 19200, 38400, 56000, 64000, 72000, 125000, 148000, 250000, 500000, 800000, 1000000, 1300000, 2000000, 4000000, or 8000000. Example: The following example sets the clock rate on the first serial interface to 64000 bits per second: interface serial 0 clock rate 64000 For more information about troubleshooting SDLC physical and link-layer problems, see the section "SDLC: Router Cannot Communicate with SDLC Device" earlier in this chapter.

Possible Problem	Solution
TCP/IP not running on host	Step 1 Check whether TCP/IP is running on the host. Step 2 If TCP/IP is not running, start it.
CIP devices not online to host	Step 1 Check the mainframe to see whether the CIP devices are online to the host. Step 2 If the CIP devices are not online, vary them online. If devices do not come online, see the section "CIP: CIP Will Not Come Online to Host" later in this chapter. Step 3 Check whether the TCP/IP device has been started. Step 4 If the device has not been started, start it. Note: It might be necessary to stop and start the TCP/IP application to start the device. If you are using obey files, this might not be necessary. Step 5 Check the configuration for the CIP in the TCP/IP profile on the host, and check the router configuration for the CIP device. Step 6 Use the moretrace claw command on the host, either from an obey file or in the TCP/IP profile. This command traces the establishment of CLAW connections and can provide information that is useful for determining causes of connection problems.

Possible Problem	Solution
Hardware problem	Step 1 Check to make sure that the router is plugged in and turned on. Step 2 Use the show version exec command and see whether the CIP card appears in the output. Step 3 If the CIP card appears in the output, the Enabled LED might be faulty. Step 4 If the CIP card does not appear in the output, reseat the CIP card, reboot the router, and check the output of the show version command again.
Old Cisco IOS release	Step 1 Use the show version exec command to find out what version of the Cisco IOS software you are running. Step 2 If you are using Cisco IOS software prior to Release 10.2(6), you should upgrade to a more recent version.

Possible Problem

Solution

CHPID1 not online to host

Step 1 Make sure the Enabled LED on the CIP card is on. If it is not on, refer to the section "CIP: No Enabled LED On" earlier in this chapter. Step 2 Use the show extended channel slot/port subchannel command and check for the SIGNAL flag in the output. Step 3 If the SIGNAL flag is not present, check whether the CHPID is online to the host. If it is not, configure it to come online. Note: On a bus and tag channel, the SIGNAL flag is turned on by OP_OUT being high from the host. On an ESCON channel, the SIGNAL flag is turned on by the presence of light on the channel. Step 4 If the CHPID does not come online to the host, check the physical cabling. Step 5 If the CIP still does not come online, check the IOCP2 definitions for the CIP device, and check the router configuration.

1CHPID = channel path identifier 2IOCP = input/output control program

Possible Problem

Solution

Addressing problem between CIP and host

Step 1 Verify that the CLAW connection is up by checking the output of the show extended channel slot/port statistics exec command on the router. Step 2 If the output shows that CLAW connections are not up (indicated by a N), refer to the section "CIP: CLAW Connection Does Not Come Up" earlier in this chapter. Step 3 If the CLAW connections are up (indicated by a Y), issue the clear counters privileged exec command. Then attempt a basic ping to the host from the router or to the router from the host. Step 4 When the ping is completed, use the show extended channel slot/port statistics exec command on the router. If you issued the ping from the router to the host, the host should have read five 100-byte ICMP echos from the router. The Total Blocks field in the show command output should indicate five blocks read. If the host replied, the output should indicate five blocks written. If you issued the ping from the host to the router, the host should have sent one 276-byte ICMP echo to the router. The Write field should indicate one block written. If the router replied, the output should indicate one block in the Read field. Step 5 If this is not the case, there could be an addressing problem between the CIP and the host. Check all IP addresses on the router and in the host TCP/IP profile and make sure they are correct.

Possible Problem

Solution

Missing or misconfigured IP routes

Step 1 If the mainframe host is unable to communicate with networks on the other side of the router, try to ping the remote network from the router. If the ping succeeds, proceed to Step 4. Step 2 If the ping fails, use the show ip route privileged exec command to verify that the network is accessible by the router. Step 3 If there is no route to the network, check the network and router configuration for problems. Step 4 Verify that the host connection is active by pinging the host IP address from the router. If the ping is unsuccessful, see the section "CIP: Router Cannot ping Host or Host Cannot ping Router" earlier in this chapter. Step 5 Issue the netstat gate command on the host and check for a route to the network. Step 6 If a route does not exist, make sure the host is using the address of the CIP in the router as the default route. If it is not, add a GATEWAY statement in the TCP/IP profile that points to the network, or set the CIP in the router as the default route using a DEFAULTNET statement in the TCP/IP profile.

Possible Problem	Solution
RIP not properly configured on the router	Step 1 Use the show running-config privileged exec command to view the router configuration. Make sure RIP is configured on the router. If RIP is not configured, configure it. Step 2 Check the configuration to see whether there are network statements for each of the networks that should be advertised in RIP updates. If they are missing, add them to the configuration. Step 3 Make sure the passive-interface command is not configured on the channel interface. Step 4 If the command is present, remove it using the no passive-interface router configuration command. Step 5 Make sure there are no distribute-list statements filtering RIP routing updates. Step 6 Check the router configuration to be sure the broadcast keyword has been specified in the claw interface configuration command. The following is the claw command syntax: claw path device-address ip-address host-name device-name host-app device-app [broadcast] Example: The following example shows how to enable IBM channel-attach routing on the CIP port 0, which is supporting a directly connected ESCON channel: interface channel 3/0 ip address 198.92.0.1 255.255.255.0 claw 0100 00 198.92.0.21 CISCOVM EVAL TCPIP TCPIP Step 7 If there is no broadcast keyword specified, add it to the configuration.
Host misconfiguration	Step 1 Use the netstat gate command on the host. Check whether there are routes learned from RIP updates. Step 2 If you do not see RIP routes, verify that the host connection is active by pinging the host IP address from the router. Step 3 If the ping is unsuccessful, see the section "CIP: Router Cannot ping Host or Host Cannot ping Router" earlier in this chapter. Step 4 Verify that the routed daemon is running on the host. Step 5 Use the show extended channel slot/port stat exec command to see whether RIP routing updates are incrementing the counters. Step 6 Check the TCP/IP profile on the host to be sure that there are BSDROUTINGPARMS instead of GATEWAY statements.