Vision 3 5 1 Installation

Dell EMC Vision Intelligent Operations
Version 3.5.1
Installation Guide
Document revision 2.0

February 2017
DELL EMC CONFIDENTIAL

Subject to Confidentiality Use Restrictions
Revision history
Date Document revision Description of changes
April 2017 2.0 Minor editorial change
February 2017 1.0 New release of the product
Revision history | 2
Contents
Introduction................................................................................................................................................. 6
System requirements................................................................................................................................. 7
Installing and configuring the Vision Core VM........................................................................................ 9

Preparing for installation.........................................................................................................................9
Downloading the OVA file for the Vision Core VM...........................................................................9
Downloading compliance content for the Vision Core VM............................................................... 9
Deploying, starting and configuring the Vision Core VM...................................................................... 10
Deploying the Vision Core VM....................................................................................................... 10
Starting the Vision Core VM...........................................................................................................21
Configuring Vision software with a second Ethernet adapter........................................................ 22
Connecting to the Vision Core VM.................................................................................................24
Configuring Vision software IP information for a second Ethernet adapter................................... 25
Verifying the Vision Core VM successfully deployed..................................................................... 30
Checking network properties for the Vision Core VM.................................................................... 31
Verifying the version of the Vision Core VM.................................................................................. 33
Verifying RPM file signing keys......................................................................................................33
Accepting the end user license agreement (EULA)....................................................................... 35
Configuring Vision software to discover Vblock System components..................................................37
Configuring the vblock.xml file....................................................................................................... 37
Generating the vblock.xml file automatically................................................................................101
Modifying the vblock.xml file........................................................................................................ 102
Configuring Vision software to discover VxBlock System and VxRack System components............ 103
Configuration editor overview...................................................................................................... 103
Configuring a VxRack System when a configuration file is not available.....................................104
Ensuring ScaleIO 2.0 discovery...................................................................................................105
Configuring a VxBlock System or a VxRack System when a configuration file is available........ 105
Editing component properties with the configuration editor......................................................... 106
Adding a component with the configuration editor....................................................................... 107
Deleting a component with the configuration editor..................................................................... 109
Configuration editor component reference...................................................................................109
Configuring VCE System components for Vision software discovery................................................ 121
Configuring the Converged Technology Extension for Isilon storage.......................................... 121
Configuring Red Hat Enterprise Linux for discovery.................................................................... 124
Configuring the IPI appliance for discovery................................................................................. 125
Creating a Vision software user in the VxRack Controller........................................................... 125
Configuring Vision software................................................................................................................127
Enabling northbound communication through SNMP.................................................................. 127
Updating the IP tables on the Vision Core VM.............................................................................128
Installing compliance content on the Vision Core VM........................................................................ 129
Starting VCE System discovery......................................................................................................... 131
Verifying SNMP communication.................................................................................................. 132
Confirming discovery is complete................................................................................................ 133
Verifying VCE System discovery................................................................................................. 134
Installing the Vision Plug-in for vCenter............................................................................................. 135
3 | Contents
Configuring the Vision Plug-in Manager...................................................................................... 135
Installing the Plug-in for vCenter..................................................................................................137
Configuring the Plug-in for vCenter..............................................................................................139
Verifying the Plug-in for vCenter installation................................................................................ 140
Troubleshooting the Vision Core installation...................................................................................... 141
Restarting Vision software services with Puppet......................................................................... 141
Starting and stopping services on the Vision Core VM................................................................142
Creating a task to back up the configuration databases (Vision software 2.5.1+)....................... 142
Backing up VMAX configuration files........................................................................................... 144
Manually deploying the Compliance Checker on Vision Core..................................................... 145
Manually clearing the work directory associated with the Plug-in for vCenter............................. 146
Installing and configuring the multisystem management (MSM) VM................................................ 147

About the MSM environment..............................................................................................................147
Preparing for installation.....................................................................................................................147
Downloading the OVA for the MSM VM.......................................................................................147
Deploying the MSM VM......................................................................................................................147
Monitoring the MSM VM setup........................................................................................................... 159
Connecting to the MSM VM............................................................................................................... 161
Associating a Vision Core VM with an existing MSM VM...................................................................162
Starting the Vision dashboard............................................................................................................ 163
Enabling software modules................................................................................................................ 164
Enabling the RCM Management module..................................................................................... 164
Enabling the Security Hardening module ....................................................................................165
Uploading compliance content........................................................................................................... 166
Installing the Dell EMC Vision shell Security Hardening Remediation Extension Pack..................... 167
Updating a compliance profile on the MSM node...............................................................................168
Installing and configuring the multisystem prepositioning (MSP) VM for the RCM content
prepositioning feature............................................................................................................................ 170
Preparing for installation.....................................................................................................................170
Downloading the OVA file for the multisystem prepositioning virtual machine............................ 170
Deploying the MSP OVA.................................................................................................................... 170
Monitoring the MSP VM setup............................................................................................................182
Connecting to the MSP VM................................................................................................................ 183
Checking network properties for the MSP VM................................................................................... 184
Verifying the MSP VM deployed successfully.................................................................................... 184
Completing the Vision software installation........................................................................................ 186

Resetting the end user license agreement (EULA)............................................................................ 186
Configuring ESRS for Vision software................................................................................................. 187

Retrieving the software ID from the Licensing system....................................................................... 187
Registering Vision software with an ESRS gateway.......................................................................... 188
Adding a software identifier for an MSM VM...................................................................................... 191
Configuration file format and examples............................................................................................... 193

Configuration file (.cfg) format............................................................................................................ 193
Vblock System configuration file example..........................................................................................202
VxBlock System configuration file examples......................................................................................204
Contents | 4
VxRack System configuration file examples...................................................................................... 215
5 | Contents
Introduction
This document provides instructions for installing Dell EMC Vision Intelligent Operations, which includes
the Vision Core VM, the multisystem management (MSM) VM, and the multisystem prepositioning (MSP)
VM.
The target audience for this document is the person responsible for installing Vision software.
Important: Do not copy and paste the commands outlined in this guide without first modifying them to
suit your needs.
Refer to the Glossary for terms, definitions, and acronyms.
Introduction | 6
System requirements
The system requirements specify the minimum support required for the Vision Core VM, the multisystem
management (MSM) VM, and the multisystem prepositioning (MSP) VM.
VM Memory requirement vCPUs Disk size (GB)

(GB)
Vision Core VM 8 2 200
MSM VM 12 4 250
MSP VM 1 2 250
The Vision Core VM, MSM VM, and MSP VMs can be installed on the following Advanced Management
Platforms (AMP) and storage types:
Logical AMP - Vblock System storage array
HA-AMP version 1 - VNXe3100
HA-AMP version 2 - VNXe3150
AMP-2V - Vblock System storage array
AMP-2P - C-Series local storage
AMP-2RP - C-Series local storage
AMP-2HA - VNXe3200
AMP-2LP - C-Series local storage
AMP-2S - VNXe storage
Use the attended configuration tool to configure AMP-2S on the Vblock System 240.
Use the unattended configuration tool to configure AMP-2S on the following systems:
VxBlock System 240
Vblock System 350 and VxBlock System 350
AMP-3V - Vblock System storage array
AMP-3P - C-Series local storage
VxRack Controller - Management servers local storage
7 | System requirements
You must consider the following when deploying the Vision Core VM, MSM VM, and MSP VMs:
When deploying on AMP, the RAM size must be greater than or equal to 128 GB. If the RAM is
less than 128 GB, the AMP must be upgraded to a minimum of 128 GB of RAM. Contact VCE
Support for assistance when upgrading the AMP: https://support.vce.com/
It is recommended to use NFS mount from the storage array for the MSP VM, where available.
For AMP, VNXe3100 and VNXe3150 leverage the local storage capacity. Storage can be added
and is documented by Cisco but this might add downtime.
Depending on the VCE System, the Vision Core, MSM, and MSP VMs can be installed on either a logical
or physical AMP as described in the following table:
VCE System Logical AMP Physical AMP
Vblock System 100 Yes No
Vblock System 200 Yes Yes
Vblock System 240 Yes Yes
VxBlock System 240 Yes Yes
Vblock System 300 series No Yes
VxBlock System 340 No Yes
Vblock System 540 No Yes
Vblock System 700 series No Yes
VxRack System with FLEX No Yes
System requirements | 8
Installing and configuring the Vision Core VM
Preparing for installation
Downloading the OVA file for the Vision Core VM

The first step in the installation process is to download the Open Virtual Appliance (OVA) file for the
Vision Core VM. After you download the OVA file, you can deploy the Vision Core VM.
Before you begin
Verify that you can access the VCE Download Center where the OVA file resides.
Ensure that a valid DNS is configured.
Procedure
1 Connect to the VCE Download Center. Use either Secure Copy (SCP) or SSH File Transfer
Protocol (SFTP) as appropriate.
2 Navigate to the location of the Vision Core VM OVA file.
3 Download the OVA file to a location where you can access it from the VMware vSphere Client.
The vSphere Client is installed as part of the VMware vCenter Server infrastructure on the VCE
System.
Download time: The OVA file is more than 1 GB in size. The download process can take several
minutes depending on your network conditions.
Downloading compliance content for the Vision Core VM

Compliance content is not included on the Vision Core VM by default. You must separately download the
RPM Package Manager (RPM) files that contain the appropriate compliance content before you install it
on the Vision Core VM.
Before you begin
Verify that you can access the VCE Download Center where the compliance content RPM files reside.
Procedure
1 Connect to the VCE Download Center. Use either Session Control Protocol (SCP) or SSH File
Transfer Protocol (SFTP) as appropriate.
9 | Installing and configuring the Vision Core VM

2 Navigate to the location of the compliance content RPM files that you want to download.
Vision software includes different files for various types of compliance content, as in the following
examples:
vce-compliance-content-version_number.rpm
vce-compliance-content-hardening-version_number.rpm
3 Download the compliance content to a location where you can transfer it to the Vision Core VM.
Related information
Installing compliance content on the Vision Core VM (see page 129)
Uploading compliance content (see page 166)
Deploying, starting and configuring the Vision Core VM
Deploying the Vision Core VM

Deploying the Vision Core VM installs Vision software on the VCE System.
About this task

The Vision Core VM is packaged as an OVA file. To deploy the Vision Core VM, you use the VMware
vSphere Client to select the OVA file and then specify deployment and network properties. The vSphere
Client is installed as part of the VMware vCenter Server infrastructure on the VCE System.
Important: The steps in this document provide images of the deployment process. These images are for
illustrative purposes only. Refer to the Logical Configuration Survey (LCS) for virtual machine
settings as appropriate.
Before you begin
Download the OVA file.
Confirm that you can access the vSphere Client running on the VCE System.
Ensure that the version of the vSphere Client matches the version specified in the Release
Certification Matrix (RCM) for that VCE System.
Ensure that you have the LCS.
Ensure that you have reviewed the System requirements (see page 7).
You need the following information to deploy the Vision Core VM:
Information Description
OVA source Location where you downloaded the Vision software OVA file. Alternatively,
you can use a URL if the OVA is available on the network.
Installing and configuring the Vision Core VM | 10

Name of the virtual machine Display name of the Vision Core VM.
Available in the LCS.
Location of the virtual machine Data center in the inventory where the virtual machine resides.
Host or cluster ESX or ESXi host for the virtual machine.

If the host has a resource pool available, the vSphere Client prompts you to
select it during deployment.
Storage Location where the virtual machine saves files.
Network mapping Network that the virtual machine uses.

Network properties FQDN, IP address, gateway server, netmask, DNS, and NTP server for the
virtual machine.
Procedure
1 Start the vSphere Client.
2 Select the vCenter Server host.
a Select Inventory > Hosts and Clusters.
b Locate the vCenter Server host at the top of the navigation tree.
c Select the vCenter host.
3 Select File > Deploy OVF Template. The Deploy OVF Template window opens.
4 Select the source location of the OVA file.
a Select Browse. A new window opens to let you navigate the file system.
b Locate and select the OVA file on the file system and click Open.

c Verify the file name and location and click Next.
5 Verify the template details for the Vision Core VM.
a Confirm the version of the Vision Core VM.

b Verify that the vendor and publisher display as VCE Company, LLC and click Next.
This field indicates if the OVA was correctly signed using the VCE SSL certificate.
The vSphere Client attempts to verify the VCE SSL certificate with the issuing authority,
starfieldtech.com. If it can successfully verify the VCE SSL certificate, the vSphere Client
displays a green check mark in the Publisher field.
If it cannot contact the issuing authority, the vSphere Client does not verify the VCE SSL
certificate. If you are installing Vision software in a closed network and cannot access the
issuing authority directly from a browser, you should proceed with the deployment.
If you have network access, but cannot successfully validate the VCE SSL certificate, it
indicates a security issue with the OVA. Contact VCE Support.
6 Specify the name and location of the Vision Core VM.
a Type the display name of the Vision Core VM in the Name field. Refer to the LCS for the
display name.

b Select the data center for the virtual machine in the Inventory Location pane and click Next.

7 Select the ESX or ESXi host or cluster for the virtual machine and click Next.

8 If available, select the resource pool for the virtual machine and click Next.
The vSphere Client prompts you to select a resource pool only if one or more are
available for the configured host or cluster.

9 Select a datastore for the virtual machine and click Next.
10 Select Thin provision as the disk format and click Next.

11 Select the main management VLAN from the LCS for the network mapping and click Next.

12 Specify network properties from the LCS and click Next.

13 Verify the deployment settings and click Finish.
The vSphere Client displays the progress of the Vision Core VM deployment.
14 Right-click the Vision Core VM in the VM Inventory, and select Snapshot > Take Snapshot. If
there are any configuration issues during first boot, you can then revert the virtual machine to a
clean, initial state without having to redeploy the OVA.
15 Right-click the Vision Core VM in the VM Inventory, and select Power > Power On.

What to do next
When the virtual machine deployment finishes, and you have powered on the Vision Core VM, open the
Recent Tasks pane to confirm the deployment was successful. Verify the tasks are completed as shown
in the following image:
Starting the Vision Core VM

After deploying the Vision Core VM, start the Vision Core VM to ensure it successfully deployed.
Before you begin
Deploy the Vision Core VM.
Procedure
1 If the VMware vSphere Client prompts you, power on the Vision Core VM.

2 Open the vSphere Client console and monitor the first boot set up.
After the guest operating system starts, the Vision Core VM goes through the first boot set up.
During this process, the system checks network settings, performs initial configuration tasks,
installs and configures Vision software applications, and starts Vision software services. The
following image is an example of the first boot set up in the vSphere Client console:
When the first boot set up is complete, the vSphere Client displays a log on prompt such as the
following:
CentOS release OS_version (Final)

Kernel kernel_version on an x86_64
hostname login:
Configuring Vision software with a second Ethernet adapter

A second Ethernet adapter must be configured with Vision software to harden security.
About this task
This process applies to VxRack Systems only.
Before you begin
The host or cluster where Vision software is installed needs to have access to VLAN 105 and 111.
Procedure
1 Find the Vision Core VM in the inventory.

2 Click Edit Settings.
3 Click Add

4 Select Ethernet Adapter and click Next.
5 On the Network Type page, select the following options:
Adapter Type: VMXNET3
Named network with specified label: vcesys-ipmi
Device Status: Connect at power on
6 Click Next.
7 Click Finish.
8 Click OK.
9 Review the Resources pane on the virtual machine Summary screen and ensure both network
resources are listed.
Connecting to the Vision Core VM

After you deploy the Vision Core VM, you must connect to it in order to verify the installation and
complete additional tasks to configure Vision software. When you connect to the Vision Core VM, you can
interact with the guest operating system and Vision software components.

Before you begin
Deploy the Vision Core VM.
Ensure the virtual machine is running.
Check that the virtual machine is deployed successfully.
Procedure
1 Establish a connection to the Vision Core VM with either of the following methods:
Virtual machine console in the VMware vSphere Client.
SSH client.
You must have the IP address of the Vision Core VM to connect with an SSH client.
Vision software gives you the following prompt:
hostname login:
2 Enter the username and password to connect to the Vision Core VM.
Username: root
Password: V1rtu@1c3!
If you log on successfully, Vision software gives you the following prompt:
Last login: time_stamp from IP_address

[root@hostname ~]#
Configuring Vision software IP information for a second Ethernet

adapter
After adding a second Ethernet adapter to the Vision Core VM, configure the IP information for that
device.
About this task
This process applies to VxRack Systems only.
Before you begin
Determine the IP information to use during configuration.
For Static IP, select an IP address on the subnet VLAN 111 is using.
For Netmask, use a subnet mask appropriate to the network. In most cases 255.255.255.0 is
acceptable.
Connect to the Vision Core VM.

Procedure
1 Type the following command to configure the second eth1 interface.
/usr/sbin/system-config-network
2 Select the Device Configuration action.
3 Select New Device.

4 Select Ethernet.
5 Enter the IP Information for the new Ethernet device, and select OK.

6 Select Save.
7 Select Save & Quit.

8 Type the following command to activate the interface at system boot:
echo "ONBOOT=yes" >> /etc/sysconfig/network-scripts/ifcfg-eth1
9 Type the following command to enable the interface:
ifup eth1
Interfaces and routes should now look like this:

10 Run the following command to set up SNMP trap listening:
sed -i.orig 's/${jext} \$/${jext} -Dfm.trap.listenAddress=udp:0.0.0.0\/162 \$/' \

/etc/init.d/vce-fm-agent
This command creates a backup /etc/init.d/vce-fm-agent.orig file, which can be

deleted after a successful FM Agent restart.
11 Restart the FM Agent services from the Vision Core VM.
a Run the following command:
stopFMagent
b Run the following command:
startFMagent
What to do next
Type a traceroute command to ensure there is now only one direct hop to the target IPMI interface.
Verifying the Vision Core VM successfully deployed

To ensure that the Vision Core VM successfully deployed, you must verify that the first boot script
completed successfully, and ensure the system services are running.
Before you begin
Procedure
1 Check that the first boot script completed successfully.
a Type the following command:
cd /opt/vmware/var/log/
b Type the following command:
tail firstboot

The output of the firstboot script should display as follows:
time_stamp: To start the VCE FMagent services, issue 'startFMagent' after

configuration.
time_stamp: Starting VCE Prepositioning services...
Starting crond: [ OK ]
Enabling Asset Manager services to start automatically...
time_stamp: Done!
If Done! displays as the last line of the output, the firstboot script completed successfully.
If Failed! displays as the last line of the output, the firstboot script did not complete
successfully. This can occur if Vision software applications do not deploy successfully. To
resolve this issue, run shutdown -h now and then restart the Vision Core VM from the
vSphere Client.
2 Verify that the system services are running.
a Type the following command:
service jboss status
b Type the following command:
service postgresql-9.1 status
c Type the following command:
service rabbitmq-server status
d Type the following command:
service rsyslog status
e Type the following command:
service tomcat-asset-mgr status
The status for each service should display as running or provide details about running
processes.
Checking network properties for the Vision Core VM

Complete these steps to verify that the Vision Core VM network properties are correct.
Procedure
1 Start an SSH session to the Vision Core VM if you are connected to the vSphere Client console.
If you can successfully start an SSH session, it indicates that the IP address of the Vision Core
VM is valid.

2 Verify the IP addresses of the configured name servers.
cat /etc/resolv.conf
The IP addresses of the primary and secondary name servers display.
b Check that the IP addresses for the name servers match the Logical Configuration Survey.
3 Ping the default gateway server from the Vision Core VM.
ping IP_address -c4
Where IP_address is the IP address of the default gateway server.
The Vision Core VM sends a ping request to the default gateway server, as in the following
example:
PING IP_address (IP_address) 56(84) bytes of data.

64 bytes from IP_address: icmp_seq=1 ttl=127 time=0.360 ms
The ping statistics display as in the following example:
--- IP_address ping statistics ---

4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 0.360/0.441/0.480/0.054 ms

Verifying the version of the Vision Core VM
Complete these steps to verify the version of the Vision Core VM.
Before you begin
Procedure
1 Run the following command:
getFMagentInfo
The Vision Core VM returns the version and build information, as in the following example:
OVA version: X.X.X.X-build_number

Name : FMagent Relocations: (not relocatable)
Version : X.X.X.X Vendor: VCE
Release : release Build Date: time_stamp
Install Date: time_stamp Build Host: hostname
Group : VCE Applications/System Source RPM: FMagent-X.X.X.X-
build_number.src.rpm
Size : size License: Commercial
Signature : RSA/SHA1, time_stamp, Key ID key_ID
URL : http://www.vce.com
Summary : VCE FMagent
Description :
VCE FMagent build for System Library Integration
'rpm -qi FMagent' will get the same information.
2 Ensure that the Version field displays the version of Vision software you just installed.
Verifying RPM file signing keys

The deployment process includes an automatic step to verify the integrity of the RPM Package Manager
files for the Vision Core VM.
Before you begin

Procedure
1 Run one of the following commands to list the installed RPM files:
Command Description
rpm -qa List all installed RPM files.
rpm -qa | grep vce List installed RPM files that include vce in the name.
The Vision Core VM returns a list of installed RPM files, as in the following example:
[root@hostname log]# rpm -qa | grep vce

vce-vision-repo-version_number
vce-upgrade-manager-version_number
vce-compliance-api-version_number
vce-asset-manager-version_number
vce-puppetmodules-version_number
2 Run the following command to display the keys used to sign each RPM file:
rpm -q --qf '%{RSAHEADER:pgpsig} %{vendor} %{name}-%{version}-%{release}\n' RPM_name
Where RPM_name is one or more RPM file names.
Specify the RPM file name only. Do not include the version number.
Separate multiple RPM file names with a space. You do not need to use a comma or other
delimiter.
For example, the following command displays the keys used to sign the vce-vision-repo and
vce-puppetmodules RPM files:
rpm -q --qf '%{RSAHEADER:pgpsig} %{vendor} %{name}-%{version}-%{release}\n' vce-vision-

repo vce-puppetmodules
The Vision Core VM displays the keys used to sign each RPM file, as in the following example:
RSA/SHA1, time_stamp, Key ID e01792e3d99b5d06 VCE jboss-version_number

RSA/SHA1, time_stamp, Key ID e01792e3d99b5d06 VCE flyway-version_number
RSA/SHA1, time_stamp, Key ID e01792e3d99b5d06 VCE FMagent-version_number
RSA/SHA1, time_stamp, Key ID e01792e3d99b5d06 VCE VblockVision-version_number
RSA/SHA1, time_stamp, Key ID e01792e3d99b5d06 VCE vce-vision-repo-version_number
RSA/SHA1, time_stamp, Key ID e01792e3d99b5d06 VCE vce-upgrade-manager-version_number
RSA/SHA1, time_stamp, Key ID e01792e3d99b5d06 VCE vce-compliance-api-version_number
RSA/SHA1, time_stamp, Key ID e01792e3d99b5d06 VCE vce-asset-manager-version_number
RSA/SHA1, time_stamp, Key ID e01792e3d99b5d06 VCE vce-puppetmodules-version_number
3 Compare the vendor name and key ID used to sign each RPM file.
All signed RPM files should have the same key ID. If signed RPM files have different key ID's, it
could indicate an issue with the integrity of the RPM file.

4 Optional: To view the public GNU Privacy Guard (GPG) key that Dell EMC uses to sign RPM
files, run:
rpm -qi gpg-pubkey-d99b5d06
The Vision Core VM returns the public GPG key information, as in the following example:
Name : gpg-pubkey Relocations: (not relocatable)

Version : d99b5d06 Vendor: (none)
Release : release Build Date: time_stamp
Install Date: time_stamp Build Host: hostname
Group : Public Keys Source RPM: (none)
Size : 0 License: pubkey
Signature : (none)
Summary : gpg(VCE PE Build Release <pebuildrelease@vce.com>)
Description :
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: rpm-X.X.X.X (NSS-3)
mQENBFLFug4BCACzBLZKvsMD6Rm7e6bz+i7uu8U+6qCMjqBsHfwdHVBeW4h9CE2B
MOh3A74lrTgMVbJmii6w3D9qWw6rpzGQznycn4+CKClJTyfhzNa/YGtAwF41a7b0
mmcnkPOA17woudEOk31Z7UCMFO0NsYhSBh88AsjNbVztNwZBW8T+t4eGAnp1q15o
hj07Gi3+KoICLDUv/n4RQRS8alBpYNH13+dTFYZzA7X+uQb49SK7Qnsf6bU97JXP
j/OaMXgKy2jeoD9jF4f3PGDGV+uypoULMU9STARI7sSMTCK5zT+JHdBtyYnlD2Zt
PYptJmPgH3c78uoqQJN1FLnmY6lqNVLnwbefABEBAAG0LVZDRSBQRSBCdWlsZCBS
ZWxlYXNlIDxwZWJ1aWxkcmVsZWFzZUB2Y2UuY29tPokBOAQTAQIAIgUCUsW6DgIb
AwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AACgkQ4BeS49mbXQacUgf/Ry5M+OZL
zK2Jaqe6HV322pnNYwyKGhTftkSiD9RL2n/eSm3Fn79Srz4w/GtQ3c16r+ER0wIR
ZGnfKjP8hcge8nrI3c6+fdwkCMb9lp8QK7CMZ4pKHZAPG2M/1fMpKQERu+pPRH76
Eh6f8hAvE2lGgFyLp7KIgbHAGB5RcELgaOGsrAgz8bbHbSPtg+yAJG2GoxfqlIeK
YQ+rAhQcdntfiCPjIhVJ2dnN6rySUfKnADJ/Pu2CFYIXYJjK7a3BRE0uZEo8oQvL
r2yoW1JKLSvSb3QJ15Xs4S5+8PQtoGI0xcIV68p4Q43A6RJiUZz+ebYBRIgbn3yl
VmB/CPSdasC+QrkBDQRSxboOAQgAnMmnBOFkrPXDgHk2R2+w2F/SXpEgfXecsgUO
et2/otUx9nCcENw2Zzia720Aeyyh5VO7TXjaoZ/loB3CoqhA7/Golzu2GW60tRCi
3RHOpR4jqkVqZ9jHRY0LFAi4xroulv/HT+TfQCbIhxvhyeKtGnGAY2Ivm8ZX6vgZ
N0MhHAz0OZQ8Ra2kgKjzQmREb3W3z3SJ/OZn+qr9x34o3JJiWuBz+FsyfQzvlZzr
UWQcKELemKA5J+rrJxx2/KNL8WqzFObcv0ZefbZIsA4RMmaGzar2sm6FazSnmv0j
j958AUn6xePFlx2RRGxgMk96I/IYBMQwifa6wF0x96VBHDj0HQARAQABiQEfBBgB
AgAJBQJSxboOAhsMAAoJEOAXkuPZm10GFhYH/21ub91DARtf56CA4oEmzRmitl/k
guVVI2FY+WpK/OPoUrHeiXrpN3oniZ6kft1zHFbSgKntJTQtg5CuvIAtiVYIOwIa
4L5MgOyPudPiuPhPR3DHvDOQfx8dqC6pTJV5xVEUOx+F8L2KzikakYkqjoi3VG8y
5EF82DkvHLUjkmPlGA2fLryIWLYACRrExBdwHHYvWGE7gEQJT6Mm+19/VgVfcy9w
7m8wEoF3hiuLZINb4/If6xuUcj/C0VtXengA1RxGMDh2ueU6grAwjeP2AU99e26v
YqNaaktj/fNBWJxNQi0bGs0st3PCRaco+Dcxms6LOKJBoLrZYtUDmrsLx/U=
=xvPp
-----END PGP PUBLIC KEY BLOCK-----
Accepting the end user license agreement (EULA)

During the Vision software installation process, you must accept the EULA before you start
discovery. Vision software does not discover VCE System components or poll for health status
unless you accept the EULA.
About this task
Accepting the EULA involves running a command on the Vision Core VM and specifying EULA
acceptance information such as a name, job title, licensee company, and accepting company.
This note is for Dell EMC personnel only. During the installation process, you can specify
any values for the EULA license to enable discovery and health polling. After the installation

process is complete, you reset the EULA so that the customer can accept it when the VCE
System is delivered. The customer will then specify their own valid EULA acceptance
information. Vision software saves the EULA information you specify during installation
to /opt/vce/fm/logs/EULA.log. Customers can access this log file when the VCE
System is delivered. For this reason, you should ensure that any values you set to accept the
EULA adhere to business conduct guidelines.
Procedure
1 Start an SSH session to the Vision Core VM and log on with the following credentials:
Username: root
startEulaAcceptance
3 Scroll to the end of the EULA. After you have read the EULA, type q to enter data.
4 When prompted, enter a name for EULA acceptance and then press Enter.
Values cannot exceed 500 characters or contain angle brackets, < or >.
5 Enter a job title and then press Enter.
6 Enter the name of the licensee company and then press Enter.
7 Optional: Enter the name of the accepting company and then press Enter. If you do not specify
an accepting company, the value defaults to the licensee company.
8 Enter yes to accept the EULA when prompted. A message such as the following displays:
Do you accept the End User License Agreement:[yes/no]> yes

Softcopy of End User License Agreement File created in: /opt/vce/fm/eula/
VCE_EULA_V3_0.txt
time_stamp EULA has been accepted.
To create a text file of the EULA to read or print, run the following command:
createEULASoftCopy
A copy of the EULA will be created in the /opt/vce/fm/eula/VCE_EULA_V3_0.txt

directory. To read the EULA in the CLI, run the following command:
displayEula

Configuring Vision software to discover Vblock System
components
From Vision software Version 3.0 onwards, using the configTool.sh to configure components
for discovery is supported on a Vblock System only.
Configuring the vblock.xml file

Configuring the vblock.xml file involves running a shell script that prompts you for specific information
about the VCE System you are configuring. Vision System Library then uses the vblock.xml file to
perform the initial discovery of the compute, network, storage, and management components in the VCE
System.
To configure any Vblock System that contains AMP-2S (including the Vblock System 350), you must
generate the vblock.xml automatically. You cannot use the configTool.sh method. Refer to Generating the
vblock.xml file automatically (see page 101) for information about configuring the vblock.xml
automatically.
About this task
The first step is to choose a template for the vblock.xml file. After you select a template, the script
guides you through a series of prompts where you can enter information about each component. For
example, the script prompts you to enter information for different components such as IP addresses and
credentials. In this way, you build on the template to create a vblock.xml file that reflects the specific
configuration of the VCE System. The shell script provides some default credentials. You must specify the
passwords for components explicitly whose default credentials are not provided.
You can validate information during the configuration process or at the end of the configuration process
when the script validates the entire vblock.xml file. However, as a best practice, you should validate
information as you proceed through each step.
If validation should fail at any time during the configuration, make sure the component and any required
resources (server, switch, etc.) are running properly. If not, restart the server and run the validation step
again.
After the validation process is complete, save the vblock.xml file to the system. The default filename is
vblock.xml. You can save the configuration to a file with a non-default filename. However, Vision
software System Library uses only the default vblock.xml file to perform the initial discovery.
Before you begin
Complete the steps to verify the Vision Core VM deployment.
System Library services must be running.
Ensure you have the Logical Configuration Survey (LCS). You need the LCS to enter specific
information about the VCE System.
Procedure
1 Do one of the following:
a Open the vCenter vSphere Client console.

b Start an SSH session to the Vision Core VM.
2 Log on with the following credentials:
Username: root
The profile for the root user contains the path to the configTool shell script. This path is as
follows: /opt/vce/fm/bin. If you do not log on as the root user, you must change to this
directory to run the configTool shell script.
3 Type configTool.sh.
Type Ctrl+C and type exit to quit the SSH session and discard your changes at any time.
Type configTool.sh --multiple-storage and load the existing vblock.xml file if

you are configuring an existing vblock.xml file. If you want to include multiple XtremIO
storage, additional VNX and VMAX storage arrays or VMAX as a storage technology
extension, use the configTool.sh --multiple-storage option.
Vision software does not support the use of a single ECOM server (Element Manager) IP for
multiple storage arrays. You must specify a different ECOM server IP for each additional
storage array you want to add.
When running this command, it is important to include 2 dashes (--) with no spaces immediately
before the multiple-storage option.
The following line appears:
Press Enter to display the list of available templates, or Enter the full path of an
existing vblock.xml file: [/opt/vce/fm/conf/template] :

4 Press Enter to display the list of available templates. The script displays the following list of
templates:
(1)vblock100_template.xml
(2)vblock2XX_Block-Only_Storage_Unified_Network_template.xml
(3)vblock2XX_Unified_Storage_Unified_Network_template.xml
(4)vblock3XX_Block-Only_Storage_Segregated_Network_template.xml
(5)vblock3XX_Block-Only_Storage_Unified_Network_template.xml
(6)vblock3XX_Unified_Storage_Segregated_Network_template.xml
(7)vblock3XX_Unified_Storage_Unified_Network_template.xml
(8)vblock5XX_AnyStorage_Segregated_Network_template.xml
(9)vblock7XX_AnyStorage_Segregated_Network_template.xml
(10)vblock7XX_AnyStorage_Unified_Network_template.xml
(11)vblockVSS_XAPP_template.xml
Enter the number that corresponds to the system you are configuring ['0' to specify
new file or directory]:
Unified network is a VCE System without a Cisco MDS switch.
Segregated network is a VCE System with a Cisco MDS switch.
Unified storage is a VCE System with storage processors that are connected to X-Blades
over Fibre Channel (FC).
Block-only storage is a VCE System with no X-Blades in the cabinet.
AnyStorage is any storage that the Vblock System 700 and Vblock System 540 series
support; for example, VG2/VG8 Gateway, VPLEX, and block-only storage.
5 Type the number for the template that you want to use.
For example, type 5 if you are configuring a Vblock System 300 with block-only storage and
unified network.
The script applies the template that you select.

6 Pick the type of VCE System that you are configuring. For example, type 1 to configure a Vblock
System 300 EX model.
Enter the type of Vblock to be configured :

(1)300EX
(2)300FX
(3)300GX
(4)300HX
(5)320w5300
(6)320w5500
(7)320w5700
(8)320w7500
(9)340w5400
(10)340w5600
(11)340w5800
(12)340w7600
(13)340w8000
(14)350wU300
(15)350wU400
(16)350wU500
(17)350wU600
(18)350wU300F
(19)350wU400F
(20)350wU500F
(21)350wU600f
Enter an option for the type:
7 Configure optional components as appropriate. Refer to the LCS to determine if you should
include any optional components.
After you select the template for the system you are configuring, the script prompts you to include
certain optional components. For example, the following is the prompt to include the VPLEX in
the configuration:
Do you want to include VPLEX in this configuration? ('0' to include 's' to skip )
[0] :
a For each optional component, type one of the following values:
Type 0 to include the component in the configuration. If you include a component, the
script adds it to the configuration. You can modify the component attributes during the
configuration process.
Type s to continue to the next step and exclude the component from the configuration.
Refer to Vblock System optional components (see page 94) for the optional
components for each Vblock System.

8 Select a network switch if you are configuring a Vblock System 100.
The script prompts you with the following after you select the template for the Vblock System 100:
(0) Nexus3064T
(1) CA3750
Select the switch you want to add to this Vblock 100:
Type 0 to include a Cisco Nexus 3064T switch in the configuration.
Type 1 to include a Cisco Catalyst 3750 switch in the configuration.
9 Select a network switch if you are configuring a Vblock System 3XX, a Vblock System 540, or a
Vblock System 7XX.
The script prompts you to select a network switch as follows:
Specify the switch you would like to configure as part of this configuration
1. Nexus5000
2. Nexus7000
3. Nexus9000
Enter selection:
Type one of the following values:
Type 1 to include a Cisco Nexus 5000 switch in the configuration.
10 The script prompts you to select the number of Nexus 1000V switches.
How many Nexus 1000 switches are included in this installation [between '0' and '10']:
If your Vblock System contains the VMware Virtual Distributed Switch, you can skip the Cisco
Nexus 1000V switch configuration. Type 0 for the number of Cisco Nexus 1000V switches to
configure.
11 Select a management component for the configuration.
The script prompts you to include a management component in the configuration as follows:
Do you want to include a management component in this configuration? ('0' to include a

management component or 's' to skip this step.)
The management component refers to the AMP-2. For the AMP for VSS XAPP configuration, this
step is skipped.
a Type one of the following values:
Type 0 to include a management component in the configuration. Refer to the LCS to

determine to determine if you should include a management component. If you are
configuring a Vblock System 340 or a Vblock System 350, you must include a
management component in the configuration. The management component is not
optional for a Vblock System 340 or a Vblock System 350.
Management components are not supported for Vblock System 100, Vblock System 300,
Vblock System 320, Vblock System 700, and Vblock System 720.
Type s to continue to the next step and exclude the management component from the
configuration.
If you include a management component, the script prompts you to select a network switch
for the management component as in the following example:
Select a switch for the management component as follows:

(1) Nexus3000
Enter the number of the switch that you want to use. ('s' to skip this step):
b Type the number of the switch that you want to use for the management component.
For example, type 1 to use a Cisco Nexus 3000 switch, as in the preceding example.
The script adds the switch to the configuration for the management component. You
configure the switch later.
12 Follow these steps to include the Converged Technology Extension for Isilon storage in the
configuration. If you want to add a technology extension after you have completed the installation
process, contact VCE Support. The script prompts you to include the technology extension as
follows:
Do you want to include ISILON in this configuration? ('0' to include 's' to skip)
[s] :_
Type 0 to include the technology extension in the configuration.
Type s to exclude the technology extension from the configuration.
If you included the technology extension in the configuration, the script prompts for the
number of clusters in the configuration, as follows:
Enter the number of ISILON clusters in the system you are configuring: _
b Enter the number of clusters that need to be included in the configuration. The script adds the
technology extension for each cluster to the configuration. You configure the technology
extension later.

13 Follow these steps to select the connectivity file for the configuration.
The script prompts you to select a connectivity file as follows:
Press Enter to display the available connectivity files, or Enter the full path of a
file ('s' to skip) : [/opt/vce/fm/conf/template/connectivity] :
Connectivity files are optional, and are not supported for all Vblock Systems. Type s to
skip this step.
a Press Enter to display a list of available connectivity files.
The script displays the connectivity files that correspond to the system you are configuring.
The following is an example of connectivity files for a Vblock System 300:
(1) 3XX-6248-Segregated_Network-connectivity.xml
(2) 3XX-6248-Unified_Network-connectivity.xml
(3) 3XX-6296-Segregated_Network-connectivity.xml
(4) 3XX-6296-Unified_Network-connectivity.xml
Enter the number that corresponds to the system you are configuring ['0' to
specify new file or directory]:
b Type the number for the connectivity file that you want to use.
You must select the right connectivity file corresponding to your VCE System in
the configuration. Refer to the Vblock System connectivity files (see page 97)
table for a list of VCE System connectivity files.
For example, type 3 if you are configuring a Vblock System 300 that includes Cisco UCS
6296UP fabric interconnects and uses a segregated network.
The script applies the connectivity file to the configuration. Depending on the connectivity file
that you select, the script provides a confirmation of your selection as follows:
Loaded connectivity from: '/opt/vce/fm/conf/template/connectivity/7XX-6296-

Segregated_Network-connectivity.xml'

14 Follow these steps to configure the attributes for the VCE System.
The script prompts you to define attributes for the VCE System you are configuring. The following
example shows a prompt for a Vblock System 740:
Vblock null 0 componentTag:

'VB-740', serialNumber: 'VB740-975-318-642', type: '740EX'
(1) componentTag, 'VB-740'
(2) serialNumber, 'VB740-975-318-642'
(3) type, '740EX'
To change an attribute enter the corresponding number from the list ('0' to continue
to next step):
Type 0 to continue to the next step.
Type 1 to change the component tag.
Type 2 to change the serial number. You can locate the serial number on the VCE
System rack.
Type 3 to change the model type. A list of model types is displayed. Enter the number
that corresponds to your Vblock model type. Refer to Vblock System model types (see
page 96) for a complete list.
When configuring VSS for XAPP systems, the model type you select
determines how many Cisco UCS C220 servers you are prompted to
configure. If you select VSSXAPP10T1 for the model type, you will be
prompted to configure three UCS C220 Servers. If you select VSSXAPP10T2
for the model type, you will be prompted to configure four UCS C220 Servers.
15 Specify the number of vCenters to include in this configuration. The script prompts you to enter
the number of vCenters as follows:
How many Vcenters are included in this installation [between '1' and '99']:
16 If you are configuring a Vblock System 100 or a Vblock System 2XX, type the number of Cisco C-
Series servers to include. You can find the number of Cisco C-Series servers to enter in the LCS.

17 For Vblock System 3XX, Vblock System 540, or Vblock System 7XX systems, specify the number
of UCS managers to include in the configuration.
These systems can support multiple UCS domains. The script prompts you for the number of
UCS managers as follows:
How many UCS managers are included in this installation [between '1' and '99']:
For example, type 2 to configure 2 UCS managers.
How many UCS managers are included in this installation [between '1' and '99']:2
VblockLocation Vblock 1 building: '350

Campus', floor: '1rd', geo: 'Marlborough, MA', room: 'Eisenhower', row: 'Dev', tile:
'2'
(1) building, '350 Campus'
(2) floor, '1rd'
(3) geo, 'Marlborough, MA'
(4) room, 'Eisenhower'
(5) row, 'Dev'
(6) tile, '2'
to next step): 0
VCenter VCenters 2 ipaddress:

'192.168.101.77', url: 'https://192.168.101.77/sdk', username: 'administrator',
(1) ipaddress, '192.168.101.77'
(2) password, ''
(3) username, 'administrator'
Enter selection ('0' to continue to next step, or 'v' to validate ): 0

'192.168.101.51', url: 'https://192.168.101.51/sdk', username: 'administrator',
(1) ipaddress, '192.168.101.51'
(2) password, ''
Enter selection ('0' to continue to next step, or 'v' to validate ):

18 If you are configuring a Vblock System 320, a Vblock System 340, Vblock System 350, a Vblock
System 540, a Vblock System 720, or a Vblock System 740, the script prompts you to include
XtremIO storage in the configuration. The script prompts you to include XtremIO storage as
follows:
Do you want to include XtremIO in this configuration? ('0' to include 's' to skip)
[s] :_
Type 0 to include XtremIO storage in the configuration.
Type s to exclude the XtremIO storage from the configuration.
If you included XtremIO storage in the configuration, the script prompts for the number of
clusters in the configuration, as follows:
Enter the number of XtremIO configurations in the system you are configuring: _
b Enter the number of clusters that are to be included in the configuration. The script adds the
selected number of clusters to the configuration.

19 If you are configuring a Vblock System 320, Vblock System 340, Vblock System 350, a Vblock
System 540, a Vblock System 720, or a Vblock System 740, the script prompts you to include
VMAX storage in the configuration.
The following table shows the model prefix and model numbers of the Converged Technology
Extension for VMAX that can be configured on specific Vblock Systems:
Vblock System Model prefix Model number
Vblock System 320 VMAX Converged Technology Extension for VMAX

Vblock System 340 250F
Vblock System 350 Converged Technology Extension for VMAX

250FX
Vblock System 720
Converged Technology Extension for VMAX
Vblock System 740
450F
450FX
850F
850FX
The script prompts you to include VMAX storage as follows:
Do you want to include VMAX in this configuration? ('0' to include 's' to skip) [s] :_
Type 0 to include VMAX storage in the configuration.
Type s to exclude the VMAX storage from the configuration.
If you included VMAX storage in the configuration, the script prompts for the number of
VMAX configurations in the system, as follows:
Enter the number of VMAX configurations in the system you are configuring: _
b Enter the number of VMAX storage arrays that are to be included in the system that you are
configuring. The script adds the selected number of configurations to the system.
The script prompts you to include Network Attached Storage (eNAS) if you are configuring a
Vblock System 740, as follows:
Do you want to include storage eNAS in this configuration? ('0' to include, 's'
to skip) [0] :0

c Type one of the following values:
Type 0 to include eNAS in the configuration.
Type s to exclude eNAS in the configuration.
The script prompts you to add eNAS for each VMAX storage array you are configuring on a
Vblock System 740, as follows:
Do you want to add a eNAS to the VMAX with componentTag: 'VMAX-ARRAY1' in this
configuration? ('0' to include, 's' to skip) [s] :0
Do you want to add a eNAS to the VMAX with componentTag: 'VMAX-ARRAY2' in this
configuration? ('0' to include, 's' to skip) [s] :0
20 If you are configuring a Vblock System 320, a Vblock System 340, a Vblock System 350, a
Vblock System 540, a Vblock System 720, or a Vblock System 740, the script prompts you to
include VNX storage as follows:
Do you want to include VNX in this configuration? ('0' to include 's' to skip) [s] :_
Type 0 to include VNX storage in the configuration.
Type s to exclude the VNX storage from the configuration.
If you included VNX storage in the configuration, the script prompts for the number of VNX
configurations in the system, as follows:
Enter the number of VNX configurations in the system you are configuring: _
b Enter the number of VNX storage arrays that are to be included in the system that you are
21 If you are configuring a Vblock System 320, a Vblock System 340, a Vblock System 350, a
Vblock System 540, a Vblock System 720, or a Vblock System 740, the script prompts you to
include Unity storage as follows:
Do you want to include UNITY in this configuration? ('0' to include 's' to skip)
[s] :_
Type 0 to include the technology extension in the configuration.
Type s to exclude the technology extension from the configuration.
b Enter the number of UNITY storage arrays that are to be included in the system that you are
If you want to add a technology extension after you have completed the installation process,
contact VCE Support.
22 Follow these steps to include the IPI appliance in the configuration.
If you are configuring a Vblock System 340, a Vblock System 350, a Vblock System 540, a
Vblock System 720, or a Vblock System 740, the script prompts you to include a IPI appliance in
the configuration, as in the following:
Does the configuring vblock contain a Panduit Rack Gateway (y/n)?
Type y to include the IPI appliance to the configuration.
Type n to exclude the IPI appliance from the configuration.
If you choose y, the script prompts you to enter the number of IPI appliances you need to
configure, as in the following:
How many Panduit Rack Gateways do you want to configure? [1]
You can configure more than one IPI appliance. The default is 1.
b Enter the number of IPI appliances that you need to configure.
c Repeat steps a. and b. for each IPI appliance that you need to configure.
For a Vblock System 340, Vblock System 350 or a Vblock System 720, you can configure
between 0 and 99 additional IPI appliances. The script prompts you to enter the number of
additional IPI appliances you want to configure, as in the following:
Enter the number of additional Panduit Racks you are configuring

(Enter number or 's' to skip):
You will then be prompted to:
Enter selection ('0' to continue to next step, or 'v' to validate ): [0] :
23 Follow these steps to define the VCE System location.
The script prompts you with the location for the VCE System, as in the following example:
VblockLocation Vblock 1 building: '350

Campus', floor: '1rd', geo: 'Marlborough, MA', room: 'Eisenhower', row: 'Dev', tile:
'2'
(1) building, '350 Campus'
(2) floor, '1rd'
(3) geo, 'Marlborough, MA'
(4) room, 'Eisenhower'
(5) row, 'Dev'
(6) tile, '2'
to next step):
a Type the number that corresponds to the location information you need to change. You can
find the location information in the LCS. The geography information, or geo, has a limit of 64
characters.
b Type 0 to continue when you are done modifying the VCE System location.
24 Do one of the following to configure the IPI appliance. If you included the IPI appliance in the
configuration, the script prompts you to configure the IP address for the IPI appliance, as in the
following example:
RackManager Rack 3 gatewayIpAddress:

'1.2.3.118'
(1) gatewayIpAddress, '1.2.3.118'
Type 1 to change the IP address.
The script prompts you to configure the community string for the IPI appliance:
Credentials RackManager 4 community: '',

method: 'snmpv2c'
(1) community, ''
b Type one of the following values:
Type 1 to set the community string. You must enter a non-blank value for the community
string. The SNMP community string must match the string set on the server.
Type v to validate the configuration for the IPI appliance.

25 Follow these steps to configure the VMware vCenter Server:
The script prompts you to configure the VMware vCenter Server, as follows:

'192.168.101.77', url: 'https://192.168.101.77/sdk', username: 'administrator'
(1) ipaddress, '192.168.101.77'
(2) password, ''
Type 1 to change the IP address of the vCenter Server and then enter the IP address.
Type 2 to set the password. You must set the password.
Type 3 to change the username.
Type v to validate the information for the vCenter Server.
Repeat this step for each vCenter that you added to the configuration.
26 Follow these steps to include Application Hosts in the configuration.
The script prompts you to enter the number of Application Hosts.
Enter the number of ApplicationHosts that corresponds to the system you are
configuring:
a Enter the number of Application Hosts for each Windows-based virtual machine on an AMP
that has one or more Management Software Applications installed.
The script prompts you to configure the IP address for the Application Host, as follows:
ApplicationHost ManagedSoftware 2 address:

'10.168.101.40', name: 'app-host-1', type: 'windows'
(1) address, '10.168.101.40'
To change an attribute enter the corresponding number from the list ('0' to
continue to next step):

i Type 1 to change the IP address of the Application Host and then enter the IP address.
ii Type 0 to continue to the next step.
The script prompts you to change the credentials for the Application Host as follows:
Credentials ApplicationHost 3 method: 'wmi',

username: 'admin',
(1) password, ''
(2) username, 'domain\admin'or 'admin@domain'
Type 1 to set the password for the Application Host. You must set the password.
Type 2 to change the domain name and username for the Application Host. You must
include the domain name before the username using a back slash.
Type v to validate the information for the Application Hosts.
d Repeat these steps for each Application Host in your configuration.
Configuring the compute servers
If you are configuring multiple servers, you must configure the IP address of the Cisco C-Series server
and the Cisco UCS Manager for each server.

Procedure
1 Follow these steps to configure the compute servers for Vblock System 100 or Vblock System
2XX.
If you are configuring a Vblock System 100 or Vblock System 2XX, the script prompts you to
configure the IP address of the Cisco C-Series server, as follows:
Server Compute 2 address:

'192.168.101.8', componentTag: 'SERVER-A', esxi: 'null', ipaddress: '192.168.101.8',
name: 'svr1', type: 'C220M3'
(1) ipaddress, '192.168.101.8'
to next step): 0
Type 1 to change the IP address of the server and then enter the IP address.
The script then prompts you to configure the access credentials for the Cisco C-Series
server, as follows:
Credentials Server 3 community: '',

ipaddress: 'Not Applicable', method: 'snmpv2c', username: 'admin', which: 'null'
(1) community, ''
(2) password, ''
(3) username,
'admin' Enter selection ('0' to continue to next step, or 'v' to validate ): 0
Type 1 to set the SNMP community string. You must enter a non-blank value for the
community string.
The SNMP community string must match the string set on the server.
Type v to validate the information for the Cisco C-Series server.

2 Follow these steps to configure the Cisco UCS Manager for Vblock System 3XX, Vblock System
540, Vblock System 7XX, or Vblock Specialized System.
If you are configuring a Vblock System 3XX, Vblock System 540, Vblock System 7XX, or Vblock
Specialized System, the script prompts you to configure the IP address of the Cisco UCS
manager, as follows:

'192.168.104.30', componentTag: 'VMABO-UCS-1', esxi: 'null', ipaddress:
'192.168.104.30', name: 'sys1', type: 'UCS'
(1) ipaddress, '192.168.104.30'
to next step):
The default name for UCS servers is "sys". For each additional UCS server, ensure the name is
in the following format: sysXXXX where sys is lowercase and XXXX is a unique number. For
example "sys2".
Type 1 to change the IP address of the Cisco UCS manager and then enter the IP
address.
The script then prompts you to configure the access credentials for the Cisco UCS manager,
as follows:
Credentials Server 4 community:

'public', ipaddress: 'Not Applicable', method: 'xml', username: 'admin', which:
'null'
(1) community, 'public'
(2) password, ''
(3) username, 'admin'
Do not change the community string. SNMP is not used for UCS B-Series servers
Type v to validate the information for the Cisco UCS manager server.
Configuring the network switches
After completing the steps to configure the compute servers, the script prompts you to configure the
network switches for your Vblock System.

Procedure
1 Follow these steps to configure the Cisco Catalyst 3750 switch. The Cisco Catalyst 3750 switch
can be included for the Vblock System 100. If you selected to include the Cisco Catalyst 3750
switch in your configuration, the script prompts you to configure the IP address of the switch, as
follows:
Switch Network 3 address:

'192.168.101.120', componentTag: 'STACKSWITCH', type: 'CA3750'
(1) address, '192.168.101.120'
to next step):
Type 1 to change the IP address of the switch and then enter the IP address.
The script then prompts you to configure access credentials, as follows:
Credentials Switch 4 community: '',

ipaddress: 'Not Applicable', method: 'snmpv2c', username: 'null', which: 'null'
(1) community, ''
(2) password, ''
(3) username, 'null'
community string.
The SNMP community string must match the string set on the switch.
Type v to validate the information for the Cisco Catalyst 3750 switch.

2 Follow these steps to configure the Cisco Nexus 3064T switch.
Cisco Nexus 3064T switches are included in some configurations for a Vblock System 100. If you
are configuring the Cisco Nexus 3064T switch, the script prompts you to configure the IP address
of switch A, as follows:

'192.168.101.155', componentTag: 'N3A', type: 'Nexus3000'
(1) address, '192.168.101.155'
to next step):
The script prompts you to configure the access credentials for switch A, as follows:

(1) community, ''
(2) password, ''
community string.
Type v to validate the information for the Cisco Nexus 3064T switch A.
The script prompts you to configure the IP address of the Cisco Nexus 3064T switch B, as
follows:

'192.168.101.156', componentTag: 'N3B', type: 'Nexus3000'
(1) address, '192.168.101.156'

The script prompts you to configure the access credentials for switch B, as follows:

(1) community, ''
(2) password, ''
d Type one of the following values:
community string.
Type v to validate the information for the Cisco Nexus 3064T switch B.
You have finished configuring the network switches and are prompted to Configuring the storage
array (see page 69).

3 Follow these steps to configure the Cisco MDS 9000 Series Multilayer switch. Cisco MDS 9000
Series Multilayer switches are included in some configurations for a Vblock System 3XX, a
Vblock System 540, or a Vblock System 7XX. If included in your configuration, the script prompts
you to configure the IP address of the Cisco MDS 9000 Series Multilayer switch A, as follows:

'192.168.101.20', componentTag: 'M9A', type: 'MDS9000'
(1) address, '192.168.101.20'
to next step):
The script prompts you to configure the access credentials for the Cisco MDS 9000 Series
Multilayer switch A, as follows:

(1) community, ''
(2) password, ''
community string.
Type v to validate the information for the Cisco MDS 9000 Series Multilayer switch.
The script prompts you to configure the IP address of the Cisco MDS 9000 Series Multilayer
switch B, as follows:

'192.168.101.21', componentTag: 'M9B', type: 'MDS9000'
(1) address, '192.168.101.21'

The script prompts you to configure the access credentials for the Cisco MDS 9000 Series
Multilayer switch B, as follows:

(1) community, ''
(2) password, ''
community string.
Type v to validate the information for the Cisco MDS 9000 Series Multilayer switch B.

4 Follow these steps to configure the Cisco Nexus 5000 Series switch.
Cisco Nexus 5000 switches are included in the configuration for a Vblock System 2XX and a
Vblock System 3XX, and VSS XAPP. For the Vblock System 540 and Vblock System 7XX, this
switch is optional.
The script prompts you to configure the IP address of the Cisco Nexus 5000 switch A, as follows:

(1) address, '192.168.101.4'
to next step):
The script then prompts you to configure the access credentials for the Cisco Nexus 5000
switch A, as follows:

(1) community, ''
(2) password, ''
community string.
Type v to validate the information for the Cisco Nexus 5000 switch A.
The script prompts you to configure the IP address of the Cisco Nexus 5000 switch B, as
follows:

(1) address, '192.168.101.5'


(1) community, ''
(2) password, ''
community string.
Type v to validate the information for the Cisco Nexus 5000 switch B.

5 Follow these steps to configure the Cisco Nexus 7000 Series switch. Cisco Nexus 7000 Series
switches are included in the some configurations for a Vblock System 7XX, Vblock System 540,
or Vblock System 3XX. The script prompts you to configure the IP address of the Cisco Nexus
7000 switch A, as follows:
Switch Network 3 address: '10.2.0.2',

componentTag: 'N7A', type: 'Nexus7000'
(1) address, '10.2.0.2'
to next step):
switch A, as follows:

(1) community, ''
(2) password, ''
community string.
The script prompts you to configure the IP address of the Cisco Nexus 7000 switch B, as
follows:

(1) address, '10.2.0.3'


(1) community, ''
(2) password, ''
community string.

6 Follow these steps to configure the Cisco Nexus 9000 Series switch. Cisco Nexus 9000 Series
switches are included in the some configurations for a Vblock System 7XX, Vblock System 540,
or Vblock System 3XX. The script prompts you to configure the IP address of the Cisco Nexus
9000 switch A, as follows:

(1) address, '192.168.101.4'
to next step):
Series switch A, as follows:

(1) community, ''
(2) password, ''
community string.
Type 2 to set the password.
Type v to validate the information for the Cisco Nexus 9000 Series switch A.
The script prompts you to configure the IP address of the Cisco Nexus 9000 Series switch B,
as follows:

(1) address, '191.168.101.5'

Series switch B, as follows:

(1) community, ''
(2) password, ''
community string.
Type v to validate the information for the Cisco Nexus 9000 Series switch B.

7 Follow these steps to configure the Cisco Nexus 1000V switch.
The Cisco Nexus 1000V switch is an optional component for a Vblock System System 2XX, a
Vblock System 3XX, Vblock System 540, and a Vblock System 7XX.
Do not include a Cisco Nexus 1000V switch in the configuration for a Vblock System
100. This component is not available for the Vblock System 100 even though the script
prompts you to include it.
If you included a Cisco Nexus 1000V switch in the configuration, the script prompts you to
configure the IP address, as follows:

'192.168.105.15', componentTag: 'N1A', type: 'Nexus1000V'
(1) address, '192.168.105.15'
to next step):
The script then prompts you to configure access credentials for the Cisco Nexus 1000V
switch, as follows:

(1) community, ''
(2) password, ''
community string.
Type v to validate the information for the Cisco Nexus 1000V switch.

8 Follow these steps to configure the Cisco Nexus 3000 Series switches for the management
component.
If you included a management component in the configuration, the script prompts you to
configure the Cisco Nexus 3000 Series switches after you configure all other switches.
The script prompts you to configure the IP address of Cisco Nexus 3000 switch A, as follows:

'192.168.101.155', componentTag: 'MGMT-N3A', type: 'Nexus3000'
(1) address, '192.168.101.155'
to next step):
The script prompts you to configure access credentials for Cisco Nexus 3000 switch A, as
follows:

(1) community, ''
(2) password, ''

community string.
If the Vblock System contains a management component with one Cisco Nexus
3000 Series switch, the script prompts you to configure only switch A. For
example, if you are configuring a Vblock System 2XX, the script prompts you to
configure Cisco Nexus 3000 switch A but not switch B.
If your management component includes a second Cisco Nexus 3000 switch, the script
prompts you to configure the IP address of Cisco Nexus 3000 switch B, as follows:

'192.168.101.156', componentTag: 'MGMT-N3B', type: 'Nexus3000'
(1) address, '192.168.101.156'
c To configure the IP address of a second Cisco Nexus 3000 switch for your management
component, type one of the following values:
The script prompts you to configure access credentials for Cisco Nexus 3000 switch B, as
follows:

(1) community, ''
(2) password, ''

d To configure the access credentials for Cisco Nexus 3000 switch B, type one of the following
values:
community string.
Configuring the storage array
After completing the steps to configure the switches, the script prompts you to configure the storage array
for your Vblock System.
Procedure
1 Follow these steps to configure the VNXe storage array for a Vblock System 100. If you are
configuring a Vblock System 100, script prompts you to configure the VNXe storage array, as
follows:
StorageArray Storage 3 address:

'192.168.101.44', componentTag: 'ARRAY', type: 'VNXe'
(1) address, '192.168.101.44'
(2) componentTag, 'ARRAY'
(3) type, 'VNXe'
to next step):
Type 1 to change the IP address of the storage array and then enter the IP address.
Type 2 to change the component tag and enter one of the following values:
VNXe3150-ARRAY
VNXe3300-ARRAY
Type 3 to change the component type and enter one of the following values
VNXe3150

VNXe3300
The script prompts you to configure access credentials for the storage array, as follows:
Credentials StorageArray 4 community:

'null', ipaddress: 'Not Applicable', method: 'uemcli', username: 'admin', which:
'null'
(1) password, ''
Type 2 to change the username. You should specify the Unisphere, or CLI, username
and password for the VNXe storage array. The SNMP v3 trap configuration username
and password should match what you specify in the vblock.xml file.
Type v to validate the information for the storage array.
The script prompts you to configure the service user access credentials for the VNXe storage
array, as follows:
Credentials StorageArray 4 method: 'ssh',

username: 'service', which: 'Service User',
(1) password, ''
(2) username, 'service'

2 Follow these steps to configure the storage array for a Vblock System 2XX or a Vblock System
3XX with block only storage.
The script prompts you to configure information about the storage array, as follows:

'192.168.101.40', chassisList: 'null', componentTag: 'VNX5300-ARRAY', type: 'VNX5300'
(1) address, '192.168.101.40'
(2) componentTag, 'VNX5300-ARRAY'
(3) type, 'VNX5300'
to next step):
Type 2 to change the component tag and then enter the component tag in the following
format: model prefix+model number+storage method. For example, VNX5300-ARRAY.
Type 3 to change the component type and enter the component type in the following
format: model prefix+model number. For example, VNX5300.
The following table shows the model prefix and model numbers you can specify for the
component tag and type attributes:
Vblock System 200 VNX 5200
5300
5500
5700
7500
5600
5800
7600
8000
The script prompts you to configure the ECOM server information, as in the following
example:

'null', ipaddress: '192.168.101.89', method: 'cim=https://192.168.101.89:5989',
username: 'admin', which: 'ECOM Server'

(1) ipaddress, '192.168.101.89'
(2) password, ''
Type 1 to change the IP address of the ECOM server and then enter the IP address.
Type v to validate the information for the ECOM server.
The script prompts you to configure storage processor A, as in the following example:

'null', ipaddress: '192.168.101.40', method: 'navisecli=192.168.101.40', username:
'admin', which: 'SPA'
(1) ipaddress, '192.168.101.40'
(2) password, ''
Type 1 to change the IP address of the storage processor and then enter the IP address.
Type v to validate the information for the storage processor.
The script prompts you to configure storage processor B, as in the following example:
Credentials StorageArray 4 ipaddress:

'192.168.101.41', method: 'navisecli=192.168.101.41', username: 'admin', which:
'SPB',
(1) ipaddress, '192.168.101.41'
(2) password, ''

If you are configuring a Vblock System 300 and you included a VPLEX in the configuration,
the script prompts you to configure the IP address of the VPLEX, as in the following example:
StorageVirtualizer Storage 3 address:

'192.168.101.150', componentTag: 'VPLEX-000-XXX', type: 'VPLEX'
(1) address, '192.168.101.150'
e Type one of the following values:
Type 1 to change the IP address of the VPLEX and then enter the IP address.
The script prompts you to configure access credentials for the VPLEX, as in the following
example:
Credentials StorageVirtualizer 4 community:

'null', ipaddress: 'Not Applicable', method: 'xml', username: 'admin', which:
'null'
(1) password, ''
Enter selection ('0' to continueto next step, or 'v' to validate ):
f Type one of the following values:
Type v to validate the information for the VPLEX.

3 Follow these steps to configure the storage array for a Vblock System 2XX or a Vblock System
3XX with unified storage.

'192.168.101.40', chassisList: 'null', componentTag: 'VNX5300-ARRAY', type: 'VNX5300'
(1) address, '192.168.101.40'
(2) componentTag, 'VNX5300-ARRAY'
(3) type, 'VNX5300'
to next step):
The VNX (5400 5600 5800 7600 8000) storage array is also available for Vblock System 540,
Vblock System 720, and Vblock System 740 as a storage technology extension.
format: <model prefix><model number>-<storage method>. For example, VNX5300-
ARRAY.
format: <modelprefix><model number>. For example, VNX5300.
5300
5500
5700
7500
Vblock System 340 and Vblock System 350 VNX 5400
5600
5800
7600
8000
The script prompts you to configure the ECOM server information, as in the following
example:

username: 'admin', which: 'ECOM Server'
(1) ipaddress, '192.168.101.89'
(2) password, ''
Type 1 to change the IP address of the ECOM server and then enter the IP address.
Type 3 to change the username
Type v to validate the information for the ECOM server.
The script prompts you to configure the Control Station, as in the following example:

'192.168.101.42', method: 'cim=https://192.168.101.42:5989', username: 'admin',
which: 'Control Station',
(1) ipaddress, '192.168.101.42'
(2) password, ''

Type 1 to change the IP address of the Control Station and then enter the IP address.
Type v to validate the information for the Control Station.
In the event that the Control Station fails validation:
i Verify that the log on credential for the Control Station is correct.
ii Restart the CIM Server on the Control Station.
iii The CIM server uses the Control Station local user account.
The script prompts you to configure storage processor A, as in the following example:

'null', ipaddress: '192.168.101.40', method: 'navisecli=192.168.101.40', username:
'admin', which: 'SPA'
(1) ipaddress, '192.168.101.40'
(2) password, ''
The script prompts you to configure storage processor B, as in the following example:

'192.168.101.41', method: 'navisecli=192.168.101.41', username: 'admin', which:
'SPB',
(1) ipaddress, '192.168.101.41'
(2) password, ''

If you are configuring a Vblock System 300 and you included a VPLEX in the configuration,
the script prompts you to configure the IP address of the VPLEX, as in the following example:

(1) address, '192.168.101.150'
The script prompts you to configure access credentials for the VPLEX, as in the following
example:

'null', ipaddress: 'Not Applicable', method: 'xml', username: 'service', which:
'null'
(1) community, 'null'
(2) password, ''
g Type one of the following values:

4 Follow these steps to configure the Unity storage array for a Vblock System 350.

'10.1.139.52', chassisList: 'null', componentTag: 'UNITY-ARRAY', type: 'UNITY'
(1) address, '10.1.139.52'
(2) componentTag, 'UNITY-ARRAY'
(3) type, 'UNITY'
to next step):
Type 2 to change the component tag and enter a unique component tag. For example, you
can enter the component tag in the following format: <array_model><ARRAY>-
<array_number>.
If there is only one storage array, you do not need to enter the number of arrays.

5 Follow the steps in this section to configure the VMAX storage array for a Vblock System 7XX.

'192.168.101.40', chassisList: 'null', componentTag: 'VMAX-ARRAY', type: 'VMAX'
(1) address, '192.168.101.40'
(2) componentTag, 'VMAX-ARRAY'
(3) type, 'VMAX'
to next step):
The VMAX (100K, 200K, 400K,) storage array is available for Vblock System 320, Vblock System
340, Vblock System 350, and Vblock System 540 as a storage technology extension.
Type 1 to change the IP address of the array manager (ECOM server), or the eMGMT
server, and then enter the IP address.
format: model prefix+model number+storage method. For example, VMAX40K-ARRAY.
format: model prefix+model number. For example, VMAX40K.
Model prefix Model number
VMAX 40K
20K
10K
100K
250F
250FX
200K
400K
450F
450FX
850F
850FX
The script prompts you to configure access credentials for the VMAX storage array, as
follows:

username: 'admin', which: 'VMAX'
(1) ipaddress, '192.168.101.89'
(2) password, ''
Type 1 to change the IP address of the array manager (ECOM server), or the eMGMT
server.
The script prompts you to configure access credentials for Network Attached Storage (eNAS)
if you included eNAS in the configuration, as follows:

'192.168.101.20', method: 'cim=https://192.168.101.20:5989', username: 'admin',
which: 'eNAS',
(1) ipaddress, '192.168.101.20'
(2) password, ''
Type 1 to change the IP address of eNAS.
Type v to validate the information for the eNAS.
You must enter eNAS credentials for each VMAX storage array you are configuring.
The script prompts you to configure the VG2/VG8 Gateway if you choose to include an
VG2/VG8 Gateway and not eNAS in the configuration, as follows:

username: 'admin', which: 'gateway'
(1) ipaddress, '192.168.101.45'
(2) password, ''
(3) username, 'admin' Enter selection ('0' to continue to next step, or
'v' to validate ):

Type 1 to change the IP address of the VG2/VG8 Gateway.
Type v to validate the information for the VG2/VG8 Gateway.
The script prompts you to configure the IP address of the VPLEX if you included a VPLEX in
the configuration, as follows:

(1) address, '192.168.101.150'
The script prompts you to configure access credentials for the VPLEX, as follows:

'null', ipaddress: 'Not Applicable', method: 'xml', username: 'service', which:
'null'
(1) password, ''

6 Follow these steps to configure the XtremIO management server.
The XtremIO management server is available for Vblock System 320, Vblock System 340, Vblock
System 350, Vblock System 540, Vblock System 720, and Vblock System 740. The script
prompts you to configure information about the management server, as follows:

'192.168.101.41', componentTag: 'XIO-ARRAY1', type: 'XTREMIO'
(1) address, '192.168.101.41'
(2) componentTag, 'XIO-ARRAY1'
(3) type, 'XTREMIO'
to next step):
Type 1 to change the IP address and then enter the IP address of the XtremIO
management server.
Type 2 to change the component tag and then enter the component tag.
Type 3 to change the component type and enter the component type.
The script prompts you to configure access credentials for the XtremIO management server,
as follows:
Credentials StorageArray 4 method: 'xml',

username: 'admin', which: 'XTREMIO'
(1) password, ''
Type v to validate the information for the XtremIO management server.

7 Follow these steps to configure the technology extension for each Isilon cluster you included in
the configuration.
If you are including the Converged Technology Extension for Isilon storage, the script prompts
you to change the attributes for each cluster as follows:

'192.168.101.42', componentTag: 'ISILON-ARRAY-CLUSTER-1', type: 'ISILON'
(1) address, '192.168.101.42'
(2) componentTag, 'ISILON-ARRAY-CLUSTER-1'
(3) type, 'ISILON'
Type 1 to change the IP address and then enter the IP address of the storage cluster.
For the Isilon storage cluster IP address, use the IP address of any node within the Isilon
storage cluster. For example, use the IP address of the first node within the Isilon storage
cluster.
Type 2 to change the component tag and then enter the component tag.
Type 3 to change the component type and enter the component type.
The script prompts you to configure the REST API protocol credentials, as in the following
example:
Credentials StorageArray 4 method:

'restApi', username: 'vision-user',
(1) password, ''
(2) username, 'vision-user'
Type v to validate the information.
The script prompts you to configure the SSH protocol credentials, as in the following
example:
Credentials StorageArray 4 method: 'ssh',

username: 'vision-user',
(1) password, ''
(2) username, 'vision-user'

Type v to validate the information for the management cluster.
When you are finished, the script prompts you to change the community string for the
management cluster as follows:
Credentials StorageArray 4 community: '',

method: 'snmpv2c'
(1) community, ''
Type 1 to change the SNMP community string. You must enter a non-blank value for the
community string. The SNMP community string must match the string set on the cluster.
Repeat these steps for each Isilon cluster in your configuration.
What to do next
If you included a management component, refer to Configuring the management components

(see page 84) for the next steps.
If you did not include a management component, the script starts validating the vblock.xml.
Refer to Saving the Vblock System configuration (see page 92) for more information.
Configuring the management components
After you complete the steps to configure the storage array, the script prompts you to specify the type of
management component.
About this task
The following is an example:
ManagementInfrastructure Vblock 1 componentTag: 'Management',

serialNumber: 'AMP-2 SN', type: 'AMP-2P;AMP-2RP;AMP-2LP;AMP-2HA'
(1) type, 'AMP-2P'
To change an attribute enter the corresponding number from the list ('0' to continue to next
step):
If you chose not to include a management component in this configuration, the script starts the
validation of the vblock.xml file. Proceed to Saving the Vblock System configuration (see page
92) for your next steps.

If you are configuring the AMP for VSS XAPP, the management component is fixed for the Vblock
System. For this configuration, some of the following steps are skipped. Proceed to the steps for
configuring the Cisco UCS C220 servers.
Procedure
1 Type one of the following values to configure the management component.
This step is skipped for the AMP for VSS XAPP configuration.
Type 1 to change the type of management component and then select a server as follows:
Type 1 to use an AMP-2P.
Type 2 to use an AMP-2RP.
Type 3 to use an AMP-2LP.
Type 4 to use an AMP-2HA.
Type 0 to verify the type of management component and continue to the next step.
If you change the type of management component, the script applies the configuration and then
returns to the prompt to specify the type of management component. For example, if you change
the management component to include an AMP-2RP in the preceding step, the script prompts
you with the following:
ManagementInfrastructure Vblock 1 componentTag:

'Management', serialNumber: 'AMP-2 SN', type: 'AMP-2P;AMP-2RP;AMP-2LP;AMP-2HA'
(1) type, 'AMP-2RP'
to next step):
2 Verify the type of management component you are configuring and then type 0 to continue to the
next step.
This step is skipped for the AMP for VSS XAPP configuration.
If you are configuring an AMP-2HA, the script prompts you to enter the number of servers you are
configuring, as follows:
Enter the number of servers corresponds to the system you are configuring [between '2'
and '3']:
If you are configuring an AMP-2RP, the script prompts you to configure a second VMware
vCenter Server, as in the following example:

'192.168.101.185', url: 'https://192.168.101.185/sdk', username: 'svc-vcenter',
(1) ipaddress, '192.168.101.185'
(2) password, ''
(3) username, 'svc-vcenter'

3 If you are configuring an AMP-2HA, type one of the following values:
Type 2 to configure two servers.
Type 3 to configure three servers.
4 If you are configuring an AMP-2RP, type one of the following values:
Type 1 to change the IP address of the second vCenter Server and then enter the IP
address.
Type v to validate the information for the VMware vCenter Server.

5 The script prompts you to configure the IP address of the primary Cisco UCS C220 rack server,
as in the following example:

'192.168.101.118', componentTag: 'SERVER-MGMT-A', esxi: 'null', ipaddress:
'192.168.101.118', name: 'svr-mgmt-1', type: 'C220M3'
(1) ipaddress, '192.168.101.118'
to next step): 0
Type one of the following values to configure the IP address for the primary Cisco UCS C220
rack server:
The script prompts you to configure access credentials for the primary Cisco UCS C220 rack
server, as in the following example:

ipaddress: 'Not Applicable', method: 'snmpv2c', username: 'admin', which: 'null',
(1) community, ''
(2) password, ''
community string.
The string must match the SNMP community string set on the server.
Type v to validate the information for the Cisco UCS C220 rack server.
If you are configuring an AMP-2 or an AMP-2LP, the script starts the validation of the vblock.xml
file. Proceed to Saving the Vblock System configuration (see page 92) for your next steps.
If you are configuring an AMP-2RP, AMP-2HA, or an AMP for VSS XAPP, the script prompts you
to configure a secondary Cisco UCS C220 rack server, as in the following example:

'192.168.101.117', componentTag: 'SERVER-MGMT-B', esxi: 'null', ipaddress:
'192.168.101.117', name: 'svr-mgmt-2', type: 'C220M3'
(1) ipaddress, '192.168.101.117'
to next step):

6 If you are configuring an AMP-2RP, an AMP-2HA, or an AMP for VSS XAPP, type one of the
following values:
The script then prompts you to configure access credentials for the secondary Cisco UCS C220
rack server, as in the following example:

(1) community, ''
(2) password, ''
community string.
If you are configuring an AMP-2RP, the script starts the validation of the vblock.xml file. Proceed
to Saving the Vblock System configuration (see page 92) for your next steps.
If you are configuring an AMP-2HA with three servers or an AMP for VSS XAPP, the script
prompts you to configure a third Cisco UCS C220 rack server, as in the following example:

'192.168.101.116', componentTag: 'SERVER-C', esxi: 'null', ipaddress:
'192.168.101.116', name: 'svr3', type: 'C220M3'
(1) ipaddress, '192.168.101.116'
to next step):

7 If you are configuring an AMP-2HA with three servers or an AMP for VSS XAPP, type one of the
following values:
The script then prompts you to configure access credentials for the third Cisco UCS C220 rack

(1) community, ''
(2) password, ''
community string.
If you are configuring an AMP-2HA, the script prompts you to configure an VNXe3200 hybrid
storage array, as in the following example:

'192.168.101.44', componentTag: 'ARRAY', type: 'VNXe'
(1) address, '192.168.101.44'
(2) componentTag, 'ARRAY'
(3) type, 'VNXe'
If you are configuring an AMP for VSS XAPP with four servers, the script prompts you to
configure a fourth Cisco UCS C220 rack server, as in the following example:

'192.168.101.115', componentTag: 'LMID', esxi: 'null', ipaddress:
'192.168.101.115', name: 'svr4', type: 'C220M3'
(1) ipaddress, '192.168.101.115'
dTo change an attribute enter the corresponding number from the list ('0' to
continue to next step): 0

8 If you are configuring an AMP-2HA, type one of the following values:
Type 3 to change the storage array type.
The script then prompts you to configure the access credentials for the VNXe3200, as in the
following example:
Credentials StorageArray 5 community: 'null',

ipaddress: 'null', method: 'uemcli', username: 'admin', which: 'null'
(1) password, ''
Type v to validate the information for the VNXe3200.
The script starts the validation of the vblock.xml file. Proceed to Saving the Vblock System
configuration (see page 92) for your next steps.

9 If you are configuring an AMP for VSS XAPP with four servers, type one of the following values:
The script then prompts you to configure access credentials for the fourth Cisco UCS C220 rack

(1) community, ''
(2) password, ''
community string.
The script then prompts you to configure the storage array for the AMP for VSS XAPP, as in the
following example:

'192.168.101.44', componentTag: 'MGMT-VNXe', type: 'VNXe'
(1) address, '192.168.101.44'
(2) componentTag, 'MGMT-VNXe'
(3) type, 'VNXe'
to next step): 0

10 If you are configuring an AMP for VSS XAPP, type one of the following values:
Type 3 to change the storage array type.
The script then prompts you to configure the access credentials for the storage array, as in the
following example:
Credentials StorageArray 3 community: 'null',

ipaddress: 'null', method: 'uemcli', username: 'admin', which: 'null',
(1) password, ''
Type v to validate the information for the VNCe3200.
Results
The script starts the validation of the vblock.xml file.
What to do next
After successful validation, save the vblock.xml file. Refer to Saving the Vblock System configuration
(see page 92) for more information.
Saving the Vblock System configuration
After configuring the vblock.xml file, the file is validated. If the validation is successful, save the
vblock.xml file.
About this task
When you have completed all of the steps in Configuring the vblock.xml file (see page 37), the script
validates the configuration, as in the following example:
Validating C220M3 connection. Please wait...

Validating SNMP connection for ComponentTag=SERVER-A ipAddress=192.168.101.8, community= .
Please wait...
Validating VCenter connection succeeded!
Validating SNMP connection. Please wait...
Validating SNMP connection succeeded!

.
.
If the validation is not successful, verify the information and modify the vblock.xml file as necessary.
Refer to the Modifying the vblock.xml file (see page 102) topic.
If the validation is successful, the script displays the following message:
No validation errors on current Vblocks object tree.
Before you begin
Complete all of the steps in Configuring the vblock.xml file (see page 37) for your VCE System. Make
sure validation for the vblock.xml file is successful before saving the configuration.
Procedure
1 Save the vblock.xml file.
The script prompts you with the following:
Enter a filename or Press Enter to save in [/opt/vce/fm/conf/vblock.xml] :
2 Press Enter.
File exists would you like to overwrite (y/n)? y
3 Type y.
The system displays the following message:
Saved to: /opt/vce/fm/conf/vblock.xml
What to do next
Start the discovery process as described in Starting VCE System discovery (see page 131).

Vblock System optional components
The following table lists the optional components for each Vblock System:
VCE System Component
Vblock System 100 Cisco Nexus 1000V Switch
Do not include a Cisco Nexus 1000V

switch in the configuration for a Vblock
System 100. This component is not
available for the Vblock System 100 even
though the script prompts you to include it.
Management component (AMP-2LP)
Management component (LAMP)

Vblock System 240 Management component (AMP-2)
Multiple vCenters
Converged Technology Extension for Isilon storage
Vblock System 320 VPLEX

Cisco Nexus 1000V Switch
Multiple vCenters
Multiple UCS domains
Converged Technology Extension for XtremIO storage
Converged Technology Extension for VMAX3 storage
Converged Technology Extension for VNX storage
Converged Technology Extensions for Unity storage
Converged Technology Extension for VMAX 250F
Converged Technology Extension for VMAX 250FX

Management component (AMP-2)
Management component (AMP-2S)
Multiple vCenters
IPI appliance



Multiple vCenters
IPI appliance

Multiple vCenters

Multiple vCenters
IPI appliance


Multiple vCenters
IPI appliance
Embedded management (eMGMT) for VMAX
Network Attached Storage (eNAS)
Vblock Specialized Systems for Extreme Applications Management component (AMP-2)

Multiple vCenters
Vblock System model types
The following table lists Vblock System model types.
Values for Vblock System types are case sensitive.
Vblock System model types table
Vblock System Model types
Vblock System 100 series Vblock System 100 model BX

Vblock System 100 model DX
Vblock System 200 series 200EX

240

Vblock System Model types
Vblock System 300 series 300EX

300FX
300GX
300HX
320w5300
320w5500
320w5700
320w7500
340w5400
340w5600
340w5800
340w7600
340w8000
350wU300
350wU400
350wU500
350wU600
350wU300F
350wU400F
350wU500F
350wU600F
Vblock System 540 series 540w40T1

540w20T1
540w10T1
Vblock System 700 series 700LX

700MX
720w10k
720w20k
720w40k
740w100k
740w200k
740w400k
740w450f
740w450fx
740w850f
740w850fx
Vblock Specialized System for Extreme Applications VSSXAPP10T1 - One X-Brick

VSSXAPP10T2 - Two X-Bricks
Vblock System connectivity files
Connectivity files contain information that reflects the physical cabling between components such as
network switches and fabric interconnects. When you add a connectivity file to the vblock.xml

configuration, System Library populates the information from the file as part of the discovery process. As
a result, you can monitor the connectivity of components within the VCE System.
Connectivity files are optional, and are not supported for all Vblock Systems.
Connectivity files also contain information for optional components such as a Cisco Nexus
3000 switch or a VPLEX. When you add an optional component to the configuration, the
connectivity for that component is automatically included in the configuration.
Important: As of this release, connectivity files for Vblock System 300 series and Vblock System 700
series do not contain information for Cisco MDS 9513 switches. As a result, Vision software
cannot discover connectivity for Cisco MDS 9513 switches. If you are configuring a VCE
System that contains a Cisco MDS 9513 switch, you should still add a connectivity file to the
vblock.xml configuration so that Vision software can discover connectivity for other
components.
Vblock System 100 series
The following table describes the connectivity files you can select for a Vblock System 100 model:
Connectivity File Select this connectivity file if you are configuring a...
100-connectivity-nexus3064T.xml Vblock System 100 with a Cisco Nexus 3064T switch
Vblock 100 BX-connectivity.xml Vblock System 100 model BX
Vblock 100 DX-connectivity.xml Vblock System 100 model DX
The following table lists the connectivity files you can select for a Vblock System 200:
2X0-connectivity.xml Vblock System 200 or a Vblock System 240
The following table lists the connectivity files you can select for a Vblock System 3XX:
3XX-6248-Segregated_Network-connectivity.xml Vblock System 3XX with the following:
Cisco UCS 6248UP fabric interconnects

Segregated network
3XX-6248-Unified_Network-connectivity.xml Vblock System 3XX with the following:

Unified network
3XX-6296-Segregated_Network-connectivity.xml Vblock System 3XX with the following:

Segregated network

3XX-6296-Unified_Network-connectivity.xml Vblock System 3XX with the following:

Unified network
The following table lists the connectivity file that you select for a Vblock System 540:
540-connectivity.xml Vblock System 540
The following table lists the connectivity files you can select for a Vblock System 7XX:
740-6248-connectivity.xml Vblock System 7XX with the following:

740-6296-connectivity.xml Vblock System 7XX with the following:

7XX(10K)-6248-Segregated_Network-connectivity.xml Vblock System 7XX with the following:

VMAX 10K Series storage array
Segregated network
7XX(10K)-6248-Unified_Network-connectivity.xml Vblock System 7XX with the following:

Unified network
7XX(10K)-6248-with7010F1-connectivity.xml Vblock System 7XX with the following:

Cisco Nexus 7010 switch with an F1 32 port line card

7XX(10K)-6296-Segregated_Network-connectivity.xml Vblock System 7XX with the following:

Segregated network
7XX(10K)-6296-Unified_Network-connectivity.xml Vblock System 7XX with the following:

Unified network



7XX(20k40k)-6248-Segregated_Network- Vblock System 7XX with the following:

connectivity.xml One of the following:
Segregated network
7XX(20k40k)-6248-Unified_Network-connectivity.xml Vblock System 7XX with the following:

Unified network
7XX(20k40k)-6248-with7010F1-connectivity.xml Vblock System 7XX with the following:


7XX(20k40k)-6296-Segregated_Network- Vblock System 7XX with the following:

connectivity.xml VMAX 20K Series storage array
Segregated network
7XX(20k40k)-6296-Unified_Network-connectivity.xml Vblock System 7XX with the following:

Unified network



Generating the vblock.xml file automatically

If you are configuring certain components on Vblock Systems, you must generate the vblock.xml file
automatically using the unattended configuration tool.
About this task
For Dell EMC personnel only: The unattended configuration tool generates the vblock.xml file using
an input configuration file that is generated from the Vblock Automation and Script Tool (VAST) website.
This is not applicable to Vblock System 100 or Vblock System 200.
Before you begin
You must create a configuration (.cfg) file using an editor. Refer to Vblock System configuration file
example (see page 202) for an example.
For Dell EMC personnel only: Download the input configuration file for the correct Vblock System type
from the VAST website to the directory on the Vision Core VM.
Enter the vCenter name as Vcenter1 in the configuration file or when configuring the Vblock System,
this ensures the values in the configuration file are validated.
Procedure
1 Start an SSH session to the Vision Core VM.
2 Log on using the following credentials:
Username: root

3 Type configTool.sh -i /opt/vce/fm/conf/<filename>.cfg.
The full directory path must be added even if the file is within the current filepath's
location.
The vblock.xml file is saved to the /opt/vce/fm/conf directory.
To remove default components for which no data were provided in the input configuration file, you
can include the -r parameter after the filename. The -r parameter should be used by Dell EMC
personnel only.
If you are using a shared vCenter configuration with MSM clustering, the shared vCenter server
must be included in the configuration file used to build the vblock.xml on each Vision Core VM
that is associated with an MSM node within the cluster.
Modifying the vblock.xml file

Complete these steps to modify an existing vblock.xml file.
Before you begin
Procedure
cd /opt/vce/fm/bin
configTool.sh
Press Enter to display the list of available templates, or Enter the full path of an
existing vblock.xml file:
[/opt/vce/fm/conf/template] :
3 Enter the full path of the existing vblock.xml file you are modifying.
The default path is as follows: /opt/vce/fm/conf/.
The script prompts you to select a vblock.xml file, as follows:
(1) vblock.xml
Enter the number that corresponds to the system you are configuring ['0' to specify
new file or directory]:

4 Type 1 to continue.
The script displays the following message: Loaded: /opt/vce/fm/conf/vblock.xml
5 Follow the prompts and make any changes to the attribute information for the Vblock System.
Refer to Configuring the vblock.xml file (see page 37) for information about each prompt and the
attribute information you can enter. When you finished making changes, the script starts the
validation process and displays output such as the following:
Validating VCenter connection: url=https://IP_address/sdk, user=svc-vcenter,

password=password. Please wait...
Validating VCenter connection succeeded!
Validating XmlApi connection. Please wait...
Validating XmlApi connection succeeded!
Validating SNMP connection Please wait...
Validating SNMP connection succeeded!
If the validation is successful, the script displays the following message:
No validation errors on current Vblocks object tree.
If the validation is not successful, verify the information and modify the vblock.xml file as
required.
After validation is complete, the script prompts you with the following:
Enter a filename or Press Enter to save in [/opt/vce/fm/conf/vblock.xml] :
6 Press Enter.
File exists would you like to overwrite (y/n)?
7 Type y. The script displays the following message:

Saved to: /opt/vce/fm/conf/vblock.xml
Configuring Vision software to discover VxBlock System and

VxRack System components
Configuration editor overview

The configuration editor enables you to create and edit the configuration files necessary for VxBlock
System and VxRack System discovery. The configuration editor prompts you for specific information
about the VxBlock System or VxRack System you are configuring.
Vision software then uses the system.cfg to create an xml file that is used for initial discovery of the
compute, network, storage, and management components in the VCE System. The name of this file
varies depending on the system you are configuring. For VxBlock Systems, it creates a vblock.xml file.

For VxRack Systems, it creates a vxrack.xml file. You can add, edit, or delete component information
on a VxBlock System and a VxRack System.
The following VCE Systems can be configured using the configuration editor:
All VxBlock Systems
VxRack System with FLEX
Configuring a VxRack System when a configuration file is not

available
Use the configuration editor new option to create a new configuration file for VxRack System discovery.
About this task
This option is not currently supported for VxBlock System.
Before you begin
You must create a configuration (.cfg) file using an editor. Refer to VxRack System configuration file
examples (see page 215) for an example.
For Dell EMC personnel only: You must create a new configuration file when a configuration file is not
available from VAST.
Procedure
Important: Use PuTTY to access the configuration editor for Windows-based systems as non-
VSCII supported terminals display styling incorrectly.
Username: root
3 Run the following command to launch the configuration editor and create a new configuration:
configSystem new
The VCE Systems configuration editor opens.
To add the components Operating System and Component Credential, you must use
the configSystem edit command.
4 Configure the VCE System with the details outlined in Configuration editor component reference
(see page 109).

What to do next
Add components to the configuration. Refer to Adding a component with the configuration editor
(see page 107) for more information
If you need to edit the configuration after initial creation, run the following command:
configSystem edit
The configuration editor will open and allow you to edit the system configuration.
Ensuring ScaleIO 2.0 discovery

Before ScaleIO 2.0 can be discovered by Vision software, you must validate that the ScaleIO REST API
can communicate with the Meta Data Manager (MDM) and the certificate must be accepted.
Procedure
1 Log on to the ScaleIO Gateway, at https://gateway IP address.
2 Select the Maintain tab.
3 Click Test REST configuration.
4 Enter your MDM credentials to connect to the MDM.
5 Validate that data is returned to the ScaleIO REST API test.
Configuring a VxBlock System or VxRack System when a

configuration file is available
Use the configuration editor's unattended mode to automatically import and validate an existing
system.cfg.
About this task
Use the configuration editor in unattended mode when a system.cfg has already been created but you
need to edit the configuration.
Before you begin
For Dell EMC personnel only:
Download the input configuration file for the correct VCE System type from the VAST website.
Copy the file to the /opt/vce/fm/conf directory on the Vision software virtual machine.
Rename the file system.cfg.

Before you begin
Ensure the system.cfg file is in the /opt/vce/fm/conf directory on the Vision software virtual
machine. If the system.cfg file is not located in this directory, contact VCE Support.
Procedure
Important: Use PuTTY to access the configuration editor for Windows-based systems as non-
VSCII supported terminals display styling incorrectly.
Username: root
3 Run the following command to launch the configuration editor:

configSystem edit -u
The VCE Systems configuration editor imports and validates the system.cfg file.
4 Run the following command to launch the configuration editor and edit a previously imported
configuration:
configSystem edit
The VCE Systems configuration editor opens.
What to do next
Add components to the configuration. Refer to Adding a component with the configuration editor (see
page 107) for more information.
Editing component properties with the configuration editor

Modify a VxBlock System or a VxRack System configuration using the configuration editor.
About this task
You can edit the following component properties:
IP address
Username
Password
Community string

Method
Depending on method and component type, this value can be lower or mixed case
sensitive. Values for most fields are case sensitive, however, for a VxRack System
method, the value is case insensitive.
Sensitive information such as passwords and community strings are masked in the configuration editor
and encrypted in the configuration file.
Before you begin
Ensure you have configured the VxBlock System or VxRack System.
Procedure
1 Type the command configSystem edit to open the configuration editor.
2 Follow these steps to edit the component properties:
a In the configuration editor dialog, use the Next and Back options to navigate to the
component you want to edit.
b Click Tab or use the arrow keys to navigate to the specific property you want to edit.
c Click the Backspace key or the Delete key to edit the properties.
3 Select Save to save the configuration changes and exit the configuration editor, or Cancel to exit
the configuration editor without saving your changes.
The configuration editor uses the system.cfg to create (or update) an xml file that is used for initial
discovery. For VxBlock Systems, it creates a vblock.xml file. For VxRack Systems, it creates a
vxrack.xml file.
Adding a component with the configuration editor

Use the configuration editor to add components to the system configuration.
About this task
Add a new component to the system configuration with the configuration editor.
VxBlock Systems are template based. Components can only be added if they are supported in
the template. For example, Nexus 9000 switches cannot be added to a VxBlock 340.
You can add the following new component types to the system configuration:
Component types Description
Rack This is the Panduit Rack.

Component types Description
Storage array The storage array component is supported on a VxBlock

System, VxRack System and Vscale Fabric Technology
Extension.
Vision software does not support the use of a single
ECOM server (Element Manager) IP for multiple storage
arrays. You must specify a different ECOM server IP for
each additional storage array you want to add.
Switch Available for VxRack Systems and VxBlock Systems.
Compute Server The Product Serial Number is used to identify each

chassis in a VxRack System. Ensure that the value in
the Product Serial Number field for each node in a
specific chassis is identical. If you move a node from one
chassis to another, you must manually update the value
in the Product Serial Number field to ensure that the
value is identical to the value for the existing nodes for
that chassis.
vCenter The <url> attribute of the vCenter, specified in the

configuration file, must be in the form of an IP address to
be discovered by Vision software
Storage virtualizer Available for VxRack Systems and VxBlock Systems.
Application host The application host component is supported on a

VxBlock System.
Operating System Available for VxRack Systems only.
Advanced Management Platform (AMP) Available for VxRack Systems and VxBlock Systems.
Extra properties for selected component Available for VxRack Systems only. This component
type is only displayed when a storage array is selected.
Before you begin
Ensure you have configured the VxBlock System or VxRack System system.
Refer to Configuration editor component reference (see page 109) for component information.
Procedure
1 Type the command configSystem edit to open the configuration editor.
2 Select Add in the Configuration Editor dialog. The Add Component dialog opens.
3 Select the component type you want to add and click Enter.
4 Select Add. An empty component form is added as the last component in the sequence.
a In the configuration editor dialog, use the Next and Back options to navigate to the
component you want to edit.
b Click Tab or use the arrow keys to navigate to the specific component property you want to
edit.

c Click the Backspace key or the Delete key to edit the property fields.
The configuration editor uses the system.cfg to create (or update) an xml file that is used for initial
discovery. For VxBlock Systems, it creates a vblock.xml file. For VxRack Systems, it creates a
vxrack.xml file.
Related information
Configuration editor component reference (see page 109)
Configuring a VxBlock System or VxRack System when a configuration file is available (see page 105)
Deleting a component with the configuration editor

Use the configuration editor to remove components from the system configuration.
About this task
Delete components from the system configuration with the configuration editor.
Before you begin
Ensure you have configured the VxBlock System or VxRack System.
Procedure
1 Use the Next and Back options to navigate to the component type you want to delete in the VCE
Systems configuration editor dialog.
2 Select Delete. The Component deletion dialog opens displaying the following message:
Are you sure you wish to delete the component?
Type Yes and press Enter to delete the component. The Component deletion dialog closes
and the component is deleted.
Type No and press Enter if you do not want to delete the component. The Component
deletion dialog closes and you are returned to the configuration editor dialog.
Related information
Configuring a VxBlock System or VxRack System when a configuration file is available (see page 105)
Configuration editor component reference

Use the tables to configure VCE Systems with the configuration editor. All values, including location
information, are mandatory.
VxBlock System configuration settings
Field Rules Field value example
System type Dictates the VxBlock System product. The VXBLOCK

mandatory value is VXBLOCK.
Product Dictates the VxBlock System product. The VxBlock

mandatory value is VxBlock.
Product type The first three digits determine the VxBlock 320XXXX
System type. This is a mandatory field.
Serial number Should be a meaningful value. VB320-975-318-642
Component tag Should be a meaningful value. VB-320
Geo The data center location. Marlborough, MA
Building The building name. Building 4
Floor The floor number. 1
Room The room number. 1
Row The row number. 1
Tile The tile number. 1
VxRack System configuration settings
Field Rules Field value example
System type Dictates the VxRack System product. The VXRACK

mandatory value is VXRACK.
Product The VxRack System product. The mandatory VxRack

value is VxRack.
Product type VxRack System with FLEX is currently the VxRack1000FLEX

only supported VxRack System product
type. This is a mandatory field.
Serial number Can be any meaningful value. VX1000FLEX-77

7-888-999
Component tag Can be any meaningful value. VX1000FLEX
Geo The data center location. Marlborough, MA
Building The building name. Building 4
Floor The floor number. 1
Room The room number. 1
Row The row number. 1
Tile The tile number. 1

Component configuration settings
Component type VCE Systems Field Rules Field value

example
Compute server VxBlock System, In AMP Specifies if the x

VxRack System component is a part of
the AMP configuration.
Compute server Name The default name for sys

UCS servers is sys. For
each additional UCS
server, ensure the name
is in the following format:
sysXXXX where sys is
lowercase and XXXX is a
unique number. For
example sys2.
Compute server Type Must be one of the UCS

following: UCS, C200M1,
C200M2,C220M3,
C220M4,C240M3,
C240M4,QUANTA,
KYLIN, DELL
Compute server Component tag Can be any meaningful VMABO-UCS-1

value.
Compute server Server IP Address Should be a dotted IP 10.1.139.30

address. In the case of
QUANTA and DELL, you
can specify ranges by
separating the first and
last IP in a range with a
hyphen. For example,
10.1.139.30 -
10.1.139.35.
Compute server Username The SSH username. admin
Compute server Method Must be one of the REDFISH

following: REDFISH,
SNMPV2C, IMPIV2,
WEBSERVICE, SSH
Compute server Password The SSH password. password
Compute server Community The SNMP community public

string. Community string
is only necessary for the
SNMP method.
For types DELL and
KYLIN, there is no
community string.
Operating system VxRack System Type Must be: REDHAT REDHAT
Operating system Component tag Can be any meaningful RedHat-1

value.

example
Operating system IP Address Can be any meaningful XXX.XXX.XXX.X

value. You can specify IP XX-
ranges by separating the XXX.XXX.XXX.X
first and last IP in a range XX
with a hyphen. For
example, 10.1.139.30 -
10.1.139.35.
Operating system Username The SSH username root
Operating system Method Must be: SSH SSH
Operating system PasswordMethod The SSH password password

(optional if using SSH
public key authentication)
AMP VxBlock System Amp type Can be any of the AMP-2S

VxRack System following: AMP-KYL
VxBlock System: AMP-
type, where type is the
AMP model in your
environment
VxRack System: AMP-
KYL
AMP Component tag Can be any meaningful Management

value.
AMP Serial number Can be any meaningful AMP-KYL-123

value.
Component VxRack System IP Range Should be a range of XXX.XXX.XXX.X

credentials dotted IP addresses. You XX-
can specify ranges by XXX.XXX.XXX.X
separating the first and XX
last IP in a range with a
hyphen. For example,
10.1.139.30 -
10.1.139.35.
Component Community The SNMP community public

credentials string.
Component Username The username root

credentials
Component Method Must be one of the SSH

credentials following: IPMIV2,
SNMPV2C,
WEBSERVICE, SSH,
REDFISH
Component Password The password password

credentials
Rack VxBlock System, Rack ID The unique identifier of a 1

VxRack System rack.

example
Rack Rack Type Refers to the model of 1

rack.
Rack Rack Format US
Rack Gateway IP Address Specifies the default 192.168.1.X

gateway for a rack.
Rack Method Must be one of the snmpv2c

following: IPMIV2,
SNMPV2C,
WEBSERVICE, SSH
Rack Community The SNMP community public

string configured on the
rack.
Switch VxBlock System, In AMP Specifies if the x

Switch Type Must be one of the Nexus5000

following: CA3750,
MDS9000,Nexus3000,
Nexus5000, Nexus7000,
Nexus9000,Nexus1000V
or NSX.
Switch Component tag Must be one of the N5A

following: N1A, N1B,
N3A, N3B, N5A, N5B,
N7A, N7B, N9A, N9B,
MGMT-N1A, MGMT-
N1B, MGMT-N3A,
MGMT-N3B, MGMT-
N5A, MGMT-N5B,
MGMT-N7A, MGMT-
N7B, MGMT-N9A,
MGMT-N9B, NSX.
Switch Method Must be one of the snmpv2c

following: IPMIV2,
SNMPV2C,
WEBSERVICE, SSH
Switch IP Address Should be a dotted IP 10.1.139.22

address.
Switch Username The SSH username. admin
Switch Password The password password
Switch Community The SNMP community public

string.
Storage array VxBlock System In AMP Specifies if the x

VNX component is a part of

example
Storage array Type Must be one of the VNX5500

VNX following:
VNX,VNX5200,VNX5300
,VNX5400,VNX5500,VN
X5600,VNX5700,VNX58
00,VNX7500,VNX7600,V
NX8000,VNXe,VNXe315
0,VNXe3300
Storage array Component tag Must be one of the VNX5500-ARRAY

VNX following:
VNXe3150-ARRAY,
VNXe3300-ARRAY,
VNX5300-ARRAY,
VNX5500-ARRAY,
VNX5700-ARRAY,
VNX7500-ARRAY,
VNX5200-ARRAY,
VNX5400-ARRAY,
VNX5600-ARRAY,
VNX5800-ARRAY,
VNX7600-ARRAY,
VNX8000-ARRAY,
VNXe-ARRAY, VNX-
ARRAY
Storage array IP Address Should be a dotted IP 10.1.139.52

VNX address.
Storage array Username The username. admin

VNX
Storage array Password The password. password

VNX
Storage array Which Should be one of the ECOM Server

VNX following: ECOM Server,
Control Station, SPA,
SPB
Storage array Method Must be a dotted IP 10.1.139.42

VNX address. This is the CIM
entry point when Which
is an ECOM server or
Control Station.
Storage array Username The username. sysadmin

VNX

VNX
Storage array Community The SNMP community public

VNX string.

example

VMAX component is a part of
Storage array Type Must be one of the VMAX10K

VMAX following:
VMAX,VMAX10K,VMAX2
0K,VMAX40K,VMAX100
K,VMAX200K,VMAX400
K,VMAX3,VMAXe,
VMAX450F,
VMAX450FX,
VMAX850F,
VMAX850FX
Storage array Component tag Must be one of the VMAX10K-ARRAY

VMAX following:
VMAX10K-ARRAY,
VMAX20K-ARRAY,
VMAX40K-ARRAY,
VMAX3-ARRAY,
VMAX100K-ARRAY,
VMAX200K-ARRAY,
VMAX250F-ARRAY,
VMAX250FX-ARRAY,
VMAX400K-ARRAY,
VMAX-ARRAY, VMAXe-
ARRAY, VMAX450F-
ARRAY, VMAX450FX-
ARRAY, VMAX850F-
ARRAY, VMAX850FX-
ARRAY

VMAX address.
Storage array Which Should be one of the VMAX

VMAX following: VMAX

VMAX address. This is the CIM
entry point when Which
Control Station.
Storage array Username The username. fmuser

VMAX

VMAX

VMAX w/ gateway component is a part of

example
Storage array Type Must be one of the VMAX10K

VMAX w/ gateway following:
VMAX,VMAX10K,VMAX2
0K,VMAX40K,VMAX100
K,VMAX200K,VMAX400
K,VMAX3,VMAXe,
VMAX450F,
VMAX450FX,
VMAX850F,
VMAX850FX
Storage array Component tag Must be one of the VMAX10K-ARRAY

VMAX w/ gateway following:
VMAX10K-ARRAY,
VMAX20K-ARRAY,
VMAX40K-ARRAY,
VMAX3-ARRAY,
VMAX100K-ARRAY,
VMAX200K-ARRAY,
VMAX400K-ARRAY,
VMAX-ARRAY, VMAXe-
ARRAY, VMAX450F-
ARRAY, VMAX450FX-
ARRAY, VMAX850F-
ARRAY, VMAX850FX-
ARRAY

VMAX w/ gateway address.
Storage array Which Should be: VMAX VMAX

VMAX w/ gateway

VMAX w/ gateway address.
Storage array Username The VMAX username. fmuser

VMAX w/ gateway
Storage array Password The VMAX password. password

VMAX w/ gateway
Storage array Which The second Which field gateway

VMAX w/ gateway should be: gateway
Storage array Method The second Method is a 10.1.139.42

VMAX w/ gateway dotted IP address.
Storage array Username The NAS administrator nasadmin

VMAX w/ gateway username.
Storage array Password The NAS administrator password

VMAX w/ gateway password.

example

XtremIO component is a part of
Storage array Type Must be the following: XTREMIO

XtremIO XTREMIO
Storage array Component tag Must be the following: XIO-ARRAY-1

XtremIO XIO-ARRAY-1

XtremIO address.
Storage array Which Should be: XTREMIO XTREMIO

XtremIO
Storage array Method Should be xml. xml

XtremIO
Storage array Username The XtremIO username. admin

XtremIO
Storage array Password The Xtremio password. password

XtremIO

Isilon component is a part of
Storage array Type Must be the following: ISILON

Isilon ISILON
Storage array Component tag Must be the following: ISILON-ARRAY-

Isilon ISILON-ARRAY- CLUSTER-1
CLUSTER-1

Isilon address.
Storage array Method Must be one of the snmpv2c

Isilon following: IPMIV2,
SNMPV2C,
WEBSERVICE, SSH
Storage array Username The Isilon username. admin

Isilon
Storage array Password The Isilon password. password

Isilon

Unity component is a part of
Storage array Type Must be the following: UNITY

Unity UNITY

example
Storage array Component tag Must be the following: UNITY-ARRAY-1

Unity UNITY-ARRAY-x
where x is the number of
the array

Unity address.
Storage array Method Must be restApi. restApi

Unity
Storage array Username The Unity username. admin

Unity
Storage array Password The Unity password. password

Unity
VCenter VxBlock System, In AMP Specifies if the x

If you are configuring a
shared vCenter with
MSM, be sure to include
the shared vCenter
server information in the
configuration file on each
Vision Core VM that is
associated with an MSM
node.
Do not define a shared
vCenter as a part of the
AMP if the shared
vCenter resides on a
Shared Management
Platform (SMP), rather
than on a VCE System.

example
VCenter Name Should be vCenter1, Vcenter1

vCenter2, ... vCenterN,
and so forth.
shared vCenter with
the shared vCenter
node.
When a shared vCenter
resides on an SMP, that
SMP will not be
discovered. However, the
fact that the vCenter is
shared by multiple VCE
Systems will be apparent
in the results returned for
a find VIManager
query.
vCenter URL Should be a dotted IP 10.1.139.39

address to the vCenter
server.
shared vCenter with
the shared vCenter
node.
VCenter Username The vCenter server SDK vb300swqa

username. \administrato
If you are configuring a r
shared vCenter with
the shared vCenter
node.

example
VCenter Password The vCenter server SDK password

password.
shared vCenter with
the shared vCenter
node.
Application host VxBlock System Name The Application host app-host-1

name.
Application host IP Address Should be a dotted IP 10.1.139.42

address.
Application host Username The username. admin
Application host Password The password. password
Storage virtualizer VxBlock System Type Must be the following: VPLEX

VPLEX VPLEX
Storage virtualizer Component tag Can be any meaningful VPLEX-000-XXX

VPLEX value.
Storage virtualizer Address Should be a dotted IP 10.1.139.5

VPLEX address.
Storage virtualizer Method Must be xml. xml

VPLEX
Storage virtualizer Username The username. service

VPLEX
Storage virtualizer Password The password. password

VPLEX
Storage virtualizer VxRack System Type Must be the following: SCALEIO

ScaleIO SCALEIO
Storage virtualizer Component tag Can be any meaningful SCALEIO-000-

ScaleIO value. XXX
Storage virtualizer Address Should be a dotted IP 10.3.249.240

ScaleIO address.
Storage virtualizer Method Must be restApi restApi

ScaleIO
Storage virtualizer Username The username. admin

ScaleIO
Storage virtualizer Password The password. password

ScaleIO

Related information
Adding a component with the configuration editor (see page 107)
Configuring VCE System components for Vision software

discovery
Follow these component-specific configuration steps before starting discovery to allow the System Library
to connect with VCE System components.
Configuring the Converged Technology Extension for Isilon storage

Configure the technology extension so that it can be discovered by Vision software.
In Vision software version 3.1.1 and higher, Converged Technology Extension for
Isilon storage is supported on a Vblock System and a VxBlock System only.
Creating a non-admin user for Isilon
Create a non-admin user when configuring SSH and REST API credentials of the Isilon cluster in the
vblock.xml file.
Before you begin
Procedure
1 Start an SSH session to the Isilon cluster using root user credentials.
For each step below, replace the variable text as follows:
Replace ${VISION_USERNAME} with a username of your choice.
Replace ${VISION_PASSWORD} with a password of your choice.
Replace ${VISION_ROLE} with a role of your choice.
a Type the following command to create a user for Vision software:
isi auth users create --name=${VISION_USERNAME} --enabled=yes --password=$

{VISION_PASSWORD} --password-expires=no
b Type the following command to create a role for Vision software:
isi auth roles create --description='Role for Vision Application' --name=$

{VISION_ROLE}

c Type the following command to add read-only privileges for logging on to the console:
isi auth roles modify ${VISION_ROLE} --add-priv-ro=ISI_PRIV_LOGIN_CONSOLE
d Type the following command to add read-only privileges for accessing the web API:
isi auth roles modify ${VISION_ROLE} --add-priv-ro=ISI_PRIV_LOGIN_PAPI
e Type the following command to add read-only privileges for logging on via SSH:
isi auth roles modify ${VISION_ROLE} --add-priv-ro=ISI_PRIV_LOGIN_SSH
f Type the following command to add the new Vision software user to the new role:
isi auth roles modify ${VISION_ROLE} --add-user=${VISION_USERNAME}
2 Type isi_visudo to open a vi editor. Enter the code manually, to avoid a syntax error due to
the command length.
a Append the following text:
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi_nodes

${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi_gather_info
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi job start TreeDelete --
path /ifs/data/Isilon_Support/pkg/VisionIO
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi_gather_smb_info
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi license status
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi networks list interfaces
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi networks list interfaces -w
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi auth roles list --verbose
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi networks list pools --verbose
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi networks list subnets --verbose
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi snmp list
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi email list
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi networks
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi network
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/sbin/isi_log_server list
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi_ntp_config list
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi events notifications list
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi nfs settings export view
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi nfs settings zone view
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi nfs settings global view
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi auth users list --verbose
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi_promptsupport -s
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi worm domains list
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi worm cdate view
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi_for_array -s isi_drivenum -bsT
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi nfs exports list --verbose
${VISION_USERNAME} ALL=(ALL) NOPASSWD: /usr/bin/isi_classic networks list
interfaces -w

Configuring SNMP for Isilon
Configure SNMP for Isilon by changing the default SNMP trap message type.
About this task
By default, Isilon sends SNMP traps with the message type: Inform. This should be changed to: Trap.
Follow this procedure to change the default SNMP message type.
Procedure
1 Start an SSH session to the Isilon cluster using root user credentials.
2 To change the default SNMP message format from Inform to Trap, type the following command:
isi_gconfig celog.celog_settings.use_snmp_trap=true
Configuring Isilon for discovery
Edit the component-services.properties file if you have to create a subnet that has a lower value
than the Isilon management subnet value.
About this task
You must edit the component-services.properties file for Vision software to discover Isilon. If
Isilon has a subnet value that is lower than the management subnet value, the correct IP addresses are
not returned during discovery and it fails.
Before you begin
Log on to Isilon, navigate to Cluster Management > Network Configuration, and note the values for
management subnet. The following is an example of the management subnet.
subnet0 - Default ext-1 subnet

Subnet: 10.3.50.0
Netmask: 255.255.255.0
Gateway: 10.3.50.1
SmartConnect zone: mpe-isi-mgmt.vmo.lab
Procedure
1 Navigate to opt/vce/fm/conf and open the component-services.properties file.
2 Edit the isilon.services.discovery.cluster.subnet value to the management subnet

name. For example:
isilon.services.discovery.cluster.subnet=subnet0
3 Edit the isilon.services.discovery.cluster.interface value to the interface value.

For example:
isilon.services.discovery.cluster.interface=ext-1

4 Edit the isilon.services.discovery.cluster.override.default.ssh.command
value to true and save the file. For example:
isilon.services.discovery.cluster.override.default.ssh.command=true
5 Type startFMagent to start FMAgent. If successful, you will see this message:
isilon.IsilonDiscoveryService - invoking discovery for StorageArray 'ISILON-ARRAY-

CLUSTER-1'
Configuring Red Hat Enterprise Linux for discovery

Configure credentials on each Red Hat instance for Vision software to discover the Red Hat Enterprise
Linux Operating System.
About this task
If the Vision Core VM OVA is reinstalled, it will not retain any certificate configuration. Follow this process
for each Red Hat instance to reconfigure Red Hat for discovery by Vision software.
Discovery of Red Hat Enterprise Linux is supported on a VxRack System only.
Before you begin
Ensure you have the necessary credentials to create a new user.
Procedure
/opt/vce/fm/bin/rhel-create-vision-user.sh --user <user> --usergroup

<group> <IP address>
where <user> is the Red Hat username, <group> is the group the user belongs to, and <IP
address> is the Red Hat server address.
Username and usergroup are optional arguments. If unspecified, default values will be used.
Specify an IP range to run the script against each Red Hat instance. For example,
10.3.249.191-195
For example,
rhel-create-vision-user.sh --username TestUser --usergroup VCE 10.3.249.191
2 The system will prompt for a password for the newly created user.
3 The system will prompt you for administrator credentials. For example, the root user, or another
user that belongs to the sudoer group.
4 Run SSH to connect to the Red Hat instance and validate setup: SSH
TestUser@10.3.249.191
Configuring the IPI appliance for discovery
You must configure the SNMP NMS table to contain the Vision IP address in order for Vision software to
discover the IPI appliance.
Before you begin
Ensure you have the necessary credentials to access the IPI appliance interface.
Configure the vblock.xml file, or the VCE System configuration file, specifying the IPI appliance
IP and community string.
Procedure
1 Log on to the IPI appliance interface. Enter your username and password.
2 Select SNMP NMS from the left-hand navigation pane.
3 Enter the Vision IP address in the NMS IP Address field.
4 Enter the community string specified in the vblock.xml or in the VCE System configuration file,
for the IPI appliance in the Community String field.
5 Select Read Only from the NMS Access field drop-down menu, and click Save.
What to do next
Start FMAgent and when discovery is complete, verify that the IPI appliance is present in the REST API.
Creating a Vision software user in the VxRack Controller

Create a Vision software user with read-only management rights through the VxRack Controller before
adding the VxRack Controller to the input configuration file.
About this task
This procedure is supported on a VxRack System only.
Before you begin
Ensure that you have the authentication credentials for the default VxRack Controller user.
Start an SSH session to the Vision Core VM.
Procedure
1 Obtain a list of the VxRack Controller users by running the following command:
ipmitool -I lanplus -H [IP] -U [admin_user] -P [admin_pwd] -v user list
2 Choose the next available ID from the list of VxRack Controller users.

3 Run the following commands, replacing IP, admin_user, and admin_pwd as appropriate:
ipmitool -I lanplus -H [IP] -U [admin_user] -P [admin_pwd] -v user set name 3

[vision_user]
ipmitool -I lanplus -H [IP] -U [admin_user] -P [admin_pwd] -v user set password 3

[vision_pwd]
ipmitool -I lanplus -H [IP] -U [admin_user] -P [admin_pwd] -v user priv 3 2
ipmitool -I lanplus -H [IP] -U [admin_user] -P [admin_pwd] -v channel setaccess 14 3

link=on ipmi=on privilege=2
ipmitool -I lanplus -H [IP] -U [admin_user] -P [admin_pwd] -v user enable 3
The read-only Vision software user is created and their password and role are configured.
What to do next
1 Verify that the read-only Vision software user is created by running the following command:
ipmitool -I lanplus -H [IP] -U [vision_user] -P [vision_pwd] -L USER bmc info
2 Add the read-only Vision software user and password that you created to the configuration input
file.

Configuring Vision software
Enabling northbound communication through SNMP

Complete these steps to configure SNMP communication between Vision software and your network
management system (NMS). This procedure involves adding access credentials and specifying your NMS
as the trap target.
Before you begin
Ensure you have the following information:
IP address of the trap target
SNMPv1 or SNMPv2c community string
Procedure
configureSNMP
The script prompts you with the following list of actions:
[root@hostname ~]# configureSNMP

Select the your action
1) Add v1/v2c community with read only permissions
2) Add v1/v2c community with read/write permissions
3) Add v1/v2c trap target
4) Add v3 user with minimal security (no auth, no priv)
5) Add v3 user with moderate security (auth, no priv)
6) Add v3 user with maximum security (auth, priv)
7) Add v3 trap target
8) List community/user and trap targets
9) Delete v1/v2c community
10) Delete v3 user
11) Delete trap target
12) Done
#?

2 Type one of the following values:
Type 1 to create a read-only community string.
Type 2 to create a read/write community string.
The script prompts you to enter the following information:
SNMP version
Community string
After you specify the SNMP version and community string, the script returns to the list of actions.
3 Type 3 to create a trap target. The script prompts you to enter the following information:
SNMP version
Community string
IP address of the trap target.
After you specify the trap target, the script returns to the list of actions. Repeat this step to enter
another trap target.
4 Type 12 when you are done configuring SNMP. The script then prompts you to update the
following file: /etc/srconf/agt/snmpd.cnf
5 Type one of the following values:
Type 1 to commit your changes.
Type 2 to discard your changes.
Updating the IP tables on the Vision Core VM

Complete these steps to update the IP tables on the Vision Core VM. This procedure involves running a
script that parses the vblock.xml file and updates the IP tables so that Vision software does not block
traffic from VCE System components.
Before you begin
Create the vblock.xml file.

Procedure
Run the following command:
/opt/vce/fm/bin/runConfigCollector -iptablesOnly
Vision software parses the vblock.xml and updates IP table rules to include the IP addresses of VCE
System components. The following is an example of the output from this command:
time_stamp INFO [Thread: main] [ConfigureCollector] fmversion=version

...
time_stamp INFO [Thread: main] [VblockConfigParser] vcenter info added for vblock:Vblock
System serial
time_stamp INFO [Thread: main] [ConfigureCollector] config file loaded.
time_stamp INFO [Thread: main] [ConfigureCollector] total switch: 5
time_stamp INFO [Thread: main] [UCSXMLApiDriver] successfully log in to https://IP_address/
nuova
time_stamp INFO [Thread: Thread-1] [UCSXMLApiDriver] no need to refresh within ms:
time_stamp INFO [Thread: main] [UCSXMLApiDriver] logout ...https://IP_address/nuova
time_stamp INFO [Thread: main] [ConfigureCollector] total compute systems:1
time_stamp INFO [Thread: main] [ConfigureCollector] total storage systems:1
time_stamp INFO [Thread: main] [ConfigureCollector] reset the iptables:[IP_address,
IP_address, IP_address, IP_address, IP_address, IP_address, IP_address, IP_address]
iptables was updated.
time_stamp INFO [Thread: Thread-1] [UCSXMLApiDriver] terminate the refresh
thread:java.lang.InterruptedException: sleep interrupted
time_stamp INFO [Thread: main] [VCECmdExec] Do not register the VCECmdExec since its
timeout=0,/opt/vce/fm/bin/restore_iptables.sh
successfully restored the iptables service
time_stamp INFO [Thread: main] [ConfigureCollector] done the iptables
time_stamp INFO [Thread: main] [ConfigureCollector] No configure collector handlers are
configured to run.
time_stamp INFO [Thread: Thread-0] [FMShutdownHandler] FMShutdown Handler call start
time_stamp INFO [Thread: Thread-0] [FMShutdownHandler] FMShutdown Handler call end
What to do next
Confirm the IP addresses for VCE System components are included in the IP table rules with the
following command:
iptables -L
Installing compliance content on the Vision Core VM

Installing compliance content ensures that the Compliance Checker has the most recent compliance
information for your Vblock System. Compliance content includes policies for RCMs, Security Compliance
Validation, and VCE Technical Advisories compliance.
Before you begin
Installing compliance content on Vision Core is supported on a Vblock System only. For VxBlock Systems
and a VxRack System, you need to install the compliance content as part of the multisystem
management (MSM) installation.

This step is only applicable if you are installing compliance content on the Vision Core VM for a
Vblock System.
Download the compliance content RPM files.
Ensure you have the CAS authentication credentials for the administrator user. The default
credentials are:
Username: admin
Password: 7j@m4Qd+1L
Procedure
1 Copy the RPM file, or files, to any location on the Vision Core VM.
2 Change to the directory that contains the RPM file.
3 Type the following command:
rpm -Uvh content_rpm_name-build_number.rpm
Type this command and perform the following steps separately for each RPM file you
plan to install.
Where:
rpm is the command to run RPM Package Manager.

-Uvh is the option to upgrade the RPM.
content_rpm_name-build_number.rpm is the name of the RPM file.
For example, vce-compliance-content-build_number.rpm and vce-compliance-
content-hardening-build_number.rpm.
For example, the following command installs the Vision Core compliance content:
rpm -Uvh vce-compliance-content-build_number.rpm
The command saves compliance content from the RPM file to the following location on the Vision
Core VM: /opt/vce/compliance/content.
cd /opt/vce/compliance/content
sh install_content.sh

6 Authenticate to the CAS service when prompted.
The installation script uses the API for Compliance Checker to install the compliance content. For
this reason, you must authenticate to the CAS service.
Results
The script installs the compliance content and a message displays as shown in the following example:
CONTENT INSTALL RESULTS

Successfully imported content:
-----------------------------------------------------------
Hardening Content for VCE Vblock (TM) System 300 family
RCM Content for VCE Vblock (TM) System 300
Related information
Downloading compliance content for the Vision Core VM (see page 9)
Starting VCE System discovery

After you configure the vblock.xml file, or the VCE System configuration file, you should start the
discovery process so that the System Library can connect to VCE System components.
Before you begin
Accept the end user license agreement (EULA).
Configure the vblock.xml file or the VCE System configuration..
Enable northbound communication via SNMP (see page 127)
Enabling northbound communication via SNMP is supported on a Vblock System and

a VxBlock System only.

Procedure
startFMagent
The FM Agent services start and the following message displays:
[root@<hostname> log]# startFMagent

Enabling FMagent services to start automatically...
Waiting for the FMagent services to start.................
vce-fm-master is running (pid=19357 )
vce-fm-adapter is running (pid=19871 )
vce-fm-agent is running (pid=20130 )
vce-fm-net-snmpd (pid=19617 ) is running
vce-fm-naaagent is running (pid=20409 )
Verifying SNMP communication

Complete these steps to verify the SNMP interface on the Vision Core VM.
Before you begin
Configure the vblock.xml file.
Start the discovery process.
Enable northbound communication via SNMP.
Procedure
getmany v2c localhost community_string entPhysicalDescr
Where:
localhost is the hostname of the Vision Core VM.
community_string is the community string that you used to configure SNMP communication.
Important: Enclose non-alphanumeric characters in single quotes; for example, str'!'ng'@'

Results
Vision software returns physical entity descriptions for the VCE System and all components, as in the
following example:
entPhysicalDescr.1 = VCE Vblock Platforms

entPhysicalDescr.2 = 340w5400 (Vblock 340w5400)
entPhysicalDescr.3 = Vblock Racks
entPhysicalDescr.4 = Vblock Compute
entPhysicalDescr.5 = Vblock Network
entPhysicalDescr.6 = Vblock StorageentPhysicalDescr.13 = Panduit 28U Rack
entPhysicalDescr.1003 = Cisco UCS System
entPhysicalDescr.1004 = Cisco UCS Chassis 1
...
Confirming discovery is complete

You must check the FMAgent.log to determine if the discovery process is complete. The discovery
process takes several minutes to complete.
About this task
Depending on the VCE System on which you installed Vision software, you should allow up to 15 minutes
for the discovery process.
Before you begin
Procedure
cd /opt/vce/fm/logs/
grep -i 'current status' FMA* | grep 100% | grep discoverAll
The command searches FMAgent.log for messages that indicate discovery is complete, as
follows:
INFO time_stamp [thread_pool] : VblockDiscoveryTask - Current status of Vblock System

discoverAll: started at time_stamp with 100% finished, Current finishing component:
INFO time_stamp [thread_pool] : FMEventServiceFactory - publish event: id=Vblock
System allCurrent status of Vblock System discoverAll: started at time_stamp with 100%
finished, Current finishing component:

Verifying VCE System discovery
After you have successfully created the vblock.xml file, or the VCE System configuration file, and
started discovery of the VCE System components, you should complete these steps to verify discovery.
Before you begin
Configure the vblock.xml file, or the VCE System configuration file.
Ensure you have the CAS authentication credentials for the administrator user. The default
credentials are:
Username: admin
Password: 7j@m4Qd+1L
Procedure
1 Open a web browser from the VMware vCenter Server host on the VCE System.
2 Navigate to the following URL: https://fqdn:8443/fm/vblocks for a Vblock System, or

https://fqdn:8443/fm/systems for a VCE System such as a VxRack System.
Where fqdn is the fully qualified domain name (FQDN) of the Vision Core VM.
3 Authenticate to the CAS service when prompted.
4 The API for System Library returns an XML response with details for the VCE System
components.
The discovery process can take several minutes to complete. If you get an empty XML response,
you should wait a few minutes and then confirm discovery is complete.
5 Navigate through the XML response to verify discovery of VCE System components as required.

Results
The XML response returns details about the VCE System as well as information about individual
components, including health status. The following XML snippets provides an example XML response:
<vblocks>
<vblock>
<alias>340w5400</alias>
<dbId>6188</dbId>
<description>340w5400 (Vblock 340w5400)</description>
<moId>V07FN4013002CM</moId>
<name/>
<url>
https://fqdn:8443/fm/vblocks/6188
</url>
<assetId/>
<calculatedStatus>major</calculatedStatus>
<firmwareRev/>
<fru>false</fru>
<hardwareRev/>
<lastOperStatus>critical</lastOperStatus>
<lastStatusChange>time_stamp</lastStatusChange>
<systems>
<system>
<alias>VxRack1000FLEX</alias>
<dbId>5188</dbId>
<description>VxRack VCE System</description>
<moId>VX1000FLEX-975-318-642</moId>
<name />
<uniqueId>VX1000FLEX-975-318-642</uniqueId>
<url>https://fqdn:8443/fm/systems/5188</url>
<assetId />
<calculatedStatus>critical</calculatedStatus>
<firmwareRev />
<fru>false</fru>
<hardwareRev />
<lastOperStatus>notApplicable</lastOperStatus>
<lastStatusChange>time_stamp</lastStatusChange>
Installing the Vision Plug-in for vCenter

In Vision software, installing the Vision Plug-in for vCenter is supported on a Vblock System only.
Configuring the Vision Plug-in Manager

The Vision Plug-in Manager (VPM) is a framework for deploying the Plug-in for vCenter to VMware
vCenter Server. If upgrading from Vision software Version 2.5.x or earlier, you must configure the VPM
before you install the Plug-in for vCenter if you are upgrading from Vision software Version 2.5.x or
earlier.
About this task
To configure the Vision VPM, you must specify the email address of the administrator who
manages the VMware vCenter Server plug-ins. You must also specify the hostname of the
vCenter Server and administrator credentials if they are not set in the vblock.xml file.

If the vpm-settings.properties file has already been created in the /opt/vce/
tools/vpm/conf folder, then the following message appears:
A VPM configuration file has already been created. To overwrite the existing file, use
the 'vpm setup force option, which will configure VPM with the settings in vblock.xml
The vpm-settings.properties file does not need to be updated after upgrade unless the
administrator email address or the vCenter credentials in the vblock.xml file has changed.
If you specify a command line parameter with a backslash character (\), you must escape the
backslash character with an additional backslash character. For example, to provide the vCenter
server hostname and credentials domain\username, you must type domain\\username.
The Administrator group must have permission for the following resources:
Extension.Register
Extension.Unregister
Extension.Update
Before you begin
Uninstall the existing Plug-in for vCenter from the Vision Core VM.
Ensure that the user is part of the Administrator user group in the VMware vSphere Client. Refer
to the VMware vSphere documentation.
Ensure that the user has administrative permission to the vCenter Server. For example, the local
Administrator is granted the Administrator role below.
Ensure that the /opt/vce/fm/conf/vblock.xml file is configured with the vCenter Server
hostname and administrator credentials.
Procedure
cd /opt/vce/plugins

vpm setup
Type vpm setup -help for usage options. The following message appears:
VPM configuration file does not exist yet. Use the setup command to configure VPM.
3 Type the email address when prompted.
Extension administrator email address: username@companyname.com
4 Type the FQDN of the vCenter Server.
5 Type the username and password for the vCenter server. The username and password must be
for the administrator user. The following message appears:
The VPM configuration has been saved to '/opt/vce/tools/vpm/conf/vpm-

settings.properties'
Installing the Plug-in for vCenter

Use this procedure to install the Plug-in for vCenter on your vCenter Server.
Before you begin
Ensure one of the following versions of the VMware vSphere Web Client is installed:
5.5
6.0
The compatibility details of each version of the VMware vSphere Web Client (VWC) are outlined
in the following table:
Compatibility with: vCenter 5.5 vCenter 6.0
VWC 5.5 Yes No
VWC 6.0 Yes Yes
Ensure the vCenter Server host can resolve the fully qualified domain name (FQDN) of the Vision
Core VM.
If you use a host file for FQDN resolution, remove the entry after you install the Plug-in
for vCenter. Removing the host file entry ensures that it does not conflict with any IP
address changes you make.
The Administrator group must have permission for the following resources:
Extension.Register

Extension.Unregister
Extension.Update
Ensure that the user is part of the Administrator user group in the VMware vSphere Client. Refer
to the VMware vSphere documentation.
Ensure that the user has administrative permission to the vCenter Server. For example, the local
Administrator is granted the Administrator role below.
Procedure
cd /opt/vce/plugins

2 Type the following command to install the Plug-in for vCenter:
rpm -Uvh vce-plugin-version_number-build_number.x86_64.rpm
The following messages display:
Preparing... ########################################### [100%]

1:vce-plugin ########################################### [100%]
Installing VCE Vision (TM) plugin
Successfully imported 'vce-plugin-version_number.zip'
Successfully deployed 'vce-plugin-version_number.zip'
Successfully registered 'vce-plugin-version_number.zip'
To enable component counts to be shown at the top level on VMware vSphere 6.0
installations, follow these steps:
a Log on to the machine where VMware vSphere 6.0 is installed.
b Open \ProgramData\VMware\vCenterServer\cfg\vsphere-client
\webclient.properties
c Locate the property named large.inventory.mode.
d Change the value to false.
e Reload any open browser instances of vSphere 6.0.
3 Restart the VMware vSphere Web Client service.
Configuring the Plug-in for vCenter

Configure the Plug-in for vCenter so that it can connect to Vision Core VM.
Before you begin
Ensure the VMware vSphere Web Client service is running on the VMware vCenter Server host.

Procedure
1 Open a web browser and navigate to the following URL: https://fqdn:9443/vsphere-

client.
Where fqdn is the fully qualified domain name (FQDN), or IP address, of the vCenter Server.
2 Log on to the vSphere Web Client with administrative privileges.
3 Select Administration in the left navigation pane on the Home window.
4 Locate the VCE Vision(TM) Plug-in for vCenter section and then select Settings.
5 Set connection properties as follows:
Property Description
Hostname Case sensitive FQDN of the Vision Core VM.
Port Port number for the Central Authentication Service (CAS) on the
Vision Core VM.
The default is 8443.
The port number value cannot be modified.
Username CAS user for the Vision Core VM.
The username cannot be modified.
Password Password that corresponds to the CAS user.
Confirm Password Confirmation of the password.
6 Select Update Settings and click OK when prompted.
7 Restart the web client services on the VMware vCenter Server virtual machine.
Verifying the Plug-in for vCenter installation

After you complete the steps to install the Plug-in for vCenter, verify that it installed successfully on the
vCenter Server virtual machine.
Procedure
1 Connect to the Vision Core VM.
vpm list
3 Verify that the extension ID displays com.vce.vblock Version:3.5.1.0 in the output.
4 Log on to the VMware vCenter Web Client.
5 Navigate to the settings page and verify that the version of the plug-in is displayed as 3.5.1.0.
6 Select or highlight the top-level VCE System icon.
7 Click Manage > Compliance > Policies.
If you installed the compliance content package, you will see one or more policies.
If the VCE System platform type is changed from the last time the compliance content
was installed, you must reinstall the compliance content.
Troubleshooting the Vision Core installation
Restarting Vision software services with Puppet

Puppet is a service management utility that monitors certain services on the Vision Core VM. Using
Puppet lets you gracefully restart services where multiple dependencies between components in the
Vision Core VM exist.
Before you begin
Procedure
cd /etc/puppet/manifests/
puppet apply vce-puppet-stop.pp
Puppet stops running services in the correct order.
3 To restart services, run the following command:
puppet apply vce-puppet-start.pp

Starting and stopping services on the Vision Core VM
You can manually start and stop services and check the status of services to resolve issues and
troubleshoot the Vision Core VM deployment. You should only start and stop services manually if you
cannot successfully use the Puppet service management utility to resolve issues with services.
Before you begin
Procedure
service service_name argument
service_name
Is one of the following services:
jboss
postgresql-9.1
rabbitmq-server
rsyslog
iptables
tomcat-asset-mgr
vce-fm-all-services
argument
Is one of the following:
stop
start
reload
restart
status
Creating a task to back up the configuration databases (Vision

software 2.5.1+)
Complete the task below to back up the configuration databases.

About this task
Use the Microsoft Windows Task Scheduler to run the batch script and back up the configuration
databases from the Solutions Enabler with SMI-S Provider. When you create the task, you set a time and
frequency so that the task regularly backs up the configuration databases.
Follow the steps below if you are using Vision software 2.5.1+
Enable the TFTP client on the Windows host machine where Solutions Enabler with SMI-S
Provider is installed.
Ensure you have the IP address of the Vision software virtual machine to which you want to
backup the configuration databases.
Save the VMAXConfigBackup.bat script to your local file system.
Procedure
1 Log in to the Windows host machine where Solutions Enabler with SMI-S Provider is installed.
2 Click Start > Administrative Tools > Task Scheduler.
The Task Scheduler window opens.
3 In the left navigation pane, right-click Task Scheduler and then select Create Task from the
drop-down menu.
The Create Task dialog opens.
4 On the General tab, specify a name for the task.

You should specify a name that is meaningful and easy to recognize; for example, VMAX Config
Backup.
5 Optionally, enter an description in the description field.

The description can help you find this task if you need to modify or delete it later; for example,
This task runs a batch script to back up the Solutions Enabler configuration databases.
6 Select the Run whether user is logged on or not option.

Select the Triggers tab.
7 Click New to create a new trigger.

The New Trigger dialog opens.
8 Do the following in the Settings frame:
a Select Daily.
b Set a start time.
c Enter 1 in the Recur every ... days field.
9 Do the following in the Advanced settings frame:
a Select the Repeat task every: check box and enter 12 hours.
b In the For a duration of box, select Indefinitely.

c Select Enabled.
10 Click OK to save the trigger.

The New Trigger dialog closes.
11 Select the Actions tab on the Create Task dialog.
12 Click New to create a new action.

The New Action dialog opens.
13 In the Action drop-down list, select Start a program.
14 In the Program/Script field, browse to the location of VMAXConfigBackup.bat on your local

file system.
15 In the Add arguments field, specify the IP address of the Vision software virtual machine to
which you want to backup the configuration databases.
16 Click OK to save the action.

The New Action dialog closes.
17 Review the settings on the Create Task dialog and then click OK.
The task to back up the configuration databases automatically runs as scheduled every 12 hours.
Backing up VMAX configuration files

Vision software backs up configuration and environment data so that you can restore the Vision Core VM
to a working state, if required. Most VCE System component configuration data is automatically backed
up every 12 hours by default. VMAX storage systems require extra steps for backing up configuration
data.
About this task
Backing up VMAX configuration files is supported on a Vblock System and a VxBlock System only.
Before you begin

Follow the steps in Updating the IP tables on the Vision Core VM (see page 128) before starting this task.
Create a scheduled task to back up the configuration databases from the Solutions Enabler with SMI-S
Provider. Refer to Creating a task to back up the configuration databases (Vision software 2.5.1+) (see
page 142).
After completing this task, follow these steps to ensure that the VMAX configuration is backed up
properly.

Procedure
1 After the VMAXConfigBackup.bat script on the Windows host completes its first scheduled run,
check this location on the Vision Core VM for the backup files: /var/lib/tftpboot/
storage. The following VMAX configuration files should be present after the backup script on
the Windows hosts is run.
symapi_db.bin
accessdb.bin
Instead of waiting for the backup script to run, you can run the script from the Windows
command line to initiate the process.
2 After the Vblock System Configuration Collector completes its scheduled run, check the following
location to make sure the VMAX configuration files are backed up: /opt/vce/backup/
storage.
Instead of waiting for the VCE System Configuration Collector to run, you can run the
collectConfig.sh script from the following directory to initiate the process.
/opt/vce/fm/bin
Manually deploying the Compliance Checker on Vision Core

If the Compliance Checker does not deploy successfully, you cannot install compliance content.
Complete the steps in this procedure to verify the Compliance Checker installation and manually deploy it
if required.
About this task
Manually deploying the Compliance Checker on Vision Core is supported on a Vblock System and a
VxBlock System only.
Procedure
1 Verify the Compliance Checker installation.
a Open a web browser from the VMware vCenter Server host on the VCE System.
b Navigate to the following URL: https://fqdn:8443/compliance/ where fqdn is the fully

qualified domain name (FQDN) of the Vision Core VM.
c Authenticate to the CAS service when prompted.
One of the following occurs:
A message responds to indicate if the Compliance Checker is successfully deployed.
The web browser displays an HTTP 404 error if the Compliance Checker is not successfully
deployed.
2 Connect to the Vision Core VM.

3 Run the following commands to manually deploy the Compliance Checker:
cd /opt/jboss/bin
./jboss-cli.sh --connect
deploy /opt/vce/compliance/webapp/compliance-api.war --force
exit
4 Repeat the steps to verify the Compliance Checker installation.
Manually clearing the work directory associated with the Plug-in for
vCenter
Clear the work directory for the Plug-in for vCenter to resolve any caching issues in list view or if you see
stale data in the right pane of the plug-in.
About this task
Manually clearing the work directory associated with the Plug-in for vCenter is supported on a Vblock
System only.
Procedure
1 Stop VMware vSphere Web Client Service from Windows services.
2 Delete all content in the vSphere web-client work directory.
vSphere 5.X:
drive:\Program Files\VMware\Infrastructure\vSphereWebClient\server\work
\*
vSphere 6.X:
drive:\Program Files\VMware\vCenter Server\WebClient\server\work\*
3 Start VMware vSphere Web Client Service from Windows services.

Installing and configuring the multisystem
management (MSM) VM
About the MSM environment

The MSM VM maps to a separate Vision Core VM. The MSM VM is deployed as a separate Open Virtual
Appliance (OVA).
The Vision Core VMs that will be associated with a deployed MSM VM must be deployed, configured and
discovered prior to MSM deployment.
For details on the hardware requirements for deploying the MSM VM, refer to System requirements (see
page 7).
Downloading the OVA for the MSM VM

After you download the Open Virtual Appliance (OVA) for the MSM VM, you can deploy the virtual
machine.
Before you begin
Procedure
2 Navigate to the location of the MSM VM OVA.
3 Download the MSM VM OVA file to a location where you can access it from the VMware vSphere
Client.
The download process can take several minutes depending on your network
conditions.
Deploying the MSM VM

The MSM VM is packaged as an OVA file. To deploy the virtual machine, use the VMware vSphere Client
to select the OVA file and specify the deployment and network properties.
147 | Installing and configuring the multisystem management (MSM) VM

About this task
Deploying the MSM VM installs the software for MSM.
Important: The steps in this document provide images of the deployment process. These images are for
illustrative purposes only.
Before you begin
Ensure that the Vision Core VM that you want to map to an MSM VM has been deployed,
powered on, and configured before you begin the MSM deployment process.
Download the MSM VM OVA.
Confirm that you can access the vSphere Client running on the VCE System.
Ensure that you have the Logical Configuration Survey (LCS).
You need the following information to deploy the virtual machine:
OVA source Location where you downloaded the vision-msm.3.5.0.0-xxxx-xx.ova.

Alternatively, you can use a URL if the OVA is available on the network.
Name of the virtual machine Display name of the virtual machine.

Host or cluster ESXi host for the virtual machine.

Storage Datastore where the virtual machine saves files.

Installing and configuring the multisystem management (MSM) VM | 148

Network properties Standard network properties, as well as properties needed to associate the
virtual machine with an MSM cluster and data center, and also map the virtual
machine to a Vision software instance.
FQDN
The fully-qualified domain for the routable IP address you are using.
IP address
The IP address for the MSM VM
Gateway server
The default gateway address
Netmask
The subnet mask address
Primary DNS
Primary DNS server
Secondary DNS
Secondary DNS server
Cluster Name (required)
The cluster name for Elasticsearch and Cassandra. The cluster name
should be the same for all virtual machines deployed. This is used to
configure the /etc/elasticsearch/elasticsearch.yml and
the /opt/vce/multivbmgmt/conf/cvm-config.properties
files. For Cassandra, the entry is included in the /opt/cassandra/
conf/cassandra.yaml file.
The cluster name is specific to MSM and may or may not

match the vCenter cluster name.
The value for the cluster name cannot exceed 255 characters
and must not contain any spaces. Only letters, numbers, and
underscores are accepted. The first character of the cluster
name must be a letter or a number. The cluster name cannot
be just an underscore. If the name contains an underscore, it
must also contain other characters as well.
Data Center Name (required)
The name of the data center. The data center name should be the same
for all virtual machines deployed. This name is used in the configuration of
the /opt/vce/multivbmgmt/conf/cvm-config.properties
file. The data center name is also included in /opt/cassandra/
conf/cassandra-rackdc.properties.
The data center name is specific to MSM and may or may

not match the vCenter data center name.
The value for the data center name cannot exceed 255
characters and must not contain any spaces. Only letters,
numbers, and underscores are accepted. The first character
of the data center name must be a letter or a number. The
data center name cannot be just an underscore. If the name

contains an underscore, it must also contain other characters

as well.
NTP Servers (required)
This is a comma-separated list of Network Time Protocol (NTP) server IP
addresses. At least one NTP server IP address is required.
Optional Initial System Library IP(s)
You can add a System Library instance to an existing MSM

VM after deployment. However, if you do this, be aware that
the OVF properties of the virtual machine will not contain the
new System Library instance added after the deployment.
If you are redeploying an MSM VM, specify an NTP server IP address when configuring the
server.
Procedure
4 Select the source location of the vision-msm.3.5.0.0-xxxx-xx.ova file.
b Locate and select the vision-msm.3.5.0.0-xxxx-xx.ova file and click Open.

c Verify the file name or URL location and click Next.
5 Verify the template details for the virtual machine.
a Confirm the version of the virtual machine.

b Verify that the vendor and publisher display as VCE Company, LLC and click Next.
This field indicates if the OVA was correctly signed using the SSL certificate.
The vSphere Client attempts to verify the SSL certificate with the issuing authority,
starfieldtech.com. If it can successfully verify the SSL certificate, the vSphere Client displays
a green check mark in the Publisher field.
If it cannot contact the issuing authority, the vSphere Client does not verify the SSL
certificate. If you are installing the software in a closed network and cannot access the
issuing authority directly from a browser, you should proceed with the deployment.
If you have network access, but cannot successfully validate the SSL certificate, it indicates a
security issue with the vision-msm.3.5.0.0-xxxx-xx.ova. Contact VCE Support.
6 Specify the name and location of the virtual machine.
a Type the display name of the machine in the Name field. Refer to the LCS for the display
name.

7 Select the ESXi host or cluster for the virtual machine and click Next.


10 Select Thin Provision as the disk format and click Next.

11 Select the main management VLAN for the network mapping and click Next.

12 Specify the network properties and click Next.

Only a single System Library IP address is supported in this release.
Results
The vSphere Client displays the progress of the virtual machine deployment, as in the following image:

What to do next
When the virtual machine deployment finishes, open the Recent Tasks pane to verify the deployment of
the virtual machine.
Depending on how your network is configured, you may need to edit the hosts file on the virtual
machine. The hosts file may need an entry for the MSM VM and Vision Core VM you intend to
access.
Monitoring the MSM VM setup

Ensure the MSM VM is running and deployed successfully.
Before you begin
Deploy the MSM virtual machine and take a snapshot of the virtual machine before powering it on for the
first time. If there are any configuration issues during first boot, you can then revert the virtual machine to
a clean, initial state without having to redeploy the OVA.
Procedure
1 Power on the virtual machine and open the vSphere console.

2 Monitor the first boot set up.
After powering on the virtual machine, the guest operating system starts.
After the guest operating system starts, the virtual machine goes through the first boot set up.
installs and configures the application, and starts the required services.
The first boot process also configures the following ports as open for external communication:
Port number Description
22 SSH remote log on port
80 Apache HTTPd port to redirect to HTTPS
443 Apache HTTPd port for CAS authentication
8443 Apache HTTPd port for SSL
4369 RabbitMQ port for Erlang Port Mapper Daemon

(epmd)
5672 RabbitMQ port used to send asynchronous

messages
25672 RabbitMQ port for distributed node protocol
7000 Cassandra port for inter-node communication
7001 Cassandra port for SSL inter-node communication
7199 Cassandra port for JMX monitoring
9042 Cassandra port for native protocol client access
9160 Cassandra port for thrift client access
All other ports are denied access by default.

3 If prompted, specify the SSH user name and password for each Vision Core VM configured for
the MSM cluster.
You will only be prompted for the Vision Core credentials on MSM first boot if the Optional Initial
System Library IP(s) OVF property was configured with a valid IP address. Otherwise, you will
not be prompted for credentials. To add a System Library host after deployment, you can execute
the addSlibHost.sh script, as described in Associating a Vision Core VM with an existing MSM
VM (see page 162).
The root credentials are needed to access the vblock.xml file on startup. The default credentials
are:
Username: root
The console relies on the US keyboard. The @ symbol is shift+2.
If the credentials are valid, the vblock.xml and other files will be transferred from the Vision Core
VM to the MSM VM. At this point, the vblock.xml, as well as the SSH and CAS credentials for the
Vision software environment, will be automatically imported into Credential Manager.
When the first boot set up is complete, the vSphere console displays a log on prompt such as the
following:
Connecting to the MSM VM

After you deploy the virtual machine, you must connect to it in order to verify the installation and complete
additional tasks to configure the software. When you connect to the virtual machine, you can interact with
the guest operating system and software components.
Before you begin
Deploy the virtual machine.

Procedure
1 Establish a connection to the virtual machine with either of the following:
SSH client
You must have the IP address of the virtual machine to connect with an SSH client.
2 Enter the username and password to connect to the MSM VM.
Username: root
Associating a Vision Core VM with an existing MSM VM

You can associate a Vision Core VM (System Library host) with an existing MSM VM after the initial MSM
deployment. You can also add a Vision Core VM after a cluster of MSM VMs has been formed.
About this task
The MSM VM provides a wrapper script called addSlibHost.sh that allows you to add the IP address
of a Vision Core VM to an MSM VM. In a single system environment where one Vision Core VM is
mapped to a single MSM VM, you should only execute the addSlibHost.sh script if either the Optional
Initial System Library IP(s) OVF property is not configured, or if the property is configured, and there
were failures adding the Vision Core VM on MSM first boot.
To ensure your environment can successfully add a Vision Core VM to an existing MSM VM,
you can run a pre-check option of the script by running the following command:
/opt/vce/multivbmgmt/install/addSlibHost.sh -p IP_address
The -p option runs the pre-check logic but does not add the Vision Core VM to the MSM VM.
When associating a Vision Core VM to an MSM VM, no other operations should be performed on that
Vision Core VM from any other MSM VMs, until the association is complete.
The script verifies that the IP address has a valid format. If the IP address is valid, the script imports the
vblock.xml file and then imports the credentials.
If your Vision Core VM is already associated with your MSM VM, ensure the Vision Core VM is configured
to use NTP. To do that, you must set the NTP server on the Vision Core VM. To configure the Vision Core
VM to use NTP, run the following command:
/opt/vce/multivbmgmt/install/addSlibHost.sh -n IP_address
where the IP address is the server for which you want to set the time. The -n option sets up the NTP on
the Vision Core VM, it does not add it to the MSM VM.

Before you begin
Before you associate a Vision Core VM with an MSM VM, you must take a snapshot of each MSM VM
within the cluster. In addition, you must ensure that the firstboot script has completed successfully on the
MSM VM where you will be adding the Vision Core VM, and the subsequentboot script must not still be in
progress. To access the logs, navigate to /opt/vmware/var/log/firstboot and /opt/
vmware/var/log/subsequentboot.
Before you associate a Vision Core VM with an MSM VM, ensure that the following conditions are true:
The version of the System Library is the same version as the MSM VM.
The number of VCE Systems to associate with an MSM VM cannot exceed two.
The serial number of the Vblock System can be added once. Each serial number must be unique.
You can only have one Vblock System 7xx with VMAX.
The addSlibHost script performs checks on the previous criteria when you run the script. If your
environment does not meet these criteria, the addSlibHost script provides you with the reason
it failed and does not allow the Vision Core VM to be added.
To ensure discovery is complete, open a web browser and navigate to the following URL: https://
FQDN:8443/fm/vblocks, where FQDN is the fully qualified domain name of the Vision Core VM.
Procedure
Run the following command to add the Vision Core VM to an existing MSM VM:
/opt/vce/multivbmgmt/install/addSlibHost.sh IP_address
You can check the /opt/vce/logs/multivbmgmt/addSlibHost.log file if you encounter any

problems adding hosts.
It may take up to 30 minutes before the data is available.
Starting the Vision dashboard

Before you begin
You need the following information to access the dashboard:
Fully-qualified domain name (FQDN) of the multisystem management (MSM) VM.
A username and password with access to the Vision dashboard.
One of the following supported browsers:
Google Chrome, Version 19 or later
Microsoft Internet Explorer, Version 11
The dashboard supports a minimum screen resolution of 1280 x 1024.

Procedure
1 Use a web browser to navigate to the MSM VM.
The URL format is https://FQDN, where FQDN is the fully qualified domain name of the MSM
VM.
The MSM VM has to be able to ping the FQDN of the Vision Core VM. If it cannot, a
host file entry for the Vision Core VM must exist on the MSM VM.
2 Log on with your username and password.
The default credentials for the dashboard are:
Username: admin
Password: D@ngerous1
This password should be changed to protect the system from unauthorized access.
If this is the first time you have opened the dashboard, there is a quick tour of some of the new
features for Version 3.5.1.
3 When you finish the tour, click End Tour.
Results
The dashboard initially displays the list of VCE Systems.
Enabling software modules

After deployment, the Vision RCM Compliance Module must be enabled. The Vision Security Compliance
Module is enabled if it has been purchased by the customer or a valid license exists.
In Vision software Version 3.5.1, the Vision Security Compliance Module module is supported on a
Vblock System and a VxBlock System only.
Vision software provides the Software Module Manager service as part of the MSM virtual machine. This
service allows you to enable these modules using the Vision dashboard.
In the Vision dashboard and the Vision shell, the Vision Security Compliance Module is referred to as the
Security Hardening module and the Vision RCM Compliance Module is referred to as the RCM
Management module.
Enabling the RCM Management module

The RCM Management module is mandatory and required in order to run an RCM compliance scan.
About this task
By default, the RCM Management module is disabled after the multisystem management (MSM) virtual
machine is deployed.

Before you begin
Ensure the MSM VM is deployed and configured.
Procedure
1 Starting the Vision dashboard (see page 163).
2
From the toolbar, click the menu icon ( ) and navigate to Manage > Software Modules.
3 Click the Enabled checkbox to enable the RCM Management module.
What to do next
Verify that the RCM Management module is successfully enabled by completing the following steps:
1 Complete the compliance management option in the dashboard, which involves:
Installing compliance content
Setting the target profile
Starting a compliance scan
Related information
Enabling the Security Hardening module

If you have the Security Hardening module and a valid license exists, the Security Hardening module
must be enabled after the multisystem management (MSM) virtual machine is deployed.
About this task
In Vision software Version 3.5.1, the Security Hardening module is supported on a Vblock System and a
VxBlock System only.
Before you begin
Ensure the MSM VM is deployed and configured.
Procedure
1 Starting the Vision dashboard (see page 163).
2
From the toolbar, select the menu icon ( ) and navigate to Manage > Software Modules.
3 Click the Enabled checkbox to enable the Security Hardening module.

What to do next
Verify that the Security Hardening module is successfully enabled by completing the following steps:
1 Install the Dell EMC Vision shell Security Remediation Extension Pack.
2 Complete the compliance management option in the dashboard, which involves:
Installing compliance content
Setting the target profile
Starting a compliance scan
Related information
Installing Dell EMC Vision shell Security Remediation Extension Pack (see page 167)
Uploading compliance content

Use the dashboard to upload and install new compliance content. You can get new compliance content
from the VCE Download Center.
Before you begin
To install new compliance content, it must meet the following requirements:
All of the XML content must be in a compressed ZIP file.
The ZIP file must contain at least one valid XCCDF file and one valid OVAL file.
Procedure
Click the menu icon ( ) in the toolbar and select Manage > Compliance Policies.
Results
The Manage Compliance Policies dialog box appears. The prompts step you through the process of
uploading the compliance content ZIP file, setting the target profile, and running compliance scans.
What to do next
After uploading any new compliance content, you need to re-run all compliance scans.
Related information
Downloading compliance content for the Vision Core VM (see page 9)
Enabling the RCM Management module (see page 164)

Installing Dell EMC Vision shell Security Remediation
Extension Pack
The shell Security Remediation Extension Pack, which is optional, is installed on the MSM VM and
enables remediation of any non-compliant items identified by the baseline security settings compliance
scan.
About this task
In Vision software Version 3.5.1, installing Dell EMC Vision shell Security Remediation Extension Pack is
supported on a Vblock System and a VxBlock System only.
Procedure
1 Download the following shell Security Remediation Extension Pack RPM file to any location on
the MSM VM:
vision-shell-security-extension-pack-x.x.x.x-build_number.x86_64.rpm
rpm -ivh <file_name>
Where:
rpm is the command to run RPM Package Manager.
-ivh is the option to install the RPM file.
<file_name> is the name of the RPM file.
The command installs the shell Security Remediation Extension Pack content on the MSM VM.
What to do next
1 To verify that the shell Security Remediation Extension Pack is installed, run the following
command from any directory to start Vision shell:
vshell
2 Select Enter when the following prompt displays:
MSM Hostname (Press Enter for localhost):
3 Log on to Vision shell using the following credentials:
Username: csadmin
4 Wait for the following prompt to display:

Username:csadmin
Password:
Initializing......[Done]
Type "help" for an introduction to VCE Vision shell
or type "show" to see a list of avaialble commands
Vision>
5 Type show security and ensure the shell Security Remediation Extension Pack content
displays as shown below.
This is an example of some of the extensions that display. It does not include all the
available extensions.
Vision>show security
%cdp:Retreives and sets the CiscoDiscovery Protocol (CDP) setting for components
%cimxml:Retreives and sets the CIM-XML setting for the components
%http:Retreives and sets the HTTP server setting for the components
%https:Retreives and sets the HTTPS server setting for the components
%ip_source_route:Retreives and sets the IP source routing setting for the components
%lldp:Retreives and sets the Link Layer Discovery Protocol(LLDP)setting for components
%login_banner:Retreives and sets the login banner for components
%ntp:Retreives and sets the NTP servers for the components
%pw_strength_check:Retreives and sets the password strength check setting for the
components
%remote_syslog_server:Retreives and sets the remote system log servers for the
components
%set_vision_as_remote_syslog_server:Adds VCE Vision software to the set of remote

system log servers
6 Type quit to exit the shell.
Updating a compliance profile on the MSM node

Depending on the configuration for any system, you might need to make changes to the rules and checks
in a profile to obtain a more accurate compliance score. Any changes you make to a profile are saved to
a custom copy of that profile. Make sure that any subsequent changes are saved in the same custom
copy to avoid multiple custom profiles with different updates.
Before you begin
Log on to the Vision dashboard to perform these steps.
Procedure
1
From the dashboard toolbar, click the menu icon ( ) and select Manage > Compliance
Profiles.
2 Follow the prompts to customize your profile.

Installing and configuring the multisystem
prepositioning (MSP) VM for the RCM content
prepositioning feature
You must install and configure the multisystem prepositioning (MSP) VM to use the RCM content
prepositioning feature.
Important: Only one MSP VM must be deployed and configured within a cluster. The MSP VM must be
associated with the MSM VMs in its local data center for that cluster. If other MSP VMs have
been deployed and configured, you must power down these VMs.
Downloading the OVA file for the multisystem prepositioning (MSP)

virtual machine
The first step in the installation process is to download the Open Virtual Appliance (OVA) for the MSP
VM. After you download the OVA, you can deploy the virtual machine.
Before you begin
Procedure
2 Navigate to the location of the MSP VM OVA file.
3 Download the OVA file to a location where you can access it from the VMware vSphere Client.
The download process can take several minutes depending on your network
conditions.
Deploying the MSP OVA

Complete the steps in this task to deploy the multisystem prepositioning (MSP) VM.
About this task

The MSP VM is packaged as an OVA file. To deploy the VM, you use the VMware vSphere Client to
select the OVA file and then specify deployment and network properties.
Important: Some of the steps in this procedure include images of the deployment process. These images
are for illustrative purposes only.
prepositioning feature | 170
Before you begin
Ensure that the multisystem management (MSM) virtual machine that you want to map to has
been deployed, powered on and configured prior to the MSP VM deployment.
Download the MSP VM OVA file.
Confirm that you can access the vSphere Client running on the VCE System where you are
deploying the OVA.
Ensure that you have the Logical Configuration Survey (LCS) for virtual machine settings as
appropriate.
You need the following information to deploy the virtual machine:
OVA source Location where you downloaded the MSP VM OVA file. Alternatively, you can
use a URL if the OVA is available on the network.
Name of the virtual machine Display name of the virtual machine.

Available in the LCS, for example, Vision multisystem
prepositioning.
Host or cluster ESX or ESXi host for the virtual machine.

Storage Location where the virtual machine saves files.

171 | Installing and configuring the multisystem prepositioning (MSP) VM for the RCM content
Network properties Standard network properties, as well as properties needed to associate the
virtual machine with a MSM cluster and data center.
FQDN
The fully-qualified domain for the routable IP address you are using.
IP address
The IP address for the MSP VM.
Gateway
The default gateway address
Netmask
The subnet mask address
Primary DNS
Primary DNS server
Secondary DNS
Secondary DNS server
MSM cluster nodes
This is a comma separated list of FQDNs for each MSM node in the same
data center. Do not use the IP address.
NTP Servers
This is a comma-separated list of Network Time Protocol (NTP) server IP
addresses. The NTP service will synchronize the virtual machine's time
with the configured NTP server(s) on first boot. If this synchronization fails,
the MSP VM will use VMware Tools time synchronization feature, thus
ensuring the MSP VM time is synchronized with the time of the ESXi host
it runs on.
Procedure
4 Select the source location of the OVA file.
b Locate and select the OVA file and click Open.
c Verify the file name or URL location and click Next.
5 Verify the template details for the virtual machine.
a Confirm the version of the virtual machine.
b Verify that the vendor and publisher appear as VCE Company, LLC and click Next.
The Publisher field indicates if the OVA was correctly signed using the SSL certificate.
The vSphere Client attempts to verify the SSL certificate with the issuing authority,
starfieldtech.com. If it can successfully verify the SSL certificate, the vSphere Client displays
a green check mark in the Publisher field.
If it cannot contact the issuing authority, the vSphere Client does not verify the SSL
certificate. If you are installing the software in a closed network and cannot access the
issuing authority directly from a browser, proceed with the deployment.
If you have network access, but cannot successfully validate the SSL certificate, it indicates a
security issue with the OVA. Contact VCE Support.
6 Specify the name and location of the virtual machine.
a Type the display name of the machine in the Name field. Refer to the LCS for the display
name.
7 Select the ESX or ESXi host or cluster for the virtual machine and click Next.
10 Select Thin Provision as the disk format and click Next.
11 Select the main management VLAN from the LCS and click Next.
12 Specify network properties from the LCS and click Next.
For MSM cluster nodes, enter the FQDN for each MSM node. Do not enter the IP address.
Results
The vSphere Client displays the progress of the virtual machine deployment, as in the following image:
What to do next
If the CAS password has been updated on the MSM VM you must update the CAS password on the
multisystem prepositioning (MSP) VM to match the CAS password on the MSM VM.
When the virtual machine deployment finishes, open the Recent Tasks pane to verify the
deployment of the virtual machine.
Monitoring the MSP VM setup

Complete these steps to monitor the MSP VM set up to ensure it is running and deployed successfully.
Before you begin
Deploy the MSP VM and take a snapshot of the virtual machine before powering it on for the first time. If
there are any configuration issues during first boot, you can then revert the virtual machine to a clean,
initial state without having to redeploy the OVA.
Procedure
1 Power on the VM, open the vSphere Client console, and monitor the first boot set up.
The guest operating system starts.
After the guest operating system starts, the virtual machine goes through the first boot set up.
installs and configures the application, and starts the required services.
The following image is an example of the first boot set up in the vSphere Client console:
2 When the first boot set up is complete, the vSphere Client displays a log on prompt such as the
following:
Specify the username and password for the MSP VM. The default credentials are:
Username: root
Connecting to the MSP VM

After you deploy the MSP VM, you must connect to it in order to verify the installation. When you connect
to the virtual machine, you can interact with the guest operating system and software components.
Before you begin
Deploy the virtual machine.
Procedure
1 Establish a connection to the virtual machine with either of the following:
SSH client
You must have the IP address of the virtual machine to connect with an SSH client.
2 Enter the username and password to connect to the MSP VM.
Username: root
Checking network properties for the MSP VM

Complete these steps to verify that the MSP VM network properties are correct.
Procedure
1 Connecting to the MSP VM (see page 183). If you can successfully start an SSH session, it
indicates that the IP address of the MSP VM is valid.
2 Verify the IP addresses of the configured name servers.
cat /etc/resolv.conf
The IP addresses of the primary and secondary name servers display.
b Check that the IP addresses for the name servers match the Logical Configuration Survey.
3 Ping the default gateway server from the MSP VM.
ping IP_address -c4
Where IP_address is the IP address of the default gateway server and -c4 specifies that 4
packets will be sent.
The ping sends a request to the default gateway server, as in the following example:
PING IP_address (IP_address) 56(84) bytes of data.

--- 10.3.18.230 ping statistics ---

4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 0.219/0.227/0.239/0.007 ms
Verifying that the MSP VM deployed successfully

To ensure that the MSP VM deployed successfully, you must verify that the first boot script completed
successfully and ensure the system services are running.
Before you begin
Connect to the MSP VM virtual machine.
Procedure
1 Check that the first boot script completed successfully by running the following commands:
cd /opt/vmware/var/log/
tail firstboot
The output of the firstboot script should display as follows:
Notice: Compiled catalog for techpubdeploy06.iaas.lab in environment production in

0.34 seconds
Notice: /Stage[main]/Main/Service[iptables]/ensure: ensure changed 'stopped' to
'running'
Notice: /Stage[main]/Main/Service[rsyslog]/ensure: ensure changed 'stopped' to
'running'
Notice: /Stage[main]/Main/Service[postgresql-9.1]/ensure: ensure changed 'stopped' to
'running'
Notice: /Stage[main]/Main/Service[vision-contentshare]/ensure: ensure changed
'stopped' to 'running'
Notice: /Stage[main]/Main/Service[vision-contentsource]/ensure: ensure changed
Notice: /Stage[main]/Main/Service[vision-downloader]/ensure: ensure changed 'stopped'
to 'running'
Notice: /Stage[main]/Main/Service[vision-assetmanager]/ensure: ensure changed
Notice: Finished catalog run in 83.52 seconds
2015-04-03 08:32:11: Done!
If Done! displays as the last line of the output, the firstboot script completed successfully.
If Failed! displays as the last line of the output, the firstboot script did not complete
successfully. This can occur if the service applications did not deploy successfully. To resolve
this issue, run shutdown -h now and then restart the MSP VM from the vSphere Client.
2 Verify that the component services are running by running the following commands:
service httpd status
service vision-assetmanager status
service vision-contentshare status
service vision-contentsource status
service vision-downloader status
The status for each service should display as running or provide details about running
processes.
Completing the Vision software installation
Resetting the end user license agreement (EULA)

You must reset the EULA to ensure that the customer can accept it when the VCE System is delivered.
When you reset the EULA on the Vision Core VM, the discovery and health polling of the VCE System
stops.
About this task
This section is not applicable if you are installing on an existing VCE System. This procedure is for Dell
EMC personnel only.
Before you begin
Ensure that you have successfully completed all tasks to install VCE System.
Confirm that you do not need to perform any additional tasks that require discovery or health
polling of the VCE System.
Procedure
1 Start an SSH session to the Vision Core VM and log on with the following credentials:
Username: root
resetEulaAcceptance
A message such as the following displays:
resetEulaAcceptance
Resetting EULA: [time_stamp]
Are you sure you want to reset the End User License Agreement:[yes/no]> yes
[time_stamp] EULA has been reset.
3 Enter yes when prompted to reset the EULA. The following message displays:
time_stamp EULA has been reset.
Completing the Vision software installation | 186

Configuring ESRS for Vision software
Vision software can connect to Secure Remote Services (ESRS) and automatically send system
inventory and RCM fitness information through the ESRS connection to the Dell EMC Data Lake.
Services and Support can use the collected data for analysis and remote troubleshooting.
Before you begin
Make sure that the ESRS virtual appliance is installed. If you need to do this, refer to the EMC Secure
Remote Services Installation and Operations Guide. You can find this guide at support.emc.com/
products/37716_EMC-Secure-Remote-Services-Virtual-Edition/Documentation.
The minimum version installed of Secure Remote Services Virtual Edition must be at least ESRS VE
3.14.
Retrieving the software ID from the Licensing system

Use this procedure to retrieve the software ID (SWID) from the Dell EMC Licensing system. You need this
software ID when configuring Secure Remote Services (ESRS) for Vision software.
Before you begin
Make sure you have received an email from Dell EMC with a license activation code (LAC). You also
have the option of entering the sales order number in the procedure below.
If you need more information on the software activation process, refer to the product documentation
located on Dell EMC Software Licensing Central.
Procedure
1 Connect to Dell EMC Software Licensing Central.
2 Click Activate My Software.
3 In the License Authorization Code field, type (or copy and paste) the LAC code. You can
alternately enter the sales order number in the Sales Order # field. Click Search. The STEP 1:
SELECT AVAILABLE PRODUCTS TO ACTIVATE page displays products available for
activation.
4 Select the product to activate and click Start the Activation Process. The STEP 2: CONFIRM
COMPANY & SITE page appears.
5 Confirm the company registered for the activation. Click Select a Machine. The STEP 3:
SELECT A MACHINE page appears.
6 In the Add a New Machine field, enter the a unique identifier for the machine name. It is
recommended that this be the VCE System serial number. Click Save Machine & Continue to
Next Step. The STEP 4: ENTER PRODUCT QUANTITIES & MACHINE DETAILS page
appears.
7 In the Quantity to Activate field, enter the quantity of entitlements to activate for the machine.
Click Next: Review. The STEP 5: REVIEW YOUR SELECTIONS page appears.
187 | Configuring ESRS for Vision software

8 Review the information. Click Activate to generate the software identifier. The STEP 6:
ACTIVATION COMPLETE page appears.
9 Obtain a copy of the software identifier needed to configure ESRS for Vision software by
performing either of the following steps:
Copy to the clipboard the SOFTWARE ID displayed after Your new key files are listed
below:
Email the information:
Click View Certificate.
On the next page, click Email Certificate.
Under Choose what will be emailed, select Email and license key files.
In the Email Addresses box, provide at least one email address.
Click Send Email.
Open the email and copy the software identifier to the clipboard.
What to do next
Use the software identifier when configuring ESRS for Vision software.
Registering Vision software with an ESRS gateway

Use the Vision shell to register Vision software with Secure Remote Services (ESRS).
Before you begin
To configure ESRS for Vision software, you need to provide a software identifier (SWID). Refer to
Retrieving the software ID from the Licensing system (see page 187) for information on how to obtain the
SWID.
Perform ESRS for Vision software configuration only at a customer site.
Procedure
1 Establish an SSH connection to the MSM VM and log on. The default credentials are:
Username: root
Note that this password should be changed to protect the system from unauthorized access.
2 Execute the following script:
/opt/vce/shell/bin/ESRSScript/esrs_setup.sh
Configuring ESRS for Vision software | 188

3 The following message displays:
Are you a Dell EMC employee using a RSA token (FOB)? (yes/[no]):
If yes, go to Step 4.
If no, go to Step 5.
4 Type yes at the prompt. A message similar to the following appears:
No software identifier (SWID) found for host 10.1.174.174

Do you want to enter a software identifier (SWID) for host 10.1.174.174 (yes/[no]):
a Type yes. A message similar to the following appears:
Please enter the software identifier (SWID) for host 10.1.174.174:
b Type the software identifier (SWID). A message similar to the following appears:
Please enter your ESRS gateway hostname or IP address:
c Type the ESRS gateway IP address. The following message appears:
Please enter your NTID:
d Type your Dell EMC network/Windows ID. The following message appears:
Please wait for next token and enter your RSA PIN + Token:
e Type your RSA pin and token. It takes a moment to authenticate, then a message similar to
the following appears:
ESRS configuration for 10.1.174.174 for the ESRS gateway 10.1.174.148 was
successful.
ESRS gateway configuration completed, exiting setup script.
f Go to Step 6.
5 Type no at the prompt. A message similar to the following appears:
ESRS gateway configuration not found in VCE Vision System

Do you want to create a new ESRS gateway configuration (yes/[no]):
a Type yes to create a new ESRS gateway configuration.

b Type the ESRS gateway hostname or IP address. Then provide your username and
password for support.emc.com at the prompt for each.
Messages similar to the following appear:
ESRS gateway configuration has been created for 10.1.174.148

No software identifier (SWID) found for host 10.1.174.174
Do you want to enter a software identifier (SWID) for host 10.1.174.174 (yes/[no]):
c Type yes to enter the software identifier (SWID).
d At the SWID prompt, type the unique software identifier (SWID) from the CLP file.
A message similar to the following appears:
ESRS configuration for 10.1.174.174 for the ESRS gateway 10.1.174.148 was
successful.
ESRS gateway configuration completed, exiting setup script
6 Verify the registration status by performing the following steps.
a Run the following command: vshell
The Vision shell initializes with the following messages:
VCE Vision shell 3.5.0.0
Copyright 2013-2016 VCE Company, LLC. All rights reserved.

VCE, VCE Vision, VCE Vscale, Vblock, VxBlock,VxRail and the VCE logo are
registered trademarks of VCE Company LLC.
All other trademarks used herein are the property of their respective owners.
Note that you can skip the login prompts by starting shell with the following option:
vshell -l /opt/vce/shell/conf/ipython.conf
b Enter the MSM hostname to which you want to connect or press Enter for the localhost.
c When prompted, enter your username and password. The default administrative credentials
for Vision shell are:
Username: csadmin

d Wait for the deviceState to be set to Managed and the deviceStatus to be set to Online.
Verify the registration status is similar to the following:
Vision>%esrs_register status
{'deviceState': 'Managed',
'deviceStatus': 'Online',
'ipAddress': '10.3.16.36',
'model': 'VCEVISION',
'responseCode': 0,
'serialNumber': 'VCEVISIONTCOE03',
'validationCode': '0',
'validationError': 'No errors in general.'}
Adding a software identifier for an MSM VM

Use the Vision shell to add a software ID for an MSM VM to an already configured ESRS gateway. You
are prompted to enter the ESRS gateway to use from a known list of ESRS gateway IP addresses.
Before you begin
If you are adding a software ID to an ESRS gateway that has not been configured, refer to Registering
Vision software with an ESRS gateway (see page 188) for what to do.
Perform ESRS for Vision software configuration only at a customer site.
Procedure
1 Establish an SSH connection to the MSM VM and log on. The default credentials are:
Username: root
Note that this password should be changed to protect the system from unauthorized access.
2 Run the following command: vshell
The Vision shell initializes with the following messages:
VCE Vision shell 3.5.0.0
Copyright 2013-2016 VCE Company, LLC. All rights reserved.

VCE, VCE Vision, VCE Vscale, Vblock, VxBlock,VxRail and the VCE logo are registered
trademarks of VCE Company LLC.
All other trademarks used herein are the property of their respective owners.
Note that you can skip the login prompts by starting shell with the following option:
vshell -l /opt/vce/shell/conf/ipython.conf
3 Enter the MSM hostname to which you want to connect or press Enter for the localhost.

4 When prompted, enter your username and password. The default administrative credentials for
Vision shell are:
Username: csadmin
5 Type the following command: esrs_register add swid=software identifier
Any existing ESRS gateways display.
6 Type the number (0, 1, 2...) of the ESRS gateway to which you want to register the VM. A
message displays that the product is successfully registered.

Configuration file format and examples
Configuration file (.cfg) format

Use the configuration file (.cfg) entry format and conventions to edit the configuration settings of a
component.
The following conventions apply to the configuration file (.cfg) format:
File uses standard dotted notation.
Containments are separated using dots:
a.b.c=123
Containments can be indexed:
a.b.c is equivalent to a.b[1].c
a.b.c is not equivalent to a.b[2].c
Component Configuration file entry format Rules Configuration file entry

type example
VxBlock The first three digits of $

System type=${vxblockType} {vblockType} determine type=320w5500
the VxBlock System type.
VxBlock ${componentTag}
System componentTag=$ should be a meaningful componentTag=VB-320
{componentTag} value.
VxBlock ${serialNumber}
System serialNumber=$ should be a meaningful serialNumber=VB320-
{serialNumber} value. 975-318-642
VxBlock ${product} dictate the

System product=${product} VxBlock System product. product=Vxblock
The mandatory value is
Vxblock
VxBlock ${system} dictate the

System system=${system} VxBlock System product. system=VXBLOCK
The mandatory value is:
VXBLOCK
VxRack VxRack System with FLEX

System type=${vxrackType} is currently the only type=VxRack1000FLEX
supported VxRack System
type.
193 | Configuration file format and examples

type example
VxRack ${componentTag} can

System componentTag=$ be any meaningful value. componentTag=VX1000
{componentTag} FLEX
VxRack ${serialNumber} can

System serialNumber=$ be any meaningful value. serialNumber=VX1000
{serialNumber} FLEX-77
7-888-999
VxRack ${product} dictate the

System product=${product} VxRack System product. product=VxRack
Must be: VxRack
VxRack ${system} dictate the

System system=${system} VxRack System product. system=VXRACK
Must be: VXRACK
VxRack ${serialNumber} can

Controller amp.serialNumber=$ be any meaningful value amp.serialNumber=AM
{serialNumber} P-KYL-123
VxRack ${type} can be any

Controller amp.type=${type} meaningful value amp.type=AMP-KYL
VxRack ${componentTag}
Controller amp.componentTag=$ should be a meaningful amp.componentTag=Ma
{componentTag} value. nagement
VxRack ${type} must be:

Controller operatingsystems.operatin REDHAT operatingsystems.op
gsystem.type=${type} eratingsystem.type=
REDHAT
VxRack ${componentTag} can

Controller operatingsystems.operatin be any meaningful value operatingsystems.op
gsystem.componentTag=$ eratingsystem.compo
{componentTag} nentTag=RedHat-1
VxRack ${ipAddress} can be

Controller operatingsystems.operatin any meaningful value operatingsystems.op
gsystem.address=$ eratingsystem.addre
{ipAddress} ss=XXX.XXX.XXX.XXX-
XXX.XXX.XXX.XXX
Configuration file format and examples | 194

type example
VxRack ${username} is the SSH

Controller operatingsystems.operatin username amp.compute.server[
gsystem.credentials.usern 1].credentials.user
ame=${username} name=root
VxRack ${method} must be: SSH

Controller operatingsystems.operatin amp.compute.server[
gsystem.credentials.metho 1].credentials.meth
d=${method} od=SSH
VxRack ${password} is the SSH

Controller operatingsystems.operatin password (optional if using amp.compute.server[
gsystem.credentials.passw SSH public key 1].credentials.pass
ord=${password} authentication) word=password
VxRack ${iprange} should be a

Controller componentcredentials.comp range of dotted IP componentcredential
onentcredential[1].iprang addresses. s.componentcredenti
e=${iprange} al[1].iprange=XXX.X
XX.XXX.XXX-
XXX.XXX.XXX.XXX
VxRack ${community} should be

Controller componentcredentials.comp the SNMP community string. componentcredential
onentcredential[1].creden s.componentcredenti
tials.community=$ al[1].credentials.c
{community} ommunity=snmp4lab
VxRack ${username}is the

Controller componentcredentials.comp username componentcredential
tials.username=$ al[1].credentials.u
{username} sername=root
VxRack ${method} must be one

Controller componentcredentials.comp of the following: IPMIV2, componentcredential
onentcredential[1]. SNMPV2C, WEBSERVICE, s.componentcredenti
credentials.method=$ SSH al[1].credentials.m
{method} ethod=SSH
VxRack ${password} is the

Controller componentcredentials.comp password componentcredential
tials.password=$ al[1].credentials.p
{password} assword=password

type example
vCenter ${componentTag} can

amp.vcenters.vcenter[?].c be any meaningful value. amp.vcenters.vcente
omponentTag=$ r[1].componentTag=V
{componentTag center1
shared vCenter with MSM,
be sure to include the
shared vCenter server
information in the
node.
Do not define a shared
vCenter as a part of the
AMP if the shared vCenter
resides on a Shared
Management Platform
(SMP), rather than on a
VCE System. When a
shared vCenter resides on
an SMP, that SMP will not
be discovered. However, the
fact that the vCenter is
shared by multiple VCE
Systems will be apparent in
the results returned for a
find VIManager query.
VCenter ${name} should be

vcenters.vcenter[?].name= vCenter1, vCenter2, ... vcenters.vcenter.na
${name} vCenterN, etc. me=Vcenter1
information in the
node.
When a shared vCenter
resides on an SMP, that
SMP will not be discovered.
However, the fact that the
vCenter is shared by
multiple VCE Systems will
be apparent in the results
returned for a find
VIManager query.

type example
vCenter ${ipAddress} should be

vcenters.vcenter[?].url=$ a dotted IP address to the vcenters.vcenter.ur
{ipAddress} vCenter server. l=10.1.139.39
information in the
node.
VCenter ${username} is the

vcenters.vcenter[?].usern vCenter server SDK vcenters.vcenter.us
ame=${username} username. ername=vb300swqa
\administrator
information in the
node.
VCenter ${password} is the

vcenters.vcenter[?].passw vCenter server SDK vcenters.vcenter.pa
ord=${password} password. ssword=password
information in the
node.
Application ${appHostName} is the

host managedSoftware.applicati Application host name. managedSoftware.app
onHost[?].name=$ licationHost[1].nam
{appHostName} e=app-host-1
Application ${ipAddress} should be

host managedSoftware.applicati a dotted IP address. managedSoftware.app
onHost[?].address=$ licationHost[1].add
{ipAddress} ress=10.1.139.42

type example
Application ${userName} is the

host managedSoftware.applicati username. managedSoftware.app
onHost[?].credentials.use licationHost[1].cre
rname=${userName} dentials.username=a
dmin
Application ${password} is the

host managedSoftware.applicati password. managedSoftware.app
onHost[?].credentials.pas licationHost[1].cre
sword=${password} dentials.password=p
assword
Compute ${name} can be any

server compute.server[?].name=$ meaningful value. compute.server.name
{name} =sys
The default
name for UCS
servers is
"sys". For each
additional UCS
server, ensure
the name is in
the following
format:
sysXXXX
where sys is
lowercase and
XXXX is a
unique
number. For
example
"sys2".
Compute ${serverType} must be

server compute.server[?].type=$ one of the following: UCS, compute.server.type
{serverType} C200M1, C200M2,C220M3, =UCS
C220M4,C240M3,
C240M4,QUANTA, KYLIN,
DELL
Compute ${componentTag} can

server compute.server[?].compone be any meaningful value. compute.server.comp
ntTag=${componentTag onentTag=VMABO-
UCS-1
Compute ${ipAddress} should

server compute.server[?].address be a dotted IP address. In compute.server.addr
=${ipAddress} the case of QUANTA, you ess=10.1.139.30
can specify ranges.

type example
Compute ${username}is the SSH

server compute.server[?].credent username. compute.server.cred
ials.username=${username} entials.username=ad
min
Compute ${password} is the SSH

server compute.server[?].credent password. compute.server.cred
ials.password=${password} entials.password=pa
ssword
Compute ${community} is the

server compute.server[?].credent SNMP community string. compute.server.cred
ials.community=$ entials.community=p
{community} ublic
Switch ${switchType} must be

network.switch[?].type=$ one of the following: network.switch[1].t
{switchType} Nexus1000V, Nexus3000, ype=Nexus5000
Nexus5000, Nexus7000,
Nexus9000, CA3750, or
MDS9000.
Switch ${componentTag} must

network.switch[?].compone be one of the following: network.switch[1].c
ntTag=${componentTag} N1A, N1B, N3A, N3B, N5A, omponentTag=N5A
N5B, N7A, N7B, N9A, N9B,
MGMT-N1A, MGMT-N1B,
MGMT-N3A, MGMT-N3B,
MGMT-N5A, MGMT-N5B,
MGMT-N7A, MGMT-N7B,
MGMT-N9A, MGMT-N9B.
Switch ${ipAddress} should be

network.switch[?].address a dotted IP address. network.switch[1].a
=${ipAddress} ddress=10.1.139.22
Switch ${username} is the SSH

network.switch[?].credent username. network.switch[1].c
ials.username=${username} redentials.username
=admin
Switch ${community} is the

network.switch[?].credent SNMP community string. network.switch[1].c
ials.community=$ redentials.communit
{community} y=public

type example
Storage array ${type} must be one of

storage.storageArray[?].t the following: VNXe3150, storage.storageArra
ype=${type} VNXe3300, VNX5300, y[1].type=VNX5500
VNX5500, VNX5700,
VNX7500, VMAX10K,
VMAX20K, VMAX40K,
VMAX3, VMAX100K,
VMAX200K, VMAX400K,
VMAX450F,VMAX450FX,
VMAX850F,VMAX850FX,
VNX5200, VNX5400,
VNX5600, VNX5800,
VNX7600, VNX8000, VNXe,
VNX, VMAX, VMAXe,
VPlex, ISILON, XIO, UNITY.
Storage array ${componentTag} must

storage.storageArray[?].c be one of the following: storage.storageArra
omponentTag=$ y[1].componentTag=V
VNXe3150-ARRAY,
{componentTag} NX5500-ARRAY
VNXe3300-ARRAY,
VNX5300-ARRAY,
VNX5500-ARRAY,
VNX5700-ARRAY,
VNX7500-ARRAY,
VMAX10K-ARRAY,
VMAX20K-ARRAY,
VMAX40K-ARRAY, VMAX3-
ARRAY, VMAX100K-
ARRAY, VMAX200K-
ARRAY, VMAX400K-
ARRAY, VMAX450F-
ARRAY, VMAX450FX-
ARRAY, VMAX850F-
ARRAY, VMAX850FX-
ARRAY, VNX5200-ARRAY,
VNX5400-ARRAY,
VNX5600-ARRAY,
VNX5800-ARRAY,
VNX7600-ARRAY,
VNX8000-ARRAY, VNXe-
ARRAY, VNX-ARRAY,
VMAX-ARRAY, VMAXe-
ARRAY, VPlex-ARRAY,
ISILON-ARRAY, XIO-
ARRAY, UNITY-ARRAY.
Storage array ${ipAddress} should be

storage.storageArray[?].a a dotted IP address. storage.storageArra
ddress=${ipAddress} y[1].address=10.1.1
39.52

type example
Storage array ${which}

storage.storageArray[?].c storage.storageArra
redentials[?].which=$ should be one of the y[1].credentials[1]
{which} following: ECOM Server, .which=ECOM Server
Control Station, SPA, SPB.
Storage array ${method}

redentials[?].method=$ must be a dotted IP y[1].credentials[1]
{method} address. This is the CIM .method=10.1.139.42
entry point when ${which}
Control Station.
Storage array ${username}

redentials[?].username=$ is the username. y[1].credentials[1]
{username} .username=fmuser
Storage array ${password} is the

storage.storageArray[?].c password. storage.storageArra
redentials[?].password=$ y[1].credentials[1]
{password} .password=password
Storage ${type} is one of the

virtualizer storage.storageVirtualize following storage virtualizer storage.storageVirt
r[?].type=${type} types: VPLEX (for Vblock ualizer[1].type=VPL
Systems and VxBlock EX
Systems) and SCALEIO (for
VxRack Systems).
Storage ${componentTag} can

virtualizer storage.storageVirtualize be any meaningful value. storage.storageVirt
r[?].componentTag=$ ualizer[1].componen
{componentTag} tTag=VPLEX-000-XXX
Storage ${ipAddress} should be

virtualizer storage.storageVirtualize a dotted IP address. storage.storageVirt
r[?].address=${ipAddress} ualizer[1].address=
10.1.139.5
Storage ${method} is the method.

virtualizer storage.storageVirtualize storage.storageVirt
r[?].credentials.method=$ ualizer[1].credenti
{method} als.method=xml
Storage ${username} is the

virtualizer storage.storageVirtualize username. storage.storageVirt
r[?].credentials.username ualizer[1].credenti
=${username} als.username=servic
e

type example
Storage ${password} is the

virtualizer storage.storageVirtualize password. storage.storageVirt
r[?].credentials.password ualizer[1].credenti
=${password} als.password=passwo
rd
Vblock System configuration file example

product=Vblock
system=VBLOCK
type=340w5800
componentTag=VB-340
serialNumber=Marl-VB340-MPE31
vcenters.vcenter[1].name=Vcenter1
vcenters.vcenter[1].url=10.3.32.197
vcenters.vcenter[1].username=username
vcenters.vcenter[1].password=password
compute.server[1].name=sys1
compute.server[1].type=UCS
compute.server[1].componentTag=VMABO-UCS-1
compute.server[1].address=10.3.32.30
compute.server[1].credentials.username=username
compute.server[1].credentials.password=password
compute.server[1].credentials.community=public
network.switch[1].type=Nexus3000
network.switch[1].componentTag=MGMT-N3A
network.switch[1].address=10.3.32.18
network.switch[1].credentials.username=username
network.switch[1].credentials.password=password
network.switch[1].credentials.community=snmp4lab
network.switch[2].componentTag=MGMT-N3B
network.switch[3].componentTag=N9A
network.switch[4].componentTag=N9B
network.switch[5].type=MDS9000
network.switch[5].componentTag=M9A
network.switch[6].componentTag=M9B
storage.storageArray[1].type=VNX5600
storage.storageArray[1].componentTag=VNX5600-ARRAY
storage.storageArray[1].address=10.3.32.199
storage.storageArray[1].credentials[1].which=ECOM Server
storage.storageArray[1].credentials[1].method=10.3.32.199
storage.storageArray[1].credentials[1].username=username
storage.storageArray[1].credentials[1].password=password
storage.storageArray[1].credentials[2].which=Control Station

storage.storageArray[1].credentials[4].which=SPA
storage.storageArray[1].credentials[5].which=SPB
storage.storageVirtualizer.type=VPLEX
storage.storageVirtualizer.componentTag=VPLEX-000-XXX
storage.storageVirtualizer.address=10.3.32.45
storage.storageVirtualizer.credentials.method=xml
storage.storageVirtualizer.credentials.username=username
storage.storageVirtualizer.credentials.password=password
amp.type=AMP-2HA
amp.componentTag=Management
amp.serialNumber=AMP-2-SN
amp.compute.server[1].name=svr-mgmt-1
amp.compute.server[1].type=C220M3
amp.compute.server[1].componentTag=SERVER-A
amp.compute.server[1].address=10.3.32.8
amp.compute.server[1].credentials.username=username
amp.compute.server[1].credentials.password=password
amp.compute.server[1].credentials.community=cimcpublic
amp.compute.server[2].componentTag=SERVER-B
amp.storage.storageArray.type=VNXe
amp.storage.storageArray.componentTag=VNXe-ARRAY
amp.storage.storageArray.address=10.3.32.44
amp.storage.storageArray.credentials[1].method=uemcli
amp.storage.storageArray.credentials[1].username=username
amp.storage.storageArray.credentials[1].password=password
VxBlock System configuration file examples
Component Example
VxBlock System
product=Vxblock
system=VXBLOCK
type=320w5500
componentTag=VB-320
serialNumber=VB320-975-318-642

Component Example
Production vCenter
vcenters.vcenter.name=Vcenter1
vcenters.vcenter.url=10.1.139.39
centers.vcenter.username=vb300swqa\administrator
vcenters.vcenter.password=password
Management
managedSoftware.applicationHost[1].name=app-host-1
managedSoftware.applicationHost[1].address=10.1.139.42
managedSoftware.applicationHost[1].credentials.username=admin
managedSoftware.applicationHost[1].credentials.password=password
UCS server
compute.server.name=sys
compute.server.type=UCS
compute.server.componentTag=VMABO-UCS-1
compute.server.address=10.1.139.30
compute.server.credentials.username=admin
compute.server.credentials.password=password
compute.server.credentials.community=public

Component Example
C-Series server
compute.server.name=svr1
compute.server.type=C220M3
compute.server.componentTag=SERVER-A
compute.server.address=10.1.139.10
compute.server.credentials.username=admin
compute.server.credentials.password=password
compute.server.credentials.community=cimcpublic
Nexus 3000 Switch

network.switch[3].credentials.username=admin
network.switch[3].credentials.community=public

Component Example
Nexus 5000 Switch

Nexus 9000 Switch

MDS 9000 Switch

network.switch[5].componentTag=M9A

Component Example
Nexus 1000 Switch

network.switch[7].type=Nexus1000V
VNXe storage array

storage.storageArray[1].type=VNXe
storage.storageArray[1].componentTag=VNXe-ARRAY
storage.storageArray[1].credentials[1].method=uemcli
storage.storageArray[1].credentials[1].username=admin

Component Example
VNX storage array

storage.storageArray[1].credentials[1].username=fmuser
storage.storageArray[1].credentials[2].username=sysadmin
storage.storageArray[1].credentials[2].password=sysadmin
storage.storageArray[1].credentials[3].username=sysadmin

Component Example
VMAX storage array

storage.storageArray[1].type=VMAX
storage.storageArray[1].componentTag=VMAX-ARRAY
storage.storageArray[1].credentials[1].which=VMAX
storage.storageArray[1].credentials[1].username=fmuser
Isilon storage array

storage.storageArray[2].type=ISILON
storage.storageArray[2].componentTag=ISILON-ARRAY-CLUSTER-1
storage.storageArray[2].credentials[1].method=snmpv2c
storage.storageArray[2].credentials[1].community=cluster1snmppassw
ord
storage.storageArray[2].credentials[2].method=ssh
storage.storageArray[2].credentials[2].username=vision-user
storage.storageArray[2].credentials[3].method=restApi
storage.storageArray[2].credentials[3].username=vision-user

Component Example
VPLEX
storage.storageVirtualizer.type=VPLEX
storage.storageVirtualizer.componentTag=VPLEX-000-XXX
storage.storageVirtualizer.credentials.method=xml
storage.storageVirtualizer.credentials.username=service
Xtremio storage
array storage.storageArray[2].type=XTREMIO
storage.storageArray[2].componentTag=XIO-ARRAY-1
storage.storageArray[2].credentials[1].which=XTREMIO
storage.storageArray[2].credentials[1].method=xml
storage.storageArray[2].credentials[1].username=admin1

Component Example
Unity storage array

storage.storageArray[1].type=UNITY
storage.storageArray[1].componentTag=Unity-Array-1
storage.storageArray[1].credentials[1].method=restApi
storage.storageArray[1].credentials[1].username=admin
AMP-2S
amp.type=AMP-2S
amp.compute.server[1].name=SERVER-A
amp.compute.server[1].type=C22OM4
amp.compute.server[1].ComponentTag=Server-A
amp.compute.server[1].credentials.username=admin

Component Example
AMP C-Series
server amp.compute.server[1].name=svr1
amp.compute.server[1].componentTag=SERVER-A
amp.compute.server[1].credentials.username=admin
AMP vCenter
amp.vcenters.vcenter.name=Vcenter1
amp.vcenters.vcenter.url=10.11.78.58
amp.vcenters.vcenter.username=root
amp.vcenters.vcenter.password=password
AMP VNXe storage

array amp.storage.storageArray.type=VNXe
amp.storage.storageArray.componentTag=VNXe-ARRAY
amp.storage.storageArray.address=10.11.240.243
amp.storage.storageArray.credentials[1].method=uemcli
amp.storage.storageArray.credentials[1].username=admin
amp.storage.storageArray.credentials[1].password=password

Configuration file example
product=Vxblock
system=VXBLOCK
type=240
componentTag=VXB-240
serialNumber=RTP-VXB240-DQAV24
compute.server[1].name=svr1
compute.server[1].type=C220M3
compute.server[1].componentTag=SERVER-A
compute.server[2].componentTag=SERVER-B
compute.server[3].componentTag=SERVER-C
compute.server[4].componentTag=SERVER-D
network.switch[1].type=Nexus1000V

storage.storageArray[1].credentials[2].which=Control Station
amp.type=AMP-2P
amp.compute.server[1].componentTag=SERVER-MGMT-A
VxRack System configuration file examples
Component Example
VxRack System
product=VxRack
system=VXRACK
type=VxRack1000FLEX
componentTag=VX1000FLEX
serialNumber=VX1000FLEX-777-888-999

Component Example
Location
location.building=350 Campus
location.geo=Marlborough, MA
location.floor=1rd
location.tile=2
location.row=Dev
location.room=Eisenhower
Production vCenter
vcenters.vcenter[1].username=administra
tor@vsphere.local
vcenters.vcenter[1].componentTag=Vcente
r1
vcenters.vcenter[1].password=Example123
Rack
vblockRacks.rack.rackId=1
vblockRacks.rack.rackManager.gatewayIpA
ddress=10.130.30.10
vblockRacks.rack.rackManager.credential
s.community=public
vblockRacks.rack.rackManager.credential
s.method=snmpv2c

Component Example
QUANTA server
compute.server[1].type=QUANTA
compute.server[1].componentTag=SYSTEM-1
compute.server[1].address=10.140.40.10-
10.140.40.15
compute.server[1].credentials[1].method
=SNMPV2C
compute.server[1].credentials[1].commun
ity=public1
QUANTA server
compute.server[2].address=10.140.40.20,
10.140.40.22,10.140.40.24
=SNMPV2C
ity=public2
QUANTA server
compute.server[3].address=10.140.40.25-
10.140.40.30,10.140.40.35,10.140.40.40-
10.140.40.50
=SNMPV2C
ity=public3

Component Example
Nexus 9000 Switch

network.switch[1].componentTag=vx9332a
network.switch[1].credentials.username=
admin
network.switch[1].credentials.password=
Example123
network.switch[1].credentials.community
=public
Nexus 9000 Switch

network.switch[2].componentTag=vx9332b
admin
Example123
=public

Component Example
Nexus 3000 Switch

admin
Example123
=buzz
AMP vCenter server

amp.vcenters.vcenter[1].username=admini
strator@vsphere.local
amp.vcenters.vcenter[1].name=Vcenter1
amp.vcenters.vcenter[1].password=abcdef
amp.vcenters.vcenter[1].url=10.136.30.1
04

Component Example
AMP Kylin server

amp.compute.server[1].type=KYLIN
amp.compute.server[1].componentTag=KYLI
N-SERVER -1
amp.compute.server[1].address=10.136.7.
240
amp.compute.server[1].credentials[1].me
thod=IPMIV2
amp.compute.server[1].credentials[1].us
ername=root
amp.compute.server[1].credentials[1].pa
ssword=password
AMP Kylin server

amp.compute.server[2].type=KYLIN
amp.compute.server[2].componentTag=KYLI
N-SERVER -2
amp.compute.server[2].address=10.136.7.
241
amp.compute.server[2].credentials[1].me
thod=IPMIV2
amp.compute.server[2].credentials[1].us
ername=root
amp.compute.server[2].credentials[1].pa
ssword=password

Component Example
Storage virtualizer
storage.storageVirtualizer.address=192.
168.10.100
storage.storageVirtualizer.type=SCALEIO
storage.storageVirtualizer.componentTag
=SCALEIO-123-XYZ
storage.storageVirtualizer.credentials.
username=admin
method=restApi
password=Example123
Operating Systems
operatingsystems.operatingsystem.addres
s=10.3.14.191
operatingsystems.operatingsystem.type=R
EDHAT
operatingsystems.operatingsystem.compon
entTag=RHEL1
operatingsystems.operatingsystem.creden
tials.username=root
tials.method=SSH
tials.password=password

Component Example
Component Credentials
componentcredentials.componentcredentia
l[1].iprange=10.3.249.31-10.3.249.50
l[1].credentials.method=SNMPV2C
l[1].credentials.community=snmp4lab
l[2].iprange=10.3.14.191-10.3.14.192
l[2].credentials.method=SSH
l[2].credentials.username=vision
l[2].credentials.password=password
compute.server[1].componentTag=SERVER-1
compute.server[1].address=10.3.249.31-1
0.3.249.50
s=10.3.14.191
EDHAT
entTag=RHEL1

Component Example
s=10.3.14.192
EDHAT
entTag=RHEL1

Configuration file example
product=VxRack
system=VXRACK
serialNumber=VX1000-GOLD-1234
type=VxRack1000FLEX
componentTag=VX1000-ABC
location.building= address
location.geo=Town, State
location.floor=1st
location.tile=2
location.row=row
location.room=Lab
vcenters.vcenter[1].name=VcenterCustomer
vcenters.vcenter[1].componentTag=VcenterCustomer
compute.server[1].type=DELL
compute.server[1].componentTag=DELL-SYSTEM-1
compute.server[1].address=192.168.111.11-192.168.111.12
compute.server[1].credentials[1].method=REDFISH
compute.server[1].credentials[1].username=username
compute.server[1].credentials[1].password=password
compute.server[4].componentTag=DELL-STORAGE-SYSTEM-4
network.switch[1].credentials.community=VXF-cisco1000
network.switch[2].credentials.community=VXF-cisco1000

network.switch[5].credentials.community=vision
network.switch[6].credentials.community=vision
storage.storageVirtualizer.type=SCALEIO
storage.storageVirtualizer.componentTag=SCALEIO-GOLD-XXX
storage.storageVirtualizer.credentials.username=username
storage.storageVirtualizer.credentials.method=restApi
amp.type=AMP-KYL
amp.serialNumber=AMP-DELL-123
amp.vcenters.vcenter[1].username=username
amp.vcenters.vcenter[1].name=AMP-Vcenter1
amp.vcenters.vcenter[1].componentTag=AMP-Vcenter1
amp.vcenters.vcenter[1].password=password
amp.vcenters.vcenter[1].url=10.136.56.228
amp.compute.server[1].type=DELL
amp.compute.server[1].componentTag=DELL-AMP-SERVER-1
amp.compute.server[1].address=192.168.111.22-192.168.111.24
amp.compute.server[1].credentials[1].method=REDFISH
amp.compute.server[1].credentials[1].username=username
amp.compute.server[1].credentials[1].password=password
operatingsystems.operatingsystem[1].address=192.168.150.19-192.168.150.21
operatingsystems.operatingsystem[1].type=REDHAT
operatingsystems.operatingsystem[1].componentTag=RHEL-STORAGE-1
operatingsystems.operatingsystem[1].credentials.username=username
operatingsystems.operatingsystem[1].credentials.method=SSH
operatingsystems.operatingsystem[1].credentials.password=password

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.
Copyright 2017 Dell Inc. or its subsidiaries. All Rights Reserved. Dell, EMC, and other trademarks are trademarks of
Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners. Published in the USA in
February 2017.
Dell EMC believes the information in this document is accurate as of its publication date. The information is subject to
change without notice.
Copyright | 226

Vision 3 5 1 Installation

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Vision 3 5 1 Installation

Hochgeladen von

Copyright:

Verfügbare Formate

Dell EMC Vision Intelligent Operations

Document revision 2.0

DELL EMC CONFIDENTIAL

April 2017 2.0 Minor editorial change

February 2017 1.0 New release of the product

Installing and configuring the Vision Core VM........................................................................................ 9

Installing and configuring the multisystem management (MSM) VM................................................ 147

Completing the Vision software installation........................................................................................ 186

Configuring ESRS for Vision software................................................................................................. 187

Configuration file format and examples............................................................................................... 193

Refer to the Glossary for terms, definitions, and acronyms.

VM Memory requirement vCPUs Disk size (GB)

Vision Core VM 8 2 200

Logical AMP - Vblock System storage array

HA-AMP version 1 - VNXe3100

HA-AMP version 2 - VNXe3150

AMP-2V - Vblock System storage array

AMP-2P - C-Series local storage

AMP-2RP - C-Series local storage

AMP-2LP - C-Series local storage

AMP-2S - VNXe storage

VxBlock System 240

Vblock System 350 and VxBlock System 350

Vblock System 540 and VxBlock System 540

Vblock System 740 and VxBlock System 740

AMP-3V - Vblock System storage array

AMP-3P - C-Series local storage

VxRack Controller - Management servers local storage

VCE System Logical AMP Physical AMP

Vblock System 100 Yes No

Vblock System 200 Yes Yes

Vblock System 240 Yes Yes

VxBlock System 240 Yes Yes

Vblock System 300 series No Yes

VxBlock System 340 No Yes

VxBlock System 350 No Yes

Vblock System 540 No Yes

VxBlock System 540 No Yes

Vblock System 700 series No Yes

VxBlock System 740 No Yes

VxRack System with FLEX No Yes

Preparing for installation

Downloading the OVA file for the Vision Core VM

Before you begin

Ensure that a valid DNS is configured.

2 Navigate to the location of the Vision Core VM OVA file.

Downloading compliance content for the Vision Core VM

Before you begin

9 | Installing and configuring the Vision Core VM

Installing compliance content on the Vision Core VM (see page 129)

Uploading compliance content (see page 166)

Deploying, starting and configuring the Vision Core VM

Deploying the Vision Core VM

About this task

Before you begin

Download the OVA file.

Ensure that you have the LCS.

Installing and configuring the Vision Core VM | 10

Host or cluster ESX or ESXi host for the virtual machine.

Storage Location where the virtual machine saves files.

Network mapping Network that the virtual machine uses.

1 Start the vSphere Client.

2 Select the vCenter Server host.

a Select Inventory > Hosts and Clusters.