327 Posts

March 8th, 2013 12:00

Garia666,

Does manual installation of this DUP work on the system ?

What version of OMSA is installed ?

What is the server model and operating system installed ?

Thanks,

Raj Shresta

11 Posts

March 11th, 2013 01:00

Hi thanks for your reply,

I am using version OMSA 7.1.0

On PowerEdge M610 runnin Win 2003 R2 Enterprise Edition

I am unable to find the download with Dell repository Manager

And if i search for it manualy it tells me it is for

Enterprise Servers R720

Besturingssystemen

Microsoft Windows Server 2008 x86

Windows Server 2003  

 

I am currently using DellOnline active Catalog  ReleaseID PDFW2 Release date 21-2-2013

Please Advise

_________________

update

---------------------------

  I was able to do manual install. However Openmanage Essentials doesnt detect the manual update.. I tried doing several Discovery and inventory. but it still doesnt detect the manual installed update..

327 Posts

March 11th, 2013 09:00

In Dell repository manager, select "Create -> Dell OpenManage Essentials Repository". This process will fetch the inventory data from OME database and creates a repository based on the server models managed in OME. Have you tried this option ?

Another option to refresh inventory in OME...is to manually delete the device from "All Devices" tree and run discovery+inventory on that device. This should refresh the inventory data.

Thanks,

Raj Shresta

11 Posts

March 11th, 2013 10:00

Please read up (update part ) as i have stated before i tried installing the patch manualy.

327 Posts

March 11th, 2013 11:00

There are two different issues reported:

Issue 1: OME is unable to deploy the driver package (DUP)

Issue 2: Inventory is not getting refreshed in OME.

Issue1:

OME is able to send and copy the DUP (package) to managed node. However when applying the package it is failing with compatibility check. This is probably an issue w/ silent installation of the package based on the error snippet:

• [03/06/13 22:22:21] User Parameter: logfile changed to: c:\windows\temp\dup.log

[03/06/13 22:22:21] User Parameter: force

[03/06/13 22:22:21] (DupAPI::ValidateCommand): *** DUP Capability check failed

[03/06/13 22:22:21] DUP command not supported by this payload, display user help

[03/06/13 22:22:21] Name of Exit Code: UNKNOWN_OPTION

[03/06/13 22:22:21] Exit Code set to: 11 (0xB)

[03/06/13 22:22:21] Result: FAILURE

Issue 2:

After the update has been applied, it takes time for OMSA (Server Administrator) on the managed node to refresh inventory. You may need to wait 30 minutes and re-attempt to discover/inventory the device. If that does not work, manually delete the device in OME Device tree and re-run discovery+inventory on the discovery range.

Thanks,

Raj Shresta

11 Posts

March 12th, 2013 04:00

Issue 2 is not a an real issue as other updates are refreshed and shown correctly. I always do manual discovery after changes. However i have removed the server from discovery and re added it with the same result.

Therefor coming to issue 1.

If you look for this patch on the dell site it states its for an Enterprise R 720 server. which is strange to say atleast.

Second the patch does not show up in the Dell repository manager for any of the server types that i do administration on.

The patch only shows in OME since the last update DellOnline active Catalog  ReleaseID PDFW2 Release date 21-2-2013

After manualy downloading the package shown by OME log  @ ftp.dell.com/.../DRVR_WIN_R317417.EXE

I did an succesfull manual installation  (Changes do not show in OME ) ( double clicking package with gui )

Then i tried installation trough the commands shown by OME (system update task).

DRVR_WIN_R317417.EXE /f /s /l=C:WINDOWS\TEMP\DUP.log

however there is no /f switch ( as you can see below )

C:\Dell>DRVR_WIN_R317417.EXE /f /s /l=C:\WINDOWS\TEMP\DUP.log

C:\Dell>

Update Package: R317417

Emulex Emulex Family of Server Adapters, v.5.212.09, A01

General Usage:

DRVR_WIN_R317417.exe [/ [= ]] [/ [= ]]...

See listing below for and information.

Option - Description:

---------------------

(none) - Display of graphical user interface for guided installation/update or e xtraction.

/? or /h - Displays this Dell Update Package usage information.

/s - Suppresses all graphical user interfaces of the Dell Update Package.

/e= - Extraction of update contents to a folder.

(NOTE: Requires /s option)

/drivers= - Extraction of only driver components to a folder.

(NOTE: Requires /s option)

/driveronly - Installation/Update of the driver components only.

(NOTE: Requires /s option)

/passthrough ... - (Advanced) Sends all text following the /passthrough option d irectly to the vendor install software of the Dell Update Package. This mode sup presses any Dell provided graphical user interfaces, but not necessarily those o f the vendor software.

/capabilities - (Advanced) Returns a coded description of this Dell Update Packa ge's supported features.

(NOTE: Requires /s option)

/l= - Define a specific path for the Dell Update Package log file.

(NOTE: This option can NOT be used in combination with /passthrough or /capabili

ties)

If i do the install without the /f switch the installation will go trough.

part of dub.log

MSI (s) (9C:54) [11:48:57:294]: Note: 1: 1728 MSI (s) (9C:54) [11:48:57:294]: Product: Emulex OCManager 5.212.09 -- Configuration completed successfully.

MSI (s) (9C:54) [11:48:57:294]: Cleaning up uninstalled install packages, if any exist MSI (s) (9C:54) [11:48:57:294]: MainEngineThread is returning 0 MSI (s) (9C:C0) [11:48:57:294]: Destroying RemoteAPI object.

MSI (s) (9C:28) [11:48:57:294]: Custom Action Manager thread ending.

=== Logging stopped: 12-3-2013  11:48:57 === MSI (c) (10:20) [11:48:57:294]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after

decrement: -1

MSI (c) (10:20) [11:48:57:294]: MainEngineThread is returning 0 === Verbose logging stopped: 12-3-2013  11:48:57 ===

[03/12/13 11:48:59]

--- End of Vendor Software Log ---

[03/12/13 11:48:59] Vendor Software Return Code: 0

[03/12/13 11:48:59] Name of Exit Code: SUCCESS

[03/12/13 11:48:59] Exit Code set to: 0 (0x0)

[03/12/13 11:48:59] Result: SUCCESS

[03/12/13 11:48:59] Name of Exit Code: SUCCESS

[03/12/13 11:48:59] Execution terminated at date-time 03/12/13 11:48:59

[03/12/13 11:48:59] ######

( I could email the full dup.log if you provide me your email

If needed.)

Thanks so far for all the help .

327 Posts

March 13th, 2013 13:00

I will pass on the info regarding "/f" switch not supported in this driver DUP. For various reasons, I cannot share my email address. Please open a support case by calling this number: 800-945-3355 and they will be able to collect logs and help you further.

Thanks for root causing the issue.

-Raj Shresta

11 Posts

March 20th, 2013 07:00

They have removed the patch from OME all is fixed now

327 Posts

March 20th, 2013 10:00

Can you please clarify what patch was removed ?

Thanks !

11 Posts

March 29th, 2013 07:00

they removed DRVR_WIN_R317417.exe  for the types of server i do administrating on however they replaced it with an new one . with simmilar issues Fibre-CHannel_Driver_DRMY8_WN_6.114.03_A00-00.exe

327 Posts

March 29th, 2013 09:00

thanks for sharing the info.

No Events found!

Top