Problems With (Test SFTP) On MediaSense Archiving Configuration Page
Problems With (Test SFTP) On MediaSense Archiving Configuration Page
Introduction
Prerequisites
Requirements
Components Used
Problem: Test SFTP Button Fails Due to an SSH Algorithm Negotiation Failure
Solution
Bugs
Related Information
Introduction
This document describes how to resolve a Secure SHell (SSH) algorithm negotiation failure that
may occur when you are configuring a Secure File Transfer Protocol (SFTP) server to archive
Cisco MediaSense (MS) recordings.
Prerequisites
Requirements
● Cisco MediaSense
● Linux server administration
Components Used
The information in this document is based on Cisco MediaSense version 10.5.1 and above.
The information in this document was created from the devices in a specific lab environment. All of
the devices used in this document started with a cleared (default) configuration. If your network is
live, make sure that you understand the potential impact of any command.
Solution
Look in the ORA-oraadmin logs for the SFTP configuration that is saved and the result of the Test
SFTP button test.
You get a request to update archive configuration. The SFTP server has IP 10.1.2.25.
A JSch (Java Secure Channel) connection failure occurs, where JSch is the Java Implementation
of SSH that MediaSense uses to connect to an SSHD (Secure Shell Daemon) server (i.e. an
SFTP server).
3. Click the Test SFTP button on the MediaSense archive configuration page and wait for the
test to fail.
4. After the test fails, hit ctrl + C on your MediaSense CLI to stop the packet capture.
This message will be thrown if MediaSense and your SFTP server cannot agree on a key
exchange (KEX) algorithm, cipher for encrypting traffic, or Message Authentication Code (MAC)
algorithm. These are the algorithms you must check in the packet capture. You need to ensure
that the MediaSense server and the SFTP server both negotiate at least one of the same key
exchange algorithm, cipher, and MAC algorithm. You must use the packet capture to see which
algorithm is not being negotiated, and make sure your SFTP server negotiates one or more of the
missing algorithms.
If you don't want to look at a packet capture, you can ensure this configuration on your Linux-
based SFTP server:
1. Ensure that your SFTP server negotiates with MediaSense at least one of these options for key
exchange algorithms:
For example, if your SFTP server does not negotiate a needed cipher, you can make it negotiate
this by adding this line to the sshd_config configuration file on your SFTP server.
Note: You can add any and all ciphers if necessary. Just separate with commas.
Bugs
Please note that documentation is being improved to make this process more clear.
Related Information
This is a link to man pages documentation for the sshd_config file that explains how to make
configuration changes to your Linux-based SFTP
server: http://manpages.ubuntu.com/manpages/wily/man5/sshd_config.5.html.
This file is located at /etc/ssh/sshd_config. The same configuration changes are valid for any
Linux server.