Removing and reseating a node canister

To access or replace some components during service procedures, a canister might need to be temporarily removed from, and reinserted into, the enclosure.

Before you begin

Note: This topic provides instructions for temporarily removing and replacing a canister and should be used only when instructed to do so by other service procedures. To replace a faulty node canister with one from FRU stock, follow the procedure that is described in Removing and replacing a faulty node canister.
Make a note of the following points before replacing a canister:
  • No tools are required to complete this task. Do not remove or loosen any screws.
  • Before removing a canister, it must be powered off or be in service state. Otherwise, it can result in loss of data or loss of access to data.
  • If a canister was recently removed from the system, and then added again, ensure that the canister is online for at least 25 minutes before you remove its partner canister. This delay allows multipath drivers to fail over to the online canister when the partner canister is removed.
  • Use care when you remove a canister from the enclosure. Have a flat surface ready to receive the canister after removal.
  • Use care when you lift and insert the canister.
Before you start the removal procedure, make sure to transfer the following components from the faulty canister to the replacement canister:
  • DIMMs
  • PCIe adapters
  • Backup battery

To remove and reinsert a canister in the enclosure, complete the following steps.

Procedure

  1. Shut down the canister by using the service assistant. Follow the steps in Procedure: Powering off a node canister.
  2. Use the LED indicators on the canister to confirm that it is safe to remove it from the enclosure, as described in Node canister indicators.
  3. Record which data cables are plugged into the specific ports on the rear of the canister. The cables must be inserted back into the same ports after the replacement is complete; otherwise, the system cannot function properly.
  4. Disconnect the data cables that are connected to the canister.
  5. Locate the left and right release levers for the canister, marked by blue touchpoints on the ends of the levers.
  6. Holding the canister release levers by the blue touch points, open the two levers horizontally 90 degrees, then slide the canister out of the enclosure and place it onto an antistatic mat.
    Figure 1. Removing and replacing the canister
  7. To reinstall the canister, ensure that both of the canister release levers are fully open (90 degrees relative to the canister), and then slide the canister into the enclosure, ensuring that both release levers engage with the canister and begin to close.
  8. Press the release levers closed to lock the canister into the enclosure. Press the latch ends to ensure that the latches are engaged with the canister.
  9. Reconnect all cables that were removed from the back of the canister.
  10. If the canister does not begin to power up, check that it is fully inserted into the enclosure. If necessary, remove the power and cables; then, repeat steps 7 through 10.
  11. Connect directly with the replaced canister CLI. Using the following methods:
    1. Via technician port (DHCP) at 192.168.0.1
    2. Via service IP on ethernet port1, if known (blank USB key to retrieve if needed).

    If unable to connect, refer to Resolving a problem with failure to boot.

    Once connected issue sainfo lsservicenodes command to verify the node status.

    Note: Node error code 545 is expected. For more information, see 545.

    If error 545 is present, issue command satask chbootdrive -replacecanister to update the drives to match the serial number of the new node canister. The node will automatically reboot and join cluster.

    To help identify the node canister, the inside of the release levers is labeled with the serial number.

  12. Use the management GUI or service assistant GUI to check that the node canister is online (or is Active) in the system.
  13. Review the management GUI to determine that all errors are resolved.