Dell PS-M4110 User Manual page 232

No activation or modifications to the card should occur. The card is ignored by CMC. In this situation, the $racadm
featurecard -s command returns the following message:
No feature card inserted
ERROR: can't open file
If the chassis service tag is reprogrammed, what happens if there is a feature card bound to that chassis?
• If the original feature card is present in the active CMC on that or any other chassis, the Web interface displays
the following error message:
This feature card was activated with a different chassis. It must be
removed before accessing the FlexAddress feature.
Current Chassis Service Tag = XXXXXXXX
Feature Card Chassis Service Tag = YYYYYYYY
The original feature card is no longer eligible for deactivation on that or any other chassis, unless Dell Service
re-programs the original chassis service tag back into a chassis, and CMC that has the original feature card is
made active on that chassis.
• The FlexAddress feature remains activated on the originally bound chassis. The
is updated to reflect the new service tag.
Is an error message displayed if two feature cards installed in the redundant CMC system?
The feature card in the active CMC is active and installed in the chassis. The second card is ignored by CMC.
Does the SD card have a write protection lock on it?
Yes it does. Before installing the SD card into the CMC module, verify the write protection latch is in the unlock position.
The FlexAddress feature cannot be activated if the SD card is write protected. In this situation, the $racadm feature -s
command returns this message:
No features active on the chassis. ERROR: read only file system
What happens if there isn't an SD card in the active CMC module?
The $racadm featurecard -s command returns this message:
No feature card inserted.
What happens to FlexAddress feature if the server BIOS is updated from version 1.xx to version 2.xx?
The server module needs to be powered down before it can be used with FlexAddress. After the server BIOS update is
complete, the server module does not get chassis-assigned addresses until the server has been power cycled.
What happens if a chassis with a single CMC is downgraded with firmware prior to 1.10?
• The FlexAddress feature and configuration is removed from the chassis.
• The feature card used to activate the feature on this chassis is unchanged, and remains bound to the chassis.
When this chassis's CMC firmware is subsequently upgraded to 1.10 or later, the FlexAddress feature is
reactivated by reinserting the original feature card (if necessary), resetting CMC (if feature card was inserted
after firmware upgrade was completed), and reconfiguring the feature.
What happens if a CMC unit is replaced with one that has firmware prior to 1.10 in a chassis with redundant CMCs?
In a chassis with redundant CMCs, if a CMC unit is replaced with one that has firmware prior to 1.10, the following
procedure must be used to ensure the current FlexAddress feature and configuration is NOT removed:
• Ensure the active CMC firmware is always version 1.10 or later.
• Remove the standby CMC and insert the new CMC in its place.
• From the Active CMC, upgrade the standby CMC firmware to 1.10 or later.
NOTE: If the standby CMC firmware is not updated to 1.10 or later and a failover occurs, the FlexAddress feature is
not configured. The feature must be reactivated and reconfigured again.
232
binding of that chassis feature