Configuration Guide User guide

FastIron Configuration Guide 317
53-1002494-02
IronStack troubleshooting
target ID 1 1 0 0
target MAC 15230 15230 0 0
unrel target ID 7615 0
There is 1 current jumbo IPC session
Possible errors:
*** recv from non-exist unit 2 times: unit 5
If the send message types: field is empty, it means that stack enable has not been configured.
If the number of Recv IPC packets increases, but there are no Recv message types, then the
packets are being dropped for various reasons, including the wrong IPC version, or a checksum
error. The Possible errors field will list reasons for packet loss.
NOTE
A small “***state not ready” count is normal, but if it continues to increase a problem is
indicated.
6. If the results of a show stack command show other stack members, but lists them as
non-operational, this could be due to an image mismatch, or a configuration mismatch. In the
event of an image mismatch, you can download the correct images to the entire stack from the
Active Controller. Refer to “Configuration mismatch for stack units” on page 320 for more
information about configuration mismatches.
NOTE
If your intended stacking ports are connected in a ring topology, they will not all appear to be in
the forwarding state because of spanning tree, but secure-setup can still build the stack.
7. If you run out of flash memory while doing a write memory, your stack devices may contain very
large startup-config.v4 or startup-config.old files, which are preserved for recovery purposes
(refer to “Unconfiguring an IronStack” on page 287 for more information). If you do not need
these files, you can delete them using the flash delete command. Enter the show dir command
to see all flash files.
8. Check to be sure you do not have any stacking to non-stacking connections. If you see the
following message.
Warning! Proc ???? packet in 2m from 0012.f2222.8300, Wrong dev/port: dev=4,
port=18, DSA=4971100 497--E
You might have stacking to non-stacking port connections
This indicates that you may have a connection between a stacking port and a non-stacking
port. This message will appear every 10 minutes after the first display. If you see this message
once only, and your connections are correct, your stack should be operating properly. Only
repeat displays of this message indicate a problem.
Troubleshooting a stacking upgrade
After you upgrade your device to support stacking, restart the device with the upgraded software. If
you encounter a problem at this step, make sure the memory DIMM and stacking EEPROM are
installed correctly. If they are not installed correctly, you may see output similar to the following.
FCX MEM size: 0x10000000
FCX Flash config....
FCX Boot Code Version 05.0.00
Enter ‘b’ to stop at boot....