Show ipx traffic

show ipx traffic

The output of this command is organized into several sections. The first section informs you of the total number of packets received along with a short report including the number of error conditions detected on those packets. Next, the number of broadcasts sent and received, and the number of packets sent, forwarded, and dropped (due to encapsulation failure or no route conditions) are reported. The sections following provide statistics on SAP, RIP, IPX Echo, Watchdog, queue lengths, and any other IPX routing protocols that are active (see Example 6-3).

Example 6-3 show ipx traffic Command

A_StubR#show ipx traffic

System Traffic for 0.0000.0000.0001 System-Name: A_StubR

Rcvd: 1930 total, 0 format errors, 0 checksum errors, 0 bad hop count,

0 packets pitched, 1930 local destination, 0 multicast Bcast: 1920 received, 2441 sent Sent: 2449 generated, 0 forwarded

0 encapsulation failed, 0 no route SAP: 0 Total SAP requests, 0 Total SAP replies, 26 servers 0 SAP general requests, 0 replies 0 SAP Get Nearest Server requests, 0 replies 0 SAP Nearest Name requests, 0 replies 0 SAP General Name requests, 0 replies 1460 SAP advertisements received, 1452 sent 16 SAP flash updates sent, 0 SAP format errors RIP: 0 RIP requests, 0 RIP replies, 4 routes

364 RIP advertisements received, 727 sent 3 RIP flash updates sent, 0 RIP format errors

Example 6-3 show ipx traffic Command (Continued)


Rcvd 0 requests, 0


Sent 0 requests, 0


0 unknown: 0 no socket, 0 filtered, 0 no helper

0 SAPs throttled, freed NDB len 0


0 packets received

0 replies spoofed



IPX input: 0, SAP

S, RIP 0, GNS 0

SAP throttling length: 0/(no limit), 0 nets pending lost route reply

Delayed process creation: 0


Total received 106

sent 247

Updates received 2

sent 4

Queries received 1

sent 2

Replies received 1

sent 1

SAPs received 0, sent 0

This command is very useful during the course of troubleshooting, as it lets you know if the router under investigation is or is not successfully sending and receiving IPX packets, broadcasts, SAP, RIP, and other IPX-related traffic. Not only can you use these observations to decide on whether the local router is faulty, but you can also focus your attention on more specific transactions and protocols should there be a determination of faulty behavior.

Was this article helpful?

0 0

Post a comment