topic Re: XMC failed to backup Avaya ERS switches via BOSS-SFTP script in ExtremeSwitching (VSP/Fabric Engine)

XMC failed to backup Avaya ERS switches via BOSS-SFTP script

Rafael_Lopez — Tue, 25 Sep 2018 02:19:00 GMT

When using the included "BOSS-SFTP" script to backup various recent builds of Avaya ERS switches, the backups fail to authenticate to XMC. I am not sure what credentials the script is using to authenticate to the XMC server or how to change it. I have tested an SFTP client from my PC to the XMC server using my and root credentials and I am able to get a session so I know XMC is listening. Here is syslog output from an ERS (10.33.20.10) running the script to connect to the XMC server (10.50.26.222) and failing to authenticate.

2018-09-24 13:11:12 Daemon.Info 10.33.20.10 Sep 24 13:11:13 ETR_Olive SSH:SSHC: Password Authentication failure
2018-09-24 13:11:12 Daemon.Info 10.33.20.10 Sep 24 13:11:13 ETR_Olive SSH:SSHC: ASCII CFG upload SFTP failure
2018-09-24 13:11:37 Daemon.Info 10.33.20.10 Sep 24 13:11:37 ETR_Olive SNMP:Trap: bsnConfigurationSavedToNvram
2018-09-24 13:11:42 Auth.Info 10.33.20.10 Sep 24 13:11:42 ETR_Olive SSH: [ssh]#6 Session closed (lost connection), IP address: 10.50.26.222, access mode: r/w
2018-09-24 13:11:42 Auth.Info 10.33.20.10 Sep 24 13:11:42 ETR_Olive SSH: [ssh]#6 Connection closed (lost connection), IP address: 10.50.26.222
XMC reports the results as follows:

Archive Save Management Center Archive: (10.33.20.10) Version Stamp: Sep 24, 2018 2:23:40 PM - % Failed to authenticate the connection. :

Re: XMC failed to backup Avaya ERS switches via BOSS-SFTP script

Ronald_Dvorak — Tue, 25 Sep 2018 02:29:00 GMT

You'd set the file transfer user/pw in the Administration > Options....

Re: XMC failed to backup Avaya ERS switches via BOSS-SFTP script

Rafael_Lopez — Tue, 25 Sep 2018 02:41:00 GMT

Awesome! That was the trick, didn't know where this was. We are new to XMC but it is already making things easier than what we were doing before.

Thanks for pointing me to the right place.

Re: XMC failed to backup Avaya ERS switches via BOSS-SFTP script

Magnus_Ludwig — Tue, 25 Sep 2018 11:33:00 GMT

Hi! Backup of ERS3626 not possible, cause filename too long:

XMC serverlog:

ERS3626(config)#copy config sftp address 10.10.10.80 filename /root/configs/tmp/10_10_10_232/nms.xsf username user password
% SFTP Filename too long (max length 30).

Someone knows a solution?
Thanks in advance

Re: XMC failed to backup Avaya ERS switches via BOSS-SFTP script

aloeffle — Tue, 25 Sep 2018 11:33:01 GMT

Hi all,
we see the same issue but no solution yet. Thanks for any help.
regards
Alex

Re: XMC failed to backup Avaya ERS switches via BOSS-SFTP script

rmu — Thu, 04 Oct 2018 14:57:00 GMT

Hi guys,

regarding this article
https://extremeportal.force.com/ExtrArticleDetail?n=000035775&q=%3C%40-%20%25%20SFTP%20Filename%...

there is a 30-character limitation in the boss code for filename

the default boss-sftp script copies the file into /root/config/tmp/10_10_10_232/nms.xsf

boss interprets the whole string as filename, so its too long.

provided resolution is to upgrade the switches to the last release.

BUT
- there is no hint to this problem in the release notes
- in my case with last ers3600 release (6.2.0.57) the problem still exists

i hope extreme will release a fix soon

nr
richi

Re: XMC failed to backup Avaya ERS switches via BOSS-SFTP script

rmu — Thu, 06 Dec 2018 00:02:25 GMT

Hi guys

there is a bugfix for ers3500 in release 5.3.9

for ers3600 there is no new release till april, 25th.
i hope there will a new version including this fix soon.

nr
richi

Re: XMC failed to backup Avaya ERS switches via BOSS-SFTP script

CptnBlues63 — Fri, 03 May 2019 03:02:45 GMT

Set the user/pw to what exactly? Tried my SNMP passwords (RO and RW) and tried also "anonymous" None of the above worked and I'm still getting the same error as the OP.

Help!

TIA

Re: XMC failed to backup Avaya ERS switches via BOSS-SFTP script

Violeta — Mon, 04 Nov 2019 17:39:36 GMT

Hello,

I have the same problem, but when changing "Anonymous" to root and password, it still gives me authentication error. In XMC I only have two users, root and administrator, and it doesn't work with either of them. Do I need an external server?

Best Regards!

Re: XMC failed to backup Avaya ERS switches via BOSS-SFTP script

rmu — Wed, 02 Dec 2020 21:37:02 GMT

Hi to Extreme

you recommend to use the root user of the linux system.

What is the reason for this?

As far as i know should the root user ony be used for system actions. For everything else you have a working user with fewer privileges.

Nevertheless, in all of my installations i have the root user and the working user "netsight".

Neither of the possible options works (default=anonymous, default anonymous/NAIM, root account, netsight account)

Both of my accounts fits the password guidlines you mentioned.

The only thing that works is TFTP, but in a secure environment, this is not an option.

It seems to me that you haven't done your homework in implementing modern user / permissions management.

So whats the solution for this?

NR
Richi
PS: i am running the latest xmc version.

Re: XMC failed to backup Avaya ERS switches via BOSS-SFTP script

TachyBirdy — Tue, 18 May 2021 01:42:34 GMT

Hello - I’ve been meaning to reply to this.

Our Security engineers said NO WAY to the root account being used in this manner.

I asked the Linux sysadmin to create an account (example name of “secure_backup”)

Then from Administration → Options → Inventory Manager → Data Storage we set the directory path to:

/home/secure_backup

Then from Administration - → Options → Inventory Manager → File Transfer → SFTP Server Properties → Login Information, we unchecked Anonymous and filled in the Username and Password

Then from Administration - → Options → Inventory Manager → File Transfer → SFTP Server Properties → Firmware Directory Path, we set the path to:

/home/secure_backup/firmware/images/

Then from Administration - → Options → Inventory Manager → File Transfer → SFTP Server Properties → Root Directory Path, we set the path to:

/home/secure_backup/

And we were all set.