Go to main content
Oracle® ZFS Storage ZS5-ES Service Manual, Release OS8.7.x

Exit Print View

Updated: August 2017

Resync the SP Password with the Host

  1. After the system reboots, go to the SP login by entering:
    ESC (
  2. Go to the /SP/users/root directory:
    > cd /SP/users/root
  3. Set the host password by entering:
    > set password=<enter host password>

    Optionally, set a new password.

  4. Verify that the product serial number has automatically updated.
    1. Log in to Oracle ILOM.
    2. Enter set SESSION mode=restricted.
      Oracle(R) Integrated Lights Out Manager
      Copyright (c) 201x, Oracle and/or its affiliates. All rights reserved.
      -> set SESSION mode=restricted
      WARNING: The "Restricted Shell" account is provided solely
      to allow Services to perform diagnostic tasks.
    3. Enter showpsnc.
      [(restricted_shell) x5-x-sp:~]$ showpsnc
      Primary: fruid:///SYS/PDB
      Backup 1: file:///persist/psnc_backup1.xml
      Backup 2: fruid:///SYS/CONNBD
      Element           | Primary           | Backup 1          | Backup 2          
      Container Status    Valid               Valid               Valid              
      PPN                 4702897-1           4702897-1           4702897-1          
      PSN                 1039BDR07E          1039BDR07E          1039BDR07E         
      MACADDR             00:21:28:A6:7A:FA   00:21:28:A6:7A:FA   00:21:28:A6:7A:FA  
      HOSTID              85a67afa            85a67afa            85a67afa
    4. Verify that the PSN element is consistent for Primary, Backup 1, and Backup 2.

      See document number 1280913.1 on My Oracle Support for troubleshooting help on updating product serial numbers.

    5. Enter exit to exit the restricted shell.
      [(restricted_shell) x5-x-sp:~]# exit
  5. After the motherboard is replaced and the controller has rejoined the cluster, perform a manual failback operation to return resource ownership to both controllers.
    • From the BUI of the controller that was not serviced, go to Configuration > Cluster and click FAILBACK.

    • Or from the CLI, enter configurationcluster failback.