Memory Allocation Failure; Recovering From A Mismatch - Dell PowerConnect B-FCXs Configuration Manual

5
Image mismatches
Configuration mismatches can happen during manual setups, or when moving a unit from one
stack to another stack. Secure-setup will try to overwrite a configuration mismatch even if the
configuration is static. The overwrite attempt may fail if there are multi-slot trunk or LACP
configurations on the ports of the unit to be overwritten. If this is the case, secure-setup will be
unable to resolve the mismatch.
When you renumber identical units using secure-setup, the configurations are not mapped to the
new units (since they match exactly). However, if you switch the IDs of units that are not identical, a
configuration mismatch occurs.
Configuration mismatches can also occur when LACP or multi-slot trunking configurations exist on
the modules of replacement units. In these cases, you will need to manually remove the LACP or
multi-slot trunking configuration on the replacement unit before you try to add it to the stack.
When a configuration mismatch occurs, port-related functions on all ports are disabled on the
mismatched unit (except for the stacking ports). All other functions are unaffected. For example,
the Active Controller can still copy the unit's image or reset the unit. Please refer to
from a mismatch"

Memory allocation failure

A memory allocation (malloc) failure occurs when the Active Controller does not have enough
memory to run a stack unit. This failure may occur if you configure large numbers (for example, 4 K
of VLANs, or STP instances (for example, 255).in the router image. This message means that the
Active Controller is low on memory after allocating these resources and does not have enough
remaining memory to control a stack member. You can correct this by reducing the number of
VLANs or STP instances.
NOTE
After you make configuration changes such as number of VLANs or STP instances, you must reset
the stack.

Recovering from a mismatch

When a configuration mismatch occurs, the Active Controller logs and displays a configuration
mismatch message, and puts the mismatched unit into a non-operational state. In the following
example, the original stack unit 3 has failed, and a replacement unit has been installed that does
not match the configuration of the original unit. You should see the following message.
Warning! put stack unit 3 to non-operational reason= config mismatch
Follow the steps given below to recover from a configuration or image mismatch.
1. Enter the stack secure-setup command.
2. Enter the show stack command to see the status of the stack, and a show running-config
156
on page 156.
command to see the configurations of the stack units. If secure-setup does not resolve the
configuration mismatch, proceed to step 3.
PowerConnect# show stack
alone: standalone, D: dynamic config, S: static config
ID Type Role Mac Address
1 FCX624 active 0012.f2eb.a900 128 local
2 FCX648 member 00f0.424f.4243
3 FCX624 standby 00e0.5201.0100
Pri State Comment
Ready
0 remote Ready
0 remote NON-OP: config mismatch
PowerConnect B-Series FCX Configuration Guide
"Recovering
53-1002266-01