Dell FCX624-E Laptop User Manual


  Open as PDF
of 1494
 
PowerConnect B-Series FCX Configuration Guide 157
53-1002266-01
Image mismatches
5
PowerConnectt# show running config
stack unit 1
module 1 FCX-24-port-management-module
module 3 FCX-cx4-2-port-16g-module
module 4 FCX-xfp-2-port-16g-module
priority 128
stack unit 2
module 1 FCX-24-port-management-module
module 3 FCX-xfp-2-port-16g-module
stack unit 3
module 1 FCX-48-port-management-module
module 2 FCX-cx4-2-port-16g-module
module 3 FCX-cx4-2-port-16g-module
stack enable
3. To resolve the mismatch, you must remove the configuration for stack unit 3. Use the following
command.
PowerConnect# no stack unit 3
If you are unable to remove the configuration because of a multi-slot trunk configuration, it
means secure-setup cannot overwrite the Active Controller configuration due to multi-slot
trunking configurations on the ports of the unit to be overwritten. You must first manually
remove the multi-slot trunk configuration.
4. When you have successfully deleted the mismatched stack unit, a re-election is triggered, and
the Active Controller learns the correct module configuration from the Standby Controller or
from other stack members.
Follow the steps given below to recover from an image mismatch.
1. Use the copy flash flash command to replace a mis-matched image with the correct image.
Refer to “Copying the flash image to a stack unit from the Active Controller” on page 126.
2. Reset the unit. After the reset, the unit will contain the new image and the mis-match condition
will not exist. To verify, use the show stack command.
Troubleshooting secure-setup
Secure-setup can be used to form linear and ring stack topologies. For information about the
procedure, refer to “Scenario 1 - Configuring a three-member IronStack in a ring topology using
secure-setup” on page 101. During this procedure, if secure-setup does not detect all the units that
should be detected, perform the following checks:
Make sure that all the cables are properly connected
Make sure that all the relevant ports are in UP state
Make sure that all the units are running the same image
Make sure that you issue the stack enable command only on the unit that will serve as the
Active Controller
Make sure that stack disable is not configured on any prospective members
Make sure that the connection is sequential (refer to “IronStack terminology” on page 96,
Sequential Connection)