Hi,

we try update OME from v.1.1.0 to v.1.3 in DC.

we have installa SQL Server in DC with another account as described in OME Install Guide, but when install Essentials return error: "dell openmanage essentials cannot be installed on a domain controller system".

Can you help me?!

Best regard

Renato

Dell OpenManage Deployment Toolkit (DTK) 4.4 is published and available for download now. 

The new features of this release include: 

• Support for deployment of Windows operating system in Unified Extensible Firmware Interface (UEFI) mode.
• Using DTK utilities you can deploy the following operating system:
  • Microsoft Windows Server 2012 R2 Datacenter, Foundation, Essentials, and Standard editions
  • Novell SUSE Linux Enterprise Server 11 SP3 (64–bit)
  • Red Hat Enterprise Linux 6.5 (64–bit)
• RAIDCFG extends support to Dell PERC 9 (H730P Adapter) with the following features:
  • RAID 10 virtual disk with uneven span.
  • Advanced 4K sector hard disk drives.
  • T10 Protection Information (PI) for data integrity.
• Support for USB bootable DTK embedded Linux ISO image.
• Availability of DTK in Systems Management Tools and Documentation DVD.
• The RAIDCFG utility supports the following options, which can be configured through RAID controller BIOS:
  • Configuring the boot mode of the controller.
  • Configuring the auto import property of the controller.
  • Rebuilding physical disks associated with a virtual disk.
  • Configuring the array disk state to online or offline.
  • Converting RAID to non-RAID and vice versa on an array disk.
  • Replacing the physical disk of a virtual disk.
  • Executing consistency check on a virtual disk.
  • Erasing the encrypted physical disk.
  • Displaying the following in the array disk details:
    • Power State
    • Disk State
    • S.M.A.R.T. State
    • Maximum Device Link Rate
    • Negotiated Link Rate
    • Secured State
    • Encryption Capability
• Support for the following Dell PowerEdge servers:
  • R920
  • M820VRTX
  • R220
• Added support for the following Network Interface Cards (NICs), Converged Network Adapters (CNAs), and Fiber Channels (FCs):
  • Mellanox ConnectX-3 Dual Port 10 GbE DA/SFP+ Network Adapter
  • Mellanox ConnectX-3 Dual Port 10 GbE KR Blade Mezzanine Card
  • Mellanox ConnectX-3 Dual Port 40 GbE QSFP+ Network Adapter
  • Emulex OCe14102-UX-D Dual Port 10Gb SFP+ CNA
  • Emulex OCm14102-U3-D Dual Port 10Gb KR Blade Mezz
  • Emulex OCm14102-U2-D Dual Port 10Gb KR Blade NDC
  • Emulex OiCm14104-UX-D Quad Port 10Gb DA/SFP+ Rack NDC
• Deprecated support for the following operating systems:
  • SUSE Linux Enterprise Server 10 SP4
  • Red Hat Enterprise Linux 6.4 (64–bit)
  • SUSE Linux Enterprise Server 11 SP2

Downloads:     

Linux

Windows

Documentation

Dell Systems Build and Update Utility (SBUU) 2.4 is published and available for download now. 

The release highlights of SBUU are:

• Added support for the following operating systems:
  • • Microsoft Windows Server 2012 R2 Datacenter, Foundation, Essentials, and Standard editions
    • Novell SUSE Linux Enterprise Server 11 SP3 (64-bit)
    • Red Hat Enterprise Linux 6.5 (64-bit)
    • VMware ESXi 5.5 Flash and HDD
    • VMware ESXi 5.1 U2 Flash and HDD
    • VMware ESXi 5.0 U3 Flash and HDD

     

•  Added support for the following Adapter cards:

• • Mellanox ConnectX-3 Dual Port 10 GbE DA/SFP+ Network Adapter
  • Mellanox ConnectX-3 Dual Port 10 GbE KR Blade Mezzanine Card
  • Mellanox ConnectX-3 Dual Port 40 GbE QSFP+ Network Adapter
  • Emulex OCe14102-UX-D Dual Port 10Gb SFP+ CNA
  • Emulex OCm14102-U3-D Dual Port 10Gb KR Blade Mezz
  • Emulex OCm14102-U2-D Dual Port 10Gb KR Blade NDC
  • Emulex OCm14104-UX-D Quad Port 10Gb DA/SFP+ Rack NDC

• Added support for Dell PowerEdge M820VRTX, PowerEdge R220, and PowerEdge R920.

• Added support for Dell PERC 9 controllers (H730P Adapter) with the following features:

• • • RAID 10 virtual disk with uneven span.
    • Advanced 4K sector hard-disk drives.
    • T10 Protection Information (PI) for data integrity.

• Deprecated support for the following operating systems:

• • • • SUSE Linux Enterprise Server 10 SP4
      • SUSE Linux Enterprise Server 11 SP2
      • Red Hat Enterprise Linux 6.4 (64-bit)
      • VMware ESXi 5.1 U1 HDD and Flash
      • VMware ESXi 5.0 U2 HDD and Flash

Going forward, Dell recommends using Dell Lifecycle Controller 2 as replacement for SBUU as SBUU is deprecated. Dell Lifecycle Controller 2 provides improved capabilities such as: 

• Updating the system firmware. 
• Installing an operating system. 
• Updating the firmware and BIOS on multiple systems in a pre-operating system environment. 
• Configuring the system hardware. 
• Customizing the Server Update Utility (SUU) and using it to update the system. 

For more information, see the following documents available at dell.com/support/manuals: 

• Dell Lifecycle Controller 2 Version <Version Number> User's Guide 
• Dell Lifecycle Controller 2 Web Services Interface Guide 
• Lifecycle Controller Integration Best Practices 

Downloads:  

SBUU 2.4

Documentation

Didnt find any data on acoustic noise for R820 in 4 CPU configuration

Dear All

We are using the Dell AssetService (http://xserv.dell.com/services/assetservice.asmx) to manage the support of the assets of our customer. We query the warranty and systemtype information from the service. Sometimes, mostly on new devices, the field SystemModel and SystemType in the AssetHeaderData displays the value NULL (for example, service tag J2NQ85J). Is this a general issue? Thanks for your help!

Best regards
Mario

Does anyone know if OMSA 7.4 works in Windows 7 (x64 Enterprise). I have a Dell PE1950 that needs to run this OS for some custom software. I want to monitor this servers hardware health in Dell OME that runs on another box,

Clicking the download link for OMSA 7.4

http://www.dell.com/support/drivers/us/en/19/DriverDetails/Product/poweredge-r820?driverId=28KFC&osCode=WS8R2&fileId=3350815027

..and checking "compatibility" I can see Windows 7 is listed. However after installing I'm unable to log in via the app or going to https://my-server-name:1311

Also I don't understand why the app and web page ask for a host name. I just want to log into the local box OMSA is running on to see the hardware stats.

This is the first time I've used OMSA on WIndows - all my other systems are Linux. Those don't ask for a host name when you log in.

I've spent a good hour hunting around the many many many documents hosted on this site and not managed to find an answer. Personally I find the whole multitude of product names, combinations and permutations of all the Dell Management software components horribly confusing.

Any help appreciated!

Nick

Hoping someone here can shed some light on my problem.

We have bought a new PowerEdge R520 with 4x 3TB drives.  We want to install Windows Server 2012 on the server, ideally creating a single RAID5 virtual disk, with partitions of approx 200GB (open to recommendations here) for the Windows installation (C: drive) and the rest for data (D: drive, approx 7.8TB).

The problem I get is that when I work through the OpenManage System Builder CD/DVD and install Windows Server 2012, it gets to the stage where it asks which disk I want to install to, but it already seems to have split the disk into a 2TB and 6TB partitions (which would lose me 1.8TB on my data disk).

Am I doing something wrong?  Can I do what I want to do with a simple straightforward install?

More info:

Using the System Builder I created a single RAID5 virtual drive using all the disk and this shows up correctly at just under 9TB.  And nowhere do I manually set any partitions up.

I'm aware I could probably create two virtual disk at the setting up RAID stage - a small virtual disk (of about 200GB) and the rest of the space as a second virtual drive.  But I was hoping a single virtual disk with 2 partitions would be more flexible allowing me to use diskpart to re-size if necessary.

I downloaded the latest OpenManage CD/DVD so that I had the option of selecting Windows Server 2012 (though from what I've read I could have just selected Windows Server 2008)

This is the first time I've setup a server with UEFI and I'm not sure if this is part of the issue.

I am adding 2 drives to an existing 6 drive RAID-6 array managed by a PERC H710 mini controller.

I will be adding the drives using the rebuild features of OMSA and selecting RAID-6 to RAID-6.

My question is how long should I expect for the rebuild status of the new drives to take?

Drives are 300GB SAS-10k and the current space is almost full with data.

Also I want to confirm that the rebuild process in OMSA will NOT destroy the data on the existing VD and all I will have to do after the drives are added and rebuild is complete is:

1)  Resize the LVM Physical volume
2)  Resize the LVM Virtual Group
3)  Resize the Logical Volume
4)  Resize the file system

I would like to inventory detailed hardware settings (BIOS, RAID, etc.) of PowerEdge Servers. I see there is OMCI for desktops but this is not supported on servers. The only way I know to do it now is parsing output from omreport, syscfg (DTK) and racadm. I know you can also get lots of info via WSMAN and the idrac but I would prefer not to use this route because idracs are very unstable in my opinion.

I would prefer to do it all via WMI from the OS but the root\cimv2\Dell WMI Namespace doesn't contain the detailed info I need. I am looking to inventory all these settings in SCCM but the solution doesn't need to be SCCM specific.

Thanks for any help!

I have successfully scripted the changing of BIOS Setup passwords for M620 blades in powershell using WinRM. However.. when I attempt to set a new password using special characters, Wsman on the Dell M620 replies with a BIOS18 error and message stating "Invalid BIOS Password".

Entering a password containing special characters at the console works!?

Is there any work around to this?

In our situation, OME isn't being utilized. It is simply a powershell script issuing 2 WinRM commands:

"ChangePassword" method:

winrm i ChangePassword cimv2/root/dcim/DCIM_BIOSService?SystemCreationClassName=DCIM_ComputerSystem+CreationClassName=DCIM_BIOSService -u:USERNAME -p:PASSWORD -r:https://IP -SkipCNcheck -SkipCAcheck -encoding:utf-8 -f:xml -a:basic @{OldPassword="OLDPASSWORD";NewPassword="NEWPASSWORD";PasswordType="2";Target="BIOS.Setup.1-1"}

and the "CreateTargetedConfigJob" method:

winrm i CreateTargetedConfigJob cimv2/root/dcim/DCIM_BIOSService?SystemCreationClassName=DCIM_ComputerSystem+CreationClassName=DCIM_BIOSService -u:USERNAME -p:PASSWORD -r:https://IP -SkipCNcheck -SkipCAcheck -encoding:utf-8 -f:xml -a:basic @{ScheduledStartTime="TIME_NOW";RebootJobType="3";Target="BIOS.Setup.1-1"}

This works great when applying a password without any special characters, but fails with them..

I am trying to use OME (1.3) to manage a group of five CentOS-based PowerEdge servers (1 x R320, 4 x R620) each of which has an iDRAC7 Enterprise controller. The iDrac firmware revision on the R320 is 1.30.30, two of the R620s are at 1.56.55, the other two 620s are at 1.20.20.

The problem I have is that after discovery an inventory (using WS-MAN) OME sees the operating system on the 320 as Centos, and N/A on the R620s. The consequence of this is that OME decides to upgrade firmware on the servers using WIN32 packages which does not work.

I see the following on the actual iDRAC consoles. On the iDRAC associated with the 320 (1.30.30) I see the operating system as CentOS, on the consoles with the 1.20.20 firmware I also see the OS as Centos, but on the consoles with 1.56.55 firmware the operating system fields are blank.

I am trying to debug/understand the following issues:

How does the iDRAC determine the OS, and do I have any control over the process given that OME would prefer to see the OS as RHEL

The OME folks recommended upgrading to the latest iDRAC firmware (1.56.55); I would liek to get confirmation on this.

Any help would be much appreciated.

Thanks. Peter

I experienced an odd issue when updating NIC firmware using OME and I am not sure if this is an OME question or a Systems Forum question.

The upgrade was applied to one of the nodes in a two node GFS cluster.

The update apparently shut the interfaces down and brought them back up while the node was still live before the reboot was initiated by the update process to complete the updates in the LifeCycle controller.

Is this normal?

It caused GFS to go into a lock state due to loss of connectivity to the other node. Normally the GFS connection to the node going offline is closed cleanly during the reboot process allowing the single online node to keep working.

Why did the update do anything to the live in use interfaces?

An OMSA component is generating the following alert with Event ID 1000 in the Application log on a number of our servers on a daily basis (once or twice a day around 2 am and/or 8 pm):

Event Description: Faulting application name: wmiprvse.exe, version: 6.2.9200.16384, time stamp: 0x5010ad15
Faulting module name: Xalan-C_1_10.dll, version: 1.10.0.0, time stamp: 0x50587adc
Exception code: 0xc0000005
Fault offset: 0x0000000000004cc5
Faulting process id: 0x694
Faulting application start time: 0x01cf47ef8f2758b4
Faulting application path: C:\Windows\system32\wbem\wmiprvse.exe
Faulting module path: C:\Program Files\Dell\SysMgt\oma\bin\Xalan-C_1_10.dll

We saw the errors with OMSA 7.3 and they continue with 7.4.  Are other customers seeing these errors and does someone with more Apache experience have an explanation for them?

If CSIOR (Collect System Inventory on Restart) is enabled should all the LastSystemInventoryTime properties agree with the last boot time?

Thanks for any help.

I found something called SUU 14.03 available for download when I looked for updates for a PE R720.  It looks new, but I'm confused by the version 14.03.  It's 8GB, so I assume it's an actual SUU.  Did they actually go from 7.4 to 14.03?  Anyone know a reason for that change in numbering?

Hello, I am experiencing an inconsistent behavior from racadm utility while issuing "createvd" against the shared PERC8.

If I try to get physical disks descriptions, racadm returns the entire list of FQDD of pdisks

> racadm -r 172.24.0.100 -u root -p calvin raid get pdisks
Security Alert: Certificate is invalid - Certificate is not signed by Trusted Third Party
Continuing execution. Use -S option for racadm to stop execution on certificate-related errors.                                                                      

                                                                            
Disk.Bay.3:Enclosure.Internal.0-0:RAID.ChassisIntegrated.1-1
Disk.Bay.4:Enclosure.Internal.0-0:RAID.ChassisIntegrated.1-1
Disk.Bay.5:Enclosure.Internal.0-0:RAID.ChassisIntegrated.1-1
Disk.Bay.6:Enclosure.Internal.0-0:RAID.ChassisIntegrated.1-1
Disk.Bay.7:Enclosure.Internal.0-0:RAID.ChassisIntegrated.1-1
Disk.Bay.8:Enclosure.Internal.0-0:RAID.ChassisIntegrated.1-1
Disk.Bay.10:Enclosure.Internal.0-0:RAID.ChassisIntegrated.1-1
Disk.Bay.9:Enclosure.Internal.0-0:RAID.ChassisIntegrated.1-1
Disk.Bay.1:Enclosure.Internal.0-0:RAID.ChassisIntegrated.1-1
Disk.Bay.0:Enclosure.Internal.0-0:RAID.ChassisIntegrated.1-1
Disk.Bay.2:Enclosure.Internal.0-0:RAID.ChassisIntegrated.1-1
Disk.Bay.11:Enclosure.Internal.0-0:RAID.ChassisIntegrated.1-1

Success

But if I try to issue a createvd sub-command, FQDD are reported as invalid.

Any command that includes a pdkey list

> racadm -r 172.24.0.100 -u root -p calvin raid createvd:RAID.ChassisIntegrated.1-1 -rl r50 -sc 3 -pdkey:Disk.Bay.0:Enclosure.Internal.0-0:RAID.ChassisIntegrated.1-1, Disk.Bay.1:Enclosure.Internal.0-0:RAID.ChassisIntegrated.1-1, Disk.Bay.2:Enclosure.Internal.0-0:RAID.ChassisIntegrated.1-1,Disk.Bay.3:Enclosure.Internal.0-0:RAID.ChassisIntegrated.1-1, Disk.Bay.4:Enclosure.Internal.0-0:RAID.ChassisIntegrated.1-1, Disk.Bay.5:Enclosure.Internal.0-0:RAID.ChassisIntegrated.1-1, Disk.Bay.6:Enclosure.Internal.0-0:RAID.ChassisIntegrated.1-1, Disk.Bay.6:Enclosure.Internal.0-0:RAID.ChassisIntegrated.1-1, Disk.Bay.7:Enclosure.Internal.0-0:RAID.ChassisIntegrated.1-1, Disk.Bay.8:Enclosure.Internal.0-0:RAID.ChassisIntegrated.1-1 -dcp enabled -name:DATASTORE -current

is getting back an error message

STOR009 : Physical disk FQDD did not identify a valid physical disk for the operation. 

Am I missing anything?

As far I can see racadm and createvd syntax is correct.

Thanks.

I am using Dell License Manager 1.0.1.247 to inventory and manage my iDRAC7 license keys.

Upon recently adding some new ranges to discover any inventory I am seeing this error in the logs:

3/31/2014 6:39:36 PM E3021 Error saving system information to database: 10.102.24.189 - SQL Server Compact timed out waiting for a lock. The default lock time is 2000ms for devices and 5000ms for desktops. The default lock timeout can be increased in the connection string using the ssce: default lock timeout property. [ Session id = 33,Thread id = 6212,Process id = 1956,Table name = SystemInfo,Conflict type = x lock (s blocks),Resource = TAB ]

I see similar error for about 40 of the 46 IPs in the ranges I added. The other 6 were added successfully during the same run. Some before and one after.

What do I need to do to stop this sql error for License Manager?

Is the latest version of OMSA only 7.3.2 even though OM 7.4 is shown as available?

https://linux.dell.com/repo/hardware/latest/

Is there not an OMSA 7.4?

When installing on a new install or upgrading using YUM I can only get to 7.3.2 when using;

wget -q -O - http://linux.dell.com/repo/hardware/latest/bootstrap.cgi | bash

yum install srvadmin-all

or by using yum upgrade on an existing install.

These both give me srvadmin-all.x86_64 0:7.3.2-4.1.1.el6

Dear all

I don't know this is right forum to post this query or not.. if not please admin transfer to right forum

Thanks

Question

I have ordered Dell R720 with 2 GB SD cards. but there is no SD cards in the server, I can see near to power supply, there is slots for SD cards but those are empty.

So but there is a SD card 8GB for iDRAC Vflash. can we create a paritition on that Vflash & install the VMware ESXI 5.5

please reply..

Thanks in advance