540
Chapter 10
Troubleshooting AppleTalk Connectivity
C00040000000000030E86D0FAAAA03080007809B|00418B4700000001F
F575858580205EDAC
000000000000000000000000000000010001000C010001000000000F02
04000C0001000100
TokenRing0: input AT packet: enctype SNAP, size 65
C00040000000000030E86D0FAAAA03080007809B|00418B4700000001F
F575858580205EDAC
000000000000000000000000000000010001000C010001000000000F02
04000C0001000100
TokenRing0: input AT packet: enctype SNAP, size 65
C00040000000000030E86D0FAAAA03080007809B|00418B4700000001F
F575858580205EDAC
000000000000000000000000000000010001000C010001000000000F02
04000C0001000100
TokenRing0: input AT packet: enctype SNAP, size 65
C00040000000000030E86D0FAAAA03080007809B|00418B4700000001F
F575858580205EDAC
000000000000000000000000000000010001000C010001000000000F02
04000C0001000100
debug apple events
The debug apple events command reports AppleTalk special events, including
interfaces going up or down, and neighbor unreachability. In a stable network,
this command produces no output.
Although Cisco recommends that administrators enable this command
prior to making configuration changes, few administrators heed this advice.
Many sites do use the apple event-logging command, however, which
reports special events to a syslog server.
Note that when the command is used during configuration changes
(specifically, the enabling of a new router interface), the following
sequence should be observed:
Line down
Restarting
Probing--this is an AARP process to find its address
Acquiring via GetNetInfo requests
Sending ZIP requests for a list of zones on the cable
Copyright ©2000 SYBEX , Inc., Alameda, CA
www.sybex.com