Notice that the number of hops to the server is shown, as is the type of service and the server
name. The source and destination of the update packets are also listed. The debug ipx routing
events command lists just summary information about routing updates, whereas the debug ipx
routing activity command gives the details.
All possible debugging has been turned off
Codes: S - Static, P - Periodic, E - EIGRP, N - NLSP, H - Holddown, + = detail
U - Per-user static
4 Total IPX Servers
P 4 SVR1 200.0000.0000.0001:0452 8/02 3 Se0.1
P 4 SVR2 200.0000.0000.0001:0452 8/02 3 Se0.1
P 7 SVR1 200.0000.0000.0001:0452 8/02 3 Se0.1
P 7 SVR2 200.0000.0000.0001:0452 8/02 3 Se0.1
Seville#debug ipx sap activity
IPX service debugging is on
Seville#
00:13:21: IPXSAP: Response (in) type 0x2 len 288 src:6.0200.aaaa.aaaa
dest:6.ffff.ffff.ffff(452)
00:13:21: type 0x4, "SVR2", 200.0000.0000.0001(452), 3 hops
00:13:21: type 0x4, "SVR1", 200.0000.0000.0001(452), 3 hops
00:13:21: type 0x7, "SVR2", 200.0000.0000.0001(452), 3 hops
00:13:21: type 0x7, "SVR1", 200.0000.0000.0001(452), 3 hops
00:13:27: IPXSAP: positing update to 6.ffff.ffff.ffff via Serial0.1 (broadcast)
(full)
00:13:27: IPXSAP: suppressing null update to 6.ffff.ffff.ffff
Seville#
Seville#
00:13:30: IPXSAP: Response (in) type 0x2 len 288 src:5.0200.bbbb.bbbb
dest:5.ffff.ffff.ffff(452)
00:13:30: type 0x7, "SVR1", 200.0000.0000.0001(452), 4 hops
00:13:30: type 0x7, "SVR2", 200.0000.0000.0001(452), 4 hops
00:13:30: type 0x4, "SVR1", 200.0000.0000.0001(452), 4 hops
00:13:30: type 0x4, "SVR2", 200.0000.0000.0001(452), 4 hops
undebug all
All possible debugging has been turned off
Seville#