Quantcast
Channel: Dell OpenManage Essentials - Recent Threads
Viewing all 2627 articles
Browse latest View live
↧

system updates fail

June 19, 2017, 12:10 pm
$
0
0

I have installed OME and OMSA on servers.  I can sign into OMSA on the server with my admin credentials.  every time I try to a system update on the server it fail with the following message even though the credentials work with OMSA.  

Results: Timeout was reached for obtaining the software update status from the target device. Please verify the credentials specified are valid and you can still connect to the device and re-run the inventory to determine if the update was successful.

what is wrong or what am I missing?

↧
Search

Missing updates

June 20, 2017, 8:01 am
$
0
0

Have a new implementation of OME 2.2 .  Ran updates through last night via system update which worked fine, but spotted that its missed some updates.

Server in question (T330 with a Perc H730) has 4 x ST600MP0005disks on VT31 firmware, but dells website tells me that VS0B should be applied instead.

The server (and none of my other servers now that I look) are not showing required updates for PSU either - which I know is also available.

Anyone had similar issues in the past?

↧
↧

OME configuration failing for iDRAC8

June 21, 2017, 8:49 am
$
0
0

I have eight blades (six FC630s across three FX2 chassis, two M630s in a VRTX chassis) all running the Dell ESXi 6.5 image, and I'm running into issues getting OME to create a configuration template for any of them.

I successfully created chassis templates and associated them to all of the chassis, but when I try to create a server template for any of the blades I receive:

Extracting XML from target: ($dracIP)
Protocol failed to execute commands on target $dracIP with error: Could not find a description for error #80338043

Failed to get the server config file from the target $deviceName.

I receive the same error if I try to run a Configuration Inventory, and hardware logs are not pulled either. The devices are discovered both as RAC and ESX Servers, hardware inventory (Mem/CPU/etc) is correctly populated on the Device Details tab.

I've removed the device & discovery range and bumped the WSMAN timeout up to 120s as suggested in previous posts, but that had no effect. Using the Troubleshooting utility to test WSMAN communication appears to succeed, it connects & displays 33 supported WSMAN profiles after warning about the TLS1.0 handshake failing, but the OME server runs 2012R2 & the devices are successfully discovered so that doesn't seem to be the problem.

↧

OME 2.3?

June 27, 2017, 12:23 pm
$
0
0

The form one fills out to download OME says it's for version 2.3.  If you fill out the form, you get a download button.  You click the download button and are presented with a page stating the file you seek cannot be found.

Is 2.3 available or not?

↧

OME 2.2 - iDRAC 8 - firmware update fail

June 28, 2017, 1:50 am
$
0
0

Dears,

I currenlty got the problem that I cannot update the firmwares of a iDRAC 8 server using the out of band update feature of OME.

here the "Error" I get:

27.06.17 11:09:18      Using iDRAC IP address:xxx.xxx.xxx.xxx
27.06.17 11:09:18      Verifying Connectivity/Credentials
27.06.17 11:09:21      Verifying Connectivity/Credentials: A security error occurred
                Check the following: Credentials entered are valid, iDRAC is reachable from OME host and iDRAC is in a good state.
27.06.17 11:09:21      Software Update Task Failed.
27.06.17 11:09:21      Inventory will be triggered approximately after 20 minutes and expected to complete in 3-4 minutes.

As you can see there is no error but it does not work.

Here the result of the wsman troubleshooting tool:

Using TLS 1.0 for SSL/TLS handshake.
Error: A complete request could not be sent to the remote server.
Using TLS 1.1 for SSL/TLS handshake.
TLS 1.1 Handshake successful.

The WS-Man target has TLS 1.1 enabled. If OME is unable to discover this device, install the required updates on the system where OME is installed. For more details, see “Enabling support for TLS 1.1 or 1.2” at delltechcenter.com/ome.

Connected.
WSMAN profiles found on the remote device are:
1. Profile Registration
2. Base Metrics
...

here the result of the joblist command:

winrm e cimv2/root/dcim/DCIM_LifecycleJob -u:user -p:pass -SkipCNcheck -SkipCAcheck -r:xxx.xxx.xxx.xxx/wsman:443 -auth:basic -encoding:utf-8


DCIM_LifecycleJob
    ElapsedTimeSinceCompletion = null
    InstanceID = JID_CLEARALL
    JobStartTime = TIME_NA
    JobStatus = Pending
    JobUntilTime = TIME_NA
    Message = NA
    MessageArguments = NA
    MessageID = NA
    Name = CLEARALL
    PercentComplete = 0

On the server is in addition an custom CA SSL certificate installed, maybe this causes the problem?

I checked the OME with a IDRAC7 server with the default DELL SSL certificate and there everything works fine.

Best Regards,

Guy

↧
↧

Install Windows Server 2012 R2 Update (KB2919355) before installing or upgrading to OpenManage Essentials 2.3

June 29, 2017, 3:37 am
$
0
0

Hi OME Users,

For new installation or upgrade to OpenManage Essentials version 2.3 on systems with Windows Server 2012 R2 operating system, “Windows Server 2012 R2 Update (KB2919355)” is a critical prerequisite.

“Windows Server 2012 R2 Update (KB2919355)” is a cumulative set of security updates, critical updates and updates (6 Microsoft KBs). The other critical pre-requisites for OpenManage Essentials like Microsoft Visual Studio Runtime 14.0, .net Framework 4.6.2, Microsoft Silverlight 4.6.2 require “Windows Server 2012 R2 Update (KB2919355)” installed in the system.

Required action:

Download and install “Windows Server 2012 R2 Update (KB2919355)” manually from www.microsoft.com before installing other pre-requisites on Microsoft Windows 2012 R2 system.

The missing prerequisites will not be installed by clicking Install All Critical Prerequisites, until the KB2919355 is installed and available in the OS. The following message is displayed: You must install KB2919355 before installing all other critical prerequisites.

For more details about the prerequisites and best practices around installation/upgrade, refer the latest whitepaper – “Installing Dell EMC OpenManage Essentials (OME) (v2.3)” located at OpenManage Essential TechCenter page.

Thanks,
Vijay.

↧

OpenManage Essentials version 2.3 launched with lot more exciting features addressing suggestions/requests by our users

June 29, 2017, 4:04 am
$
0
0

Hi OME Users,

We are excited to announce the launch of OpenManage Essentials version 2.3. For the complete list of features and enhancements in version 2.3, please visit OpenManage Essential TechCenter page.

Also, there are new whitepapers available which explains about these new features and use cases in detail. Listing few of them below:

  • Dell EMC OpenManage Essentials – SNMPv3 Support (v2.3) (NEW)
  • Dell EMC OpenManage Essentials – Device Support (v2.3) (NEW)
  • Managing Modular Infrastructure by using OpenManage Essentials (OME) (v2.3) (NEW)
  • Editing and Deploying Server Template by using Dell EMC OpenManage Essentials (OME) (v2.3) (NEW)
  • REST API for Interfacing with OpenManage Essentials

 We will be glad to hear the feedback from you here.

Thanks,
Vijay.

↧

OpenManage Mobile wiki (Abhijit P) "Viewing OS from mobile client."

June 29, 2017, 1:47 pm
$
0
0

I was on the OpenManage Mobile wiki. The question I wanted answered was whether or not the Mobile client would make a feasible outright replacement for KVM switches in the data center. Anybody out there using only the mobile client? And do you find it an adequate replacement? Or do you wish you also had a traditional KVM solution?

On wiki page, which seems to be maintained by :

en.community.dell.com/techcenter/systems-management/w/wiki/4965.openmanage-mobile?newtab=true

I saw a reference on how the mobile client can access the desktop, but it said: "Note: This needs a Third-Party app download from Apple App Store or Google Play Store."

Abhijit, could you please name the app instead of making a vague reference to it? 

Also I have seen multiple references on Dell's web site on supported platforms. One reference said only Android is supported. Another reference on a different Dell web page said IOS is now supported.  

It would be nice if new developments triggered somebody on the Dell team (Abhijit?) to go back and update any reference to out of date information.

↧
Search

Closed Network Updates

July 3, 2017, 9:49 pm
$
0
0

Hi All,

I have a few questions regarding the above I currently have OMSA Essentials running on a file share server  

  1. Is it possible to update field devices when on a closed network?
  2. I noticed that you can create an offline folder that you can point as your catalogue is the process automated for field device updates and dell tech centre updates ? 
  3. Is there a proffered process or manual for closed network setups?

↧
↧

SupportAssist Enterprise for OME not adding devices

July 5, 2017, 7:54 am
$
0
0

Hi, I recently upgraded OME 2.2 to 2.3 and with that upgrade, it installed SupportAssist Enterprise.  Since the upgrade, a few devices are showing up in SupportAssist as "Unable to add device"  I have tried to re-validate the device, change creds, even remove them from OME and re-add them after some syncs between OME and SupportAssist and nothing seems to work.  Looking at the logs, I see it cannot find any open ports during it's "port scan" from the validation process, but SupportAssist and the DRACs it is having issues with are on the same subnet so can't be a firewall issue.  At a loss here at this point, any help would be appreciated.  Below is a snip-it from the log.

05 Jul 2017 09:18:54,360 [SAE-PortScan-Queue-Processor-1] ERROR com.dell.supportassist.did.consumer.PortScanConsumer- 111 - Port scan failed for device with address bil-logodb2-02-drac

05 Jul 2017 09:18:54,361 [SAE-PortScan-Queue-Processor-1] ERROR com.dell.supportassist.did.consumer.PortScanConsumer- 114 - Error code : SA-17005 Reason: Required Ports are not opened for Device -10.5.3.69

05 Jul 2017 09:18:54,419 [pool-8-thread-45] ERROR com.dell.supportassist.did.websocket.handler.AddDeviceHandler- 105 - portScanFailed for deviceid:1498849479511|449239391588367935 with error Code:SA-17005

↧

iDRAC Service module showing unknown

July 7, 2017, 2:45 am
$
0
0

We installed OME in our test environment and added two 13 gen Dell servers with Windows Server 2012R2 to play with.

The problem we have is that iDRAC Service Module shows as unknown (gray question mark rectangle) for both our servers in OME. I've re-run inventory and discovery, as well as status refresh, but it still stays the same. 

The service is running on both servers and everything else regarding iSM seems normal, but I am not sure what to think of this.

Thanks,

Niksa

↧

I can't install open essential on Windows 2016

July 8, 2017, 6:25 am
$
0
0

I just installed Windows 2016 and tried to install open essential but I can't install open essential due to below error message.

-One or more mandatory prerequisites for Essential are pending. Installation cannot continue. Run the Pre-Requisite Check for details.

How do I resolve this problem to install the open essential?

I installed Windows update and installed prerequisites.

and I got two information when I install the Open essential essential but actually there is enough space over 200GB free size.

- You will not be able to install Essentials in the volume where free disk space is less than 1GB. Please refer Essentials user guide for recommended hardware configuration. 

- See Readme_essentials.txt for information on operating system updates and other pre-requisites for the proper functioning of Essentials. It is critical to apply these updates to the system. Click here to launch Essentials Release Notes

↧

Discrepancy Between Systems Update Summary and System Update Compliant Lists

July 10, 2017, 10:24 pm
$
0
0

Howdy,

There are two servers in my OME that are not showing up in the list of compliant\non-complaint devices.  These two servers were originally showing up as non-compliant.  I applied all outstanding updates to them (and verified success of the updates from the task logs).  The servers disappeared from the non-compliant list, but did not re-appear in the compliant list (or the non-inventoried list).

The two servers do appear in the main device list and are accounted for in the system update summary page (pie chart shows correct number of compliant systems if you include the two missing servers).

I have re-run discovery and inventory on the servers.  I have rebooted them and re-run discovery and inventory again.  The two servers show correct system inventory versions (from their respective Server Administrator applications).  I have rebooted OME server and re-run inventory again.

Overnight, the two servers showed up on the non-inventoried list (discovery and inventory run automatically nightly).  I am not sure why the automatic process made them show up and the manual process did not.   I manually initiated an inventory task on the two servers.  They promptly disappeared from the non-inventoried list and did not re-appear anywhere else.

OME Version 2.3

Server 1: PE R620, iDRAC7 & Lifecycle 2.41.40.40, BIOS 2.5.4, OMSA 8.5

Server 2: PE M610 Blade, iDRAC6 3.80, Lifecycle 1.7.5.4, BIOS 6.4.0, OMSA 8.5

I have updated other servers of identical hardware specs around the same time as these two servers and all have behaved as expected in OME.  These are the only two with this problem.

Any help would be appreciated.

↧
↧

OME Alert unfounded?

July 11, 2017, 7:53 am
$
0
0

I keep getting the following alert on one of my host servers but cannot determine what is causing it (if anything) or if OME is sending a false/positive alert.

Device:vmhccb3, Service Tag:Asset Tag:Unknown, Date:7/11/2017, Time:09:26:51, Severity:Critical, Message:Assert + Cable/Interconnect Config Error, Severity: Fatal, System: 4c4c4544-0046-5310-8056-b6c04f503232, Provider: RawIpmiProvider

This server is not crashing nor do the logs that I have looked at indicate anything FATAL is happening.

Any help or ideas greatly appreciated!

KBeau

↧

Packages Purpose

July 13, 2017, 2:51 pm
$
0
0

Hi,

When doing updates in OME, two packages keep showing regularly in Updates to Apply:

1. Dell 32 Bit Diagnostics

2. Dell OS Drivers pack.

Do either of these actually affect/update any hardware components or are they just software repositories stored on the client server & if so where?

Thx,

John Bradshaw

↧
Search

OME install error

July 14, 2017, 1:10 am
$
0
0

Hi,

I uninstalled OME 2.2 & now when I need to install OME 2.3 or 2.3 now getting error "Dell openmanage essential console port '2607' is either blocked or consumed by another application.

Running on T420 server with OS Windows server 2012 standard .

↧

Devices not appearing in System Update

July 17, 2017, 3:27 am
$
0
0

Have over 100 boxes discovered and inventoried fine.

Upgraded to 2.3 this morning.

Now, with 2 of our devices which were non-compliant last week & we were working on, they neither appear in compliant or non-compliant windows in OME.  I forced an inventory, switched to the compliant window, saw the server briefly appear (for a second or so) then it disappeared before I had chance to click it. Didn't make it to non-compliant or the non-inventoried window.

No errors in the tasks that I can see. 

Anyone else having this issue - or suggestions for a fix please?

ta

Ash

↧
↧

OME 2.3 Error when importing Latest Catalog for System Update

July 17, 2017, 7:44 am
$
0
0

I have OME 2.3 installed on Windows Server 2016.  When trying to download the latest Catalog for System Update it just spins over and over and never actual downloads the latest catalog file.

Any suggestions??

↧

OME 1.3 to 2.3 upgrade

July 19, 2017, 12:01 am
$
0
0

Hi all,

We have been running version 1.3 since release and have been unsuccessful previously with version upgrades to 2.x (2.0.1 & 2.1). Whenever this was attempted there was database corruption and OME itself was unusable. Our only option was to restore an image of the server taken prior to the upgrade.

The staff member who used to manage OME left quite some time ago and I have attempted 1.3 to 2.1 upgrades several times in a test environment with the same results. I have, however, had some success with what I think is quite a dirty way of performing an "upgrade" and I am not sure what may have been missed or may fail. A quick rundown is below:

- Deploy new server & install OME (2.2 and now 2.3)
- point to a new MSSQL server during install to create a fresh DB
- stop services on existing OME and new version
- Backup existing OME DB and restore in to newly created DB
- restart new OME re-enter SQL details

This strangely works, but it just does not feel right. I am not sure what tables or data I may be missing as I presume that there have been changes between 1.3 and 2.x .. although it just seems to work. Does OME re-validate when you have to enter SQL credentials again and perform changes/updates as needed?

Is there a documented process for 1.3 to 2.x upgrades? I have tried to find something in the past, however I just come across the same old info which is run the exe, make sure the SQL account is db_owner and wait a few minutes.

failing that, is the method I have used successfully several times in testing a valid option? I really want to get us off of 1.3, but I also dont want to spend a whole weekend trying to recover our hardware monitoring platform either.

If you need more information i'll provide what I can.

Thanks in advance

↧

Get rid of the stupid form

July 19, 2017, 1:23 pm
$
0
0

Why do I have to fill out the stupid marketing form every time you release a new version and I want to go download it?

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