Ridgeline Installation and Upgrade Guide
Copyright © © 2013 Extreme Networks, Inc. All Rights Reserved. Extreme Networks and the Extreme Networks logo are trademarks or registered trademarks of Extreme Networks, Inc. in the United States and/or other countries.
Table of Contents Chapter 1: Installation Overview 4 Installation Overview 4 System Requirements 6 Upgrading Ridgeline to a Service Pack Release 8 Obtaining a License Key for the Ridgeline Server 9 Installing a Permanent License When an Evaluation License is Already Installed 10 Chapter 2: Downloading Ridgeline Software 11 Overview 11 Determining Device Serial Numbers 12 Providing Serial Numbers to Extreme Networks eSupport 13 Chapter 3: Installing the Ridgeline 4.
1 Installation Overview Installation Overview System Requirements Upgrading Ridgeline to a Service Pack Release Obtaining a License Key for the Ridgeline Server Installing a Permanent License When an Evaluation License is Already Installed This chapter provides an overview of the installation or upgrade of Ridgeline software. Note Ridgeline does not provide multi-language support.
Installation Overview • A 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. For information about enabling Ridgeline to use SSH, see Enabling SSH for Secure Communications. Upgrading the Ridgeline Server Occasionally, Extreme Networks may choose to release updates to Ridgeline as a service pack release.
Installation Overview • • Reduce your inventory of managed devices to 300, or fewer, prior to upgrading. Choose not to migrate your database when performing the upgrade installation. After the upgrade installation, you will need to re-create an inventory by discovering or adding devices (for information about discovering and adding devices, see the Ridgeline Reference Guide.) System Requirements The following sections specify the system requirements for installing and running Ridgeline 4.0.
Installation Overview • • • 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 65536 colors. 512 MB RAM minimum (up to 1 GB recommended). Note To run the Ridgeline client and server on the same machine, 4 GB RAM is recommended.
Installation Overview • • • • • A monitor that supports at least 1024 x 768 resolution and 16-bit color. Your system display settings must be set for at least 65536 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. An Internet browser (Mozilla Firefox 1.5 or higher) is required to display reports and view the Ridgeline online help.
Installation Overview After you upgrade the Ridgeline 4.0 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 start the client. Obtaining a License Key for the Ridgeline Server To log on 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.
Installation Overview 3 Enter your name, company information, and similar information, and an e-mail address to which your license key should be sent. Your evaluation license key is e-mailed to you. 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.
2 Downloading Ridgeline Software Overview Determining Device Serial Numbers Providing Serial Numbers to Extreme Networks eSupport This chapter explains how to download images from the Extreme Networks eSupport. In some specific cases, the process might be different and is noted when applicable. Overview Using the Ridgeline Firmware Manager, you can download software and BootROM images from Extreme Networks to your Ridgeline server, and then upgrade the devices in your network with the new images.
Downloading Ridgeline Software Determining Device Serial Numbers The serial number for a device appears in the Device Properties window. To display this window, in the navigation pane, click Main View or the device group that has the desired device, select the device by clicking its check box, and then click Properties. The device serial number appears in the System ID field, as shown in the following figure.
Downloading Ridgeline Software Figure 3: Device Details Report 1—Chassis part number 2—Device serial number Figure 4: All Cards Card Summary Report Providing Serial Numbers to Extreme Networks eSupport To provide serial numbers to Extreme Networks eSupport: Ridgeline Installation and Upgrade Guide 13
Downloading Ridgeline Software 1 Go to www.extremenetworks.com/go/esupport.htm and log on to the eSupport page with your eSupport user ID and password. Figure 5: eSupport Log on Page 2 Click Download Software Updates (see the following figure).
Downloading Ridgeline Software 3 In the Serial # box, type the serial number of the device or module, and then 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.
Downloading Ridgeline Software 4 Accept the terms of the software license agreement and click Submit. Figure 8: Software License Agreement A table of the software versions available for the device appears. If the device is under a service contract, all software versions appear; otherwise, only software versions available for the 90-day warranty period appear.
Downloading Ridgeline Software 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.
3 Installing the Ridgeline 4.0 Server Installation Overview Installing the Ridgeline Server Adding or Upgrading License Keys Starting and Stopping the Ridgeline Server Configuring the Ridgeline Server for NATed Client Connections Installing Ridgeline on a Multi-homed Server Installing Alternative Viewers and Difference Viewers Enabling SSH for Secure Communications Uninstalling the Ridgeline Server Software This chapter describes how to install or upgrade the Ridgeline 4.
Installing the Ridgeline 4.0 Server Ridgeline 4.0 Device Inventory Limit Ridgeline 4.0 permits you to manage a maximum of 300 devices in inventory. This could be significant if you are upgrading from a previous version of Ridgeline (earlier versions of Ridgeline supported more devices). To avoid problems when installing, you are advised to do one of the following: • Reduce your inventory of managed devices to 300, or fewer, prior to upgrading.
Installing the Ridgeline 4.0 Server Installing the Ridgeline Server Caution If you have a previous version of Ridgeline with an inventory of managed devices that exceeds 300, see Ridgeline 4.0 Device Inventory Limit for important information before installing Ridgeline 4.0. To install the Ridgeline server: 1 Download the Ridgeline software from the Extreme Networks eSupport software download page (www.extremenetworks.com/services/software-updates-archives.aspx).
Installing the Ridgeline 4.0 Server 4 Click Next. The Ridgeline 4.0 license agreement dialog box appears (see the following figure) Figure 12: Ridgeline 4.0 License Agreement Dialog Box 5 After you read the agreement, click I accept the terms of the License Agreement to consent, and then click Next. The Ridgeline 4.0 installation settings dialog box appears (see the following figure) Figure 13: Ridgeline 4.
Installing the Ridgeline 4.0 Server 7 Click Next. The Ridgeline 4.0 installation client IP address dialog box appears (see the following figure). Figure 14: Ridgeline 4.0 Installation Client IP Address Dialog Box • • • Use this IP address to launch the clients and to talk to the network devices Select an IP address from the list. The list 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.
Installing the Ridgeline 4.0 Server 9 Click Next. The Ridgeline 4.0 installation database migration decision dialog box appears (see the following figure). Caution If you have a previous version of Ridgeline with an inventory of managed devices that exceeds 300, see Ridgeline 4.0 Device Inventory Limit for important information before migrating your database. Figure 15: Ridgeline 4.0 Installation Database Migration Decision Dialog Box 10 Select either: • • Yes, start the database migration assistant.
Installing the Ridgeline 4.0 Server 11 Click Next. The Ridgeline 4.0 installation review settings dialog box appears (see the following figure). Figure 16: Ridgeline 4.
Installing the Ridgeline 4.0 Server 12 Review the settings, and then click Install. The Ridgeline 4.0 installation progression dialog box appears (see the following figure). Figure 17: Ridgeline 4.0 Installation Progression Dialog Box The Ridgeline 4.0 installation Migration Tool dialog box appears (see the following figure). Figure 18: Ridgeline Migration Tool v1.
Installing the Ridgeline 4.0 Server 13 In Step 10 if you chose to migrate your database, the migration tool appears. Make selections for the following (for detailed instructions about how to perform a local migration, see Performing a Local Database Migration; for instruction for a remote migration, see Performing a Remote Database Migration): Under Source: • • • • • • Release—select the release that you have currently installed Off-line Migration—For remote migrations.
Installing the Ridgeline 4.0 Server 14 Click Start Migration. The following occurs while migrating the database: • Visual C++ redistributable 2010 is installed/upgraded as part of PostgreSQL database server installation (Windows only) • PostgreSQL database is installed. • Creates and initializes Ridgeline database. • If the migration of the database fails, installation stops and an error message appears. The Ridgeline 4.
Installing the Ridgeline 4.0 Server 15 Click Next. The Ridgeline 4.0 VM tracking feature alert dialog box appears (see the following figure). Figure 20: Ridgeline 4.0 VM Tracking Feature Alert Dialog Box The dialog box informs you that VM tracking requires an FTP server to be running if you use this feature. 16 Click Next. The Extreme Networks License Manager dialog box appears (see the following figure).
Installing the Ridgeline 4.0 Server 17 Click Install license if you entered license key(s); otherwise, click Cancel. The Ridgeline 4.0 installation success dialog box appears (see the following figure). Figure 22: Ridgeline 4.0 Installation Success Dialog Box You are informed the Ridgeline 4.0 installation was successful.
Installing the Ridgeline 4.0 Server 18 Click Next. The Ridgeline 4.0 installation system restart dialog appears (see the following figure). Figure 23: Ridgeline 4.0 Installation System Restart Dialog Box Select one of the following: • • Yes, Restart system now No, I will restart system myself later Caution You must restart the computer after installing or the database service for Ridgeline 4.0 may not start. If the database service does not start, you cannot connect to Ridgeline with a client.
Installing the Ridgeline 4.0 Server Figure 24: Ridgeline 4.0 Installation Settings Dialog Box . 1 Click Next. The Ridgeline 4.0 installation destination folder dialog box appears (see the following figure). Figure 25: Ridgeline 4.0 installation destination folder Dialog Box To set up a custom directory, type the directory path or browse to find the directory where you want to install Ridgeline 4.0.
Installing the Ridgeline 4.0 Server 2 Click Next. The Ridgeline 4.0 installation Windows services start-up dialog box appears (see the following figure). Figure 26: Ridgeline 4.0 installation Windows Services Start-up Dialog Box • To start Ridgeline services automatically when Windows starts, select the Start services automatically at startup check box. This is selected by default. • To have Ridgeline automatically search for updates and install them on the server, select Enable automatic updates.
Installing the Ridgeline 4.0 Server Performing a Remote Database Migration Use remote migration if the source release (either Ridgeline 3.0 or 3.1) and target release (4.0) are installed on different machines. Before migrating your database, do the following: • Edit <40-target-installation>/dbmigration/config/dbmigration.property file and set ridgeline.check.source.version value to false. • Start the source database on the remote machine. 1 Start the database migration tool.
Installing the Ridgeline 4.0 Server Adding or Upgrading License Keys The License Manager installs new or upgrade Ridgeline license keys. You can run the License Manager at any time after installing the Ridgeline server. Until you install a license, no client can connect to the Ridgeline server. You can run the License Manager to: Install an evaluation or permanent license. Upgrade an evaluation license to a permanent license. Upgrade to control additional devices.
Installing the Ridgeline 4.0 Server 2 Enter the 14-character license key(s) in the appropriate box(es), and then click Install license. A message appears telling you if the installation was successful or not. Starting and Stopping the Ridgeline Server By default, the Ridgeline server components installed as services (in Windows) or daemons (in Linux) are started automatically when you start or restart your computer.
Installing the Ridgeline 4.0 Server Table 2: Linux Start-up and Shutdown Commands for Ridgeline 4.0 Command Function Usage RidgelineDB40 start Start RidgelineDB None RidgelineDB40 stop Stop RidgelineServer if running, then stop RidgelineDB Otherwise, simply stop RidgelineDB. Use this command only when RidgelineServer is completely shutdown. See the RidgelineServer40 status command.
Installing the Ridgeline 4.0 Server Configuring the Ridgeline Server for NATed Client Connections If clients are connecting to the Ridgeline server through a connection that uses Network Address Translation (NAT), configure the Ridgeline server appropriately: 1 Stop the Ridgeline server if it is currently running. For information about how to stop the server, see Starting and Stopping the Ridgeline Server. 2 Start the Server Setup Utility and click Use this host name to launch the clients.
Installing the Ridgeline 4.0 Server To configure Ridgeline for multi-homed servers: 1 Stop the Ridgeline server. See Stopping the Server on Windows. 2 Start the Ridgeline Server Setup Utility: • • On a Windows system, click Start > Programs > Extreme Networks > Ridgeline4.0 > Server setup utility. On Linux, the server setup utility from symbolic link is in /root/ExtremeNetworks/ Ridgeline4.0/Server Setup Utility. The Ridgeline Server Setup Utility dialog box appears (see the following figure).
Installing the Ridgeline 4.0 Server Installing Alternative Viewers and Difference Viewers Ridgeline provides a view feature, for viewing configuration files, and a Diff feature that allows you to compare configuration files using a difference viewer. A difference viewer compares and highlights the differences between two files. The Diff feature does not work with a standard text editor. Ridgeline provides a default viewer and differences viewer, but you can chose to install and enable a different ones.
Installing the Ridgeline 4.0 Server The Ridgeline SSH Enabling Key Ridgeline’s SSH2 capability can be enabled by installing the Ridgeline SSH enabling key. This module must be downloaded from Extreme Networks, as it is subject to export restrictions. It is not provided with the Ridgeline software distribution.
Installing the Ridgeline 4.0 Server 2 Exit all clients. 3 Click Start > Programs > Extreme Networks > Ridgeline 4.0 > Uninstall to start the uninstall process. The Uninstall Ridgeline 4.0 start dialog box appears (see the following figure). Figure 29: Uninstall Ridgeline 4.0 Start Dialog Box 4 Click Next. The Ridgeline 4.0 uninstall options dialog appears (see the following figure). Figure 30: Ridgeline 4.
Installing the Ridgeline 4.0 Server 5 You are asked if you want to remove logs, database, and backups. Chose one of the following: • • Yes, remove everything—Removes the program and all data. No, leave them behind—Removes the program, but not the data components (logs, databases, and backups). 6 Click Uninstall. The uninstall process begins. The Ridgeline 4.0 uninstall progress dialog box appears showing the progress (see the following figure). Figure 31: Ridgeline 4.
Installing the Ridgeline 4.0 Server 9 Click Done. Figure 32: Ridgeline 4.0 Un-removed Items Dialog Box Uninstalling the Server on Linux To remove the Ridgeline server software: 1 Stop the Ridgeline server components if they are running. See Stopping the Server on Linux. 2 Exit all clients. 3 On Linux, the uninstall wizard has a symbolic link in root/ExtremeNetworks/Ridgeline4.0/ Uninstall Ridgeline 4.0 4 Follow the onscreen instructions to uninstall the software.
4 Starting the Ridgeline 4.0 Client About the Client Initialization Process Starting the Client Program Disabling Installation of Desktop Shortcuts Configuring the Firefox Browser for the Java Plug-In This chapter describes how to connect to the Ridgeline 4.0 server and start the Ridgeline 4.0 client software. About the Client Initialization Process The Ridgeline client initialization process uses Java Web Start technology.
Starting the Ridgeline 4.0 Client 2 Enter the URL for your Ridgeline server, in the form: http://:/ Replace with the name or IP address of the system where the Ridgeline server is running. Replace with the HTTP port number that you assigned to the Ridgeline web server during installation. Note If you configured your Ridgeline server to use the default web server port 80, you do not need to include the port number.
Starting the Ridgeline 4.0 Client 5 (Optional) If you are planning to manage the virtual machines present in the Microsoft System Center Virtual Machine Manager (SCVMM), you must install the Ridgeline XNV agent on the SCVMM host. The prerequisites for the Ridgeline XNV agent are: • • • Microsoft .Net 4.
Starting the Ridgeline 4.0 Client Disabling Installation of Desktop Shortcuts As part of the Ridgeline client initialization process, a shortcut may be installed on your desktop. The desktop shortcut allows you to start the client without having to point a browser to the server (and clicking Log onto Ridgeline). Installation of the desktop shortcut assumes that the Java setting for Shortcut Creation is set to the default of Prompt user if hinted.
Starting the Ridgeline 4.0 Client To download and install the JRE plug-in, go to the Sun website at: www.java.com/en/download/ manual.jsp For Windows, you can download either the Online or Offline versions. For Linux, download the selfextracting file (not the RPM version). For installation instructions, click Instructions next to each file's download link.
5 Upgrading the Ridgeline Software Ridgeline Software Upgrade Overview Installing a Service Pack Release This chapter describes how to upgrade the Ridgeline software. Ridgeline Software Upgrade Overview The Ridgeline software is available in the following forms. You can select which one to install based on the circumstances under which you want to upgrade: • • Base installation.
Upgrading the Ridgeline Software Service packs can only be installed on their applicable base version of Ridgeline. You cannot install a service pack meant for a certain base version of Ridgeline on another base version. You must first install the required base version. Follow the installation instructions under Installing the Ridgeline Server on page 20. Note You cannot upgrade a Ridgeline beta release using this procedure. Uninstall the beta release, and then install the full Ridgeline release.
Upgrading the Ridgeline Software 6 Click Next. The Ridgeline installation welcome dialog box appears (see the following figure). Exit all programs before continuing to install the software. Figure 36: Ridgeline Installation Welcome Dialog Box 7 Click Next. The Ridgeline software license agreement dialog box appears (see the following figure).
Upgrading the Ridgeline Software 8 If you agree to the terms of the Ridgeline software license agreement, click I accept the terms of the License Agreement, and then click Next. The Ridgeline pre-installation summary dialog box shows the installation path for the service pack (see the following figure).
Upgrading the Ridgeline Software 9 Click Install. The Ridgeline progress indicator dialog box shows the progress of the software installation (see the following figure). Figure 39: Ridgeline Progress Indicator Dialog Box You are informed when the installation successfully finishes (see the following figure).
Upgrading the Ridgeline Software 10 Click Done. 11 Restart Ridgeline services (see Starting the Server on Windows). After the installation is complete, details about the installation process are in a log file Ridgeline4.0_InstallLog.log in the following locations: • • Windows: \Logs Linux:
Upgrading the Ridgeline Software 5 Click Uninstall. The Ridgeline uninstall progress dialog box shows the files and features being removed and a progress bar (see the following figure). Figure 42: Ridgeline Uninstall Progress Dialog Box 6 You are informed when the service pack is successfully uninstalled (see the following figure). Click Done.
Upgrading the Ridgeline Software 7 Restart Ridgeline services (see Starting the Server on Windows). After uninstalling, details about the process are in a log file Ridgeline4.0_InstallLog.log in the following locations: • Windows: \Logs • Linux: /Logs Uninstalling a Service Pack from the Windows Control Panel You can uninstall a service pack from the Windows Control Panel the same way you remove other programs.
Upgrading the Ridgeline Software 2 Exit all Ridgeline clients. 3 Stop Ridgeline services and database engines if they are running (see “Stopping the Server on Linux). 4 Back up your database. Also, if the database transaction log, basecamp.log, remains in the top-level Ridgeline installation directory after the Ridgeline server has been shut down, save it. (Typically, basecamp.log is removed when the server stops.) 5 Save the files basecamp.db and epicenter.
Upgrading the Ridgeline Software 4 Open a command shell and run Uninstall Ridgeline Service Pack .bin, where = the Ridgeline base version, and = the service pack number. To avoid permission errors, run the script as the same user that performed the Ridgeline service pack installation. The Ridgeline about to uninstall dialog box appears (see the following figure).
Upgrading the Ridgeline Software 5 Click Uninstall. The Ridgeline uninstall progress dialog box shows the files and features being removed and a progress bar (see the following figure). Figure 46: Ridgeline Uninstall Progress Dialog Box You are informed when the service pack is successfully uninstalled (see the following figure).
Upgrading the Ridgeline Software 6 Click Done. 7 Restart the Ridgeline server and the database engine (see Starting the Server on Linux).
Index A activation key 10 E evaluation copy license 9, 10 J Java runtime package 6, 7 L license key activation key 10 licensing obtaining a permanent license 10 obtaining an evaluation license 9, 10 M multi-homed server 37 U uninstalling the server under Windows 40 W Windows uninstalling the server 40 Ridgeline Installation and Upgrade Guide 61
