Securing Ridgeline Client-Server Traffic - Extreme Networks Ridgeline Guide Manual

Concepts and solutions guide
Hide thumbs Also See for Ridgeline Guide:
Table of Contents

Advertisement

Managing Network Security
b After the form is submitted, Extreme Networks will review the request and respond within 2
business days.
c If your request is approved, an email will be sent with the information needed to obtain the "ssh-
enabler" key file.
d Place the "ssh-enabler" key file in your existing Ridgeline installation directory. This will unlock
the Ridgeline SSH-2 features.
3 Enable SSH on the devices for which you want Ridgeline to communicate using SSH rather than
Telnet:
a In Ridgeline, select Modify communications settings from the Device menu.
b Select the devices you want to configure for SSH. You can select multiple devices to configure at
the same time.
Figure 149: Configuring devices to Use SSH for communication
c Check the SSH box, and select SSH Enabled from the drop-down menu.
d Click Modify to have this setting take effect.
NOTE
If the SSH enabler module is not installed, you cannot configure SSH on any devices—the SSH setting will
be 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 Extreme Networks switches. It will also use SFTP
for file transfers such as uploading or downloading configuration files to the device.

Securing Ridgeline Client-Server Traffic

By default, Ridgeline server communication to its clients is unencrypted. You can secure this
communication through SSH tunneling. This requires installing and running an SSH client (PuTTY is
194
Ridgeline Concepts and Solutions Guide

Advertisement

Table of Contents
loading

This manual is also suitable for:

Ridgeline 3.0

Table of Contents