How to backup Aruba 8400 series switch with IMC 7.3 (E0703)

[cfritz]

Added an Aruba 8400 series switch to IMC version 7.3 (E0703). Switch is running 10.03.0040. When IMC attempts to backup I see the following in the switch log:

|Error while copying configs. Error: error in remote file transfer
2019-11-18T18:41:02.517774+00:00 Core-Top hpe-config[30054]: Event|6801|LOG_INFO|AMM|1/5|Copying configs from: running-config to: URL: tftp://1.1.1.1/running_2856122722.cfg, in format: cli, using vrf: default

I believe what may be the problem is that it is using the "default" VRF when somehow I need to tell IMC to use the "mgmt" VRF. From the switch CLI, I can manually tftp the config to the IMC server. Any Ideas on how to fix this. Thank you.

[jguse]

Hello,

The IMC Config Center scripts are generally able to adapt to whichever VRF (VPN Instance) you prefer, there's a setting in the Configuration Center Options for this. Navigate to Configuration Center > Options > VPN Instance, and configure your Aruba 8400 Switches to use the VRF name 'mgmt' instead.

Aruba 8400 series should be using the IMC Adapter (scripts) under C:\Program Files\iMC\server\conf\adapters\ICC\Aruba Networks\Aruba8400, where I can see that scripts like backup_running_config_tftp.tcl include the following TCL code:

set my_cmd "copy running-config tftp://$TFTPServer/$TFTPFile cli"

if { $VpnName != "" } {
   append my_cmd " vrf $VpnName"
}
send "$my_cmd\r"

Please try setting VPN Instance in the options and let us know if that works.

[parnassus]

Hi!

I added:

set VpnName mgmt

to tcl script thus:

#**************************************************************************
#Identification: backup_running_config_tftp
#Purpose:        backup running configuration by cli via tftp.
#**************************************************************************

set timeout $very_long_timeout
set WARNING_RESULT true
set my_cmd "copy running-config tftp://$TFTPServer/$TFTPFile cli"
set VpnName mgmt

if { $VpnName != "" } {
   append my_cmd " vrf $VpnName"
}
send "$my_cmd\r"
expect {
    -re "Invalid|Incomplete" {
        set ERROR_MESSAGE "Could not copy the running-configuration to a tftp server."
        set ERROR_RESULT true
        expect $enable_prompt
    } "Unknown command" {
        set ERROR_MESSAGE "Unknown command."
        set ERROR_RESULT true
        expect $enable_prompt
    } "Peer unreachable" {
        set ERROR_MESSAGE "Unable to reach TFTP host."
        set ERROR_RESULT true
        expect $enable_prompt
    } "Error copying" {
        set ERROR_MESSAGE "Unknown host."
        set ERROR_RESULT true
        expect $enable_prompt
    } "Cannot overwrite" {
        set ERROR_MESSAGE "Cannot overwrite active configuration file."
        set ERROR_RESULT true
        expect $enable_prompt
    } "Illegal" {
        set ERROR_MESSAGE "Illegal source file name."
        set ERROR_RESULT true
        expect $enable_prompt
    } "timeout" {
        set ERROR_MESSAGE "TFTP response timeout."
        set ERROR_RESULT true
        expect $enable_prompt
    } "File Not Found" {
        set ERROR_MESSAGE "TFTP File Not Found."
        set ERROR_RESULT true
        expect $enable_prompt
    } "unsupported file format" {
        set ERROR_MESSAGE "unsupported file format."
        set ERROR_RESULT true
        expect $enable_prompt  
    } "Success" {
        expect $enable_prompt
    } "100%" {
        expect $enable_prompt
    } $enable_prompt {
    }
}

if { $ERROR_RESULT != "true" } {
    set WARNING_RESULT false
}
set timeout $standard_timeout

then tried:

 Aruba 8320 logged exactly one line:

2019-11-20T13:41:18.565927+01:00 vsx-1 hpe-config[8409]: Event|6801|LOG_INFO|AMM|-|Copying configs from: running-config to: URL: tftp://<IP-Address-of-IMC>/running_2857634872.cfg, in format: cli, using vrf: mgmt

Result seems encouraging despite backup job's result messages reported above:

the cfg file is perfect.

Given the result above...it would be interesting to understand why that failure...but I think I've understood the culprit...that manually launched backup job (it's an auto backup job I executed) first tries to backup startup config then the running config...I haven't yet adapted the startup related script (as the running related one above).

Does it sound reasonable?

[parnassus]

Modified both:

/opt/iMC/server/conf/adapters/ICC/Aruba Networks/Aruba8400/backup_running_config_tftp.tcl

/opt/iMC/server/conf/adapters/ICC/Aruba Networks/Aruba8400/backup_startup_config_tftp.tcl

by hardcoding the VpnName variable with the VRF mgmt and finally both configs are backed up flawlessly:

 if no hardcoding is tolerated...mine was a fast test...do the same by leaving untouched the related tcl files and configure this as suggested:

way more elegant.

Aruba 8320 indeed logs:

2019-11-20T14:13:02.618828+01:00 vsx-1 hpe-config[18923]: Event|6801|LOG_INFO|AMM|-|Copying configs from: running-config to: URL: tftp://<IP-Address-of-IMC>/running_2857653912.cfg, in format: cli, using vrf: mgmt
2019-11-20T14:13:06.590145+01:00 vsx-1 hpe-config[18999]: Event|6801|LOG_INFO|AMM|-|Copying configs from: startup-config to: URL: tftp://<IP-Address-of-IMC>/startup_2857653962.cfg, in format: cli, using vrf: mgmt

+1 to jguse.

[cfritz]

Thank you for you assistance, this helped.

[cfritz]

Thank you for your assistance all of your screenshots and code helped. Very much appreciated. Backups are now successful.

[parnassus]

Real credit goes to jguse (Justin)!

Works like a charm...+1 Kudo to Justin...he is a real IMC Guru.

[jguse · Accepted solution]

Hello,

Thank you both for the feedback, glad to hear it works now!

Just to clarify - in general the clean and officially supported way to add VPN Instance is via the Config Center Options, as you've mentioned. I've posted the excerpt from the .tcl script only to prove that the scripts already include code to handle VPN instance configuration from the GUI.

While manually modifying the .tcl scripts works too when done correctly, it is not officially supported. It's normally only something that should be done as a workaround, while you open a support case, and have Engineering add/change code in the scripts for you to fix the issue.

[parnassus]

Absolutely Justin! Let me just add that VPN term (but why VPN instead of VRF?) would have been something impossible to guess without learning what you shown us...life is really a matter of giving things the right name...I would have looked for VRF forever...without knowing those tcl files (and their purpose).

[parnassus]

Hi! just a follow up.

The HPE IMC 7.3 E0705P04 software release (April 2020) introduced a new feature: "Configure VRF name for file transfer for Aruba OS-CX. Service -> Configuration Management -> Option -> VPN Options, VPN instance name".