Ridgeline Installation and Upgrade Guide Software Version 3.0 Extreme Networks, Inc. 3585 Monroe Street Santa Clara, California 95051 (888) 257-3000 (408) 579-2800 http://www.extremenetworks.com Published: February 2011 Part Number: 100397-00 Rev.
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 lo
Contents Chapter 1: Installation Overview............................................................................................................... 5 Installation Overview ................................................................................................................................................5 The Ridgeline Server ........................................................................................................................................
Contents Uninstalling the Ridgeline Server Software ............................................................................................................31 Uninstalling the Server on Windows................................................................................................................31 Uninstalling the Server on Linux or Solaris .....................................................................................................32 Chapter 3: Launching the Ridgeline 3.0 Client ....
1 Installation Overview CHAPTER This chapter provides an overview of the installation or upgrade of Ridgeline, and includes the following topics: ● Installation Overview on page 5 ● The Ridgeline Server on page 5 ● The Ridgeline Client on page 6 ● System Requirements on page 7 ● Browser Requirements for Launching the Ridgeline Client on page 9 ● Obtaining a License Key for the Ridgeline Server on page 10 Installation Overview Ridgeline is a powerful, yet easy to use, client-server application
Chapter 1: Installation Overview ● See “Adding or Upgrading a License Key” on page 23 for instructions on running the License Manager.
System Requirements System Requirements The following sections specify the system requirements for installing and running Ridgeline 3.0. 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.
Chapter 1: Installation Overview Sun Microsystems Solaris 10 The Ridgeline Server. The Ridgeline server software, version 3.0, 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 ● 2 GB disk space available.
System Requirements The Ridgeline server software requires the 1.6.0_10 Java runtime package, which is included in the server installation. No separate installation is needed. 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.
Chapter 1: Installation Overview 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.
Obtaining a License Key for the Ridgeline Server Your evaluation license key will be sent to you by return email. 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 Licenses To obtain a permanent license key, you must provide your activation key, found on the license agreement shipped with your purchased product. To request a permanent key, go to www.
Chapter 1: Installation Overview Ridgeline Installation and Upgrade Guide 12
2 Installing the Ridgeline 3.0 Server CHAPTER This chapter describes how to install or upgrade the Ridgeline 3.
Chapter 2: Installing the Ridgeline 3.0 Server CAUTION If you are running an evaluation version of the Ridgeline 3.0 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.
Installing the Ridgeline Server You can use any port numbers (numbers between 1024 and 65535 are recommended), except port numbers already in use by another process, or ports 514, 3873, 8083, 10550, 10554, 10555, and 10556, which are used by Ridgeline for internal functions. During the installation process, if you specify a port that Ridgeline uses internally, you are prompted to select a different port number.
Chapter 2: Installing the Ridgeline 3.0 Server For Linux: a If you downloaded the installation from the web site, change the permissions on the Linux bin file as follows: chmod 755 Ridgeline_3-0_linux32.bin or chmod 755 Ridgeline_3-0_linux64.bin (Skip this if you are installing from the CD). b Run the executable Ridgeline_3-0_linux32.bin or Ridgeline_3-0_linux64.bin, depending on your version of the operating system.
Installing the Ridgeline Server On Windows systems, if the Ridgeline components were installed as services, select one of the following options: ● Select Yes to have the installer shut down the Ridgeline services (if they are running), or ● Select No to exit the installation process. Click Next to continue. On Solaris/Linux systems, you must exit the installation process and stop the Ridgeline database and server manually. See “Stopping the Server on Linux or Solaris” on page 25.
Chapter 2: Installing the Ridgeline 3.0 Server 7 Verify or enter a location for the Ridgeline installation. By default this is the directory C:\Program Files\Extreme Networks\Ridgeline Service Advisor 3.0 for Windows, or /opt/ExtremeNetworks/RidgelineServiceAdvisor3.0 for Linux or Solaris. You can type a different directory path, or browse to find the directory in which you want to install. Click Next to continue.
Installing the Ridgeline Server Figure 4: Port Information 9 A dialog box appears asking about several options you can enable: ● Enable Automatic Updates. This feature configures Ridgeline to automatically retrieve the most current information about device and slot software and bootrom images from the Extreme Networks web site each time you connect the client to the Ridgeline server.
Chapter 2: Installing the Ridgeline 3.0 Server Figure 5: Settings 10 The next panel asks you to verify the components and installation directory. Click Install to proceed with the installation, and follow the onscreen instructions.
Installing the Ridgeline Server The installation process begins. Figure 7: Installation Progress 11 If the installation was successful, the final dialog box displays a summary message. If there were any problems, they will be noted here. Click Finish to continue.
Chapter 2: Installing the Ridgeline 3.0 Server 12 Click OK to accept the warning messages that displays. The VM tracking feature requires an FTP server running prior to starting Ridgeline. Refer to the “Managing Virtual Machines” chapter in the Ridgeline Reference Guide for more information. Figure 9: VM Tracking Requires an FTP Server Running Warning 13 Ridgeline prompts you to restart your system.
Adding or Upgrading a License Key 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.
Chapter 2: Installing the Ridgeline 3.0 Server 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.
Configuring the Ridgeline Server for NATed Client Connections 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.0 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.0 Database Engine and Ridgeline 3.0 FreeRADIUS Server in the same manner, right-click and select Stop.
Chapter 2: Installing the Ridgeline 3.0 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 10559 (default) ● TCP port 56983 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 Figure 12: System Variable 7 Restart Windows to activate the new settings. NOTE You can also open a command window and use the SET command from the command prompt to set the EPICENTER_SERVER_ADDRESS environment variable. In Solaris or Linux: 1 Open the /etc/ridgeline30.profile file.
Chapter 2: Installing the Ridgeline 3.0 Server 2 Stop the Ridgeline server if it is currently running. See “Starting and Stopping the Ridgeline Server” on page 24 for information about how to do this. 3 Open the runserver.sp file, which resides in /jboss/bin, and add the following entry: epicenter.connect.address= or This entry specifies the address used by applications such as TFTP for connecting to the Ridgeline server.
Installing a Difference Viewer ● 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 10559 (default) ● TCP port 56983 for the client to connect to the server in NAT-enabled environments Configuring the Multi-Homed Server for Client Access from Both Networks If Ridgeline clients will be connecting from both networks where the multi-homed server reside
Chapter 2: Installing the Ridgeline 3.0 Server ● 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.
Uninstalling the Ridgeline Server Software The SSH enabling key must be placed in the top-level Ridgeline installation directory (by default \Program Files\Extreme Networks\Ridgeline Service Advisor 3.0 in Windows, or /opt/ ExtremeNetworks/RidgelineServiceAdvisor3.0 under Solaris or Linux). Uninstalling the Ridgeline Server Software The following sections describe how to uninstall the Ridgeline server software.
Chapter 2: Installing the Ridgeline 3.0 Server Figure 13: Uninstall Wizard 4 Follow the onscreen instructions to uninstall the software. If you plan to re-install Ridgeline, you should restart your system before you attempt to re-install. Uninstalling the Server on Linux or Solaris To remove the Ridgeline server software, follow these steps: 1 Stop the Ridgeline server components if they are running. See “Stopping the Server on Linux or Solaris” on page 25. 2 Exit all clients.
Uninstalling the Ridgeline Server Software 4 Follow the onscreen instructions to uninstall the software. If you plan to re-install the Ridgeline server, you should restart your system before you attempt to re-install. The Ridgeline software is now completely uninstalled.
Chapter 2: Installing the Ridgeline 3.
3 Launching the Ridgeline 3.0 Client CHAPTER This chapter describes how to connect to the Ridgeline 3.0 server and launch the Ridgeline 3.
Chapter 3: Launching the Ridgeline 3.0 Client ● Solaris 10 or ● Red Hat Enterprise Linux Version 5 A Ridgeline client requires a monitor that supports 1024 x 768 resolution, and at least 16-bit color. Your system display settings must be set for at least 65536 colors. See “System Requirements” on page 7 for memory, CPU, disk and other requirements. NOTE There is no separate installation for the client.
Launching the Client Application 3 The Ridgeline Welcome page appears. Figure 14: Ridgeline Welcome Page 4 Click the Log on to Ridgeline link. 5 Ridgeline checks if your system is running the correct version of the Java plug-in. If you are not running the correct version, you are directed to a page where you can download the correct version. If you are running the correct version of the Java plug-in, the Ridgeline client software is downloaded from the Ridgeline server and installed on the local system.
Chapter 3: Launching the Ridgeline 3.0 Client 7 The Ridgeline Log On screen appears, and you are prompted for a username and password. Figure 15: Ridgeline Log On Screen 8 If this is the first time you are logging in to Ridgeline, enter admin in both the Username field and the Password field. Click Log on to connect to the Ridgeline server. 9 After a successful login, the Ridgeline 3.0 Home screen appears.
Configuring the Firefox Browser for the Java Plug-In 4 Change the setting to Never allow. Figure 16: Modifying the Java Shortcut Creation Setting 5 Click OK to apply the setting and close the Java Plug-In control panel. Configuring the Firefox Browser for the Java Plug-In If you plan to use the Mozilla Firefox browser to connect to the Ridgeline server, you must download and install the Java Runtime Environment (JRE) plug-in, and then link it to the Firefox browser. These are two separate steps.
Chapter 3: Launching the Ridgeline 3.0 Client After the plug-in is installed, you must configure and enable the JRE to run applets in your browser. You can find the instructions in one of two ways: ● On the Installation Instructions page, click the “Enable and Configure” link near the top of the page. ● You can also go directly to these instructions at the following URLs: For Windows: http://www.java.com/en/download/help/5000010400.xml#enable For Linux: http://www.java.com/en/download/help/5000010500.
4 Upgrading the Ridgeline Software CHAPTER This chapter describes how to upgrade the Ridgeline software, and includes the following sections: ● Ridgeline Software Upgrade Overview on page 41 ● Installing a Service Pack Release on page 42 ● Upgrading from EPICenter or Ridgeline Service Advisor to Ridgeline on page 46 ● Migrating the Database on page 54 Ridgeline Software Upgrade Overview The Ridgeline software is available in the following forms.
Chapter 4: Upgrading the Ridgeline Software Table 2 summarizes the options for installing and upgrading the Ridgeline software. Table 2: Ridgeline Installation and Upgrade Options Release Type Contents Available Formats Base Ridgeline Installation • Major Ridgeline software release • Ridgeline installation CD How to Install You want to perform a fresh Ridgeline installation/upgrade to a Large file downloadable new major release.
Installing a Service Pack Release NOTE You cannot upgrade a Ridgeline beta release using this method. You must uninstall the beta release and then install the full Ridgeline release. Installing a Service Pack on Windows Systems To install a Ridgeline Service Pack release on a Windows system, follow these steps: 1 Download the Ridgeline Service Pack software from the Extreme Networks software downloads page and extract the contents of the zip file into a temporary directory.
Chapter 4: Upgrading the Ridgeline Software - To install the Service Pack in a non-default directory that has a name that includes spaces, be sure to specify the directory name in quotes. For example: prompt:\> install.bat "C:\Non-Default Directory With Spaces\Ridgeline 3.0" This batch file calls a script that will back up the Ridgeline files to: \backup 7 Restart the Ridgeline server and the database engine, if applicable (see “Starting the Server on Windows” on page 24).
Installing a Service Pack Release 4 It is recommended that you back up your database. In addition, if the database transaction log, basecamp.log, remains in the top-level Ridgeline installation directory after the Ridgeline server has been shut down, you should save it also. (Under most circumstances basecamp.log is removed when the server stops.) You should also save the files basecamp.db and epicenter.
Chapter 4: Upgrading the Ridgeline Software 4 Restart the Ridgeline server and the database engine, if applicable. See “Starting the Server on Linux or Solaris” on page 24 for instructions. Ensure that you clear your browser cache before reconnecting to the Ridgeline server.
Upgrading from EPICenter or Ridgeline Service Advisor to Ridgeline 3 The Ridgeline InstallShield wizard welcome screen appears. Click Next to continue. Figure 17: InstallShield Wizard Welcome Screen 4 Accept the terms of the license Agreement and click Next to continue.
Chapter 4: Upgrading the Ridgeline Software 5 Accept the default installation directory or click Browse to select a different location. Click Next to continue.
Upgrading from EPICenter or Ridgeline Service Advisor to Ridgeline 6 Specify (verify or change) the ports to use for communication between the Ridgeline server and the database (default is 10553), between the server and Ridgeline clients via HTTP (default is 8080), and between the switches and FreeRADIUS server (default is 10559).
Chapter 4: Upgrading the Ridgeline Software 7 Select the settings you want to enable (both are enabled by default): ● Enable Automatic Updates. This feature configures Ridgeline to automatically retrieve the most current information about device and slot software and bootrom images from the Extreme Networks website each time you connect the client to the Ridgeline server.
Upgrading from EPICenter or Ridgeline Service Advisor to Ridgeline 8 Verify the components and installation directory, and click Install to continue. Figure 22: Installation Summary The installation process begins.
Chapter 4: Upgrading the Ridgeline Software 9 Select Yes to migrate the database or No to continue without doing so. Click Next to continue. When you install the Ridgeline 3.0 software, the installer automatically detects all supported prior versions of the network management software and prompts you to perform the migration. The supported versions include: EPICenter 6.0 Service Pack 1 and later releases and Ridgeline Service Advisor 2.0 and later releases.
Upgrading from EPICenter or Ridgeline Service Advisor to Ridgeline The InstallShield wizard displays a message when the installation is complete. Click Finish to exit the wizard. Figure 25: Post Installation Summary 10 Click OK to accept the warning messages that displays. The VM tracking feature requires an FTP server running prior to starting Ridgeline. Refer to the “Managing Virtual Machines” chapter in the Ridgeline Reference Guide for more information.
Chapter 4: Upgrading the Ridgeline Software 11 Ridgeline prompts you to restart your system. You must either restart your system or start the Ridgeline services manually before a client can connect to the Ridgeline server. Select one and then click Finish to complete the installation process. Figure 27: Reboot 12 Launch the License Manager and install your Ridgeline licenses. You can do this at any time after you have installed the Ridgeline server.
Migrating the Database When Ridgeline and a Previous Version are Installed on the Same System To migrate data from an earlier version of EPICenter or Ridgeline to the latest version of Ridgeline when an older version is installed on the same system as the latest version of Ridgeline, do the following: WARNING! This procedure overwrites any database information that is on the latest version of Ridgeline. We recommend you perform this procedure before you use Ridgeline.
Chapter 4: Upgrading the Ridgeline Software Figure 29: Enter Directory Paths of Previous Version and Latest Version 5 Click Migrate. The status screen opens showing the migration progress. See Figure 30. Figure 30: Database Migration Progress 6 Reboot the server. Exporting then Importing Data Migrating data from another server or operating system to a server with Ridgeline installed requires two operations.
Exporting then Importing Data 4 Enter the URL for the server where the latest version of Ridgeline is installed, for example: http://10.255.25.25:8080/exporter.html The Ridgeline Welcome screen for the Exporter opens. Figure 31: Ridgeline Exporter Welcome Screen 5 Click Launch Exporter. The Opening Exporter.jnlp dialog box opens. See Figure 32. Figure 32: Opening Exporter.jnlp 6 Use the default for: What should Firefox do with this file? Then click OK.
Chapter 4: Upgrading the Ridgeline Software You are reminded: Please make sure you are running this tool on the server which has the old database. Figure 33: Database Exporter Initial Dialog Box 7 Click Next. The Export database to archive files dialog box opens. See Figure 34. Figure 34: Enter Paths in Database Exporter 8 Enter the directory path of the older version of the product. The old product version is shown. 9 Enter the directory path where you are migrating the database to.
Exporting then Importing Data Figure 35: Export Database Progress Screen 13 Copy the export folder to the server where the latest version of Ridgeline is installed. Importing Database Information CAUTION The procedure described in this section overwrites any database information on the latest version of Ridgeline. We recommend that you perform this pro cu du re before you use Ridgeline.
Chapter 4: Upgrading the Ridgeline Software 4 Click Next. The dialog box opens where you enter the import information for the Ridgeline server. See Figure 37. Figure 37: Import Archived Database Files 5 Enter the required information: ● Import from directory. The directory where the Export folder is located on the exporting server. ● The Ridgeline directory at Program Files>Extreme Networks>Ridgeline directory 6 Click Next. The status screen opens showing the migration progress. See Figure 38.
