12.07.2015 Views

Version 3.1 SP2 Reference Guide - Extreme Networks

Version 3.1 SP2 Reference Guide - Extreme Networks

Version 3.1 SP2 Reference Guide - Extreme Networks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Managing Network SecurityFigure 437: Configuring devices to Use SSH for communicationcdCheck the SSH box, and select SSH Enabled from the drop-down menu.Click Modify to have this setting take effect.NOTEIf the SSH enabler module is not installed, you cannot configure SSH on any devices—the SSH setting willbe disabled.Ridgeline will now use SSH instead of regular Telnet for direct communications with the device,including Netlogin and polling for the FDB from the <strong>Extreme</strong> <strong>Networks</strong> switches. It will also use SFTPfor file transfers such as uploading or downloading configuration files to the device.Securing Ridgeline Client-Server TrafficBy default, Ridgeline server communication to its clients is unencrypted. You can secure thiscommunication through SSH tunneling. This requires installing and running an SSH client (PuTTY isrecommended) on the same system as the Ridgeline client, and installing and running an SSH server(OpenSSH is recommended) on the same system where the Ridgeline server resides.Tunneled communication is accomplished through port forwarding.To configure SSH tunneling between the Ridgeline server and client, you must to complete thefollowing steps:1 Install PuTTY on the Ridgeline client system2 Configure the PuTTY client with an Ridgeline session connecting to the Ridgeline server host3 Install an SSH server on the system with the Ridgeline server (if it is not already installed)4 Configure any firewall software to allow SSH connects5 Initiate Ridgeline server/client communication:594Ridgeline <strong>Reference</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!