Performing A Memory Dump - 3Com NETBuilder SI Using Manual

Performing a
Memory Dump
If the number of received packets equals or approximately equals the
number of transmitted packets, your serial line has passed the serial
loopback test. If your serial line does not pass the test, verify that your
bridge/router is cabled correctly and that the software is configured
correctly. Also, check the number of packets transmitted and the number
of errors by entering:
DLTest STATistics
6 Stop the serial loopback test by entering:
DLTest Abort
7 Restore the owner of the wide area port you are testing from loopback to
your protocol using:
SETDefault !<port> -PORT OWNer = PPP | FrameRelay | SMDS | Auto
Failure to perform this step causes the port to remain in loopback mode
preventing connectivity through the port. Performing diagnostics on the
port will reveal only that the port is down.
If a SuperStack II bridge/router unexpectedly stops functioning, it
performs a memory dump. A memory dump provides a view of the
internal state of the system, which can help Technical Support determine
the cause of the failure.
By default, the system performs a partial dump to available flash memory.
If you want a full dump to a TFTP server on the local Ethernet network,
you must have the following items available:
IP addresses and subnet masks of the SuperStack II bridge/router, TFTP
server, and possibly, the gateway leading to the network segment
where the TFTP server is located
A TFTP server on the local Ethernet network
Authorization to write to the TFTP server
10 MB of available disk space on the TFTP server
The SuperStack II bridge/router configured to dump to the TFTP server
The procedure to obtain a memory dump involves setting up destination
IP addresses and a file to hold the memory dump information. The
bridge/router uses the IP addresses to transmit the memory dump in a file
across the network to a TFTP server.

Performing a Memory Dump

145