Revision history Date Document Description of changes revision January 2018 Added support for VMware vSphere 6.5. Removed VMware vSphere 5.5. December 2016 Added support for AMP-2 Cisco UCS M4 servers with VMware vSphere 5.5. Removed VLAN 118 from topics. April 2016 Added support for VxBlock System 240, VMware vSphere 6.0, and Cisco UCS M4 servers.
Contents Introduction..............................7 Intelligent Physical Infrastructure appliance................... 8 Managing the AMP............................9 Upgrading the Cisco UCS C220 Server on the Advanced Management Platform.........9 Upgrading the Cisco UCS C2x0 Server (CIMC 2.x firmware).............. 10 Configuring RAID devices........................11 Backing up the AMP..........................11 Creating a backup directory......................
Page 4
Creating VLANs and ports on the Cisco Nexus 5548UP Switch............43 Removing a VLAN from the Cisco Nexus series switches..............44 Configuring zones for storage......................45 Configuring Cisco Nexus 5000 Series NX-OS Adapter-FEX software..........46 Manually creating virtual Ethernet interfaces..................48 Managing virtual HBA interfaces on the Cisco UCS VIC 1225............49 Creating virtual HBAs...........................
Page 5
Managing VMware vSphere virtual machines..................85 Increasing the disk timeout on Microsoft Windows virtual machines........... 85 Setting up Java and Internet Explorer on the management virtual machine........85 Managing VMware vCenter Single Sign-On for VMware vSphere 6.x..........87 VMware vCenter Single Sign-On overview..................87 Unlocking and resetting the VMware vCenter Single Sign-On administrator password (VMware vSphere 6.0)............................87 Managing the lockout status of VMware vCenter Single Sign-On account (VMware vSphere 6.0)..
Page 6
Managing licenses..........................117 Adding hosts............................117 Creating a port profile......................... 117 Modifying the uplink port profiles......................118 Removing the uplink port profiles....................... 119 Modifying vEthernet data port profiles....................120 Modifying the QoS settings ....................... 122 Upgrading the VEM software......................123 Troubleshooting the Cisco Nexus 1000V switch................123 Guidelines for backing up system configuration files................
Introduction This document explains how to perform administrative tasks on the Converged System after it has been installed. In this document, the Vblock System and the VxBlock System are referred to as Converged System. The target audience for this document includes those responsible for managing the Converged System, including the system administrator and personnel responsible for remote management of the Converged System.
IPI Appliance The IPI Appliance provides an intelligent gateway to gather information about power, thermals, security, alerts, and all components in the physical infrastructure of each cabinet. Vision Intelligent Operations uses SNMP to poll the status of the IPI Appliance and then passes the results to VMware vCenter.
Managing the Advanced Management Platform Upgrading the Cisco UCS C220 Server on the Advanced Management Platform Use this procedure to prepare the ISO for a remote upgrade using a Keyboard, Video, Mouse (KVM) switch. Before you begin If you are upgrading a Cisco UCS C220 Server on the Advanced Management Platform: Power off or migrate VMs on the host being upgraded before running the upgrade procedure.
From the Host Upgrade menu, at the Enter Choice prompt, select all of the above. After all upgrades are successful, select the appropriate CIMC settings to use during the reboot from the Host Upgrade menu. Select Reboot to retain the current settings of CIMC. Verify that all VMs are powered up and have access to the VMware vCenter.
At the Confirmation screen, select Yes. From the Confirmation screen for the BIOS update, select Yes. After reboot is complete, verify that the VMware vSphere ESXi host is accessible to the AMP-2 vCenter Server instance. Configuring RAID devices Use this procedure to set up RAID devices on the AMP-2P Cisco UCS C2x0 server that has an LSI MegaRAID controller card.
About this task This process is required to support the recovery of the Cisco network device configurations in the Converged System. Establish a process to perform network device configuration backups and that you place the repository on the AMP VM that hosts the fabric manager service. Before you begin •...
• VMware vCenter SQL database (if VMware vSphere vCenter has been deployed on Windows) • VMware vCenter Update Manager • Platform Services Controller (VMware vSphere 6.0) • Element Manager • Other VMs identified as part of the Core or Optional workloads to manage the Converged System.
Page 14
Procedure To restore a configuration file, refer to the documentation provided with the vendor to restore the device. Managing the Advanced Management Platform...
Managing compute resources Modifying the time zone setting using CIMC In the Server Summary window of the CIMC, the Current Time field shows the current date and time, that is retrieved from the server BIOS. Procedure Reboot the server and press the F2 key when prompted to access the BIOS configuration menu. Select the BIOS configuration tab and change the date and/or time.
Page 16
About this task Use an SNMP server to monitor, send alerts and reports, and to help troubleshoot. SNMP v3 is recommended as the most secure option in using the SNMP protocol. Procedure In the Navigation window in CIMC, select the Admin tab. On the Admin tab, click Communications Services.
In the Trap Destinations area, complete the following fields: ID column: Type the trap destination ID. This value cannot be modified. — Enabled column: For each SNMP trap destination that you want to use, check the associated — box in this column. Trap Destination IP Address column: Type the IP address to which SNMP trap information —...
Page 18
In the Adapter Cards area, select the adapter card. If the server is powered on, the resources of the selected adapter card appear in the tabbed menu below the Adapter Cards area. In the tabbed menu below the Adapter Cards area, select the vNICs tab. In the Host Ethernet Interfaces area, select a vNIC from the table.
Page 19
You can update any of the fields in the following areas. When you are finished, click Save Changes. General Area Description Field name Name User-defined name for the vNIC. Once you create the vNIC, the name cannot be changed. Maximum transmission unit, or packet size, that this vNIC accepts, between 1500 and 9000.
Page 20
Ethernet Receive Queue Area Field name Description Receive Queue Count Number of receive queue resources to allocate, between 1 and 256. Receive Queue Ring Size Number of descriptors in each receive queue, between 64 and 4096. Ethernet Transmit Queue Area Field name Description Transmit Queue Count...
Field name Description Enable TCP RSS distributes network receive processing across multiple CPUs in Receive Side multiprocessor systems. Scaling If this option is selected, network receive processing is shared across processors whenever possible. If this option is not selected, network receive processing is handled by a single processor, even if additional processors are available.
Page 22
In the following illustration and in the following sections, the server is connected to port Eth1/7 on both Cisco Nexus 5548UP Switches. Your configuration may be different. Related information Virtual server interface numbering standards (see page 25) Managing compute resources...
Adding virtualized servers: configuring static vEthernet interfaces on the Cisco Nexus 5548UP switches About this task In this example procedure, the server is connected to port Eth1/7 on both Cisco Nexus 5548UP switches. Before you begin Make sure the host has been zoned, masked, and allocated an appropriate sized boot LUN. This example assumes all VLANs are trunked where necessary.
Create the vEthernet and vFC interfaces for booting on Cisco Nexus 5548-B and add the vFC to the VSAN database. On Cisco Nexus 5548-B only, enter the following commands: interface Vethernet751 switchport mode trunk switchport trunk allowed vlan 1,1501 (replace 1501 with Fabric B FCoE VLAN) bind interface Ethernet1/7 channel 4 interface vfc751 bind interface Vethernet751...
Enabling network interface virtualization on the converged network adapter To enable VNTAG on the converged network adapter (CNA), perform the following steps: Procedure Log on to Cisco Integrated Management Controller (CIMC) on the server. On the left pane, select Inventory. On the top right pane, select Cisco VIC Adapters. On the middle right pane, ensure that General is selected.
Select Trust Host CoS. In the Channel Number field, enter 5. In the Port Profile field, select vmotion. Click Add vNIC. Repeat these steps for Eth3, except ensure the Uplink Port field is set to 1, and in the Channel Number field, enter 6.
In the Port Profile field, select n1k_L3_control. Click Add vNIC. Repeat these steps for Eth7, except ensure the Uplink Port field is set to 1, and in the Channel Number field, enter 10. Configuring the NFS vNICs (Unified configuration only) If you have a unified configuration, use the following steps to configure the NFS vNICs: Procedure Select Inventory >...
Click Save Changes. Repeat these steps for FC1, except make sure the Uplink Port field is set to 1, the Default VLAN field is set to 1501, and the Channel Number field is set to 4. Power cycling the host and verifying the host virtual Fibre Channel After configuring all the components, perform the following steps: Procedure Power cycle the host.
Continue with normal operating system installation procedures. Adding a bare metal host: overview The Converged System can have half of the servers as bare metal servers. Dell EMC provides limited support for bare metal servers. For more information, consult Support about the Bare Metal Support Policy.
• Create dynamic vEthernet interfaces of the Cisco Nexus 5548UP Switches, which entails less logical configuration but sacrifices some customization. vEthernet interfaces are dynamically created as the server boots up, with IDs greater than 32768. Once the vEthernet interfaces are created and the configuration is saved, the interfaces remain the same across reboots.
Page 32
Before you begin Make sure the host has been zoned, masked, and allocated an appropriately sized boot LUN. This example assumes all VLANs are trunked where necessary. On Cisco Nexus 5548UP Switches A and B, enter the following commands: Procedure Enter the following commands in configuration mode to enable virtual network tagging (VNTag) for the port that connects to the server: interface Ethernet 1/7...
Page 33
Create the VLANs: vlan 301 name PROD-VLAN-301 vlan 302 name BACKUP-VLAN-302 Create the vEthernet port-profile: port-profile type vethernet PROD-VLAN-301 switchport access vlan 301 switchport mode access state enabled port-profile type vethernet BACKUP-VLAN-302 switchport access vlan 302 switchport mode access state enabled Create static vEthernet interfaces (on both Cisco Nexus 5548UP Switches) for the server's vNICs.
Page 34
Create the vEthernet and vFC interfaces for booting on the Cisco Nexus 5548-B Switch and add the vFC to the vSAN database. On the Cisco Nexus 5548-B Switch only, enter the following commands: interface Vethernet751 switchport mode trunk switchport trunk allowed vlan 1,1501 bind interface Ethernet1/7 channel 4 interface vfc751 bind interface Vethernet751...
Bare metal host static interface numbering standards The following table provides the numbering standards for the bare metal interfaces. Servers are racked from the bottom of the cabinet from A (1) to L (12). Server Production Backup FCoE FCoE vEth Interface vEth Interface vEth Interface vFC Interface...
Page 36
The server (Server 7) in this example is connected to port Eth1/7 on both Cisco Nexus 5548UP switches, as shown in the following illustration. Your configuration may be different. On Cisco Nexus 5548UP Switches A and B, enter the following commands: Procedure Enable the auto-creation of the Cisco Nexus 5548UP Switches vEthernet interfaces: vethernet auto-create...
Page 37
Enable virtual network tagging (VNTag) for the port that connects to the server: interface Ethernet 1/7 switchport mode vntag Create the VLANs: vlan 301 name PROD-VLAN-301 vlan 302 name BACKUP-VLAN-302 Create the vEthernet port-profile: port-profile type vethernet PROD-VLAN-301 switchport access vlan 301 switchport mode access state enabled port-profile type vethernet BACKUP-VLAN-302...
Page 38
Create the vEthernet and vFC interfaces for booting on the Cisco Nexus 5548-B Switch and add the vFC to the vSAN database. On the Cisco Nexus 5548-B Switch only, enter the following commands: interface Vethernet751 switchport mode trunk switchport trunk allowed vlan 1,1501 bind interface Ethernet1/7 channel 4 interface vfc751 bind interface Vethernet751...
Bare metal host dynamically created interface numbering standards The numbers for production and backup vEthernet interfaces are established when the server boots up, and are greater than 32,768. Servers are racked from the bottom of the cabinet from A (1) to L (12). Server Production Backup...
Page 40
If jumbo frames are required, change the MTU to 9000. Otherwise leave the setting at 1500. Verify that the Uplink Port field is set to 0, which ensures that in the event of a failure, traffic fails over automatically to 5548-B. Clear the PXE Boot check box.
Related information Bare metal host static interface numbering standards (see page 35) Modifying boot options To configure the boot options, perform the following tasks. Procedure Configure the boot table. Log on to CIMC on the server. On the left pane, select Inventory > Network Adapters > vHBAs Highlight fc0 and click Boot Table.
UCS Blade Servers and Rack Servers and is shipped disabled. Dell EMC supports Cisco TPM hardware but does not support the Cisco TPM functionality. Using Cisco TPM features involves using a software stack from a vendor with significant domain experience in trusted computing.
Managing networking resources Creating VLANs and ports on the Cisco Nexus 5548UP Switch Use this procedure to create VLANs and ports on the Cisco Nexus 5548UP Switch. About this task VLANs on the Cisco Nexus 5548UP Switches allow network administrators to create logical broadcast domains that can span multiple switches, regardless of their locations.
Depending on the range of the VLAN, you can configure the following parameters for VLANs (except the default VLAN): • VLAN name • Shutdown or no shutdown When you delete a VLAN, the ports associated with that VLAN are shut down and no traffic flows. However, the system retains the VLAN-to-port mapping for that VLAN.
To enter VLAN configuration mode, type: vlan vlan_id To delete the specified VLAN, type: no vlan vlan_id Configuring zones for storage Zoning enables you to set up access control between storage devices or user groups. If you have administrator privileges in your fabric, you can create zones to increase network security and to prevent data loss or corruption.
switch(config)# zone name zone-name vsan vsan-id switch(config-zone)# member type value switch(config)# zoneset activate name zoneset-name vsan vsan-id Configuring Cisco Nexus 5000 Series NX-OS Adapter-FEX software The Cisco NX-OS Adapter-FEX feature combines the advantages of the FEX link architecture with server I/O virtualization to create multiple virtual interfaces over a single Ethernet interface.
Page 47
Configure a server network adapter. Use the network adapter configuration utility on the server to enable NIV mode on the network adapter. See the documentation of your specific server network adapter for details. To complete the configuration, you might have to reboot the server to reset the network adapter.
Initialize the Server Network Adapter. After you configure the vNICs on the server network adapter, you might have to reboot the server and reset the server network adapter and reload the drivers. See the documentation for your specific server network adapter for details. When the configuration is complete, the server network adapter and the switch re-establishes a link and performs the initial handshake and negotiation process.
5548A: interface Vethernet100 (defines the vethernet interface) inherit port-profile management (defines the port-profile to apply) bind interface Ethernet1/1 channel 1 (defines the physical port connected to the server and the channel of the vNIC) 5548B: interface Vethernet101 (defines the vethernet interface) inherit port-profile management (defines the port-profile to apply) bind interface Ethernet1/1 channel 2...
Results Reboot the server to create the vHBA. If configuration changes are required, configure the new vHBA. For more information about Cisco UCS VIC 1225 vHBAs, see the Cisco UCS C-Series Servers Integrated Management Controller CLI Configuration Guide, Release 1.4. . Related information Modifying virtual HBA properties (see page 50)
Page 51
To enter the host FC interface command mode for the specified vHBA, enter the following commands through SSH to CIMC IP address: Server# scope chassis Server /chassis # scope adapter index Server /chassis/adapter # scope host-fc-if {fc0 | fc1 | name} From FC interface command mode, you can enter the following commands: Command Description...
Page 52
Command Description set port-down-io-retry- Port down I/O retries value, the number of times an I/O request to a port is returned count count because the port is busy before the system decides the port is unavailable. The range is 0 to 255; the default is 8 retries. set port-down-timeout Port down timeout value, the number of milliseconds a remote Fibre Channel port msec...
Upgrading the Cisco Nexus 3048 Switch software Use this procedure to upgrade both the NX-OS Kickstart and NX-OS System images on the Cisco Nexus 3048 Switch. About this task Upgrade recommendations: • Upgrading the two images together. • Ensuring the version numbers of the images are the same. •...
Page 54
To verify the switch has enough space for the new image, type: switch# dir bootflash: The system lists the contents of the bootflash: 495 Apr 06 03:47:56 2011 license_XXXXXXXX.lic 49152 Apr 06 03:51:08 2011 lost+found/ 1893 May 26 23:14:43 2011 mts.log 25164288 Apr 06 03:41:50 2011 n3000-uk9-kickstart.5.0.2.N2.1.bin...
Page 55
To display the impact of the upgrade, type: switch(config)# show install all impact kickstart bootflash:n5000-uk9- kickstart.5.0.3.N1.1c.bin As the system performs the upgrade, it displays status messages like the following: Verifying image bootflash:/n5000-uk9-kickstart.5.0.3.N1.1c.bin for boot variable "kickstart".[####################] 100% -- SUCCESS Verifying image bootflash:/n5000-uk9.5.0.2.N2.1.bin for boot variable "system". [####################] 100% -- SUCCESS Verifying image type.
Page 56
To install the new Cisco NX-OS images, type install all kickstart bootflash:n5000- uk9-kickstart.5.0.3.N1.1c.bin system bootflash:n5000- uk9.5.0.3.N1.1c.bin To view the progress of the installation during the installation process, type show install all. As the system performs the installation, it displays status messages like the following: Verifying image bootflash:/n5000-uk9-kickstart.5.0.3.N1.1c.bin for boot variable "kickstart".
2011 Sep 8 18:16:43 VSJ3X2N3048A Sep 8 18:16:43 %KERN-0- SYSTEM_MSG: Shutdown Ports.. - kernel 2011 Sep 8 18:16:43 VSJ3X2N3048A Sep 8 18:16:43 %KERN-0-SYSTEM_MSG: writing reset reason 49, - kernel Broadcast message from root (Thu Sep 8 18:16:43 2011): The system is going down for reboot NOW! Type Y to continue with the installation.
Page 58
Related information http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus3000/sw/upgrade/7_x/ Cisco_n3k_Upgrade_Downgrade_7x.html? Cisco Nexus 9000 Series NX-OS Software Upgrade and Downgrade Guide Managing networking resources...
Managing storage resources Logging on to a storage array Use this procedure to log on to the storage array. Before you begin Before performing this task, obtain the: • IP addresses of the two storage processors. • IP address of the primary control station (unified only). •...
Page 60
About this task Use the following guidelines: • Use drives in multiples of RAID group sizes. Create new virtual provisioning (VP) pools only to support new application requirements. • Bare metal hosts require separate disk drives. The boot LUNs and data LUNs for bare metal cannot coexist with the same disk groups or VP pools used for ESX boot and ESX data volumes.
What to do next After the storage pool has been created, you can create LUNs in the storage pool. Expanding a storage pool Use this procedure to grow a storage pool. Before you begin Before performing this task, verify that storage pools exist and disk drives are available to expand the storage pool.
Monitoring a storage pool Use this procedure to monitor pools in a storage array. Procedure Log on to Unisphere and select the storage array you want to monitor. Select Storage > Storage Configuration > Storage Pools. When the Pools window appears, select the storage pool you want to monitor and click Properties.
Ionix UIM/P is not used. As you create a data LUN, consider the following points: • VMware ESXi 5.x can support larger LUNs. Dell EMC recommends using a maximum size of 2 TB until larger LUNs have been validated. Managing storage resources...
• Bare metal LUN sizes vary, depending on the application requirements. • When creating a LUN, ensure that LUNs are distributed evenly across the SPs. Even LUN IDs are owned by SP A, and odd LUN IDs are owned by SP B. •...
Before you begin • Obtain the IP address and the log on credentials for the VNXe array. • Confirm that increasing LUN capacity will not exceed the total array capacity. Procedure Log on to Unisphere. Select Storage > LUNs. Right click the LUN that needs to be expanded and select Expand. In the LUN Expand Storage dialog, specify the new user capacity.
To delete a storage group, select Hosts > Storage Groups. From the list of storage groups, select the storage group and click Delete. What to do next Connect the hosts and the LUNs to the storage group. Adding a host to a storage group Use this procedure to connect hosts to a storage group.
Procedure Log on to Unisphere and select the storage array on which you want to connect the LUN. Select Hosts > Storage Groups. From the Storage Groups window, select a storage group and click Connect LUNs. When the Storage Group Properties window appears, select the LUNs tab. In the Show LUNs field, select ALL.
Page 68
When upgrading Cisco UCS rack servers in a Converged System, consider the following guidelines: • Enable EVC mode only if you are adding or planning to add hosts with newer CPUs to an existing cluster. • ® ® ™ Cisco UCS rack servers all support EVC mode Intel Nehalem Generation (Xeon Core i7).
Creating X-Blades Configuring Virtual Data Movers on VNX provides information on creating X-Blades. Refer to Configuring Virtual Data Movers on VNX. Creating X-Blades...
Managing NFS Creating a file system on a storage array Use this procedure to create a file system on a storage array. Before you begin Verify that there is sufficient space in the NAS pool to create the file system. About this task Use the following guidelines for file system slicing: •...
Page 71
Procedure Log on to the primary Control Station using Unisphere on the storage management VM. From the main menu, select Storage > Storage Configuration > File Systems. When the File Systems list appears, to create a new file system, click Create. From the Create File System window, perform the following: From the Create from field, select Storage Pool.
Related information Mounting the NFS export (see page 73) Creating an NFS export on a storage array (see page 72) Creating an NFS export on a storage array Use this procedure to create an NFS export on a storage array. Before you begin Creating a file system on a storage array (see page 70)
Mounting the NFS export Use this procedure to mount the NFS export on VMware vSphere ESX. Before you begin • Set export permissions on the storage array to allow the host to access the export. • Verify that there is network connectivity between the storage array and the host where the NFS export is to be mounted.
When the warning message appears, click Yes to unmount the NFS export. Deleting the NFS Export Use this procedure to delete the NFS export. Procedure Log on to the primary control station using Unisphere on the storage management VM. Select Storage > Shared Folders > NFS . From the list of NFS exports, right-click the NFS export and select Delete.
Managing CIFS Creating a CIFS file system Use this procedure to create a CIFS file system. Before you begin Verify that: • A CIFS server exists and is licensed on the storage array. • CIFS services are up and running. •...
Procedure Log on to the Primary Control Station using Unisphere on the storage management VM. Select Storage > Storage Configuration > File Systems. When the File Systems list appears, click Create. From the Create File System window, perform the following: From the Create from field, select Storage Pool.
• Verify that the CIFS server is joined with an Active Directory domain, or a different authentication method must be used to access the CIFS share. • Verify that NTP is running on the X-Blades and the time on the X-Blades is in sync with the AD servers.
Before you begin Verify that the guest operating system on which the share is being mapped has access to the CIFS share using an authentication method, such as Active Directory. Procedure From the guest operating system where the CIFS share is to be mapped, right-click My Computer, and select Map Network Drive.
Page 79
From the listing of CIFS Shares, right-click the CIFS share and select Delete. When Confirm Delete message appears, click OK. To verify that that CIFS share was deleted, select Storage > Shared Folders > CIFS. From the list of shares, verify that the deleted share does not appear. Managing CIFS...
The following release of VMware vSphere ESXi is supported: • Dell EMC recommends that you use the VMware Update Manager (VUM) if upgrading to a newer supported build, however, you can use the CLI to install the patch. Do not use this procedure for major upgrades.
Reboot the VMware vSphere ESXi host. Configuring advanced settings for VMware vSphere ESXi (vSphere 6.x) Configure advanced VMware vSphere ESXi settings for compute servers. About this task The following advanced settings are available: Setting Value to configure Default value to restore for Default value to restore for VMware vSphere 5.5 (if VMware vSphere 6.x...
Page 82
To configure the settings on each VMware vSphere ESXi host in the VMware vCenter using the script: Verify VMware vSphere PowerCLI is installed on a Microsoft Windows machine. Verify you have network access to the VMware vCenter server. Copy the script to a .ps1 file on your hard drive. Modify the $vcenter variable.
Restoring default settings for VMware vSphere ESXi After configuring advanced settings for VMware vSphere ESXi, if you want to discard those changes and restart the configuration process, use this procedure. Before you begin You must have access the VMware vSphere Client software. Procedure Using the VMware vSphere Client, log on to the server.
ESXi 6.5 from earlier versions of ESXi, use this task to increase the SAN boot VMFS datatstore capacity for compute hosts. Dell EMC recommended Boot LUN capacity for ESXi 6.5 to be increased to 15G from 10G to accommodate additional space for scratch.
Managing VMware vSphere VMs Increasing the disk timeout on Microsoft Windows VMs Increase the amount of time for a Microsoft Windows VM to wait for unresponsive disk I/O operations. About this task • Increase the disk timeout value to 190 seconds. VMware tools, version 3.0.2 and later sets the value to 60 seconds.
Page 86
Select the Security tab. Set the security level to the lowest setting (least secure). Click Edit Site List..., which opens in the Exception Site List popup window. Add the URLs of web-based applications. For example: https:// ip_address_of_web_based_application Click OK to close the Exception Site List popup window. Click OK to close the Java Windows Control Panel.
Managing VMware vCenter SSO for VMware vSphere 6.x VMware vCenter SSO is an authentication mechanism used to configure security policies and lock out or disable an account for VMware vSphere 6.x. Default policies do not require modification. You may have to modify policies or accounts if regulations require different policies or if you are troubleshooting a problem.
Click Yes to confirm. Managing VMware vCenter SSO default password policies Manage the VMware vCenter SSO default password policies for VMware vSphere. About this task By default, the SSO passwords expire after 365 days, including the SSO administrator password. You can modify the expiration policy to manage administrative passwords.
Page 89
Procedure Log on to the VMware vSphere 6.x Web Client on the vCenter VM or Element Manager VM using this URL account at: https://FQDN / IP:9443/vsphere-client/ Log on using the administrator@vsphere.local administrator account (username and password are case-sensitive). For credentials information, refer to Converged Systems usernames and passwords.
Backing up or restoring the VMware external PSC configuration Back up or restore the VMware vCenter PSC for VMware vSphere 6.x. About this task Maintaining a back-up of the PSC configuration ensures continued VMware vSphere access for VMware vCenter Server components. Procedure Follow the back-up and restore procedure in the VMware knowledge base article 2149237.
Enabling fault tolerance for the external PSC Enable fault tolerance on the external PSC for VMware vSphere 6.x. About this task For multiple PSCs, you can create fault tolerant pairing to provide continuous availability for VMware vCenter Server instance authentication. Before you begin Read the Providing Fault Tolerance for Virtual Machines section in the VMware vSphere Availability Guide from the VMware vSphere 6.x Documentation Center.
Managing VMware vSphere ESXi 6.0 Configuring the persistent scratch location (vSphere 6.0) When all VMware vSphere ESXi hosts have been added to vCenter, you can configure the persistent scratch location on all hosts with the tasks in this procedure. About this task Follow this procedure on each VMware vSphere ESXi host.
What to do next Configure VMware vSphere ESXi core dump collector service Configuring the firewall on VMware ESXi hosts (vSphere 6.0) Follow this task once to configure the firewall services all VMware ESXi hosts. About this task Perform this procedure on all Cisco UCS server(s) in AMP-2 M4. Before you begin You must have network access and administrative privileges to the ESXi host.
Procedure Within the vSphere client, select the host. Click the Configuration tab. Click Advanced Settings, select the type shown below for each setting. Update configuration to enable service with the following parameter updates; Refer to theLogical Configuration Survey for client specific information. Setting Value Disk.UseDeviceReset...
About this task Perform this procedure on all Cisco UCS server(s) in AMP-2 M4. Before you begin Obtain the DNS server IP information. Procedure In the VMware vSphere client, highlight the host. In the Configuration tab, click DNS and Routing. Click Properties in the upper right corner of the screen.
Page 96
Procedure Configure the core dump collector for a VMware ESXi host in either of the following ways: From the VMware vSphere CLI, type: — esxcli -server <ip_address_of_esxi_host> system coredump network set -i <ip_address_of_core_dump_collector-on-vCenter> -v vmk0 -o 6500 esxcli -server <ip_address_of_esxi_host> system coredump network set -- enable true From the VMware ESXi host, type: —...
Managing VMware VDS The section provides the most common procedures for managing an existing VMware vSphere Distributed Switch (VDS). Managing licenses This section provides an overview of how to manage VMware vSphere Distributed Switch (VDS) licenses. The VMware VDS is an enterprise feature of VMware vSphere vCenter Server 5.5 and later and requires that the VMware vSphere ESXi hosts are licensed with the VMware vSphere Enterprise Plus edition.
Page 98
The following table shows recommended settings: Edit option Field: recommended setting General Name: the name chosen for the distributed port group — Port binding: Static Binding — Port allocation: Elastic — Number of ports: 8 (increases automatically as long as Elastic is —...
Edit option Field: recommended setting Miscellaneous Block all ports: No Creating a distributed port group You can use the VMware vSphere Web Client to create and add virtual and VMKernel distributed port groups to an existing VMware VDS. After you create a distributed port group, you must configure the port group.
Page 100
About this task IPv4 addresses are supported on Vblock Systems and VxBlock Systems. Before you begin Create a VMkernel distributed port group. IPv6 is not supported on vSphere 6.5. Procedure From the VMware vSphere Web Client Home tab, under Inventories, select Networking. Right-click DVSwitch01-A and select Add and Manage Hosts.
Verify that the MTU setting is set to 1500 (NFS MTU=9000). Click OK and Finish. Repeat steps g through s for each additional VMware vSphere ESXi host to create a new network adapter. Click Next. Verify that the No Impact message appears and click Next. Review and verify the Summary results and click Finish.
From the Select network adapter tasks window, deselect Manage VMKernel adapters. Verify that Manage physical adapters is selected and click Next. Select Uplink 1 and click OK. Select Uplink 2 and click OK. Click Next. Verify that the status message displays no impact and click Next. Review the Summary results and click Finish.
Procedure Open a browser and type the following URL: https://<vCenterIP>:9443/vsphere- client You can also launch the VMware vSphere Web Client by selecting Start Menu > All Programs > VMware > VMware vSphere Web Client. The alternative launch method above does not apply to vSphere 6.5. Log on to the VMware vSphere Web Client with the administrator@vsphere.local user account (VMware vSphere Single Sign-On (SSO) account) or other administrative account with appropriate permissions.
Select the green plus (+) icon to open the New Network Traffic Rule wizard, and perform the following: For the Name, type: vMotionCOS. For Action, select Tag. Change the CoS value to 4. For VMware vSphere 6.x, change the Traffic direction to Ingress. The VMware vSphere 6.x Release Notes contain information about ingress and egress parameters.
Page 105
Migrating VM distributed port group assignments to a different switch If there are powered-on VMs on the distributed port group, migrate VM distributed port group assignments to a different distributed or standard switch. About this task This procedure is not required if there are no powered-on VMs on the distributed port group. VMs connected to the distributed port group can be powered-off to remove the distributed port group.
On the VMware vSphere Web Client Home tab, under Inventories, click Networking. Right-click DVswitch01-A and select Migrate VM to Another Network. From the Migrate Virtual Machine Networking wizard, perform the following: Verify that Specific network is selected and click Browse. Select the Source network distributed port group or standard port group and click OK.
Page 107
Before you begin • Reassign all the VMs to a port group on a different distributed switch or standard switch. Otherwise, an error occurs when you attempt to delete the VMware vSphere ESXi host from the VMware VDS. • Migrate all VMKernel ports to a different distributed switch or standard switch. •...
Page 108
From the left window, select the appropriate VMware vSphere ESXi host and select the Related Objects tab. From the right window, click Virtual Machines. Using the CTRL key, select all of the VMs. Select Actions > Migrate to open the migration wizard. Verify that Change host is selected and click Next.
Page 109
• If migrating to a standard switch: Create a new standard switch and attach at least one VMNIC as an uplink for the standard — switch. vNIC0 and vNIC1 connect to a different set of physical switches than vNIC2 and vNIC3. Do —...
Page 110
The standard or distributed switch must have the minimum support criteria: • Attach at least one VMNIC to an uplink port for a new distributed or standard switch • Create the distributed port group with the same name and VLAN ID of what is created in the existing distributed or standard switch •...
Before you begin Verify that there are no VMs, vNIC uplinks and VMKernel ports attached to the existing VMware VDS coming from each VMware vSphere ESXi host. Procedure Open a browser and type the following URL: https://<vCenterIP>:9443/vsphere- client. You can also launch the VMware vSphere Web Client by selecting Start Menu > All Programs >...
Page 112
Migrating VM distributed port group assignments to a different switch If there are powered-on VMs on the distributed port group, migrate VM distributed port group assignments to a different distributed or standard switch. About this task This procedure is not required if there are no powered-on VMs on the distributed port group. VMs connected to the distributed port group can be powered-off to remove the distributed port group.
Page 113
On the VMware vSphere Web Client Home tab, under Inventories, click Networking. Right-click DVswitch01-A and select Migrate VM to Another Network. From the Migrate Virtual Machine Networking wizard, perform the following: Verify that Specific network is selected and click Browse. Select the Source network distributed port group or standard port group and click OK.
From the Select network adapter tasks window, deselect Manage physical adapters so that only Manage VMKernel adapters is selected and click Next. Under On this switch, select the VMKernel port by selecting the VMKernel adapter and click Assign port group. If you need to delete VMKernel ports, under the VMKernel adapter list, select the VMKernel port and click Remove.
Choose one of the following: Distributed switch configuration and all port groups — Distributed switch only — In the Descriptions field, type DVswitch01-A and click OK. Click Yes to save the configuration file. Importing a backup of a VMware dvSwitch configuration Create a VMware VDS from an exported configuration file using the same switch and distributed port group configuration.
Log on to the VMware vSphere Web Client with the administrator@vsphere.local user account (VMware vSphere SSO account) or other administrative account with appropriate permissions. On the VMware vSphere Web Client Home tab, under Inventories, click Networking. Right-click the VMware VDS to be restored and select All vCenter Actions > Restore Configuration.
Related information Cisco Nexus 1000V VEM Software Installation and Upgrade Guide Creating a port profile Management settings should not be changed without Dell EMC approval. This content is for example purposes only. Procedure Log on to the Cisco Nexus 1000V VSM.
Related information Cisco Nexus 1000V Port Profile Configuration Guide Modifying the uplink port profiles Modify the trunks that carry VSM to VEM traffic, service console and VMKernel, and VM data traffic and run northbound from the Cisco Nexus 1000V Switch. Recommended VLAN numbers and IP addresses are referenced in this procedure.
To modify the UPLINK port profiles for VMware VM traffic, L3 VMotion, NFS, and VSM Layer 3 Control, type the following: port-profile type ethernet PRODUCTION-UPLINK vmware port-group switchport mode trunk switchport trunk allowed vlan 300 channel-group auto mode on mac-pinning no shutdown state enabled /* For vSphere 6.0 and later */...
• Verify the use of jumbo frames. • Obtain the IP address of the Cisco Nexus 1000V Switch VSM. Procedure Log on to the VSM. Type the following commands: configure terminal no port-profile type ethernet PRODUCTION-UPLINK copy run start Modifying vEthernet data port profiles Modify data port profiles for VMware VM traffic, L3 VMotion, NFS, and VSM Layer 3 Control.
Page 121
Procedure To modify the data port profiles for VMware VM traffic, L3 VMotion, NFS, and VSM Layer 3 Control, type the following commands: port-profile type vethernet VM-DATA-300 vmware port-group switchport mode access switchport access vlan 300 or <Customer Data VLAN number> no shutdown state enabled copy run start...
To verify the procedure, view the (VM facing) port groups in VMware VCenter. In the following example, the green icon represents UPLINK, and the blue icon represents the VM facing port group: Modifying the QoS settings Modify QoS settings on the Cisco Nexus 1000V Switch and mark the service console and VMKernel traffic with the appropriate QoS.
Perform the following: For this Converged System: Type: Unified policy-map type qos SET_COS_2 class class-default set cos 2 policy-map type qos SET_COS_4 class class-default set cos 4 policy-map type qos SET_COS_6 class class-default set cos 6 Block policy-map type qos SET_COS_4 class class-default set cos 4 policy-map type qos SET_COS_6...
Page 124
Related information Cisco Nexus 1000V Troubleshooting Guide Managing the Cisco Nexus 1000V Series Switch...
Guidelines for backing up system configuration files Backing up configuration files Back up Converged System configuration files with Vision software. As a system administrator, back up and restore Vision System Library and Converged System configuration files with Vision software. For information about performing, refer to: •...
Page 126
Because of routing requirements, you may need to add VRF management to the end of each copy command. The variable $(TIMESTAMP) included in the file name inserts the date/time into the file name when the tasks are executed. From the network device, to create the backup task, type: SWITCH# conf t SWITCH(config)# scheduler aaa-authentication username login password...
To confirm the scheduler update, type: SWITCH# show scheduler config config terminal feature scheduler scheduler logfile size 16 config terminal scheduler job name cfgBackup copy startup-config tftp://<IP_Address>/9500/config/D01-9500-01_startup_$ (TIMESTAMP).cfg copy running-config tftp://<IP_Address>/9500/config/D01-9500-01_running_$ (TIMESTAMP).cfg config terminal scheduler schedule name Daily0600 time daily 06:00 job name cfgBackup config terminal scheduler schedule name Daily1800...
Page 128
Name of the device and type to match the model abbreviation used to create the repository — sub-directory structure (for example, 3500, 3700, 4900, 7000). Procedure Log on to the device account using administrator privileges. From the network device, to create the backup task and specify commands, type: SWITCH# enable SWITCH# config t SWITCH(config)# kron policy-list cfgBackup...
To save the configuration updates, type: SWITCH# copy running-config startup-config [########################################] 100% Backing up the VMware vCenter SQL Server database Use this procedure to create backup jobs within a Microsoft SQL Server configuration. Before you begin • Confirm that the Microsoft SQL Server sa log on is enabled and a password is set for the account.
Page 130
The databases that require backup are in the System Databases (master, model, msdb) and the vcenter and vum databases appear after the Database Snapshots folder. Depending on the naming standard (client or Dell EMC), names should appear as <x>mgmtvcenter and <x>mgmtvum, where <x> is a unique identifier. The tempdb database should be excluded from the backup process creation tasks.
Page 131
Copy and paste this text into the Command area, and modify the @DIRNAME and @DBNAME variables accordingly: -- SQL Server Transact SQL script to perform database backup -- Use this script for each of the databases in the AMP. Modify the following variable -- for the shared location of the backup files –...
Page 132
Set the Starting at to 06:30:00 AM and Ending at to 06:29:59 AM. Verify that the Recurs field is set to 1 day(s). In the Daily Frequency section, check Occurs every, type 4 and select hour(s). Set the Starting at time to 06:30 AM and the Ending at time to 06:29:59 AM. In the Duration section, confirm the start date is set to the current date and No end date is selected.
Page 133
Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners. Published in the USA in January 2018. Dell EMC believes the information in this document is accurate as of its publication date. The information is subject to change without notice.
Need help?
Do you have a question about the VxBlock 240 and is the answer not in the manual?
Questions and answers