Server Replacement
Cloud Execution Environment

Contents

1Introduction
1.1Scope
1.2Prerequisites
1.2.1Documents
1.2.2Tools
1.2.3Data
1.2.4Conditions

2

Procedure
2.1Preparations for Server Removal
2.2Hardware Replacement and Configuration of the Server
2.3Executing the Installation Command
2.4Fuel Synchronization
2.5Concluding Routine

Reference List

1   Introduction

The document provides instructions on how to replace a server in the Cloud Execution Environment (CEE). Throughout this document Compute host hardware is referred to as server.

1.1   Scope

This document describes how to replace a server in the CEE.

The document is applicable for the replacement of the following servers:

1.2   Prerequisites

This section provides information on the documents, tools, and conditions that apply to the procedure.

1.2.1   Documents

Before starting this procedure, ensure that the following documents have been read and understood:

The following document is referred and used in this procedure:

1.2.2   Tools

The following tools are needed:

1.2.3   Data

A site-specific IP and VLAN plan is required.

The address variables used in the document IP and VLAN plan are used throughout this document, and are summarized in the following table.

Table 1    IP Variables Based on the IP and VLAN Plan

VLAN

Variable Name

Factory Default IP Address Allocation

fuel_ctrl_sp

<vFuel (static)>

192.168.0.11

Other site-specific data is listed in the following table:

Table 2    Other Variables Used

Resource

Variable Name

Additional Information

External vCIC IP address

<vcic_address>

 

Personal user name to the vCIC

<personal-user>

 

Password for the personal username to the vCIC

   

Password for the root user on vFuel

   

Name of the host to be replaced

<hostname>

Host names are specified by the following scheme:


compute-<shelf_number>-<blade_number>

1.2.4   Conditions

Before starting this procedure, ensure that the following conditions are met:

2   Procedure

This procedure describes how to replace a server.

The procedure contains the following activities:

  1. Preparations for server removal, see Section 2.1.
  2. Hardware replacement of the server and server BIOS configuration, see Section 2.2.
  3. Executing the installation command, see Section 2.3.
  4. Concluding Routine, see Section 2.5.

Start the procedure with Section 2.1.

2.1   Preparations for Server Removal

This section describes how to prepare for changing a server.

  1. Inform the Operation and Maintenance Center (OMC) that work is in progress on the node with possible disturbance to the service.
  2. Check current alarms to have a baseline for the same checks after compute host has been changed.
  3. Log in to an active vCIC with the logon credentials given in the site documentation.

    ssh <personal-user>@<vcic_address>

    Example:

    ssh <personal-user>@10.0.22.10

  4. If prompted, provide the user password.
  5. Log on to vFuel by using SSH:

    ssh root@<vFuel (static)>

    Example:

    ssh root@192.168.0.11

  6. If prompted, provide the user password.
  7. Remove the node by issuing the following command on the vFuel node:

    removeceenode --name <hostname>

    If the removal fails, stop the process and consult the next level of support. Further actions are outside the scope of this instruction.

  8. Log out from vFuel:

    exit

  9. Log out from vCIC:

    exit

  10. Continue with Section 2.2.

2.2   Hardware Replacement and Configuration of the Server

Perform the following steps:

  1. Depending on the used HW infrastructure, refer to the relevant instruction indicated below and perform the steps provided for hardware installation of the server including BIOS configuration:
    Note:  
    In the case of unmanaged servers, before the execution of the installation command, the new server needs to be discovered in vFuel. After the new server has been configured, do the following:
    1. Set the boot device to PXE.
    2. Force restart the server.
    3. Verify in vFuel that the new server has been discovered.

  2. Continue with Section 2.3.

2.3   Executing the Installation Command

Perform the following steps:

  1. Log on to a vCIC by using SSH:

    ssh <personal-user>@<vcic_address>

    Example:

    ssh <personal-user>@10.0.22.10

  2. If prompted, provide the user password.
  3. Log on to vFuel using SSH:

    ssh root@<vFuel (static)>

    Example:

    ssh root@192.168.0.11

  4. If prompted, provide the user password.
  5. If the replacement server has different characteristics from those of the old server (for example, if GEP5 blade is exchanged to GEP7), update the server parameter in the /mnt/cee_config/config.yaml file. For more information, refer to the platform-related System Dimensioning Guide and the Configuration File Guide.
  6. Issue the following command in order to start the installation:

    expandcee --repair

    Note:  
    Verification for the newly replaced server is also performed by the command.

  7. Do the relevant action:
    • If the installation ends without issues, continue with Step 11.
    • If the command execution fails, continue with Step 8.
  8. Collect the console printout.
  9. Collect all logs by referring to Data Collection Guideline.
  10. Consult the next level of maintenance support. Stop this workflow. Further actions are outside the scope of this instruction.
  11. Log out from vFuel:

    exit

  12. Continue with Section 2.4.

2.4   Fuel Synchronization

In order to synchronize Fuel VM, follow the instructions in Fuel Synchronization.

Continue with Section 2.5.

2.5   Concluding Routine

Perform the following steps:

  1. Check that there are no additional active alarms. If new active alarms are found, act on them according to the relevant Alarm OPI.
  2. Check that there are no alerts created during the repair process. If any such alerts are present, act on them according to the relevant OPI.
  3. Log out from the vCIC.

    exit

  4. Collect all tools and equipment.
  5. Report that the server has been replaced.
  6. Handle the removed unit according to company proceduresregarding repair and data security.
    Note:  
    Sensitive data may be present on the disk.

  7. Carry out any remaining actions according to the work order, if applicable.
  8. The job is completed.

Reference List

[1] Manage Blade, 53/1543-APR 901 0549/1
[2] Hyperscale Datacenter System 8000 Customer Documentation, 2/1551-LZN 901 5032


Copyright

© Ericsson AB 2016. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

Trademark List
All trademarks mentioned herein are the property of their respective owners. These are shown in the document Trademark Information.

    Server Replacement         Cloud Execution Environment