HP Device Manager 4.6 Offline thinclient status

[LeroyK]

Dear All,

I am running HP Device Manager 4.6 to manage around 450 thinclients. Unfortuantely ever since its introduction a few months ago I am unable to resolve an issue we face with offline thinclients. I will try and explain the situation.

A thinclient is turned on and receives an IP address from our DHCP server, for example 192.168.1.69.

The thinclient is visible and fully functional within HP Device Manager.

The user shuts down the thinclient and it is left offline for more then 8 hours (our DHCP lease time).

A different user starts a different thinclient. As the lease expired this thinclient reveices the IP address 192.168.1.69 aswell. The new thinclient is working correctly, but we face issues with the old (offline) ones.

Unfortunately as the old thinclient was shutdown it was not updated in HPDM and it still shows it has the address 192.168.1.69. As the new thinclient is online with this IP address, the old thinclient is shown as online too (even though it is physically shutdown).

I have added an image below as an example with even 3 thinclients.

When pinging the devices, the only one online is the HP-14-073. The others have been shutdown. When shadowing one of the other two thinclients you connect to the online one, giving a false impression the other 2 are online and can be shadowed. Also deploying an image is risky in this situation.

I run HPDM 4.6.3610.21251

Thinclients are models T5530 and T5540 running Windows CE 6.05.657

DHCP and DNS records of offline thinclients are removed properly and no longer available.

Any help on getting HPDM to show up-to-date information at any time is very welcome. Thanks in advance.

[Chen_HPDM]

Could you please check the "PULL" value in Gateway Configuration Dialog? It is "0" by default which means HPDM Gateway will never proactively check the Agent status.

You can set a value on it so that hpdm GATEWAY will check DM Agent status periodically to ignore those

 "feak" devices.

[LeroyK]

Thanks for the advice. I have set the poll interval to 60 seconds. Hopefully the short interval wont have too much impact, but I hope to see the results a bit quicker.

However I think all thinclients will need to go offline atleast once before it takes effect, if it polls based on IP address only.

If it actually tries to match the IP addresses with a MAC address or other unique value it might be quicker.

Ill leave it running for a while and put an update here soon. 

[LeroyK]

So all thinclients have been shutdown on the main office during the weekend. 

Unfortunately adding a poll interval did not solve the issue.

Today 1 thinclient came online (HP-09-366), the other 2 remained shut down, but all 3 are shown as online.

Any other ideas what might cause this strange behavior? thanks in advance!

Edit: Is there any way to let HPDM check the device status based on client name, not IP address?

[Chen_HPDM]

Could you please send me the Gateway.log and let me know the device ID of these three units? (with same IP address)

Also please let me know the time when you shutdown all the devices so that I can easily find the useful information in Gateway.log.

As far as i know tt is not configurable to check device status based on client name.

[LeroyK]

I checked the logs, but found them to be empty. Seems like the Log Level was set to Error, so it didnt record anything.

I have set it to Debug. Ill sent the log tomorrow when it has some data.

the device ID's are visible in the picture, although a bit hard to read.

HP-08-031 001CC48CE453

HP-09-366 0025B3D65847

HP-15-016 18A90534E03F

All have the 192.168.20.52 IP Address.

I have also created a new rule to get the asset information at startup, dont know if it will do anything, but maybe worth a try.

[LeroyK]

Sorry for the delay.

I got the logs and will sent them to you.

Got a couple of thinclients as an example. There are many more, so if you need more please let me know.

HP-08-031 001cc48ce453 192.168.20.52 Shutdown 18-08-2015 2:48 PM
HP-15-001 78e7d1b42fad 192.168.20.52 Currently online, IP lease registered at 24-08-2015 7:49 AM.

HP001e0b399c2c 001e0b399c3c 192.168.20.59 Shutdown 19-08-2015 12:33 PM
HP-09-361 18a90534e19e 192.168.20.59 Currently online, IP lease registered at 24-08-2015 9:17 AM

[Chen_HPDM]

Hi,

I did see abnormal in gateway.log.1,  based on the sample of "HP-08-031 001cc48ce453 192.168.20.52" & "HP-15-001 78e7d1b42fad 192.168.20.52 "

2015-08-24 07:22:08 DEBUG [3280] .\TaskMgmt\AgentWalking.cpp@829    PollAgent - 00:1C:C4:8C:E4:53, poll result = 7, old status = off
2015-08-24 07:22:08 INFO  [3280] .\TaskMgmt\BuddyWOL\BuddyManager.cpp@162    update device 00:1C:C4:8C:E4:53 to 1.
2015-08-24 07:22:08 INFO  [3280] .\TaskMgmt\BuddyWOL\BuddyManager.cpp@314    updateDev=1

Gateway didn't receive any update then set device status from off to on (1).

Since I don't have quick answer to you, could you please submite an impact case to pull HPDM R&D in?

Please include below info in the case

1. Gateway.log.1

2. Screenshot of these two units with same IP on console

3. Agent log of the shutdown device (001cc48ce453 )

Thanks.

[LeroyK]

Hi Chen,

I'm not sure what you mean with "submit an impact case to pull HPDM R&D in?". Do you mean submit an official case with HP?

Thanks.

[Chen_HPDM]

Exactly, so that the case will be put in a higher priority and be responded ASAP.