Avaya Midsize Enterprise SFTP backup

[ejvl]

Hi,
One of our customers have a Midsize Enterprise Server 6.3.1.08003.0 installed with High Availability active.
The customer have a SFTP server installed for backup. In the past is works fine, but now the customer have replaced this SFTP server by an new server.
The backup on Communication Manager works fine, no problems!
When I'll try to make a backup on the MES server, System Platform, Server Management, Backup/Restore, I fill in the exact same details as on the Communication Manager, but doesn't work.
When I start a Putty session on Cdom, I give the command: "ssh username@ipadres" it works fine, but not in webbrowser! I've get an error.
See attached file where you can see that it works fine on Putty, but not in webbrowser.

Any ideas?

 

[janni78]

Are you using SFTP on CM as well or SCP?

If it stopped working when they changed SFTP server then there's the issue.


"Trying is the first step to failure..." - Homer

 

[ejvl]

On CM we use SFTP, that works fine.
I understand that the problem is that they changed the SFTP server, but I can still login by Putty on CDOM on this SFTP server and CM backup works fine, so the SFTP server works fine I think, otherwise the CM or CDOM Putty cannot login to this SFTP server.
Putty CDOM or browser is the same IP, so I don't understand why the Putty works and the web browser not.

 

[janni78]

Can you access /opt/avayabackup when you login with SSH?

"Trying is the first step to failure..." - Homer

 

[janni78]

Which version is the System Platform?

"Trying is the first step to failure..." - Homer

 

[ejvl]

@janni78:
When I login with putty, SSH, to CDOM, I can login to the SFTP server with command: "sftp username@ipadres". Then I can access the directory by cd opt and cd avayabackup.
I can make directory's with command mkdir, so I think I have full access to the folder of this SFTP server?

Here is the softwareversion:
[admin@mes01a-cdom ~]$ swversion
=======================================================================
System Platform Information - Domain-0
=======================================================================
Version 6.3.1.08003.0
Software UUID 0c38344e-165d-4873-ac4b-c162dd108e1d
SVN Revision 18335
Server Type ProLiant, DL360p, Gen8
Kernel Version Linux 2.6.18-348.16.1.AV2.el5xen
Initial Installation Time Dec 4 11:51:01
=======================================================================
System Platform Information - cdom
=======================================================================
Version 6.3.1.08003.0
Software UUID 0c38344e-165d-4873-ac4b-c162dd108e1d
SVN Revision 18335
Kernel Version Linux 2.6.18-348.16.1.AV2.el5xen
Initial Installation Time Dec 4 11:51:01
Solution Template Information - Midsize_Ent
=======================================================================
Platform.Product Midsize_Ent
Platform.Vendor Avaya Inc.
Platform.Version 6.2.2.0.1120
Platform.Status Enabled
Initial Installation Time Dec 4 16:57:51

 

[kyle555]

just for kicks, is the IP of the old/new backup server the same?
is it possible that something in cdom cached the ssh keys for the old sftp server and the backup is failing on that WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED error?
Does that SFTP server have another NIC you can put a different IP on just to test the idea?
Or could you just nuke the ssh keys cdom is using for that backup?

cdom or dom0 should have a /vspdata/backup/vm-backup.log that has some more information.

 

[janni78]

You say you can access it with "cd opt" and "cd avayabackup"

That's not the same as "/opt/avayabackup" since you start on your home directory.

What if you write "cd /opt/avayabackup"?
Otherwise the backup path should be "./opt/avayabackup"


"Trying is the first step to failure..." - Homer

 

[BIS]

The browser hint sounds like they changed from passive to active ftp - so check that.

 

[ejvl]

Sorry for the delay, but the answer is:

https://support.avaya.com/forums/showthread.php?p=28854

After a lot of research, reading and trial and error I've got a solution / answer to my problem.

I check'd my ssh log files for errors and found this error;
"Oct 26 16:50:31 ubuntu-avbkup sshd[2024]: fatal: Unable to negotiate with xxx.xxx.xxx.56 port 55751: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1,diffie-hellman-group-exchange-sha1 [preauth]"

I added the following lines to my sshd_config file;
"KexAlgorithms +diffie-hellman-group1-sha1"
"KexAlgorithms +diffie-hellman-group-exchange-sha1"

I was still getting the "Algorithm negotiation fail" message but I got a different error message in my ssh log file:
"Unable to negotiate with xxx.xxx.xxx.56 port 34976: no matching cipher found. Their offer: aes128-cbc,3des-cbc,blowfish-cbc [preauth]"

I had to add another line to my sshd_config file:
"Ciphers aes128-cbc,3des-cbc,blowfish-cbc"

Now my backup files are being uploaded to my Ubuntu Server via SFTP.