dell management plug-in for vmware vcenter 1.6 version 1.6 ... · dell management plug-in for...

Dell Management Plug-in for VMware vCenter

Version 1.6

Release Notes

Dell Management Plug-in for VMware vCenter version 1.6 Release Notes

ii

This document is for informational purposes only and may contain typographical errors and

technical inaccuracies. The content is provided as is, without express or implied warranties of any

kind.

© 2012 Dell Inc. All rights reserved. Dell and its affiliates cannot be responsible for errors or omissions

in typography or photography. Dell, the Dell logo, and PowerEdge are trademarks of Dell Inc. Intel and

Xeon are registered trademarks of Intel Corporation in the U.S. and other countries. Microsoft,

Windows, and Windows Server are either trademarks or registered trademarks of Microsoft Corporation

in the United States and/or other countries. Other trademarks and trade names may be used in this

document to refer to either the entities claiming the marks and names or their products. Dell disclaims

proprietary interest in the marks and names of others.

December 2012| Rev 1.0


iii

Contents

Introduction ........................................................................................................... 4

BIOS/iDRAC Co-requirement for Lifecycle Controllers .......................................................... 4

Hardware and software requirements ............................................................................. 5

Supported browsers .................................................................................................. 6

Space required for provisioned storage ........................................................................... 7

PowerEdge 12th generation servers .............................................................................. 7

PowerEdge 11th generation servers .............................................................................. 7

PowerEdge 10TH generation servers ............................................................................. 8

PowerEdge 9TH generation servers ............................................................................... 8

Port information ...................................................................................................... 9

User notes ............................................................................................................ 10

Open issues and resolutions ........................................................................................ 13

Corrected Problems ................................................................................................. 22

Tables

Table 1. – For Deployment ..................................................... Error! Bookmark not defined.

Table 2. – For Management ........................................................................................ 4

Table 3. – Management Support .................................................................................. 5

Table 4. Hypervisor Deployment Versions ...................................................................... 6

Table 5. Table 5 - VMware Version Support .................................................................... 7

Table 6. Table 6 - Feature Support .............................................................................. 7

Table 7. VMware Version Support ................................................................................ 7

Table 8. Feature Support .......................................................................................... 8





Table 13. Virtual Appliance ......................................................................................... 9

Table 14. Managed Nodes ........................................................................................... 9

........................................................................................... 12


4

Introduction

This file contains updated information for your Dell™ Management Plug-in for VMware vCenter and any other

technical documentation included with Dell Management Plug-in for VMware vCenter software.

NOTE: Dell Management Plug-in for VMware vCenter is available from http://www.dell.com/vcenterplugin.

The Dell Management Plug-in for VMware vCenter documentation includes:

Dell Management Plug-in for VMware vCenter Version 1.6_Dec. Quick Install

Dell Management Plug-in for VMware vCenter Version 1.6_Dec. User’s Guide

Context-sensitive help pages display by the user interface

This Release Notes file

BIOS/iDRAC Co-requirement for Lifecycle Controllers

The following BIOS, iDRAC, and Lifecycle Controller versions are required to enable Management Plug-In

features. These versions must match in order for the Management Plug-in to function properly.

Note: We recommend that you use SUU, Repository Manager, or Lifecycle Controller's Platform update

functionality to update your servers to one of these baselines before using The Dell Management Plug-in for

VMware vCenter. Upgrade these in the order listed below.

For deployment Table 1.

Version Version number/Release date

BIOS version Release date 3/21/2011 or later

iDRAC version for Dell PowerEdge 11th generation servers

3.35 for Modular, 1.85 for Rack or Tower

Lifecycle Controller for Dell PowerEdge 11th generation servers

1.5.2 or later


1.0.0.3017 or later


1.00.0 or later

For management Table 2.

Version Version number/Release date

BIOS version Release date 3/21/2011 or later


3.35 for Modular, 1.85 for Rack or Tower


1.5.2 or later


1.0.0.3017 or later


1.00.0 or later

http://www.dell.com/vcenterplugin




5

Hardware and software requirements

The following support matrix tables detail the VMware version and Management Plug-in functional support for

Dell PowerEdge 9th, 10th, 11th, and 12th generation Dell servers.

OpenManage 6.4 agent or greater - SNMP alerts, Hardware Inventory, Blink Server LED,

View/Clear SEL logs

Lifecycle Controller 1.5.2 or later - BIOS/Firmware Updates, Bare metal Deployment,

Hardware Configuration, Change Configuration Settings

iDRAC Express/Enterprise - Power On a Server, Link and Launch iDRAC

OpenManage Server Administrator (OMSA) Agent — Required for all Dell servers prior to Dell

PowerEdge 12th generation servers

The manual installation of the OMSA agent on Dell PowerEdge 11th Generation hosts is no

longer required on all ESX/ESXi hosts prior to the Dell Management Plug-in installation. The

OMSA agent is installed automatically during deployment. In addition, the Dell Management

Plug-in provides options to install OMSA as part of acquiring host compliance.

For the management, we support the following:

Management support Table 3.

Hypervisor version OMSA version

ESX 4.1 OMSA 6.5

ESXi 4.1 OMSA 6.5 VIB

ESX 4.1 U1 OMSA 6.5

ESXi 4.1 U1 OMSA 6.5 VIB

ESX 4.1 U2 OMSA 7.0



ESX 4.1 U3 OMSA 7.2





6

For Hypervisor deployment, we support the following:

Hypervisor deployment versions Table 4.

Hypervisor version OMSA version Notes

ESX 4.1 OMSA 6.5 Limited to servers with native drivers included in VMware ESX ISO

ESXi 4.1 OMSA 6.5 VIB Use the Dell Custom ISO for driver inclusion

ESX 4.1 U1 OMSA 6.5 Limited to servers with native drivers included in VMware ESX ISO

ESXi 4.1 U1 OMSA 6.5 VIB Use the Dell Custom ISO for driver inclusion

ESX 4.1 U2 OMSA/ 7.0 Limited to servers with native drivers included in VMware ESX ISO


ESX 4.1 U3 OMSA/ 7.2 Limited to servers with native drivers included in VMware ESX ISO


ESXi 5.0 OMSA 7.0 VIB Use the Dell Custom ISO for driver inclusion

ESXi 5.0 U1 OMSA 7.1 VIB Use the Dell Custom ISO for driver inclusions

ESXi 5.1 OMSA 7.1 VIB Use the Dell Custom ISO for driver inclusions

Note: Product test may at their discretion test key platforms (example, test rack only if tower equivalent

exists).

Supported browsers

Access the Administration Portal and the Dell Management Plug-in using the following browsers:

Internet Explorer 7.0.x, 8.0.x, and 9.0.x set to not use a proxy when communicating with the Dell

Management Plug-in. Make sure to set your default browser to Internet Explorer.

Note: Document Mode and Bowser Mode must be set to the right IE version. Press F12 to set them.


7

Space required for provisioned storage

The Dell Management Plug-in virtual appliance requires 36.083 GB of disk space for provisioned storage.


VMware Version Support Table 5.

Model VMware versions

T320, R320, R420, T420, M420, R520, M520, T620, R620, M620, R720, R720XD, R820, M820

ESX Classic, ESXi Installable

Feature Support Table 6.

Model Features

T320, R320, R420, T420, M420, R520, M520, T620, R620, M620, R720, R720XD, R820, M820

SNMP alerts, BIOS/Firmware Updates, Hardware Inventory, Power on server, Bare Metal Deployment, Hardware Configuration, Blink Server LED, View/Clear SEL logs, Link and Launch iDRAC, Change Configuration Settings, Warranty Information


VMware version support Table 7.


R210, R310, T410 ESX Classic

R210 II, R410, R415, R510, R515, T610, R610, M1000e, M610, T710, R710, M710, M710D, R810, R905, R910, M910, M915, R715, R815

ESX Classic, ESXi Embedded


8

Feature support Table 8.

Model Features

R210, R210II, R310, T410, R410, R415, R510, R515, T610, R610, M1000e, M610, T710, R710, M710, M710HD, R810, R905, R910, M910, M915, R715, R815

SNMP alerts, BIOS/Firmware Updates, Hardware Inventory, Power on server, Bare Metal Deployment, Hardware Configuration, Blink Server LED, View/Clear SEL logs, Link and Launch iDRAC, Change Configuration Settings, Warranty Information

PowerEdge 10TH generation servers



R200, T300, R300, M600 ESX Classic

M605, T605, M805, R805, R900, R905, M905 ESX Classic, ESXi Embedded

Feature support Table 10.

Model Features

R200, T300, R300, M600, M605, T605, M805, R805, R900, M905

SNMP alerts, Hardware Inventory, Power on server, Blink Server LED, View/Clear SEL logs, Link and Launch iDRAC, Warranty Information

PowerEdge 9TH generation servers



PE1950 I/II ESX Classic

PE1950 III ESX Classic, ESXi Embedded

PE1955 ESX Classic





PE2970 ESX Classic, ESXi Embedded

PE6950 ESX Classic

Feature Support Table 12.

Model Features

All supported PowerEdge 9th generation servers SNMP alerts, Hardware Inventory, Power on server, Blink Server LED, View/Clear SEL logs, Link and Launch iDRAC, Warranty Information


9

Port information

NOTE: When deploying the OMSA agent using the Fix non-compliant vSphere hosts link available from the

Compliance window in the Dell Management Center, the Dell Management Plug-in starts the httpClient service

and enables port 8080 on and releases after ESXi 5.0 to download OMSA VIB and install it. Once the OMSA

installation is completed, the service automatically stops and the port is closed.

Virtual appliance Table 13.

Port Number

Protocols Port Type Maximum Encryption

Level

Direction Usage Configurable

21 FTP TCP None Out FTP command client

No

53 DNS TCP None Out DNS client No

80 HTTP TCP None Out Dell Online Data Access

No

80 HTTP TCP None In Administration Console

No

162 SNMP Agent

UDP None In SNMP Agent (server)

No

443 HTTPS TCP 128-bit In HTTPS server No

443 WSMAN TCP 128-bit In/Out iDRAC/OMSA communication

No

4433 HTTPS TCP 128-bit In Auto Discovery No

2049 NFS UDP/TCP None All Public Share No

4001-4004 NFS UDP/TCP None All Public Share No

5432 Postgres TCP 128-bit All PostgreSQL No

11620 SNMP Agent

UDP None In SNMP Agent (server)

No

Managed nodes Table 14.

Port Number


Level


162, 11620 SNMP UDP None Out Hardware Events No

443 WSMAN TCP 128-bit In iDRAC/OMSA communication

No

4433 HTTPS TCP 128-bit Out Auto Discovery No

2049 NFS UDP None All Public Share No

4001-4004 NFS UDP None All Public Share No

443 HTTPS TCP 128-bit In HTTPS server No

8080 HTTP TCP In HTTP server; downloads the OMSA VIB and fixes non-compliant vSphere hosts

No

50 RMCP UDP/TCP 128-bit Out Remote Mail Check Protocol

No


10

Port Number


Level


51 IMP UDP/TCP None N/A IMP Logical Address Maintenance

No

5353 mDNS UDP/TCP All Multicast DNS No

631 IPP UDP/TCP None Out Internet Printing Protocol (IPP)

No

69 TFTP UDP 128-bit All Trivial File Transfer

No

111 NFS UDP/TCP 128-bit In SUN Remote Procedure Call (Portmap)

No

68 BOOTP UDP None Out Bootstrap Protocol Client

No

User notes

Dell Management Plug-in for VMware vCenter only supports BIOS mode to auto-deploy

hypervisor on the target server. Make sure that you have BIOS mode selected in the reference

hardware profile prior to applying the Hypervisor profile. If there is no hardware profile

selected, then make sure to manually configure the boot mode as BIOS and reboot the server

prior to applying the hypervisor profile.

After the deployment of ESXi finishes, the server shows a purple screen as shown below with

the error “Two file systems with the same UUID have been detected. Make sure you do not

have two ESXi installations.”


11

This is a known issue from VMware and the resolution is in the VMware knowledge base article

found here:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&ex

ternalId=2000476

or here:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&ex

ternalId=1035107

Incorrect warning is displayed on the VCenter Summary tab when the hypervisor was deployed

and root password set to non-default as shown in the screen below.

This is a known issue from VMware and the resolution is to remove the host from the VMware

tree and re-add it back with the correct root password.

Incorrect warning is displayed. Figure 1.

Time stamps are converted to the user’s local time zone and the Dell Management Plug-in

displays Coordinated Universal Time (UTC) time offsets.

If you run a security scanner tool (such as Nessus) against the Server Administrator Web server,

certain security warnings against port 1311 running the Server Administrator Web server may

be displayed. These warnings have been investigated by Dell engineering and are determined

to be false positives.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2000476





12

If the proxy settings are provided in the configuration, then the proxy settings are used to

access the Repository URL provided in the Administration Portal. However, if the URL to the

Update Repository is an internal URL, then disable the proxy setting. If you do not disable the

internal proxy setting, then the appliance attempts to connect to the URL with the proxy.

A hardware profile created using a reference server with a certain BIOS version could cause

deployment to fail. Some BIOS versions do not give accurate information for certain BIOS

settings, such as the Embedded NIC1 and NIC2 settings. When a server with BIOS version is

used as a reference server in a hardware profile, the fields are ignored both by the UI and by

deployment. A problem could arise, however, if the settings in question are required to have a

certain value for deployment to complete successfully.

The solution to this issue is to use a server with an up to date BIOS as a reference server for a

hardware profile.

Note: Servers being used for deployment should also have updated BIOS. If deployment tries

to apply settings to a server with problematic BIOS, deployment fails. Currently the BIOS

version is not checked for compliance, but it is displayed on the server compliance page.

Warnings are displayed on the hardware profile reference server and BIOS settings pages, as

well as when they select a deployment template with an affected hardware profile during

deployment.

To resolve this issue, use one of the following BIOS versions:

BIOS versions

Model BIOS

R710, T610, R610, M610/ M710/ M610x, T710: 6.1.0

M710HD: 5.0.1

M910: 2.5.0

M915: 2.6.0

R210: 1.8.2

R210II: 1.3.1

R310,R110,T310: 1.8.2

R410,T410: 1.9.0

R415,R515: 1.8.6

R510: 1.9.0

R715,R815: 2.3.0

R810,R910: 2.5.0


13

Open issues and resolutions

The following section lists the open issues and resolutions with the Dell Management Plug-In for VMware

vCenter 1.6:

Issue1: Invalid time format for Automated Backup settings in

Administration Portal.

Description: Backup scheduling fails if the backup scheduling is performed in

the month of December. This is happening due to incorrect date-time

formatting.

Resolution/Workaround: Avoid scheduling the backup activity in December.

You can manually perform backups for the month of December. Schedule the

backup activity after the month of December.

Version Affected: All

Issue 2: NPE is thrown when trying to register the Dell Management Plug-in.

Description: The registration of Dell Management Plug-in fails after upgrade to version 1.5.1 even if there is no

earlier Dell Management Plug-in registered and the vCenter locale is one of the supported locales. The issue

happens since some SQL scripts failed to execute during RPM update.

Resolution/Workaround: It is recommended that you take backup before performing any RPM

upgrade. Install the previous version of plugin prior to the upgrade and restore the DB. Now repeat the

process of upgrade using RPM upgrade.

Version Affected: 1.5.1 and later

Issue 3: The RAID topology does not support a dedicated hotspare in the reference topology and also does

not support a dedicated hotspare while applying a hardware profile.

Description: Raid Topology does not support a dedicated hotspare in the reference topology and also does not

support dedicated hotspare while applying hardware profile.

Resolution/Workaround: If you need a dedicated hotspare in reference topology, set up the RAID outside of the

Dell Management Plug-in.



14

Issue 4: Firmware download fails when trying to downgrade firmware from Q4 block

release.

Description: The firmware downgrade will fail sometimes if the user is trying to downgrade LC,

IDRAC and other firmware at the same time.

Resolution/Workaround: downgrade LC first and then downgrade the rest of the firmware

once LC firmware downgrade is completed.

Issue 5: Connection profile association not shown in host compliance page when inventory is not

able to get iDRAC IP for the host.

Description: If while running inventory, the iDRAC is non-responsive and it is not able to get iDRAC

IP, the inventory will fail and on the host compliance page the host is shown as not associated with

the connection profile.

Resolution/Workaround: Reset the iDRAC to fix the issue of iDRAC not being responsive and then

rerun the inventory. If the inventory is able to get the iDRAC IP, then the host will be associated

with the correct connection profile.

Version Affected: 1.6

Issue 6: A Communication Error Message is displayed after clicking the Firmware link from vSphere Client. Description: If you have a slow network speed (9600BPS), you may get a Communication

Error Message as shown below after clicking on the Firmware link in vSphere Client for the

Dell Management Plug-in. The Communication Error Message is caused when the connection

times out (which was initiated by the Microsoft Internet Explorer) while trying to obtain the

Software Inventory list. For Microsoft Internet Explorer 8/9/10, the default “Receive Time

out” value is set to 10 seconds.

Resolution/Workaround: Use the follow steps to fix the issue:

1. Open RegEdit. 2. Navigate to the following location:

KHEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings. 3. Add a new DWORD value for ReceiveTimeout.


15

4. Set the value to 30 seconds (30000) [This may need to try higher value in your environment]. 5. Exit RegEdit. 6. Restart Internet Explorer.

Note: Just opening a new Internet Explorer window is not enough. You must restart the Internet Explorer browser.

The error that displays when the value is set too low is:

Version Affected: 1.5 and later.


16

Issue 7: After deploying ESX 4.1u3(800380), OMSA is not configured. Description: ESX 4.1 base, U1, U2, and U3 all require SSH to be enabled on Dell PowerEdge

11th generation servers at the time when inventory is run to determine if the OMSA is

configured correctly.

If Dell Management Plug-in was used to deploy ESX 4.1 base, u1, u2, u3, it installs and

configures OMSA correctly. However, since SSH is not enabled, it shows the host as Not

configured on the host compliance page. In addition, if ESX 4.1 was installed outside and

OMSA was installed and configured using Dell Management Plug-in, and then the user turned

off SSH later, the host shows as “Not configured.” The system must have SSH enabled to

show the correct status.

Resolution/Workaround: Either the user has to ignore the wrong status or keep SSH enabled

at all times.

Version Affected: 1.5 and later.

Issue 8: Deployment with IPV6 enabled may add host to vCenter with IPV6 address. Description: If an IPV6 address was used to add the host to the vCenter, then the inventory

will fail on that host.

Resolution/Workaround: The workaround is to remove the host from the connection

profile, remove the host from the vCenter tree, then add the host back to the vCenter tree

using the hostname, and then add the newly added host to the connection profile.


Issue 9: Using localhost for hostname causes problems identifying the source of SNMP alerts.

Description: Starting with ESXi 5.1, a value of localhost for the hostname causes problems in

identifying the source of SNMP alerts. The use of localhost is not supported and a Fully Qualified

Domain Name FQDN should be used instead.

Resolution/Workaround: When deploying an ESXi 5.1 server using DHCP, it is strongly

recommended that a combination of a DHCP reservation based on the selected NIC MAC

addresses, and a DNS host entry using the reservation’s IP address be configured. The MAC address

is visible from the Deployment Wizard’s Server Identification screen, Network Interface drop-

down, and provided to help identify the network interfaces. The DHCP reservation and DNS entry

should be created for the server prior to scheduling the deployment, and if properly configured

should set the hostname to the value from DNS.



17

Issue 10: Balloon driver or vMotion is not functioning as expected.

Description: VMware tools are out of date causing potential issues like the balloon driver or

vMotion not to functioning as expected.

Resolution/Workaround: Tools can be updated by powering the virtual machine down and

changing the virtual machine type to Linux/Centos 32 bit. Once the virtual machine comes

back online do an automatic upgrade of the tools. Detailed steps are located at our tech

center site:



Issue 11: Deployments failure error message seen on R210 II machines.

Description: Timeout issue on R210 II systems produces a hypervisor deployments failure

error due to failure of BIOS to boot from attached ISO.

Resolution/Workaround: Manually install hypervisor on the machine.

Version Affected: 1.5.1, 1.6

Issue 12: Dell Management Plug-in gets a security error message.

Description: Although the SSL Certificate is valid on a vCenter and user credentials are correct, a

user encounters an error message saying , “There are either too many Virtual Management Console

connections or an incorrect user name or password or session ID, or an incorrect SSL certificate.

Please verify these items and try again.”

Resolution/Workaround: This happens due to an invalid session in vCenter. Simply closing and re-

opening the vSphere client resolves seeing this error message. You can check your session by clicking

“Sessions” under Administration in the vSphere Client for advanced troubleshooting.



18


Issue 13: Unable to boot to service partition while deploying OS ISO.

Description: Hypervisor deployments are failing on Dell 11th and 12th generation servers with this

error displayed on the screen during POST: “Warning: Unable to boot to Service Partition.” There

is a BIOS issue to identify the network ISO when there is a local USB CD-ROM installed on the system

and that USB CD-ROM is the only USB mass storage device plugged into the system.”

Resolution/Workaround: Remove the local USB CD-ROM (note that not all local CD-ROM would

expose this issue), or plug in additional USB floppy or USB key on the system, or attach the virtual

media (virtual floppy and virtual CD) from the iDRAC.


Issue 14: A firmware update fails with an error message saying that USC is in use and it should be

retried after 30 seconds.

Description: During a firmware update if the update fails with error message “If USC is in use,

wait until USC has exited and retry the action. Otherwise retry after 30 seconds to check if

network connectivity caused this error.”

Resolution/Workaround: To fix this issue, reset iDRAC and wait until iDRAC boots back up

properly and try the firmware update again.


Issue 15: Events from different vCenter posted to another vCenter from a shared Dell Management

Plug-in Appliance.

Description: This situation can occur when a bare-metal server that was deployed in one vCenter is

rediscovered again as bare-metal server but then selected for a hypervisor deployed in another

vCenter.

This situation occurs if the host that was already on one of the registered vCenters was added to

another registered VCenter. In this case the host on first vCenter appears as disconnected.

Resolution/Workaround: Remove the host from the first VCenter where it is now showing as

disconnected.



19

Issue 16: The inventory ran and failed after servers were removed from the connection

profile.

Description: The Inventory attempted to run after servers were removed from the connection

profile and failed.

Resolution/Workaround: If an inventory job is started, and hosts are removed from the

connection profile, then this issue appears. The system needs to make sure the inventory job is

finished or that no Inventory job is running when hosts are removed from Connection Profile.


Issue 17: The NIC selected as the management NIC during the deployment process is not the

active management NIC after deployment.

Description: During the ESXi 5 deployment using any NIC other than NIC 0 may show up in

vCenter after deployment as the standby NIC with NIC 0 as the primary management network

NIC.

Resolution/Workaround: Manually reconfigure management NICs in vCenter after

deployment.


Issue 18: Rarely, an ESXi 4.1 U1 deployment fails on a PowerEdge server.

Description: The ESXi deployment log shows failure installing OMSA.

Resolution: This is a known VMware issue and VMware has provided a workaround to resolve the issue

as seen here:


037190

Use these steps for a workaround:

- Logon to ESXi 4.1 U1.

- Manually create a directory /tmp.

- Logoff from the ESXi host.

- Manually add the host to vCenter.

- Go to Host Compliance page of Dell Management Center.

- Run the Compliance Check wizard.





20

Issue 19: On an R515, R815, or other AMD based Dell hardware, inventory is running continuously.

Description: OMSA may malfunction on certain AMD chipsets when not upgraded to the latest version.

Resolution: To resolve this issue, upgrade to the latest version of ESX or ESXi and install the latest

version of OMSA available.


Issue 20: A non-compliant server shows a CSIOR status as Unknown.

Resolution: An unknown CSIOR state indicates a non-responsive iDRAC on the host. A manual iDRAC

reset on the host fixes this problem.

Version Affected: 1.5, 1.5.1, 1.6

Issue 21: The Launch OMSA link does not work in the vSphere Client Dell Tab when using Dell

PowerEdge 12th generation servers.

Resolution: Install OMSA manually onto Dell PowerEdge 12th generation servers, then the Launch OMSA

link will work.


Issue 22: Hypervisor installation fails.

Description: Hypervisor installation fails with the error The Job check status with ID of

DCIM_OSConcreteJob:1 failed with the following error message: Mount network share failed – incorrect IP

address or share name.

Resolution: Restart the appliance.


Issue 23: NFS mount remains mounted after deploy is completed using ESXi5.

Description: : After the hypervisor deployment is completed and the host is added to the VCenter tree,

there is an entry in the Summary page under the data sources called remote-install-location (inactive)

(unmounted) for the new host added.

Resolution: None.



21

Issue 24: The Memory reported is in a different format between Dell PowerEdge 11th generation

servers and Dell PowerEdge 12th generation servers.

Description: When memory is displayed in a table, they amounts display differently between Dell

PowerEdge 11th generation servers and Dell PowerEdge 12th generation servers.

Resolution: None.


Issue 25: Details for tasks are not recorded in the task history.

Description: Details for tasks are not recorded in the task history.

Resolution: This is a known VMware issue; go to the Dell Management Center Plug-in logs to view

the details.

Version Affected: 1.0, 1.0.1, 1.0.1 Update 1, 1.5, 1.5.1, 1.6

Issue 26: When using the user interface and pressing <ENTER> while on a highlighted button does not

always activate the action.

Description: Using keyboard navigation and selecting highlighted buttons and pressing <ENTER>

sometimes does not activate the button. Keyboard navigation is not supported at this time.

Resolution: Use the mouse.


Issue 27: The ESXI install leaves behind a file after installation.

Description: The ESXi install leaves behind a temporary file in the /store/resolv.conf (static IP only).

Resolution: None, there is no impact to the functionality of the software.


Issue 28: Dell Management Center EXE file shows Unknown for Publisher.

Description: When you right-click on the executable file, no publisher (vendor name) is displayed.

Resolution: None



22

Corrected Problems

The following problems were reported in earlier releases of the Dell Management Plug-In and have been

corrected in this release:

Bug number Issue Description

TFSID:2825 Issue 1 Could not access vCenter using the fqdn or dns short name

TFSID:2506 Issue 2 NullPointerException is thrown during the Deploymnent Minimal ISO if eth0 is missing

TFSID:2597 Issue 3 Perc H700 RAID controller is not listed for FW update using repository method

TFSID:3330 Issue 4 Dell Management Plug-in for vCenter Product Page for Chinese is not functional

TFSID:3641 Issue 5 R810, Broadcom NetXtreme II FW missing from ftp.dell.com

TFSID:3642 Issue 6 R810, PERC H700 FW update not listed with local report.

TFSID 3593 Issue 7 A user saw a message saying that there was a missing or

expired 11th generation server license.

TFSID 2385 Issue 8 Custom Raid Configuration from UI is misleading.

TFSID 2281 Issue 9 Hardware Profile for iDRAC/network settings has incorrect modifiable parameters.

TFSID 1284 Issue 10 The Connection Profile of vCenter selected in Hypervisor Profile is not used for Deployment.

TFSID 2306 Issue 11 When clicking on the Dell Server Management Tab or the Dell Management Center icon, the Dell Management Plug-in throws an error saying the given vCenter <xyz> is not registered to the Dell Management appliance.

dell management plug-in for vmware vcenter 1.6 version 1.6 ... · dell management plug-in for...

Documents