EM316LNXNM-OT
Appendix
PN 1275005-100 Rev E6
168
4. LNXNM Troubleshooting
4.1. SNMP Problems
If your SNMP manager has trouble communicating with the SNMP agent in the EM316LNXNM, check
your SNMP configuration parameters.
Your network administrator can help determine if your IP configuration (IP address and netmask) is
correct. If the SNMP management workstation is on a different network, make sure that you define an
appropriate default gateway IP address.
Change the SNMP v1 community string configuration by using the
snmp-server community
read/write
command. Please note that community string information can not be displayed using any
show
command. The community strings are encrypted, even in
write terminal
output.
If you are not receiving any traps, check that you entered the network management workstation address in
the trap receiver table correctly. Display the table using the
show snmp-server hosts
command.
Check that both the IP address and the SNMP v1 community string are correct.
Check that you have a working network connection.
Test the connection to the network management station by pinging it. If the network's physical topology
has changed recently (e.g. a network management station has been moved from one segment to another),
you may have to wait for the entries in the ARP cache to time out.
4.2. Hot-swap issues
If the LNXNM is hot-swapped, the configuration in the LNXNM database and the settings in the hardware
may not match. For some devices, the hot-swap feature only works correctly when all changes are written
to flash with the "
write file
" command before a hot-swap or a warm reset. To make sure that the
hardware configuration matches the software database, use the "
restart cold
" command or power-
cycle the box.
Always save changes with "
write file
" before a hot-swap.
4.3. Serial Port Connection is stuck at "
=>
" Prompt
If you see the "
=>
" prompt again when you press "enter" key and nothing else seems to work, the system
is halted at the boot ROM prompt. Get out of this prompt by using the "
reset
" command or power-cycle.
When it starts to boot again, "
Hit any key to stop autoboot:
" should appear and you will
see a count down. Let the count down finish, and let the boot ROM attempt to load the firmware. You
should eventually get the login prompt. If the symptom persists, and the prompt remains at "
=>
" even after
rebooting, the system failed to boot correctly and the unit must be repaired or replaced. Alternately, see
the "
Recovering from a failed 'upgrade' command"
section below.
