UIM - Cannot create or delete a maintenance schedule

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

When creating a new maintenance schedule or deleting an existing one you may see the following error (either in the wasp.log file or browser will display it): 

Details:

[http-nio-80-exec-8, com.firehunter.ump.exceptions.DataFactoryException] (4) not found, Received status (4) on response (for sendRcv) for cmd = 'nametoip' name = '/<Domain address>/<primary HUb address>/<robot address>/maintenance_mode'
    at com.nimsoft.nimbus.NimSessionBase.sendRcv(NimSessionBase.java:627)
    at com.nimsoft.nimbus.NimSessionBase.sendRcv(NimSessionBase.java:578)
    at com.nimsoft.nimbus.NimSessionBase.getHostAndPortForName(NimSessionBase.java:443)
    at com.nimsoft.nimbus.NimNamedClientSession.<init>(NimNamedClientSession.java:33)
    at com.nimsoft.nimbus.NimObjectSender.connectNamed(NimObjectSender.java:83)
    at com.nimsoft.nimbus.NimRequest.sendImpersonate(NimRequest.java:258)
    at com.nimsoft.nimbus.pool.NimRequestPool.sendImpersonate(NimRequestPool.java:97)
    at com.nimsoft.nimbus.pool.NimRequestPool.sendImpersonate(NimRequestPool.java:79)
    at com.nimsoft.nimbus.pool.NimRequestPool.send(NimRequestPool.java:71)
    at com.nimsoft.nimbus.pool.NimRequestPoolInstance.send(NimRequestPoolInstance.java:197)
    at com.nimsoft.nimbus.pool.NimRequestPoolInstance.send(NimRequestPoolInstance.java:156)
    at com.firehunter.umpportlet.PDSUtils.send(PDSUtils.java:60)
    at com.firehunter.operatorconsole.service.MaintenanceScheduleService.getNextFireTimeFromPDS(MaintenanceScheduleService.java:354)
    at com.firehunter.operatorconsole.service.MaintenanceScheduleService.getNextFireTimes(MaintenanceScheduleService.java:333)
    at com.firehunter.operatorconsole.service.MaintenanceScheduleService.getSchedules(MaintenanceScheduleService.java:301) .........

Environment

Any UIM Version

Resolution

The maintenance_mode probe address information was missing the ump_common section in the wasp probe, or the key configured for maintenance_mode was wrong (it is case sensitive)

Make sure, that the OC wasp probe, has the correct ump_common configuration pointing to the maintenance_mode probe.

The string for the "maintenance_mode" key should be identical to the address of the maintenance_probe on the primary hub. 

 

/<Domain address>/<primary hubb address>/<robot address>/maintenance_mode