Ridgeline Installation and Upgrade Guide

Transcription

1 Software Version 3.1 Service Pack 1 Extreme Networks, Inc Monroe Street Santa Clara, California (888) (408) Published: February 2012 Part Number: Rev. 03

2 AccessAdapt, Alpine, Altitude, BlackDiamond, Direct Attach, EPICenter, ExtremeWorks Essentials, Ethernet Everywhere, Extreme Enabled, Extreme Ethernet Everywhere, Extreme Networks, Extreme Standby Router Protocol, Extreme Turbodrive, Extreme Velocity, ExtremeWare, ExtremeWorks, ExtremeXOS, Go Purple Extreme Solution, ExtremeXOS ScreenPlay, ReachNXT, Ridgeline, Sentriant, ServiceWatch, Summit, SummitStack, Triumph, Unified Access Architecture, Unified Access RF Manager, UniStack, XNV, the Extreme Networks logo, the Alpine logo, the BlackDiamond logo, the Extreme Turbodrive logo, the Summit logos, and the Powered by ExtremeXOS logo are trademarks or registered trademarks of Extreme Networks, Inc. or its subsidiaries in the United States and/or other countries. sflow is the property of InMon Corporation. Specifications are subject to change without notice. All other registered trademarks, trademarks, and service marks are property of their respective owners Extreme Networks, Inc. All Rights Reserved. 2

3 Contents Chapter 1: Installation Overview...5 Installation Overview...5 The Ridgeline Server...6 Upgrading the Ridgeline Server...6 The Ridgeline Client...6 System Requirements...7 Windows Vista/XP/2003 Server/2008 Server/Windows The Ridgeline Server...7 The Ridgeline Client...8 Sun Microsystems Solaris The Ridgeline Server...8 The Ridgeline Client...9 Red Hat Enterprise Linux The Ridgeline Server...9 The Ridgeline Client...10 Browser Requirements for Launching the Ridgeline Client...10 Upgrading Ridgeline to a Service Pack Release...11 Obtaining a License Key for the Ridgeline Server...11 Evaluation License...12 Permanent License...12 Distinguishing Between a License Key and an Activation Key...13 Installing a Permanent License When an Evaluation License is Already Installed...13 Chapter 2: Downloading Ridgeline Software...15 Overview...15 Determining Device Serial Numbers...16 Providing Serial Numbers to Extreme Networks esupport...18 Chapter 3: Installing the Ridgeline 3.1 Server...21 Installation Overview...21 Retaining the Database when Reinstalling Ridgeline...22 User Permissions...22 Local Name Resolution for the Server...22 Required Patches for Solaris...23 Setting the Run Level for Linux...23 Installing the Ridgeline Server...23 When Ridgeline Detects Other Versions of Ridgeline...25 If Ridgeline Does Not Support a Platform...27 Choosing Ridgeline Installation Settings...28 Destination Path for Ridgeline...28 Starting Windows Services...30 Setting IP Address...31 Automatic Updates to Ridgeline...32 Default Ports Already in Use...32 Software Installation...33 Database Migration...35 Software Installation Successful...38 FTP Server for VM Tracking

4 Contents Ridgeline Installation Complete...40 Windows System Restart...40 Viewing Installation Logs...40 Launching the License Manager...41 Adding or Upgrading a License Key...41 Adding a License for an Upgrade Product...42 Starting and Stopping the Ridgeline Server...42 Starting the Server on Windows...43 Stopping the Server on Windows...43 Linux and Solaris Command Summary...43 Starting the Server on Linux or Solaris...44 Stopping the Server on Linux or Solaris...44 Configuring the Ridgeline Server for NATed Client Connections...44 Installing Ridgeline on a Multi-Homed Server...45 Installing a Difference Viewer...47 For Windows...47 For Linux or Solaris...47 Enabling SSH for Secure Communications...47 The Ridgeline SSH Enabling Key...48 Uninstalling the Ridgeline Server Software...48 Uninstalling the Server on Windows...48 Uninstalling the Server on Linux or Solaris...52 Viewing Uninstall Logs...52 Chapter 4: Launching the Ridgeline 3.1 Client...53 About the Client Initialization Process...53 Launching the Client Application...53 Disabling Installation of Desktop Shortcuts...56 Configuring the Firefox Browser for the Java Plug-In...57 Chapter 5: Upgrading the Ridgeline Software...59 Ridgeline Software Upgrade Overview...59 Installing a Service Pack Release...60 Installing a Service Pack on Windows Systems...61 Viewing Installation Logs...66 Uninstalling the Service Pack on Windows Systems...66 Viewing Uninstall Logs...70 Uninstalling a Service Pack from the Windows Control Panel...70 Installing a Service Pack on Solaris or Linux Systems...71 Uninstalling the Service Pack on Solaris or Linux Systems

5 1 Installation CHAPTER Overview This chapter provides an overview of the installation or upgrade of Ridgeline software, and includes the following sections: Installation Overview on page 5 The Ridgeline Server on page 6 The Ridgeline Client on page 6 System Requirements on page 7 Browser Requirements for Launching the Ridgeline Client on page 10 Obtaining a License Key for the Ridgeline Server on page 11 NOTE Ridgeline does not provide multi-language support. Installation Overview Ridgeline is a powerful, yet easy to use, client-server application for the centralized management of a network of Extreme Networks switches and selected third-party devices. Ridgeline offers a comprehensive set of network management tools that are easy to use from a client workstation with a web browser and the appropriate Java plug-in. The Ridgeline software can be installed on systems running Windows Vista, XP, Windows 2003 server, Windows 2008 server, or Windows 7 (Ridgeline 32- bit version only) on SPARC workstations running Solaris 10, or on systems running Red Hat Enterprise Linux version 5. NOTE This release, Ridgeline 3.1, will be the last release that supports Solaris. There are several options for installing the Ridgeline 3.1 software, depending on whether you already have versions of Ridgeline installed, or whether this is a new Ridgeline installation. 5

6 Chapter 1: Installation Overview The Ridgeline Server The Ridgeline server requires a license key, installed onto the server, to enable clients to connect to the server. You can perform the installation successfully without a Ridgeline license, but you will need to add a license key by running the License Manager, in order to use the Ridgeline product. License key installation is separate from the Ridgeline server installation. You can run the License Manager at any time to add or upgrade licenses. The installation process is very similar under Windows, Solaris, or Linux. CAUTION If you are running an evaluation version of the Ridgeline 3.1 software, and you want to retain the information in your Ridgeline database, DO NOT REINSTALL the Ridgeline software to upgrade to a permanent license. See Adding or Upgrading a License Key on page 41 for instructions on running the License Manager. There are several additional (optional) components you may want to install along with your Ridgeline server: a difference viewer you can use to compare configuration files within the Configuration Manager; and the SSH enabling key, which enables Ridgeline to use SSH2 instead of Telnet to communicate to the devices Ridgeline manages (assuming the devices are enabled to use SSH), and to securely upload and download configuration files. See Installing a Difference Viewer on page 47 for instructions on obtaining and installing a difference viewer. See Enabling SSH for Secure Communications on page 47 for information on enabling Ridgeline to use SSH. Upgrading the Ridgeline Server From time to time Extreme Networks may choose to release updates to Ridgeline as a Service Pack release. On systems with a previously installed base release of the Ridgeline server, you can upgrade to a service pack release by installing a Ridgeline service pack patch. See Upgrading Ridgeline to a Service Pack Release on page 11 for details. NOTE If you have been running a beta version of the Ridgeline 3.1 software, you must uninstall the beta version and do a new install of the final version. You cannot upgrade a beta version of the Ridgeline 3.1 software to the general availability (GA) release of the software. The Ridgeline Client The Ridgeline client is an application that is launched from a Microsoft Internet Explorer or Mozilla Firefox browser. A browser is also required to display Ridgeline reports and to view the Ridgeline online help. 6

7 System Requirements The Ridgeline client can run on a different type of system from the server; for example, you can run the client on a Windows system connected to a Ridgeline server installed on a Linux system. No software installation is required for a client to connect to the Ridgeline server; however, the Java 1.6.0_25 and later plug-in is required, and you will be prompted to install it if it is not already present. There is no separate installation package for the Ridgeline client. When you connect to the Ridgeline server with a browser and launch the Ridgeline client, all required files are downloaded and installed on your system automatically. No license is needed to run the Ridgeline client; however, the Ridgeline server must have a valid license installed before any client connections are allowed. NOTE If you are running the Microsoft System Center Virtual Machine Manager (SCVMM), you must install the Ridgeline XNV agent on the SCVMM host. For installation information, see Step 6 on page 55. System Requirements The following sections specify the system requirements for installing and running Ridgeline 3.1. Please check the most current version of the Ridgeline Release Notes for any additional or changed requirements for the Ridgeline release you are installing. Windows Vista/XP/2003 Server/2008 Server/Windows 7 The Ridgeline Server. The system requirements for the Ridgeline server on Microsoft Windows are as follows: Microsoft Windows Vista, Windows XP Professional with SP1 or later, Windows 2003 server, Windows 2008 server, or Windows 7 running on an Intel Pentium-compatible CPU. NOTE The Windows platform 32-bit version of Ridgeline 3.1 can be installed on any Windows platform listed above, regardless of whether it is a 32-bit or 64-bit machine/os. The 64-bit version of Ridgeline 3.1 can only be installed on Intel-based 64-bit systems for the 64-bit Windows platforms listed above. If you try to install 64-bit Ridgeline 3.1 on Itanium- or AMD-based 64-bit machines, the Windows OS might report an error message. 2 GB RAM minimum, 4 GB recommended. Up to 4 GB might be needed to manage very large numbers of devices (1000 or more). NOTE If the Ridgeline Client and Server are to be run on the same machine, 4 GB RAM is recommended. 7

8 Chapter 1: Installation Overview 2 GB disk space available, NTFS filesystem recommended. 2 GB of swap space minimum for the 32-bit version of Ridgeline; for the 64-bit version, we recommend a minimum of 4 GB of swap space. 1 GHz or greater Pentium-compatible processor (2 GHz or greater recommended). The Ridgeline server software requires the installation of Oracle/Sun JRE 1.6.0_25 (or later). The Oracle/Sun JRE 1.6.0_25 is included in the server installation and is the version we recommend you use. NOTE Additional disk space may be needed to hold alarm logs and other runtime data. The amount of space depends on the number of devices and the number of traps and syslog messages generated by the managed devices. The Ridgeline Client. The system requirements for the Ridgeline client on Microsoft Windows are as follows: Windows Vista, Windows XP Professional with SP1 or later, Windows 2003 server, Windows 2008 server, Windows 7 (Ridgeline 32-bit version only) running on an Intel Pentium-compatible CPU. A monitor that supports at least 1024 x 768 resolution, and 16-bit color. Your system display settings must be set for at least colors. 512 MB RAM minimum (up to 1 GB recommended). NOTE If the Ridgeline Client and Server are to be run on the same machine, 4 GB RAM is recommended. 256 MB of disk space, NTFS filesystem recommended. Swap space equal to double the amount of memory. For example, if you have 512 MB of RAM, you should have 1 GB of swap space. A browser (Mozilla Firefox or Microsoft Internet Explorer) is required to launch the Ridgeline client, display reports, and view the Ridgeline online help. Sun Microsystems Solaris 10 NOTE This release, Ridgeline 3.1 will be the last release that supports Solaris. The Ridgeline Server. The Ridgeline server software, version 3.1, is supported on the Sun Solaris operating environment on SPARC workstations. The system requirements for the server and client are as follows: 2 GB RAM minimum, 4 GB recommended. Up to 4 GB may be needed for very large numbers of devices (1000 or more). 400 Mhz or better processor 8

9 System Requirements 2 GB disk space available. Swap space equal to double the amount of memory. For example, if you have 512 MB of RAM, you should have 1 GB of swap space. The Ridgeline server software requires the installation of Oracle/Sun JRE 1.6.0_22 (or later). The Oracle/Sun JRE 1.6.0_22 is included in the server installation and is the version we recommend you use. NOTE Additional disk space may be needed to hold alarm logs and other runtime data. The amount of space depends on the number of devices and the number of traps and syslog messages generated by the managed devices. The Ridgeline Client. The system requirements for the Ridgeline client on Solaris are as follows: A monitor that supports at least 1024 x 768 resolution, and 16-bit color. Your system display settings must be set for at least colors. 512 MB RAM minimum. (Up to 1 GB recommended.) 256 MB disk space available. Swap space equal to double the amount of memory. For example, if you have 512 MB of RAM, you should have 1 GB of swap space. A browser (Mozilla Firefox) is required to launch the Ridgeline client, display reports, and view the Ridgeline online help. Red Hat Enterprise Linux 5 The Ridgeline Server. The Ridgeline server software, version 3.1, is supported on Red Hat Enterprise Linux version 5. The system requirements are as follows: NOTE The Linux platform 32-bit version of Ridgeline 3.1 can be installed on the Linux platform listed above, regardless of whether it is a 32-bit or 64-bit machine/os. The 64-bit version of Ridgeline 3.1 can only be installed on Intel-based 64-bit systems for the 64-bit Linux platform listed above. If you try to install 64-bit Ridgeline 3.1 on Itanium- or AMD-based 64-bit machines, the Linux OS might report an error message. 2 GB RAM minimum, 4 GB recommended. Up to 4 GB may be needed for very large numbers of devices (1000 or more). 1 GHz or greater Pentium-compatible processor (2 GHz recommended). 2 GB disk space available. Swap space equal to double the amount of memory. For example, if you have 512 MB of RAM, you should have 1 GB of swap space. A GUI/Desktop environment must be installed on the server machine. The Ridgeline server software requires the installation of Oracle/Sun JRE 1.6.0_22 (or later). The Oracle/Sun JRE 1.6.0_22 is included in the server installation and is the version we recommend you use. 9

10 Chapter 1: Installation Overview NOTE Additional disk space may be needed to hold alarm logs and other runtime data. The amount of space depends on the number of devices and the number of traps and syslog messages generated by the managed devices. The Ridgeline Client. The system requirements for the Ridgeline client on Red Hat Enterprise Linux are as follows: A monitor that supports at least 1024 x 768 resolution, and 16-bit color. Your system display settings must be set for at least colors. 512 MB RAM minimum (1 GB recommended). 256 MB disk space available. Swap space equal to double the amount of memory. For example, if you have 512 MB of RAM, you should have 1 GB of swap space. A browser (Mozilla Firefox 1.5 or higher) is required to display reports and view the Ridgeline online help. Browser Requirements for Launching the Ridgeline Client The Ridgeline client is launched from a browser window. Ridgeline uses signed applets. You will be prompted to accept the security certificate from Extreme Networks the first time you try to launch the applet. NOTE The Java plug-in version 1.6.0_25 and later is required for the Ridgeline client. If this version of the plug-in is not already installed, you will be prompted to download it the first time you try to launch the Ridgeline client. Table 1 lists the browsers that are supported by the Ridgeline 3.1 release. A browser is also required to display Ridgeline reports and the Ridgeline online help. Table 1: Ridgeline 3.1 supported browsers Operating System Minimum Browser Configuration Windows Internet Explorer 6.0 or higher, Mozilla Firefox 1.5 or 2.0 Sun Solaris 10 Mozilla Firefox 1.5, 2.0, or 3.0 Red Hat Enterprise Linux version 5 Mozilla Firefox 3.0 NOTE For the Mozilla Firefox browser, you must install the Java plug-in, and then link it to the Firefox browser. See Configuring the Firefox Browser for the Java Plug-In on page 57 10

11 Upgrading Ridgeline to a Service Pack Release Upgrading Ridgeline to a Service Pack Release From time to time Extreme Networks may elect to release updates to the current Ridgeline release as Service Packs. Service Packs are minor releases that provide fixes for known problems from previous releases. A Service Pack is released as a patch release that integrates the Service Pack fixes into an existing base Ridgeline software installation. If you already have the Ridgeline software installed on your system when a Service Pack is released, you can add the Service Pack fixes by installing the patch release. See Installing a Service Pack Release on page 60 for installation instructions. If the Service Pack you want to install is for a different base release than the one currently installed on your system, first install the base release and then install Service Pack patch. After you upgrade the Ridgeline 3.1 server to a Service Pack release, if any files are necessary to run the Ridgeline client on your system, they are downloaded and installed automatically when you launch the client. Obtaining a License Key for the Ridgeline Server To log in to the Ridgeline server from a Ridgeline client, Ridgeline must be configured with a valid license. You can install the software without a license key, but you cannot connect to it from a Ridgeline client. (If you install the product without a license key, you can add the key later using the License Manager, described in Installing a Permanent License When an Evaluation License is Already Installed on page 13). Ridgeline licenses allow you to use all of the standard features of the product, including discovery and visualization of the devices in your network, scripting, and point-and-click provisioning for VLANs and EAPS domains. Additional feature licenses are available from Extreme Networks that unlock additional Ridgeline features, including: identity management, VM support, and service provider features, such as E-LINE, E-LAN, VMAN (PB), PBB and VPLS discovery, monitoring, and provisioning for an unlimited number of devices. For more information about the various types of software licenses available for Ridgeline, refer to the Ridgeline Release Notes. 11

12 Chapter 1: Installation Overview You can get two types of licenses from Extreme Networks, an evaluation license and a permanent license at Select the option for the license key you want. Evaluation License An evaluation license allows you to run the product on a temporary basis. If you want to continue using the product beyond the evaluation period, you must obtain a permanent license. To get an evaluation license: 1 Go to: 2 Select the option to obtain an evaluation license key. 3 Enter your name, company information, and similar information, and an address to which your license key should be sent. Your evaluation license key will be sent to you by return . If your evaluation license expires before you have finished evaluating the product, you can request another evaluation key, up to three evaluation keys for a total of 90 days of evaluation use. Permanent License A permanent license has no time limit. Permanent licenses are sold based on the number of devices you want Ridgeline to manage. To obtain a permanent license: 1 You must provide your activation key, found on the license agreement shipped with your purchased product. 2 Fill in the requested information, and enter your activation key. The activation key is a 14-character key that starts with AC found on the License Agreement you received when you purchased the product. Your permanent license key will be sent to you by return . 12

13 Installing a Permanent License When an Evaluation License is Already Installed Distinguishing Between a License Key and an Activation Key Both permanent and evaluation license keys are 14-character keys that start with RS and are followed by 12 additional upper- and lower-case alphabetic characters, numbers, and special characters such as +. The license key is NOT the same as the activation key, which starts with AC, and is found on the License Agreement shipped with your purchased product. You use the activation key to obtain a permanent license. Installing a Permanent License When an Evaluation License is Already Installed To install a Ridgeline evaluation or permanent license, or to upgrade an evaluation license to a permanent license you must run the License Manager. Until you install a license, no client will be able to connect to the Ridgeline server. Refer to Adding or Upgrading a License Key on page 41 for instructions to do this. 13

14 Chapter 1: Installation Overview 14

15 2 Downloading CHAPTER Ridgeline Software This chapter comprises information and procedures to download images from Extreme Networks esupport. In some specific cases, the process might be different and is noted when applicable. It contains the following sections: Overview on page 15 Determining Device Serial Numbers on page 16 Providing Serial Numbers to Extreme Networks esupport on page 18 Overview Using the Ridgeline Firmware Manager, you can download software and BootROM images from Extreme Networks to your Ridgeline server, then upgrade the devices in your network with the new images. To download new images from Extreme, you must have a current support contract and an Extreme Networks esupport user name and password. You also need to provide esupport with the serial number of a device of the type you are upgrading in order to obtain updated images for that type of device. For example, to obtain updated Summit X650 software, you need to provide the serial number of one of the Summit X650 switches in your network prior to downloading the software. After you do this, the updated Summit X650 software can be downloaded from Extreme, and you can use it to upgrade any of the Summit X650 switches in your network. For chassis devices, you provide the serial number of a Management Module or I/O Module. Once you have provided the serial number for the device, you can download subsequent image updates for that type of device without having to enter the serial number again. If you have not yet provided esupport with a serial number for the device type you are upgrading, you may see the following window when you attempt to download a new image using Firmware Manager: 15

16 Chapter 2: Downloading Ridgeline Software Figure 1: Progress and Results Window Showing Unsuccessful Image Download To obtain the new images, you must determine the serial numbers for the type of device you want to upgrade, then supply those serial numbers to Extreme Networks esupport. Refer to Determining Device Serial Numbers on page 16. After you do this, the software images download normally. Determining Device Serial Numbers The serial number for a device is displayed in the Device Properties window. To display this window, select a device, then select Properties from the File menu, or from the right-click pop-up menu. The device serial number appears in the System ID field, as shown in Figure 2. Figure 2: Location of Serial Number in the Device Properties Window Device Serial Number Chassis Part Number 16

17 Determining Device Serial Numbers You can also display the serial numbers of devices in your network by running a Device Details report in Ridgeline. For example: Figure 3: Device Details Report 17

18 Chapter 2: Downloading Ridgeline Software To display the serial numbers of individual modules (Figure 4), run the Card Summary report. Figure 4: All Cards Card Summary Report Providing Serial Numbers to Extreme Networks esupport To provide serial numbers to Extreme Networks esupport, complete the following steps: 1 Go to and log into the esupport page with your esupport user ID and password. Figure 5: esupport Login page 2 Select the Download Software Updates link. 18

19 Providing Serial Numbers to Extreme Networks esupport Figure 6: Download Software Updates Link on esupport Page 3 In the Serial # box, enter the serial number of the device or module, and click Software Downloads. NOTE For chassis devices, you must provide the serial number of a Management Module or I/O Module. Figure 7: Serial Number Entry Box NOTE If you are upgrading SSH on a switch, you must do this operation for each Ridgeline switch. 4 Accept the terms of the software license agreement and click Submit. Figure 8: Software License Agreement 19

20 Chapter 2: Downloading Ridgeline Software A table of the software versions available for the device is displayed. If the device is under a service contract, all software versions are displayed; otherwise, only software versions available for the 90-day warranty period are displayed. For example: Figure 9: List of Available Software Versions for a Device 5 In the Ridgeline Firmware Manager, select one of the software versions listed in the esupport table. When you do this, the software image is downloaded to the Ridgeline server. Figure 10: Downloading a Selected Software Image to the Ridgeline Server 20

21 3 Installing CHAPTER the Ridgeline 3.1 Server This chapter describes how to install or upgrade the Ridgeline 3.1 server software in Windows, Solaris, and Linux, and includes the following sections: CAUTION If you are running an evaluation version of the Ridgeline 3.1 software, and you want to retain the information in your Ridgeline database, DO NOT REINSTALL the Ridgeline software to upgrade to a permanent license. Installation Overview on page 21 Installing the Ridgeline Server on page 23 Adding or Upgrading a License Key on page 41 Starting and Stopping the Ridgeline Server on page 42 Configuring the Ridgeline Server for NATed Client Connections on page 44 Installing Ridgeline on a Multi-Homed Server on page 45 Installing a Difference Viewer on page 47 Enabling SSH for Secure Communications on page 47 Uninstalling the Ridgeline Server Software on page 48 Installation Overview You can install the Ridgeline server in the following environments: Microsoft Windows Vista, Windows XP Professional with SP1 or later, Windows 2003 server, Windows 2008 server, or Windows 7 (Ridgeline 32-bit version only) running on an Intel Pentiumcompatible CPU or Red Hat Enterprise Linux Version 5 or Solaris 10 running on a SPARC system 21

22 Chapter 3: Installing the Ridgeline 3.1 Server NOTE This release, Ridgeline 3.1 will be the last release that supports Solaris The installation process is very similar under all three operating environments; the few differences are noted in the description of the process when applicable. See System Requirements on page 7 for memory, CPU, disk and other requirements. To install the Ridgeline server you will need the following information: The HTTP port for communication with Ridgeline clients (default is 8080) A license key. See Obtaining a License Key for the Ridgeline Server on page 11 for more information. NOTE Prior to installing Ridgeline, make sure the system where you are installing the software is DNS-resolvable and accessible both by IP address and by hostname from all machines where the Ridgeline client will be launched. If it is not, add an entry for the system in the local DNS server or the hosts file on the client machines. Retaining the Database when Reinstalling Ridgeline CAUTION If you are running an evaluation version of the Ridgeline 3.1 software, and you want to retain the information in your Ridgeline database, DO NOT REINSTALL the Ridgeline software to upgrade to a permanent license. Reinstalling Ridgeline will reinitialize the database, which erases all information in the database. To update an evaluation copy of the Ridgeline server to a licensed copy without reinitializing the database, follow the update procedure described in Adding or Upgrading a License Key on page 41. User Permissions To install the Ridgeline software components as services under Microsoft Windows as daemons under Solaris/Linux, you must have administrator privileges on that system. Local Name Resolution for the Server The system on which Ridgeline is installed must be able to resolve both its own local name and its domain name. For example if you install Ridgeline on a system named system1, then it must be able to resolve both system1 and its domain name, such as system1.company.com. You can test for this by attempting to ping the system using both the local name and the domain name. If there are problems resolving either of these names, make sure the hosts file contains the correct information. 22

23 Installing the Ridgeline Server Required Patches for Solaris The Solaris operating environment may require patches for the Ridgeline software to function properly. Make certain these patches have been installed before you install the Ridgeline server software. For the most current information on required patches, see the Ridgeline Release Notes that accompanies your Ridgeline software, or go to the Extreme Networks web site at Setting the Run Level for Linux On Linux systems, in order for the Ridgeline database and server components to start automatically at system boot, the run level on the server must be set to 5. Installing the Ridgeline Server To install the Ridgeline server, complete the following steps: 1 Download the Ridgeline software from the Extreme Networks esupport software download page. 2 Extract the contents of the zip or tar file into a temporary directory, if necessary. For information about downloading the software, refer to Chapter 2, Downloading Ridgeline Software. 3 To start the installation wizard, launch the Ridgeline installer executable that you downloaded. Figure 11: Ridgeline Welcome 23

24 Chapter 3: Installing the Ridgeline 3.1 Server 4 The Ridgeline Software license agreement opens. After you read the agreement, click Accept to consent then click Next to proceed. Figure 12: License Agreement Figure 13: Solaris Non-Support Notice 24

25 Installing the Ridgeline Server When Ridgeline Detects Other Versions of Ridgeline If Ridgeline detects Ridgeline 3.1 is already installed, you are instructed to uninstall it before reinstalling Ridgeline 3.1 again. Figure 14: Ridgeline 3.1 is Already Installed If Ridgeline detects an older version of Ridgeline or EPICenter, the previous versions are listed, along with their installed location. This can be the case if you are upgrading to Ridgeline 3.1 from an older version, as shown in Figure

26 Chapter 3: Installing the Ridgeline 3.1 Server Figure 15: Other Ridgeline or EPICenter Services are Running Click Next to continue the installation. 26

27 Installing the Ridgeline Server If Ridgeline Does Not Support a Platform If Ridgeline detects a platform it does not support, the Platform not supported dialog opens. See Figure 16. Figure 16: Platform Not Supported 27

28 Chapter 3: Installing the Ridgeline 3.1 Server Choosing Ridgeline Installation Settings The Ridgeline installer provides a choice of installation settings. You can use the recommended values for all settings, or supply custom values of your own. Figure 17: Installation Settings If you choose Recommended settings, the installation process skips the custom setup steps, and proceeds to Software Installation on page 33.The default installation directories are: C:\Program Files\Extreme Networks\Ridgeline 3.1 for Windows, or /opt/extremenetworks/ridgeline3.1 for Linux or Solaris. If you choose Custom settings, a sequence of dialogs open, starting with the directory path for Ridgeline installation described in the following section. 1 Select the desired option and click Next. Destination Path for Ridgeline When you choose Custom Settings, the first choice is the destination path where you want to install Ridgeline. 28

29 Installing the Ridgeline Server 1 To set up a custom directory, type the directory path, or browse to find the directory where you want to install Ridgeline. See Figure 18. Figure 18: Installation Destination 2 Click Next to continue. Or, click Restore Default Folder to reset the installation path to the default. 29

30 Chapter 3: Installing the Ridgeline 3.1 Server Starting Windows Services To start services automatically when Windows starts, check the box. This is the default. To start services manually, click the check mark to remove it. Figure 19: Windows Services Startup 30

31 Installing the Ridgeline Server Setting IP Address The Ridgeline server provides several options for IP communications with Ridgeline clients and network devices, as shown in Figure 20. Figure 20: Setting IP Address 1 Choose the desired IP Address option: Use this IP address to launch the clients and to talk to the network devices. Open the drop down menu to choose an IP address. The drop down menu shows the IP address for each interface on the host. With this choice Ridgeline uses a single interface to communicate with both Network clients and network devices. Use this host name to launch the clients. The server host name is displayed. When you choose this selection, Ridgeline clients communicate with the Ridgeline server using the hostname, and Ridgeline determines the interface to use when talking to network devices Use this host name to launch the clients and this IP address when talking to network devices. The server host name is displayed, along with a drop down menu to choose an IP address. This option is only present on hosts with multiple network interfaces. 2 Set the HTTP port that clients should use when connecting to Ridgeline. The Ridgeline default HTTP port is Choose Next to continue. 31

32 Chapter 3: Installing the Ridgeline 3.1 Server Automatic Updates to Ridgeline Ridgeline automatically searches for updates and installs them on the server. Default Ports Already in Use Ridgeline automatically installs the server software on specified ports: If recommended ports are in use, a dialog lists these port numbers. Figure 21: Ports in Use To specify unused ports, complete the following steps: 1 Click Previous until you open the Installation settings dialog. 2 Choose Custom settings 3 Enter a different path as described in Destination Path for Ridgeline on page

33 Installing the Ridgeline Server Software Installation 1 After you have specified all installation options, and optionally migrated the previous database, the Pre-installation Summary opens. Figure 22: Pre-installation Summary For Windows Figure 23: Pre-installation Summary For Linux 2 Click Install. The installation process begins. 33

34 Chapter 3: Installing the Ridgeline 3.1 Server NOTE Ridgeline automatically stops the services for the server and database engine See Stopping the Server on Linux or Solaris on page 44 for manual shutdown instructions. The following dialog shows the installation progress. Figure 24: Installation Progress 34

35 Installing the Ridgeline Server Database Migration 1 Choose Yes to migrate the previous database, or No to continue without migrating. If you choose No, the installer skips to Software Installation Successful on page 38. Figure 25: Database Migration 2 Click Next to continue. 35

36 Chapter 3: Installing the Ridgeline 3.1 Server 3 Choose the Migrate option to have the Wizard migrate the database automatically, or the Import option if you want to use database files previously archived. This procedure demonstrates the Migrate option. Click Next to continue. Figure 26: Database Migration Options 4 Verify the locations of the previous and current Ridgeline installations and click Migrate to continue. The migration begins and progress is displayed. Figure 27: Database Migration Assistant Setup 36

37 Installing the Ridgeline Server Figure 28: Database Migration Assistant Progress 5 When migration is 100% complete, click Close. The successful migration dialog is then displayed. Additional information about the previous installation is displayed, along with any special instructions. Figure 29: Database Migration Success 6 Record any onscreen instructions and click Next to complete the migration. The database migration notice dialog is displayed. 37

38 Chapter 3: Installing the Ridgeline 3.1 Server Figure 30: Database Migration Notice Software Installation Successful When the software installation is complete, the following dialog is displayed. Figure 31: Installation Successful Click Next to continue. 38

39 Installing the Ridgeline Server FTP Server for VM Tracking The following dialog can inform you that VM tracking requires an FTP server to be up and running if you use this feature. Click Next. Figure 32: FTP Server for VM Tracking Reminder 1 Be sure the FTP server is started. 2 Click Next to complete the installation process. 39

40 Chapter 3: Installing the Ridgeline 3.1 Server Ridgeline Installation Complete A dialog opens that informs you that the installation is complete and shows the path where Ridgeline is installed. For Windows, it prompts you to restart your system. You must restart your system before a client can connect to the Ridgeline server. Figure 33: Installation Complete For Windows installations, click Next to continue. For Linux or Solaris, click Done. Windows System Restart For Windows installations, choose to restart your system immediately, or to manually restart your system later. The default is to restart your system immediately. Click Done. Viewing Installation Logs After the installation is complete, details about the installation process are in log files in the following locations: Windows: <installed directory>\logs Linux: <installed directory>/logs Solaris: <installed directory>/logs 40

41 Adding or Upgrading a License Key Launching the License Manager Launch the License Manager and install your Ridgeline licenses. You can do this at any time after you have installed the Ridgeline server. The server can be running while you do this, but this is not required. See Adding or Upgrading a License Key for more detailed instructions. Adding or Upgrading a License Key To install an evaluation or permanent license for Ridgeline, or to upgrade an evaluation license to a permanent license you must run the License Manager. Until you install a license, no client will be able to connect to the Ridgeline server. NOTE You must install a Base 50 license key even if you have purchased additional 50-node or 250-node license keys. The Base 50 license gives you access to the Ridgeline server; the optional upgrade licenses enable you to manage additional devices. To install or upgrade a license, complete the following steps: 1 Run the License Manager: In Windows, from the Start menu, select Start > Programs > Extreme Networks > Ridgeline 3.1 > License Manager On Linux or Solaris, go to the Ridgeline installation directory and run LicenseManager. By default, the Ridgeline installation directory is /opt/extremenetworks/ridgeline3.1. On Linux, the License Manager symbolic link is found in /root/extremenetworks/ Ridgeline3.1/License Manager. On Solaris, the License Manager is also available in Administrative Tools. Select Administrative Tools > Extreme Networks > Ridgeline > License Manager. 41

42 Chapter 3: Installing the Ridgeline 3.1 Server The License Manager window opens: Figure 34: License Key Manager 2 Enter the 14-character license key(s) in the appropriate fields, and click Install License. A pop-up window tells you whether the installation was successful or not. Adding a License for an Upgrade Product When you purchase a product upgrade option such as a 50-node license or an Advanced Services licenses, you receive a separate key to enable Ridgeline to manage additional devices or unlock additional features. To add the license key for a Ridgeline upgrade, run the License Manager as described above. Starting and Stopping the Ridgeline Server By default, the Ridgeline server components installed as services (in Windows) or daemons (in Linux or Solaris) are started automatically when you start or restart your computer. If you elected not to restart your computer at the end of the installation process, then you must start the Ridgeline database and server manually. In Windows, if you selected the option to start the Ridgeline server components manually, then you must start them before running Ridgeline. 42

43 Starting and Stopping the Ridgeline Server Starting the Server on Windows To start or restart the Ridgeline services manually, do the following in the specified order: 1 Open the Services window (found under Administrative Tools in the Control Panel). 2 Highlight Ridgeline 3.1 Database Engine, right-click and select Start from the pop-up menu to start the Ridgeline database. 3 Start the Ridgeline 3.1 Server and Ridgeline 3.1 FreeRADIUS Server in the same manner. Stopping the Server on Windows To stop the Ridgeline server: 1 Open the Services window (found in Administrative Tools in the Control Panel). 2 Highlight Ridgeline 3.1 Server, right-click and select Stop to stop the Ridgeline server. This should be done while the database is still running. 3 Highlight the Ridgeline 3.1 Database Engine and Ridgeline 3.1 FreeRADIUS Server in the same manner, right-click and select Stop. Linux and Solaris Command Summary The following table summarizes the Linux and Solaris commands for controlling Ridgeline. Table 2: Linux and Solaris Startup and Shutdown Commands for Ridgeline 3.1 Command Function Usage RidgelineDB31 start Start RidgelineDB None RidgelineDB31 stop Stop RidgelineServer if running, then stop RidgelineDB RidgelineServer31 start Otherwise, simply stop RidgelineDB. Start RidgelineDB first, if not running, then start RidgelineServer Use this command only when RidgelineServer is completely shutdown. See the RidgelineServer31 status command. Although this command stops the RidgelineServer first if it is currently running, a clean RidgelineServer shutdown before the RidgelineDB shutdown cannot be assured. RidgelineDB must be running before RidgelineServer can start. RidgelineServer31stop Stop RidgelineServer Use RidgelineServer status to verify that the service is fully stopped. RidgelineServer31status Display RidgelineServer status Use this command to determine whether the RidgelineServer is running or not, and to verify that it is completely shutdown after issuing RidgelineServer31 stop. RidgelineServer31stop Stop RidgelineServer None RidgelineFreeRadius31 start Start RidgelineFreeRadius None RidgelineFreeRadius31 stop Stop RidgelineFreeRadius None 43

44 Chapter 3: Installing the Ridgeline 3.1 Server Starting the Server on Linux or Solaris To start or restart the Ridgeline daemons manually, complete the following steps: Enter the following commands in the order shown: /etc/init.d/ridgelinedb31 start /etc/init.d/ridgelineserver31 start /etc/init.d/ridgelinefreeradius31 start You must have administrative rights to access init.d files. Stopping the Server on Linux or Solaris To stop the Ridgeline server, enter the following commands: Enter the following commands in the order shown: /etc/init.d/ridgelineserver31 stop (kills the server daemon) /etc/init.d/ridgelineserver31 status (repeat until Ridgeline server PID is stopped) /etc/init.d/ridgelinedb31 stop (kills the database daemon) /etc/init.d/ridgelinefreeradius31 stop Configuring the Ridgeline Server for NATed Client Connections If clients will be connecting to the Ridgeline server through a connection that uses Network Address Translation (NAT), configure the Ridgeline server as follows: 1 Stop the Ridgeline server if it is currently running. See the previous section for information about how to do this. 2 Set the EPICENTER_SERVER_ADDRESS environment variable to the hostname of the Ridgeline server. 3 Open the runserver.sp file, which resides in <Ridgeline_install_dir>/jboss/bin, and add the following entry: remoting.bind_by_host=true 4 In Ridgeline, set the TCP port number that clients use to connect to the Ridgeline server to To do this, go to Ridgeline Administration, click the Server Properties tab, select Other from the dropdown list, and enter in the Client Port field. 5 On the client machine, make sure the hostname of the Ridgeline server resolves to the correct outside IP address of the server. If the server s IP address does not resolve correctly, add an entry for the server in the client s hosts file. In Windows, the hosts file is c:\windows\system32\drivers\etc\hosts (where c: is the drive where Windows is installed). In Solaris and Linux, the hosts file is /etc/hosts. 6 Ensure that the ports used by Ridgeline are accessible through your firewall/nat setup. Ridgeline uses the following ports: 44

45 Installing Ridgeline on a Multi-Homed Server jboss ports 3873, 8080 (default), and 8083, which allow the Ridgeline server to talk to the client HTTP port 8334, which allows switches to talk to the Ridgeline server in HTTPs mode FreeRADIUS port (default) TCP port for the client to connect to the server in NAT-enabled environments 7 Restart the Ridgeline server, as described in the previous section. Installing Ridgeline on a Multi-Homed Server A multi-homed server has more than one network interface card (NIC) installed and might be using multiple IP addresses. If you are installing Ridgeline on a multi-homed server, you must specify either the IP address or hostname that Ridgeline clients should use when communicating to the Ridgeline server. You also specify which IP address Ridgeline should use when communicating with managed devices, or simply let Ridgeline choose the IP address automatically. Ridgeline 3.1 provides a Ridgeline Server Setup Utility that simplifies the process of configuring Ridgeline interfaces. The configuration options are: Select a single IP address for communication with Ridgeline clients and network devices. Other host IP addresses are unused by Ridgeline. Although this is a valid Ridgeline setting, and is presented in the setup utility, it is not useful for multi-homed systems because it only utilizes a single interface. Set a hostname that Ridgeline clients can use to communicate with the Ridgeline server, and let Ridgeline choose the IP address to communicate with network devices. Set a hostname that Ridgeline clients can use to communicate with Ridgeline, and specify an IP address that Ridgeline uses to communicate with network devices. To configure Ridgeline for multi-homed servers: 1 Stop the Ridgeline server. See Starting and Stopping the Ridgeline Server on page Start the Ridgeline Server Setup Utility: On a Windows system, from the Start menu go to: Programs > Extreme Networks > Ridgeline3.1 > Server Setup Utility On Linux, the server setup utility from symbolic link is in /root/extremenetworks/ Ridgeline3.1/Server Setup Utility. The Ridgeline Server Setup Utility dialog box opens. 45

46 Chapter 3: Installing the Ridgeline 3.1 Server Figure 35: Ridgeline Server Setup Utility 3 Choose one of the setup options: - Use this IP address to launch the clients and to talk to the network devices. This selection is not relevant for a multi-homed system, because it only specifies a single interface for all communications. - Use this host name to launch the clients. If you choose this option, clients should use the displayed hostname to communicate with Ridgeline. Ridgeline will determine which IP address to use to communicate with network devices. - Use this host name to launch the clients and this IP address to talk to the network devices. If this is selected, clients should use the displayed hostname to communicate with Ridgeline, and choose an IP address from the drop-down list for network device communication. 4 Optionally, specify a different HTTP port. 5 Click Confirm. A confirmation dialog is displayed. 6 Click OK on the confirmation dialog, then close the setup utility. 7 Start the Ridgeline server. 46

47 Installing a Difference Viewer Installing a Difference Viewer Ridgeline provides a Diff feature that allows you to compare configuration files using a Difference Viewer. This feature requires that a Difference Viewer be installed on the client system. A Difference Viewer can automatically compare and highlight the differences between two files. The Diff feature does not work with a standard text editor. You can use any Diff viewer that is installed on the system where your Ridgeline client is running. Select Difference Viewer from the Tools menu to tell Ridgeline the location of the viewer. If you do not have a Diff viewer already installed, you must install one on your client system in order to use the Diff feature. For Windows. You can obtain a Diff viewer from the following sources: WinMerge.exe; downloadable from Araxis Merge; 30 day free trial evaluation downloadable from For Linux or Solaris. sdiff (in /usr/bin/sdiff) is assumed as the default Diff viewer. Enabling SSH for Secure Communications By default, the Ridgeline server communicates to the devices it manages using unencrypted access, and unencrypted file transfers. In addition, the communications between the Ridgeline server and its clients are also unencrypted by default. By installing an SSH enabling key, you can use SSH2 instead of Telnet to communicate to the devices Ridgeline manages, and securely upload and download configuration files to and from your Extreme devices. By installing an SSH2 server co-resident with the Ridgeline server, and by installing SSH2 clients on the systems where your Ridgeline clients reside, you can use SSH2 to encrypt the communications between the Ridgeline server and Ridgeline clients. See the Appendix in the Ridgeline Service Advisor Concepts and Solutions Guide for details on setting up secure client-server communication. There are three requirements for enabling Ridgeline to use SSH2 to communicate with the devices it manages: The Ridgeline SSH enabling key must be installed. Due to export restrictions, you must obtain this module from Extreme Networks. It is not included with the Ridgeline software distribution. Your switches must be running versions of ExtremeWare or ExtremeXOS that support SSH, and SSH must be enabled on those devices. Due to export restrictions, a special license is required. To request versions of ExtremeWare or ExtremeXOS that support SSH, contact Extreme Networks Technical Support. SSH must be enabled in Ridgeline for the devices to which you want to communicate using SSH. NOTE If the SSH enabling key is not installed in the Ridgeline directory, you will not be able to configure SSH in Ridgeline. The relevant fields will be grayed out. 47