Highlighted
gaal.stefan
1 Copper

OME 2.0.1.2222 won`t add 13th gen servers to inventory

Jump to solution

Since a wile we started racking 13th gen Dell`s to our datacenters and I`ve noticed that most of them are not being discovered by OME.

They are in the same network as the old ones (12th gen) which are discovered, having the same settings, same user/password, IPMI enabled, SNMP enabled etc.

On all of this hosts I see in the lifecycle log the following line repeating many times "Successfully logged in using root, from xxx.xxx.xxx.xxx and WS-MAN."

iDRAC8 firmware version is 2.10.10.10

Please hit me with some ideas 

Stef

0 Kudos
2 Solutions

Accepted Solutions

RE: OME 2.0.1.2222 won`t add 13th gen servers to inventory

Jump to solution

Hi Stef,

Few questions:

  • Can confirm which protocol are you using to perform discovery?
  • Are you able to connect to those servers using that protocol via troubleshooting tool?
  • Are the required ports opened on these new servers as needed by OME for communication to happen between OME and server?
  • Also, is there a specific IP range where you are not able to discover the servers?

Thanks,
Pupul

0 Kudos
gaal.stefan
1 Copper

RE: OME 2.0.1.2222 won`t add 13th gen servers to inventory

Jump to solution

Dear All,

Finally I managed to solve this.

The problem was the "DNS DRAC Name" that was set to "idrac" and not "idrac-SERVICETAG", as we used to receive our 12th gen boxes from Dell.

Basically OME found the server, but merged all iDRACs into one discovered device, which had multiple IP addresses from every iDRAC with DNS DRAC Name set to "idrac".

Cheers!

12 Replies

RE: OME 2.0.1.2222 won`t add 13th gen servers to inventory

Jump to solution

Hi Stef,

Few questions:

  • Can confirm which protocol are you using to perform discovery?
  • Are you able to connect to those servers using that protocol via troubleshooting tool?
  • Are the required ports opened on these new servers as needed by OME for communication to happen between OME and server?
  • Also, is there a specific IP range where you are not able to discover the servers?

Thanks,
Pupul

0 Kudos
gaal.stefan
1 Copper

RE: OME 2.0.1.2222 won`t add 13th gen servers to inventory

Jump to solution

  • WS-MAN
  • Yes, I can connect from the OME server with the troubleshooting tool using WS-MAN
  • Yes, ports are open, as I explained before, this servers are on the same management network then the ones that had been discovered.
  • It`s not a specific IP range, it`s just some of the 13th gen servers (around 90% of them)

I forgot to mention in first post that some 13G`s are discovered (around 10% of them). Many times they are even physically located in the same rack as other that are not discovered, and connected to the same switch etc.

What I did now, took two servers, one that showed up in OME and one that didn`t, physically located in the same rack. Ran "racadm -r <ip> -u root -p <password> get -f <filename>" for both and then compared the results. Unfortunately I can`t find any setting that would be different from one to another host, nor firmware levels. 

0 Kudos

RE: OME 2.0.1.2222 won`t add 13th gen servers to inventory

Jump to solution

Hi,

Thanks for the details.

Can you run the winrm command from the OME box on the affected iDRAC and enumerate DCIM_SystemView and share the output here (please omit confidential information like servicetag, etc.)

For ex. winrm e cimv2/root/dcim/DCIM_SystemView -u:<userid>-p:<password> -r:https://<ipaddress>/wsman:443 -SkipCNcheck -SkipCAcheck -encoding:utf-8 -a:basic

This will enable us to identify your problem.

Vijay.

0 Kudos

RE: OME 2.0.1.2222 won`t add 13th gen servers to inventory

Jump to solution

Thanks for confirming.

Can you confirm one more thing, are these servers/RACs classified under unclassified or you are seeing all of these classified under RAC device group with the same name?

Thanks,
Pupul

0 Kudos
gaal.stefan
1 Copper

RE: OME 2.0.1.2222 won`t add 13th gen servers to inventory

Jump to solution

Hi Vijay,

Here`s the output:

C:\Users\xxxxx\Desktop>winrm e cimv2/root/dcim/DCIM_SystemView -u:root -p:xxxx -r:https://xxxxx /wsman:443 -SkipCNcheck -SkipCAcheck -encoding:utf-8 -a:basic
DCIM_SystemView
AssetTag
BIOSReleaseDate = 03/09/2015
BIOSVersionString = 1.2.10
BaseBoardChassisSlot = NA
BatteryRollupStatus = 1
BladeGeometry = 255
BoardPartNumber = xxxx
BoardSerialNumber = xxxxx
CMCIP = null
CPLDVersion = 1.0.1
CPURollupStatus = 1
ChassisModel
ChassisName = Main System Chassis
ChassisServiceTag = xxxxxx
ChassisSystemHeight = 2
DeviceDescription = System
EstimatedSystemAirflow = 27
ExpressServiceCode = xxxxxx
FQDD = System.Embedded.1
FanRollupStatus = 1
HostName = xxxxxx
InstanceID = System.Embedded.1
LastSystemInventoryTime = 20150508232851.000000+000
LastUpdateTime = 20150508232843.000000+000
LicensingRollupStatus = 1
LifecycleControllerVersion = 2.10.10.10
Manufacturer = Dell Inc.
MaxCPUSockets = 2
MaxDIMMSlots = 24
MaxPCIeSlots = 6
MemoryOperationMode = OptimizerMode
Model = PowerEdge R730xd
NodeID = xxxxxxx
PSRollupStatus = 1
PlatformGUID = 3234474f-c0ca-4880-3510-00324c4c4544
PopulatedCPUSockets = 2
PopulatedDIMMSlots = 16
PopulatedPCIeSlots = 1
PowerCap = 365
PowerCapEnabledState = 3
PowerState = 2
PrimaryStatus = 1
RollupStatus = 1
ServerAllocation = null
ServiceTag = xxxxx
StorageRollupStatus = 1
SysMemErrorMethodology = 6
SysMemFailOverState = NotInUse
SysMemLocation = 3
SysMemMaxCapacitySize = 786432
SysMemPrimaryStatus = 1
SysMemTotalSize = 524288
SystemGeneration = 13G Monolithic
SystemID = 1575
SystemRevision = 0
TempRollupStatus = 1
UUID = 4c4c4544-0032-3510-8048-cac04f473432
VoltRollupStatus = 1
smbiosGUID = 44454c4c-3200-1035-8048-cac04f473432

 

Stefan

0 Kudos
gaal.stefan
1 Copper

RE: OME 2.0.1.2222 won`t add 13th gen servers to inventory

Jump to solution

Pupul,

Not sure what you mean by seeing all the devices with the same name. They don`t show up at all in OME, not under unclassified, nor elsewhere. 

Stefan

0 Kudos

RE: OME 2.0.1.2222 won`t add 13th gen servers to inventory

Jump to solution

Hi Stefan,

Since you are able to connect to the iDRAC using OME machine, it should at least be there under any of the groups, least possible unclassified. Can you try pinging the device from OME? May be you have already tried. If that works, we will need a trouble ticket to figure this one out. Support number is 800-945-3355.

Thanks,
Pupul

0 Kudos

RE: OME 2.0.1.2222 won`t add 13th gen servers to inventory

Jump to solution

Thanks. The WSMAN output looks good and doesn't have any issue. In case this is the issue, the iDRAC will still appear in unclassified group.

As per the behavior what you are seeing that iDRAC is not appearing anywhere in the device tree. Can you confirm when you click that particular range in Discovery Portal, the Discovered vs. Inventories Devices does not show anything?

If the above is true, we suspect the affected iDRAC is not pingable from your OME box. You can try ICMP test from Troubleshooting tool in that case to confirm.

Let  us know if this helps.

Vijay

0 Kudos
gaal.stefan
1 Copper

RE: OME 2.0.1.2222 won`t add 13th gen servers to inventory

Jump to solution

Hi Vijay,

The devices are pingable from the OME box, of course. 

Thanks

0 Kudos