Quantcast
Channel: OpenManage Integration for VMware vCenter - Recent Threads
Viewing all 90 articles
Browse latest View live
↧

Can't update ESX hosts via Openmanage Integration for VMware

May 1, 2015, 12:18 pm
$
0
0

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.

↧
Search

ISM Ports for VMWare

May 18, 2015, 10:23 am
$
0
0

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

May 29, 2015, 10:33 am
$
0
0

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

↧

unable to clear jobqueue

June 4, 2015, 5:43 pm
$
0
0

I have tried all of these commands, the jobque continues to show Status=Running. Percent Complete=[34]

racadm jobqueue delete -i ALL

racadm powercycle

racadm jobqueue delete -i JID_CLEARALL_FORCE

racadm racreset

Please help. 

iDRAC 7, Dell R730XD, Asset # 

187538

↧

OMIVV 3.0 - "Unsupported Hypervisor" errors, can't update multiple hosts firmware on M610 / ESXi 5.5 U2

June 22, 2015, 11:55 am
$
0
0

We just updated OMIVV to 3.0 release.

We are having problems with 3 hosts in our infrastructure - all M610's running ESXi 5.5 U2 P55.  All hosts report strangely in OMIVV.

- "Unsupported Hypervisor" is reported in the "Check hosts for compliance" screen.

- We can update firmware on individual hosts, but updating multiple hosts at the cluster level does not work at all.  The firmware inventory page displays nothing.

All other features seem to work fine on these hosts and all of our M620's are not acting in the same way in OMIVV.  All firmware is quite up-to-date already on all hosts.

↧
↧

Version 3.0 on vCenter 5.5 using vSphere client

June 30, 2015, 10:51 pm
$
0
0

New vCenter 5.5 (build 2646482) latest from VMware website.

vSphere client 5.5 (of course)

Shiny new V3.0 of OMIVV

Install appliance and registered in vCenter without error.

Seems to work in the VMware web client (I'm still exploring). I can add servers iDRACs manually.

From the Win32 fat client, I don't get the wizard but I do get an empty bar in the middle of the screen with "Error #2048" down the bottom.

My client is Win7 x64 with IE10 as the default browser.

Where do I begin ???

Cheers

Ian

 

 

 

↧

Unable to Install OMSA on ESXi 4.1 U3 - on an R905

July 1, 2015, 9:38 am
$
0
0

First question- Which version of OMSA do I need for a first time installation? 

I tried every single version same errors for every version. It just wouldn't install.  I have tried in various ways as follows-  

1. ESX Host by puttying on to it. Error I get-

No bulletins for this platform could be found. Nothing to do.

Errno - 13
Description - No matching bulletin or VIB was found in the metadata.

error at the root-

Url - ./OM-SrvAdmin-Dell-Web-7.0.0-4614.VIB-ESX41i_A00.zip
Localfile - /var/cache/esxupdate/bundle8459924186783898588.zip
Message - [Errno 5] OSError: [Errno 2] No such file or directory: '/root
/OM-SrvAdmin-Dell-Web-7.0.0-4614.VIB-ESX41i_A00.zip'
Errno - 26
Description - Failed to download offline bundle .zip.

Also dropped the zip bundle at \var\cache\esxupdate, root.  

VCLI 4.1 -Error I get- No bulletins for this platform could be found. Nothing to do.

Vsphere update manager- Shows as installed and the host compliant but the ESX host doesn't show it in the installed programs. 

So superficially it looks like a OMSA version mismatch but its really not. I have now spent hours in finding the correct version and installing it. right from 6.0.0 to 7.0.0 and everything in between. exact same error for EACH version and iteration I tried. I haven't tried another server since this is the only host I can test on. need to get it working on this first.

Dell has done a good job of not publishing (or quickly taking down) any relevant information of which exact version is required and which version is the actual software and not just a patch.

Now I am out of ideas about what I am really missing.  

Can someone point me in the right direction?

PS- WHY are we still using ESXi 4.1 and and old dell R905? The question is above my pay grade... :) I inherited it and thats what we have in the environment. And I have been asked to install OMSA's latest version. The company doesnt want to pay for out of warranty Dell Tech Support.

↧

Error 2000000 with fresh install of OMIVV 3.0 and vCenter 6.0

July 6, 2015, 2:41 pm
$
0
0

We recently installed vCenter 6.0 in our lab. I downloaded the OMIVV OVF and deployed a brand new instance of the appliance. (I experimented with 2.3.0 in the past, but never got it working, so just threw all that out.) The connection to the vCenter went without a hitch, but the web client is showing an "Error 2000000" dialog whenever I click through the interface. When I used the first-time configuration wizard, I was able to enter all the passwords, but the list of hosts was empty, even though this vCenter has 8 attached. Without being able to select a host, I wasn't allowed to proceed through the wizard.

It seems like this error has been reported in prior versions, but it's slightly different in OMIVV 3.0, so I thought I should start a new thread. It says:

An unknown exception has occurred and has been logged in the extended logs.
Severity: CRITICAL
Error: 2000000
Date and time: <now>
Details:
An unknown exception has occurred and has been logged in the extended logs. If the issue continues, please restart your appliance. If this does not resolve the issue, please contact Dell Support.

Things I've tried:

- Enable and disable the web proxy settings (no change in behavior)

- Disconnected and reconnected the vCenter in the administrative interface several times

- Made sure the vCenter and OMIVV appliance are on the same network, with no firewalls between

- Re-registered the vCenter using the official FQDN, such that name -> numeric -> name results in the same name being returned

I downloaded the support bundle and looked through the logs, but didn't see anything obvious. I'd be happy to start over and upload a clean log file or files if that would help.

Any hints on where to go from here?

Joseph Jackson,
Computing Services,
Carnegie Mellon University.

↧
Search

OMIVV 3 - ISO Deployment for host iDracIP xxx.xxx.xxx.xxx was unsuccessful

July 13, 2015, 10:44 pm
$
0
0

Hi All,

Vcenter 5.5

Target is an R530 with Dual SD card.

Reference server is R530 for the Hardware profile

Hypervisor profile is ESXi 5.5u2 (Dell ISO) which is on a share on the vcenter server. Credentials checked. Account has permissions to the share.

Builds the RAID (although only RAID 1 even though custom was selected from a RAID 6 setup)

Sets the BIOS configuration

Sets the boot order

Fails the ISO.

Lifecycle log shows successful login as root using WS-MAN on the target. I also see deployment ISO service entries.

OMIVV and Vcenter are off-site but we have a 20mb link.

Where should I look ?

Cheers

Ian

↧
↧

Could not retrieve user permissions from vCenter xxxxxxx

July 20, 2015, 12:06 am
$
0
0

OMIVV 3.0

I have deployment credentials setup.

I have Connection Profile setup with credentials setup.

This was working fine and then I created another hardware profile.


How can I find more info on what is happening ?


Cheers

Ian

↧

OMIVV 3.0 & Dell R630 Bare Metal Deployment Error: Apply ISO Failed, Exception Occurred *servicetag*

July 20, 2015, 4:41 am
$
0
0

Hi,

We are trying to use OMIVV on a new deployment of Dell R630 servers with dual SD card deploying ESXi 6.

After deployment is run the server restarts but does not boot the ISO, iDRAC IP is in a different network to OMIVV but there is no restriction on communications between the iDRAC network and the OMIVV box.

Looking at the firewall no attempt is made to connect to the file share from iDRAC network, but there is a small amount of comms to the OMIVV box.

No traffic is being blocked.

This just doesnt seem to function properly at all and the information on why a failure occurred is non existent!

Is anyone else seeing these issues?

Thanks

↧

OMIVV 3.0 inventory failed for host

August 14, 2015, 11:26 am
$
0
0

Used OMIVV 3.0 to deploy a M620 host - worked fine and host was added to vCenter - now when running inventory against this host, I get the error "Inventory Failed" in vCenter - The Conenction Profile test passes for both iDRAC and host creds

Any suggestions?

↧

OMIVV 3 and ESXi host profiles

August 20, 2015, 12:07 pm
$
0
0

Does OMIVV work with Host Profiles in vCenter?  If so, how i.e. I know I can define a host profile in the Hypervisor Profile but will it get applied to a deployed ESXi host?

↧
↧

Having a big issue. I can't get my laptop to get connected to the internet

September 7, 2015, 6:48 pm
$
0
0

Hi. I'm not sure if I'm in the right place or what I'm doing! I can't get my Dell Inspiron N5110 to connect to the internet? Could somebody please try to help?

↧

Firmware Update Wizard Error

October 20, 2015, 4:48 am
$
0
0

Within the vSphere client the Firmware update wizard is failing due to the following error:

Severity: CRITICAL
Error Code: 210013
Time (Appliance server time): Oct 20, 2015 at 12:44:00
Details: Configure the firmware update repository and make sure there is a valid catalog file present

Browsing to the location of the Dell url it would appear to me as though there is a case error in the filename (linux is case sensitive). The appliance defaults the catalog  to the following location and filename:

Dell Online (ftp.dell.com/.../Catalog.xml.gz)

The appliance cannot be changed.

How can i contact or get Dell to address this?

↧
Search

OMIVV Bare Metal Deployment NFS Failure

October 22, 2015, 10:08 am
$
0
0

I am working to do bare metal esx deployments to dell servers.  Currently testing on a PowerEdge M610 blade in a M1000e chassis.  Inside the OMIVV app in vCenter it shows the host as compliant for bare metal server.  I can push the deployment and it goes through most of the steps.  It does the RAID configuration, installs ESXi.  Also use the Dell customized ESXi image for the ISO.  Then errors out and shows me the following:  

Error copying / downloading file

NFS mount failure for URL nfs:x.x.x.x/nfsstage/dell_plugin_extract/1/2/3/4/payload

I have verified the nfs share from a Linux system and it is there and mountable.  I can browse down to the nfsstage/dell_plugin_extract/1/2/3/4/ at this point the path to the cfg file no longer exists.

Any suggestions would be most appreciated as we are looking to use for a large number of new ESXi deployments.

↧

Incompatible iDRAC License

January 19, 2016, 2:16 pm
$
0
0

I have a Dell R810 that has an iDRAC 7 Enterprise license.  I had a problem with the Drac not working and had to reset the server to get it back and now when I click on the OpenManage Integration tab in my vCenter 5.5, I get the following error:

The OpenManage integration for VMware vCenter cannot manage this server because a compatible IDRAC license to support the hardware features is not present on the server.  The OpenManage integration for VMware Vcenter uses iDRAC with LifeCycle Controller for major features such as monitoring, firmware updates, and bare metal deployment.

Why is this happening all of a sudden?  I have had this server in production for quite some time now and have used OpenManage Integration before on this server before without any issues.

↧
↧

Firmware job currently scheduled not showing in firmware queue

January 28, 2016, 8:37 am
$
0
0

Dell OMI 3.0.0 on vCenter 6.0 build 3018323

Had one successful firmware patch of a Dell R720 server via the vSphere web client.  Tried another R720 using the vSphere thick client and it displayed an error and now every time I attempt to run the firmware update wizard am presented with a message saying "The following firmware jobs are currently scheduled" and to check the firmware job status from the job queue.  The only problem is that the firmware job queue shows nothing.  I went on the host's iDRAC and killed the queued jobs but that doesn't alter anything.

In the OMI log file, it has the following entries:

1) Fetching bundles from Repository succeeded

2) Fetching files from Bundle succeeded

3) An unknown exception has occurred and has been logged in the extended logs (HOW DO I LOOK AT THE EXTENDED LOGS??)

4) Task apply updates with ID xxxxx created

5) Firmware scheduled task apply updates is scheduled


Looking for a way to kill that firmware update job that I can "see" from the firmware job queue (either in the thick or web client). 


Thanks!

↧

Certificate replacement OMIVV not importing certificate chain

March 2, 2016, 11:40 pm
$
0
0

Hi, 

I'm trying to replace the https certificate for the omivv appliance by "Generate Certificate Signing request". 

I then fill out the fqdn as commonname, and sign it. 

When i upload just the .pem file, the cert-chain isn't provided and fails browser check

When i upload the .pem with the complete cert chain, the same happens, ie. no chain is presentet from the webserver.  (check with command 
openssl s_client -verify 5 -CAfile ca-bundle.crt -connect omivvserver:443  shows only one issuer

The pem file with chain with intermediary and root contains for the following sections

-----BEGIN CERTIFICATE-----
[...]
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
[....]
-----END CERTIFICATE-----
[...]
-----BEGIN CERTIFICATE-----
[...]
-----END CERTIFICATE-----

Any takers?

Brgds

Kristen

↧

DNS settings of OMIVV

March 2, 2016, 11:46 pm
$
0
0

In our OMIVV administrator console, the DNS settings has only primary listed, the secondary is "unknown". But no option to edit? 

brgds

Kristen

↧
Viewing all 90 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>