Network Management

Hi,

It doesn't seem as IMC has got support for IOS-XR (config backup, deploy, software etc.).

Does anybody know if this is on the road map?

Is there a road map, by the way?

Cheers,

Rick, Sweden

Hello Rick,

IMC definitely has an adapter (folder with scripts for Config Center) for IOS-XR, as you can see here:

EDIT: Sorry it seems the forums bugged out when I put a screenshot in my post, and most of my answer was lost.

For IOS_XR, the script folder is located under iMC\server\conf\adapters\ICC\Cisco. IMC determines which adapter to use based on the SysOID of the device, so it's possible that your device model isn't yet listed in the adapter-index.xml file in the folder path I've listed.

Open the adapter-index.xml for ICC\Cisco in a text editor, find the <adapter name="CiscoIOS_XR">, and add a new <sysoid>sysoid here</sysoid> entry with the SysOID of your device, if you don't see it listed there already. Then just save the file and restart IMC and test if it's working.

If it's still not working correctly, you can check the iMC\server\conf\log\imccfgbakdm<datestamp>.txt file for configuration backup and restore errors, or imcupgdm.txt files for software upgrade errors.

For an IMC Roadmap, please contact your HPE Sales Rep or Account Manager.

Hope that helps.

Hi and thanks for your answer.

Yep, I had aldready put the device's sysOID in the adapter-file, under IOS-XR.

There is no "backup_running_config_scp.tcl" in the CiscoIOS_XR folder.. CLI or TFTP method is not applicable in our environment, it must be SCP.

The log iMC\server\conf\log\imccfgbakdm<datestamp>.txt contains the following..

2019-11-12 09:39:04.382 [WARNING (32)] [THREAD(3906939760)] [CComponentAdapter::checkAccessTypeMatchTransferProtocol()] transfer protocol does not match access type,iTransferProtocol=4,iAccessType=3

2019-11-12 09:39:04.382 [WARNING (32)] [THREAD(3906939760)] [CComponentAdapter::isDevSupportServiceAction()] transfer protocol does not match access type,ServiceName = ConfigBackup,commandName=ICC,iTransferProtocol=4,iAccessType=3

2019-11-12 09:39:04.383 [WARNING (102)] [THREAD(3906939760)] [qvdm::QvGetConfItem] Fail to get item[thirdpart_scripts] in file[/opt/iMC/server/bin/../../server/conf/qvdm.conf].

2019-11-12 09:39:04.384 [WARNING (32)] [THREAD(3906939760)] [CComponentAdapter::checkAccessTypeMatchTransferProtocol()] transfer protocol does not match access type,iTransferProtocol=4,iAccessType=3

2019-11-12 09:39:04.384 [WARNING (32)] [THREAD(3906939760)] [CComponentAdapter::isDevSupportServiceAction()] transfer protocol does not match access type,ServiceName = ConfigBackup,commandName=Custom,iTransferProtocol=4,iAccessType=3

2019-11-12 09:39:04.384 [ERROR (18)] [THREAD(3906939760)] [CComponentAdapter::isDevSupportServiceAction()] fail to call getDevAdapterName().DevID=4175,ServiceName = ConfigBackup

2019-11-12 09:39:04.384 [WARNING (32)] [THREAD(3906939760)] [CComponentAdapter::checkAccessTypeMatchTransferProtocol()] transfer protocol does not match access type,iTransferProtocol=4,iAccessType=3

2019-11-12 09:39:04.384 [WARNING (32)] [THREAD(3906939760)] [CComponentAdapter::isDevSupportServiceAction()] transfer protocol does not match access type,ServiceName = ConfigBackup,commandName=ICC,iTransferProtocol=4,iAccessType=3

2019-11-12 09:39:14.387 [ERROR (18)] [THREAD(3906939760)] [CScriptProcessor::exec()] Failed to execute by cli method.

Hello Rick,

Sorry for the delay in getting back to you.

If you must use SCP and IMC doesn't have the scripts for it, that would explain why it doesn't work, and complains about transfer protocol not matching access type.

Since there's no backup_running_config_scp.tcl, you could try creating one based on other scripts with the same name in other folders under the Cisco adapter.  For example CiscoIOSGeneric folder has SCP support that you can use for reference.

The alternative to have it implemented in a future IMC version would be to contact your HPE Sales/Account Mgmt representative, and ask them to open a Feature Request for SCP Support on IOS-XR. Note that Engineering might need to request some logs and/or attended remote access to the IOS-XRs.

If you'd like to try adding it yourself, you would need to add the respective .tcl scripts, like the backup_running... one I've mentioned above, as well as a few others:

1) initialize.tcl if any new variable declarations are needed for the SCP method

2) CiscoIOS_XR_Config_Backup_Builder.xml with entries for the new SCP method

3) CiscoIOS_XR_Config_Backup_Builder_Script.xml with entries for the new SCP method

For more details please refer to the Extending and customizing functions to support third-party devices chapter in the IMC Administrator Guide for more details, or search online for "IMC customization" to find another helpful unofficial guide.

Hope that helps and you can get this issue sorted out.