| A wide variety of commands can be used to aid in troubleshooting Novell protocols, including the configuration, statistics, IPX, and SAP protocols. The Cisco router's show commands provide a wealth of information regarding IPX. The following bulleted list reviews the output from the most commonly used IPX troubleshooting commands, which include the following: -
debug ipx routing . This command displays the IPX routing protocol processes running on the router. These processes include the IPX routing protocols IPX RIP, IPX-EIGRP, and NLSP. An example of the output follows : *Sep 30 03:14:47.301 UTC: IPXRIP: Deleting network 101 *Sep 30 03:14:47.303 UTC: IPX: cache flush *Sep 30 03:14:47.304 UTC: IPX: Setting state of E0:300 to [up]:[up] *Sep 30 03:14:47.304 UTC: IPX: cache flush *Sep 30 03:38:47.304 UTC: IPXRIP: Marking network 100 for Flash Update -
debug ipx packet . This command is used to display all the IPX traffic either entering or exiting the router.  | The debug ipx packet command should be used with caution because the debug command is assigned a high priority on the router's processor and can actually render the router inoperable. |
 | The debug ipx packet command doesn't display IPX packets that are fast-switched. If you need to view all packets, including those that are fast-switched, use the no ipx route-cache command on each interface that you wish to include in the debug capture. The following is an example of the output. It shows the entry of a packet destined for a server on the 200 network, with the response sent to the gateway on network 200: IPX: src=253.0000.604c.12bf, dst=200.0000.0000.0001, packet received IPX: src=253.0000.604c.12bf, dst=200.0000.0000.0001, gw=200.0000.80a5.abd1, sending packet |
-
debug ipx sap activity . This command allows you to view the SAP traffic, which provides information regarding whether or not the SAP processes are functioning correctly. If SAP is not functioning properly, you can prevent access to services and cause other connectivity issues in your network. An example of the output follows: DCS2514# debug ipx sap activity IPX service debugging is on Oct 30 10:06:31.424:type 0x30C, "PTR_1",800.0006.0d86.5380(401C), 4 hops Oct 30 10:06:31.424:type 0x30C, "PTR_2",800.0006.0d6e.1a65(400C), 4 hops Oct 30 10:06:31.618:type 0x44C, "AR3", 300.0000.0000.0001(8600), 3 hops Oct 30 10:06:31.618:type 0x23F, "SRL03",300.0000.0000.0001(907B), 3 hops Oct 30 10:06:31.704: IPXSAP: at 690465B4: I SAP Response type 0x2 len 480 src:800.0060.837b.4a19 dest:200.ffff.ffff.ffff(452) The highlighted line represents an SAP packet received. The "PTR 1" indicates the name of the server being advertised. The address of 800.0006.0d86.5380(401C) indicates the address and socket number in parenthesis. The last line indicates the number of hops to the server from the router. -
ping ipx . Just like in IP where the ping command uses the ICMP protocol and an IP address, you can use the ping ipx command and an IPX address to verify connectivity with another device. By using this utility for troubleshooting IPX connectivity problems, you can verify that the routing tables are being updated correctly and that connectivity to other networks and devices is taking place. The following shows an example of using the ping ipx command to ping a Cisco router's interface assigned to the 18a network: DCS2621# ping ipx 18a.0000.834a.3d51 Type escape sequence to abort. Sending 5, 100-byte IPX cisco Echoes to 18a.0000.834a.3d51, timeout is 2 seconds !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 16/19/31 ms -
show ipx route . This command can be useful when you need to know the state of a NetWare network. You can use this command to verify that certain paths exist through the network. Using this command, you can view the routes learned; path decisions made by IPX RIP, NLSP, IPX-EIGRP, and IPXWAN; and the static routes that are configured on the interface. The following shows an example of using this command: DCS2514# show ipx route Codes: C - Connected primary network c - Connected secondary network, S - Static, F - Floating static, L - Local (internal), W IPXWAN R RIP, E - EIGRP, N - NLSP, X - External, A Aggregate s - seconds, u - uses 1 Total IPX routes. Up to 3 parallel paths and 16 hops allowed. No default route known. R 1 [03/02] via 300.0060.602a.1d4c, 8s, Hs3/0 The above output shows that the router has learned of one network via the IPX RIP routing protocol and that the router has no default gateway. -
show ipx servers . This command displays all servers known to the router that have been learned from SAP advertisements. If servers are missing, there may be an access list misconfiguration, duplicate network numbers , a downed link or interface, network congestion, or misconfigured frame types. The following is the output from the command, followed by an explanation of the fields that are listed: DCS2514# show ipx servers Codes: S - Static, P - Periodic, E - EIGRP, N - NLSP, H - Holddown, + = detail 2 Total IPX Servers Table ordering is based on routing and server info Type Name Net Address Port Route Hop Itf N 4 File&Print1 100.0000.0000.0001:0451 727/03 2 E1 N+ 4 EmailSAC 200.0000.0000.0001:0451 729/03 2 E1 -
show ipx traffic . This command displays information regarding IPX packets that have been transmitted or received. An example of the output from this command follows: DCS 2514# show ipx traffic System Traffic for 300.0000.0000.0001 System-Name: DCS2514 Rcvd: 3298322 total, 158 format errors, 0 checksum errors, 0 bad hop count, 6 packets pitched 65955970 local destination, 0 multicast Bcast: 3287985 received, 139078 sent Sent: 1324204 generated, 4 forwarded 0 encapsulation failed, 0 no route SAP: 0 SAP requests, 0 SAP replies, 2 servers 0 SAP advertisements received, 8 sent 5 SAP flash updates sent, 0 SAP format errors RIP: 0 RIP requests, 0 RIP replies, 6 routes 0 RIP advertisements received, 0 sent 0 RIP flash updates sent, 0 RIP format errors Echo: Rcvd 0 requests, 0 replies Sent 0 requests, 0 replies 0 unknown: 0 no socket, 0 filtered, 0 no helper 0 SAPs throttled, freed NDB len 0 Watchdog: 0 packets received, 0 replies spoofed Queue lengths: IPX input: 0, SAP 0, RIP 0, GNS 0 SAP throttling length: 0/(no limit), 0 nets pending lost route reply Delayed process creation: 0 EIGRP: Total received 4413, sent 1784 Updates received 58, sent 128 Queries received 32, sent 17 Replies received 17, sent 32 SAPs received 0, sent 0 NLSP: Level-1 Hellos received 0, sent 0 PTP Hello received 0, sent 0 Level-1 LSPs received 0, sent 0 LSP Retransmissions: 0 LSP checksum errors received: 0 LSP HT=0 checksum errors received: 0 Level-1 CSNPs received 0, sent 0 Level-1 PSNPs received 0, sent 0 Level-1 DR Elections: 0 Level-1 SPF Calculations: 0 Level-1 Partial Route Calculations: 0 The above output is great for getting a detailed description of how IPX is working. The output shows that there are 158 format errors from received servers. The output also shows that the router has learned about two servers through SAP. You should be aware that some of these commands are not available on certain IOS versions, and some versions support additional syntaxes that are not displayed here. You should always use the show ipx ? command to see the available syntaxes.  |
