topic Re: ILO3 - IRS 7.7 - Not Discovered in Insight Remote Support

ILO3 - IRS 7.7 - Not Discovered

wazh — Thu, 09 Mar 2017 21:51:02 GMT

Hey All,

Ok pulling my hair out

I have some DL360 G7 Servers. Oct SPP installed. WMI Mapper installed. Windows 2012 R2 installed

I am trying to discover these within IRS. I am unable to use SNMP as the security guys dont want me using the old version. I am able to telnet on 5989 to the G7 OS (so FW OK). I have a user on the OS provisioned with Admin rights.

However IRS is unable to discover the system.

There is something fundamentally I am missing here and I am unable to find it in the doco or work it out.

Any suggestions would be appreciated.

Thanks

Warren

Re: ILO3 - IRS 7.7 - Not Discovered

toddg1 — Thu, 09 Mar 2017 22:10:13 GMT

Insight Remote Support doesn't support iLO3 devices - in general we can see them, but we don't support them as they don't contain the embedded Remote Support features that are present in iLO 4 (in Gen8 and Gen9 ProLiant).

Question: Are you giving I-RS the address of the SERVER or of the iLO?

For pre-Gen8 (iLO4) devices, we need the IP address of the server, and a pre-requisite is that you need to have the support pack for ProLiant installed and configured.

You didn't say what Operating System you have here - that also impacts what can be supported. Windows could use either SNMP (which you can't) or WMI -

Linux only uses SNMP - so if that's what you have (Linux) and a restriction that SNMP cannot be used, then unfortunately, these devices are not supportable.

If ESXi, then WBEM providers (which come with the VMWare) need to be installed and we use those - if it's ESXi and you're in lockdown mode, make sure to use the vCenter method to discover and talk to them (this works even not in lockdown and is easier, but is required if in lockdown)

Please correct me if I got anything wrong here.

Re: ILO3 - IRS 7.7 - Not Discovered

wazh — Thu, 09 Mar 2017 22:32:21 GMT

Hey Todd,

Thanks for the reposonse (and quick - awesome)

I am giving IRS the address of the server. However its unable to discover the server. The server is running windows 2012 R2 and SPP 2016_10. Including the WBEM agents.

I can telnet to 5989 from the IRS server so I can see the port is open.

Hope that helps.

Re: ILO3 - IRS 7.7 - Not Discovered

toddg1 — Thu, 09 Mar 2017 22:37:38 GMT

Have you configured the SPP to use the WMI agents instead of SNMP, which I think it does by default?

Re: ILO3 - IRS 7.7 - Not Discovered

wazh — Thu, 09 Mar 2017 22:57:40 GMT

You are correct

Attached so no confusion

Re: ILO3 - IRS 7.7 - Not Discovered

toddg1 — Fri, 10 Mar 2017 13:29:35 GMT

Can you tell me specifically which version of Insight Remote Support you have? (in the pulldown menu About Insight RS) or on the login screen.

Do you see ANYTHING in the "Devices" panel for these devices at all? If there is anything there for the device, and you have the latest Insight RS, then there is a tab called "Journal" that shows what Insight RS tried during discovery process.

Can you provide that for one of these devices if it exists?

If you see nothing there, then it seems we are at the point where trying to resolve via this forum isn't going to be quick or probably even useful and it may be time to raise a support case with HPE support.

Re: ILO3 - IRS 7.7 - Not Discovered

wazh — Fri, 10 Mar 2017 20:26:31 GMT

Sorry,

IRS Version is 7.7.0.0042

Here is a copy of the journal for the device.

2017-03-10 03:28:18Z Dispatch initial classifier 2017-03-10 03:28:18Z Try com.hp.dcs.devices.generic.UnknownDevice 2017-03-10 03:28:18Z 2017-03-10 03:28:18Z Process classifier com.hp.dcs.devices.generic.UnknownDevice with quality 300 2017-03-10 03:28:18Z Check additional protocols 2017-03-10 03:28:18Z 2017-03-10 03:28:18Z Dispatch classifier com.hp.dcs.devices.generic.UnknownDevice 2017-03-10 03:28:18Z Try com.hp.dcs.devices.generic.SnmpDevice 2017-03-10 03:28:42Z Try com.hp.dcs.devices.make.HP.Ilo 2017-03-10 03:28:44Z Try com.hp.dcs.devices.make.HP.OnboardAdministrator 2017-03-10 03:28:44Z Try com.hp.dcs.devices.make.HP.EMU 2017-03-10 03:28:44Z Try com.hp.dcs.devices.helper.WindowsPortTester 2017-03-10 03:28:45Z 2017-03-10 03:28:45Z Process classifier com.hp.dcs.devices.helper.WindowsPortTester with quality 300 2017-03-10 03:28:45Z Check additional protocols 2017-03-10 03:28:45Z 2017-03-10 03:28:45Z Dispatch classifier com.hp.dcs.devices.helper.WindowsPortTester 2017-03-10 03:28:45Z Try com.hp.dcs.devices.generic.Windows 2017-03-10 03:29:07Z Try com.hp.dcs.devices.make.HP.ProLiantWindows 2017-03-10 03:29:07Z Try com.hp.uca.discovery.classifiers.generic.WMIDevice 2017-03-10 03:29:49Z Try com.hp.uca.discovery.classifiers.make.wbem.HPWinComputerSystem 2017-03-10 03:29:52Z Try com.hp.uca.discovery.classifiers.make.wbem.SMX_WSMANDevice 2017-03-10 03:29:52Z Try com.hp.uca.discovery.classifiers.make.wbem.CIMOperatingSystemHPUX 2017-03-10 03:29:52Z Try com.hp.uca.discovery.classifiers.make.wbem.CIMOperatingSystemNonStop 2017-03-10 03:29:52Z Try com.hp.uca.discovery.classifiers.make.wbem.HPVMSProcessor 2017-03-10 03:29:52Z Try com.hp.uca.discovery.classifiers.make.wbem.SMX_WBEMDevice 2017-03-10 03:29:52Z Try com.hp.dcs.devices.generic.WindowsFull 2017-03-10 03:29:52Z 2017-03-10 03:29:52Z Process classifier com.hp.dcs.devices.generic.WindowsFull with quality 300 2017-03-10 03:29:52Z Check additional protocols 2017-03-10 03:29:52Z 2017-03-10 03:29:52Z Dispatch classifier com.hp.dcs.devices.generic.WindowsFull 2017-03-10 03:29:52Z Try com.hp.dcs.devices.make.HP.CommandViewEva 2017-03-10 03:29:54Z Try com.hp.uca.discovery.classifiers.make.hp.CommandViewTl 2017-03-10 03:29:55Z Try com.hp.uca.discovery.classifiers.make.hp.msa.MsaProxyProvider 2017-03-10 03:29:55Z Try com.hp.uca.discovery.classifiers.make.brocade.DataCenterFabricManager 2017-03-10 03:29:55Z Try com.hp.uca.discovery.classifiers.make.hp.VCenter 2017-03-10 03:29:56Z Try com.hp.uca.discovery.classifiers.generic.GenericDevice 2017-03-10 03:29:56Z 2017-03-10 03:29:56Z Process classifier com.hp.uca.discovery.classifiers.generic.GenericDevice with quality 300 2017-03-10 03:29:56Z Check additional protocols 2017-03-10 03:29:57Z Protocol ELMC : SUCCESS 2017-03-10 03:29:57Z 2017-03-10 03:29:57Z Dispatch classifier com.hp.uca.discovery.classifiers.generic.GenericDevice 2017-03-10 03:29:57Z Try com.hp.uca.discovery.classifiers.generic.Localhost 2017-03-10 03:29:57Z No more classifiers 2017-03-10 03:30:00Z 2017-03-10 03:30:00Z Retaining alternative information due to higher quality: 2017-03-10 03:30:00Z No information retained

Re: ILO3 - IRS 7.7 - Not Discovered

toddg1 — Fri, 10 Mar 2017 20:50:46 GMT

Thank you - I will pass this around to a few folks and see what they can tell from this data. We may still end up needing a support case. It may take a few days.

Re: ILO3 - IRS 7.7 - Not Discovered

toddg1 — Fri, 10 Mar 2017 20:56:59 GMT

One thing I see here:

Try com.hp.dcs.devices.make.HP.ProLiantWindows 2017-03-10 03:29:07Z Try com.hp.uca.discovery.classifiers.generic.WMIDevice 2017-03-10 03:29:49Z Try com.hp.uca.discovery.classifiers.make.wbem.HPWinComputerSystem 2017-03-10 03:29:52Z

The discovery doesn't appear to have been able to connect with WMI - or we would have seen some result in that area.

Are you certain that WMI itself is enabled from an OS/Windows perspective?

Re: ILO3 - IRS 7.7 - Not Discovered

wazh — Sun, 12 Mar 2017 23:05:49 GMT

Hey Thanks again for the responses.

I can see that the service is running. I checked permissions as well and the local account is in the admin group. So permissions wise looks OK.

Re: ILO3 - IRS 7.7 - Not Discovered

toddg1 — Mon, 13 Mar 2017 15:38:15 GMT

The team is checking - these questions are asked, while they dig a little harder - but all agree, we are not able to talk to the device as expected.

Are you sure there is not a firewall between the Insight RS system and the endpoint G7 ProLiant?

From the team:

I don't see any obvious problems with the customer's setup.
1. Is he positive he has the correct WMI credential? Type the password on the cmd line, then paste it into our passwd field.
2. WMIMapper sits between IRS and the endpoint.

(I have an expert trying to help determine if WMIMapper is setup correctly)

Are ANY Windows devices working properly to the WMI services? If they are, then WMIMApper is probably setup correctly.

Re: ILO3 - IRS 7.7 - Not Discovered

wazh — Tue, 14 Mar 2017 06:12:03 GMT

HI Guys,

Thanks again.

In answer to your points.

Yes there is a FW between the IRS and the G7. However TCP_5989 has been opened and I am able to telnet from IRS to the G7 and see the port is open.

The G7 is a standalone system and not on a domain. The account HPSIM has been configured locally on there. Within IRS I have the same credential. (see pic below) (cos pics are always good :) ). Yes there are other systems talking to IRS correctly. (however I would need to check that these are using WMI and not the old SNMP that some older systems are still using and what we are trying to move away from)

Is there anything special that needs to be done on the WMIMapper?

Re: ILO3 - IRS 7.7 - Not Discovered

toddg1 — Tue, 14 Mar 2017 17:54:48 GMT

A few more questions, comments. You state that you can "telnet" to the port on the endpoint. However, Insight RS doesn't connect to the endpoint in that manner. We use the WMI-MAPPER (installed on the Insight RS) to connect, using DCOM, to the endpoint.

I think there could be something about the way DCOM on that specific endpoint is not configured? If you have Insight RS talking to other G7 endpoints via WMI, then the WMI-MAPPER is likely setup correctly.

Can you validate?

Re: ILO3 - IRS 7.7 - Not Discovered

toddg1 — Tue, 14 Mar 2017 18:59:50 GMT

I missed one other point, sorry for the second post. Is there a chance that this G7 is on a subnet that has the firewall configured to not allow DCOM?

After this - if these ideas don't spur something in your mind, I am going to have to suggest that it's time to open an official support case at this time.

Re: ILO3 - IRS 7.7 - Not Discovered

wazh — Thu, 16 Mar 2017 06:28:13 GMT

Hi,

While I talk to the FW guys on the other node (which could take a while). I decided to get a older node in the same network segment and rule out any other issue.

As much as I got more information in the journal I did worry about the same thing you made mention of which was.

2017-03-16 06:21:01Z Dispatch classifier com.hp.dcs.devices.helper.WindowsPortTester
2017-03-16 06:21:01Z Try com.hp.dcs.devices.generic.Windows
2017-03-16 06:21:01Z Try com.hp.dcs.devices.make.HP.ProLiantWindows
2017-03-16 06:21:01Z Try com.hp.uca.discovery.classifiers.generic.WMIDevice
2017-03-16 06:21:03Z Try com.hp.uca.discovery.classifiers.make.wbem.HPWinComputerSystem
2017-03-16 06:21:05Z Try com.hp.uca.discovery.classifiers.make.wbem.SMX_WSMANDevice
2017-03-16 06:21:05Z Try com.hp.uca.discovery.classifiers.make.wbem.CIMOperatingSystemHPUX
2017-03-16 06:21:05Z Try com.hp.uca.discovery.classifiers.make.wbem.CIMOperatingSystemNonStop
2017-03-16 06:21:05Z Try com.hp.uca.discovery.classifiers.make.wbem.HPVMSProcessor
2017-03-16 06:21:05Z Try com.hp.uca.discovery.classifiers.make.wbem.SMX_WBEMDevice
2017-03-16 06:21:05Z Try com.hp.dcs.devices.generic.WindowsFull
2017-03-16 06:21:05Z
2017-03-16 06:21:05Z Process classifier com.hp.dcs.devices.generic.WindowsFull with quality 300
2017-03-16 06:21:05Z Check additional protocols

It appears to try WMI and doesnt get a response.

FULL Journal below.

2017-03-16 06:21:55Z Type : SERVER
2017-03-16 06:21:55Z Make : HP
2017-03-16 06:21:55Z Model : ProLiant DL380 G6
2017-03-16 06:21:55Z UUID : 33313934-3233-5541-4230-31315036384D
2017-03-16 06:21:55Z Serial number : AUB011P68M
2017-03-16 06:21:58Z Add port : [Hardware address: 18:a9:05:54:55:ac; Index: 12; Description: HP NC382i DP Multifunction Gigabit Server Adapter #2; Type: ETHERNET_CSMACD; Admin State: DOWN; Oper State: <cleared>; Speed: 0]
2017-03-16 06:21:58Z Add port : [Hardware address: 00:00:00:00:00:00:00:e0; Index: 18; Description: Microsoft ISATAP Adapter #3; Type: TUNNEL; Admin State: UP; Oper State: DOWN; Speed: 100000]
2017-03-16 06:21:58Z Add port : [Hardware address: 20:41:53:59:4e:ff; Index: 9; Description: RAS Async Adapter; Type: PPP; Admin State: UP; Oper State: UP; Speed: 1073741824]
2017-03-16 06:21:58Z Add port : [Hardware address: 3e:9e:20:52:41:53; Index: 6; Description: WAN Miniport (IPv6); Type: ETHERNET_CSMACD; Admin State: UP; Oper State: UP; Speed: 1073741824]
2017-03-16 06:21:58Z Add port : [Hardware address: 18:a9:05:54:55:aa; Index: 11; Description: HP NC382i DP Multifunction Gigabit Server Adapter #5; Type: ETHERNET_CSMACD; Admin State: UP; Oper State: UP; Speed: 100000000]
2017-03-16 06:21:58Z
2017-03-16 06:21:58Z IP Configuration:
2017-03-16 06:21:58Z IP address: fe80:0:0:0:44c6:3733:5fef:df43
2017-03-16 06:21:58Z IP address: 10.16.104.54
2017-03-16 06:21:58Z Add port : [Hardware address: 00:00:00:00:00:00:00:00; Index: 10; Description: WAN Miniport (IKEv2); Type: TUNNEL; Admin State: UP; Oper State: DOWN; Speed: 0]
2017-03-16 06:21:58Z Add port : [Hardware address: <cleared>; Index: 3; Description: WAN Miniport (L2TP); Type: TUNNEL; Admin State: UP; Oper State: UP; Speed: 1073741824]
2017-03-16 06:21:58Z Add port : [Hardware address: <cleared>; Index: 2; Description: WAN Miniport (SSTP); Type: TUNNEL; Admin State: UP; Oper State: UP; Speed: 1073741824]
2017-03-16 06:21:58Z Add port : [Hardware address: <cleared>; Index: 4; Description: WAN Miniport (PPTP); Type: TUNNEL; Admin State: UP; Oper State: UP; Speed: 1073741824]
2017-03-16 06:21:58Z Add port : [Hardware address: 18:a9:05:54:55:ae; Index: 16; Description: HP NC382i DP Multifunction Gigabit Server Adapter #4; Type: ETHERNET_CSMACD; Admin State: DOWN; Oper State: <cleared>; Speed: 0]
2017-03-16 06:21:58Z Add port : [Hardware address: <cleared>; Index: 1; Description: Software Loopback Interface 1; Type: SOFTWARE_LOOPBACK; Admin State: UP; Oper State: UP; Speed: 1073741824]
2017-03-16 06:21:58Z
2017-03-16 06:21:58Z IP Configuration:
2017-03-16 06:21:58Z IP address: 127.0.0.1
2017-03-16 06:21:58Z IP address: 0:0:0:0:0:0:0:1
2017-03-16 06:21:58Z Add port : [Hardware address: <cleared>; Index: 5; Description: WAN Miniport (PPPOE); Type: PPP; Admin State: UP; Oper State: UP; Speed: 1073741824]
2017-03-16 06:21:58Z Add port : [Hardware address: 18:a9:05:54:55:b0; Index: 15; Description: HP NC382i DP Multifunction Gigabit Server Adapter #3; Type: ETHERNET_CSMACD; Admin State: DOWN; Oper State: <cleared>; Speed: 0]
2017-03-16 06:22:02Z
2017-03-16 06:22:02Z Retaining alternative information due to higher quality:
2017-03-16 06:22:02Z UNSET/450 Product number : 491332-371
2017-03-16 06:22:02Z UNSET/450 Operating system : Windows Server 2008 R2 x64 Standard Edition, Service Pack 1

Attaching additional Journal

2017-03-16 06:20:09Z Type : SERVER
2017-03-16 06:20:09Z Make : HP
2017-03-16 06:20:09Z Model : ProLiant DL380 G6
2017-03-16 06:20:09Z UUID : 33313934-3233-5541-4230-31315036384D
2017-03-16 06:20:09Z Serial number : AUB011P68M
2017-03-16 06:20:11Z Add port : [Hardware address: <cleared>; Index: 4; Description: WAN Miniport (PPTP); Type: TUNNEL; Admin State: UP; Oper State: UP; Speed: 1073741824]
2017-03-16 06:20:11Z Add port : [Hardware address: 18:a9:05:54:55:aa; Index: 11; Description: HP NC382i DP Multifunction Gigabit Server Adapter #5; Type: ETHERNET_CSMACD; Admin State: UP; Oper State: UP; Speed: 100000000]
2017-03-16 06:20:11Z
2017-03-16 06:20:11Z IP Configuration:
2017-03-16 06:20:11Z IP address: fe80:0:0:0:44c6:3733:5fef:df43
2017-03-16 06:20:11Z IP address: 10.16.104.54
2017-03-16 06:20:11Z Add port : [Hardware address: 3e:9e:20:52:41:53; Index: 7; Description: WAN Miniport (Network Monitor); Type: ETHERNET_CSMACD; Admin State: UP; Oper State: UP; Speed: 1073741824]
2017-03-16 06:20:11Z Add port : [Hardware address: <cleared>; Index: 5; Description: WAN Miniport (PPPOE); Type: PPP; Admin State: UP; Oper State: UP; Speed: 1073741824]
2017-03-16 06:20:11Z Add port : [Hardware address: 20:41:53:59:4e:ff; Index: 9; Description: RAS Async Adapter; Type: PPP; Admin State: UP; Oper State: UP; Speed: 1073741824]
2017-03-16 06:20:11Z Add port : [Hardware address: 18:a9:05:54:55:ae; Index: 16; Description: HP NC382i DP Multifunction Gigabit Server Adapter #4; Type: ETHERNET_CSMACD; Admin State: DOWN; Oper State: <cleared>; Speed: 0]
2017-03-16 06:20:11Z Add port : [Hardware address: 18:a9:05:54:55:ac; Index: 12; Description: HP NC382i DP Multifunction Gigabit Server Adapter #2; Type: ETHERNET_CSMACD; Admin State: DOWN; Oper State: <cleared>; Speed: 0]
2017-03-16 06:20:11Z Add port : [Hardware address: <cleared>; Index: 1; Description: Software Loopback Interface 1; Type: SOFTWARE_LOOPBACK; Admin State: UP; Oper State: UP; Speed: 1073741824]
2017-03-16 06:20:11Z
2017-03-16 06:20:11Z IP Configuration:
2017-03-16 06:20:11Z IP address: 0:0:0:0:0:0:0:1
2017-03-16 06:20:11Z IP address: 127.0.0.1
2017-03-16 06:20:11Z Add port : [Hardware address: 00:00:00:00:00:00:00:00; Index: 10; Description: WAN Miniport (IKEv2); Type: TUNNEL; Admin State: UP; Oper State: DOWN; Speed: 0]
2017-03-16 06:20:11Z Add port : [Hardware address: 00:00:00:00:00:00:00:e0; Index: 17; Description: Microsoft ISATAP Adapter #4; Type: TUNNEL; Admin State: UP; Oper State: DOWN; Speed: 100000]
2017-03-16 06:20:11Z Add port : [Hardware address: <cleared>; Index: 2; Description: WAN Miniport (SSTP); Type: TUNNEL; Admin State: UP; Oper State: UP; Speed: 1073741824]
2017-03-16 06:20:11Z Add port : [Hardware address: <cleared>; Index: 3; Description: WAN Miniport (L2TP); Type: TUNNEL; Admin State: UP; Oper State: UP; Speed: 1073741824]
2017-03-16 06:20:11Z Add port : [Hardware address: 18:a9:05:54:55:b0; Index: 15; Description: HP NC382i DP Multifunction Gigabit Server Adapter #3; Type: ETHERNET_CSMACD; Admin State: DOWN; Oper State: <cleared>; Speed: 0]
2017-03-16 06:20:16Z
2017-03-16 06:20:16Z Process classifier com.hp.dcs.devices.generic.UnknownDevice with quality 300
2017-03-16 06:20:16Z Check additional protocols
2017-03-16 06:20:16Z
2017-03-16 06:20:16Z Dispatch classifier com.hp.dcs.devices.generic.UnknownDevice
2017-03-16 06:20:16Z Try com.hp.dcs.devices.generic.SnmpDevice
2017-03-16 06:20:59Z Try com.hp.dcs.devices.make.HP.Ilo
2017-03-16 06:21:01Z Try com.hp.dcs.devices.make.HP.OnboardAdministrator
2017-03-16 06:21:01Z Try com.hp.dcs.devices.make.HP.EMU
2017-03-16 06:21:01Z Try com.hp.dcs.devices.helper.WindowsPortTester
2017-03-16 06:21:01Z
2017-03-16 06:21:01Z Process classifier com.hp.dcs.devices.helper.WindowsPortTester with quality 300
2017-03-16 06:21:01Z Check additional protocols
2017-03-16 06:21:01Z
2017-03-16 06:21:01Z Dispatch classifier com.hp.dcs.devices.helper.WindowsPortTester
2017-03-16 06:21:01Z Try com.hp.dcs.devices.generic.Windows
2017-03-16 06:21:01Z Try com.hp.dcs.devices.make.HP.ProLiantWindows
2017-03-16 06:21:01Z Try com.hp.uca.discovery.classifiers.generic.WMIDevice
2017-03-16 06:21:03Z Try com.hp.uca.discovery.classifiers.make.wbem.HPWinComputerSystem
2017-03-16 06:21:05Z Try com.hp.uca.discovery.classifiers.make.wbem.SMX_WSMANDevice
2017-03-16 06:21:05Z Try com.hp.uca.discovery.classifiers.make.wbem.CIMOperatingSystemHPUX
2017-03-16 06:21:05Z Try com.hp.uca.discovery.classifiers.make.wbem.CIMOperatingSystemNonStop
2017-03-16 06:21:05Z Try com.hp.uca.discovery.classifiers.make.wbem.HPVMSProcessor
2017-03-16 06:21:05Z Try com.hp.uca.discovery.classifiers.make.wbem.SMX_WBEMDevice
2017-03-16 06:21:05Z Try com.hp.dcs.devices.generic.WindowsFull
2017-03-16 06:21:05Z
2017-03-16 06:21:05Z Process classifier com.hp.dcs.devices.generic.WindowsFull with quality 300
2017-03-16 06:21:05Z Check additional protocols
2017-03-16 06:21:05Z
2017-03-16 06:21:05Z Dispatch classifier com.hp.dcs.devices.generic.WindowsFull
2017-03-16 06:21:05Z Try com.hp.dcs.devices.make.HP.CommandViewEva
2017-03-16 06:21:07Z Try com.hp.uca.discovery.classifiers.make.hp.CommandViewTl
2017-03-16 06:21:08Z Try com.hp.uca.discovery.classifiers.make.hp.msa.MsaProxyProvider
2017-03-16 06:21:08Z Try com.hp.uca.discovery.classifiers.make.brocade.DataCenterFabricManager
2017-03-16 06:21:08Z Try com.hp.uca.discovery.classifiers.make.hp.VCenter
2017-03-16 06:21:09Z Try com.hp.uca.discovery.classifiers.generic.GenericDevice
2017-03-16 06:21:09Z
2017-03-16 06:21:09Z Process classifier com.hp.uca.discovery.classifiers.generic.GenericDevice with quality 300
2017-03-16 06:21:09Z Check additional protocols
2017-03-16 06:21:10Z Protocol ELMC : SUCCESS
2017-03-16 06:21:10Z
2017-03-16 06:21:10Z Dispatch classifier com.hp.uca.discovery.classifiers.generic.GenericDevice
2017-03-16 06:21:10Z Try com.hp.uca.discovery.classifiers.generic.Localhost
2017-03-16 06:21:10Z No more classifiers
2017-03-16 06:21:10Z
2017-03-16 06:21:10Z Retaining alternative information due to higher quality:
2017-03-16 06:21:10Z UNSET/500 Make : HP
2017-03-16 06:21:10Z UNSET/500 Model : ProLiant DL380 G6
2017-03-16 06:21:10Z UNSET/450 Product number : 491332-371
2017-03-16 06:21:10Z UNSET/500 Serial number : AUB011P68M
2017-03-16 06:21:10Z 300/500 Uuid : 33313934-3233-5541-4230-31315036384d
2017-03-16 06:21:10Z UNSET/500 Type : SERVER
2017-03-16 06:21:10Z UNSET/450 Operating system : Windows Server 2008 R2 x64 Standard Edition, Service Pack 1
2017-03-16 06:21:10Z UNSET/300 Sys description : Hardware: Intel64 Family 6 Model 26 Stepping 5 AT/AT COMPATIBLE - Software: Windows Version 6.1 (Build 7601 Multiprocessor Free)
2017-03-16 06:21:10Z UNSET/300 Sys object id : 1.3.6.1.4.1.311.1.1.3.1.2

Re: ILO3 - IRS 7.7 - Not Discovered

justjeff — Wed, 22 Nov 2017 15:25:58 GMT

This is all great but, PLEASE, when saying something like: "Use the 'vcenter method' of (registration/discovery)," please give a link or more details - I know it's not applicable here, but it would have been nice to have more detail, when you made this comment:

"If ESXi, then WBEM providers (which come with the VMWare) need to be installed and we use those - if it's ESXi and you're in lockdown mode, make sure to use the vCenter method to discover and talk to them (this works even not in lockdown and is easier, but is required if in lockdown)" Thanks!

Re: ILO3 - IRS 7.7 - Not Discovered

SANJAY MUNDHRA — Thu, 23 Nov 2017 01:53:38 GMT

Hi,

You can refer the IRS Managed Device Configuration guide for more details on how to discover the servers via Vcentre and the pre-requisites required - https://support.hpe.com/hpsc/doc/public/display?docId=a00023073en_us

Other good IRS documentations are available at http://h17007.www1.hpe.com/us/en/enterprise/servers/solutions/info-library/index.aspx?cat=HP_Insight_Remote_Support#.WhYp4WYUmuU