Metro node SolVe Generator

Version: 1.0.2.8 Generated on January 17 2025 04:00 PM

Topic
Metro node Installation Procedures

Selections
Select the Metro node OS version: 8.0 SP1
Install Procedures: Configuration and Installation Guide

If you find any errors in this procedure or have comments regarding this application, send
email to [email protected]

Copyright © 2024 Dell Inc. or its subsidiaries. All Rights Reserved. Dell Technologies, Dell, EMC, Dell EMC and other trademarks are
trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners.

The information in this publication is provided “as is.” Dell Inc. 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 software described in this publication requires an applicable software license.

This document may contain certain words that are not consistent with Dell's current language guidelines. Dell plans to update the
document over subsequent future releases to revise these words accordingly.

This document may contain language from third party content that is not under Dell's control and is not consistent with Dell's current
guidelines for Dell's own content. When such third party content is updated by the relevant third parties, this document will be revised
accordingly.
Dell Technologies – Restricted Use – Confidential & Subject to NDA

Page 1 of 120
 Contents
Preliminary Activity Tasks .......................................................................................................3
Read, understand, and perform these tasks.................................................................................................3

Dell Metro node 8.0 Service Pack 1 Configuration and Installation Guide..............................5

Dell Technologies – Restricted Use – Confidential & Subject to NDA

Page 2 of 120
Preliminary Activity Tasks
This section may contain tasks that you must complete before performing this procedure.

Read, understand, and perform these tasks

1. Table 1 lists tasks, cautions, warnings, notes, and/or knowledgebase (KB) solutions that you need to
be aware of before performing this activity. Read, understand, and when necessary perform any
tasks contained in this table and any tasks contained in any associated knowledgebase solution.

Table 1 List of cautions, warnings, notes, and/or KB solutions related to this activity

Dell Technologies – Restricted Use – Confidential & Subject to NDA

Page 3 of 120
Dell Technologies – Restricted Use – Confidential & Subject to NDA

Page 4 of 120
Dell Metro node 8.0 Service Pack 1 Configuration and Installation
Guide

Dell Technologies – Restricted Use – Confidential & Subject to NDA

Page 5 of 120
Dell Metro node 8.0 Service Pack 1
Configuration and Installation Guide
8.0.1

January 2025
Rev. A01

Page 6 of 120
Notes, cautions, and warnings

NOTE: A NOTE indicates important information that helps you make better use of your product.

CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid
the problem.

WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

© 2025 Dell Inc. or its subsidiaries. All rights reserved. Dell Technologies, Dell, and other trademarks are trademarks of Dell Inc. or its
subsidiaries. Other trademarks may be trademarks of their respective owners.

Page 7 of 120
 Contents

Chapter 1: Overview...................................................................................................................... 5
High-Level Overview.......................................................................................................................................................... 5
Ports and Connections.......................................................................................................................................................6
mn-114...............................................................................................................................................................................6
mn-215.............................................................................................................................................................................. 7

Chapter 2: Installation requirements............................................................................................. 9

Volume pre-requisites.........................................................................................................................................................9
User input details for system configuration.................................................................................................................. 9
Connect to the node......................................................................................................................................................... 10
Connect through SVC port........................................................................................................................................10
Connect through iDRAC Direct Micro-USB port..................................................................................................12

Chapter 3: Procedure...................................................................................................................14
Precautions..........................................................................................................................................................................14
Help Command................................................................................................................................................................... 14
Task 1: Pre-configuration................................................................................................................................................. 15
Accept EULA................................................................................................................................................................. 15
Pre-configuration Phases...........................................................................................................................................15
Task 2: Interview (phase 1)............................................................................................................................................. 16
Task 3: Apply changes (phase 1)................................................................................................................................... 20
Task 4: Backend path zoning configuration................................................................................................................22
Task 5: Interview (phase 2)............................................................................................................................................24
IP WAN(configuration for mn114)............................................................................................................................24
IP WAN(configuration for mn215)...........................................................................................................................29
FC WAN(configuration for mn215)......................................................................................................................... 33
Task 6: Apply Changes (phase 2)..................................................................................................................................38
Task 7: Create Metavolume Backup.............................................................................................................................39
Cluster Witness.............................................................................................................................................................41
WAN configuration details.............................................................................................................................................. 42
IP WAN Configuration details (for mn-114)...........................................................................................................42
IP WAN for mn215.......................................................................................................................................................48
Configuring SupportAssist.............................................................................................................................................. 55
Pre-requisite: Collect the SupportAssist configuration details........................................................................ 55
Step 1: Interview (SupportAssist configuration)................................................................................................. 55
Step 2: Apply changes to SupportAssist configuration..................................................................................... 55
More SupportAssist Commands.............................................................................................................................. 57
Configure the SMTP...................................................................................................................................................59

Chapter 4: Reconfigure Specific Parameters............................................................................... 63

Introduction........................................................................................................................................................................ 63
Help Command...................................................................................................................................................................63
Change the NTP server IP.............................................................................................................................................. 65
Change the WAN COM................................................................................................................................................... 66

Contents 3

Page 8 of 120
 Topology change (Applicable only for mn-215).................................................................................................... 71
Remove WAN COM.....................................................................................................................................................77
Change the Public IP/EC-01 Address of the director.............................................................................................. 78
Change the name of the cluster.................................................................................................................................... 79
View the SCIF content.....................................................................................................................................................80
Change the login banner..................................................................................................................................................82
Retrieve the iDRAC password ...................................................................................................................................... 83
Change the service user password...............................................................................................................................84
Change the SSL certificates for self_signed............................................................................................................. 85
Change the SSL certificate for cust_signed.............................................................................................................. 86
Reset SSL Certificates.....................................................................................................................................................88
Renew self-signed SSL certificates..............................................................................................................................88
Enabling and disabling of metro node ports............................................................................................................... 89
Help command for Port-toggle................................................................................................................................ 89
Enable port for one director..................................................................................................................................... 90
Disable port for one director.................................................................................................................................... 90
Enable port for one cluster....................................................................................................................................... 90
Disable port for one cluster....................................................................................................................................... 91
Enable port for all directors....................................................................................................................................... 91
Disable port for all directors..................................................................................................................................... 92
Exclude one or more directors................................................................................................................................. 92
Configure or change the LDAP or AD.......................................................................................................................... 92
Configure the LDAP....................................................................................................................................................93
Show the LDAP configuration..................................................................................................................................94
Add users.......................................................................................................................................................................95
Remove users...............................................................................................................................................................96
Add groups.................................................................................................................................................................... 97
Remove groups............................................................................................................................................................ 97
Reset the LDAP configuration................................................................................................................................. 98
Update the LDAP/AD certificates.......................................................................................................................... 99
Configure or change SSH Keys....................................................................................................................................102

Chapter 5: Logs......................................................................................................................... 104

SCIF File and Logs...........................................................................................................................................................104

Chapter 6: DNS configuration.................................................................................................... 105

Interview phase................................................................................................................................................................105

Chapter 7: Post Upgrade............................................................................................................108

Process Overview for Updating GAM........................................................................................................................ 108
Get DST and GUID using UI method...........................................................................................................................108
Get DST and GUID using CLI method........................................................................................................................ 109
Submitting a Case to GAM Team................................................................................................................................. 110
Index.......................................................................................................................................... 114

4 Contents

Page 9 of 120
 1
Overview
Step-by-step guide to install a metro node.
Topics:
• High-Level Overview
• Ports and Connections

High-Level Overview
This segment covers the high-level overview of the implementation steps.
1. Hardware installation-See the Dell Metro Node Hardware Installation Guide.
2. Connect all the ports with the cables.

NOTE: If all the ports are not connected properly, then the interview process fails.

3. Pre-configuration phase:
a. To set the public IP for all the nodes of the metro node, log in to each node.
Command: vplex_system_config --interview
4. Interview (phase 1)-Run on any of the nodes, it collects the cluster details and NTP information.
Command: vplex_system_config --interview
5. Apply changes (phase 1)-It commits the configuration to all the nodes of the metro node.
Command: vplex_system_config --start
6. Back-end zoning and volumes- Zone the backend ports to the storage arrays and present the system volumes.
7. Interview (phase 2)- Collects metavolume candidates, logging volume candidates, and creates them. Also, collect the
WAN-COM information for metro cluster configuration.
Command: vplex_system_config --interview
8. Apply Changes (phase 2)- Once the metavolume and logging volume are created, then configure all the nodes of the
metro node, and perform the WAN-COM configuration.
Command: vplex_system_config --complete
9. Meta-data backup-Configure the backup of the metadata volumes.
Command: vplex_system_config --metadata-backup-create
10. iDRAC phase- Runs the ansible-playbook to configure the iDRAC parameters on all the nodes of the metro node.
Command: vplex_system_config --idrac
11. Post-configuration phase: Post metro node configuration, Dell Employees, and Partners must update the Global Asset
Management (GAM) with the generated Cluster Serial Number (GUID) by following the procedure in the post-deployment
steps.
12. Configuring Support Assist: Configures CallHome alerts to be send to the backend.

Overview 5

Page 10 of 120
Ports and Connections
The following figure describes hardware ports available in the system for mn-114 and mn-215.

mn-114

Figure 1. mn-114

Figure 2. Logical View

Table 1. Ports and Descriptions

Ports Description
CUST The External Public port that is connected to the network of
the customer (EC-01)
I/O-00, I/O-01 Front-End FC Ports/I/O Ports
I/O-02, I/O-03 Back-End FC Ports/I/O Ports
LCOM1 Internal Local Communication Port connected between nodes
of Local cluster (LC-00)
LCOM2 Internal Local Communication Port connected between nodes
of Local cluster (LC-01)
MGMT1 Internal Management Port connected between two nodes of
the same cluster (MC-00)

6 Overview

Page 11 of 120
Table 1. Ports and Descriptions (continued)
Ports Description
MGMT2 Internal Management Port connected between two nodes of
the same cluster (MC-01)
Power Supply Unit (PDU1) Power Port 1
Power Supply Unit (PDU2) Power Port 2
SVC The service terminal where service laptop must be connected
over Ethernet port (EC-00).
WCOM1 WAN communication port for intercluster connectivity
between directors (WC-00).
WCOM2 WAN communication port for intercluster connectivity
between directors (WC-01).

mn-215

Figure 3. mn-215

Figure 4. Logical View

Table 2. Ports and Descriptions

Ports Description
CUST The External Public port that is connected to the network of
the customer (EC-01).

Overview 7

Page 12 of 120
Table 2. Ports and Descriptions (continued)
Ports Description
EC-01 Customer/Public Port
I/O-00, I/O-01 I/O-02,I/O-03 Front-End FC Ports/I/O Ports
I/O-04, I/O-05 I/O-06,I/O-07 Back-End FC Ports/I/O Ports
LCOM1 Internal Local Communication Port connected between nodes
of Local cluster (LC-00)
LCOM2 Internal Local Communication Port connected between nodes
of Local cluster (LC-01)
MGMT1 Internal Management Port connected between two nodes of
the same cluster (MC-00)
MGMT2 Internal Management Port connected between two nodes of
the same cluster (MC-01)
Power Distribution Units (PDU1) Power Port 1
Power Distribution Units (PDU2) Power Port 2
SVC The service terminal where service laptop must be connected
over Ethernet port (EC-00).
WCOM-IP-1 WAN communication port for inter-cluster connectivity
between directors (WC-IP-00)
WCOM-IP-2 WAN communication port for inter-cluster connectivity
between directors (WC-IP-01)
WCOM-FC-1 WAN communication port for inter-cluster connectivity
between directors (WC-FC-00)
WCOM-FC-2 WAN communication port for inter-cluster connectivity
between directors (WC-FC-01)

8 Overview

Page 13 of 120
 2
Installation requirements
Before installing the metro node, see the following requirements:

NOTE: See Dell Metro Node Security Configuration Guide, for Password Policy section.

Topics:
• Volume pre-requisites
• User input details for system configuration
• Connect to the node

Volume pre-requisites
See the following pre-requisites:
1. Meta-volume candidates: Export four storage-volumes of size >= 80 GB from two different storage arrays.
2. Logging volume candidates: Export four storage volumes of at least 10 GB each from two different storage arrays. The
upper limit for the logging volume has been removed, allowing for greater capacity with no upper limit.

User input details for system configuration

The system configuration requires the following information for all nodes:
NOTE: For the User input details table, Director-2-1-A and Director-2-1-B are not applicable for local cluster setup.

Table 3. User inputs details

User input details for system Director-1-1-A/Director-1-1-B / Comments
configuration Director-2-1-A /Director-2-1-B
IP Address Y EC-01 (CUST) port IP address is set for
each node.
Netmask Y EC-01 (CUST) port Netmask is set for
each node.
Gateway Y EC-01 (CUST) port Gateway is set for
each node.
MTU (default: 1500) Y EC-01 (CUST) port MTU for each node.
Service user password Y A new password is set for each node.
NOTE:
● Director-1-1-A and Director-1-1-
B should have the same
password.
● Director-2-1-A and Director-2-1-
B should have the same
password.

NTP server1 address - NTP server1 address is common for all

the nodes.
NTP server2 address - NTP server2 address is common for all
the nodes.

Installation requirements 9

Page 14 of 120
Table 3. User inputs details (continued)
User input details for system Director-1-1-A/Director-1-1-B / Comments
configuration Director-2-1-A /Director-2-1-B
Primary DNS address - Common for all the nodes.
Secondary DNS address - Common for all the nodes.

Connect to the node

There are two ways to connect to the node from the service laptop:
1. Connect through SVC port (only for mn114).
2. Connect through iDRAC Direct Micro-USB port.

Connect through SVC port

Steps
1. If the cabinet has a laptop tray, then this step is applicable. Follow these steps:
● At the front of the cabinet, remove the filler panel at the U23 position (38.5 inches up from the floor of the cabinet).
● Slide the laptop tray out and place the laptop on the tray.
● To loosen the cable tie, press the tab that secures the red service cable to the tray.
● Connect the service cable to the Ethernet port on the laptop.
● Connect the other end to the SVC port of the node.
2. Open a web browser on the laptop, and go to "http://128.221.252.2." Follow the instructions mentioned on the web page,
and then go to step 3.
NOTE: If you do not see the web page, then verify that the Dynamic Host Configuration Protocol (DHCP) is enabled on
the laptop.

3. On the laptop, launch PuTTY.exe.

NOTE: Several tasks in this document use PuTTY for logging in to the management server. You can use any similar
Telnet/SSH client. Ensure that you use the SSH protocol, version 2, with any client. If you see a PuTTY security alert,
then read it, and then click Yes.

4. Configure the PuTTY Configuration window as shown in the following figure:

10 Installation requirements

Page 15 of 120
 Figure 5. PuTTY configuration

5. From the Category list, select SSH and ensure that the Preferred SSH protocol version is set to 2.

Figure 6. PuTTY configuration-SSH

6. From the Category list, select Session. Click Save in the PuTTY Configuration window to save the settings for the session.
7. In the PuTTY Configuration window, click Open to establish a connection to the node, and log in with username as Service
and service password (for service password, ask from the system administrator).
NOTE: The default shell prompt for username service is service@localhost:~>.

8. Go to the Procedure section.

Installation requirements 11

Page 16 of 120
Connect through iDRAC Direct Micro-USB port
iDRAC Direct USB-NIC feature allows direct access to the iDRAC web-interface without requiring the connectivity by using the
iDRAC Network Systems Management port.

About this task

WARNING: Do not change the IDRAC default credentials. By default, the iDRAC GUI suggests changing
credentials. Select the "No" option to ignore changing the iDRAC credentials.

Steps
1. Take a Micro-USB 2.0 cable and connect the connector end of the cable to the iDRAC Direct Micro-USB port on the System
Front Panel. And, connect the other end of the cable to the USB port of the service laptop.

Figure 7. Micro-USB 2.0

Figure 8. System front panel view without bezel

2. Launch any browser, and then type "https://169.254.0.3 " in the address bar.
3. Skip the certificate error and select Continue to this website.
4. Enter the iDRAC credentials.

Figure 9. iDRAC home page

12 Installation requirements

Page 17 of 120
5. Open the virtual console, and then click Launch Virtual Console.

Figure 10. Virtual Console

6. Log in with the service credentials and go to the Procedure section.

Installation requirements 13

Page 18 of 120
 3
Procedure
Topics:
• Precautions
• Help Command
• Task 1: Pre-configuration
• Task 2: Interview (phase 1)
• Task 3: Apply changes (phase 1)
• Task 4: Backend path zoning configuration
• Task 5: Interview (phase 2)
• Task 6: Apply Changes (phase 2)
• Task 7: Create Metavolume Backup
• WAN configuration details
• Configuring SupportAssist

Precautions
Any forced termination of the system-configuration process may result in the retention of a stale SCIF lock file on the system.
This lock file prevents any additional system-configuration operations. To handle this situation, see the Troubleshooting guide for
metro node. To prevent leaving a stale SCIF lock file on the system, the system:
● Do not reboot any node while a system-configuration operation is in progress.
● Do not kill a system-config process (for example, kill -9 <pid_of_vplex_system_config>).
● Do not press Ctrl + z, when system config operation is in progress.
● To connect to the system, enable SSH keepalive heartbeats in the SSH client.
● Avoid circumstance that may cause a disruption in the network connectivity to the metro node while system-configuration
operations are in progress, such as unreliable WiFi.

Help Command
To see the system configuration command, run the vplex_system_config --help command in any node. Also,
vplex_system_config -i --help. can be used to view the list of commands.

service@director-1-1-a:~> vplex_system_config --help

usage: vplex_system_config [-s|--start] | [-c|--complete] | [-r|--reset] | [--idrac] |
[--reset-idrac] | [--support-enable] | [--support-disable] | [--reset-supportassist] [-
h|--help]
-----------------------------------------------------------------------------------------
-
-h | --help - Show the help for the command.
-s | --start - Command starts executing the initial phase of system-config.
-i | --interview - Command starts executing the interview script of system-
config.
-c | --complete - Command starts executing the second phase of system-config.
-r | --reset - Command starts executing the reset of system-config changes.
--reset-ntp - Command starts executing reset of ntp configuration.
--idrac - Command starts executing configuration of idrac.
--reset-idrac - Command starts executing reset of idrac configuration.
--wancom - Command starts executing wancom configuration.
--reset-wancom - Command starts executing reset of wancom configuration.
--support-assist - Command starts configuration process for SupportAssist
--support-enable - Command starts executing to enable SupportAssist service.
--support-disable - Command starts executing to disable SupportAssist service.
--reset-supportassist - Command starts executing reset of SupportAssist.

14 Procedure

Page 19 of 120
 --reset-smtp - Command starts executing reset of smtp configuration.
--smtp-config - Command starts executing smtp configuration.
--port-toggle - Command starts toggling port on given director.
--banner - Command starts executing banner configuration.
--reset-banner - Command starts executing reset of banner configuration.
--reset-dns - Command starts executing reset of DNS configuration.
--update-ssl-certificates - Command starts executing update of SSL certificates.
--reset-ssl-certificates - Command starts executing reset of SSL certificates.
--cw-show - Command starts executing to show CW details
--cw-configure - Command starts executing CW configuration.
--cw-reset - Command starts executing reset of CW configuration.
--cw-enable - Command starts executing to enable CW.
--cw-disable - Command starts executing to disable CW.
--update-passwordpolicy - Command starts executing to update password policy.
--update-sshkey - Command starts executing to update ssh key.
--metadata-backup-create - Command starts executing to create meta data backup.
service@director-1-1-a:~>

Task 1: Pre-configuration
NOTE:
1. This phase sets IP address of EC-01 port and changes the default password of service user for each node.
2. This step must be performed for each node.

Accept EULA
NOTE: To perform the system configuration, the user has to accept the EULA during pre-configuration displayed in all the
nodes.

service@localhost:~> vplex_system_config --interview

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.
Congratulations on your new Dell purchase!

<metro node EULA will be displayed>

Pre-configuration Phases
Perform the below steps on each node:
1. Run the pre-configuration interview phase using the command vplex_system_config --interview or
vplex_system_config -i.

service@director-1-1-b:~> vplex_system_config --interview

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.

Pre-config phase interview process is started...

Creating System Configuration Inventory File at /etc/opt/dell/vplex/scif.yml

VPLEX system details

Enter director's EC01 port details:
IP Address : 10.x.x.x
IP Address is validating, please wait...
Director is already configured with same IP address "10.x.x.x"
Netmask : 255.x.x.x
Gateway : 10.x.x.x
MTU (default: 1500):
Enter the service user password:
Current password :

Procedure 15

Page 20 of 120
 New password :
Retype new password :

Password has been changed successfully for the 'service' user

################### To receive the highest level of support, inform Dell support if

there is a change in the service password ###################

################### The service user's password must be the same on all nodes in a
cluster ###################

Please review the EC01 port details entered.

clusters:
nodes:
8K5ZY23
interfaces:
EC-01
ip:
address: 10.x.x.x
netmask: 255.x.x.x
gateway: 10.x.x.x
mtu: 1500

Please review the above details. Do you want to proceed(y/n)? (default: y):

IP configuration is successful on this 8K5ZY23

2. Run the command that is mentioned above on all the remaining nodes to complete the pre-configuration of the metro node.

Task 2: Interview (phase 1)

NOTE: Once the pre-configuration phase completes successfully on all the nodes, you can perform the System
Configuration commands from any node. For future, ensure to perform all the system configuration commands on the
same node. For examples, Director-1-1-B is used to perform all the rest of system configuration commands.

Director-1-1-B
1. To log in to Director-1-1-B as a service user.
2. Run the command vplex_system_config --interview or vplex_system_config --i and answer the interview questions.

service@localhost:~> vplex_system_config -i
Do you want to re-run the pre-config phase(y/n)?
Press "y" to re-run or press "enter" to proceed with phase-1 interview. (default: n):

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.

Phase-1 interview process is started...

Using system configuration file at /etc/opt/dell/vplex/scif.yml

VPLEX system details

Choose VPlex configuration.
1. Local
2. Metro
Please select configuration (default: local): 2
Enter 'cluster-1' details:
Service user password :
Re-enter service user password :
Enter 'cluster-1' node details:
Enter 'cluster-1' director details:
Enter 'director-1-1-a' details:
IP address : 10.x.x.x
Enter 'director-1-1-b' details:
IP address : 10.x.x.x

16 Procedure

Page 21 of 120
 Enter 'cluster-2' details:
Service user password :
Re-enter service user password :
Enter 'cluster-2' node details:
Enter 'cluster-1' director details:
Enter 'director-2-1-a' details:
IP address : 10.x.x.x
Enter 'director-2-1-b' details:
IP address : 10.x.x.x

Clearing existing files on node(director-1-1-a), with 10.x.x.x

Clearing existing files on node(director-1-1-b), with 10.x.x.x
Clearing existing files on node(director-2-1-a), with 10.x.x.x
Clearing existing files on node(director-2-1-b), with 10.x.x.x
Generating SSH key on node(director-1-1-a), with 10.x.x.x
Generating SSH key on node(director-1-1-b), with 10.x.x.x
Generating SSH key on node(director-2-1-a), with 10.x.x.x
Generating SSH key on node(director-2-1-b), with 10.x.x.x
Exchanging the key with other nodes from node(director-1-1-a), with
10.x.x.x
Exchanging the key with other nodes from node(director-1-1-b), with
10.x.x.x
Exchanging the key with other nodes from node(director-2-1-a), with
10.x.x.x
Exchanging the key with other nodes from node(director-2-1-b), with
10.x.x.x
Enabled passwordless SSH successfully between the nodes.

Enter NTP server 1 address (default: 127.0.0.1):

Enter NTP server 2 address (default: ):

Connecting to 10.x.x.x to fetch gateway and netmask details...

gateway and netmask have been fetched successfully for the node 10.x.x.x

Connecting to 10.x.x.x to fetch gateway and netmask details...

gateway and netmask have been fetched successfully for the node 10.x.x.x

Connecting to 10.x.x.x to fetch gateway and netmask details...

gateway and netmask have been fetched successfully for the node 10.x.x.x

Connecting to 10.x.x.x to fetch gateway and netmask details...

gateway and netmask have been fetched successfully for the node 10.x.x.x

Connecting to 10.x.x.x to fetch the hardware description file (hal.yml)

Connecting to 10.x.x.x to fetch the hardware description file (hal.yml)

Connecting to 10.x.x.x to fetch the hardware description file (hal.yml)

Connecting to 10.x.x.x to fetch the hardware description file (hal.yml)

Dell service tag and WWN Seed has been read sucessfully for the node 10.x.x.x

Dell service tag and WWN Seed has been read sucessfully for the node 10.x.x.x

GUID has been read successfully for cluster-1

Dell service tag and WWN Seed has been read sucessfully for the node 10.x.x.x

Dell service tag and WWN Seed has been read sucessfully for the node 10.x.x.x

Procedure 17

Page 22 of 120
 GUID has been read successfully for cluster-2

Please review the details entered.

ntp_server_1: 127.0.0.1
ntp_server_2:
snmp:
clusters
name: cluster-1
director_count: 2
instance: 1
id: 1
guid: 43A52L9
ldap:
call_home:
nodes
8K16Z23
name: Director-1-1-A
wwn_seed: 2D60002E
interfaces:
EC-01
role: cust
ip:
address: 10.x.x.x
netmask: 255.x.x.x
gateway: 10.x.x.x
mtu: 1500
LC-00
role: com
ip:
address: 128.x.x.x
netmask: 255.x.x.x
gateway:
mtu: 1500
LC-01
role: com
ip:
address: 128.x.x.x
netmask: 255.x.x.x
gateway:
mtu: 1500
MC-00
role: man
ip:
address: 128.x.x.x
netmask: 255.x.x.x
gateway:
mtu: 1500
MC-01
role: man
ip:
address: 128.x.x.x
netmask: 255.x.x.x
gateway:
mtu: 1500
8K14Z23
name: director-1-1-B
wwn_seed: 2D60002F
interfaces:
EC-01
role: cust
ip:
address: 10.x.x.x
netmask: 255.x.x.x
gateway: 10.x.x.x
mtu: 1500
LC-00
role: com
ip:
address: 128.x.x.x
netmask: 255.x.x.x

18 Procedure

Page 23 of 120
 gateway:
mtu: 1500
LC-01
role: com
ip:
address: 128.x.x.x
netmask: 255.x.x.x
gateway:
mtu: 1500
MC-00
role: man
ip:
address: 128.x.x.x
netmask: 255.x.x.x
gateway:
mtu: 1500
MC-01
role: man
ip:
address: 128.x.x.x
netmask: 255.x.x.x
gateway:
mtu: 1500
name: cluster-2
director_count: 2
instance: 1
id: 2
guid: 4xxxxx3
ldap:
call_home:
nodes
8K17Z23
name: director-2-1-A
wwn_seed: 2D600030
interfaces:
EC-01
role: cust
ip:
address: 10.x.x.x
netmask: 255.x.x.x
gateway: 10.x.x.x
mtu: 1500
LC-00
role: com
ip:
address: 128.x.x.x
netmask: 255.x.x.x
gateway:
mtu: 1500
LC-01
role: com
ip:
address: 128.x.x.x
netmask: 255.x.x.x
gateway:
mtu: 1500
MC-00
role: man
ip:
address: 128.x.x.x
netmask: 255.x.x.x
gateway:
mtu: 1500
MC-01
role: man
ip:
address: 128.x.x.x
netmask: 255.x.x.x
gateway:
mtu: 1500
8K11Z23
name: director-2-1-B
wwn_seed: 2D600031

Procedure 19

Page 24 of 120
 interfaces:
EC-01
role: cust
ip:
address: 10.x.x.x
netmask: 255.x.x.x
gateway: 10.x.x.x
mtu: 1500
LC-00
role: com
ip:
address: 128.x.x.x
netmask: 255.x.x.x
gateway:
mtu: 1500
LC-01
role: com
ip:
address: 128.x.x.x
netmask: 255.x.x.x
gateway:
mtu: 1500
MC-00
role: man
ip:
address: 128.x.x.x
netmask: 255.x.x.x
gateway:
mtu: 1500
MC-01
role: man
ip:
address: 128.x.x.x
netmask: 255.x.x.x
gateway:
mtu: 1500

Please review the above details.

Do you want to proceed(y/n)? (default: y):

SCIF has been copied to ['10.x.x.x', '10.x.x.x', '10.x.x.x', '10.x.x.x'] successfully.

Phase-1 interview process is completed.

To start the phase-1 configuration, run the command "vplex_system_config -s".

service@localhost:~>

3. Once the interview process completes successfully, then go to the next task.

Task 3: Apply changes (phase 1)

Director-1-1-B
NOTE: Ensure that you connect the backend cables to SAN. If the ports show no-link, then script fails at the time of
verification of BE port status.
1. To start the Phase 1 of the system_config process, run the command vplex_system_config -s.
The following output is displayed in two parts: Starting part and the ending part of the command:

service@localhost:~> vplex_system_config -s
Starting the system configuration process for phase 1...
TASK: Gathering Facts - PASS
TASK: Get multi-user.target service Status - PASS
TASK: Getting the vplex node version - PASS
TASK: Format version output and IPs - PASS
.

20 Procedure

Page 25 of 120
 .
.
TASK: Creating rest urls for BE ports - PASS
TASK: Getting BE ports - PASS
TASK: Storing BE ports values - PASS
TASK: Show wwn details - PASS
TASK: Getting the local_com health - PASS

PLAY RECAP
**************************************************************************************
************************************************************
director-1-1-A|8K63Z23 : ok=128 changed=41 unreachable=0 failed=0
skipped=140 rescued=0 ignored=0
director-1-1-B|8K64Z23 : ok=104 changed=39 unreachable=0 failed=0
skipped=159 rescued=0 ignored=0
director-2-1-A|8K65Z23 : ok=105 changed=39 unreachable=0 failed=0
skipped=158 rescued=0 ignored=0
director-2-1-B|8K66Z23 : ok=104 changed=39 unreachable=0 failed=0
skipped=159 rescued=0 ignored=0

System configuration process for phase 1 is successful

service@localhost:~>

Apply iDRAC
NOTE: The iDRAC passwords are set using metro node, and they meet the Dell security requirements. Connecting the
iDRAC port to the customer network is not supported. The iDRAC must be accessed only using Customer Support over
Metro node.

WARNING: vplex_system_config --idrac auto-generates the iDRAC passwords. Manually updating the
iDRAC password is not supported and is dangerous/fatal.
1. To start the iDRAC tasks, run the command vplex_system_config --idrac.
The following output is displayed in two parts: Starting part and the ending part of the command:

service@localhost:~> vplex_system_config --idrac

Starting the system configuration process for idrac tasks...
TASK: Gathering Facts - PASS
TASK: Generate random password - PASS
.
.
.
TASK: Get iDRAC password - PASS
TASK: Setting hostname in iDRAC - PASS

PLAY RECAP
**************************************************************************************
************************************************************
director-1-1-A|8K63Z23 : ok=23 changed=7 unreachable=0 failed=0
skipped=5 rescued=0 ignored=0
director-1-1-B|8K64Z23 : ok=22 changed=7 unreachable=0 failed=0
skipped=5 rescued=0 ignored=0
director-2-1-A|8K65Z23 : ok=23 changed=8 unreachable=0 failed=0
skipped=4 rescued=0 ignored=0
director-2-1-B|8K66Z23 : ok=23 changed=8 unreachable=0 failed=0
skipped=4 rescued=0 ignored=0

System configuration process for idrac configuration is successful

service@localhost:~>

2. Once the earlier command is successful, then go to the next task.

Procedure 21

Page 26 of 120
Task 4: Backend path zoning configuration
Director-1-1-B
1. Log in to VPlexcli, and run the below command to list the director ports:

NOTE: The same command is applicable for both mn-114 and mn-215 for getting the list of director ports.

The example that is shown here is from mn-215.

service@localhost:~> vplexcli
System config has not been completed. Please complete the initial system
configuration process.
If you need to access the vplexcli anyways, enter 'DANGER' and press Enter >
DANGER
Trying ::1...
Connected to localhost.
Escape character is '^]'.

VPlexcli:/>

VPlexcli:/> ll clusters/*/directors/*/ports

/clusters/cluster-1/directors/director-1-1-A/ports:
Name Address Role Status RxPower[uW] TxPower[uW] Temp[C]
Speed Topology
----- ------------------ ---------- ------ ----------- ----------- -------
--------- --------
EC-01 10.226.93.59 public up - - -
1Gbits/s -
IO-00 0xc001446600221800 front-end up 715 870 51
32Gbits/s p2p
IO-01 0xc001446600221900 front-end up 833 820 51
32Gbits/s p2p
IO-02 0xc001446600222000 front-end up 783 874 47
32Gbits/s p2p
IO-03 0xc001446600222100 front-end up 904 921 48
32Gbits/s p2p
IO-04 0xc001446600223000 back-end up 754 846 57
32Gbits/s p2p
IO-05 0xc001446600223100 back-end up 833 947 55
32Gbits/s p2p
IO-06 0xc001446600223800 back-end up 924 891 56
32Gbits/s p2p
IO-07 0xc001446600223900 back-end up 911 960 58
32Gbits/s p2p
LC-00 128.221.250.35 local-com up - - -
20Gbits/s -
LC-01 128.221.251.35 local-com up - - -
20Gbits/s -
MC-00 128.221.252.35 management up - - -
1Gbits/s -
MC-01 128.221.253.35 management up - - -
1Gbits/s -

/clusters/cluster-1/directors/director-1-1-B/ports:
Name Address Role Status RxPower[uW] TxPower[uW] Temp[C]
Speed Topology
----- ------------------ ---------- ------ ----------- ----------- -------
--------- --------
EC-01 10.226.93.60 public up - - -
1Gbits/s -
IO-00 0xc001446600231800 front-end up 833 994 41
32Gbits/s p2p
IO-01 0xc001446600231900 front-end up 1006 871 41
32Gbits/s p2p
IO-02 0xc001446600232000 front-end up 797 818 39

22 Procedure

Page 27 of 120
 32Gbits/s p2p
IO-03 0xc001446600232100 front-end up 878 739 38
32Gbits/s p2p
IO-04 0xc001446600233000 back-end up 742 1065 42
32Gbits/s p2p
IO-05 0xc001446600233100 back-end up 519 923 41
32Gbits/s p2p
IO-06 0xc001446600233800 back-end up 755 852 44
32Gbits/s p2p
IO-07 0xc001446600233900 back-end up 1047 806 44
32Gbits/s p2p
LC-00 128.221.250.36 local-com up - - -
20Gbits/s -
LC-01 128.221.251.36 local-com up - - -
20Gbits/s -
MC-00 128.221.252.36 management up - - -
1Gbits/s -
MC-01 128.221.253.36 management up - - -
1Gbits/s -

2. Note the node WWNs of backend ports from the output:

● Sample WWNs for director-1-1-A: 0xc001446600223000, 0xc001446600223100, 0xc001446600223800,
0xc001446600223900
● Sample WWNs for director-1-1-B: 0xc001446600233000, 0xc001446600233100, 0xc001446600233800,
0xc001446600233900
3. Complete the backend arrays zoning to the nodes with WWN mentioned in the Step 2.
4. Log in to VPlexcli, and run ll /clusters/**/storage-arrays/ command to list the storage arrays to confirm the
zoning is proper

ervice@localhost:/opt/dell/vplex/bin/system_config>vplexcli
Trying ::1...
Connected to localhost.
Escape character is '^]'.

VPlexcli:/>

VPlexcli:/> ll /clusters/**/storage-arrays/

/clusters/cluster-1/storage-elements/storage-arrays:
Name Connectivity Auto Ports Logical
--------------------------- Status Switch ------------------- Unit
--------------------------- ------------ ------ ------------------- Count
--------------------------- ------------ ------ ------------------- -------
DellEMC-PowerStore-2R10643 ok - 0x58ccf0904a620539, 130
0x58ccf0984a620539
EMC-CLARiiON-APM00212103684 ok true 0x5006016548e0080c, 24
0x5006016d48e0080c
EMC-SYMMETRIX-197902579 ok - 0x50000973b0284c0a, 130
0x50000973b0284c4a

/clusters/cluster-2/storage-elements/storage-arrays:
Name Connectivity Auto Ports Logical
-------------------------- Status Switch ------------------- Unit
-------------------------- ------------- ------ ------------------- Count
-------------------------- ------------- ------ ------------------- -------
DellEMC-PowerStore-6QMRJM3 ok - 0x58ccf0904b21064c, 130
0x58ccf0984b21064c
EMC-SYMMETRIX-197902578 ok - 0x50000973b0284886, 130
0x50000973b02848c6

5. To ensure that the backend ports IO-04, IO-05, IO-06, and IO-07 are operational for all the nodes, use command ll
clusters/*/directors/*/ports/. For more details, see the step 1 of backend path zoning configuration.
6. Ensure that the after system configuration phase-2 apply is completed, the frontend ports IO-00, IO-01, IO-02, and IO-03
are operational for all the nodes using the command ll clusters/*/directors/*/ports/.
7. Ensure that the storage volumes are available as mentioned in Volume pre-requisite.
8. Once the zoning is completed, then go to the next task.

Procedure 23

Page 28 of 120
Task 5: Interview (phase 2)
Director-1-1-B
NOTE:
● Before starting phase 2, ensure to have all the BE arrays zoned, and WAN IP details are ready. For more details on
WAN-related requirements, see the section WAN configuration details and checklist.
● The metro node cluster only asks the logging volumes, not the local cluster.
● Platforms can look for the respective examples for IP WAN and FC WAN in the below sections.

IP WAN(configuration for mn114)

About this task
NOTE: Get all WAN IP details ready. For more details on WAN-related requirements, see the section WAN configuration
details and checklist.

Steps
1. To log in to Voyager Director-1-1-B as a service user.
2. Ensure that the WANCOM IP addresses entered are accurate.
3. Run vplex_system_config --interview, and press ENTER to proceed with phase-2 interview.

service@director-1-1-a:~> vplex_system_config --interview

Do you want to re-run the phase-1 interview(y/n)?
Press "y" to re-run or "enter" to proceed with phase-2 interview. (default: n):

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.

Phase-2 interview process is started...

Rediscovering the array EMC-CLARiiON-APM00233408560 on cluster-1

Rediscovering the array EMC-SYMMETRIX-120001710 on cluster-1

List of the meta volume candidates for cluster: cluster-1

SERIAL NO VOLUME NAME CAPACITY IO

STATUS TYPE ARRAY NAME
--------- ------------- --------
--------- ---- ----------

1 VPD83T3:60000970000120001710533030443142 80G alive

traditional EMC-SYMMETRIX-120001710

2 VPD83T3:60000970000120001710533030443143 100G alive

traditional EMC-SYMMETRIX-120001710

.
.

11 VPD83T3:6006016053d050004260566595b013a5 80G alive

traditional EMC-CLARiiON-APM00233408560

12 VPD83T3:6006016053d05000445f56652f5b0ab0 100G alive

traditional EMC-CLARiiON-APM00233408560

24 Procedure

Page 29 of 120
Note: Storage volumes can be specified by name, by serial number, or by a combination
of both.

Please select two volumes from different arrays (one from each array) from above list.

Enter Meta-volume candidate 1 : 1

Enter Meta-volume candidate 2 : 12

Selected volumes are: ['VPD83T3:60000970000120001710533030443142',

'VPD83T3:6006016053d05000445f56652f5b0ab0']

Meta volume meta_C1_43A47L9 has been created successfully for the cluster: cluster-1

Rediscovering the array EMC-CLARiiON-APM00235007880 on cluster-2

Rediscovering the array EMC-SYMMETRIX-120001734 on cluster-2

List of the meta volume candidates for cluster: cluster-2

SERIAL NO VOLUME NAME CAPACITY IO

STATUS TYPE ARRAY NAME
--------- ------------- --------
--------- ---- ----------

1 VPD83T3:60000970000120001734533030353846 100G alive

traditional EMC-SYMMETRIX-120001734

2 VPD83T3:60000970000120001734533030353930 100G alive

traditional EMC-SYMMETRIX-120001734
.
.

8 VPD83T3:6006016030405e00c295a865406e2a89 100G alive

traditional EMC-CLARiiON-APM00235007880

9 VPD83T3:6006016030405e00c495a865c558bbc4 80G alive

traditional EMC-CLARiiON-APM00235007880

Note: Storage volumes can be specified by name, by serial number, or by a combination

of both.

Please select two volumes from different arrays (one from each array) from above list.

Enter Meta-volume candidate 1 : 1

Enter Meta-volume candidate 2 : 9

Selected volumes are: ['VPD83T3:60000970000120001734533030353846',

'VPD83T3:6006016030405e00c495a865c558bbc4']

Meta volume meta_C2_43A67L9 has been created successfully for the cluster: cluster-2

Do you want to proceed with logging volume creation(y/n)? (default: y):

Creating logging volume process is started...

Do you want to choose the components for logging volumes (Y/N) (default: y):
Choose number of volumes for logging volumes(1/2) (default: 2):

Rediscovering the array EMC-CLARiiON-APM00233408560 on cluster-1

Procedure 25

Page 30 of 120
 Rediscovering the array EMC-SYMMETRIX-120001710 on cluster-1

Storage volume candidate list for cluster: cluster-1

SERIAL NO VOLUME NAME CAPACITY IO

STATUS TYPE ARRAY NAME
--------- ------------- --------
--------- ---- ----------

1 VPD83T3:60000970000120001710533030443033 20G alive

traditional EMC-SYMMETRIX-120001710

2 VPD83T3:60000970000120001710533030443034 20G alive

traditional EMC-SYMMETRIX-120001710

.
.
.

49 VPD83T3:6006016053d050006b5f566537e1dc92 20G alive

traditional EMC-CLARiiON-APM00233408560

50 VPD83T3:6006016053d050006e5f566532fab735 20G alive

traditional EMC-CLARiiON-APM00233408560

Note: Storage volumes can be specified by name, by serial number, or by a combination

of both.

Please select two volumes from different arrays (one from each array) from above list.

Enter logging-volume candidate 1 : 1

Enter logging-volume candidate 2 : 50

Selected volumes are: ['VPD83T3:60000970000120001710533030443033',

'VPD83T3:6006016053d050006e5f566532fab735']

Logging volume c1_logging_43A47L9_vol has been created successfully for the cluster
:cluster-1

Rediscovering the array EMC-CLARiiON-APM00235007880 on cluster-2

Rediscovering the array EMC-SYMMETRIX-120001734 on cluster-2

Storage volume candidate list for cluster: cluster-2

SERIAL NO VOLUME NAME CAPACITY IO

STATUS TYPE ARRAY NAME
--------- ------------- --------
--------- ---- ----------

1 VPD83T3:60000970000120001734533030353735 20G alive

traditional EMC-SYMMETRIX-120001734

2 VPD83T3:60000970000120001734533030353736 20G alive

traditional EMC-SYMMETRIX-120001734

.
.
.

46 VPD83T3:6006016030405e00fd95a865da093735 20G alive

traditional EMC-CLARiiON-APM00235007880

26 Procedure

Page 31 of 120
 47 VPD83T3:6006016030405e00ff95a86560c5531d 20G alive
traditional EMC-CLARiiON-APM00235007880

Note: Storage volumes can be specified by name, by serial number, or by a combination

of both.

Please select two volumes from different arrays (one from each array) from above list.

Enter logging-volume candidate 1 : 1

Enter logging-volume candidate 2 : 47

Selected volumes are: ['VPD83T3:60000970000120001734533030353735',

'VPD83T3:6006016030405e00ff95a86560c5531d']

Logging volume c2_logging_43A47L9_vol has been created successfully for the cluster
:cluster-2

WANCOM interview process is started...

Types of wan configurations supported.

1. Routed
2. Bridged
Please select your wan type: 2

Collecting the wan details for cluster-1

Collecting Gateway, subnet, MTU & prefix for WC-00 ports at cluster-1
Enter prefix IP(should be same for all WC-00 of cluster-1)(example:
192.168.35.0): 192.x.x.x
Enter netmask IP(should be same for all WC-00 of cluster-1): 255.x.x.x
Enter MTU(should be same for all WC-00 of cluster-1) (default: 1500):

Collecting Gateway, subnet, MTU & prefix for WC-01 ports at cluster-1
Enter prefix IP(should be same for all WC-01 of cluster-1)(example:
192.168.36.0): 192.x.x.x
Enter netmask IP(should be same for all WC-01 of cluster-1): 255.x.x.x
Enter MTU(should be same for all WC-01 of cluster-1) (default: 1500):

Collecting director-1-1-A details

Enter WC-00 IP address: 192.x.x.x
Enter WC-01 IP address: 192.x.x.x

Collecting director-1-1-B details

Enter WC-00 IP address: 192.x.x.x
Enter WC-01 IP address: 192.x.x.x

Collecting the wan details for cluster-2

Collecting Gateway, subnet, MTU & prefix for WC-00 ports at cluster-2
Enter MTU(should be same for all WC-00 of cluster-2) (default: 1500):

Collecting Gateway, subnet, MTU & prefix for WC-01 ports at cluster-2
Enter MTU(should be same for all WC-01 of cluster-2) (default: 1500):

Collecting director-2-1-A details

Enter WC-00 IP address: 192.x.x.x
Enter WC-01 IP address: 192.x.x.x

Collecting director-2-1-B details

Enter WC-00 IP address: 192.x.x.x
Enter WC-01 IP address: 192.x.x.x

Please review the details entered.

wan_type: bridged
name: cluster-1
wan-com:
WC-00:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x

Procedure 27

Page 32 of 120
 mtu: 1500
WC-01:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
nodes
8K63Z23
interfaces:
WC-00:
ip:
address: 192.x.x.x
role: wan-com
WC-01:
ip:
address: 192.x.x.x
role: wan-com
8K64Z23
interfaces:
WC-00:
ip:
address: 192.x.x.x
role: wan-com
WC-01:
ip:
address: 192.x.x.x
role: wan-com
name: cluster-2
wan-com:
WC-00:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
WC-01:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
nodes
8K65Z23
interfaces:
WC-00:
ip:
address: 192.x.x.x
role: wan-com
WC-01:
ip:
address: 192.x.x.x
role: wan-com
8K66Z23
interfaces:
WC-00:
ip:
address: 192.x.x.x
role: wan-com
WC-01:
ip:
address: 192.x.x.x
role: wan-com

Please review the above details.

Do you want to proceed(y/n)? (default: y):

Phase-2 interview process is completed.

To start the phase-2 configuration, run the command "vplex_system_config -c".

service@director-1-1-a:~>

28 Procedure

Page 33 of 120
4. Once the interview process completes successfully, then go to next task.

IP WAN(configuration for mn215)

About this task
NOTE: Get all WAN IP details ready. For more details on WAN-related requirements, see the section WAN configuration
details and checklist.

Steps
1. To log in to Voyager Director-1-1-B as a service user.
2. Ensure that the WANCOM IP addresses entered are accurate.
3. Run vplex_system_config --interview, and press ENTER to proceed with phase-2 interview.

service@director-1-1-a:~> vplex_system_config -i
Do you want to re-run the phase-1 interview(y/n)?
Press "y" to re-run or "enter" to proceed with phase-2 interview. (default: n):

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.

Phase-2 interview process is started...

Rediscovering the array DellEMC-PowerStore-F39WPT3 on cluster-1

Rediscovering the array EMC-CLARiiON-APM00140915047 on cluster-1

Rediscovering the array DellEMC-PowerStore-719WPT3 on cluster-1

Rediscovering the array EMC-CLARiiON-APM00140215986 on cluster-1

List of the meta volume candidates for cluster: cluster-1

SERIAL NO VOLUME NAME CAPACITY IO

STATUS TYPE ARRAY NAME
--------- ------------- --------
--------- ---- ----------

1 VPD83T3:6006016017303500020bda38892fed11 100G alive

traditional EMC-CLARiiON-APM00140215986

...
...

20 VPD83T3:68ccf09800f4a5409af12f526508b3a4 100G alive

traditional DellEMC-PowerStore-F39WPT3

Note: Storage volumes can be specified by name, by serial number, or by a combination

of both.

Please select two volumes from different arrays (one from each array) from above list.

Enter Meta-volume candidate 1 : 1

Enter Meta-volume candidate 2 : 20

Selected volumes are: ['VPD83T3:6006016017303500020bda38892fed11',

'VPD83T3:68ccf09800f4a5409af12f526508b3a4']

Logging volume meta_C1_4S1LDH5 has been created successfully for the cluster

Procedure 29

Page 34 of 120
 :cluster-1

Rediscovering the array DellEMC-PowerStore-719WPT3 on cluster-2

Rediscovering the array DellEMC-PowerStore-F39WPT3 on cluster-2

Rediscovering the array EMC-CLARiiON-APM00140915047 on cluster-2

Rediscovering the array EMC-CLARiiON-APM00140215986 on cluster-2

List of the meta volume candidates for cluster: cluster-2

SERIAL NO VOLUME NAME CAPACITY IO

STATUS TYPE ARRAY NAME
--------- ------------- --------
--------- ---- ----------

1 VPD83T3:600601601730350080442c1e88a6ea11 100G alive

traditional EMC-CLARiiON-APM00140215986

...
...

15 VPD83T3:68ccf09800ceb539b9d69fe28e475e44 100G alive

traditional DellEMC-PowerStore-F39WPT3

Note: Storage volumes can be specified by name, by serial number, or by a combination

of both.

Please select two volumes from different arrays (one from each array) from above list.

Enter Meta-volume candidate 1 : 1

Enter Meta-volume candidate 2 : 15

Selected volumes are: ['VPD83T3:600601601730350080442c1e88a6ea11',

'VPD83T3:68ccf09800ceb539b9d69fe28e475e44']

Meta volume meta_C2_4S1LDH7 has been created successfully for the cluster: cluster-2

Do you want to proceed with logging volume creation(y/n)? (default: y): y

Creating logging volume process is started...

Do you want to choose the components for logging volumes (Y/N) (default: y): y
Choose number of volumes for logging volumes(1/2) (default: 2):

Rediscovering the array DellEMC-PowerStore-F39WPT3 on cluster-1

Rediscovering the array EMC-CLARiiON-APM00140915047 on cluster-1

Rediscovering the array DellEMC-PowerStore-719WPT3 on cluster-1

Rediscovering the array EMC-CLARiiON-APM00140215986 on cluster-1

Storage volume candidate list for cluster: cluster-1

SERIAL NO VOLUME NAME CAPACITY IO

STATUS TYPE ARRAY NAME
--------- ------------- --------

30 Procedure

Page 35 of 120
--------- ---- ----------

1 VPD83T3:600601601730350005e6ff133a88ec11 10G alive

traditional EMC-CLARiiON-APM00140215986

...
...

158 VPD83T3:68ccf09800fcfe261850103bbea16999 20G alive

traditional DellEMC-PowerStore-F39WPT3

Note: Storage volumes can be specified by name, by serial number, or by a combination

of both.

Please select serial no or volume name of volumes from above list.

Enter logging-volume candidate 1 : 1

Enter logging-volume candidate 2 : 158

Selected volumes are: ['VPD83T3:600601601730350005e6ff133a88ec11',

'VPD83T3:68ccf09800fcfe261850103bbea16999']

Logging volume c1_logging_4S1LDH5_vol has been created successfully for the cluster
:cluster-1

Rediscovering the array DellEMC-PowerStore-719WPT3 on cluster-2

Rediscovering the array DellEMC-PowerStore-F39WPT3 on cluster-2

Rediscovering the array EMC-CLARiiON-APM00140915047 on cluster-2

Rediscovering the array EMC-CLARiiON-APM00140215986 on cluster-2

Storage volume candidate list for cluster: cluster-2

SERIAL NO VOLUME NAME CAPACITY IO

STATUS TYPE ARRAY NAME
--------- ------------- --------
--------- ---- ----------

1 VPD83T3:6006016017303500e11d960988a6ea11 100G alive

traditional EMC-CLARiiON-APM00140215986

...
...

133 VPD83T3:68ccf09800fe1f5c7e9559b59c4e745d 20G alive

traditional DellEMC-PowerStore-F39WPT3

Note: Storage volumes can be specified by name, by serial number, or by a combination

of both.

Please select serial no or volume name of volumes from above list.

Enter logging-volume candidate 1 : 1

Enter logging-volume candidate 2 : 133

Selected volumes are: ['VPD83T3:6006016017303500e11d960988a6ea11',

'VPD83T3:68ccf09800fe1f5c7e9559b59c4e745d']

Logging volume c2_logging_4S1LDH5_vol has been created successfully for the cluster
:cluster-2

WANCOM interview process is started...

Procedure 31

Page 36 of 120
 Types of protocol supported for WAN configurations.
1. FC
2. IP
Please select your protocol by typing 'IP' or 'FC': (default: FC): IP
WAN IP is selected. IP Ports need to be properly connected
Are you sure you want to select protocol IP? (yes/no): yes

Types of wan configurations supported.

1. Routed
2. Bridged
Please select your wan type: 2

Collecting the wan details for cluster-1

Collecting Gateway, subnet, MTU & prefix for WC-IP-00 ports at cluster-1
Enter prefix IP(should be same for all WC-IP-00 of cluster-1)
(example: 192.168.35.0): 192.x.x.x
Enter netmask IP(should be same for all WC-IP-00 of cluster-1):
255.x.x.x
Enter MTU(should be same for all WC-IP-00 of cluster-1) (default:
1500):

Collecting Gateway, subnet, MTU & prefix for WC-IP-01 ports at cluster-1
Enter prefix IP(should be same for all WC-IP-01 of cluster-1)
(example: 192.168.36.0): 192.x.x.x
Enter netmask IP(should be same for all WC-IP-01 of cluster-1):
255.x.x.x
Enter MTU(should be same for all WC-IP-01 of cluster-1) (default:
1500):

Collecting director-1-1-A details

Enter WC-IP-00 IP address: 192.x.x.x
Enter WC-IP-01 IP address: 192.x.x.x

Collecting director-1-1-B details

Enter WC-IP-00 IP address: 192.x.x.x
Enter WC-IP-01 IP address: 192.x.x.x

Collecting the wan details for cluster-2

Collecting Gateway, subnet, MTU & prefix for WC-IP-00 ports at cluster-2
Enter MTU(should be same for all WC-IP-00 of cluster-2) (default:
1500):

Collecting Gateway, subnet, MTU & prefix for WC-IP-01 ports at cluster-2
Enter MTU(should be same for all WC-IP-01 of cluster-2) (default:
1500):

Collecting director-2-1-A details

Enter WC-IP-00 IP address: 192.x.x.x
Enter WC-IP-01 IP address: 192.x.x.x

Collecting director-2-1-B details

Enter WC-IP-00 IP address: 192.x.x.x
Enter WC-IP-01 IP address: 192.x.x.x

Please review the details entered.

wan_type: bridged
name: cluster-1
wan-com:
WC-IP-00:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
WC-IP-01:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
nodes

32 Procedure

Page 37 of 120
 4GCK0R3
interfaces:
WC-IP-00:
ip:
address: 192.x.x.x
role: wan-com
WC-IP-01:
ip:
address: 192.x.x.x
role: wan-com
5GCK0R3
interfaces:
WC-IP-00:
ip:
address: 192.x.x.x
role: wan-com
WC-IP-01:
ip:
address: 192.x.x.x
role: wan-com
name: cluster-2
wan-com:
WC-IP-00:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
WC-IP-01:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
nodes
6GCK0R3
interfaces:
WC-IP-00:
ip:
address: 192.x.x.x
role: wan-com
WC-IP-01:
ip:
address: 192.x.x.x
role: wan-com
7GCK0R3
interfaces:
WC-IP-00:
ip:
address: 192.x.x.x
role: wan-com
WC-IP-01:
ip:
address: 192.x.x.x
role: wan-com

Please review the above details.

Do you want to proceed(y/n)? (default: y): y

Phase-2 interview process is completed.

To start the phase-2 configuration, run the command "vplex_system_config -c".

4. Once the interview process completes successfully, then go to next task.

FC WAN(configuration for mn215)

Steps
1. Run vplex_system_config --interview, and press ENTER to proceed with the phase-2 interview.

Procedure 33

Page 38 of 120
 NOTE: Before starting phase-2, ensure to have all the BE arrays zoned.

service@director-1-1-a:~> vplex_system_config --interview

Do you want to re-run the phase-1 interview(y/n)?
Press "y" to re-run or "enter" to proceed with phase-2 interview. (default: n):

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.

Phase-2 interview process is started...

Rediscovering the array EMC-CLARiiON-APM00140215986 on cluster-1

Rediscovering the array DellEMC-PowerStore-719WPT3 on cluster-1

Rediscovering the array EMC-CLARiiON-APM00140915047 on cluster-1

Rediscovering the array DellEMC-PowerStore-F39WPT3 on cluster-1

List of the meta volume candidates for cluster: cluster-1

SERIAL NO VOLUME NAME CAPACITY IO

STATUS TYPE ARRAY NAME
--------- ------------- --------
--------- ---- ----------

1 VPD83T3:6006016017303500020bda38892fed11 100G alive

traditional EMC-CLARiiON-APM00140215986

2 VPD83T3:60060160173035006fc76560892fed11 100G alive

traditional EMC-CLARiiON-APM00140215986

.
.
.

19 VPD83T3:68ccf09800da992896081ce15c1e636f 100G alive

traditional DellEMC-PowerStore-F39WPT3

20 VPD83T3:68ccf09800f4a5409af12f526508b3a4 100G alive

traditional DellEMC-PowerStore-F39WPT3

Note: Storage volumes can be specified by name, by serial number, or by a combination

of both.

Please select two volumes from different arrays (one from each array) from above list.

Enter Meta-volume candidate 1 : 1

Enter Meta-volume candidate 2 : 20

Selected volumes are: ['VPD83T3:6006016017303500020bda38892fed11',

'VPD83T3:68ccf09800f4a5409af12f526508b3a4']

Meta volume meta_C1_4S1LDH5 has been created successfully for the cluster: cluster-1

Rediscovering the array DellEMC-PowerStore-719WPT3 on cluster-2

Rediscovering the array EMC-CLARiiON-APM00140215986 on cluster-2

34 Procedure

Page 39 of 120
Rediscovering the array DellEMC-PowerStore-F39WPT3 on cluster-2

Rediscovering the array EMC-CLARiiON-APM00140915047 on cluster-2

List of the meta volume candidates for cluster: cluster-2

SERIAL NO VOLUME NAME CAPACITY IO

STATUS TYPE ARRAY NAME
--------- ------------- --------
--------- ---- ----------

1 VPD83T3:600601601730350080442c1e88a6ea11 100G alive

traditional EMC-CLARiiON-APM00140215986

2 VPD83T3:6006016017303500e11d960988a6ea11 100G alive

traditional EMC-CLARiiON-APM00140215986

.
.
.

14 VPD83T3:68ccf098009f6db62449f07c4cf6c4e2 100G alive

traditional DellEMC-PowerStore-719WPT3

15 VPD83T3:68ccf09800ceb539b9d69fe28e475e44 100G alive

traditional DellEMC-PowerStore-F39WPT3

Note: Storage volumes can be specified by name, by serial number, or by a combination

of both.

Please select two volumes from different arrays (one from each array) from above list.

Enter Meta-volume candidate 1 : 1

Enter Meta-volume candidate 2 : 15

Selected volumes are: ['VPD83T3:600601601730350080442c1e88a6ea11',

'VPD83T3:68ccf09800ceb539b9d69fe28e475e44']

Meta volume meta_C2_4S1LDH7 has been created successfully for the cluster: cluster-2

Do you want to proceed with logging volume creation(y/n)? (default: y):

Creating logging volume process is started...

Do you want to choose the components for logging volumes (Y/N) (default: y):
Choose number of volumes for logging volumes(1/2) (default: 2):

Rediscovering the array EMC-CLARiiON-APM00140215986 on cluster-1

Rediscovering the array DellEMC-PowerStore-719WPT3 on cluster-1

Rediscovering the array EMC-CLARiiON-APM00140915047 on cluster-1

Rediscovering the array DellEMC-PowerStore-F39WPT3 on cluster-1

Storage volume candidate list for cluster: cluster-1

SERIAL NO VOLUME NAME CAPACITY IO

STATUS TYPE ARRAY NAME

Procedure 35

Page 40 of 120
 --------- ------------- --------
--------- ---- ----------

1 VPD83T3:600601601730350005e6ff133a88ec11 10G alive

traditional EMC-CLARiiON-APM00140215986

2 VPD83T3:600601601730350006e6ff133a88ec11 10G alive

traditional EMC-CLARiiON-APM00140215986
.
.
.

157 VPD83T3:68ccf09800efe3b9bcee426b466ed6c3 20G alive

traditional DellEMC-PowerStore-F39WPT3

158 VPD83T3:68ccf09800fcfe261850103bbea16999 20G alive

traditional DellEMC-PowerStore-F39WPT3

Note: Storage volumes can be specified by name, by serial number, or by a combination

of both.

Please select serial no or volume name of volumes from above list.

Enter logging-volume candidate 1 : 1

Enter logging-volume candidate 2 : 158

Selected volumes are: ['VPD83T3:600601601730350005e6ff133a88ec11',

'VPD83T3:68ccf09800fcfe261850103bbea16999']

Logging volume c1_logging_4S1LDH5_vol has been created successfully for the cluster
:cluster-1

Rediscovering the array DellEMC-PowerStore-719WPT3 on cluster-2

Rediscovering the array EMC-CLARiiON-APM00140215986 on cluster-2

Rediscovering the array DellEMC-PowerStore-F39WPT3 on cluster-2

Rediscovering the array EMC-CLARiiON-APM00140915047 on cluster-2

Storage volume candidate list for cluster: cluster-2

SERIAL NO VOLUME NAME CAPACITY IO

STATUS TYPE ARRAY NAME
--------- ------------- --------
--------- ---- ----------

1 VPD83T3:6006016017303500e11d960988a6ea11 100G alive

traditional EMC-CLARiiON-APM00140215986

2 VPD83T3:600601601940380000cfd5dfb986e711 10G alive

traditional EMC-CLARiiON-APM00140915047
.
.
.
132 VPD83T3:68ccf09800fe093f0fce64f478956306 20G alive
traditional DellEMC-PowerStore-719WPT3

133 VPD83T3:68ccf09800fe1f5c7e9559b59c4e745d 20G alive

traditional DellEMC-PowerStore-F39WPT3

Note: Storage volumes can be specified by name, by serial number, or by a combination

of both.

Please select serial no or volume name of volumes from above list.

36 Procedure

Page 41 of 120
Enter logging-volume candidate 1 : 1

Enter logging-volume candidate 2 : 133

Selected volumes are: ['VPD83T3:6006016017303500e11d960988a6ea11',

'VPD83T3:68ccf09800fe1f5c7e9559b59c4e745d']

Logging volume c2_logging_4S1LDH5_vol has been created successfully for the cluster
:cluster-2

WANCOM interview process is started...

Types of protocol supported for WAN configurations.

1. FC
2. IP
Please select your protocol by typing 'IP' or 'FC': (default: FC): FC
WAN FC is selected. FC Ports need to be properly connected
Are you sure you want to select protocol FC? (yes/no): yes

Connecting to 100.x.x.x to fetch the hardware description file (hal.yml)

Connecting to 100.x.x.x to fetch the hardware description file (hal.yml)

Connecting to 100.x.x.x to fetch the hardware description file (hal.yml)

Connecting to 100.x.x.x to fetch the hardware description file (hal.yml)

Please review the details entered.

wan_type: FC
name: cluster-1
wan-com:
nodes:
4GCK0R3
interfaces:
WC-FC-00:
enabled: False
role: wan-com
WC-FC-01:
enabled: False
role: wan-com
5GCK0R3
interfaces:
WC-FC-00:
enabled: False
role: wan-com
WC-FC-01:
enabled: False
role: wan-com
name: cluster-2
wan-com:
nodes:
6GCK0R3
interfaces:
WC-FC-00:
enabled: False
role: wan-com
WC-FC-01:
enabled: False
role: wan-com
7GCK0R3
interfaces:
WC-FC-00:
enabled: False
role: wan-com
WC-FC-01:
enabled: False
role: wan-com

Procedure 37

Page 42 of 120
 Please review the above details.
Do you want to proceed(y/n)? (default: y):

Phase-2 interview process is completed.

To start the phase-2 configuration, run the command "vplex_system_config -c".

service@director-1-1-a:~>

2. Once the interview phase_2 completes successfully, go to the next task.

Task 6: Apply Changes (phase 2)

Director-1-1-B
Pre-requisite:
1. Ensure that the frontend cables are connected to SAN. If the ports show no-link, then script fails at the time of verification
of FE port status.
2. For WAN IP ports (Routed or Bridged wan type), ensure that WANCOM routing is done before running phase-2 apply.
3. For WAN FC ports, to perform WANCOM routing, find the WWN of WAN FC ports for each node using the below steps:
a. Open a web browser and go to https://central.dell.com/wwn-calculator/metro-node or click WWN
Calculator| Metro node.
b. On the WWN Calculator page, under Hardware Version select as mn-215 and, then under Cluster select as Single.
c. Run sudo /opt/dell/vplex/bin/vplex-fru17 read wwn_seed command in the node to know the WWN seed
for the node.
d. Go back to the WWN Calculator page, in the Seed Number 1 textbox, paste the output of the above command.
e. Click Encode to see the WWN values of WC-FC-00 and WC-FC-01 ports in the WWPN column and note these values.
f. Once WWPNs of all the nodes have been noted, complete WAN COM routing.
1. To start the Phase 2 of system_config, run the command vplex_system_config -c.

NOTE: The below output is a sample output.

service@director-1-1-a:~> vplex_system_config -c

Active meta volume 'meta_C1_43A47L9' is already present for the cluster: cluster-1

Active meta volume 'meta_C2_43A67L9' is already present for the cluster: cluster-2
Starting the system configuration process for phase 2...
TASK: Gathering Facts - PASS
TASK: Configuring front ports - PASS
TASK: Get the directors - PASS
TASK: Get all director names - PASS
.
.
.
TASK: Start the vplex-node target - PASS
TASK: Setting vplex-node target as default - PASS
TASK: Disabling the nsfw - PASS
TASK: Checking system is running - PASS

PLAY RECAP
**************************************************************************************
************************************************************
director-1-1-A|8K63Z23 : ok=40 changed=7 unreachable=0 failed=0
skipped=19 rescued=0 ignored=0
director-1-1-B|8K64Z23 : ok=26 changed=7 unreachable=0 failed=0
skipped=33 rescued=0 ignored=0

38 Procedure

Page 43 of 120
 director-2-1-A|8K65Z23 : ok=29 changed=7 unreachable=0 failed=0
skipped=30 rescued=0 ignored=0
director-2-1-B|8K66Z23 : ok=26 changed=7 unreachable=0 failed=0
skipped=33 rescued=0 ignored=0

System configuration process for phase 2 is successful

service@director-1-1-a:~>

Task 7: Create Metavolume Backup

● Run the command vplex_system_config --metadata-backup-create to start the backup of metadata for both
clusters.

Director-1-1-B
1. Run the command vplex_system_config --metadata-backup-create command to start the backup of metadata
on cluster-1.

service@director-1-1-a:~> vplex_system_config --metadata-backup-create

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.

Validating active meta volume availability...

Active meta volume 'meta_C1_XXXXXXX' is already present for the cluster: cluster-1

Active meta volume 'meta_C2_YYYYYYY' is already present for the cluster: cluster-2

Creating meta data backup process started...

Enter the hour of daily backup(0-23) (default: 1):

Enter the minute of daily backup(0-59) (default: 30):

List of the meta volume candidates for cluster: cluster-1

SERIAL NO VOLUME NAME CAPACITY IO

STATUS TYPE ARRAY NAME
--------- ------------- --------
--------- ---- ----------

1 VPD83T3:60000970000197902579533030393345 80G alive

traditional EMC-SYMMETRIX-197902579

2 VPD83T3:60000970000197902579533030393430 80G alive

traditional EMC-SYMMETRIX-197902579

3 VPD83T3:60000970000197902579533030393431 80G alive

traditional EMC-SYMMETRIX-197902579

4 VPD83T3:60000970000197902579533030393432 100G alive

traditional EMC-SYMMETRIX-197902579

5 VPD83T3:60000970000197902579533030393433 100G alive

traditional EMC-SYMMETRIX-197902579

6 VPD83T3:68ccf098001475d928c1b8b958fbfcfc 100G alive

traditional DellEMC-PowerStore-2R10643

7 VPD83T3:68ccf098001f6db78ba7134bfa131178 80G alive

Procedure 39

Page 44 of 120
 traditional DellEMC-PowerStore-2R10643

8 VPD83T3:68ccf098005de14f2ea337596257c9cc 80G alive

traditional DellEMC-PowerStore-2R10643

9 VPD83T3:68ccf098008ab70b108aafc03f9ca55e 80G alive

traditional DellEMC-PowerStore-2R10643

10 VPD83T3:68ccf09800a6529cb9647f72ff951c69 80G alive

traditional DellEMC-PowerStore-2R10643

Note: Storage volumes can be specified by name, by serial number, or by a combination

of both.

Please select serial no or volume name of two volumes from above list.

Enter Meta-volume candidate 1 : 1

Enter Meta-volume candidate 2 : 10

Selected volumes are: ['VPD83T3:60000970000197902579533030393345',

'VPD83T3:68ccf09800a6529cb9647f72ff951c69']

Meta data backup schedule meta_C1_XXXXXXX_backup has been created successfully for
the cluster: cluster-1

List of the meta volume candidates for cluster: cluster-2

SERIAL NO VOLUME NAME CAPACITY IO

STATUS TYPE ARRAY NAME
--------- ------------- --------
--------- ---- ----------

1 VPD83T3:60000970000197902578533030444439 100G alive

traditional EMC-SYMMETRIX-197902578

2 VPD83T3:60000970000197902578533031353633 80G alive

traditional EMC-SYMMETRIX-197902578

3 VPD83T3:60000970000197902578533032363536 80G alive

traditional EMC-SYMMETRIX-197902578

4 VPD83T3:60000970000197902578533032363537 80G alive

traditional EMC-SYMMETRIX-197902578

5 VPD83T3:60000970000197902578533032363538 80G alive

traditional EMC-SYMMETRIX-197902578

6 VPD83T3:68ccf098004456fad11abb1494515434 80G alive

traditional DellEMC-PowerStore-6QMRJM3

7 VPD83T3:68ccf0980045521ed15323405e78aab1 80G alive

traditional DellEMC-PowerStore-6QMRJM3

8 VPD83T3:68ccf098004e962244f5d669aa6d1569 80G alive

traditional DellEMC-PowerStore-6QMRJM3

9 VPD83T3:68ccf0980054113d32c80e986ae0234a 100G alive

traditional DellEMC-PowerStore-6QMRJM3

10 VPD83T3:68ccf098006ca5eb5c40e89469ad0edc 80G alive

traditional DellEMC-PowerStore-6QMRJM3

Note: Storage volumes can be specified by name, by serial number, or by a combination

of both.

Please select serial no or volume name of two volumes from above list.

Enter Meta-volume candidate 1 : 1

40 Procedure

Page 45 of 120
 Enter Meta-volume candidate 2 : 10

Selected volumes are: ['VPD83T3:60000970000197902578533030444439',

'VPD83T3:68ccf098006ca5eb5c40e89469ad0edc']

Meta data backup schedule meta_C2_YYYYYYY_backup has been created successfully for
the cluster: cluster-2

Creating meta data backup process completed.

service@director-1-1-b:~>

Check Cluster Status

1. Once the above steps are successfully completed, the cluster status must have OK for all the fields, and cluster summary
must show both the clusters on the same island.

Trying ::1...
Connected to localhost.
Escape character is '^]'.

VPlexcli:/> cluster status

Cluster cluster-1
operational-status: ok
transitioning-indications:
transitioning-progress:
health-state: ok
health-indications:
local-com: ok

Cluster cluster-2
operational-status: ok
transitioning-indications:
transitioning-progress:
health-state: ok
health-indications:
local-com: ok

wan-com: ok

VPlexcli:/> cluster
summary

Clusters:
Name Cluster ID TLA Connected Expelled Operational Status Health
State
--------- ---------- ------- --------- -------- ------------------
------------
cluster-1 1 43A26L9 true false ok ok
cluster-2 2 43A56L9 true false ok ok

Islands:
Island ID Clusters
--------- --------------------
1 cluster-1, cluster-2

NOTE: Once the metadata backup is created successfully in both the clusters and the cluster status command shows "OK,"
the system configuration is completed. The user can proceed with login into the UI and creating the soft configurations
such as creating devices, virtual volumes, and (apart from distributed devices which can be configured later after WAN is
configured) exporting to hosts.

Cluster Witness
The support of Cluster Witness (metro node Witness) enables the metro node solution to improve overall environment
availability by arbitrating a pure communication failure between two primary sites, and an actual site failure in a multisite

Procedure 41

Page 46 of 120
architecture. The Witness is an optional component that is deployed in the customer environments where regular preference
rule sets are insufficient to provide zero or near-zero RTO storage availability during site disasters, metro node cluster, and
intercluster failures.
For more information related to the configuration of Cluster Witness (CW), see the Dell Metro node Cluster Witness
Configuration Guide , available at SolVe.

WAN configuration details

NOTE:
● WAN COM port configuration is applicable only for metro cluster setup.
● (For mn-114) It is not necessary to use VLANs. If used, then all WC-00 ports and WC-01 ports must be assigned to the
same VLAN. Also, the VLAN used for WC-00 ports must be different than the VLAN used for WC-01 ports. If you are
not using VLANS, then ensure them to have on different subnets and different fault domain.
There are two types of WAN: Routed and Bridged. See the following sections for requirements of each WAN type:

IP WAN Configuration details (for mn-114)

The following details are required:

Table 4. IP WAN Configuration details (for mn-114)

Type or Port Description IPs required
Gateway Common for all WC-00 Ports → It can be 1 per cluster
left blank, if the IPs provided are internal
IP and no gateway is required.
Common for all WC-01 Ports → It can be 1 per cluster
left blank, if the IPs provided are internal
IP and no gateway is required.
Prefix Common for all WC-00 Ports → The first 1 per cluster
three octets of the WC-00 IP and the 0
in the last octet for example: if WC-00
interfaces start with 192.168.35.xx then
the prefix is 192.168.35.0
Common for all WC-01 ports → The first 1 per cluster
three octets of the WC-00 IP and the 0
in the last octet for example: if WC-01
interfaces start with 192.168.36.xx then
the prefix is 192.168.36.0
Netmask Common for all WC-00 Ports 1 per cluster
Common for all WC-01 ports 1 per cluster
MTU Common for all WC-00 Ports → Default N/A
1500
Common for all WC-00 Ports → Default N/A
1500
WC-00 All WC-00 IPs should be in the same 2 per cluster
vlan if vlans are present and reachable
through the gateway that is provided for
WC-00 ports.
WC-01 All WC-01 IPs should be in the same 2 per cluster
vlan if vlans are present and reachable
through the gateway that is provided for
WC-01 ports.

42 Procedure

Page 47 of 120
Example
See the sample of WAN interface IPs in the following table:
Cluster-1

Table 5. Cluster 1 - WAN interface IPs

Type or Port Interface IP Address
Gateway WC-00 ports '""
WC-01 ports '""
Prefix WC-00 ports 192.168.35.0
WC-01 ports 192.168.36.0
Netmask WC-00 ports 255.255.255.0
WC-01 ports 255.255.255.0
MTU WC-00 ports 1500
WC-01 ports 1500
1-1-A WC-00 192.168.56.35
1-1-A WC-01 192.168.57.35
1-1-B WC-00 192.168.56.36
1-1-B WC-01 192.168.57.36

Cluster-2

Table 6. Cluster 2 - WAN interface IPs

Type/port Interface IP Address
Gateway WC-00 ports '""
WC-01 ports '""
Prefix WC-00 ports 192.168.35.0
WC-01 ports 192.168.36.0
Netmask WC-00 ports 255.255.255.0
WC-01 ports 255.255.255.0
MTU WC-00 ports 1500
WC-01 ports 1500
2-1-A WC-00 192.168.156.67
2-1-A WC-01 192.168.157.67
2-1-B WC-00 192.168.156.68
2-1-B WC-01 192.168.157.68

Similarly, the same set of details is required for other clusters.

Routed WAN network configuration process

WANCOM interview process is started...

Types of wan configurations supported.

1. Routed
2. Bridged
Please select your wan type: 1

Collecting the wan details for cluster-1

Procedure 43

Page 48 of 120
 Collecting Gateway, subnet, MTU & prefix for WC-00 ports at cluster-1
Enter Gateway IP(should be same for all WC-00 of cluster-1) (default: ):
192.x.x.x
Enter prefix IP(should be same for all WC-00 of cluster-1)(example:
192.168.35.0): 192.x.x.x
Enter netmask IP(should be same for all WC-00 of cluster-1): 255.x.x.x
Enter MTU(should be same for all WC-00 of cluster-1) (default: 1500):

Collecting Gateway, subnet, MTU & prefix for WC-01 ports at cluster-1
Enter Gateway IP(should be same for all WC-01 of cluster-1) (default: ):
192.x.x.x
Enter prefix IP(should be same for all WC-01 of cluster-1)(example:
192.168.36.0): 192.x.x.x
Enter netmask IP(should be same for all WC-01 of cluster-1): 255.x.x.x
Enter MTU(should be same for all WC-01 of cluster-1) (default: 1500):

Collecting director-1-1-A details

Enter WC-00 IP address: 192.x.x.x
Enter WC-01 IP address: 192.x.x.x

Collecting director-1-1-B details

Enter WC-00 IP address: 192.x.x.x
Enter WC-01 IP address: 192.x.x.x

Collecting the wan details for cluster-2

Collecting Gateway, subnet, MTU & prefix for WC-00 ports at cluster-2
Enter Gateway IP(should be same for all WC-00 of cluster-2) (default: ):
192.x.x.x
Enter prefix IP(should be same for all WC-00 of cluster-2)(example:
192.168.35.0): 192.x.x.x
Enter netmask IP(should be same for all WC-00 of cluster-2): 255.x.x.x
Enter MTU(should be same for all WC-00 of cluster-2) (default: 1500):

Collecting Gateway, subnet, MTU & prefix for WC-01 ports at cluster-2
Enter Gateway IP(should be same for all WC-01 of cluster-2) (default: ):
192.x.x.x
Enter prefix IP(should be same for all WC-01 of cluster-2)(example:
192.168.36.0): 192.x.x.x
Enter netmask IP(should be same for all WC-01 of cluster-2): 255.x.x.x
Enter MTU(should be same for all WC-01 of cluster-2) (default: 1500):

Collecting director-2-1-A details

Enter WC-00 IP address: 192.x.x.x
Enter WC-01 IP address: 192.x.x.x

Collecting director-2-1-B details

Enter WC-00 IP address: 192.x.x.x
Enter WC-01 IP address: 192.x.x.x

Please review the details entered.

wan_type: routed
name: cluster-1
wan-com:
WC-00:
prefix: 192.x.x.x
gateway: 192.x.x.x
netmask: 255.x.x.x
mtu: 1500
WC-01:
prefix: 192.x.x.x
gateway: 192.x.x.x
netmask: 255.x.x.x
mtu: 1500
nodes
8KC4Z23
interfaces:
WC-00:
ip:
address: 192.x.x.x
WC-01:

44 Procedure

Page 49 of 120
 ip:
address: 192.x.x.x
8KC5Z23
interfaces:
WC-00:
ip:
address: 192.x.x.x
WC-01:
ip:
address: 192.x.x.x
name: cluster-2
wan-com:
WC-00:
prefix: 192.x.x.x
gateway: 192.x.x.x
netmask: 255.x.x.x
mtu: 1500
WC-01:
prefix: 192.x.x.x
gateway: 192.x.x.x
netmask: 255.x.x.x
mtu: 1500
nodes
8KC6Z23
interfaces:
WC-00:
ip:
address: 192.x.x.x
WC-01:
ip:
address: 192.x.x.x
8KCYY23
interfaces:
WC-00:
ip:
address: 192.x.x.x
WC-01:
ip:
address: 192.x.x.x

Please review the above details.

Do you want to proceed(y/n)? (default: y):

Bridged WAN
The following details are required:

Table 7. Bridged WAN

Type or Port Description IPs required
Gateway Common for all WC- 00 Ports at both 1 per cluster
clusters→ It can be left blank if the IPs
provided are internal IP and no gateway
is required.
Common for all WC-01 Ports at both 1 per cluster
clusters→ It can be left blank if the IPs
provided are internal IP and no gateway
is required.
Prefix Common for all WC-00 Ports at both 1 per cluster
clusters → The first three octets of the
WC-00 IP and the 0 in the last octet
for example: if WC-00 interfaces start
with 192.168.35.xx then the prefix is
192.168.35.0

Procedure 45

Page 50 of 120
Table 7. Bridged WAN (continued)
Type or Port Description IPs required
Common for all WC-01 ports at both 1 per cluster
clusters → The first three octets of the
WC-00 IP and the 0 in the last octet
for example: if WC-01 interfaces start
with 192.168.36.xx then the prefix is
192.168.36.0
Netmask Common for all WC-00 Ports 1 per cluster
Common for all WC-01 ports 1 per cluster
MTU Common for all WC-00 Ports → Default N/A
1500
Common for all WC-01 Ports → Default N/A
1500
WC-00 If VLANs are present and reachable 2 per cluster
through the gateway that is provided for
WC-00 ports, then all WC-00 IPs should
be in the same VLAN.
WC-01 If VLANs are present and reachable 2 per cluster
through the gateway that is provided for
WC-01 ports, then all WC-01 IPs should
be in the same VLAN.

Example
See the sample of bridged network IPs for WAN interface in the following table:

Table 8. WAN interface IPs

Type or Port Interface IP Address
Gateway WC-00 ports '""
WC-01 ports '""
Prefix WC-00 ports 192.x.x.x
WC-01 ports 192.x.x.x
Netmask WC-00 ports 255.x.x.x
WC-01 ports 255.x.x.x
MTU WC-00 ports 1500
WC-01 ports 1500
1-1-A WC-00 192.x.x.x
1-1-A WC-01 192.x.x.x
1-1-B WC-00 192.x.x.x
1-1-B WC-01 192.x.x.x
2-1-A WC-00 192.x.x.x
2-1-A WC-01 192.x.x.x
2-1-B WC-00 192.x.x.x
2-1-B WC-01 192.x.x.x

46 Procedure

Page 51 of 120
Example for bridged WAN network configuration process

WANCOM interview process started...

Types of wan configurations supported.

1. Routed
2. Bridged
Please select your wan type: 2

Collecting the wan details for cluster-1

Collecting Gateway, subnet, MTU & prefix for WC-00 ports at cluster-1
Enter prefix IP(should be same for all WC-00 of cluster-1)(example:
192.168.35.0): 192.x.x.x
Enter netmask IP(should be same for all WC-00 of cluster-1): 255.x.x.x
Enter MTU(should be same for all WC-00 of cluster-1) (default: 1500):

Collecting Gateway, subnet, MTU & prefix for WC-01 ports at cluster-1
Enter prefix IP(should be same for all WC-01 of cluster-1)(example:
192.168.35.0): 192.x.x.x
Enter netmask IP(should be same for all WC-01 of cluster-1): 255.x.x.x
Enter MTU(should be same for all WC-01 of cluster-1) (default: 1500):

Collecting director-1-1-A details

Enter WC-00 IP address: 192.x.x.x
Enter WC-01 IP address: 192.x.x.x

Collecting director-1-1-B details

Enter WC-00 IP address: 192.x.x.x
Enter WC-01 IP address: 192.x.x.x

Collecting the wan details for cluster-2

Collecting Gateway, subnet, MTU & prefix for WC-00 ports at cluster-2
Enter MTU(should be same for all WC-00 of cluster-2) (default: 1500):

Collecting Gateway, subnet, MTU & prefix for WC-01 ports at cluster-2
Enter MTU(should be same for all WC-01 of cluster-2) (default: 1500):

Collecting director-2-1-A details

Enter WC-00 IP address: 192.x.x.x
Enter WC-01 IP address: 192.x.x.x

Collecting director-2-1-B details

Enter WC-00 IP address: 192.x.x.x
Enter WC-01 IP address: 192.x.x.x

Please review the details entered.

wan_type: bridged
name: cluster-1
wan-com:
WC-00:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
WC-01:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
nodes
GMGT753
interfaces:
WC-00:
ip:
address: 192.x.x.x
WC-01:
ip:
address: 192.x.x.x
GMGV753
interfaces:

Procedure 47

Page 52 of 120
 WC-00:
ip:
address: 192.x.x.x
WC-01:
ip:
address: 192.x.x.x
name: cluster-2
wan-com:
WC-00:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
WC-01:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
nodes
GMGX753
interfaces:
WC-00:
ip:
address: 192.x.x.x
WC-01:
ip:
address: 192.x.x.x
GMGY753
interfaces:
WC-00:
ip:
address: 192.x.x.x
WC-01:
ip:
address: 192.x.x.x

Please review the above details.

Do you want to proceed(y/n)? (default: y):

IP WAN for mn215

The following details are required:

Table 9. IIP WAN Configuration details (for mn-215)

Type or Port Description IPs required
Gateway Common for all WC-IP-00 Ports → It 1 per cluster
can be left blank, if the IPs provided are
internal IP and no gateway is required.
Common for all WC-IP-01 Ports → It can 1 per cluster
be left blank, if the IPs provided are
internal IP and no gateway is required.
Prefix Common for all WC-IP-00 Ports → 1 per cluster
The first three octets of the WC-IP-00
IP and the 0 in the last octet for
example: if WC-IP-00 interfaces start
with 192.168.35.xx then the prefix is
192.168.35.0
Common for all WC-IP-01 ports → The 1 per cluster
first three octets of the WC-IP-00
IP and the 0 in the last octet for
example: if WC-IP-01 interfaces start
with 192.168.36.xx then the prefix is
192.168.36.0

48 Procedure

Page 53 of 120
Table 9. IIP WAN Configuration details (for mn-215) (continued)
Type or Port Description IPs required
Netmask Common for all WC-IP-00 Ports 1 per cluster
Common for all WC-IP-01 ports 1 per cluster
MTU Common for all WC-IP-00 Ports → N/A
Default 1500
Common for all WC-IP-00 Ports → N/A
Default 1500
WC-00 All WC-IP-00 IPs should be in the same 2 per cluster
vlan if vlans are present and reachable
through the gateway that is provided for
WC-IP-00 ports.
WC-01 All WC-IP-01 IPs should be in the same 2 per cluster
vlan if vlans are present and reachable
through the gateway that is provided for
WC-IP-01 ports.

Example
See the sample of WAN interface IPs in the following table:
Cluster-1

Table 10. Cluster 1 - WAN interface IPs

Type or Port Interface IP Address
Gateway WC-IP-00 ports '""
WC-IP-01 Ports '""
Prefix WC-IP-00 ports 192.x.x.x
WC-IP-01 Ports 192.x.x.x
Netmask WC-IP-00 ports 255.x.x.x
WC-IP-01 Ports 255.x.x.x
MTU WC-IP-00 ports 1500
WC-IP-01 Ports 1500
2-1-A WC-IP-00 ports 192.x.x.x
2-1-A WC-IP-01 Ports 192.x.x.x
2-1-B WC-IP-00 ports 192.x.x.x
2-1-B WC-IP-01 Ports 192.x.x.x

Cluster-2

Table 11. Cluster 2 - WAN interface IPs

Type or Port Interface IP Address
Gateway WC-IP-00 ports '""
WC-IP-01 Ports '""
Prefix WC-IP-00 ports 192.x.x.x
WC-IP-01 Ports 192.x.x.x
Netmask WC-IP-00 ports 255.x.x.x
WC-IP-01 Ports 255.x.x.x

Procedure 49

Page 54 of 120
Table 11. Cluster 2 - WAN interface IPs (continued)
Type or Port Interface IP Address
MTU WC-IP-00 ports 1500
WC-IP-01 Ports 1500
1-1-A WC-IP-00 ports 192.x.x.x
1-1-A WC-IP-01 Ports 192.x.x.x
1-1-B WC-IP-00 ports 192.x.x.x
1-1-B WC-IP-01 Ports 192.x.x.x

Similarly, the same set of details is required for other clusters.

Routed WAN network configuration process

WANCOM interview process is started...

Types of wan configurations supported.

1. Routed
2. Bridged
Please select your wan type: 1

Collecting the wan details for cluster-1

Collecting Gateway, subnet, MTU & prefix for WC-IP-00 ports at cluster-1
Enter Gateway IP(should be same for all WC-IP-00 of cluster-1) (default:
): 192.x.x.x
Enter prefix IP(should be same for all WC-IP-00 of cluster-1)(example:
192.168.35.0): 192.x.x.x
Enter netmask IP(should be same for all WC-IP-00 of cluster-1): 255.x.x.x
Enter MTU(should be same for all WC-IP-00 of cluster-1) (default: 1500):

Collecting Gateway, subnet, MTU & prefix for WC-IP-01 ports at cluster-1
Enter Gateway IP(should be same for all WC-IP-01 of cluster-1) (default:
): 192.x.x.x
Enter prefix IP(should be same for all WC-IP-01 of cluster-1)(example:
192.168.36.0): 192.x.x.x
Enter netmask IP(should be same for all WC-IP-01 of cluster-1): 255.x.x.x
Enter MTU(should be same for all WC-IP-01 of cluster-1) (default: 1500):

Collecting director-1-1-A details

Enter WC-IP-00 IP address: 192.x.x.x
Enter WC-IP-01 IP address: 192.x.x.x

Collecting director-1-1-B details

Enter WC-IP-00 IP address: 192.x.x.x
Enter WC-IP-01 IP address: 192.x.x.x

Collecting the wan details for cluster-2

Collecting Gateway, subnet, MTU & prefix for WC-IP-00 ports at cluster-2
Enter Gateway IP(should be same for all WC-IP-00 of cluster-2) (default:
): 192.168.156.1
Enter prefix IP(should be same for all WC-IP-00 of cluster-2)(example:
192.168.35.0): 192.168.156.0
Enter netmask IP(should be same for all WC-IP-00 of cluster-2):
255.255.255.0
Enter MTU(should be same for all WC-IP-00 of cluster-2) (default: 1500):

Collecting Gateway, subnet, MTU & prefix for WC-IP-01 ports at cluster-2
Enter Gateway IP(should be same for all WC-IP-01 of cluster-2) (default:
): 192.168.157.1
Enter prefix IP(should be same for all WC-IP-01 of cluster-2)(example:
192.168.36.0): 192.168.157.0
Enter netmask IP(should be same for all WC-IP-01 of cluster-2):
255.255.255.0
Enter MTU(should be same for all WC-IP-01 of cluster-2) (default: 1500):

Collecting director-2-1-A details

50 Procedure

Page 55 of 120
 Enter WC-IP-00 IP address: 192.x.x.x
Enter WC-IP-01 IP address: 192.x.x.x

Collecting director-2-1-B details

Enter WC-IP-00 IP address: 192.x.x.x
Enter WC-IP-01 IP address: 192.x.x.x

Please review the details entered.

wan_type: routed
name: cluster-1
wan-com:
WC-IP-00:
prefix: 192.x.x.x
gateway: 192.x.x.x
netmask: 255.x.x.x
mtu: 1500
WC-IP-01:
prefix: 192.x.x.x
gateway: 192.x.x.x
netmask: 255.x.x.x
mtu: 1500
nodes
8KC4Z23
interfaces:
WC-IP-00:
ip:
address: 192.x.x.x
WC-IP-01:
ip:
address: 192.x.x.x
8KC5Z23
interfaces:
WC-IP-00:
ip:
address: 192.x.x.x
WC-IP-01:
ip:
address: 192.x.x.x
name: cluster-2
wan-com:
WC-IP-00:
prefix: 192.x.x.x
gateway: 192.x.x.x
netmask: 255.x.x.x
mtu: 1500
WC-IP-01:
prefix: 192.x.x.x
gateway: 192.x.x.x
netmask: 255.x.x.x
mtu: 1500
nodes
8KC6Z23
interfaces:
WC-IP_00:
ip:
address: 192.x.x.x
WC-IP-01:
ip:
address: 192.x.x.x
8KCYY23
interfaces:
WC-IP-00:
ip:
address: 192.x.x.x
WC-IP-01:
ip:
address: 192.x.x.x

Please review the above details.

Do you want to proceed(y/n)? (default: y):

Procedure 51

Page 56 of 120
Bridged WAN
The following details are required:

Table 12. Bridged WAN

Type or Port Description IPs required
Gateway Common for all WC-IP- 00 Ports at both 1 per cluster
clusters→ It can be left blank if the IPs
provided are internal IP and no gateway
is required.
Common for all WC-IP-01 Ports at both 1 per cluster
clusters→ It can be left blank if the IPs
provided are internal IP and no gateway
is required.
Prefix Common for all WC-IP-00 Ports at both 1 per cluster
clusters → The first three octets of the
WC-IP-00 IP and the 0 in the last octet
for example: if WC-IP-00 interfaces start
with 192.168.35.xx then the prefix is
192.168.35.0
Common for all WC-IP-01 ports at both 1 per cluster
clusters → The first three octets of the
WC-IP-00 IP and the 0 in the last octet
for example: if WC-IP-01 interfaces start
with 192.168.36.xx then the prefix is
192.168.36.0
Netmask Common for all WC-IP-00 Ports 1 per cluster
Common for all WC-IP-01 ports 1 per cluster
MTU Common for all WC-IP-00 Ports → N/A
Default 1500
Common for all WC-IP-01 Ports → N/A
Default 1500
WC-IP-00 If VLANs are present and reachable 2 per cluster
through the gateway that is provided for
WC-00 ports, then all WC-00 IPs should
be in the same VLAN.
WC-IP-01 If VLANs are present and reachable 2 per cluster
through the gateway that is provided for
WC-IP-01 ports, then all WC-IP-01 IPs
should be in the same VLAN.

Example
See the sample of bridged network IPs for WAN interface in the following table:

Table 13. WAN interface IPs

Type or Port Interface IP Address
Gateway WC-IP-00 Ports '""
WC-IP-01 ports '""
Prefix WC-IP-00 Ports 192.168.35.0
WC-IP-01 ports 192.168.36.0
Netmask WC-IP-00 Ports 255.255.255.0
WC-IP-01 ports 255.255.255.0

52 Procedure

Page 57 of 120
Table 13. WAN interface IPs (continued)
Type or Port Interface IP Address
MTU WC-IP-00 Ports 1500
WC-IP-01 ports 1500
1-1-A WC-IP-00 192.168.54.35
1-1-A WC-IP-01 192.168.55.35
1-1-B WC-IP-00 192.168.54.36
1-1-B WC-IP-01 192.168.55.36
2-1-A WC-IP-00 192.168.54.67
2-1-A WC-IP-01 192.168.55.67
2-1-B WC-IP-00 192.168.54.68
2-1-B WC-IP-01 192.168.55.68

Example for bridged WAN network configuration process

Types of wan configurations supported.

1. Routed
2. Bridged
Please select your wan type: 2

Collecting the wan details for cluster-1

Collecting Gateway, subnet, MTU & prefix for WC-IP-00 ports at cluster-1
Enter prefix IP(should be same for all WC-IP-00 of cluster-1)(example:
192.168.35.0): 192.x.x.x
Enter netmask IP(should be same for all WC-IP-00 of cluster-1): 255.x.x.x
Enter MTU(should be same for all WC-IP-00 of cluster-1) (default: 1500):

Collecting Gateway, subnet, MTU & prefix for WC-IP-01 ports at cluster-1
Enter prefix IP(should be same for all WC-IP-01 of cluster-1)(example:
192.168.36.0): 192.x.x.x
Enter netmask IP(should be same for all WC-IP-01 of cluster-1): 255.x.x.x
Enter MTU(should be same for all WC-IP-01 of cluster-1) (default: 1500):

Collecting director-1-1-A details

Enter WC-IP-00 IP address: 192.x.x.x
Enter WC-IP-01 IP address: 192.x.x.x

Collecting director-1-1-B details

Enter WC-IP-00 IP address: 192.x.x.x
Enter WC-IP-01 IP address: 192.x.x.x

Collecting the wan details for cluster-2

Collecting Gateway, subnet, MTU & prefix for WC-IP-00 ports at cluster-2
Enter MTU(should be same for all WC-IP-00 of cluster-2) (default: 1500):

Collecting Gateway, subnet, MTU & prefix for WC-IP-01 ports at cluster-2
Enter MTU(should be same for all WC-IP-01 of cluster-2) (default: 1500):

Collecting director-2-1-A details

Enter WC-IP-00 IP address: 192.x.x.x
Enter WC-IP-01 IP address: 192.x.x.x

Collecting director-2-1-B details

Enter WC-IP-00 IP address: 192.x.x.x
Enter WC-IP-01 IP address: 192.x.x.x

Please review the details entered.

wan_type: bridged
name: cluster-1
wan-com:

Procedure 53

Page 58 of 120
 WC-IP-00:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
WC-IP-01:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
nodes
4GCK0R3
interfaces:
WC-IP-00:
ip:
address: 192.x.x.x
role: wan-com
WC-IP-01:
ip:
address: 192.x.x.x
role: wan-com
5GCK0R3
interfaces:
WC-IP-00:
ip:
address: 192.x.x.x
role: wan-com
WC-IP-01:
ip:
address: 192.x.x.x
role: wan-com
name: cluster-2
wan-com:
WC-IP-00:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
WC-IP-01:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
nodes
6GCK0R3
interfaces:
WC-IP-00:
ip:
address: 192.x.x.x
role: wan-com
WC-IP-01:
ip:
address: 192.x.x.x
role: wan-com
7GCK0R3
interfaces:
WC-IP-00:
ip:
address: 192.x.x.x
role: wan-com
WC-IP-01:
ip:
address: 192.x.x.x
role: wan-com

Please review the above details.

Do you want to proceed(y/n)? (default: y): y

54 Procedure

Page 59 of 120
Configuring SupportAssist
SupportAssist is the component on the metro node that is responsible for delivering CallHome, alerts, and telemetry to the
backend. SupportAssist must be configured for this communication to take place. SupportAssist can switch between enable and
disable states that are based on the inputs you provide.vplex_system_config -i --supportassist-config is the
main command for initiating the configuration.
The SupportAssist can be configured independently after system configuration. With SupportAssist, you can perform the
following operations:
1. Collect the SupportAssist details- vplex_system_config --interview --supportassist-config.
2. Show the SupportAssist details- vplex_system_config --interview --show-supportassist .
3. Apply the SupportAssist configuration- vplex_system_config --support-assist.
4. Enable the SupportAssist configuration- vplex_system_config --support-enable.
5. Disable the SupportAssist configuration- vplex_system_config --support-disable.
6. Reset the SupportAssist configuration- vplex_system_config --reset-supportassist.
7. Update the SupportAssist gateway- vplex_system_config --interview --update-supportassist-
gateway .
WARNING: Do not run the vplex_system_config --start or vplex_system_config -s command on an
already configured system, as it leads to the node firmware being taken down, and causes a Total Cluster
Outage.

Pre-requisite: Collect the SupportAssist configuration details

Checklist
The following values should be ready before performing the following next steps:
● Secure Connect Gateway v5.0 and later can used it configure SupportAssist.
● Access key and Pin. Contact Customer Support for further assistance Access Key Portal.
● Customer contact information
● If the user selects the useProxy and useGateway as false options while installing SupportAssist, then DNS configuration is
must.
● The Access key and Pin are only used once. In case, if the supportassist configuration is not successful after giving them,
then generate a new Access key and Pin. They are valid for 7 days.
NOTE: Run these commands in one node, and all the node will reflect the changes.

Step 1: Interview (SupportAssist configuration)

1. Run the command for the SupportAssist configuration:
a. service@director-1-1-a:~> vplex_system_config --interview --supportassist-config
Once this command runs, it displays the EULA agreement.

Step 2: Apply changes to SupportAssist configuration

1. Run the command to apply the SupportAssist configuration : vplex_system_config --support-assist
Once the command runs, the Apply phase for the SupportAssist configuration runs. It ensures that the SupportAssist
configuration completes successfully .

service@director-1-1-a:~> vplex_system_config --support-assist

Starting the system configuration process for SupportAssist tasks...
TASK: Gathering Facts - PASS
TASK: Restarting the vplex-ese service - PASS
TASK: Waiting for vplex-ese service to come up - PASS
TASK: Checking if the vplex-ese service is started - PASS
TASK: Restarting the vplex-supportassist service - PASS

Procedure 55

Page 60 of 120
 TASK: Waiting for vplex-supportassist service to come up - PASS
TASK: Checking if the vplex-supportassist service is started - PASS
TASK: Get Auth key - PASS
TASK: Check the target environment - PASS
TASK: Set target environment - PASS
TASK: command for stage client-id - PASS
TASK: Get the client-id - PASS
TASK: command for stage secret - PASS
TASK: Get the client secret - PASS
TASK: Get passphrase - PASS
TASK: Config API call - PASS
TASK: Getting the product version - PASS
TASK: Setting version value - PASS
TASK: Get Auth key - PASS
TASK: Config API with given data - PASS
TASK: Restarting the vplex-supportassist service - PASS
TASK: Waiting for vplex-supportassist service to come up - PASS
TASK: Checking if the vplex-supportassist service is started - PASS
TASK: Get Auth key - PASS
TASK: Disable backend connection - PASS
TASK: Get Auth key - PASS
TASK: Check the target environment - PASS
TASK: Set target environment - PASS
TASK: command for stage client-id - PASS
TASK: Get the client-id - PASS
TASK: command for stage secret - PASS
TASK: Get the client secret - PASS
TASK: Reading Authentication file - PASS
TASK: Reading acceskey and pin - PASS
TASK: Add clientId and secret to dict - PASS
TASK: getUniversalKey api call - PASS
TASK: deleting auth file from ansible - PASS
TASK: reset flag is false - PASS
TASK: Waiting for seconds after authentication - PASS
TASK: Get Auth key - PASS
TASK: Enable backend connection - PASS
TASK: Get Auth key - PASS
TASK: Connectivity api call - PASS
TASK: Reading connectivity output json - PASS
TASK: Reading status - PASS
TASK: Setting connectivity status value - PASS
TASK: Enable Remote Support - PASS
TASK: Enable RSC - PASS
TASK: Restarting the vplex-supportassist service - PASS
TASK: Waiting for vplex-supportassist service to come up - PASS
TASK: Checking if the vplex-supportassist service is started - PASS
TASK: Get Auth key - PASS
TASK: cfg_supportassist : debug - PASS
TASK: Payload api call - PASS
TASK: cfg_supportassist : debug - PASS

PLAY RECAP
*****************************************************************************************
****************************************************************
director-1-1-A|GMHN753 : ok=71 changed=5 unreachable=0 failed=0 skipped=129 rescued=0
ignored=0
director-1-1-B|GMFS753 : ok=71 changed=4 unreachable=0 failed=0 skipped=129 rescued=0
ignored=0
director-2-1-A|GMFV753 : ok=71 changed=4 unreachable=0 failed=0 skipped=129 rescued=0
ignored=0
director-2-1-B|GMHX753 : ok=71 changed=4 unreachable=0 failed=0 skipped=129 rescued=0
ignored=0

System configuration process for support assist configuration is successful

56 Procedure

Page 61 of 120
More SupportAssist Commands

View SupportAssist configuration details

1. View the SupportAssist configuration details that you have configured at any point by running the following command:
vplex_system_config --interview --show-supportassist

service@director-1-1-a:~> vplex_system_config --interview --show-supportassist

SupportAssist details for cluster-1

gateway_endpoints: [{'gatewayip': '10.228.67.5', 'gatewayport': '9443'}]

primary_contact:
email : [email protected]
first_name : john
language : English
last_name : doe
phone : +19876543210
remotesupport: True
secondary_contact:
email : [email protected]
first_name : joe
language : English
last_name : alex
phone : +18976543219
usegateways: True
useproxy: False
usessl: True

SupportAssist details for cluster-2

gateway_endpoints: [{'gatewayip': '10.228.67.5', 'gatewayport': '9443'}]

primary_contact:
email : [email protected]
first_name : john
language : English
last_name : doe
phone : +19876543210
remotesupport: True
secondary_contact:
email : [email protected]
first_name : joe
language : English
last_name : alex
phone : +18976543219
usegateways: True
useproxy: False
usessl: True

service@director-1-1-a:~>

Enable SupportAssist Configuration

1. Run the command to enable the SupportAssist configuration details : vplex_system_config --support-enable

NOTE: Skip this step if support assist is already configured, as this is to test enable/disable supportassist.

service@director-1-1-a:~> vplex_system_config --support-enable

SupportAssist task to enable service...
TASK: Gathering Facts - PASS
TASK: Get Auth key - PASS
TASK: Enable backend connection - PASS
TASK: Get Auth key - PASS
TASK: Connectivity api call - PASS

Procedure 57

Page 62 of 120
 TASK: Reading connectivity output json - PASS
TASK: Reading status - PASS
TASK: Setting connectivity status value - PASS
TASK: Enable Remote Support - PASS
TASK: Enable RSC - PASS

PLAY RECAP
**************************************************************************************
*******************************************************************
director-1-1-A|GMHN753 : ok=14 changed=0 unreachable=0 failed=0 skipped=11 rescued=0
ignored=0
director-1-1-B|GMFS753 : ok=14 changed=0 unreachable=0 failed=0 skipped=11 rescued=0
ignored=0
director-2-1-A|GMFV753 : ok=14 changed=0 unreachable=0 failed=0 skipped=11 rescued=0
ignored=0
director-2-1-B|GMHX753 : ok=14 changed=0 unreachable=0 failed=0 skipped=11 rescued=0
ignored=0

System configuration process for support assist enable is successful

Disable SupportAssist Configuration

1. Run the command to disable the SupportAssist configuration : vplex_system_config --support-disable.

NOTE: Skip this step if supportassist is already configured, as this is to test enable/disable supportassist.

service@director-1-1-a:~> vplex_system_config --support-disable

SupportAssist task to disable service...
TASK: Gathering Facts - PASS
TASK: Get Auth key - PASS
TASK: Disable backend connection - PASS

PLAY RECAP
**************************************************************************************
************************************************************
director-1-1-A|8K63Z23 : ok=5 changed=0 unreachable=0 failed=0
skipped=12 rescued=0 ignored=0
director-1-1-B|8K64Z23 : ok=5 changed=0 unreachable=0 failed=0
skipped=12 rescued=0 ignored=0
director-2-1-A|8K65Z23 : ok=5 changed=0 unreachable=0 failed=0
skipped=12 rescued=0 ignored=0
director-2-1-B|8K66Z23 : ok=5 changed=0 unreachable=0 failed=0
skipped=12 rescued=0 ignored=0

System configuration process for support assist disable is successful

service@director-1-1-a:~>

Reset SupportAssist configuration

NOTE: Skip this step if you want to configure supportassist.

1. Run the command to rest the SupportAssist configuration details : vplex_system_config --reset-supportassist.

Update SupportAssist configurations

NOTE:
● If you set the remote support to disable, then Dell cannot dial in.
● Skip this step during initial configuration. This is to update the gateway details which are already configured.
● If the user wants to update with useProxy: False and usegateways: False, then first configure DNS. Follow
the DNS Configuration, else the user finds a message:

58 Procedure

Page 63 of 120
 DNS is not configured. Please complete DNS configuration [vplex_system_config
-interview --dns-config] and
re-run current command.

service@director-1-1-a:~> vplex_system_config -interview --update-supportassist-

gateway

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.

Update SupportAssist Gateway process is started...

Enter SupportAssist details for cluster-1

Enter (true/false) for UseGateways (default: True):
Gateway IP (default: 10.228.67.74):
Gateway Port (default: 9443):
Do you want to give another Gateway End point (default: n):
Enter SupportAssist details for cluster-2
Enter (true/false) for UseGateways (default: True):
Gateway IP (default: 10.228.67.74):
Gateway Port (default: 9443):
Do you want to give another Gateway End point (default: n):

Update SUPPORTASSIST Gateway process is completed.

To start the supportassist configuration, run the command "vplex_system_config --

supportassist-gateway".

service@director-1-1-a:~> vplex_system_config --supportassist-gateway

Starting the system configuration process for SupportAssist tasks with
authentication...
TASK: Gathering Facts - PASS
TASK: Restarting the vplex-ese service - PASS
TASK: Waiting for vplex-ese service to come up - PASS
.
.
.
TASK: Reading connectivity output json - PASS
TASK: Reading status - PASS
TASK: Setting connectivity status value - PASS

PLAY RECAP
**************************************************************************************
************************************************************
director-1-1-A|8K63Z23 : ok=37 changed=4 unreachable=0 failed=0
skipped=82 rescued=0 ignored=0
director-1-1-B|8K64Z23 : ok=37 changed=4 unreachable=0 failed=0
skipped=82 rescued=0 ignored=0
director-2-1-A|8K65Z23 : ok=37 changed=4 unreachable=0 failed=0
skipped=82 rescued=0 ignored=0
director-2-1-B|8K66Z23 : ok=37 changed=4 unreachable=0 failed=0
skipped=82 rescued=0 ignored=0

System configuration process for support assist gateway configuration is successful

service@director-1-1-a:~>

1. Run the command to update the SupportAssist configuration : vplex_system_config -interview --update-
supportassist-gateway.

Configure the SMTP

Simple Mail Transfer Protocol is an Internet standard for mail transmission across IP networks that are typically only used for
sending messages to a mail server for relaying.
WARNING: Running the vplex_system_config --start or vplex_system_config -s command on an
already configured system stops the node firmware, causing a Total Cluster Outage.

Procedure 59

Page 64 of 120
An SMTP server is a system or an application that is responsible for sending mails. SMTP server receives mails from the email
client. It then passes it on to another SMTP email server and relays them to the incoming mail server. Metro node needs an
SMTP server IP (which must be provided during SMTP configuration), in order to send Metro node alert mails. This command
allows you to change or update the SMTP configuration of the current cluster.
● --smtp-config - Command starts performing SMTP configuration.
● --reset-smtp - Command starts performing reset of SMTP configuration.
NOTE:
● Changing the SMTP should be done in a configured metro node, not in an unconfigured metro node. SMTP configuration
is optional. On configuration of SMTP, whenever events occur, then you receive a mail notification. Presently, SMTP
IPv4 addresses are supported. Dell Technologies recommends the distribution of connections over multiple SMTP
servers for better availability.
● Check with the Metro node administrator for the service password as it would have been changed during installation and
might have changed further after.
● Run this command in one node, and the changes are reflected in all the node.
1. Log in as the service user with the credentials in one of the nodes of the metro node.
2. Run the command with the following options to show and update the SMTP configuration:
a. To show the SMTP configuration on the Metro node, run the following command: vplex_system_config -i --show-
smtp-config

service@director-1-1-b:~> vplex_system_config -i --show-smtp-config

SMTP config...
cluster: cluster-1

primary_connection: 10.x.x.x
failover_connection: 10.x.x.x
primary_email: [email protected]
secondary_email: [email protected]

cluster: cluster-2

primary_connection: 10.x.x.x
failover_connection: 10.x.x.x
primary_email: [email protected]
secondary_email: [email protected]

SHOW SMTP config is completed.

service@director-1-1-b:~>

b. To update the SMTP configuration on the Metro node, run the following command: vplex_system_config --smtp-
config

service@director-1-1-a:~> vplex_system_config --smtp-config

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.
SMTP interview process is started...

Below are the options to configure SMTP configuration for the clusters:
1. test-cluster1 only
2. test-cluster2 only
3. Both clusters have same SMTP config
4. Both clusters have different SMTP config
Please select option: 4
Enter 'test-cluster1' details:
Enter the SMTP IPv4 address (Ex:192.168.10.1) or fqdn (Ex:smtp.fqdn.com)
for primary connection: 10.x.x.x
Enter the SMTP IPv4 address (Ex:192.168.10.1) or fqdn (Ex:smtp.fqdn.com)
for failover connection: 10.x.x.x
Enter the recipient email address Ex:[email protected]:
[email protected]
Enter additional recipient email address Ex:[email protected]:
[email protected]

60 Procedure

Page 65 of 120
 Enter 'test-cluster2' details:
Enter the SMTP IPv4 address (Ex:192.168.10.1) or fqdn (Ex:smtp.fqdn.com)
for primary connection: smtp-outbound-pc1.dell.com
Enter the SMTP IPv4 address (Ex:192.168.10.1) or fqdn (Ex:smtp.fqdn.com)
for failover connection: smtp-outbound-pc1.dell.com
Enter the recipient email address Ex:[email protected]:
[email protected]
Enter additional recipient email address Ex:[email protected]:
[email protected]

Please review the SMTP details entered.

primary_connection: 10.x.x.x
failover_connection: 10.x.x.x
primary_email: [email protected]
secondary_email: [email protected]
primary_connection: smtp-outbound-pc1.dell.com
failover_connection: smtp-outbound-pc1.dell.com
primary_email: [email protected]
secondary_email: [email protected]
Please review the above details. Do you want to proceed(y/n)? (default: y):

SMTP interview process is completed.

TASK: Gathering Facts - PASS
TASK: Restarting the notifications service - PASS
TASK: Checking if the notifications service is started - PASS

PLAY RECAP
************************************************************************************
**************************************************************
director-1-1-A|8K13Z23 : ok=3 changed=1 unreachable=0 failed=0
skipped=9 rescued=0 ignored=0
director-1-1-B|8K12Z23 : ok=3 changed=1 unreachable=0 failed=0
skipped=9 rescued=0 ignored=0
director-2-1-A|8K15Z23 : ok=3 changed=1 unreachable=0 failed=0
skipped=9 rescued=0 ignored=0
director-2-1-B|8K10Z23 : ok=3 changed=1 unreachable=0 failed=0
skipped=9 rescued=0 ignored=0

System configuration process for SMTP configuration is successful

service@director-1-1-a:~

c. After you update the SMTP configuration on the Metro node, run the following command: vplex_system_config -i
--show-smtp-config

service@director-1-1-b:~> vplex_system_config -i --show-smtp-config

SMTP config...
cluster: cluster-1

primary_connection: 10.x.x.x
failover_connection: 10.x.x.x
primary_email: [email protected]
secondary_email: [email protected]

cluster: cluster-2

primary_connection: 10.x.x.x
failover_connection: 10.x.x.x
primary_email: [email protected]
secondary_email: [email protected]

SHOW SMTP config is completed.

service@director-1-1-b:~>

Procedure 61

Page 66 of 120
Change SMTP
To change SMTP, follow the below steps:
1. To reset the SMTP configuration on the Metro node, run the following command: service@director-1-1-b:~>
vplex_system_config --reset-smtp

NOTE: When you run the vplex_system_config --reset-smtp command, the specified primary and secondary
mail recipients no longer receive mail alerts in the Metro node.

service@director-1-1-a:~> vplex_system_config --reset-smtp

WARNING !!!
Running this command will reset the smtp parameters from the metro node. Do you really want to continue?
Please type 'yes' to proceed or 'no' to exit:
yes
Starting the system configuration process for reset smtp tasks...

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.
Reseting SMTP configurations...
Removed SMTP configurtions
Removed SMTP configurtions

TASK: Gathering Facts - PASS

TASK: Restarting the notifications service - PASS
TASK: Checking if the notifications service is started - PASS

PLAY RECAP
**************************************************************************************
************************************************************
director-1-1-A|8K13Z23 : ok=3 changed=1 unreachable=0 failed=0
skipped=9 rescued=0 ignored=0
director-1-1-B|8K12Z23 : ok=3 changed=1 unreachable=0 failed=0
skipped=9 rescued=0 ignored=0
director-2-1-A|8K15Z23 : ok=3 changed=1 unreachable=0 failed=0
skipped=9 rescued=0 ignored=0
director-2-1-B|8K10Z23 : ok=3 changed=1 unreachable=0 failed=0
skipped=9 rescued=0 ignored=0

System configuration process for reset SMTP configuration is successful

service@director-1-1-a:~>

2. If you want to reconfigure SMTP, repeat step 2b above.

62 Procedure

Page 67 of 120
 4
Reconfigure Specific Parameters
WARNING: Running the vplex_system_config --start or vplex_system_config -s command on an
already configured system stops the node firmware, causing a Total Cluster Outage.

NOTE: Any reconfiguration options (update password, NTP, and so on) must be performed only after the system
configuration has been completed successfully. It ensures that the changes are reflected on all nodes.

Topics:
• Introduction
• Help Command
• Change the NTP server IP
• Change the WAN COM
• Change the Public IP/EC-01 Address of the director
• Change the name of the cluster
• View the SCIF content
• Change the login banner
• Retrieve the iDRAC password
• Change the service user password
• Change the SSL certificates for self_signed
• Change the SSL certificate for cust_signed
• Reset SSL Certificates
• Renew self-signed SSL certificates
• Enabling and disabling of metro node ports
• Configure or change the LDAP or AD
• Configure or change SSH Keys

Introduction
Any forced termination of the system-configuration process may result in the retention of a stale SCIF lock file on the system.
This lock file prevents any additional system-configuration operations. To handle this situation, see the Troubleshooting guide for
metro node. To prevent leaving a stale SCIF lock file on the system, the system:
● Do not reboot any node while a system-configuration operation is in progress.
● Do not kill a vplex_system_config process (for example, kill -9 <pid_of_vplex_system_config>).
● To connect to the system, enable SSH keepalive heartbeats in the SSH client.
● Avoid circumstance that may cause a disruption in the network connectivity to the metro node while system-configuration
operations are in progress, such as unreliable WiFi.
This segment describes how a user can change any specific configuration parameter with the following options:

Help Command
This command provides the information about the commands available to configure a certain configuration parameter using the
arguments.

service@director-1-1-a:~> vplex_system_config -i --help

usage: system_config_collect.py [-h] [--wancom] [--local-to-metro]
[--show-ntp] [--update-ntp] [--show-ec01-ip]
[--update-peer-ec01-ip]
[--supportassist-config]
[--supportassist-with-accesskey]

Reconfigure Specific Parameters 63

Page 68 of 120
 [--show-idrac-password]
[--show-ssl-certificates]
[--update-ssl-certificates]
[--show-smtp-config] [--ldap-config]
[--show-ldap-config] [--reset-ldap-config]
[--add-users-ldap-config]
[--update-ldap-certs]
[--remove-users-ldap-config]
[--add-groups-ldap-config]
[--remove-groups-ldap-config] [--logging-vol]
[--show-cluster-name] [--update-cluster-name]
[--update-service-password]
[--skip-service-password]
[--update-local-service-password]
[--update-supportassist-gateway]
[--show-supportassist] [--show]
[--universalkeyapi]
[--update-supportassist-contact]
[--dns-config] [--show-dns]
[--metadata-backup-create]

optional arguments:
-h, --help show this help message and exit
--wancom, --WANCOM Use this command to configure wancom
--local-to-metro, --LOCAL-TO-METRO
Use this command to convert local to metro
--show-ntp, --SHOW-NTP
Use this command to show ntp
--update-ntp, --UPDATE-NTP
Use this command to update ntp
--show-ec01-ip, --SHOW-EC01-IP
Use this command to show EC01 ip
--update-peer-ec01-ip, --UPDATE-PEER-EC01-IP
Use this command to update peer EC01 ip
--supportassist-config, --SUPPORTASSIST-CONFIG
Use this command to configure SupportAssist
--supportassist-with-accesskey, --SUPPORTASSIST-WITH-ACCESSKEY
Use this command to configure SupportAssist
--show-idrac-password, --SHOW-IDRAC-PASSWORD, --show-idrac-pwd, --SHOW-IDRAC-PWD
Use this command to show idrac password
--show-ssl-certificates, --show-ssl-certs, --SHOW-SSL-CERTIFICATES, --SHOW-SSL-CERTS
Use this command to show ssl-certificates
--update-ssl-certificates, --update-ssl-certs, --UPDATE-SSL-CERTIFICATES, --UPDATE-SSL-
CERTS
Use this command to update ssl-certificates
--show-smtp-config, --SHOW-SMTP-CONFIG
Use this command to show SMTP config
--ldap-config, --LDAP-CONFIG
Use this command to configure LDAP/AD
--show-ldap-config, --SHOW-LDAP-CONFIG
Use this command to show LDAP/AD config
--reset-ldap-config, --RESET-LDAP-CONFIG
Use this command to reset LDAP/AD config
--add-users-ldap-config, --ADD-USERS-LDAP-CONFIG
Use this command to add users in LDAP/AD config
--update-ldap-certs, --UPDATE-LDAP-CERTS
Use this command to update LDAP/AD certificates
--remove-users-ldap-config, --REMOVE-USERS-LDAP-CONFIG
Use this command to remove users from LDAP/AD config
--add-groups-ldap-config, --ADD-GROUPS-LDAP-CONFIG
Use this command to add users in LDAP/AD config
--remove-groups-ldap-config, --REMOVE-GROUPS-LDAP-CONFIG
Use this command to remove users from LDAP/AD config
--logging-vol, --LOGGING-VOL, --logging-volume, --LOGGING-VOLUME
Use this command to create logging volume
--show-cluster-name, --SHOW-CLUSTER-NAME
Use this command to show cluster name
--update-cluster-name, --UPDATE-CLUSTER-NAME
Use this command to update cluster name
--update-service-password, --UPDATE-SERVICE-PASSWORD
Use this command to update service user password
--skip-service-password, --SKIP-SERVICE-PASSWORD
Use this command to skip the service user password

64 Reconfigure Specific Parameters

Page 69 of 120
 change
--update-local-service-password, --UPDATE-LOCAL-SERVICE-PASSWORD
Use this command to update service user password in
the local node
--update-supportassist-gateway, --UPDATE-SUPPORTASSIST-GATEWAY
Use this command to update SupportAssist gateway
endpoints
--show-supportassist, --SHOW-SUPPORTASSIST
Use this command to show SupportAssist details
--show, --SHOW Use this command to check SCIF content
--universalkeyapi, --UNIVERSALKEYAPI
Use this command to call universal key API
--update-supportassist-contact, --UPDATE-SUPPORTASSIST-CONTACT
Use this command to update SupportAssist Contact
Details
--dns-config, --DNS-CONFIG
Use this command to configure DNS
--show-dns, --SHOW-DNS
Use this command to show DNS config
--metadata-backup-create, --METADATA-BACKUP-CREATE
Use this command to create metadata backup
service@director-1-1-a:~>

Change the NTP server IP

It includes iDRAC NTP.
To change or update the node NTP and iDRAC NTP server details, see the following steps:
WARNING: Running the vplex_system_config --start or vplex_system_config -s command on an
already configured system stops the node firmware, causing a Total Cluster Outage.
1. Log in as a service user with the credentials in one of the nodes of the metro node.
2. Run the command with the following options for show and update NTP server ( updates SCIF and run the playbook with
NTP):
a. service@director-1-1-a:~> vplex_system_config -i --show-ntp

service@director-1-1-a:~> vplex_system_config -i --show-ntp

NTP server 1 address: 10.106.16.22

NTP server 2 address: 10.106.16.23

service@director-1-1-a:~>

b. service@director-1-1-a:~> vplex_system_config -i --update-ntp

service@director-1-1-a:~> vplex_system_config -i --update-ntp

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.

Update NTP process is started...

Enter NTP server 1 address (default: 127.0.0.1):
Enter NTP server 2 address (default: ):
TASK: Gathering Facts - PASS
TASK: Copying the ntp configuration file to the node-1-1-A - PASS
TASK: Copying the ntp configuration file to the node - PASS
.
.
.
TASK: Verifying NTP sync - PASS
TASK: Get iDRAC password - PASS
TASK: Setting iDRAC NTP server - PASS

PLAY RECAP
************************************************************************************
************************************************************************************
director-1-1-A|8K13Z23 : ok=14 changed=2 unreachable=0 failed=0

Reconfigure Specific Parameters 65

Page 70 of 120
 skipped=3 rescued=0 ignored=0
director-1-1-B|8K12Z23 : ok=15 changed=2 unreachable=0 failed=0
skipped=3 rescued=0 ignored=0
director-2-1-A|8K15Z23 : ok=14 changed=2 unreachable=0 failed=0
skipped=3 rescued=0 ignored=0
director-2-1-B|8K10Z23 : ok=14 changed=2 unreachable=0 failed=0
skipped=3 rescued=0 ignored=0

System configuration process for update NTP is successful

service@director-1-1-a:~>

c. service@director-1-1-a : ~ > vplex_system_config -i --show-ntp

service@director-1-1-a:~> vplex_system_config -i --show-ntp

NTP server 1 address: 10.106.16.22

NTP server 2 address: 10.106.16.23

service@director-1-1-a:~>

Change the WAN COM

WARNING: Running the vplex_system_config --start or vplex_system_config -s command on an
already configured system stops the node firmware, causing a Total Cluster Outage.

Reconfigure WAN COM

NOTE:
● WANCOM reconfiguration is performed per port group. For example, whenever you perform WC-00 reconfiguration, it
does not affect the WC-01 port configuration, and conversely.
● The following examples show the reconfiguration commands on mn-114. The same commands can be applied on mn-215,
but the port names on WANCOM are as WC-IP-00/01 on mn-215.
Help command:

service@director-1-1-a:~> vplex_system_config -i --wancom --help

usage: vplex_system_config -i --wancom [-h] --port {WC-00,WC-01}

This command is used to run the interview for wancom reconfigurarion per port.
For ex. vplex_system_config -i --wancom --port WC-00

optional arguments:
-h, --help show this help message and exit
--port {WC-00,WC-01} Port to reconfiugre.

To reconfigure the WC-00 port, run the following commands:

1. vplex_wan_reconfig -i WC-00
2. vplex_wan_reconfig -a WC-00
NOTE: Default values come from the existing configuration.

vplex_wan_reconfig -i WC-00

service@director-1-1-a:~> vplex_system_config -i --wancom --port WC-00

Checking the alternate port group WC-01 connectivity status to make sure we have wan com
availability during reconfiguration...
WC-01 connectivity status is OK.

WARNING !!!
Running this command will reconfigure WC-00 ports in the metro node. WC-00 ports will be
rebooted in all the nodes. Do you really want to continue?
Please type 'yes' to continue or 'no' to exit:
yes

66 Reconfigure Specific Parameters

Page 71 of 120
Setting port WC-00 to disabled on ['director-1-1-B', 'director-1-1-A', 'director-2-1-B',
'director-2-1-A'], updating SCIF on ['director-1-1-B', 'director-1-1-A', 'director-2-1-
B', 'director-2-1-A']

Setting port WC-00 to disabled on director-1-1-B

Setting port WC-00 to disabled on director-1-1-A
Setting port WC-00 to disabled on director-2-1-B
Setting port WC-00 to disabled on director-2-1-A

Validating WC-00 port status on all directors...

WC-00 ports are disabled on all directors.

WC-00 interface status on director-1-1-B :

WC-00 interface status on director-1-1-A :
WC-00 interface status on director-2-1-B :
WC-00 interface status on director-2-1-A :

Types of wan configurations supported.

1. Routed
2. Bridged
Please select your wan type (default: 2):

Collecting the wan details for cluster-1

Collecting Gateway, subnet, MTU & prefix for WC-00 ports at cluster-1
Enter prefix IP(should be same for all WC-00 of cluster-1)(example:
192.168.35.0) (default: 192.x.x.x):
Enter netmask IP(should be same for all WC-00 of cluster-1) (default:
255.x.x.x):
Enter MTU(should be same for all WC-00 of cluster-1) (default: 1500):

Collecting director-1-1-A details

Enter WC-00 IP address (default: 192.x.x.x):

Collecting director-1-1-B details

Enter WC-00 IP address (default: 192.x.x.x):

Collecting the wan details for cluster-2

Collecting Gateway, subnet, MTU & prefix for WC-00 ports at cluster-2
Enter MTU(should be same for all WC-00 of cluster-2) (default: 1500):

Collecting director-2-1-A details

Enter WC-00 IP address (default: 192.x.x.x):

Collecting director-2-1-B details

Enter WC-00 IP address (default: 192.x.x.x):

Please review the details entered.

wan_type: bridged
name: cluster-1
wan-com:
WC-00:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
WC-01:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
nodes
8K14Z23
interfaces:
WC-00:
ip:

Reconfigure Specific Parameters 67

Page 72 of 120
 address: 192.x.x.x
role: wan-com
WC-01:
ip:
address: 192.x.x.x
role: wan-com
8KJ0Z23
interfaces:
WC-00:
ip:
address: 192.x.x.x
role: wan-com
WC-01:
ip:
address: 192.x.x.x
role: wan-com
name: cluster-2
wan-com:
WC-00:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
WC-01:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
nodes
8K11Z23
interfaces:
WC-00:
ip:
address: 192.x.x.x
role: wan-com
WC-01:
ip:
address: 192.x.x.x
role: wan-com
8K17Z23
interfaces:
WC-00:
ip:
address: 192.x.x.x
role: wan-com
WC-01:
ip:
address: 192.x.x.x
role: wan-com

Please review the above details.

Do you want to proceed(y/n)? (default: y):

To apply the WC-00 port configuration, run the command 'vplex_system_config --wancom --
port WC-00'.
service@director-1-1-a:~>

vplex_wan_reconfig -a WC-00

service@director-1-1-a:~> vplex_system_config --wancom --port WC-00

Starting the system configuration process for wancom tasks...

Checking the alternate port group WC-01 connectivity status to make sure we have wan com
availability during reconfiguration...
WC-01 connectivity status is OK.
TASK: Gathering Facts - PASS
TASK: Setting the ip for wan com ports - PASS
TASK: Setting the netmask for wan com ports - PASS
.
.
.
TASK: Waiting for 10 seconds before checking the port status - PASS

68 Reconfigure Specific Parameters

Page 73 of 120
 TASK: Enabling the {{ port_role }} ports - PASS
Pausing for 5 seconds
(ctrl+C then 'C' = continue early, ctrl+C then 'A' = abort)
TASK: Verifying the {{ port_role }} ports status - PASS

PLAY RECAP
*****************************************************************************************
**********************************************************
director-1-1-A|8KJ0Z23 : ok=18 changed=2 unreachable=0 failed=0
skipped=8 rescued=0 ignored=0
director-1-1-B|8K14Z23 : ok=12 changed=2 unreachable=0 failed=0
skipped=15 rescued=0 ignored=0
director-2-1-A|8K17Z23 : ok=12 changed=2 unreachable=0 failed=0
skipped=14 rescued=0 ignored=0
director-2-1-B|8K11Z23 : ok=11 changed=2 unreachable=0 failed=0
skipped=15 rescued=0 ignored=0

System configuration process for WAN reconfiguration is successful

Checking WC-00 connectivity status...
WC-00 connectivity is OK.
service@director-1-1-a:~>

To reconfigure the WC-01 port, run the following commands:

1. vplex_wan_reconfig -i WC-01
2. vplex_wan_reconfig -a WC-01
NOTE: Default values come from the existing configuration.

vplex_wan_reconfig -i WC-01

service@director-1-1-a:~> vplex_system_config -i --wancom --port WC-01

Checking the alternate port group WC-00 connectivity status to make sure we have wan com
availability during reconfiguration...
WC-00 connectivity status is OK.

WARNING !!!
Running this command will reconfigure WC-01 ports in the metro node. WC-01 ports will be
rebooted in all the nodes. Do you really want to continue?
Please type 'yes' to continue or 'no' to exit:
yes

Setting port WC-01 to disabled on ['director-1-1-B', 'director-1-1-A', 'director-2-1-B',

'director-2-1-A'], updating SCIF on ['director-1-1-B', 'director-1-1-A', 'director-2-1-
B', 'director-2-1-A']

Setting port WC-01 to disabled on director-1-1-B

Setting port WC-01 to disabled on director-1-1-A
Setting port WC-01 to disabled on director-2-1-B
Setting port WC-01 to disabled on director-2-1-A

Validating WC-01 port status on all directors...

WC-01 ports are disabled on all directors.

WC-01 interface status on director-1-1-B :

WC-01 interface status on director-1-1-A :
WC-01 interface status on director-2-1-B :
WC-01 interface status on director-2-1-A :

Types of wan configurations supported.

1. Routed
2. Bridged
Please select your wan type (default: 2):

Collecting the wan details for cluster-1

Collecting Gateway, subnet, MTU & prefix for WC-01 ports at cluster-1
Enter prefix IP(should be same for all WC-01 of cluster-1)(example:

Reconfigure Specific Parameters 69

Page 74 of 120
 192.168.36.0) (default: 192.x.x.x):
Enter netmask IP(should be same for all WC-01 of cluster-1) (default:
255.x.x.x):
Enter MTU(should be same for all WC-01 of cluster-1) (default: 1500):

Collecting director-1-1-A details

Enter WC-01 IP address (default: 192.x.x.x):

Collecting director-1-1-B details

Enter WC-01 IP address (default: 192.x.x.x):

Collecting the wan details for cluster-2

Collecting Gateway, subnet, MTU & prefix for WC-01 ports at cluster-2
Enter MTU(should be same for all WC-01 of cluster-2) (default: 1500):

Collecting director-2-1-A details

Enter WC-01 IP address (default: 192.x.x.x):

Collecting director-2-1-B details

Enter WC-01 IP address (default: 192.x.x.x):

Please review the details entered.

wan_type: bridged
name: cluster-1
wan-com:
WC-00:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
WC-01:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
nodes
8K14Z23
interfaces:
WC-00:
ip:
address: 192.x.x.x
role: wan-com
WC-01:
ip:
address: 192.x.x.x
role: wan-com
8KJ0Z23
interfaces:
WC-00:
ip:
address: 192.x.x.x
role: wan-com
WC-01:
ip:
address: 192.x.x.x
role: wan-com
name: cluster-2
wan-com:
WC-00:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
WC-01:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
nodes
8K11Z23
interfaces:

70 Reconfigure Specific Parameters

Page 75 of 120
 WC-00:
ip:
address: 192.x.x.x
role: wan-com
WC-01:
ip:
address: 192.x.x.x
role: wan-com
8K17Z23
interfaces:
WC-00:
ip:
address: 192.x.x.x
role: wan-com
WC-01:
ip:
address: 192.x.x.x
role: wan-com

Please review the above details.

Do you want to proceed(y/n)? (default: y):

To apply the WC-01 port configuration, run the command 'vplex_system_config --wancom --
port WC-01'.
service@director-1-1-a:~>

vplex_wan_reconfig -a WC-01

service@director-1-1-a:~> vplex_system_config --wancom --port WC-01

Starting the system configuration process for wancom tasks...

Checking the alternate port group WC-00 connectivity status to make sure we have wan com
availability during reconfiguration...
WC-00 connectivity status is OK.
TASK: Gathering Facts - PASS
TASK: Setting the ip for wan com ports - PASS
TASK: Setting the netmask for wan com ports - PASS
TASK: Setting the mtu for wan com ports - PASS
.
.
.
TASK: Enabling the {{ port_role }} ports - PASS
Pausing for 5 seconds
(ctrl+C then 'C' = continue early, ctrl+C then 'A' = abort)
TASK: Verifying the {{ port_role }} ports status - PASS

PLAY RECAP
*****************************************************************************************
**********************************************************
director-1-1-A|8KJ0Z23 : ok=18 changed=2 unreachable=0 failed=0
skipped=8 rescued=0 ignored=0
director-1-1-B|8K14Z23 : ok=12 changed=2 unreachable=0 failed=0
skipped=15 rescued=0 ignored=0
director-2-1-A|8K17Z23 : ok=12 changed=2 unreachable=0 failed=0
skipped=14 rescued=0 ignored=0
director-2-1-B|8K11Z23 : ok=11 changed=2 unreachable=0 failed=0
skipped=15 rescued=0 ignored=0

System configuration process for WAN reconfiguration is successful

Checking WC-01 connectivity status...
WC-01 connectivity is OK.
service@director-1-1-a:~>

Topology change (Applicable only for mn-215)

WARNING: During Topology change, there is a full WANCOM reset, which results in a wan outage until the
WANCOM is configured back with the new topology.

Reconfigure Specific Parameters 71

Page 76 of 120
If the user wants to change the WAN topology that is either convert from WAN IP to WAN FC or conversely, it resets the
WANCOM and reconfigures using new topology.

Change the topology from WANCOM IP to WANCOM FC:

The following commands are used to change the WAN topology:
● vplex_system_config --reset-wancom
● vplex_system_config -i --wancom
● vplex_system_config --wancom
vplex_system_config --reset-wancom

service@director-1-1-a:~> vplex_system_config --reset-wancom

WARNING !!!
Running this command will reset the wancom parameters from the metro node. Do you really
want to continue?
Please type 'yes' to proceed or 'no' to exit:
yes
Starting the system configuration process for reset wancom tasks...
TASK: Resetting wan-com ports - PASS
TASK: Checking nsfw status - PASS
TASK: Get the directors - PASS
.
.
.
TASK: Resetting gateway for wan com ports - PASS
TASK: Resetting the route file for WC ports - PASS
TASK: Disabling WC interfaces at OS level - PASS

PLAY RECAP
*****************************************************************************************
**********************************************************
director-1-1-A|4GCK0R3 : ok=18 changed=4 unreachable=0 failed=0
skipped=2 rescued=0 ignored=0
director-1-1-B|5GCK0R3 : ok=10 changed=4 unreachable=0 failed=0
skipped=9 rescued=0 ignored=0
director-2-1-A|6GCK0R3 : ok=10 changed=4 unreachable=0 failed=0
skipped=9 rescued=0 ignored=0
director-2-1-B|7GCK0R3 : ok=10 changed=4 unreachable=0 failed=0
skipped=9 rescued=0 ignored=0

System configuration process for reset WAN configuration is successful

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.
Removed WANCOM ports from SCIF.
To start the WANCOM interview, run the command "vplex_system_config -i --wancom".
service@director-1-1-a:~>

vplex_system_config -i --wancom

service@director-1-1-a:~> vplex_system_config -i --wancom

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.

WANCOM interview process is started...

Types of protocol supported for WAN configurations.

1. FC
2. IP
Please select your protocol by typing 'IP' or 'FC': (default: FC): FC
WAN FC is selected. FC Ports need to be properly connected
Are you sure you want to select protocol FC? (yes/no): yes

Connecting to 100.x.x.x to fetch the hardware description file (hal.yml)

72 Reconfigure Specific Parameters

Page 77 of 120
 Connecting to 100.x.x.x to fetch the hardware description file (hal.yml)

Connecting to 100.x.x.x to fetch the hardware description file (hal.yml)

Connecting to 100.x.x.x to fetch the hardware description file (hal.yml)

Please review the details entered.

wan_type: FC
name: cluster-1
wan-com:
nodes:
4GCK0R3
interfaces:
WC-FC-00:
enabled: False
role: wan-com
WC-FC-01:
enabled: False
role: wan-com
5GCK0R3
interfaces:
WC-FC-00:
enabled: False
role: wan-com
WC-FC-01:
enabled: False
role: wan-com
name: cluster-2
wan-com:
nodes:
6GCK0R3
interfaces:
WC-FC-00:
enabled: False
role: wan-com
WC-FC-01:
enabled: False
role: wan-com
7GCK0R3
interfaces:
WC-FC-00:
enabled: False
role: wan-com
WC-FC-01:
enabled: False
role: wan-com

Please review the above details.

Do you want to proceed(y/n)? (default: y):

WANCOM interview process is completed.

To apply the new WANCOM configuration, run the command 'vplex_system_config --wancom'.
service@director-1-1-a:~>

vplex_system_config --wancom

service@director-1-1-a:~> vplex_system_config --wancom

Starting the system configuration process for wancom tasks...
TASK: Gathering Facts - PASS
TASK: Creating udcom paths for wancom and nmg add site - PASS
.
.
TASK: Waiting for 5 seconds before checking the port status - PASS
TASK: Verifying the ports status - PASS

Reconfigure Specific Parameters 73

Page 78 of 120
 PLAY RECAP
*****************************************************************************************
**********************************************************
director-1-1-A|4GCK0R3 : ok=10 changed=0 unreachable=0 failed=0
skipped=8 rescued=0 ignored=0
director-1-1-B|5GCK0R3 : ok=4 changed=0 unreachable=0 failed=0
skipped=14 rescued=0 ignored=0
director-2-1-A|6GCK0R3 : ok=5 changed=0 unreachable=0 failed=0
skipped=13 rescued=0 ignored=0
director-2-1-B|7GCK0R3 : ok=4 changed=0 unreachable=0 failed=0
skipped=14 rescued=0 ignored=0

System configuration process for WAN configuration is successful

service@director-1-1-a:~>

Change the topology from WANCOM FC to WANCOM IP

The following commands are used to change the WAN topology:
● vplex_system_config --reset-wancom
● vplex_system_config -i --wancom
● vplex_system_config --wancom
vplex_system_config --reset-wancom

service@director-1-1-a:~> vplex_system_config --reset-wancom

WARNING !!!
Running this command will reset the wancom parameters from the metro node. Do you really
want to continue?
Please type 'yes' to proceed or 'no' to exit:
yes
Starting the system configuration process for reset wancom tasks...
TASK: Resetting wan-com ports - PASS
TASK: Checking nsfw status - PASS
TASK: Get the directors - PASS
.
.
TASK: Waiting for 5 seconds before checking the port status - PASS
TASK: Verifying the ports - PASS

PLAY RECAP
*****************************************************************************************
**********************************************************
director-1-1-A|4GCK0R3 : ok=11 changed=0 unreachable=0 failed=0
skipped=3 rescued=0 ignored=0
director-1-1-B|5GCK0R3 : ok=3 changed=0 unreachable=0 failed=0
skipped=10 rescued=0 ignored=0
director-2-1-A|6GCK0R3 : ok=3 changed=0 unreachable=0 failed=0
skipped=10 rescued=0 ignored=0
director-2-1-B|7GCK0R3 : ok=3 changed=0 unreachable=0 failed=0
skipped=10 rescued=0 ignored=0

System configuration process for reset WAN configuration is successful

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.
Removed WANCOM ports from SCIF.

To start the WANCOM interview, run the command "vplex_system_config -i --wancom".

service@director-1-1-a:~>

vplex_system_config -i --wancom

service@director-1-1-a:~> vplex_system_config -i --wancom

74 Reconfigure Specific Parameters

Page 79 of 120
Taking backup of existing SCIF has been started...
Taking backup of existing SCIF has been completed.

WANCOM interview process is started...

Types of protocol supported for WAN configurations.

1. FC
2. IP
Please select your protocol by typing 'IP' or 'FC': (default: FC): IP
WAN IP is selected. IP Ports need to be properly connected
Are you sure you want to select protocol IP? (yes/no): yes

Types of wan configurations supported.

1. Routed
2. Bridged
Please select your wan type: 2

Collecting the wan details for cluster-1

Collecting Gateway, subnet, MTU & prefix for WC-IP-00 ports at cluster-1
Enter prefix IP(should be same for all WC-IP-00 of cluster-1)(example:
192.168.35.0): 192.x.x.x
Enter netmask IP(should be same for all WC-IP-00 of cluster-1): 255.x.x.x
Enter MTU(should be same for all WC-IP-00 of cluster-1) (default: 1500):

Collecting Gateway, subnet, MTU & prefix for WC-IP-01 ports at cluster-1
Enter prefix IP(should be same for all WC-IP-01 of cluster-1)(example:
192.168.36.0): 192.x.x.x
Enter netmask IP(should be same for all WC-IP-01 of cluster-1): 255.x.x.x
Enter MTU(should be same for all WC-IP-01 of cluster-1) (default: 1500):

Collecting director-1-1-A details

Enter WC-IP-00 IP address: 192.x.x.x
Enter WC-IP-01 IP address: 192.x.x.x

Collecting director-1-1-B details

Enter WC-IP-00 IP address: 192.x.x.x
Enter WC-IP-01 IP address: 192.x.x.x

Collecting the wan details for cluster-2

Collecting Gateway, subnet, MTU & prefix for WC-IP-00 ports at cluster-2
Enter MTU(should be same for all WC-IP-00 of cluster-2) (default: 1500):

Collecting Gateway, subnet, MTU & prefix for WC-IP-01 ports at cluster-2
Enter MTU(should be same for all WC-IP-01 of cluster-2) (default: 1500):

Collecting director-2-1-A details

Enter WC-IP-00 IP address: 192.x.x.x
Enter WC-IP-01 IP address: 192.x.x.x

Collecting director-2-1-B details

Enter WC-IP-00 IP address: 192.x.x.x
Enter WC-IP-01 IP address: 192.x.x.x

Please review the details entered.

wan_type: bridged
name: cluster-1
wan-com:
WC-IP-00:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
WC-IP-01:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
nodes
4GCK0R3
interfaces:

Reconfigure Specific Parameters 75

Page 80 of 120
 WC-IP-00:
ip:
address: 192.x.x.x
role: wan-com
WC-IP-01:
ip:
address: 192.x.x.x
role: wan-com
5GCK0R3
interfaces:
WC-IP-00:
ip:
address: 192.x.x.x
role: wan-com
WC-IP-01:
ip:
address: 192.x.x.x
role: wan-com
name: cluster-2
wan-com:
WC-IP-00:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
WC-IP-01:
prefix: 192.x.x.x
gateway:
netmask: 255.x.x.x
mtu: 1500
nodes
6GCK0R3
interfaces:
WC-IP-00:
ip:
address: 192.x.x.x
role: wan-com
WC-IP-01:
ip:
address: 192.x.x.x
role: wan-com
7GCK0R3
interfaces:
WC-IP-00:
ip:
address: 192.x.x.x
role: wan-com
WC-IP-01:
ip:
address: 192.x.x.x
role: wan-com

Please review the above details.

Do you want to proceed(y/n)? (default: y):

WANCOM interview process is completed.

To apply the new WANCOM configuration, run the command 'vplex_system_config --wancom'.
service@director-1-1-a:~>

vplex_system_config --wancom

service@director-1-1-a:~> vplex_system_config --wancom

Starting the system configuration process for wancom tasks...
TASK: Gathering Facts - PASS
TASK: Check if config files WC-00 and WC-01 exist - PASS
TASK: Check if route files WC-00 and WC-01 exist - PASS
.
.
TASK: Get wan port names - PASS

76 Reconfigure Specific Parameters

Page 81 of 120
 TASK: Enabling the ports - PASS
TASK: Waiting for 5 seconds before checking the port status - PASS
TASK: Verifying the ports status - PASS

PLAY RECAP
*****************************************************************************************
**********************************************************
director-1-1-A|4GCK0R3 : ok=21 changed=4 unreachable=0 failed=0
skipped=10 rescued=0 ignored=0
director-1-1-B|5GCK0R3 : ok=15 changed=4 unreachable=0 failed=0
skipped=16 rescued=0 ignored=0
director-2-1-A|6GCK0R3 : ok=16 changed=4 unreachable=0 failed=0
skipped=15 rescued=0 ignored=0
director-2-1-B|7GCK0R3 : ok=15 changed=4 unreachable=0 failed=0
skipped=16 rescued=0 ignored=0

System configuration process for WAN configuration is successful

service@director-1-1-a:~>

Remove WAN COM

1. To reset the WAN COM, use the command vplex_system_config --reset-wancom.

NOTE: Performing this command ends up losing the WAN COM link.

service@director-1-1-a:~> vplex_system_config --reset-wancom

WARNING !!!
Running this command will reset the wancom parameters from the metro node. Do you
really want to continue?
Please type 'yes' to proceed or 'no' to exit:
yes
Starting the system configuration process for reset wancom tasks...
TASK: Resetting wan-com ports - PASS
TASK: Checking nsfw status - PASS
TASK: Get the directors - PASS
.
.
.
TASK: Resetting the route file for WC ports - PASS
TASK: Disabling WC interfaces at OS level - PASS

PLAY RECAP
**************************************************************************************
**********************************************************************************
director-1-1-A|8K13Z23 : ok=17 changed=4 unreachable=0 failed=0
skipped=2 rescued=0 ignored=0
director-1-1-B|8K12Z23 : ok=11 changed=4 unreachable=0 failed=0
skipped=9 rescued=0 ignored=0
director-2-1-A|8K15Z23 : ok=10 changed=4 unreachable=0 failed=0
skipped=9 rescued=0 ignored=0
director-2-1-B|8K10Z23 : ok=10 changed=4 unreachable=0 failed=0
skipped=9 rescued=0 ignored=0

System configuration process for reset WAN configuration is successful

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.
Removed WANCOM ports from SCIF.

To start the WANCOM interview, run the command "vplex_system_config -i --wancom".

service@director-1-1-a:~>

Reconfigure Specific Parameters 77

Page 82 of 120
Change the Public IP/EC-01 Address of the director
WARNING: Running the vplex_system_config --start or vplex_system_config -s command on an
already configured system stops the node firmware, causing a Total Cluster Outage.
To update the Public or EC-01 IP Address of the current director of the metro node, use the following steps:
NOTE:
● Changing the Public IP Address is done from peer director of the same cluster.
● Check with the Metro node administrator for the service password as it would have been changed during installation and
might have changed further after.
1. Log in as service user credentials on to the Director where you want to update the Public or EC-01 IP.
2. Run the command below to show the current public IP of that director.

service@director-1-1-a:~> vplex_system_config -i --show-ec01-ip

Ip: 10.x.x.x
Gateway: 10.x.x.x
Netmask: 255.x.x.x
Mtu: 1500
service@director-1-1-a:~>

3. Log in as service credentials on to the peer director of the same cluster. For example: If you want to update the public or
EC-01 IP of director-1-1-A, Login to director-1-1-B.
4. Run the command below to update the public IP of the peer director.

NOTE: Default values come from the existing configuration

service@director-1-1-b:~> vplex_system_config -i --update-peer-ec01-ip

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.
This will update EC-01 IP of director-1-1-A
Enter director's EC-01 port details:
IP Address (default: 10.x.x.x): 10.x.x.x
IP Address is validating, please wait...
Netmask (default: 255.x.x.x):
Gateway (default: 10.x.x.x):
MTU (default: 1500):
The EC-01 port on director-1-1-A is about to be reconfigured.
All connections to this IP will be terminated.
Log in to the new IP after the configuration procedure completes.
Peer EC-01 IP was updated successfully
Updating the known_hosts file with the new ssh key
Key appended successfully for 10.x.x.x
Key appended successfully for 10.x.x.x
Key appended successfully for 10.x.x.x
Key appended successfully for 10.x.x.x
New IP Fingerprints are accepted from all the nodes
Copying the scif content to other nodes

Restarting the NGINX service

TASK: Gathering Facts - PASS
TASK: Restarting the nginx service - PASS
TASK: Checking if the nginx service is started - PASS

PLAY RECAP
**************************************************************************************
*************************************************************
director-1-1-A|8K63Z23 : ok=3 changed=1 unreachable=0 failed=0
skipped=9 rescued=0 ignored=0
director-1-1-B|8K64Z23 : ok=3 changed=1 unreachable=0 failed=0
skipped=9 rescued=0 ignored=0
director-2-1-A|8K65Z23 : ok=3 changed=1 unreachable=0 failed=0
skipped=9 rescued=0 ignored=0

78 Reconfigure Specific Parameters

Page 83 of 120
 director-2-1-B|8K66Z23 : ok=3 changed=1 unreachable=0 failed=0
skipped=9 rescued=0 ignored=0

System configuration process for nginx restart is successful

As node-11A IP is updated, Performing NTP restart
TASK: Gathering Facts - PASS
TASK: Copying the ntp configuration file to the node-1-1-A - PASS
.
.
.
TASK: Setting iDRAC NTP server - PASS

PLAY RECAP
**************************************************************************************
*************************************************************
director-1-1-A|8K63Z23 : ok=15 changed=2 unreachable=0 failed=0
skipped=3 rescued=0 ignored=0
director-1-1-B|8K64Z23 : ok=14 changed=3 unreachable=0 failed=0
skipped=3 rescued=0 ignored=0
director-2-1-A|8K65Z23 : ok=14 changed=3 unreachable=0 failed=0
skipped=3 rescued=0 ignored=0
director-2-1-B|8K66Z23 : ok=14 changed=3 unreachable=0 failed=0
skipped=3 rescued=0 ignored=0

System configuration process for update NTP is successful

Performing CWS NTP update
TASK: Gathering Facts - PASS
.
.
.
TASK: Gathering Facts - PASS

PLAY RECAP
**************************************************************************************
*************************************************************
cws : ok=7 changed=5 unreachable=0 failed=0
skipped=0 rescued=0 ignored=0
director-1-1-A|8K63Z23 : ok=1 changed=0 unreachable=0 failed=0
skipped=0 rescued=0 ignored=0
director-1-1-B|8K64Z23 : ok=1 changed=0 unreachable=0 failed=0
skipped=0 rescued=0 ignored=0
director-2-1-A|8K65Z23 : ok=1 changed=0 unreachable=0 failed=0
skipped=0 rescued=0 ignored=0
director-2-1-B|8K66Z23 : ok=1 changed=0 unreachable=0 failed=0
skipped=0 rescued=0 ignored=0

System configuration process for update_peer_ec01_ip is successful

Update Peer EC-01 IP process is successfully completed.

5. Login onto the peer director using the new IP.

6. Run the following command to see the new Public or EC-01 IP.

service@director-1-1-a:~> vplex_system_config -i --show-ec01-ip

Ip: 10.x.x.x
Gateway: 10.x.x.x
Netmask: 255.x.x.x
Mtu: 1500
service@director-1-1-a:~>

Change the name of the cluster

To change or update the cluster name of the current cluster, use the following steps:
NOTE:
● To change the cluster name, you should do it in a configured metro node, not in an unconfigured one.

Reconfigure Specific Parameters 79

Page 84 of 120
 ● Check with the metro node administrator for the service password as it would have been changed during installation and
might have changed further after.
● Run this command in one node, and it reflects the changes in all the nodes.
1. Log in to any node as a service user.
2. Run the command with the following options for show and update cluster name. After collecting the cluster-name from the
end user, if the playbook runs successfully, it invokes the playbook with the cluster-name tag and updates it accordingly in
the SCIF.
a. vplex_system_config -i --show-cluster-name

service@director-1-1-a:~> vplex_system_config -i --show-cluster-name

cluster-1: cluster-1

service@director-1-1-a:~>

b. vplex_system_config i - update-cluster-name

service@director-1-1-a:~> vplex_system_config -i --update-cluster-name

Taking backup of existing SCIF has been started...
Taking backup of existing SCIF has been completed.

Update cluster name process is started...

Please enter the new name for existing 'test-cluster1'
cluster (default: test-cluster1): cluster1
Please enter the new name for existing 'test-cluster2'
cluster (default: test-cluster2): cluster2
TASK: Gathering Facts - PASS
TASK: Update cluster name for cluster-1 - PASS
TASK: Update cluster name for cluster-2 - PASS

PLAY RECAP
************************************************************************************
**************************************************************
director-1-1-A|8K13Z23 : ok=2 changed=0 unreachable=0 failed=0
skipped=1 rescued=0 ignored=0
director-1-1-B|8K12Z23 : ok=1 changed=0 unreachable=0 failed=0
skipped=2 rescued=0 ignored=0
director-2-1-A|8K15Z23 : ok=2 changed=0 unreachable=0 failed=0
skipped=1 rescued=0 ignored=0
director-2-1-B|8K10Z23 : ok=1 changed=0 unreachable=0 failed=0
skipped=2 rescued=0 ignored=0

System configuration process for update cluster name is successful

View the SCIF content

To view the SCIF file content in the metro node, see the following steps:
WARNING: Running the vplex_system_config --start or vplex_system_config -s command on an
already configured system stops the node firmware, causing a Total Cluster Outage.

NOTE:
● Check with the Metro node administrator for the service password as it would have been changed during installation and
might have changed further after.
● Run this command in one node, and the changes are reflected in all the node.
1. Log in as service user with the credentials in one of the directors of the metro node.
2. Run the following command: vplex_system_config -i --show

service@director-1-1-a:~> vplex_system_config -i --show

Displaying the current configuration SCIF data content.

# Warning!!! This file contains the configuration details of a VPlex system. So
changing the contents of the file would not be recommended as it would lead the
system to go into a vulnerable state. vplex_system:

80 Reconfigure Specific Parameters

Page 85 of 120
clusters:
- call_home: {}
director_count: 2
guid: 43AXXXX
id: 1
instance: 1
ldap: {}
name: cluster-1
nodes:
8K14Z23:
address: XX.XXX.XX.XXX
interfaces:
EC-01:
enabled: true
ip:
address: XX.XXX.XX.XXX
gateway: XX.XXX.XX.X
mtu: 1500
netmask: XXX.XXX.XXX.X
paths: []
role: cust
IO-00:
enabled: true
role: front-end
IO-01:
enabled: true
role: front-end
IO-02:
enabled: true
role: back-end
IO-03:
enabled: true
role: back-end
LC-00:
enabled: true
ip:
address: 128.221.250.36
gateway: ''
mtu: 1500
netmask: 255.255.255.224
paths:
- 128.221.250.35
role: com
secondary_ip:
address: 128.221.241.36
netmask: 255.255.252.0
LC-01:
enabled: true
ip:
address: 128.221.251.36
gateway: ''
mtu: 1500
netmask: 255.255.255.224
paths:
- 128.221.251.35
role: com
secondary_ip:
address: 128.221.242.36
netmask: 255.255.252.0
MC-00:
enabled: true
ip:
address: 128.221.252.36
gateway: ''
mtu: 1500
netmask: 255.255.255.224
paths:
- 128.221.252.35
role: man
MC-01:
enabled: true
ip:
address: 128.221.253.36

Reconfigure Specific Parameters 81

Page 86 of 120
 gateway: ''
mtu: 1500
netmask: 255.255.255.224
paths:
- 128.221.253.35
role: man
idrac:
lom_address: 128.221.240.36
lom_netmask: 255.255.252.0
lom_selection: LOM1
role: idrac
name: director-1-1-B
wwn_seed: 2XX000XX
8K16Z23:
address: XX.XXX.XX.XXX
interfaces:
.
.
.
name: director-1-1-A
ntp_servers:
- 127.0.0.1
- ''
wwn_seed: 2XX000YY
ssl_certificates:
.
.
.
snmp: {}
service@director-1-1-a:~>

Change the login banner

WARNING: Running the vplex_system_config --start or vplex_system_config -s command on an
already configured system stops the node firmware, causing a Total Cluster Outage.

NOTE:
● Check with the Metro node administrator for the service password as it would have been changed during installation and
might have changed further after.
● Run this command in one node, and the changes are reflected in all the node.
To change or update the login banner of the current node, use the following steps:
1. Upload the updated banner content in /home/service/banner.txt. It is a manual step as banner details are not collected
during the interview.
2. Log in as a service user with the credentials in one of the directors of the metro node.
3. Run the command with the following options for show and update banner:
a. vplex_system_config --banner

service@director-1-1-a:~> vplex_system_config --banner

Starting the banner file configuration process in system configuration...
TASK: Gathering Facts - PASS
TASK: Checking banner file exists. - PASS

PLAY RECAP
************************************************************************************
**************************************************************
director-1-1-A|8K13Z23 : ok=3 changed=0 unreachable=0 failed=0
skipped=2 rescued=0 ignored=0
director-1-1-B|8K12Z23 : ok=3 changed=0 unreachable=0 failed=0
skipped=2 rescued=0 ignored=0
director-2-1-A|8K15Z23 : ok=3 changed=0 unreachable=0 failed=0
skipped=2 rescued=0 ignored=0
director-2-1-B|8K10Z23 : ok=3 changed=0 unreachable=0 failed=0
skipped=2 rescued=0 ignored=0

System configuration process for banner is successful

82 Reconfigure Specific Parameters

Page 87 of 120
4. To reset the process, use the following command:

Resetting the login banner

To reset the process, use the following command:
1. vplex_system_config --reset-banner

service@director-1-1-a:~> vplex_system_config --reset-banner

WARNING !!!
Running this command will reset the banner parameters from the metro node. Do you
really want to continue?
Please type 'yes' to proceed or 'no' to exit:
no
exiting...

service@director-1-1-a:~> vplex_system_config --reset-banner

WARNING !!!
Running this command will reset the banner parameters from the metro node. Do you
really want to continue?
Please type 'yes' to proceed or 'no' to exit:
yes
Starting the system configuration process for reset banner tasks...
TASK: Removing the login banner - PASS

PLAY RECAP
**************************************************************************************
************************************************************
director-1-1-A|8K13Z23 : ok=2 changed=1 unreachable=0 failed=0
skipped=1 rescued=0 ignored=0
director-1-1-B|8K12Z23 : ok=2 changed=1 unreachable=0 failed=0
skipped=1 rescued=0 ignored=0
director-2-1-A|8K15Z23 : ok=2 changed=1 unreachable=0 failed=0
skipped=1 rescued=0 ignored=0
director-2-1-B|8K10Z23 : ok=2 changed=1 unreachable=0 failed=0
skipped=1 rescued=0 ignored=0

System configuration process for reset banner is successful

Retrieve the iDRAC password

This command allows the user to show the iDRAC password for the clusters.
WARNING: Running the vplex_system_config --start or vplex_system_config -s command on an
already configured system stops the node firmware, causing a Total Cluster Outage.

NOTE:
● Both the directors of the cluster have the same iDRAC password.
● Check with the metro node administrator for the service password as it would have been changed during installation and
might have changed further after.
● Run this command in one node, and the changes are reflected in all the node.
1. Log in as service user, using the credentials on one of the directors in the cluster.
2. To show iDRAC password for the clusters, run the following command:
a. vplex_system_config -i --show-idrac-password

service@director-1-1-a:~> vplex_system_config -i --show-idrac-password

Idrac Password: T%jhg6E

service@director-1-1-a:~>

Reconfigure Specific Parameters 83

Page 88 of 120
Change the service user password
WARNING: Running the vplex_system_config --start or vplex_system_config -s command on an
already configured system stops the node firmware, causing a Total Cluster Outage.
To change the service user password for both the directors in a cluster, use the following steps:
NOTE:
● This command should be run on a configured system only. If you change the service password before configuring the
system, and expects the default password, this results in failure. Change the service password during the configuration
steps only.
● Check with the metro node administrator for the service password as it would have been changed during installation and
might have changed further after.
● Run this command in one node, and the changes are reflected in all the node.
1. Log in as service user, with the credentials in one of the directors of the metro node.
2. Run the command with the following options: vplex_system_config -i --update-service-password
a. Success output:

service@director-1-1-a:~> vplex_system_config -i --update-service-password

Updating service user password process started...

Enter the service user password:
Current password :
New password :
Retype new password :

The password has been changed successfully for the 'service' user for the
director-1-1-b(8K11Z23).

The password has been changed successfully for the 'service' user for the
director-1-1-a(8K17Z23).

################### To receive the highest level of support, inform Dell support if

there is a change in the service password ###################
service@director-1-1-a:~>

b. Error output: If the updated password fails in the peer node, then the below output is seen:

service@director-1-1-a:~> vplex_system_config -i --update-service-password

Updating service user password process started...

Enter the service user password:
Current password :
New password :
Retype new password :

The password has been changed successfully for the 'service' user for the
director-1-1-a(8K17Z23).

################### To receive the highest level of support, inform Dell support if

there is a change in the service password ###################

Error in executing the playbook while changing the password for the user: service,
details: Authentication service cannot retrieve authentication info. The password is not changed.
Please run the interview command with '--update-local-service-password' in director-1-1-b(8K11Z23) and
ensure that a valid current password has been provided.

service@director-1-1-a:~>

If you log in to a particular node and perform the service password command, then the password change is applicable in
that node only.
c. Before running the below command, contact Customer support.

service@director-1-1-a:~> vplex_system_config -i --update-local-service-password

84 Reconfigure Specific Parameters

Page 89 of 120
 Taking backup of existing SCIF has been started...
Taking backup of existing SCIF has been completed.

Updating service user password process is started...

Enter the service user password:
Current password :
New password :
Retype new password :

The password has been changed successfully for the 'service' user.

################### To receive the highest level of support, inform Dell support if

there is a change in the service password ###################
service@director-1-1-a:~>

Change the SSL certificates for self_signed

To change or update the SSL certification of the current cluster, use the following steps:
WARNING: Running the vplex_system_config --start or vplex_system_config -s command on an
already configured system stops the node firmware, causing a Total Cluster Outage.

NOTE:
● Check with the Metro node administrator for the service password as it would have been changed during installation and
might have changed further after.
● Run this command in one node, and the changes are reflected in all the node.
1. Log in as service user with the credentials in one of the directors of the metro node.
2. Run the command with the following options for show and update SSL certificates details (updates SCIF and run the
playbook with ssl_certificates):
a. To show SSL certificate information: Run vplex_system_config -i --show-ssl-certificates

service@director-1-1-a:~> vplex_system_config -i --show-ssl-certificates

Certificates details
ca:
algo_type : rsa
expiry_days : 1825
key_length : 2048
cert_type: self_signed
host:
algo_type : rsa
expiry_days : 730
key_length : 2048

b. To update the certificates: Run vplex_system_config -i --update-ssl-certificates

service@director-1-1-a:~> vplex_system_config -i --update-ssl-certificates

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.

Update SSL certificates process is started...

Enter SSL certificates details:

Types of certificate configurations supported.

1. self_signed
2. cust_signed
Please select your certificate type. (default: self_signed):
CA Expiry Days (default: 1825):
CA Key Length (default: 2048):
CA Algo Type (default: rsa):
Host Expiry Days (default: 730):
Host Key Length (default: 2048):
Host Algo Type (default: rsa):

Reconfigure Specific Parameters 85

Page 90 of 120
 TASK: Gathering Facts - PASS
TASK: Validating if the default values are changed - PASS
.
.
.
TASK: Deleting ca_cert and ca_key temp files - PASS
TASK: Restarting the nginx service - PASS
TASK: Deleting certificate backup directory - PASS
TASK: Checking nsfw status - PASS
TASK: Generating host certificate request
Failed and Rescued (continue with next tasks): director-1-1-B|8K12Z23
Failed and Rescued (continue with next tasks): director-1-1-A|8K13Z23
Failed and Rescued (continue with next tasks): director-2-1-B|8K10Z23
Failed and Rescued (continue with next tasks): director-2-1-A|8K15Z23

PLAY RECAP
************************************************************************************
**************************************************************
director-1-1-A|8K13Z23 : ok=31 changed=11 unreachable=0 failed=0
skipped=7 rescued=1 ignored=0
director-1-1-B|8K12Z23 : ok=35 changed=10 unreachable=0 failed=0
skipped=7 rescued=1 ignored=0
director-2-1-A|8K15Z23 : ok=31 changed=10 unreachable=0 failed=0
skipped=7 rescued=1 ignored=0
director-2-1-B|8K10Z23 : ok=31 changed=10 unreachable=0 failed=0
skipped=7 rescued=1 ignored=0

System configuration process for update SSL certificates is successful

service@director-1-1-a:~>

c. To check certificate details: Run vplex_system_config -i --show-ssl-certificates

service@director-1-1-a:~> vplex_system_config -i --show-ssl-certificates

Certificates details
ca:
algo_type : rsa
expiry_days : 1825
key_length : 2048
cert_type: self_signed
host:
algo_type : rsa
expiry_days : 1825
key_length : 2048

service@director-1-1-a:~>

Change the SSL certificate for cust_signed

WARNING: Running the vplex_system_config --start or vplex_system_config -s command on an
already configured system stops the node firmware, causing a Total Cluster Outage.
For cust_signed SSL certificates (import type), import the certificates at /home/service/ this location with the following
names:
● /home/service/director-1-1-A.crt- host-1-1-A certificates
● /home/service/director-1-1-A.key- host-1-1-A key certificates
● /home/service/ca.crt - ca certificates
● /home/service/director-1-1-B.crt - host-1-1-B certificates
● /home/service/director-1-1-B.key - host-1-1-B key certificates
● /home/service/director-2-1-B.crt - host-2-1-B certificates
● /home/service/director-2-1-B.key - host-2-1-B key certificates
● /home/service/director-2-1-A.crt- host-2-1-A certificates
● /home/service/director-2-1-A.key- host-2-1-A key certificates

86 Reconfigure Specific Parameters

Page 91 of 120
After updating the certificates, run the command service@director-1-1-a:~> vplex_system_config -i --
update-ssl-certificates

NOTE: Enter the passphrase key which is used to create the certificates.

1. Log in as service user with the credentials in one of the directors of the metro node.
2. Run the command with the following options to show and update SSL certificates details (updates SCIF and run the
playbook with ssl_certificates):
a. To show certificate information for custom-signed certificates: Run vplex_system_config -i --show-ssl-certificates

service@director-1-1-a:~> vplex_system_config -i --show-ssl-certificates

Certificates details

cert_type: cust_signed
passphrase_key: oldstrongswan
service@director-1-1-a:~>

b. To update custom-signed certificates: Run vplex_system_config -i --update-ssl-certificates

service@director-1-1-a:~> vplex_system_config -i --update-ssl-certificates

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.

Update SSL certificates process is started...

Enter SSL certificates details:

Types of certificate configurations supported.

1. self_signed
2. cust_signed
Please select your certificate type. (default:
self_signed): 2
Please make sure you have uploaded the following
certificates
i.e.. ca.crt, director-1-1-A.crt, director-1-1-B.crt,
director-1-1-B.key, director-1-1-A.key, director-2-1-A.crt,
director-2-1-B.crt, director-2-1-A.key, director-2-1-B.key
for metro.
And for local ca.crt, director-1-1-A.crt,
director-1-1-B.crt,
director-1-1-B.key, director-1-1-A.key are required.
Do you want to proceed? (default: y):
Validating the certificates...
ca certificate is available.
director-1-1-A certificate is available.
director-1-1-B certificate is available.
director-1-1-A key is available.
director-1-1-B key is available.
director-2-1-A certificate file is available.
director-2-1-B certificate file is available.
director-2-1-A key file is available.
director-2-1-B key file is available.
please enter passphrase key:
TASK: Gathering Facts - PASS
TASK: Copy SSL certs from current node to all nodes - PASS
TASK: Validate node certs with ca cert - PASS
.
.
.
TASK: Generating truststore - PASS
TASK: Assemble from fragments from a directory - PASS
TASK: Generating the keystore - PASS
TASK: Restarting the nginx service - PASS

PLAY RECAP
************************************************************************************
**************************************************************
director-1-1-A|8KJ0Z23 : ok=22 changed=4 unreachable=0 failed=0

Reconfigure Specific Parameters 87

Page 92 of 120
 skipped=10 rescued=0 ignored=0
director-1-1-B|8K14Z23 : ok=26 changed=5 unreachable=0 failed=0
skipped=11 rescued=0 ignored=0
director-2-1-A|8K17Z23 : ok=22 changed=4 unreachable=0 failed=0
skipped=10 rescued=0 ignored=0
director-2-1-B|8K11Z23 : ok=22 changed=4 unreachable=0 failed=0
skipped=10 rescued=0 ignored=0

System configuration process for update SSL certificates is successful

service@director-1-1-a:~>

c. To check custom signed certificate details: Run vplex_system_config -i --show-ssl-certificates

service@director-1-1-a:~> vplex_system_config -i --show-ssl-certificates

Certificates details
cert_type: cust_signed
passphrase_key: newstrongswan

service@director-1-1-a:~>

Reset SSL Certificates

Steps
1. Log in as a service user with the credentials in one of the nodes.
2. Run the command vplex_system_config -i --reset-ssl-certificates.
Output:

service@director-1-1-a:~> vplex_system_config --reset-ssl-certificates

WARNING !!!
Running this command will reset the ssl_certificates parameters from the metro node.
Do you really want to continue?
Please type 'yes' to proceed or 'no' to exit:
yes
Starting the system configuration process for reset ssl_certificates tasks...
TASK: deleting certificates files from ansible - PASS

PLAY RECAP
**************************************************************************************
************************************************************
director-1-1-A|8K13Z23 : ok=2 changed=1 unreachable=0 failed=0
skipped=3 rescued=0 ignored=0
director-1-1-B|8K12Z23 : ok=2 changed=1 unreachable=0 failed=0
skipped=3 rescued=0 ignored=0
director-2-1-A|8K15Z23 : ok=2 changed=1 unreachable=0 failed=0
skipped=3 rescued=0 ignored=0
director-2-1-B|8K10Z23 : ok=2 changed=1 unreachable=0 failed=0
skipped=3 rescued=0 ignored=0

System configuration process for reset SSL certificates is successful

service@director-1-1-a:~>

Renew self-signed SSL certificates

WARNING: Running the vplex_system_config --start or vplex_system_config -s command on an
already configured system stops the node firmware, causing a Total Cluster Outage.
In self-signed certificates, there is a role of Ansible for renewal which cron job triggers automatically. The SSL certificate gets
renewed when the expiry date is less than 14 days.

88 Reconfigure Specific Parameters

Page 93 of 120
To trigger the certificate renewal, services vplex-node-ssl-renewal.service and vplex-node-ssl-renewal.timer are created.
These services start when the vplex-node.target invokes (vplex-node.target invokes during phase2 process). The vplex-
node-ssl-renewal.timer triggers every day at 00:00:00 hours and invokes vplex-node-ssl-renewal.service. The vplex-
node-ssl-renewal.service performs the python script which validates the expiry of the SSL certificate. If the validity is less
than 14 days from the current date, then the certificate renews through invoking the Ansible playbook.

service@director-1-1-a:~> sudo systemctl status vplex-node-ssl-renewal.timer

● vplex-node-ssl-renewal.timer - Execute ssl renewal service once in a day[Timer]
Loaded: loaded (/usr/lib/systemd/system/vplex-node-ssl-renewal.timer; enabled; vendor
preset: enabled)
Active: active (waiting) since Thu 2020-11-12 11:22:24 UTC; 18h ago
Trigger: Sat 2020-11-14 00:00:00 UTC; 17h left

Nov 12 11:22:24 localhost systemd[1]: Started Execute ssl renewal service once in a
day[Timer].
service@director-1-1-a:~> sudo systemctl status vplex-node-ssl-renewal.service
● vplex-node-ssl-renewal.service - ssl certificate renewal
Loaded: loaded (/usr/lib/systemd/system/vplex-node-ssl-renewal.service; enabled;
vendor preset: enabled)
Active: inactive (dead) since Fri 2020-11-13 00:00:06 UTC; 6h ago
Process: 18788 ExecStart=/usr/bin/python3 /opt/dell/vplex/lib/python/vplexsetup/
ssl_renewal.py (code=exited, status=0/>
Main PID: 18788 (code=exited, status=0/SUCCESS)

Nov 13 00:00:06 director-1-1-a systemd[1]: Started ssl certificate renewal.

Nov 13 00:00:06 director-1-1-a python3[18788]: SSL certificate renewed successfully!

NOTE: In import certificates, user gets the warnings to renew their certificates 14 days before.

Enabling and disabling of metro node ports

WARNING: Running the vplex_system_config --start or vplex_system_config -s command on an
already configured system stops the node firmware, causing a Total Cluster Outage.

Help command for Port-toggle

This command allows the user to enable or disable ports (LCOM, FE, BE, and WAN) at NSFW layer directly from the service
prompt without logging into vplexcli. You can only use this command on a configured system.
NOTE:
● If a node is down, then use -e option with this command.
● Use this command as CLI set command for port switching does not work.
● Check with the metro node administrator for the service password as it would have been changed during installation and
might have changed further after.
● Run this command in one node, and it will reflect the changes in all the node.
1. Log in as service user with the credentials in one of the directors of the metro node.
2. Run the command with the following option: vplex_system_config --port-toggle -h

service@director-1-1-a:~> vplex_system_config --port-toggle -h

Starting port toggle process...
usage: set_port.py [-h] -s {enable,e,disable,d} -t
{director-*,director-1-*,director-2-*,director-1-1-B,director-1-1-
A,director-2-1-B,director-2-1-A}
[{director-*,director-1-*,director-2-*,director-1-1-B,director-1-1-
A,director-2-1-B,director-2-1-A} ...]
-p {IO-03,LC-01,IO-02,LC-00,IO-01,WC-00,WC-01,IO-00}
[-e [{director-1-1-B,director-1-1-A,director-2-1-B,director-2-1-A}
[{director-1-1-B,director-1-1-A,director-2-1-B,director-2-1-A} ...]]]

optional arguments:
-h, --help show this help message and exit
-s {enable,e,disable,d}

Reconfigure Specific Parameters 89

Page 94 of 120
 Set the port to this state
-t {director-*,director-1-*,director-2-*,director-1-1-B,director-1-1-A,director-2-1-
B,director-2-1-A} [{director-*,director-1-*,director-2-*,director-1-1-B,director-1-1-
A,director-2-1-B,director-2-1-A} ...]
Directors where the port should be toggled
-p {IO-03,LC-01,IO-02,LC-00,IO-01,WC-00,WC-01,IO-00}
Port to enable/disable
-e [{director-1-1-B,director-1-1-A,director-2-1-B,director-2-1-A} [{director-1-1-
B,director-1-1-A,director-2-1-B,director-2-1-A} ...]]
Ignore these nodes when toggling ports. WARNING: USING
THIS OPTION LEAVES THE SYSTEM IN AN INCONSISTENT STATE
THAT MUST BE MANUALLY CORRECTED
service@director-1-1-a:~>

Enable port for one director

See the following steps:

Steps
1. Log in as a service user with the credentials in one of the nodes of the metro node.
2. Run the following command to enable I/O-02 port of director-1-1-B: vplex_system_config --port-toggle -s e -t
director-1-1-B -p IO-02.

service@director-1-1-a:~> vplex_system_config --port-toggle -s e -t director-1-1-B -p IO-02

Starting port toggle process...
Setting port IO-02 to enabled on ['director-1-1-B'], updating SCIF on ['director-1-1-
B', 'director-1-1-A', 'director-2-1-B', 'director-2-1-A']

Setting port IO-02 to enabled on director-1-1-B

service@director-1-1-a:~>

Disable port for one director

See the following steps:

Steps
1. Log in as a service user with the credentials in one of the nodes of the metro node.
2. Run the following command to disable I/O-02 port of director-1-1-B: vplex_system_config --port-toggle -s d -t
director-1-1-B -p IO-02.

service@director-1-1-a:~> vplex_system_config --port-toggle -s d -t director-1-1-B -p IO-02

Starting port toggle process...
Setting port IO-02 to disabled on ['director-1-1-B'], updating SCIF on ['director-1-1-
B', 'director-1-1-A', 'director-2-1-B', 'director-2-1-A']

Setting port IO-02 to disabled on director-1-1-B

service@director-1-1-a:~>

Enable port for one cluster

See the following steps:

Steps
1. Log in as a service user (with the credentials) to one of the nodes of metro node for cluster-1.

90 Reconfigure Specific Parameters

Page 95 of 120
2. Run the following command to enable I/O-02 port of director-1-1-A and director-1-1-B: vplex_system_config --port-
toggle -s e -t director-1-* -p IO-02.

service@director-1-1-a:~> vplex_system_config --port-toggle -s e -t director-1-* -p IO-02

Starting port toggle process...
Setting port IO-02 to enabled on ['director-1-1-B', 'director-1-1-A'], updating SCIF
on ['director-1-1-B', 'director-1-1-A', 'director-2-1-B', 'director-2-1-A']

Setting port IO-02 to enabled on director-1-1-B

Setting port IO-02 to enabled on director-1-1-A
service@director-1-1-a:~>

Disable port for one cluster

See the following steps:

Steps
1. Log in as a service user with the credentials in one of the nodes of the metro node for cluster-1.
2. Run the following command to disable I/O-02 port of director-1-1-A and director-1-1-B: vplex_system_config --port-
toggle -s d -t director-1-* -p IO-02.

service@director-1-1-a:~> vplex_system_config --port-toggle -s d -t director-1-* -p IO-02

Starting port toggle process...
Setting port IO-02 to disabled on ['director-1-1-B', 'director-1-1-A'], updating SCIF
on ['director-1-1-B', 'director-1-1-A', 'director-2-1-B', 'director-2-1-A']

Setting port IO-02 to disabled on director-1-1-B

Setting port IO-02 to disabled on director-1-1-A
service@director-1-1-a:~>

Enable port for all directors

See the following steps:

Steps
1. Log in as a service user with the credentials in one of the nodes of the metro node.
2. Run the following command to enable I/O-02 port of all directors: vplex_system_config --port-toggle -s e -t director-*
-p IO-02.

service@director-1-1-a:~> vplex_system_config --port-toggle -s e -t director-* -p

IO-02
Starting port toggle process...
Setting port IO-02 to enabled on ['director-1-1-B', 'director-1-1-A', 'director-2-1-
B', 'director-2-1-A'], updating SCIF on ['director-1-1-B', 'director-1-1-A',
'director-2-1-B', 'director-2-1-A']

Setting port IO-02 to enabled on director-1-1-B

Setting port IO-02 to enabled on director-1-1-A
Setting port IO-02 to enabled on director-2-1-B
Setting port IO-02 to enabled on director-2-1-A
service@director-1-1-a:~>

Reconfigure Specific Parameters 91

Page 96 of 120
Disable port for all directors
See the following steps:

Steps
1. Log in as a service user with the credentials in one of the nodes of the metro node.
2. Run the following command to disable the I/O-02 port of all directors: vplex_system_config --port-toggle -s d -t
director-* -p IO-02.

service@director-1-1-a:~> vplex_system_config --port-toggle -s d -t director-* -p

IO-02
Starting port toggle process...
Setting port IO-02 to disabled on ['director-1-1-B', 'director-1-1-A', 'director-2-1-
B', 'director-2-1-A'], updating SCIF on ['director-1-1-B', 'director-1-1-A',
'director-2-1-B', 'director-2-1-A']

Setting port IO-02 to disabled on director-1-1-B

Setting port IO-02 to disabled on director-1-1-A
Setting port IO-02 to disabled on director-2-1-B
Setting port IO-02 to disabled on director-2-1-A
service@director-1-1-a:~>

Exclude one or more directors

See the following steps:

Steps
1. Log in as a service user with the credentials in one of the nodes of the metro node.
2. Run the following command to disable I/O-02 port of director-1-1-A and exclude director-1-1-B for unavoidable reasons:
vplex_system_config --port-toggle -s d -t director-1-1-A -p IO-02 -e director-1-1-B
When you use the option director-1-1-B (excluded director), it does not copy SCIF to director-1-1-B. Use the option -e for
enabling or disabling the ports.
● You can perform the following example, port toggle from the director-1-1-A. The director-1-1-B skips simultaneously
because it is unreachable. Director-1-1-B does not copy the SCIF.
● Copy the SCIF from director-1-1-A to director-1-1-B node once director-1-1-B is in a reachable state. If SCIF is not
synchronized with the other nodes, then the system is not in the correct state.

service@director-1-1-a:~> vplex_system_config --port-toggle -s d -t director-1-1-A -p IO-02 -e

director-1-1-B
Starting port toggle process...
Setting port IO-02 to disabled on ['director-1-1-A'], updating SCIF on ['director-1-1-
A', 'director-2-1-B', 'director-2-1-A']

Setting port IO-02 to disabled on director-1-1-A

service@director-1-1-a:~>

Configure or change the LDAP or AD

This command allows the user to change or update the LDAP configuration of the current cluster.
WARNING: Running the vplex_system_config --start or vplex_system_config -s command on an
already configured system stops the node firmware, causing a Total Cluster Outage.

NOTE:
● Changing the LDAP should be done in a configured metro node, not in an unconfigured metro node.

92 Reconfigure Specific Parameters

Page 97 of 120
 ● To configure the LDAP/AD, only one group and user are required.
A user can perform the following operations:
1. Configure the LDAP - vplex_system_config -interview --ldap-config
2. Show LDAP configuration - vplex_system_config -interview --show-ldap-config
3. Add users - vplex_system_config -interview --add-users-ldap-config
4. Remove users - vplex_system_config -interview --remove-users-ldap-config
5. Add groups- vplex_system_config -interview --add-groups-ldap-config
6. Remove groups - vplex_system_config -interview --remove-groups-ldap-config
7. Reset the LDAP configuration - vplex_system_config -interview --reset-ldap-config
8. Update the LDAP/AD certificates - vplex_system_config -i --update-ldap-certs

Configure the LDAP

See the following steps:
1. Log in as a service user with the credentials in one of the nodes of the metro node.
2. Before running the command, ensure that the certificates you give must be downloaded using Managed File Transfer (MFT)
to /home/service/mft/.
3. To configure the LDAP, run the following command:
service@director-1-1-a:~> vplex_system_config -interview --ldap-config

service@director-1-1-a:~> vplex_system_config -interview --ldap-config

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.
LDAP/AD interview process started...

Below are the options to configure SSSD service configuration for the clusters:
1. cluster-1 only
2. cluster-2 only
3. Both clusters have same config
4. Both clusters have different config
Please select option: 3

Do you want to configure LDAP/AD (default: LDAP): LDAP

Enter 'cluster-1' details:
Server address (default: 10.227.240.55): 10.x.x.x
IP Address is validating, please wait...
Default search base (default: dc=ldapcore,dc=com): dc=ldapcore,dc=com
Bind dn (default: cn=admin,dc=ldapcore,dc=com): cn=admin,dc=ldapcore,dc=com
Default auth type: password
Bind password :
Choose certificate type to configure.
1. Self-signed certificate.
2. CA certificate. (default: self-signed): 1
Certificate (default: /etc/opt/dell/vplex/ldap_certs/ldapcacert.crt):
ldapcacert.crt
Simple allow users (default: testuser01):
User must be either in users/groups field
Proceeding with available users: testuser01
Simple allow groups (default: vatsgroup): NewGroup01
Proceeding with available groups: NewGroup01

Please review the cluster-1, details entered.

domain: ldap
server_address: 10.x.x.x
ldap_search_base: dc=ldapcore,dc=com
bind_dn: cn=admin,dc=ldapcore,dc=com
ldap_tls_cacertdir: /etc/opt/dell/vplex/ldap_certs/ldapcacert.crt
simple_allow_users: testuser01
simple_allow_groups: NewGroup01
ldap_default_authtok_type: password

Reconfigure Specific Parameters 93

Page 98 of 120
 Please review the cluster-2, details entered.

domain: ldap
server_address: 10.x.x.x
ldap_search_base: dc=ldapcore,dc=com
bind_dn: cn=admin,dc=ldapcore,dc=com
ldap_tls_cacertdir: /etc/opt/dell/vplex/ldap_certs/ldapcacert.crt
simple_allow_users: testuser01
simple_allow_groups: NewGroup01
ldap_default_authtok_type: password

Please review the above details. Do you want to proceed(y/n)? (default: y):

LDAP/AD interview process completed.

Update sssd config process started...
TASK: Gathering Facts - PASS
TASK: Create sssd configuration template - PASS
.
.
.
TASK: Retrieve "ldap_tls_cacertdir" from sssd configuration - PASS
TASK: Updating certificate path in sssd configuration - PASS
TASK: Updating ldap_tls_reqcert in sssd configuration for self-signed - PASS

PLAY RECAP
**************************************************************************************
***************************************************************
director-1-1-A|8K63Z23 : ok=12 changed=3 unreachable=0 failed=0
skipped=5 rescued=0 ignored=0
director-1-1-B|8K64Z23 : ok=12 changed=3 unreachable=0 failed=0
skipped=5 rescued=0 ignored=0
director-2-1-A|8K65Z23 : ok=12 changed=3 unreachable=0 failed=0
skipped=5 rescued=0 ignored=0
director-2-1-B|8K66Z23 : ok=12 changed=3 unreachable=0 failed=0
skipped=5 rescued=0 ignored=0

System configuration process for SSSD configuration is successful

Password obfuscate process started...
TASK: Gathering Facts - PASS
TASK: Set sssd obfuscate password - PASS
.
.
.
TASK: Setting preset to sssd service - PASS
TASK: Starting the sssd service - PASS

PLAY RECAP
**************************************************************************************
***************************************************************
director-1-1-A|8K63Z23 : ok=9 changed=2 unreachable=0 failed=0
skipped=4 rescued=0 ignored=0
director-1-1-B|8K64Z23 : ok=9 changed=2 unreachable=0 failed=0
skipped=4 rescued=0 ignored=0
director-2-1-A|8K65Z23 : ok=9 changed=2 unreachable=0 failed=0
skipped=4 rescued=0 ignored=0
director-2-1-B|8K66Z23 : ok=9 changed=2 unreachable=0 failed=0
skipped=4 rescued=0 ignored=0

System configuration process for SSSD obfuscate is successful

Password obfuscate process completed.

Show the LDAP configuration

See the following steps:
1. Log in as a service user with the credentials in one of the nodes of the metro node.
2. To show the LDAP configuration, run the following command:

94 Reconfigure Specific Parameters

Page 99 of 120
 service@director-1-1-a:~> vplex_system_config -interview --show-ldap-config

service@director-1-1-a:~> vplex_system_config -interview --show-ldap-config

LDAP config...
cluster: cluster-1
domain: ldap
server_address: 10.118.253.19
ldap_search_base: dc=ldapcore,dc=com
ldap_tls_cacertdir: /etc/openldap/cacerts/
simple_allow_users: newuser02
simple_allow_groups: NewGroup01

cluster: cluster-2
domain: AD
server_address: 10.228.67.30
ldap_search_base: dc=ldapcore,dc=com
bind_dn: cn=Administrator,CN=Users,DC=ldapcore,DC=com
ldap_tls_cacertdir: /etc/openldap/cacerts/
simple_allow_users: testuser01
simple_allow_groups: vatsgroup
ldap_default_authtok_type: password

SHOW LDAP config is completed.

service@director-1-1-a:~>

Add users
See the following steps:
1. Log in as a service user with the credentials in one of the nodes of the metro node.
2. To add users in the LDAP configuration, run the following command:
service@director-1-1-a:~> vplex_system_config -interview --add-users-ldap-config

service@director-1-1-a:~> vplex_system_config -interview --add-users-ldap-config

Taking backup of existing SCIF has been started...
Taking backup of existing SCIF has been completed.
LDAP/AD add users process started...
Enter user 'cluster-1' details:
bind password :
Simple allow users (please provide users with comma separated) (default:
newuser02): newuser03
Authentication failed

service@director-1-1-a:~> vplex_system_config -interview --add-users-ldap-config

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.
LDAP/AD add users process started...
Enter user 'cluster-1' details:
bind password :
Simple allow users (default: testuser01): testuser02
Proceeding with available users: testuser02
Enter user 'cluster-2' details:
bind password :
Simple allow users (default: testuser01): testuser02
Proceeding with available users: testuser02

TASK: Gathering Facts - PASS

TASK: Retrieve "simple_allow_users" from sssd configuration - PASS
TASK: Add all users in sssd configuration - PASS
.
.
.
TASK: Setting preset to sssd service - PASS

Reconfigure Specific Parameters 95

Page 100 of 120

 TASK: Starting the sssd service - PASS

PLAY RECAP
**************************************************************************************
***************************************************************
director-1-1-A|8K63Z23 : ok=11 changed=1 unreachable=0 failed=0
skipped=10 rescued=0 ignored=0
director-1-1-B|8K64Z23 : ok=11 changed=1 unreachable=0 failed=0
skipped=10 rescued=0 ignored=0
director-2-1-A|8K65Z23 : ok=11 changed=1 unreachable=0 failed=0
skipped=10 rescued=0 ignored=0
director-2-1-B|8K66Z23 : ok=11 changed=1 unreachable=0 failed=0
skipped=10 rescued=0 ignored=0

System configuration process for LDAP/AD update users is successful

Remove users
See the following steps:
1. Log in as a service user with the credentials in one of the nodes of the metro node.
2. To remove users in the LDAP configuration, run the following command:
service@director-1-1-a:~> vplex_system_config -interview --remove-users-ldap-config

service@director-1-1-a:~> vplex_system_config -interview --remove-users-ldap-config

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.
WARNING !!!
Running this command will remove ldap users parameters from the metro node. Do you
really want to continue?
Please type 'yes' to continue or 'no' to exit:yes
LDAP/AD remove users process started...
Enter user 'cluster-1' details:
bind password :
Simple allow users (default: testuser01,testuser02): testuser01
Proceeding with available users: testuser01
Enter user 'cluster-2' details:
bind password :
Simple allow users (default: testuser01,testuser02): testuser01
Proceeding with available users: testuser01

TASK: Gathering Facts - PASS

TASK: Retrieve "simple_allow_users" from sssd configuration - PASS
.
.
.
TASK: Reloading daemon - PASS
TASK: Setting preset to sssd service - PASS
TASK: Starting the sssd service - PASS

PLAY RECAP
**************************************************************************************
***************************************************************
director-1-1-A|8K63Z23 : ok=11 changed=1 unreachable=0 failed=0
skipped=10 rescued=0 ignored=0
director-1-1-B|8K64Z23 : ok=11 changed=1 unreachable=0 failed=0
skipped=10 rescued=0 ignored=0
director-2-1-A|8K65Z23 : ok=11 changed=1 unreachable=0 failed=0
skipped=10 rescued=0 ignored=0
director-2-1-B|8K66Z23 : ok=11 changed=1 unreachable=0 failed=0
skipped=10 rescued=0 ignored=0

System configuration process for LDAP/AD update users is successful

96 Reconfigure Specific Parameters

Page 101 of 120

Add groups
See the following steps:
1. Log in as a service user with the credentials in one of the nodes of the metro node.
2. To add groups in the LDAP configuration, run the following command:
service@director-1-1-a:~> vplex_system_config -interview --add-groups-ldap-config

service@director-1-1-a:~> vplex_system_config -interview --add-groups-ldap-config

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.
LDAP/AD add groups process started...
Enter user 'cluster-1' details:
bind password :
Simple allow groups (default: NewGroup01): vatsgroup
Proceeding with available groups: vatsgroup
Enter user 'cluster-2' details:
bind password :
Simple allow groups (default: NewGroup01): vatsgroup
Proceeding with available groups: vatsgroup

TASK: Gathering Facts - PASS

TASK: Retrieve "simple_allow_groups" from sssd configuration - PASS
TASK: Add all groups in sssd configuration - PASS
.
.
.
TASK: Setting preset to sssd service - PASS
TASK: Starting the sssd service - PASS

PLAY RECAP
**************************************************************************************
***************************************************************
director-1-1-A|8K63Z23 : ok=11 changed=1 unreachable=0 failed=0
skipped=10 rescued=0 ignored=0
director-1-1-B|8K64Z23 : ok=11 changed=1 unreachable=0 failed=0
skipped=10 rescued=0 ignored=0
director-2-1-A|8K65Z23 : ok=11 changed=1 unreachable=0 failed=0
skipped=10 rescued=0 ignored=0
director-2-1-B|8K66Z23 : ok=11 changed=1 unreachable=0 failed=0
skipped=10 rescued=0 ignored=0

System configuration process for LDAP/AD update groups is successful

Remove groups
See the following steps:
1. Log in as a service user with the credentials in one of the nodes of the metro node.
2. To remove groups in the LDAP configuration, run the following command:
service@director-1-1-a:~> vplex_system_config -interview --remove-groups-ldap-config

service@director-1-1-a:~> vplex_system_config -interview --remove-groups-ldap-config

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.
WARNING !!!
Running this command will remove ldap group parameters from the metro node. Do you
really want to continue?
Please type 'yes' to continue or 'no' to exit:yes
LDAP/AD remove groups process started...
Enter user 'cluster-1' details:
bind password :

Reconfigure Specific Parameters 97

Page 102 of 120

 Simple allow groups (default: vatsgroup,NewGroup01): NewGroup01
Proceeding with available groups: NewGroup01
Enter user 'cluster-2' details:
bind password :
Simple allow groups (default: vatsgroup,NewGroup01): NewGroup01
Proceeding with available groups: NewGroup01

TASK: Gathering Facts - PASS

TASK: Retrieve "simple_allow_groups" from sssd configuration - PASS
TASK: Add all groups in sssd configuration - PASS
.
.
.
TASK: Setting preset to sssd service - PASS
TASK: Starting the sssd service - PASS

PLAY RECAP
**************************************************************************************
***************************************************************
director-1-1-A|8K63Z23 : ok=11 changed=1 unreachable=0 failed=0
skipped=10 rescued=0 ignored=0
director-1-1-B|8K64Z23 : ok=11 changed=1 unreachable=0 failed=0
skipped=10 rescued=0 ignored=0
director-2-1-A|8K65Z23 : ok=11 changed=1 unreachable=0 failed=0
skipped=10 rescued=0 ignored=0
director-2-1-B|8K66Z23 : ok=11 changed=1 unreachable=0 failed=0
skipped=10 rescued=0 ignored=0

System configuration process for LDAP/AD update groups is successful

Reset the LDAP configuration

See the following steps:
1. Log in as a service user with the credentials in one of the nodes of the metro node.
2. To reset the LDAP configuration, run the following command:
service@director-1-1-a:~> vplex_system_config --interview --reset-ldap-config

service@director-1-1-a:~> vplex_system_config --interview --reset-ldap-config

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.
WARNING !!!
Running this command will reset the ldap parameters from the metro node. Do you
really want to continue?
Please type 'yes' to continue or 'no' to exit:no

exiting...
service@director-1-1-a:~>

service@director-1-1-a:~> vplex_system_config --interview --reset-ldap-config

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.
WARNING !!!
Running this command will reset the ldap parameters from the metro node. Do you
really want to continue?
Please type 'yes' to continue or 'no' to exit:yes
LDAP/AD reset config process started...
TASK: Erase sssd cache - PASS
.
.
.
TASK: Setting preset to sssd service - PASS
TASK: Stopping the sssd service - PASS

98 Reconfigure Specific Parameters

Page 103 of 120

 PLAY RECAP
**************************************************************************************
***************************************************************
director-1-1-A|8K63Z23 : ok=9 changed=2 unreachable=0 failed=0
skipped=2 rescued=0 ignored=0
director-1-1-B|8K64Z23 : ok=9 changed=2 unreachable=0 failed=0
skipped=2 rescued=0 ignored=0
director-2-1-A|8K65Z23 : ok=9 changed=2 unreachable=0 failed=0
skipped=2 rescued=0 ignored=0
director-2-1-B|8K66Z23 : ok=9 changed=2 unreachable=0 failed=0
skipped=2 rescued=0 ignored=0

System configuration process for LDAP/AD reset config is successful

service@director-1-1-a:~>

Update the LDAP/AD certificates

See the following steps:
1. Log in as a service user with the credentials in one of the nodes of the metro node.
2. Before running the command, ensure that the certificates you give must be downloaded using Managed File Transfer (MFT)
to /home/service/mft/.
3. To update the LDAP/AD certificates, run the following command:
service@director-1-1-a:~> vplex_system_config -i --update-ldap-certs

service@director-1-1-a:~> vplex_system_config -i --update-ldap-certs

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.
LDAP/AD updation of certificates process started...
Enter LDAP/AD certificate 'cluster-1' details:
Choose certificate type to update.
1. Self-signed certificate.
2. CA certificate. (default: self-signed): 3
Select either 1 or 2.
Choose certificate type to update.
1. Self-signed certificate.
2. CA certificate. (default: self-signed): 2
Certificate (please only provide the certificate name you want to update):
(default: /etc/opt/dell/vplex/ldap_certs/ldap_cert_chain.pem): Cert_chain.pem
Enter LDAP/AD certificate 'cluster-2' details:
Choose certificate type to update.
1. Self-signed certificate.
2. CA certificate. (default: self-signed): 2
Certificate (please only provide the certificate name you want to update):
(default: /etc/opt/dell/vplex/ldap_certs/AD_certchain.crt): AC_certs.crt/

SCIF has been copied to ['172.16.0.8', '172.16.0.9', '172.16.0.10', '172.16.0.11']

successfully.
[WARNING]: Skipping plugin (/usr/lib/python3.6/site-packages/ansible/plugins/
connection/saltstack.py) as it seems to be invalid:
The 'cryptography' distribution was not found and is required by ansible

PLAY [localhost]
**************************************************************************************
**************************

TASK [Gathering Facts]

**************************************************************************************
********************
ok: [localhost]

PLAY [cluster*]
**************************************************************************************
***************************

TASK [Gathering Facts]

Reconfigure Specific Parameters 99

Page 104 of 120

 **************************************************************************************
********************
[WARNING]: Platform linux on host 11000BB is using the discovered Python interpreter
at /usr/bin/python3.6, but future
installation of another Python interpreter could change this. See
https://docs.ansible.com/ansible/2.9/reference_appendices/interpreter_discovery.html
for more information.
ok: [11000BB]
[WARNING]: Platform linux on host 11000AA is using the discovered Python interpreter
at /usr/bin/python3.6, but future
installation of another Python interpreter could change this. See
https://docs.ansible.com/ansible/2.9/reference_appendices/interpreter_discovery.html
for more information.
ok: [11000AA]
[WARNING]: Platform linux on host 12000BB is using the discovered Python interpreter
at /usr/bin/python3.6, but future
installation of another Python interpreter could change this. See
https://docs.ansible.com/ansible/2.9/reference_appendices/interpreter_discovery.html
for more information.
ok: [12000BB]
[WARNING]: Platform linux on host 12000AA is using the discovered Python interpreter
at /usr/bin/python3.6, but future
installation of another Python interpreter could change this. See
https://docs.ansible.com/ansible/2.9/reference_appendices/interpreter_discovery.html
for more information.
ok: [12000AA]

TASK [cfg_sssd_update : include_tasks]

**************************************************************************************
****
skipping: [11000AA]
skipping: [11000BB]
skipping: [12000AA]
skipping: [12000BB]

TASK [cfg_sssd_update : include_tasks]

**************************************************************************************
****
skipping: [11000AA]
skipping: [11000BB]
skipping: [12000AA]
skipping: [12000BB]

TASK [cfg_sssd_update : include_tasks]

**************************************************************************************
****
included: /opt/dell/vplex/system_config/ansible/roles/cfg_sssd_update/tasks/certs.yml
for 11000AA, 11000BB, 12000AA, 12000BB

TASK [cfg_sssd_update : extracting certificate]

*********************************************************************************
ok: [11000BB]
ok: [12000BB]
ok: [12000AA]
ok: [11000AA]

TASK [cfg_sssd_update : Copying the certificates to destination]

****************************************************************
ok: [11000BB]
ok: [12000AA]
ok: [12000BB]
ok: [11000AA]

TASK [cfg_sssd_update : Checking if the certificate exists]

*********************************************************************
ok: [11000BB]
ok: [11000AA]
ok: [12000BB]
ok: [12000AA]

TASK [cfg_sssd_update : Retrieve "ldap_tls_cacertdir" from sssd configuration]

**************************************************
[WARNING]: Consider using 'become', 'become_method', and 'become_user' rather than

100 Reconfigure Specific Parameters

Page 105 of 120

running sudo
ok: [11000AA]
ok: [12000AA]
ok: [11000BB]
ok: [12000BB]

TASK [cfg_sssd_update : Add "ldap_tls_cacertdir" string in sssd configuration]

**************************************************
skipping: [11000AA]
skipping: [11000BB]
skipping: [12000AA]
skipping: [12000BB]

TASK [cfg_sssd_update : Updating certificate path in sssd configuration]

********************************************************
ok: [11000AA]
ok: [11000BB]
ok: [12000AA]
ok: [12000BB]

TASK [cfg_sssd_update : Updating ldap_tls_reqcert in sssd configuration for self-

signed] ****************************************
skipping: [11000AA]
skipping: [11000BB]
skipping: [12000AA]
skipping: [12000BB]

TASK [cfg_sssd_update : Updating ldap_tls_reqcert in sssd configuration for CA

signed] ******************************************
ok: [11000AA]
ok: [11000BB]
ok: [12000BB]
ok: [12000AA]

TASK [cfg_sssd_service : include_tasks]

**************************************************************************************
***
included: /opt/dell/vplex/system_config/ansible/roles/cfg_sssd_service/tasks/
configure.yml for 11000AA, 11000BB, 12000AA, 12000BB

TASK [cfg_sssd_service : Setting ldap variable]

*********************************************************************************
ok: [11000AA]
ok: [11000BB]
ok: [12000AA]
ok: [12000BB]

TASK [cfg_sssd_service : Adding enable sssd in preset]

**************************************************************************
ok: [12000BB]
ok: [12000AA]
ok: [11000AA]
ok: [11000BB]

TASK [cfg_sssd_service : Removing disable sssd in preset]

***********************************************************************
ok: [11000BB]
ok: [11000AA]
ok: [12000AA]
ok: [12000BB]

TASK [cfg_sssd_service : Adding disable sssd in preset during opt out any of the
cluster] ***************************************
skipping: [11000AA]
skipping: [11000BB]
skipping: [12000AA]
skipping: [12000BB]

TASK [cfg_sssd_service : Removing enable sssd in preset during opt out any of the
cluster] **************************************
skipping: [11000AA]
skipping: [11000BB]
skipping: [12000AA]

Reconfigure Specific Parameters 101

Page 106 of 120

 skipping: [12000BB]

TASK [cfg_sssd_service : Reloading daemon]

**************************************************************************************
ok: [11000AA]
ok: [11000BB]
ok: [12000AA]
ok: [12000BB]

TASK [cfg_sssd_service : Setting preset to sssd service]

************************************************************************
ok: [11000BB]
ok: [11000AA]
ok: [12000AA]
ok: [12000BB]

TASK [cfg_sssd_service : Starting the sssd service]

*****************************************************************************
ok: [11000BB]
ok: [12000AA]
ok: [11000AA]
ok: [12000BB]

TASK [cfg_sssd_service : Stopping the sssd service during opt out any of the cluster]
*******************************************
skipping: [11000AA]
skipping: [11000BB]
skipping: [12000AA]
skipping: [12000BB]

TASK [cfg_sssd_service : include_tasks]

**************************************************************************************
***
skipping: [11000AA]
skipping: [11000BB]
skipping: [12000AA]
skipping: [12000BB]

PLAY RECAP
**************************************************************************************
********************************
11000AA : ok=15 changed=0 unreachable=0 failed=0
skipped=8 rescued=0 ignored=0
11000BB : ok=15 changed=0 unreachable=0 failed=0
skipped=8 rescued=0 ignored=0
12000AA : ok=15 changed=0 unreachable=0 failed=0
skipped=8 rescued=0 ignored=0
12000BB : ok=15 changed=0 unreachable=0 failed=0
skipped=8 rescued=0 ignored=0
localhost : ok=1 changed=0 unreachable=0 failed=0
skipped=0 rescued=0 ignored=0

LDAP/AD updation of certificates process completed...

Configure or change SSH Keys

See the following steps:
1. Log in as a service user with the credentials in one of the nodes of the metro node.
2. To configure or change SSH keys, run the following command:
service@director-1-1-a:~> vplex_system_config --update-sshkey

service@director-1-1-a:~> vplex_system_config --update-sshkey

service@director-1-1-b:/opt/dell/vplex/system_config/bin> vplex_system_config --
update-sshkey
Starting the generation of sshkey
Taking backup of existing SCIF has been started...

102 Reconfigure Specific Parameters

Page 107 of 120

Taking backup of existing SCIF has been completed.
Enter service password for cluster cluster-1:
Enter service password for cluster cluster-2:
Enabling passwordless SSH between the nodes...
Clearing existing files on node(director-1-1-A), with 10.226.102.101
Clearing existing files on node(director-1-1-B), with 10.226.102.102
Clearing existing files on node(director-2-1-B), with 10.226.102.104
Clearing existing files on node(director-2-1-A), with 10.226.102.103
Generating SSH key on node(director-1-1-A), with 10.226.102.101
Generating SSH key on node(director-1-1-B), with 10.226.102.102
Generating SSH key on node(director-2-1-B), with 10.226.102.104
Generating SSH key on node(director-2-1-A), with 10.226.102.103
Exchanging the key with other nodes from node(director-1-1-A), with
10.226.102.101
Exchanging the key with other nodes from node(director-1-1-B), with
10.226.102.102
Exchanging the key with other nodes from node(director-2-1-B), with
10.226.102.104
Exchanging the key with other nodes from node(director-2-1-A), with
10.226.102.103
Enabled passwordless SSH successfully between the nodes.

If the Setup has CWS configured. Enter the root password of CWS host.

Enter root password for CWS VM:

Exchanging ssh keys from 10.226.102.101 to cws 10.244.118.168 is successful
Exchanging ssh keys from 10.226.102.102 to cws 10.244.118.168 is successful
Exchanging ssh keys from 10.226.102.104 to cws 10.244.118.168 is successful
Exchanging ssh keys from 10.226.102.103 to cws 10.244.118.168 is successful
Enabled passwordless SSH successfully between node and CWS
Generation of sshkey completed

Reconfigure Specific Parameters 103

Page 108 of 120

 5
Logs
Topics:
• SCIF File and Logs

SCIF File and Logs

See the logs and SCIF file that is generated during the system configuration process.
● SCIF-scif.yml is the overall system configuration for the local and metro cluster.
/etc/opt/dell/vplex/scif.yml
● SCIF latest backup- scif.yml.bak is created at the end of each interview process. It is a backup of the latest
scif.yml and it is same across the nodes.
/etc/opt/dell/vplex/scif.yml.bak
● SCIF existing backup- scif.yml.1 is created at the beginning of the interview process. It is a backup of the
existing scif.yml file. It is same across the nodes. The existing backup file is created in a local node where the
interview process is triggered. Maximum 10 existing backup are created after that it will be rotated.
/etc/opt/dell/vplex/scif.yml.1 to /etc/opt/dell/vplex/scif.yml.10
● Python Logs-Contains all the logs related to collection/interview phase
To collect the journald logs(Python Logs ) or SCIF, run the following command to do the same:

service@localhost:/opt/dell/vplex/system_config/ansible> sudo journalctl -t SCIF -f

● Ansible Logs-Contains all the logs related to configuration phase done through ansible playbooks
For Ansible logs, see the log file /var/log/vplex/system_config/system_config.log.

104 Logs

Page 109 of 120

 6
DNS configuration
NOTE:
1. It is an optional configuration. It can be done in the last phase of system configuration.
2. It can be configured independently after the system configuration.
3. Before you go to the interview phase, keep the DNS IP address values handy.

Topics:
• Interview phase

Interview phase
Follow these steps for configuring DNS:
WARNING: Running the vplex_system_config --start or vplex_system_config -s command on an
already configured system stops the node firmware, causing a Total Cluster Outage.
1. Log in to metro node as a service user.
2. To configure DNS, run the command vplex_system_config -interview --dns-config.

service@director-1-1-A:/> vplex_system_config -interview --dns-config

Taking backup of existing SCIF has been started...

Taking backup of existing SCIF has been completed.
DNS interview process is started...

Below are the options to configure DNS configuration for the clusters:
1. cluster-1 only
2. cluster-2 only
3. Both clusters have same DNS config
4. Both clusters have different DNS config
Please select option: 4

Enter the details for cluster-1

Enter the primary DNS IP: 11.11.11.11
Enter (true/false) to set up secondary ip (default: True):
Enter the secondary DNS IP: 22.22.22.22

Enter the details for cluster-2

Enter the primary DNS IP: 33.33.33.33
Enter (true/false) to set up secondary ip (default: True):
Enter the secondary DNS IP: 44.44.44.44

Please review the DNS details entered.

DNS details for cluster-1

Primary DNS IP: 11.11.11.11
Secondary DNS IP: 22.22.22.22
DNS details for cluster-2
Primary DNS IP: 33.33.33.33
Secondary DNS IP: 44.44.44.44

Please review the above details. Do you want to proceed(y/n)? (default: y):

SCIF has been copied to ['10.x.x.x', '10.x.x.x', '10.x.x.x', '10.x.x.x'] successfully.

DNS interview process is completed.

DNS configuration 105

Page 110 of 120

 PLAY [localhost]
**************************************************************************************
********************************************************

TASK [Gathering Facts]

**************************************************************************************
**************************************************
ok: [localhost]

PLAY [all]
**************************************************************************************
**************************************************************

TASK [Gathering Facts]

**************************************************************************************
**************************************************
[WARNING]: Platform linux on host 11000BB is using the discovered Python interpreter
at /usr/bin/python3.6, but future installation of another Python
interpreter could change this. See https://docs.ansible.com/ansible/2.9/
reference_appendices/interpreter_discovery.html for more information.
ok: [11000BB]
[WARNING]: Platform linux on host 12000AA is using the discovered Python interpreter
at /usr/bin/python3.6, but future installation of another Python
interpreter could change this. See https://docs.ansible.com/ansible/2.9/
reference_appendices/interpreter_discovery.html for more information.
ok: [12000AA]
[WARNING]: Platform linux on host 12000BB is using the discovered Python interpreter
at /usr/bin/python3.6, but future installation of another Python
interpreter could change this. See https://docs.ansible.com/ansible/2.9/
reference_appendices/interpreter_discovery.html for more information.
ok: [12000BB]
[WARNING]: Platform linux on host 11000AA is using the discovered Python interpreter
at /usr/bin/python3.6, but future installation of another Python
interpreter could change this. See https://docs.ansible.com/ansible/2.9/
reference_appendices/interpreter_discovery.html for more information.
ok: [11000AA]

TASK [cfg_dns : include_tasks]

**************************************************************************************
******************************************
included: /opt/dell/vplex/system_config/ansible/roles/cfg_dns/tasks/configure.yml for
11000AA, 11000BB, 12000AA, 12000BB

TASK [cfg_dns : Adding DNS value in config file when dns defined for cluster.]
********************************************************************************
changed: [11000BB]
changed: [12000BB]
changed: [12000AA]
changed: [11000AA]

TASK [cfg_dns : clearing DNS value in config file when dns is not defined for
cluster.] ***********************************************************************
skipping: [11000AA]
skipping: [11000BB]
skipping: [12000AA]
skipping: [12000BB]

TASK [cfg_dns : Execute netconfig update command]

**************************************************************************************
***********************
[WARNING]: Consider using 'become', 'become_method', and 'become_user' rather than
running sudo
ok: [11000BB]
ok: [12000AA]
ok: [12000BB]
ok: [11000AA]

TASK [cfg_dns : include_tasks]

**************************************************************************************
******************************************
skipping: [11000AA]
skipping: [11000BB]

106 DNS configuration

Page 111 of 120

 skipping: [12000AA]
skipping: [12000BB]

PLAY RECAP
**************************************************************************************
**************************************************************
11000AA : ok=4 changed=1 unreachable=0 failed=0
skipped=2 rescued=0 ignored=0
11000BB : ok=4 changed=1 unreachable=0 failed=0
skipped=2 rescued=0 ignored=0
12000AA : ok=4 changed=1 unreachable=0 failed=0
skipped=2 rescued=0 ignored=0
12000BB : ok=4 changed=1 unreachable=0 failed=0
skipped=2 rescued=0 ignored=0
localhost : ok=1 changed=0 unreachable=0 failed=0
skipped=0 rescued=0 ignored=0

DNS is configured successfully.

Output
The DNS IP address is visible in /etc/resolv.conf file with the following format:

service@director-1-1-A:~> vi /etc/resolv.conf

### /etc/resolv.conf is a symlink to /var/run/netconfig/resolv.conf

### autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
# NETCONFIG_DNS_STATIC_SEARCHLIST
# NETCONFIG_DNS_STATIC_SERVERS
# NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
# NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
### Call "netconfig update -f" to force adjusting of /etc/resolv.conf.
nameserver 11.11.11.11
nameserver 22.22.22.22

DNS configuration 107

Page 112 of 120

 7
Post Upgrade
Post metro node configuration the Dell Employees and the Partners must update the Global Asset Management (GAM) with the
generated Cluster Serial Number (GUID) by following the procedure that is given below.
Topics:
• Process Overview for Updating GAM
• Get DST and GUID using UI method
• Get DST and GUID using CLI method
• Submitting a Case to GAM Team

Process Overview for Updating GAM

Steps
1. Record your Dell Service Tags (DST), Cluster Serial number (GUID), both if metro node-Metro, and the version details of the
metro node following either the UI Method or CLI Method.
NOTE: GUID stands for Global Unique IDentifier.

2. See Submitting a case to GAM team to open an administrative support case with GAM, using one of the Dell Service Tag
numbers to register all DSTs, Cluster Serial numbers, and version details.

Get DST and GUID using UI method

Follow the below to find the Cluster DSTs, serial number (GUID), and the code version once the installation completes using the
UI.

Steps
1. Using the public IP Address (https://xx.xx.xx.xx) for the metro node, login to a web browser using the service username and
password.

Figure 11. Login Screen

2. The metro node UI Dashboard opens. At the bottom of the dashboard, you can see the information about each Cluster. Take
note of the Serial Number (GUID), the Dell Service tags (DSTs), and the Version Details as these are used during the case
creation.

108 Post Upgrade

Page 113 of 120

 Figure 12. Metro Node Dashboard

Get DST and GUID using CLI method

Follow the below to find the Cluster DSTs, serial number (GUID), and the code version once the installation has been completed
using the VPlexcli.

Steps
1. Using the public IP Address (https://xx.xx.xx.xx) for the metro node, login to a web browser using the service username and
password.
NOTE: As the service account password was changed during the installation, you must check with the customer for the
password, if you do not have it.
Example:

login as: service

Keyboard-interactive authentication prompts from server:
| Password:
End of keyboard-interactive prompts from server
Last login: Tue Apr 4 05:13:13 2023 from x.x.x.x
service@director-1-1-a:~>

2. Now, log in the VPlexcli by typing vplexcli.

Example:

service@director-1-1-b:~> vplexcli
Trying ::1...
Connected to localhost.
Escape character is '^]'.

VPlexcli:/>

3. To get a list of the DSTs for all directors in the entire setup (both clusters if a metro configuration), run the command ls
-t /clusters/*/directors/*/::serial-number .
Example:

VPlexcli:/> ls -t /clusters/*/directors/*/::serial-number

/clusters/cluster-2/directors/director-2-1-B:
Name Value
------------- -------
serial-number 9WVWxx3 <-- the Dell Service Tag (DST)

/clusters/cluster-2/directors/director-2-1-A:
Name Value
------------- -------
serial-number 9WVVxx3

/clusters/cluster-1/directors/director-1-1-B:
Name Value

Post Upgrade 109

Page 114 of 120

 ------------- -------
serial-number 9WVTxx3

/clusters/cluster-1/directors/director-1-1-A:
Name Value
------------- -------
serial-number 9WVSxx3

4. To get the GUID for each cluster in the setup, run the command ls -t /clusters/*/::top-level-assembly .
Example:

VPlexcli:/> ls -t /clusters/*/::top-level-assembly

/clusters/cluster-2:
Name Value
------------------ -------
top-level-assembly 4EUWxx0 <-- the GUID

/clusters/cluster-1:
Name Value
------------------ -------
top-level-assembly 4EUTxx0

5. To get the version of metro node operating system running, run the following command from the VPlexcli prompt
version .
Example:

VPlexcli:/> version
Node Version Platform MNFB
-------------- ------------ ----------- -----------------
cws 8.0.0.1.0-21 SLES 15-SP3 n/a
director-1-1-A 8.0.0.1.0-21 mn-114 mn-114_Feb_CY23_0
director-1-1-B 8.0.0.1.0-21 mn-114 mn-114_Feb_CY23_0
director-2-1-A 8.0.0.1.0-21 mn-114 mn-114_Feb_CY23_0
director-2-1-B 8.0.0.1.0-21 mn-114 mn-114_Feb_CY23_0

Submitting a Case to GAM Team

Follow the below procedure to submit a case to the Global Asset Management (GAM) team.

Steps
1. Go to Administrative Support, and ensure that you are signed in as a partner or an employee.
NOTE: The Administrative Support can be found on SUPPORT/INCIDENTS-ONLINE/ADM-SUPPORT.

2. Once you are signed in, you can see the Administrative Support options. Click the More Support & Solutions section to
proceed. If you are not logged in, only a limited list of options are available.

Figure 13. Administrative Support

3. In the Tell us more drop-down list, select Install Base/Asset Maintenance. Then enter one of your Dell Service Tags
(DST).

110 Post Upgrade

Page 115 of 120

 Figure 14. Tell us more

4. In the Provide the appropriate ID relevant to your issue drop-down list, select Service Tag/Express Service.

Figure 15. Field to provide ID

5. Now, in the field to the right, enter a DST and click Submit.

Figure 16. Service Tag/Express Service

6. Click Create Service Request button to proceed.

Figure 17. Create Service Request

7. Ensure Customer Information, and Service tag are correct. For Quantity of Assets Affected, include the count of all
Dell Service tags in your request.

Post Upgrade 111

Page 116 of 120

 Figure 18. Customer Information

8. Under Case Details select the following options from the drop-down menus. Enter your description as per the template
provided below, and submit your request.

Figure 19. Request Description

● Select Issue: Asset Maintenance/Order Management

● Select Details: Create Asset/Missing Asset.
● Select Type: Hardware
● Request Description:

112 Post Upgrade

Page 117 of 120

 Figure 20. Case Details

9. Enter the required details, and click Submit.

Post Upgrade 113

Page 118 of 120

Index
A M
Accept EULA 15 mn-114 6
Add groups 97 mn-215 7
Add users 95
Apply changes to SupportAssist configuration 55
N
B name of the cluster 79

Bridged WAN 48
P
C Pre-configuration Phases 15
Public IP Address 78
Change the NTP server IP 65
Change the SSL certificate for cust_signed 86
Change the SSL certificates for self_signed 85
R
Change the WAN COM 66 Remove groups 97
Configure the LDAP 93 Remove users 96
Connect through iDRAC Direct Micro-USB port 12 Remove WAN COM 77
Connect through SVC port 10 Reset SSL Certificates 88
Reset the LDAP configuration 98
D
Disable port for all directors 92
S
Disable port for one cluster 91 service user password 84
Disable port for one director 90 SMTP 59
Disable SupportAssist Configuration 58 Step 1: Interview (SupportAssist configuration) 55
Submitting a Case to GAM Team 110
E
enable and disable 89
T
Enable port for all directors 91 Task 2: Interview (phase 1) 16
Enable port for one cluster 90 Task 3: Apply changes (phase 1) 20
Enable port for one director 90 Task 4: Backend path zoning configuration 22
Enable SupportAssist Configuration 57 Task 5: Interview (phase 2) 24
Exclude one or more directors 92 Task 6: Apply Changes (phase 2) 38
Task 7: Create Metavolume Backup 39
F Topology change (Applicable only for mn-215) 71

FC WAN(configuration for mn215) 33

U
H Update SupportAssist configurations 58
User input details for system configuration 9
Help Command 63
High-Level Overview 5
V
I View SupportAssist configuration details 57
Volume pre-requisites 9
iDRAC password 83
IP WAN Configuration details (for mn-114) 42
IP WAN(configuration for mn114) 24, 29

L
login banner 82

Page 119 of 120

Dell Technologies – Restricted Use – Confidential & Subject to NDA

Page 120 of 120