ILO3 - IRS 7.7 - Not Discovered

[wazh]

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

[toddg1]

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.

[wazh]

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.

[toddg1]

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

[wazh]

You are correct

Attached so no confusion

[toddg1]

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.

[wazh]

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

[toddg1]

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.

[toddg1]

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?

[wazh]

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.