Hello,
iMC supports many different Cisco devices out of the box. If it doesn't work directly, add the SysOID of the devices to the iMC\server\conf\adapters\ICC\Cisco\adapter-index.xml file under the adapter (script folder) that should work, like CiscoIOSGeneric adapter.
For more details about how you can customize iMC, I'd recommend searching online for 'customizing iMC', there is a great third-party document about this. You can customize it to back up/restore any devices that have a text-based configuration (and even some devices like F5 with a .tar.gz archive).
Justin
Working @ HPE
Hello Jesper,
That error message is misleading, as it usually means that iMC actually cannot find the adapter to use for backup.
First, make sure the device is recognized properly in iMC. That means under System > Resource Management > Device Definition > Device Model tab, you should be able to find a result when searching for your device's SysOID (shown on the Device Details page for each device). If the SysOID is not associated with a Model definition in iMC, you won't be able to perform the backup.
Second, navigate on iMC server to iMC\server\conf\adapters\ICC\Cisco\ and open adapter-index.xml in a text editor. Here you will see the list of SysOIDs which are associated to various different adapters, since the scripts needed to backup an ASA will obviously need to differ from those used to backup an IOS switch, and so on. Make sure the SysOID of your C9300 exists in this file - most likely it does not, so you should add it in the same format as the other SysOIDs, under the adapter that you think will most likely work. In this case, I would suggest adding it under CiscoIOSGeneric as this works with IOS-based switches. Save the file after you added the <sysoid> entry.
Lastly, restart iMC (or at least the imccfgbakdm process) and then synchronize the device (Device Details > Actions). Then try the backup again - does it work now, or does it provide a different error at least?
Justin
Working @ HPE
Hi Justin,
Please see attached screenshot. As you can see I don't have a Cisco adapter in this path, iMC\server\conf\adapters\Cisco\adapter-index.xml
There are however Cisco adapters in: iMC\server\conf\adapters\GenericConfig. This .xml only have very few devices.
Is it pissible to copy adapter index from iMC\server\conf\adapters\ICC to iMC\server\conf\adapters\Cisco\adapter-index.xml ???
Kind regards,
Jesper
Hello Jesper,
Sorry about that, I posted an incomplete path above. It should be iMC\server\conf\adapters\ICC\Cisco instead. I'll correct this. ICC folder contains all the adapters for the Intelligent Configuration Center, which handles the config backup/restore and software deployment features. You should have an adapter-index under that folder that you can edit.
Justin
Working @ HPE
Hello Jesper,
Glad to hear one of them is working now. If that is the full excerpt from adapter-index.xml, I'd note that these SysOIDs are listed twice - you might want to remove the duplicates (not sure if it would cause errors but it's worth a shot):
<sysoid>1.3.6.1.4.1.9.1.2500</sysoid>
<sysoid>1.3.6.1.4.1.9.1.2501</sysoid>
Regarding 9400 and 9600, the errors seem like something is not working as expected with iMC's adapter scripts. You can debug it via System > System Configuration > Log Configuration and setting the imccfgbakdm to DEBUG level, then testing the backup again. There's also a link there to download the logfile afterwards (ignore IMF log, that is not relevant).
You should see the execution sequence of the adapter scripts and the output from the device in there, look for entries like:
[INFO (0)] [THREAD(8528)] [CTclExecutor::exec_impl()] Begin to exec:
[INFO (0)] [THREAD(8528)] [CTelnetScriptProcessor::gotoMode()] Begin, ip: <your-device-ip>, current mode: , new mode: initialize
[INFO (0)] [THREAD(8528)] [CTclExecutor::exec_impl()] Begin to exec: C:/Program Files/iMC/server/bin/../../server/conf/adapters/ICC/Hewlett Packard/HPProcurve2500/backup_startup_config_scp.tcl
[ERROR (0)] [THREAD(8528)] [CTclExecutor::exec_impl()] Error occured to exec cmd: C:/Program Files/iMC/server/bin/../../server/conf/adapters/ICC/Hewlett Packard/HPProcurve2500/backup_startup_config_scp.tcl, error message: Timeout to login. No message recive from device!
[INFO (0)] [THREAD(8528)] [CTclExecutor::exec_impl()] Finished.
[WARNING (11)] [THREAD(8528)] [CSSHScriptProcessor::exec_step()] Fail to call oTclExecutor.execFile(), will try next command. AdaptName = HPProcurve2500, DevIP = <your-device-ip>, command script name = backup_startup_config_scp.tcl.
[INFO (0)] [THREAD(8528)] [CCLIScriptProcessor::login_impl()] Begin ...
[INFO (0)] [THREAD(8528)] [CCLIScriptProcessor::login()] Begin ...
[INFO (0)] [THREAD(8528)] [CTclExecutor::exec_impl()] Begin to exec: spawn plink.exe -P 22 <your-username>@<your-device-ip>
The example above is from a failed HP 2500-series backup via SCP, but you should be able to find something similar at the timestamp when your backup started. Note the error above was caused by a timeout, which is probably different in your case, but it's the kind of log entry you want to look for. Shortly thereafter you will see the sequence of .tcl scripts rund, which can also reveal which script, if any, failed to run properly.
Justin
Working @ HPE
Hi Justin,
I have now tried to set imccfgbakdm to "DEBUG" Can you see what and why something goes wrong. My debug outpunt doesn't look like you example.
Kind regards,
Jesper
Hi Jesper,
Looking at the timestamp in your screenshots, it appears that those logs are from midnight on your server - probably not when you tested the backup, right? You'll want to look through the log for the timestamp when the IMC GUI shows that the backup started, and then you should be able to find something similar.
PS. I'd highly recommend a tool like Notepad++ for analyzing iMC logs, as Notepad tends to have difficulties handling larger logs and also doesn't have good search functionality etc.
Justin
Working @ HPE
Hello,
For the first (9600), it looks like iMC cannot find the correct adapter to use:
adapter_name = 'N/A',sysoid = '1.3.6.1.4.1.9.1.2871',
A few things you can check...
* Make sure you have defined the device model for this SysOID via Resource Management > Device Definition
* Make sure iMC is provided with SNMP RW and full CLI access, and the CLI Login Type (Telnet/SSH) is set
* Verify the SysOID of the switch is indeed in the adapter-index.xml file under the correct adapter
* Try deleting the device from iMC and re-adding it, this will force it to update the adapter
One more thing - if you use Telnet as CLI access, iMC expects that you will also use TFTP/FTP as transfer protocol, and with SSH it will expect a secure transfer protocol like SCP/SFTP, otherwise it will complain (in the log, "transfer protocol does not match access type").
You can check which protocols and methods (CLI or SNMP-triggered backup) iMC detected as supported for your device by going to Configuration Center > Options page. Device Capability Set shows you this. The default transfer protocol used is on the next tab "File Transfer Mode", and further down on the page you can define a "Single Device Transfer Mode" for individual devices that do not work with the default transfer mode.
Keep in mind that for FTP and SFTP Server modes you must set up a third-party FTP solution on iMC's server for it to work. Personally I'd recommend TFTP or SCP for ease of setup where supported.
---
Regarding the 9400, what is the Cisco C9K adapter? Did you create a custom adapter for these switches? If so, which existing adapter are the scripts based on? I'm asking since my own iMC installations don't have such a folder.
2020-09-28 10:16:46.850 [ERROR (21)] [THREAD(6252)] [CDevAdapter::parserAdapterIndexProcess()] get Doc Node error, file: D:\Program Files\iMC\server\bin\..\..\server\conf\adapters\ICC\Cisco\Cisco C9K\adapter.xml
2020-09-28 10:16:46.850 [ERROR (21)] [THREAD(6252)] [CDevAdapter::getAdapterService] fail to call parseAdapterIndex.AdapterName = Cisco C9K
2020-09-28 10:16:46.850 [WARNING (21)] [THREAD(6252)] [CComponentAdapter::getAdapterService] fail to call poAdapter->getAdapterService().service name = ConfigBackup
2020-09-28 10:16:46.851 [WARNING (21)] [THREAD(6252)] [CComponentAdapter::isDevSupportServiceAction()] Can not support specify service.DevID=3423,ServiceName = ConfigBackup,adaptername=Cisco C9K
The error message seems to indicate there's a problem with the adapter.xml file, which is a file located in each adapter folder that defines the services (config backup, deployment etc) that are available for the devices using it. If you create a custom adapter folder, note that they do not have any blank space in the name. Please make sure there is no space - Cisco C9K should be changed to CiscoC9K and adapter-index.xml updated accordingly too.
Justin
Working @ HPE