LMS 3.2: problem with HUM due to device deleted

[a.perrichon]

Hi,

I have an issue with HUM 1.2.1. I have deleted a device in Common Services, Device Management. The problem is that there was a poller configured with this device in HUM. I am now unable deleting the poller.

[Nael Mohammad]

Try adding the device back to Common Services, go to HUM, delete the poller, and remove the device.

1. Add the device back to common services if possible.

2. Go to HUM, delete the poller.

3. Remove device from Common Services.

If that does not work, you have two options:

1. Stop the UPMProcess from the cli using "pdterm UPMProcess".

2. Go to HUM and delete the poller.

And if that fails, reinit the HUM db or we can provide you with a SQL query to delete the poller from the database.

[a.perrichon]

Hi,

OK I will try it.

Just to give more information :

The first problem was that in DFM the device stayed in learning state. I tried to increase timeout, delete the device, rediscover it, ... But the device still in learning state.I notice a thread talking about possible problem with the SNMP engineID. I configured the device with a new SNMP engineID, and deleted it using Common Services/Device Management.

And the problem with HUM appeared ...

I have already rediscovered the device with his new SNMP engineID. All is working in RME and in Campus Manager. The problem still the same in HUM.

I will try the other actions that you suggested.

Rgds

[a.perrichon]

it doesn't work using "pdterm UPMProcess"

Is it possible to have a solution which doesn't reinit the HUM database ?

Thanks in advance for the helps