IPSA reports config version mismatch, despite correct alias command existing
(Doc ID 1435093.1)
Last updated on SEPTEMBER 21, 2016
Applies to:Oracle Communications IP Service Activator - Version 5.2.4 and later
Information in this document applies to any platform.
The customer was having an issue where the IPSA config version alias was sent, but it was not showing up in the device audit:
While attempting to execute a device audit on an NP managed Cisco device. The audit screen shows an IPSA Config version of 2012-03-09T08:03:09.456Z while the device config version is empty. The following command is shown in red at the bottom of the audit pane 'alias exec IpsaConfigVersion 2012-03-09T08:03:09.456Z' and the following critical fault object is created:
Fault:"Unexpected IPSA Config Version detected on device - IPSA Version: 2012-03-09T08:03:09.456Z Device Version: "
The running config contains the correct config version:
mi-za-cpt-mspe2#sh run | inc IpsaConfigVersion
alias exec IpsaConfigVersion 2012-03-09T08:03:09.456Z
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document