Legacy HDS Forums

HTnM Agent problems after storage change?

Discussion created by Legacy HDS Forums on Mar 7, 2013
Latest reply on Mar 8, 2013 by Legacy HDS Forums

Originally posted by: Alastair



Like everyone, migration from one storage sub-system to another is a fact of life. However it appears to be something that HTnM doesn't really like!

After such migrations I have a number of servers where HTnM appears to have 'lost' the relationship between 'Device File' and the storage. Whilst HTnM continues to collect data against the Device Files, it now shows 'no data' for the 'Storage System', 'Port', 'LDEV' and 'Parity Group' details. This makes following the performance details from server to sub-system difficult.

I was hoping that some sort of forced 'refresh' was possible, but have been unable to find anything in the manual. I've tried an agent upgrade (which had no effect), but would prefer to avoid an agent uninstall/re-install as that would certainly lose the historical data.

Has anyone else experienced this and/or got a workaround for it?

Outcomes