Novell Router Diagnostic Tools
493
debug ipx packet
The debug ipx packet command displays all IPX traffic that enters or
leaves the router. Thus, this command can generate a great deal of output,
and its use is recommended only with caution.
IPX packets that are fast-switched are not captured by the debug ipx packet
command. In order to view all packets, add the no ipx route-cache command
to each interface that you wish to include in the debug capture. If the initial
problem is related to fast switching, this may lead to erroneous troubleshoot-
ing results.
The following example contains the entry of a packet destined for server
130--internal network number. The response was sent to the gateway on
network 120:
IPX: src=100.0000.0c4c.42fa, dst=130.0000.0000.0001,
packet received
IPX: src=100.0000.0c4c.42fa,
dst=130.0000.0000.0001,gw=120.0000.0ca3.1bd0, sending
packet
debug ipx sap activity
As previously reviewed, SAP traffic provides the foundation for all Novell
functions. Incorrect functioning of the SAP process can prevent access to ser-
vices and cause other connectivity problems. As such, the debug ipx sap
activity
command provides an administrator with additional information
and possible indications of problem causes:
Router_A#debug ipx sap activity
IPX service debugging is on
Feb 1 10:08:38.424: type 0x30C, "PTR_1",
105.0006.0d86.5380(401C), 4 hops
Feb 1 10:08:38.424: type 0x30C, "PTR_2",
105.0006.0d6e.1a65(400C), 4 hops
Feb 1 10:08:38.648: type 0x44C, "AR3",
102.0000.0000.0001(8600), 3 hops
Feb 1 10:08:38.648: type 0x23F, "SRL03",
102.0000.0000.0001(907B), 3 hops
Copyright ©2000 SYBEX , Inc., Alameda, CA
www.sybex.com