Digi PortServer II, User Manual

Page: 257 / 277

90030500B Troubleshooting Page 237
Note: Gateways 12 and 14 through 17 did not respond to the probe packets. Typi-
cally, this occurs if the host does not send ICMP Time Exceeded messages,
or send them with a TTL that is too small to reach PortServer II.
Troubleshooting Frame Relay
Problems with a Frame Relay link generally fall into one of two categories:
• The link does not come up
• The link appears to start, but does not route or pass packets
To identify the source of the problem, we suggest you do the following:
1. Check for critical errors since PortServer II was initialized by reading the Trace
Log. Enter the following command to print the Trace Log:
set trace state=dump
Refer to the Command Reference Guide for more information on the set trace
command.
2. If the Trace Log does not provide any assistance in identifying the problem, check
the current state of PortServer II. You can do this by setting the Trace mode to
concurrent with the following command:
set trace mode=concurrent
Frequently, the process that is failing to run will retry periodically. If you can
identify this process, you may be able to isolate the location of the fault.
3. Display the counters for the Frame Relay links, by entering the following com-
mand:
info frame :* (to display the counter for all Frame Relay links), or
info frame :*:*
(to display the counter for all PVCs)
Note: The best option to select depends on the number of Frame Relay links and
the extent of the fault. Select the option that gives you sufficient counters
for meaningful interpretation.
In either case, both sent and received frames should be displayed with no errors
(Err) and error fault (ErrFaults) counts, or a small number of errors.
4. If you require more information, you can display detailed debug commands by
entering a command similar to the following: