This is not a new behavior. Orion has never had any ability to remap volumes. When you think about it, in most cases it's an impossible task to handle programmatically. Usually what triggers this situation is the volume name was changed, so you can't track this by the volume label. When the volume name was changed, the volumes were assigned new indexes, so you can't follow the index ID. There's really no single piece of consistent data available via SNMP to identify this as an existing volume vs a newly added volume that isn't yet monitored by Orion.
↧