Replacing a node canister

To replace a faulty node canister with a new one received from CRU or FRU stock, use this procedure. When replacing a node canister, aim to maximize drive and system availability by maintaining one online node in the control enclosure containing the faulty node canister. If you cannot maintain at least one node canister online in the system, then you might need to follow the system recovery procedure after replacing the faulty node canister.

Procedure

  1. Follow Procedure: Removing a node canister to remove the faulty node canister.
  2. Remove the lid of the faulty canister, as described in Procedure: Removing and replacing the lid of a node canister. Do the same to the replacement canister.
  3. Some components inside the faulty node canister must be transferred to the replacement canister. Transfer each of the following:
  4. Replace the lid of the faulty canister and the lid of the replacement canister. Refer to Procedure: Removing and replacing the lid of a node canister.
  5. Open the release levers of the replacement canister.
  6. Push the replacement canister into the slot of the enclosure that the faulty canister was removed from, until it stops.
  7. Finish inserting the replacement canister by closing both release levers and pushing both orange locks into place.
  8. The canister is correctly installed when the rear face of the canister is flush with the rear edge of the enclosure. If the enclosure is powered and the canister is correctly installed, the canister starts automatically. Repeat step 5, if the canister is not correctly installed.
  9. Reinsert the data cables into the ports that they were originally connected.
  10. If no node canisters are online, the system is not online. To recover the system in the case when no node canisters are online, see Recover system procedure.
  11. If the control enclosure is a FlashSystem 5015, and the new node canister is running software earlier than 8.4, then Upgrade the new node canister to the latest 8.4 PTF using either the satask installsoftware -file <package> -ignore command, or the service assistant GUI "install software" action.
  12. If only the replacement node is in service state with node error 503, apply Procedure: Rescuing node canister software from another node (node rescue) to rescue the replacement node canister.
    Attention:

    If the replacement node gives node error 503, that might be because the node canister code level was too old to recognize a FlashSystem 5015 control enclosure.

    If the code on the new node canister is older than 8.4.0.1, then you need to use the service CLI or service assistant to install 8.4.0.2 or later version on to the new node canister.

  13. When the node canister is powered up, it is automatically added to the system and the system automatically ensures that the machine code version on the new canister matches that of the other node canister in the control enclosure. This is reflected in the system event log.
  14. When the canister is back online, check the event log for any new events that might indicate a problem with the reassembly.