adapter-index.xml and updating.

[dasi66]

Every time I update IMC, and It's time again now, I need to add my special OID's that are not supported. Is it a way of fix this? I do want the new adapter-index.xml if there are new OID's in the new release, But how to check this?

I usually back up adapter-index.xml and some other files and owerwrite the new update but it's not a very convenient way of doing it.

[jguse]

Hello,

Currently the only way to preserve your adapter customizations is to back up all modified adapter folders & files before upgrading - and then compare any files that were changed with your own backup. Tools like Notepad++ can compare text files quite effectively, though it still requires some manual effort.

While I agree with you that there should be a better way, this would need to be added via a Feature Request via your HPE Sales/Account Mgmt channel.

[dasi66]

Hi, I have major trouble now after upgrading to iMC PLAT 7.3 (E0705P07)

Cannot get backups for Nexus 5000 and7000 to work. Adapters are updated as they were before upgrade. All OID should be there in the right place.

5000/7000: Result: Script exist error.

Information:

Task or step detail does not exist. Possible reasons: 1.Task has not been run. 2.Task does not exist.

All these switches worked well before upgrade.

Tell me if you want any logs for this. This is a nightmare...

[jguse · Accepted solution]

Hello,

That error "Script exist error." means that there is an issue in the scripts themselves. For example an undeclared variable being called or a typo somewhere etc... and usually the imccfgbakdm log will show you an error message indicating on which line of the TCL scripts the issue is located. It will possibly also show in the Error Details output of your failed config backup - might be worth checking there.

If not, try setting "imccfgbakdm" process to DEBUG via System Configuration > Log Configuration and then attempting the backup again. Then you can check the log with the same name and current date in iMC\server\conf\log folder and see if you can find the exact error message about where your scripts failed. If you upload the full imccfgbakdm log somewhere and share the link via PM to me I can also have a look at the log myself.

[dasi66]

Thank you Justin. Somthing was wrong in the folders CiscoNX5K, CiscoNX7K. Probably because I created these long before Nexus was supported.

I copied contents from CiscoNX9K, as was working fine and changed som names and it works.

[root@x5378 Cisco]# ls -la
total 120
drwxr-xr-x 24 root root 4096 Oct 27 10:41 .
drwxr-xr-x 41 root root 4096 Jan 14 2020 ..
-rw-r--r-- 1 root root 29436 Oct 26 19:34 adapter-index.xml
-rw-r--r-- 1 root root 29009 Oct 26 12:20 adapter-index.xml.orig
drwxr-xr-x 3 root root 4096 Jan 14 2020 CiscoAC
drwxr-xr-x 3 root root 37 Jan 14 2020 CiscoAS54xx
drwxr-xr-x 3 root root 4096 Oct 22 12:43 CiscoASA
drwxr-xr-x 3 root root 4096 Jan 14 2020 CiscoC2980G
drwxr-xr-x 3 root root 4096 Jan 14 2020 CiscoCatNative
drwxr-xr-x 3 root root 37 Jan 14 2020 CiscoESR
drwxr-xr-x 3 root root 37 Jan 14 2020 CiscoIOS12K
drwxr-xr-x 3 root root 37 Jan 14 2020 CiscoIOS7K
drwxr-xr-x 3 root root 4096 Jan 14 2020 CiscoIOSGeneric
drwxr-xr-x 3 root root 37 Jan 14 2020 CiscoIOSGenericNoLog
drwxr-xr-x 3 root root 37 Jan 14 2020 CiscoIOSGenericSwitch
drwxr-xr-x 3 root root 37 Jan 14 2020 CiscoIOSL3Switch
drwxr-xr-x 3 root root 37 Jan 14 2020 CiscoIOSSwitchRoutingModule
drwxr-xr-x 3 root root 37 Jan 14 2020 CiscoIOSUndiscovered
drwxr-xr-x 3 root root 4096 Jan 14 2020 CiscoIOS_XR
drwxr-xr-x 2 root root 4096 Oct 22 12:43 CiscoNX5K-orig
drwxr-xr-x 2 root root 4096 Oct 27 10:37 CiscoNX7K
drwxr-xr-x 3 root root 4096 Oct 26 19:26 CiscoNX7K-orig
drwxr-xr-x 2 root root 4096 Aug 7 2019 CiscoNX9K
drwxr-xr-x 3 root root 4096 Jan 14 2020 CiscoNXOSSNMP
drwxr-xr-x 3 root root 4096 Jan 14 2020 CiscoSNMP
drwxr-xr-x 6 root root 98 Jan 14 2020 .svn
[root@x5378 Cisco]#

[dasi66]

All ok now.