Finalizing and verifying the replacement server configuration

NAS Platform Series 5000 Hardware Reference

Version
15.1.x
Audience
anonymous
Part Number
MK-92HNAS089-09

The maximum Fibre Channel (FC) link speed on the NAS Platform Series 5000 is 16 Gbps.

On the replacement server:

  1. Navigate to Home > Server Settings > License Keys to load the license keys.
  2. Remove the previous license keys in the backup file, then add the new keys.
  3. Use fc-link-speed to verify and, if necessary, configure the FC port speed as required. For example:
    1. Enter fc-link-speed to display the current settings.
    2. Enter fc-link-speed -i port_number -s speed for each port.
    3. Enter fc-link-speed to verify the settings.
  4. Modify zoning and switches with the new WWPN, if you are using WWN-based zoning.
    If you are using port-based zoning, no modifications are necessary for the switch configurations.
  5. Open Device Manager - Storage Navigator and re-configure the LUN mapping and host group on the storage system that is dedicated to the server with the new WWPNs. Perform this step for every affected server port.
  6. If the server does not recognize the system drives, enter fc-link-reset to reset the fiber paths.
  7. Enter the sdpath command to display the path to the devices (system drives) and the port and storage port that are used.
  8. Enter the sd-list command to verify the system drive statuses are OK and that access is allowed.
  9. Use the CLI to verify that the new node has access to the system drives. Use sd-list from the node that you have just replaced.
    For example: pn x sd-list where x is the node number in the cluster.
    FSS-HNAS-1:$ sd-list
    Device  Status  Alw  GiByte  Mirror   In span        Span Cap
    -----   ------  ---  ------  ------   -------        --------
    0       OK      Yes   1607   Pri      FSS_Pool_1     3214 
    1       OK      Yes   1607   Pri      FSS_Pool_1     3214 
    4       OK      Yes    390   Pri      FSS_AMS200     1560
    5       OK      Yes    390   Pri      FSS_AMS200     1560
    6       OK      Yes    390   Pri      FSS_AMS200     1560
    7       OK      Yes    390   Pri      FSS_AMS200     1560
           
  10. Enter span-list to verify the storage pools (spans) are accessible.
    Note: In this instance, cluster is synonymous with the stand-alone server.
  11. Enter the span-list-cluster-uuids span_label command to display the cluster serial number (UUID) to which the storage pool belongs.
    The UUID is written into the storage pool configuration on disk (COD). The COD is a data structure stored in every SD, which provides information how the different SDs are combined into different stripesets and storage pools.
  12. Enter the span-assign-to-cluster span_label command to assign all the spans to the new server.
  13. If EVS mapping or balancing is required, select the EVS to migrate, assign it to the preferred node, then click migrate.


  14. To set the preferred node for any remaining EVSs, navigate to Home > Server Settings > EVS Management > EVS Details.


  15. Select the node from the Preferred Cluster Node list, then click apply.
  16. Reconfigure any required tape backup application security.
  17. Navigate to Home > Status & Monitoring > Event Logs, and click Clear Event Logs.
  18. Navigate to Home > Status & Monitoring > System Monitor and verify the server status:
    • If the server is operating normally and is not displaying any alarm conditions, run a backup to capture the revised configuration, then download another diagnostic to support. Permanent license keys for the replacement server are normally provided within seven days.
    • If the server is not operating normally for any reason, contact Customer Support for assistance.
  19. Navigate to Home > Server Settings > Cluster Configuration to verify the cluster configuration status. Verify the cluster is shown as Online and Robust and has the correct number of nodes.
    cluster configuration
  20. Confirm all final settings, IP addresses, customer contact information, service restarts, client access, and that customer expectations are all in place. Features such as replication and data migration must all be confirmed as working, and all file systems and storage pools must be online.