Zhone 5100 安装指南

CHAPTER 5
Troubleshooting

This section describes normal operation for the 5100/6100 VDR under various conditions, such 

as power loss, and the meaning of console output during normal operation. Examples of console 

output and suggestions for avoiding problems are given to facilitate recognition of normal VDR 

operation.

If the unit loses power before a new image is completely saved, the unit will not boot with the new 

image active.
To avoid this situation, ensure that you wait until the “save successful” message appears before 

resetting the 5100/6100 VDR. If the 5100/6100 VDR is reset (such as a power loss during a 

software upgrade) before the new image is saved, you need to reload the new image.

The LAN port is configured to always autonegotiate.
If downlink devices are not configured to autonegotiate, the 5100/6100 VDR generates undersize 

packets and console error messages will intermittently appear (see example). When the remote 

end operates in “forced” mode, the Ethernet hardware falls back to half-duplex operation mode 

and causes the incorrect operation of the LAN port.
Example:

To avoid generating undersized packets, you must enable autonegotiation on the downlink 

device(s).

If there is no more room on the Flash memory, the 5100/6100 VDR prompts you to delete 

current image.
From the user file management interface, go into the /maincode directory and delete any 

undesirable files to free up enough Flash space to hold another operating image before 

downloading the image.

Console messages appear on the terminal screen as a part of normal operation. These messages 

alert you to conditions that might have appeared prior to a reset or auto-recovery event. If you 

notice significant output or frequent fatal errors, you can save them as a session log and analyze 

them with the help of Vpacket Customer Care representatives. 

VPacket# tfKernelWarn: tfIpIncomingPacket --- Bad IP header

tfKernelWarn: tfIpIncomingPacket --- Bad IP header