Avamar Data Store Gen4T Platform

Rekickstart Procedures
302-005-041
Rev C03
March 2020
 Copyright © 2016-2020 Dell Inc. or its subsidiaries. All rights reserved.

Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS-IS.” DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND
WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED
IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.

Dell Technologies, Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property
of their respective owners. Published in the USA.

Dell EMC
Hopkinton, Massachusetts 01748-9103
1-508-435-1000 In North America 1-866-464-7381
www.DellEMC.com

2 Avamar Data Store Gen4T Platform Rekickstart Procedures

CONTENTS

Preface 5

Chapter 1 Overview 7
About this procedure.......................................................................................... 8
Compatibility..........................................................................................8
Obtain a rekickstart ISO image........................................................................... 8
Before you begin.................................................................................................9
Remote rekickstarts............................................................................. 10

Chapter 2 General Information 11

Establish a serial connection to a Gen4T node or server.................................... 12
Connect the laptop to a Gen4T RMC port......................................................... 13
Verify checksums in Microsoft Windows........................................................... 15
Verify checksums in Linux................................................................................. 15
Add an Avamar node or server to the Java site exception list............................ 16

Chapter 3 Rekickstarting 19
Rekickstarting with RMC.................................................................................. 20
Configure RMC.................................................................................... 20
Review the RMC configuration............................................................. 21
Mount the ISO image or a local DVD as a virtual DVD drive..................22
Boot the node from the virtual DVD drive (SLES11SP4).......................25
Boot the node from the virtual DVD drive (SLES12).............................27
Rekickstarting with a USB DVD drive................................................................ 31
Boot the node from a USB DVD drive (SLES11SP4).............................32
Boot the node from a USB DVD drive (SLES12)...................................35

Chapter 4 Post-requisites 41
Check for successful completion (SLES11SP4).................................................42
Check for successful completion (SLES12).......................................................43
Configure the power/reset button.................................................................... 44
Clear the RMC configuration............................................................................ 45
Apply the new RMC configuration.................................................................... 45
Record service tag information......................................................................... 47
Register the product with the Install Base Group..............................................48
Create a case using the Avamar Install Base audit form on the Business
Services portal..................................................................................... 49

Avamar Data Store Gen4T Platform Rekickstart Procedures 3

Contents

4 Avamar Data Store Gen4T Platform Rekickstart Procedures

Preface

As part of an effort to improve its product lines, Dell EMC periodically releases revisions of its
software and hardware. Therefore, some functions that are described in this document might not
be supported by all versions of the software or hardware currently in use. The product release
notes provide the most up-to-date information on product features.
Note: This document was accurate at publication time. To find the latest version of this
document, go to Online Support (https://support.EMC.com).
Purpose
This guide describes how to rekickstart one Avamar Data Store (ADS) Gen4T node by using the
remote management console (RMC) or a USB DVD drive. This process destroys all data on the
node, re-creates all partitions, and then reloads the operating system. The node is left in a state
equivalent to having arrived from the factory.
Do not follow this procedure unless explicitly directed to do so by Customer Support.
Audience
The information in this guide is intended for Dell EMC service personnel and Authorized Service
Partners who are responsible for installing and maintaining Avamar servers.
Related documentation
The following publications provide additional information:
l Avamar Data Store Gen4T Platform Hardware Installation Procedures
l Avamar Data Store Shutdown or Reboot Procedure
Special notice conventions used in this document
These conventions are used for special notices.
DANGER Indicates a hazardous situation which, if not avoided, results in death or serious
injury.
WARNING Indicates a hazardous situation which, if not avoided, could result in death or
serious injury.
CAUTION Indicates a hazardous situation which, if not avoided, could result in minor or
moderate injury.
NOTICE Addresses practices that are not related to personal injury.

Note: Presents information that is important, but not hazard-related.

Typographical conventions
These type style conventions are used in this document.

Table 1 Typographical conventions

Bold Used for names of interface elements, such as names of windows,

dialog boxes, buttons, fields, tab names, key names, and menu paths
(what the user specifically selects or clicks)

Italic Used for full titles of publications that are referenced in text

Avamar Data Store Gen4T Platform Rekickstart Procedures 5

Preface

Table 1 Typographical conventions (continued)

Monospace Used for:

l System code
l System output, such as an error message or script
l Pathnames, filenames, prompts, and syntax
l Commands and options

Monospace italic Used for variables

Monospace bold Used for user input

[] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means “or”

{} Braces enclose content that the user must specify, such as x or y or
z

... Ellipses indicate nonessential information that is omitted from the

example

Where to get help

The Avamar support page provides access to licensing information, product documentation,
advisories, and downloads, as well as how-to and troubleshooting information. This information
may resolve a product issue before contacting Customer Support.
To access the Avamar support page:
1. Go to https://www.dell.com/support/home/us/en/19.
2. Type a product name in the Enter a Service Tag, Serial Number, Service Request, Model,
or Keyword search box.
3. Select the product from the list that appears. When you select a product, the Product
Support page loads automatically.
4. (Optional) Add the product to the My Products list by clicking Add to My Saved Products in
the upper right corner of the Product Support page.
Comments and suggestions
Comments and suggestions help to continue to improve the accuracy, organization, and overall
quality of the user publications. Send comments and suggestions about this document to
[email protected].
Please include the following information:
l Product name and version
l Document name, part number, and revision (for example, 01)
l Page numbers
l Other details to help address documentation issues

6 Avamar Data Store Gen4T Platform Rekickstart Procedures

CHAPTER 1
Overview

This chapter contains the following topics:

l About this procedure...............................................................................................................8

l Obtain a rekickstart ISO image................................................................................................8
l Before you begin..................................................................................................................... 9

Avamar Data Store Gen4T Platform Rekickstart Procedures 7

Overview

About this procedure

This guide describes how to rekickstart one Avamar Data Store (ADS) Gen4T node by using the
remote management console (RMC) or a USB DVD drive. It covers kickstarting with both SLES 11
and SLES 12, as described in this chapter.
This process destroys all data on the node, re-creates all partitions, and then reloads the operating
system. The node is left in a state equivalent to having arrived from the factory.
Do not follow this procedure unless you are explicitly directed to do so by Customer Support.
Rekickstarting is valid for the following scenarios:
l New ADS nodes from the factory that were incorrectly imaged.
l New ADS nodes from the factory whose storage was incorrectly configured.
l ADS nodes with storage failures that require new operating system installation.
If you must perform a rekickstart as part of a break/fix activity, contact Customer Support for
assistance. Do not perform a rekickstart unless explicitly directed to do so by Customer Support.
The Customer Services team is responsible for performing break/fix rekickstart activities.
Non-break/fix activities, such as repurposing existing hardware or moving hardware to a new
location, are not covered by maintenance. If you must perform a rekickstart as part of an activity
that is not break/fix, engage Professional Services or an Authorized Service Partner to quote for
this activity.
These teams engage Customer Services to perform the rekickstart and subsequent hardware
installation procedure. Customer Services time is then charged back to the appropriate project.
After the rekickstart, Professional Services reinstalls and reimplements the Avamar server.
CAUTION Always verify the identity of the node before you perform the rekickstart procedure.
Dell EMC recommends that you use more than one method to verify the identity of the node.

Compatibility
This procedure contains tasks to kickstart with SLES11SP4, SLES12SP4, and SLES12SP5. The
kickstart ISO image design for each OS and, by extension, the tasks are very similar.
Before you continue, select the OS version that matches the desired Avamar release.

Table 2 Kickstart compatibility

Avamar release SLES OS version

19.1 or earlier SLES11SP4

19.2 SLES12SP4

19.3 or later SLES12SP5

Obtain a rekickstart ISO image

The GA Avamar SuSE Linux Enterprise Server (Gen4T) 64-bit ISO images are single DVD images
that support all approved Avamar Gen4T hardware configurations for a particular operating
system.
Obtain the required files from the download links in SolVe Desktop by selecting Avamar Install and
Upgrade Procedures > Avamar Software Download Links.

8 Avamar Data Store Gen4T Platform Rekickstart Procedures

 Overview

Dell EMC recommends that you download the required files to the laptop or USB memory stick
before you go to the customer site.
General Information on page 11 provides more information about how to verify checksums for
the ISO images.
Required files for SLES11SP4
Gen4T rekickstart ISO image:
l ADS4T-SLES11-SP4-64-<VERSION>.iso
l ADS4T-SLES11-SP4-64-<VERSION>.iso.sha256
where <VERSION> is the current ISO image release for SLES11.
Required files for SLES12SP4
Gen4T rekickstart ISO image:
l ADS-SLES12.4-<VERSION>.iso
l ADS-SLES12.4-<VERSION>.iso.sha256
where <VERSION> is the current ISO image release for SLES12.
Required files for SLES12SP5
Gen4T rekickstart ISO image:
l ADS-SLES12.5-<VERSION>.iso
l ADS-SLES12.5-<VERSION>.iso.sha256
where <VERSION> is the current ISO image release for SLES12.

Before you begin

There are two ways to rekickstart an ADS Gen4T node:
l Mount the ISO image or a physical DVD as virtual media, and then use the RMC virtual console.
Virtual media is convenient when you do not have a USB DVD drive. You can use the RMC
whether you are remote or onsite.
l Burn a physical DVD from the ISO image, and then connect a USB DVD drive.
Use DVD burning software to burn the kickstart ISO image to a DVD.
Follow the tasks for the selected method, plus the tasks in Post-requisites on page 41. Some
tasks are indicated for different versions of the SLES operating system. Ensure that you perform
the tasks that correspond to the selected kickstart ISO image.
General Information on page 11 provides more information about tasks that apply throughout this
procedure.
Note:
The rekickstart procedure does not configure the network interfaces on the node. After you
complete this procedure, use the Avamar Data Store Gen4T Platform Hardware Installation
Procedures to complete the node installation and implementation before you install the Avamar
software.
SolVe Desktop provides the Avamar Data Store Gen4T Platform Hardware Installation Procedures
at Avamar > Avamar Install and Upgrade Procedures > Avamar Installation Procedures >
Hardware Installation.

Avamar Data Store Gen4T Platform Rekickstart Procedures 9

Overview

Remote rekickstarts
You cannot perform a remote rekickstart through SSH. Remotely rekickstarting a node requires
the RMC.
This procedure contains tasks to configure the RMC ports. If the RMC ports are not configured,
work with the customer to obtain the necessary network configuration and ensure that the RMC
interface is connected. Then, use SSH to configure one of the ports. Alternatively, perform the
rekickstart onsite.

10 Avamar Data Store Gen4T Platform Rekickstart Procedures

CHAPTER 2
General Information

This chapter contains the following topics:

l Establish a serial connection to a Gen4T node or server........................................................ 12

l Connect the laptop to a Gen4T RMC port..............................................................................13
l Verify checksums in Microsoft Windows................................................................................15
l Verify checksums in Linux......................................................................................................15
l Add an Avamar node or server to the Java site exception list................................................ 16

Avamar Data Store Gen4T Platform Rekickstart Procedures 11

General Information

Establish a serial connection to a Gen4T node or server

Gen4T nodes and servers have no local ports for keyboard, mouse, or video. A serial console port
on the rear I/O panel replaces these functions and provides you with direct console access.
About this task
Use the following steps when a procedure instructs you to make a serial connection to an Avamar
node or server:
Procedure
1. Connect a null modem cable between the RS-232 port on the laptop and the serial console
port on the rear I/O panel.
Figure 1 Serial console port

If the laptop does not have an RS-232 port, use a USB-to-serial adapter instead.

2. If you know the COM port number that is assigned to the serial port on the laptop, go to the
next step. Otherwise, the following substeps describe how to determine the COM port
number:
a. Click the Start menu and then type Device Manager.
b. Click the Device Manager icon and then click Yes on the User Account Control dialog
box.
c. Locate and expand the Ports (COM & LPT) category.

12 Avamar Data Store Gen4T Platform Rekickstart Procedures

 General Information

Figure 2 Device Manager results for serial ports

d. Note the COM port number that Windows assigned to the serial port.
If Device Manager lists multiple COM ports and you are unsure which port is correct, you
may need to try each port in turn until you determine the correct COM port number.
e. Close Device Manager.
3. Open PuTTY.
4. Change the Connection Type to Serial.
5. Configure a serial connection to the node or server using the correct COM port and the
following parameters:

Table 3 Serial port parameters

Baud rate 115200

Parity None

Data bits 8

Stop bits 1

Hardware flow control None

Terminal type Linux

To configure serial port settings in PuTTY, click the Connection > Serial category in the
PuTTY Configuration window.

6. Configure PuTTY to use Linux keyboard sequences.

To select keyboard sequences in PuTTY, click the Terminal > Keyboard category in the
PuTTY Configuration window.

7. Click Open.
The terminal window opens. If you receive only a black screen, you may need to press Enter
to bring up the login prompt.

Connect the laptop to a Gen4T RMC port

Configure the laptop for a static IP address that is compatible with the active IP address and
subnet on the RMC port. You must have an unused IP address in this range and know whether to
connect to the shared or dedicated RMC port.
About this task
Windows 10 provides several different methods to open the Network and Sharing Center. For
consistency, this task describes one method.

Avamar Data Store Gen4T Platform Rekickstart Procedures 13

General Information

Procedure
1. From the search box on the Start menu or the taskbar, type control panel, and then
select Control Panel from the list of results.
2. You can configure the Control Panel for one of three views using the View By drop-down:
Category, Large Icons, and Small Icons. The latter two are functionally identical.
l For Category view, click View network status and tasks.
l For Icon view, click Network and Sharing Center.
3. In the left pane, click Change Adapter Settings.
4. Right-click Local Area Connection, and then select Properties.
5. Double-click Internet Protocol Version 4 (TCP/IPv4).
6. Select Use the following IP address.
7. Set the IP address to the provided IP address.
8. Set the Subnet mask to 255.255.255.0.
9. Setting a Default gateway is not necessary.
10. Click OK to close the Internet Protocol Version 4 (TCP/IPv4) Properties sheet.
11. Click OK to close the Local Area Connection Properties sheet.
12. At a Windows command prompt, type ipconfig to ensure that the new IP address is
active.
If not, right-click Local Area Connection, disable the connection, and then re-enable it.
13. Using an Ethernet Cat6 cable, connect the laptop to the correct RMC port on the rear I/O
panel.
Figure 3 Gen4T RMC ports

1 2

1. RMC dedicated port 2. RMC shared port

14 Avamar Data Store Gen4T Platform Rekickstart Procedures

 General Information

Verify checksums in Microsoft Windows

This topic provides instructions about how to verify checksums for downloaded files before you
transfer them from the laptop to an Avamar node or server. Verify the integrity of all downloaded
files, especially before you use an offline or indirect method to transfer downloaded files.
Most Avamar downloads use SHA-256 checksums. Some older downloads may use MD5
checksums.
SHA-256 checksums
To verify a SHA-256 checksum, open the command prompt and type the following command:
certutil -hashfile <FILE> SHA256
where <FILE> is the name of the downloaded file. If the downloaded file is not located in the
current directory, the file path is also required.
The console displays output similar to the following:
SHA256 hash of file C:\ProgramData\EMC\SolVeDesktop\AVAMAR.SOLVE\Tools\stunnel-4
.36-0.10.2.x86_64.rpm:
61 00 a8 28 82 99 86 f6 0c 43 dd e4 f8 8d 44 53 25 ab 55 48 1f 50 d9 9d 65 4a
87 70 67 54 f7 b2
CertUtil: -hashfile command completed successfully.

Compare the computed checksum to the checksum that you obtained with the downloaded file.
The output of this command contains spaces, while the checksum file does not.
MD5 checksums
The Microsoft File Checksum Integrity Verifier (FCIV) tool is a convenient way to compute MD5
checksums for downloaded files. Microsoft KB841290 provides information about how to obtain
and use this tool. Compare the computed checksum to the checksum that you obtained with the
downloaded file.
Note: Though Microsoft no longer supports the FCIV tool, you can still use the FCIV tool with
Windows 7 and Windows 10.

Verify checksums in Linux

This topic provides instructions about how to verify checksums for downloaded or copied files.
Verify the integrity of all downloaded files, especially before and after you use an offline or indirect
method to transfer downloaded files.
Most Avamar downloads use SHA-256 checksums. Some older downloads may use MD5
checksums.
After you download or copy a file and the corresponding checksum file to an Avamar node or
server, verify the checksum by typing one of the following commands:

SHA-256 sha256sum -c <FILE>*.sha256*

MD5 md5sum -c <FILE>*.md5sum

where <FILE> is the name of the downloaded file.

The console displays output similar to the following:
AvamarUpgrade.avp: OK

Avamar Data Store Gen4T Platform Rekickstart Procedures 15

General Information

The checksum utility automatically compares the computed checksum to the value from the
checksum file. Observe the output for errors.

Add an Avamar node or server to the Java site exception list

This task applies if you receive a security error when you try to launch a Java application such as
the RMC viewer. Newer versions of Java require that you trust the source of Java applications.
Procedure
1. For Windows 10, from the search box on the Start menu or the taskbar, type control
panel, and then select Control Panel from the list of results.
2. Change the Control Panel to icon view.
The Control Panel can be configured for one of three views using the View By drop-down:
Category, Large Icons, and Small Icons. The latter two are functionally identical.
Change the View by selection to Large or Small Icons.

3. Double-click Java (32-bit).

The Java Control Panel opens.
4. Click the Security tab.

16 Avamar Data Store Gen4T Platform Rekickstart Procedures

 General Information

Figure 4 Java Control Panel

5. Click Edit Site List to open the Exception Site List.

Figure 5 Exception Site List

6. Click Add.

Avamar Data Store Gen4T Platform Rekickstart Procedures 17

General Information

7. In the new row, type the following:

http://<AvamarRMC>:80

where <AvamarRMC> is the hostname or IP address for the RMC port on the node.

8. Click OK to close the Exception Site List.

9. Click OK to close the Java Control Panel.
10. Close the Control Panel.
11. Launch the Java application again.

18 Avamar Data Store Gen4T Platform Rekickstart Procedures

CHAPTER 3
Rekickstarting

This chapter contains the following topics:

l Rekickstarting with RMC...................................................................................................... 20

l Rekickstarting with a USB DVD drive.....................................................................................31

Avamar Data Store Gen4T Platform Rekickstart Procedures 19

Rekickstarting

Rekickstarting with RMC

Mount the ISO image or a physical DVD as virtual media, and then boot from the rekickstart image.
Before you begin, obtain the RMC configuration details from the customer. Verify the status of the
RMC ports and then determine the correct course of action.
l Scenario 1: The RMC ports are not configured.
l Scenario 2: An RMC port is configured and the customer intends to retain this configuration.
l Scenario 3: An RMC port is configured and the customer does not intend to retain this
configuration.
Only certain tasks apply to each scenario, including parts of the Post-requisites on page 41.

Configure RMC
This task applies when performing a rekickstart onsite with RMC, where the RMC ports are not
configured (Scenario 1).
About this task
A Gen4T node can communicate with a management client through either the eth0 (RMC shared)
or the RMC dedicated ports. Regardless of whether you use the shared or dedicated port, apply a
temporary configuration for the duration of the rekickstart procedure.
Procedure
1. Establish a serial console connection to the node.
2. Log in as the admin user.
3. Change to the root user by typing the following command:
su -

4. For SLES11, determine the current kickstart version tag by typing the following command:
ls /sles*

The console displays output similar to the following:

/sles11-SP3-64v01.32
5. For SLES12, determine the current kickstart version by typing the following command:
cat /PlatformInfo

Output similar to the following appears:

KS_OS_NAME="SUSE Linux Enterprise Server"
KS_OS_VERSION="12"
KS_OS_PATCHLEVEL="4"
KS_VERSION="1.61"
KS_PRODUCT="DellEMC Avamar Server"
KS_MODEL="accelerator"
KS_PLATFORM="ADS4T"
6. Configure the RMC port by typing the following commands:
ipmitool lan set 1 ipsrc static
ipmitool lan set 4 ipsrc static
ipmitool lan set <CHANNEL> ipaddr 169.254.1.100
ipmitool lan set <CHANNEL> netmask 255.255.255.0
ipmitool lan set <CHANNEL> defgw ipaddr 169.254.1.101

20 Avamar Data Store Gen4T Platform Rekickstart Procedures

 Rekickstarting

where <CHANNEL> is 1 or 4, corresponding to the eth0 (RMC shared) and RMC dedicated
ports, respectively.

7. Set the temporary password for the RMC root user by typing the following commands:
ipmitool user set name 2 root
ipmitool user set password 2 <PASSWORD>
where <PASSWORD> is the chosen password. The default password for the RMC ports is
calvin.

8. Configure the laptop with the IP address 169.254.1.101 and then connect to the selected
RMC port.
Connect the laptop to a Gen4T RMC port on page 13 provides more information.

After you finish

At the end of the rekickstart procedure, follow the steps to clear the temporary configuration.

Review the RMC configuration

This task applies when performing a rekickstart onsite using RMC, where the RMC port is already
configured (Scenarios 2 & 3).
About this task
A Gen4T node can communicate with a management client through either the eth0 (RMC shared)
or the RMC dedicated ports. Obtain and record the existing RMC configuration for later use.
Procedure
1. Establish a serial console connection to the node.
2. Log in as the admin user.
3. Change to the root user by typing the following command:
su -

4. For SLES11, determine the current kickstart version tag by typing the following command:
ls /sles*

The console displays output similar to the following:

/sles11-SP3-64v01.32
5. For SLES12, determine the current kickstart version by typing the following command:
cat /PlatformInfo

Output similar to the following appears:

KS_OS_NAME="SUSE Linux Enterprise Server"
KS_OS_VERSION="12"
KS_OS_PATCHLEVEL="4"
KS_VERSION="1.61"
KS_PRODUCT="DellEMC Avamar Server"
KS_MODEL="accelerator"
KS_PLATFORM="ADS4T"
6. Save the current RMC configuration by typing the following commands:
ipmitool lan print 1 > /usr/local/avamar/src/rmclan1
ipmitool lan print 4 > /usr/local/avamar/src/rmclan4

Avamar Data Store Gen4T Platform Rekickstart Procedures 21

Rekickstarting

Note:
Channel 1 corresponds to the eth0 (RMC shared) port. Channel 4 corresponds to the
RMC dedicated port.
The current RMC root password cannot be saved in this manner. Obtain the RMC root
password from the customer.

7. Review the contents of the RMC configuration files and record the values. If required, copy
them to the laptop using SCP or a USB memory stick.
To restore the RMC settings later, use these saved values.
8. Configure the laptop with an unused IP address on the same subnet and then connect to the
selected RMC port.
For example, if the RMC port IP address is 10.100.200.1, use 10.100.200.2.
Connect the laptop to a Gen4T RMC port on page 13 provides more information.

Mount the ISO image or a local DVD as a virtual DVD drive

This task applies to all scenarios (1, 2, and 3).
About this task
Use the RMC to present the rekickstart image directly from the ISO or, if you have already burned
the image to a DVD, from a local DVD drive.
Procedure
1. If the node is part of an operating Avamar server, use the Avamar Data Store Shutdown or
Reboot Procedure in SolVe Desktop to perform a graceful shutdown of the Avamar software
on the node.
Note: You do not need to shut down the entire Avamar server.

2. In a web browser, type the following:

https://<AvamarRMC>
where <AvamarRMC> is the hostname or IP address that is assigned to the RMC port on
the node.
Acknowledge any browser warnings about self-signed certificates.

3. Log in to the RMC as the root user.

4. In the left pane, click vKVM & vMedia.
The Virtual KVM and Media Launch page opens.

22 Avamar Data Store Gen4T Platform Rekickstart Procedures

 Rekickstarting

Figure 6 Virtual KVM and Media Launch page

5. Click Launch Java VM Client.

You are prompted to download data.jnlp. Open this file and leave the web browser open.
If you receive a security warning (Do you want to run this application?), check
the I accept the risk and want to run this application box and click Run.
Figure 7 Java warning

If the RMC prompts that the Java version on the laptop is out of date, ensure that you are
running a current version of Java and then click Later.
If you receive other security errors, Add an Avamar node or server to the Java site exception
list on page 16 provides a resolution.

The Virtual Media Session window opens.

Avamar Data Store Gen4T Platform Rekickstart Procedures 23

Rekickstarting

Figure 8 Virtual Media Session window

6. To mount an ISO image, perform the following substeps:

a. Click Add Image...
b. Browse to the location where you saved the ISO image.
c. Select the ISO image and click Open.
The Client View area lists the ISO image.
d. Check the Mapped box next to the ISO image.
7. To mount a physical DVD, perform the following substeps:
a. Insert the DVD in the local DVD drive and then wait for the operating system to
recognize the DVD.
b. Check the Mapped box next to the local DVD drive.
8. Click Details for more information.
Figure 9 Virtual Media Session window

Ensure that the RMC mounts the ISO image or physical DVD as a CD/DVD drive.

24 Avamar Data Store Gen4T Platform Rekickstart Procedures

 Rekickstarting

Boot the node from the virtual DVD drive (SLES11SP4)

This task applies to all scenarios (1, 2, and 3).
About this task
The rekickstart proceeds automatically as the node boots from the virtual drive. Observe the
process and wait for the rekickstart to complete.
Procedure
1. In the web browser, click Launch Java KVM Client.
The RMC prompts you to download viewer.jnlp(<AvamarRMC>@0@<timestamp>),
where <AvamarRMC> is the hostname or IP address that is assigned to the RMC port on
the node. Open this file.
If you are prompted that Windows cannot open the file:

a. Choose Select a program from a list of installed programs.

b. Click OK.
c. Select Java(TM) Web Start Launcher.
d. Click OK.
If you receive a security warning (Do you want to run this application?), check
the I accept the risk and want to run this application box and then click Run.

The Video Viewer window opens.

2. Log in as the admin user.
3. Change to the root user by typing the following command:
su -

4. Reboot the node by typing the following command:

reboot

5. When you see the BIOS logo, press F2 or Del to enter the BIOS.
Figure 10 BIOS logo

6. Use the left and right arrow keys to move to Save & Exit.

Avamar Data Store Gen4T Platform Rekickstart Procedures 25

Rekickstarting

Figure 11 Save & Exit menu

7. Use the up and down arrow keys to move to the Boot Override section and select
CDROM:MP EMS Virtual Media 0399.
Figure 12 BIOS Boot Override options

8. Press Enter to boot from the rekickstart image.

When the node boots, the SUSE Linux Enterprise Server 11 SP4 boot menu opens.
Figure 13 SUSE Linux Enterprise Server 11 SP4 boot menu

9. Select SLES 11 SP4 <version> for ADS Gen4T (KVM Console) and then press Enter.
where <version> is the version number for the rekickstart image.
10. Select the correct profile for this node from the list and then press Enter.

26 Avamar Data Store Gen4T Platform Rekickstart Procedures

 Rekickstarting

Figure 14 SUSE Linux Enterprise Server 11 SP4 boot profiles

11. Observe the boot and rekickstart process for any errors. The rekickstart process produces
extensive on-screen output, but should not require intervention.
The elapsed time depends on the connection between the computer hosting the ISO image
and the node. You can observe the transfer statistics in the Virtual Media Session window.

During the rekickstart process, the node reboots several times.

Figure 15 Rekickstart process

When you receive the node login: prompt, the rekickstart is complete.
12. If the RMC video viewer or virtual media session times out or disconnects, log in to the RMC
console again. Reopen the Java KVM client or remount the ISO image.

Boot the node from the virtual DVD drive (SLES12)

This task applies to all scenarios (1, 2, and 3). This task applies when kickstarting the node for
SLES12SP4 and SLES12SP5, which have a different sequence of menu prompts than SLES 11.
About this task
The rekickstart proceeds automatically as the node boots from the virtual drive. Observe the
process and wait for the rekickstart to complete.

Avamar Data Store Gen4T Platform Rekickstart Procedures 27

Rekickstarting

Procedure
1. In the web browser, click Launch Java KVM Client.
The RMC prompts you to download viewer.jnlp(<AvamarRMC>@0@<timestamp>),
where <AvamarRMC> is the hostname or IP address that is assigned to the RMC port on
the node. Open this file.
If you are prompted that Windows cannot open the file:

a. Choose Select a program from a list of installed programs.

b. Click OK.
c. Select Java(TM) Web Start Launcher.
d. Click OK.
If you receive a security warning (Do you want to run this application?), check
the I accept the risk and want to run this application box and then click Run.

The Video Viewer window opens.

2. Log in as the admin user.
3. Change to the root user by typing the following command:
su -

4. Reboot the node by typing the following command:

reboot

5. When you see the BIOS logo, press F2 or Del to enter the BIOS.
Figure 16 BIOS logo

6. Use the left and right arrow keys to move to Save & Exit.
Figure 17 Save & Exit menu

7. Use the up and down arrow keys to move to the Boot Override section and select
CDROM:MP EMS Virtual Media 0399.

28 Avamar Data Store Gen4T Platform Rekickstart Procedures

 Rekickstarting

Figure 18 BIOS Boot Override options

8. Press Enter to boot from the rekickstart image.

Wait for the data loss warning to appear.
Figure 19 Data loss warning

9. Press 6 to acknowledge the data loss warning.

The platform selection menu appears. The platform selection menus for SLES12SP4 and
SLES12SP5 are very similar.

Avamar Data Store Gen4T Platform Rekickstart Procedures 29

Rekickstarting

Figure 20 Platform selection menu (SLES12SP4)

Figure 21 Platform selection menu (SLES12SP5)

10. Select ADS Gen4T (KVM Console), and then press Enter.
The node type selection menu appears. The node type selection menus for SLES12SP4 and
SLES12SP5 are identical.

30 Avamar Data Store Gen4T Platform Rekickstart Procedures

 Rekickstarting

Figure 22 Gen4T node type selection menu

11. Select the correct profile for this node from the list and then press Enter.
12. Observe the boot and rekickstart process for any errors. The rekickstart process produces
extensive on-screen output, but should not require intervention.
The elapsed time depends on the connection between the computer hosting the ISO image
and the node. You can observe the transfer statistics in the Virtual Media Session window.

During the rekickstart process, the node reboots several times.

Figure 23 Rekickstart process

When you receive the node login: prompt, the rekickstart is complete.
13. If the RMC video viewer or virtual media session times out or disconnects, log in to the RMC
console again. Reopen the Java KVM client or remount the ISO image.

Rekickstarting with a USB DVD drive

Use the following task to connect a USB DVD drive, and then to boot from the rekickstart image.

Avamar Data Store Gen4T Platform Rekickstart Procedures 31

Rekickstarting

Boot the node from a USB DVD drive (SLES11SP4)

The rekickstart proceeds automatically as the node boots from the DVD drive. Observe the
process and wait for the rekickstart to complete.
Procedure
1. Burn a copy of the ISO image to a DVD.
2. If the node is part of an operating Avamar server, use the Avamar Data Store Shutdown or
Reboot Procedure in SolVe Desktop to perform a graceful shutdown of the Avamar software
on the node.
Note: You do not need to shut down the entire Avamar server.

3. Connect a USB DVD drive to the USB port on the rear I/O panel.
4. Insert the DVD that contains the ISO image.
5. Establish a serial console connection to the node.
6. Press the power/reset button on the rear I/O panel.
Figure 24 Power/reset button

1. Power/reset button

7. When you see the BIOS logo, press F2 or Del to enter the BIOS.

32 Avamar Data Store Gen4T Platform Rekickstart Procedures

 Rekickstarting

Figure 25 BIOS logo

8. Use the left and right arrow keys to move to Save & Exit.
Figure 26 Save & Exit menu

9. Use the up and down arrow keys to navigate to the Boot Override section and highlight
CDROM:.
The remaining text on the CDROM: line varies, depending on the type of DVD drive that you
connect to the USB port.
Figure 27 BIOS Boot Override options

10. Press Enter to boot from the rekickstart image.

When the node boots, the SUSE Linux Enterprise Server 11 SP4 boot menu opens.

Avamar Data Store Gen4T Platform Rekickstart Procedures 33

Rekickstarting

Figure 28 SUSE Linux Enterprise Server 11 SP4 boot menu

11. Select SLES 11 SP4 <version> for ADS Gen4T (Serial Console) and then press Enter.
where <version> is the version number for the rekickstart image.
12. Select the correct profile for this node from the list and then press Enter.
Figure 29 SUSE Linux Enterprise Server 11 SP4 boot profiles

13. Observe the boot and rekickstart process for any errors. The rekickstart process produces
extensive onscreen output, but should not require intervention.
During the rekickstart process, the node reboots several times.

34 Avamar Data Store Gen4T Platform Rekickstart Procedures

 Rekickstarting

Figure 30 Rekickstart process

When you receive the node login: prompt, the rekickstart is complete.

Boot the node from a USB DVD drive (SLES12)

This task applies when kickstarting the node for SLES12SP4 and SLES12SP5, which have a
different sequence of menu prompts than SLES 11. The rekickstart proceeds automatically as the
node boots from the DVD drive. Observe the process and wait for the rekickstart to complete.
Procedure
1. Burn a copy of the ISO image to a DVD.
2. If the node is part of an operating Avamar server, use the Avamar Data Store Shutdown or
Reboot Procedure in SolVe Desktop to perform a graceful shutdown of the Avamar software
on the node.
Note: You do not need to shut down the entire Avamar server.

3. Connect a USB DVD drive to the USB port on the rear I/O panel.
4. Insert the DVD that contains the ISO image.
5. Establish a serial console connection to the node.
6. Press the power/reset button on the rear I/O panel.

Avamar Data Store Gen4T Platform Rekickstart Procedures 35

Rekickstarting

Figure 31 Power/reset button

1. Power/reset button

7. When you see the BIOS logo, press F2 or Del to enter the BIOS.
Figure 32 BIOS logo

8. Use the left and right arrow keys to move to Save & Exit.
Figure 33 Save & Exit menu

9. Use the up and down arrow keys to navigate to the Boot Override section and highlight
CDROM:.
The remaining text on the CDROM: line varies, depending on the type of DVD drive that you
connect to the USB port.

36 Avamar Data Store Gen4T Platform Rekickstart Procedures

 Rekickstarting

Figure 34 BIOS Boot Override options

10. Press Enter to boot from the rekickstart image.

Wait for the data loss warning to appear.
Figure 35 Data loss warning

11. Press 6 to acknowledge the data loss warning.

The platform selection menu appears. The platform selection menus for SLES12SP4 and
SLES12SP5 are very similar.

Avamar Data Store Gen4T Platform Rekickstart Procedures 37

Rekickstarting

Figure 36 Platform selection menu (SLES12SP4)

Figure 37 Platform selection menu (SLES12SP5)

12. Select ADS Gen4T (Serial Console), and then press Enter.
The node type selection menu appears. The node type selection menus for SLES12SP4 and
SLES12SP5 are identical.

38 Avamar Data Store Gen4T Platform Rekickstart Procedures

 Rekickstarting

Figure 38 Gen4T node type selection menu

13. Select the correct profile for this node from the list and then press Enter.
14. Observe the boot and rekickstart process for any errors. The rekickstart process produces
extensive onscreen output, but should not require intervention.
During the rekickstart process, the node reboots several times.
Figure 39 Rekickstart process

When you receive the node login: prompt, the rekickstart is complete.

Avamar Data Store Gen4T Platform Rekickstart Procedures 39

Rekickstarting

40 Avamar Data Store Gen4T Platform Rekickstart Procedures

CHAPTER 4
Post-requisites

This chapter contains the following topics:

l Check for successful completion (SLES11SP4)..................................................................... 42

l Check for successful completion (SLES12)........................................................................... 43
l Configure the power/reset button........................................................................................ 44
l Clear the RMC configuration.................................................................................................45
l Apply the new RMC configuration.........................................................................................45
l Record service tag information..............................................................................................47
l Register the product with the Install Base Group.................................................................. 48

Avamar Data Store Gen4T Platform Rekickstart Procedures 41

Post-requisites

Check for successful completion (SLES11SP4)

The rekickstart process produces artifacts that indicate successful completion. This task applies
when kickstarting the node for SLES11SP4.
About this task
CAUTION If any of the checks indicate a problem with the rekickstart process, do not continue
until the issues are resolved. Contact Customer Support for assistance.
Procedure
1. Log in as the root user.
At this stage, you are not required to log in as the admin user and use su.
2. Determine the current kickstart version tag by typing the following command:
ls /sles*

The console displays output similar to the following:

/sles11-SP4-64v01.02

Ensure that the kickstart version tag matches the version of the kickstart ISO image.
If the kickstart version tag is not present, then the rekickstart did not complete
successfully.
3. Verify that all of the rekickstart post scripts exist by typing the following commands:
cd /var/log/YaST2
grep -iE 'autoinstscript.*\.sh' * | grep -v "\.log"

The console displays output similar to the following:

y2log:2018-05-29 19:01:53 <1> linux(4426) [YCP] AutoinstScripts.ycp:749
Writing script into /var/adm/autoinstall/scripts/post_config.sh
y2log:2018-05-29 19:05:14 <1> node(4426) [YCP] AutoinstScripts.ycp:703
Writing init script into /var/adm/autoinstall/init.d/zzz-post_cleanup.sh
y2log:2018-05-29 19:05:14 <1> node(4426) [YCP] AutoinstScripts.ycp:703
Writing init script into /var/adm/autoinstall/init.d/reorder_nics.sh
y2log-1:2018-05-29 18:56:43 <1> linux(5224) [YCP] AutoinstScripts.ycp:728
Writing chroot script into /mnt/var/adm/autoinstall/scripts/
copy_from_ramdisk.sh
y2log-1:2018-05-29 18:57:18 <1> linux(5224) [YCP] AutoinstScripts.ycp:728
Writing chroot script into /var/adm/autoinstall/scripts/
configure_services.sh
y2log-1:2018-05-29 18:57:18 <1> linux(5224) [YCP] AutoinstScripts.ycp:728
Writing chroot script into /var/adm/autoinstall/scripts/
configure_serial_port.sh

Verify that there were no errors during the generation of the post scripts.
4. Verify that all the post scripts exist as expected by typing the following command:
ls -a /var/adm/autoinstall/scripts/*.sh

The console displays the following output:

/var/adm/autoinstall/scripts/configure_serial_port.sh
/var/adm/autoinstall/scripts/configure_services.sh
/var/adm/autoinstall/scripts/copy_from_ramdisk.sh
/var/adm/autoinstall/scripts/post_config.sh
/var/adm/autoinstall/scripts/reorder_nics.sh
/var/adm/autoinstall/scripts/zzz-post_cleanup.sh

42 Avamar Data Store Gen4T Platform Rekickstart Procedures

 Post-requisites

Ensure that all of these scripts are present. If any file is not present, then the rekickstart did
not complete successfully.
5. Check the contents of the Message of the Day file by typing the following command:
grep -i avamar /etc/motd

The console displays the following output:

* This is an Avamar Super Node *

If the file does not include this output, then the rekickstart did not complete successfully.

Check for successful completion (SLES12)

The rekickstart process produces artifacts that indicate successful completion. This task applies
when kickstarting the node for SLES12SP4 and SLES12SP5, which have a different series of
artifacts than SLES11.
About this task
CAUTION If any of the checks indicate a problem with the rekickstart process, do not continue
until the issues are resolved. Contact Customer Support for assistance.
Procedure
1. Log in as the root user.
At this stage, you are not required to log in as the admin user and use su.
2. Determine the current kickstart version by typing the following command:
cat /PlatformInfo

For SLES12SP4, output similar to the following appears:

KS_OS_NAME="SUSE Linux Enterprise Server"
KS_OS_VERSION="12"
KS_OS_PATCHLEVEL="4"
KS_VERSION="1.61"
KS_PRODUCT="DellEMC Avamar Server"
KS_MODEL="accelerator"
KS_PLATFORM="ADS4T"

For SLES12SP5, output similar to the following appears:

KS_OS_NAME="SUSE Linux Enterprise Server"
KS_OS_VERSION="12"
KS_OS_PATCHLEVEL="5"
KS_VERSION="8"
KS_PRODUCT="DellEMC Avamar Server"
KS_MODEL="M2400"
KS_PLATFORM="ADS4T"

Ensure that the kickstart version matches the version of the kickstart ISO image. If the
platform information file does not exist or does not match the kickstart ISO image, the
kickstart was unsuccessful.
3. Verify the existence of the kickstart post scripts by typing the following commands:
cd /var/log/YaST2
grep -iE 'autoinstscript.*\.sh' * | grep -v "\.log"

The following output appears:

y2log:2019-09-12 05:59:35 <1> node(2816) [Ruby] modules/
AutoinstScripts.rb:907 Writing script into /var/adm/autoinstall/scripts/
zzz-build_rpm_list.sh

Avamar Data Store Gen4T Platform Rekickstart Procedures 43

Post-requisites

Verify that errors did not occur during the generation of the post scripts.
4. Verify that all of the post scripts exist as expected by typing the following command:
ls -a /var/adm/autoinstall/scripts/*.sh

The following output appears:

/var/adm/autoinstall/scripts/info_<nodetype>.sh
/var/adm/autoinstall/scripts/zzz-build_rpm_list.sh
/var/adm/autoinstall/scripts/info_gen4t.sh

Verify that all of these scripts exist. If any of these scripts are missing, the kickstart was
unsuccessful.
5. Check the contents of the Message of the Day file by typing the following command:
grep -i avamar /etc/motd

The following output appears:

* This is an Avamar Super Node *

If the file does not include the output above, the kickstart was unsuccessful.

Configure the power/reset button

The power/reset button should only be used when referenced in a procedure or as directed by
Customer Support.
About this task
CAUTION
Using the power/reset button on the rear I/O panel to power off a node while the operating
system is active may result in loss of customer data. To prevent data loss, use the correct
procedure to stop the operating system and power off the node.
Using the power/reset button does not completely remove power from a node. The RMC and
related components are still active.
Procedure
1. Determine the current power/reset button settings by typing the following command:
ipmitool raw 0x30 0x83

The console displays output similar to the following:

01 02 04 03

Note and record these values.

2. Configure the power/reset button by typing the following command:
ipmitool raw 0x30 0x82 0x01 0x01 0x04 0x04

3. Confirm the change to the power/reset button settings by typing the following command:
ipmitool raw 0x30 0x83

The console displays output similar to the following:

01 01 04 04

Results
The power/reset button is now configured for the following behavior:

44 Avamar Data Store Gen4T Platform Rekickstart Procedures

 Post-requisites

Table 4 Power/reset button configuration

Input Action

Pressing the power button for less than 10 s The node resets

Pressing the power button for 10 s or more The node powers off

All actions occur when you release the power/reset button.

Clear the RMC configuration

This task applies when performing a rekickstart onsite using RMC, where the RMC ports were not
configured before the rekickstart (Scenario 1).
About this task
Because the RMC port was not configured before you performed the rekickstart, clear the
temporary configuration that you assigned at the beginning of this procedure.
Procedure
1. Clear the configuration from the shared RMC port by typing the following commands:
ipmitool lan set 1 ipaddr 0.0.0.0
ipmitool lan set 1 defgw ipaddr 0.0.0.0

2. Clear the configuration from the dedicated RMC port by typing the following commands:
ipmitool lan set 4 ipaddr 0.0.0.0
ipmitool lan set 4 defgw ipaddr 0.0.0.0

Apply the new RMC configuration

This task applies when performing a rekickstart onsite using RMC, where the customer intends to
change the RMC configuration after the rekickstart (Scenario 3).
About this task
After you perform the rekickstart, change the existing RMC configuration to the customer-
specified values.
Procedure
1. If the new RMC configuration is known, obtain the following information from the customer:
l Whether to use the eth0 (RMC shared) or the RMC dedicated port
l IP address for the RMC port
l Subnet mask for the RMC port
l Default gateway for the RMC port
If the new RMC configuration is not known, clear the existing configuration from both RMC
ports. Clear the RMC configuration on page 45 provides more information.

2. If the node is fresh from manufacturing or the node's RMC ports have never been used,
perform the following substeps:
a. Enable the RMC by typing the following command:
ipmitool raw 0x30 0xf8 0x01 0x01 0x01

Avamar Data Store Gen4T Platform Rekickstart Procedures 45

Post-requisites

This command enables the web interface, RMC, and virtual media, and is independent of
the choice of RMC port that you make later.

b. Verify that the RMC is enabled by typing the following command:

ipmitool raw 0x30 0xf9

If the RMC is enabled, the console displays the following output:

01 01 01
c. Enable access to the RMC ports by typing the following commands:
ipmitool lan set 1 access on
ipmitool lan set 4 access on

d. Enable ARP for the RMC ports by typing the following commands:
ipmitool lan set 1 arp respond on
ipmitool lan set 4 arp respond on

e. Configure the RMC ports for static addressing by typing the following commands:
ipmitool lan set 1 ipsrc static
ipmitool lan set 4 ipsrc static

3. Configure the RMC ports appropriately by typing the commands below, each on one line:
Note: If you are configuring the eth0 (RMC shared) port for use, clear the configuration
from the RMC dedicated port, and conversely. Clear any existing configuration from the
RMC port that is not in use.

To clear the configuration from an RMC port:

l ipmitool lan set <CHANNEL> ipaddr 0.0.0.0
l ipmitool lan set <CHANNEL> defgw ipaddr 0.0.0.0
where <CHANNEL> is 1 or 4, corresponding to the eth0 (RMC shared) and RMC dedicated
ports, respectively.

To configure an RMC port:

l ipmitool lan set <CHANNEL> ipaddr <IP ADDRESS>
l ipmitool lan set <CHANNEL> netmask <SUBNET MASK>
l ipmitool lan set <CHANNEL> defgw ipaddr <DEFAULT GATEWAY>
where:
l <CHANNEL> is 1 or 4, corresponding to the eth0 (RMC shared) and RMC dedicated
ports, respectively.
l <IP ADDRESS>, <SUBNET MASK>, and <DEFAULT GATEWAY> are the three values
that were obtained from the customer.

4. Set the password for the RMC root user by typing the following commands:
ipmitool user set name 2 root
ipmitool user set password 2 <PASSWORD>
where <PASSWORD> is the chosen password. The default password for the RMC ports is
calvin.

46 Avamar Data Store Gen4T Platform Rekickstart Procedures

 Post-requisites

5. If you cleared the configuration from both RMC ports, skip the remainder of this task. If you
assigned a new configuration to either RMC port, continue.
6. Configure the laptop with an IP address on the same subnet as the IP address that you
obtained from the customer, and then connect to the selected RMC port.
For example, if the new RMC port IP address is 10.100.200.1, use 10.100.200.2.
Connect the laptop to a Gen4T RMC port on page 13 provides more information.

7. In a web browser, type the following:

https://<AvamarRMC>
where <AvamarRMC> is the IP address that you assigned to the selected RMC port.
Acknowledge any browser warnings about self-signed certificates before you continue.

The ability to successfully log in to the RMC indicates that the new RMC configuration is
correct.

Record service tag information

Procedure
1. From the back of the cabinet, locate the service tag on the lower-right side of each node,
just below the power supplies.

Avamar Data Store Gen4T Platform Rekickstart Procedures 47

Post-requisites

Figure 40 Service tag location

2. Pull out the service tag, and then record the part number and serial number for each node.
Use this information to register the product with the Install Base Group.

Register the product with the Install Base Group

Notification of the Install Base Group is mandatory when you complete an installation or
implementation. Notification ensures that the CSI/Oracle database is up to date for each
customer.
If you need help to complete this follow-up task, call the Install Base Group telephone number at
1-508-249-9410. The call tracking system and Customer Support rely on this essential information.

48 Avamar Data Store Gen4T Platform Rekickstart Procedures

 Post-requisites

Note: The installation is incomplete until you complete this critical task that ensures timely,
proper, and professional service procedures and high customer satisfaction. Completing the
Install Base Group form is a mandatory requirement for closing this CSI Service Request.

Create a case using the Avamar Install Base audit form on the Business Services
portal
The Business Services portal provides a centralized location for service professionals to submit
requests directly to the Install Base Group. For ease of use, the portal is accessible outside the
corporate network and has an enhanced user interface for mobile devices.
Procedure
1. Browse to http://emc.force.com/BusinessServices.
The Business Services portal appears.
2. Browse to the Post Sales section, and then click Install Base Group.
The Install Base Group case creation page appears.
3. Choose a specific Case Sub Type from the drop-down list, and then click Select.

Option Description
IB Status Change Provide updated hardware or software status to the Oracle Install
Base. This type is the most common choice.
PDR Update Assign or update the Dispatch Resource for a TLA. This function
determines which field rep, group, or partner gets dispatched on a
service request.
Move or Party Move or update the customer party number that is associated to
Change hardware or software products in the Oracle Install Base.
Upgrade/Conversion Reflect in-family upgrade conversion in the Install Base, based on
the Sales Order Shipment.
Debrief Part usage on the different task types in Oracle.
Model Quantity Update service processors, microcodes, and remote connection in
Update the Install Base, to obtain secure credentials.
Other All other requests that do not fit into existing categories.
Model Separation Split multiple TLAs bundled under the same model into single/
stand-alone instances.
Microcode Update Update the microcode or OS to the desired version.

After you select a sub-type, the form populates with all relevant fields for the specific
service request.
4. Populate your contact name, email address, phone, and theatre.
Include the email addresses of any other users who you would like to copy on this request in
the Additional Notification Email fields. Required fields are marked in red.

5. In the Case Details section, populate the Subject and Description fields with details about
the type of support.
6. If this case is a Federal request, select the Federal Case checkbox.
If not, do not make a federal case out of it.

Avamar Data Store Gen4T Platform Rekickstart Procedures 49

Post-requisites

7. Select the corresponding Product Family that applies to the request.

8. Complete the additional fields that are relevant to the specific case sub-type.
l To submit multiple serial numbers, separate the values with a comma.
l To submit a large number of values, attach an Excel spreadsheet. A following step
provides additional information.
l Obtain the serial number from the Avamar UID. The UID is listed in the System ID field in
the output of mccli server show-prop. Remove the colons and the @ symbol.

9. If you selected the IB Status Change case sub-type, complete the Remote Connection
section with important ConnectEMC/dial-home information.
Note:
A dial-home contact is a person for Customer Support to contact when ConnectEMC
receives an alert and automatically generates a service request.
The form allows multiple alternate dial-home contacts. Customer Support contacts the
primary contact first and may contact alternate contacts in any order.

10. To include additional documents with the request, browse to the Upload Attachments
section and click Choose file.
Provide details on each file in the Description field for that file.
11. Attach an Excel spreadsheet that contains the individual node serial numbers, found on the
service tag for each node.
12. Provide all other relevant information and include any necessary attachments, and then click
Submit.
The Submit button resides above the file attachment area.

The Business Services portal sends the request to the Install Base Group for review and
sends automated email notifications to advise you about the progress of the request. Record
the case number.

50 Avamar Data Store Gen4T Platform Rekickstart Procedures