Quantcast
Viewing all 98 articles
Browse latest View live

Is Dell even supporting this product anymore?

This product is advertised as a way to simply updating your ESXi hosts and save time.

As of the last few months I've found it to be unstable and inoperable half the time.

As an example, I've never had consistent results trying to update an R710.  If I actually get to the point where I can select a bundle and initiate a firmware or driver update the product says it's is staging all the files to the iDRAC but then it never reboots into the LifeCycle Controller and actually updates anything. 

I just have a "Dell Hardware Update Task" sitting as Queued ind vCenter and the job never reboots the host and completes.  

I then have to resort to using a Repository Manager boot ISO to update anything.  What is the point of this product then?

And Dell is a no show on this forum to help.

What's going on Dell?  Are you even supporting this product anymore?


Vcenter Integration - Problem with iDRAC Enterprise on R710

Hi,

I'm trying to connect an R710 to my Vcenter Integration.

I've already connected a T610 without issue but with the r710 I can't connect to the iDRAC.

Image may be NSFW.
Clik here to view.

The plugin gets the correct IP for the iDRAC, I can see it from the logs.

Also, credentials are ok and tested, iDRAC is running on the dedicated NIC.

BIOS, iDRAC and Lifecycle Controller are at the latest version.

The OMSA Agent has been installed through VMWare Update Manager form the DELL repository

Connecting to the Openmanage appliance with readonly shows no errors on pinging both the host and the idrac using the ip address and the DNS name

What am I doing wrong?

Thank you

Dell openmanage for vmware vcenter : appliance AUTOMATIC SCHEDULED BACKUP does not work (3.1)

Hello,

I've set up the backup / restore settings and manual backup works perfectly. But automatic backup produces nothing. 

Set as enabled, 

AUTOMATIC SCHEDULED BACKUP

Edit
Information
Modify the backup schedule
Automatic Scheduled BackupsEnabled
Days for BackupSU, MO, TU, WE, TH, FR, SA
Time for Backup (24 Hour, HH:mm)12:25
Next Backup9/14/2016 12:25 GMT+2
Local TimezoneGMT+2

Nothing is produced. No error message except last backup is successful whereas there's no file in the NFS volume with the scheduled backup. 

Manual backup produces correctly the NFS backup files.

Thank you for any advise.

Regards

ESXi deployment job fails when including more than one server

Hello,

Using the deployment wizard using one single server succeed while attempting to deploy 2 ou 3 server in the same job created an apply iso failed.

Any idea ?

Regards

No plug in for vcenter web client

Using vcenter 6 and OMI 3.2.1.  The plug in showed up automatically on the thick client but does not show up on the web client.  I've verified that the extension is listed for the vcenter and that DNS entries are correct.  I've unregistered and reregistered the vcenters.  Any ideas??

Scheduling multiple firmware updates.

We recently had to update 15 clusters with a critical firmware update.  Since we cannot more than one at a time it took a long time to do the updates.  Any plans to address this issue?

Unlimited host licensing

If I get the unlimited host license, can I use it on multiple vcenter instances?

vSphere Web Client issue

Hi All

I've just installed openmanage for vcentre in a new 2-host vsphere 5.5 cluster. 

If I access OpenManage from the fat client everything is fine, I review host information, apply updates etc. 

BUT if I try to access openamange from the 5.5 web client I get "A Web server communication error occured, wait a few moments.... reboot appliance....contact support"

I've rebooted everything (hosts and all!) but this has not made a difference. Any ideas please?

Thanks


Where to find end of life support information for OMI

Can anyone point me to a url or document which describes the support lifecycle of OMI? I am looking for the general timelines in preference to a specific answer to a specific version of OMI.

Most other vendors have support information where a product is in like general support, technical support, extended support etc. ie 2 years after GA is general support. another 2 years for extended support. 4+ from GA out of all support. If not related to the release could be related to versions. ie only support back 2 versions etc.

I cannot seem to find anything of this nature on the website.

Support for ESXi 6.0 Beta with OMSA and OMIVV

I am running beta tests with ESXi 6.0 Beta 2 RC. Does anybody know if there are any special instructions to use and install OMSA and OMIVV or any special versions required. 

If OMSA and OMIVV aren't really ready is there an indication how quickly they will be after the release of ESXi v6.0 (appears to be very close)

How to programmatically determine OMIVV version

How can I programmatically retrieve the version of OMIVV (OpenManage Integration for VMware vCenter)?

This is how I would do it manually
1.Login to https://<servername>
2.From the left menu select APPLIANCE MANAGEMENT
3.Version is displayed under APPLIANCE UPDATE

There is no url under the Appliance Management hyperlink. It is a javascript action.
I would rather not have to hack all the javascript and html to find the source of the information as this could easily change in a future release rendering this hack out of date.

There is no SNMP agent
You cannot SSH to OMI

I would like to write a script to gather this information on a regular basis as part of a state of my environment management report.

How to delete old License in OpenManage Integration VMware vSphere

Hello Community,

we have a 10 seat + 10 seat licensed OMIVV Appliance latest Version. One of the two 10 seat licenses is expired. We do not want to renew, because we have only 10 hosts. Anyone know how we can delete the expired license? Normaly I wouldn't care but I read in the licensing guide that appliance updates are not possible with expired licenses installed.

Best regards,

Bjoern

OpenManage 2.3 for VMWare showing Spurious Updates For Intel NICs on R720?

Using the latest OM for VMware and System Bundle v531, my R720 server claims it needs updates to my Intel NICS.  I have version 15.0.28 as current, yet it is offering updates for both 15.5.0 and 16.0.24. If I choose either update, neither one installs.

Anyone else running into this issue?

Image may be NSFW.
Clik here to view.

vCenter 6 support?

Is there target date when vCenter 6 will be supported?

openmanage integration for vmware

Hi all, I'm new to this forum,

i have a question, is it possible for the OMIVV to have 2 nic interfaces, for some of our blades, Where the idrac is in an different VLAN then the management VLAN,

i hope this is possible


Dell OpenManage Integration for vCenter Download

Hi,

Purchased Dell OpenManage Integration for vCenter via a Reseller.  The reseller has provided the license file, but no links to download the software.

Where can I obtain the software?

OMIVV 2.3 Hypervisor Deployment - PowerEdge R730, ESXI 5.1 U3

I have OMIVV 2.3 and have created a Deployment Template with only a Hypervisor Profile for ESXi 5.1 U3 deployment.

Hardware/BIOS/iDRAC are all configured as desired.

When I run the Deployment Wizard, the job fails after the following messages in the Deployment Job Details:
-Preparing ISO for installation
-Apply ISO failed
-An exception occured: (Service Tag)

I have the ESXi ISO (Reference ISO) in the root of the CIFS share and have verified permissions to the share.

Question: Does the Deployment job power on the server or does the server need to be already powered on when the Deployment job is started?

Question: Does the CIFS connection to the ESXi ISO (Reference ISO) originate from the iDRAC's IP address?

Are there any additional logs I can review to see where this is failing? The log in the OMIVV console just says: "ISO Deployment for host with iDRACIP 1.2.3.4 was unsuccessful."

Thanks in advance for any assistance.

Can't update ESX hosts via Openmanage Integration for VMware

I'm trying to update the firmware on my ESX hosts (R720, R910, R730) via the Firmware Update Wizard in the Dell OpenManage plugin for VMware.  I created a repository using the Datacenter Repository Manager and the Dell System Management Plugin for vCenter Inventory.  I choose Update from repository and click Next.  The following error pops up:

Severity: CRITICAL
Error Code: 210013
Time (Appliance server time): May 1, 2015 at 15:15:00
Details: Configure the firmware update repository and make sure there is a valid catalog file present. Once configured, allow 10 minutes for the firmware bundles to be downloaded.

The log shows The firmware repository file does not exist or is invalid.

I've verified the path and credentials entered are correct, and the catalog.xml file exists.  I've recreated the repository numerous times, but get the same error.

Datacenter Repository Manager 1.5, Dell plugin for vCenter is 2.2.0 Build 251.  I tried upgrading the DRM 2.0, but the scan against the vCenter would never complete.

ISM Ports for VMWare

Hi Folks,

I just installed the ISM VIB and it, as planned, added the USB NIC to VMWare and set its IP correctly.

I can ping to 169.254.0.1 and can SSH to that IP and get racadm prompt.  So given that, I have no doubt communication is established between the iDRAC and the Operating System.

Yet my /var/log/syslog shows: "The iDRAC Service Module is unable to communicate with iDRAC using the OS to iDRAC Pass-through channel."

I'm thinking VMWare is blocking for firewall the communication to the proper port.  Can someone tell me which port(s) this communicates on (a minimum is preferred) so that I can enable only the ports needed to get this to communicate between iDRAC7 and ISM?

If there's suggestions other than firewall I'm happy to hear them, but seem confident on that one.

-M

OME 1.2.1 hardware reporting reliability

Hello

I am trying to reduce the number of times our datacenter staff needs to perform visual checks on our Dell servers for hardware alerts: hdd, fan, psu etc.

I am using OMSA + snmp combo for both Windows and ESXI. Server hardware is mostly a mix from 9th-12th gen. Reporting has been fairly reliable with some exceptions. One 2008R2 server was not listing any hardware alerts and the status was unknown. Logging in locally, found the DSM SA Data Manager service had quit. After starting it up, OME started getting alert data from this system. There a few other Windows 2003 servers that have unknown health but report alerts just fine.

What is the best strategy to ensure reliable alerting? I know I can set Windows to auto-restart DSM services upon failure, and probably need to do the same for snmp service. How do I accomplish similar on ESXI?

Looks like I posted in the wrong section, can someone move the posting? Thanks

Viewing all 98 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>