Extreme Networks Ridgeline, Ridgeline 3.0 Installation Manual
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. 01
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.
© 2011 Extreme Networks, Inc. All Rights Reserved.
2
Ridgeline Installation and Upgrade Guide
Contents
Chapter 1: Installation Overview ...............................................................................................................5
Installation Overview ................................................................................................................................................5
The Ridgeline Server ........................................................................................................................................5
Upgrading the Ridgeline Server.................................................................................................................6
The Ridgeline Client ..........................................................................................................................................6
System Requirements ..............................................................................................................................................7
Windows Vista/XP/2003 Server/2008 Server/Windows 7 .................................................................................7
The Ridgeline Server ..........................................................................................................................7
The Ridgeline Client ...........................................................................................................................7
Sun Microsystems Solaris 10............................................................................................................................8
The Ridgeline Server ..........................................................................................................................8
The Ridgeline Client ...........................................................................................................................8
Red Hat Enterprise Linux 5 ...............................................................................................................................8
The Ridgeline Server ..........................................................................................................................8
The Ridgeline Client ...........................................................................................................................9
Browser Requirements for Launching the Ridgeline Client...............................................................................9
Upgrading Ridgeline to a Service Pack Release....................................................................................................10
Obtaining a License Key for the Ridgeline Server..................................................................................................10
Evaluation Licenses ........................................................................................................................................10
Permanent Licenses .......................................................................................................................................11
Chapter 2: Installing the Ridgeline 3.0 Server ....................................................................................... 13
Installing the Ridgeline Server................................................................................................................................13
User Permissions ............................................................................................................................................14
Local Name Resolution for the Server ............................................................................................................14
Required Patches for Solaris ..........................................................................................................................14
Setting the Run Level for Linux .......................................................................................................................14
Installation Overview .......................................................................................................................................14
Server Installation Steps .................................................................................................................................15
Adding or Upgrading a License Key.......................................................................................................................23
Adding a License for an Upgrade Product ......................................................................................................24
Starting and Stopping the Ridgeline Server ...........................................................................................................24
Starting the Server on Windows......................................................................................................................24
Starting the Server on Linux or Solaris ...........................................................................................................24
Stopping the Server on Windows....................................................................................................................25
Stopping the Server on Linux or Solaris..........................................................................................................25
Configuring the Ridgeline Server for NATed Client Connections ...........................................................................25
Installing Ridgeline on a Multi-Homed Server ........................................................................................................26
Setting the EPICENTER_SERVER_ADDRESS Environment Variable..........................................................26
Configuring a Multi-Homed Server with Separate Management and Client Access Networks .......................27
Configuring the Multi-Homed Server with NAT ........................................................................................28
Configuring the Multi-Homed Server for Client Access from Both Networks ..................................................29
Installing a Difference Viewer .................................................................................................................................29
For Windows.....................................................................................................................................29
For Linux or Solaris...........................................................................................................................29
Enabling SSH for Secure Communications............................................................................................................29
The Ridgeline SSH Enabling Key ...................................................................................................................30
Ridgeline Installation and Upgrade Guide
3
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 ......................................................................................35
About the Client Initialization Process ....................................................................................................................35
Launching the Client Application ............................................................................................................................35
Disabling Installation of Desktop Shortcuts ............................................................................................................38
Configuring the Firefox Browser for the Java Plug-In.............................................................................................39
Chapter 4: Upgrading the Ridgeline Software .......................................................................................41
Ridgeline Software Upgrade Overview...................................................................................................................41
Installing a Service Pack Release ..........................................................................................................................42
Installing a Service Pack on Windows Systems..............................................................................................43
Uninstalling the Service Pack on Windows Systems ......................................................................................44
Installing a Service Pack on Solaris or Linux Systems....................................................................................44
Uninstalling the Service Pack on Solaris or Linux Systems ............................................................................45
Upgrading from EPICenter or Ridgeline Service Advisor to Ridgeline ...................................................................46
Migrating the Database ..........................................................................................................................................54
When Ridgeline and a Previous Version are Installed on the Same System..................................................55
Exporting then Importing Data................................................................................................................................56
Exporting Database Information......................................................................................................................56
Importing Database Information......................................................................................................................59
4
Ridgeline Installation and Upgrade Guide
Installation Overview
1
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 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 32bit version only) on SPARC workstations running Solaris 10, or on systems running Red Hat Enterprise
Linux version 5.
There are several options for installing the Ridgeline 3.0 software, depending on whether you already
have versions of Ridgeline installed, or whether this is a new Ridgeline installation.
The Ridgeline Server
The Ridgeline server requires a license key, installed into 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.
● See “Installing the Ridgeline Server” on page 13 for detailed instructions.
Ridgeline Installation and Upgrade Guide
5
NOTE
Chapter 1: Installation Overview
● See “Adding or Upgrading a License Key” on page 23 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 29 for instructions on obtaining and installing a
difference viewer.
● See “Enabling SSH for Secure Communications” on page 29 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 10 for details.
If you have been running a beta version of the Ridgeline 3.0 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.0 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.
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_10 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.
6
Ridgeline Installation and Upgrade Guide
NOTE
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. 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 (Ridgeline 32-bit version only) running on an Intel Pentiumcompatible CPU.
Both 32-bit and 64-bit versions of the Windows operating system are supported.
● 2 GB RAM minimum, 4 GB recommended.
Up to 4 GB may be needed to manage very large numbers of devices (1000 or more).
● 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 1.6.0_10 Java runtime package, which is included in the
server installation. No separate installation is needed.
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 65536 colors.
● 512 MB RAM minimum (up to 1 GB 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.
Ridgeline Installation and Upgrade Guide
7
NOTE
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.
● 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.
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.
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 65536 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.0, is supported on Red Hat Enterprise
Linux version 5. Both the 32-bit and 64-bit versions are supported, only on X-86 based platforms. The
system requirements 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).
● 1 GHz or greater Pentium-compatible processor (2 GHz recommended).
● 2 GB disk space available.
● 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.
● A GUI/Desktop environment must be installed on the server machine.
8
Ridgeline Installation and Upgrade Guide
NOTE
NOTE
NOTE
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.
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 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.
● 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.
The Java plug-in version 1.6.0_10 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.
Tab le 1 lists the browsers that are supported by the Ridgeline 3.0 release. A browser is also required to
display Ridgeline reports and the Ridgeline online help.
Table 1: Ridgeline 3.0 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
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 39
Ridgeline Installation and Upgrade Guide
9
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. 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 42 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.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 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, as described in “Adding or Upgrading a License Key” on page 23.)
● 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.
● A permanent license has no time limit. Permanent licenses are sold based on the number of devices
you want Ridgeline to manage.
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 “RC,” and is found on the
license agreement shipped with your purchased product. You use the activation key to obtain a
permanent license key as described below.
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.
Evaluation Licenses
You do not need an activation key to obtain an evaluation license key. To obtain an evaluation license
key, go to
Select the option to obtain an evaluation license key. You are asked to enter your name, company
information, and similar information, and an email address to which your license key should be sent.
www.extremenetworks.com/go/ridgelinelicense.
10
Ridgeline Installation and Upgrade Guide
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.extremenetworks.com/go/ridgelinelicense and select the option to
obtain a permanent license key.
Fill in the requested information, and enter your activation key. The activation key is a 14-character key
that starts with “RC” found on the license agreement you received when you purchased the product.
Your permanent license key will be sent to you by return email.
Ridgeline Installation and Upgrade Guide
11
Chapter 1: Installation Overview
12
Ridgeline Installation and Upgrade Guide
Installing the Ridgeline 3.0
Server
2
CHAPTER
This chapter describes how to install or upgrade the Ridgeline 3.0 server software in Windows, Solaris,
and Linux, and includes the following sections:
● Installing the Ridgeline Server on page 13
● Installation Overview on page 14
● Server Installation Steps on page 15
● Adding or Upgrading a License Key on page 23
● Starting and Stopping the Ridgeline Server on page 24
● Configuring the Ridgeline Server for NATed Client Connections on page 25
● Installing Ridgeline on a Multi-Homed Server on page 26
● Installing a Difference Viewer on page 29
● Enabling SSH for Secure Communications on page 29
● Uninstalling the Ridgeline Server Software on page 31
Installing the Ridgeline Server
The Ridgeline server can be installed 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
● Solaris 10 running on a SPARC system
or
● Red Hat Enterprise Linux Version 5
See “System Requirements” on page 7 for memory, CPU, disk and other requirements.
Ridgeline Installation and Upgrade Guide
13
CAUTION
Chapter 2: Installing the Ridgeline 3.0 Server
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. 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 23.
User Permissions
To install the Ridgeline software components as services under Microsoft Windows, or as daemons
under Solaris/Linux, you must have administrator privileges on that system. In addition, if you want to
be able to import user and host information from a Windows Domain Controller, the Ridgeline server
must run with permissions that allow it to get user information from the Domain Controller.
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
resolve both
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
system1 and its domain name, such as system1.company.com. You can test for this by
hosts file contains the correct information.
system1, then it must be able to
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
www.extremenetworks.com.
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.
Installation Overview
The installation process is very similar under all three operating environments: the few differences are
noted as appropriate during the description of the process.
To install the Ridgeline server you will need the following information:
● The port that the Ridgeline server will use to communicate with the database (default is 10553)
● The HTTP port for communication with Ridgeline clients (default is 8080)
● See “Obtaining a License Key for the Ridgeline Server” on page 10 for more information.
14
Ridgeline Installation and Upgrade Guide
NOTE
NOTE
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.
If you intend to keep multiple versions of the Ridgeline server on the same computer, to avoid a port
conflict each Ridgeline server must be configured to use a unique port number to communicate with the
database, or all but one of the Ridgeline servers must be disabled.
Extreme Networks recommends that you choose port numbers that are not currently registered at Internet
Assigned Numbers Authority (IANA). To check if a port number is registered, go to http://www.iana.org/
numbers.html.
Within the installation procedure you can choose to do the following:
● Enable automatic information updates, allowing Ridgeline to connect to the Extreme web site when
you start the Ridgeline client, and once every 24 hours thereafter to obtain a list of the current
ExtremeWare and ExtremeXOS releases as well as the latest Ridgeline patches.
● Start the Ridgeline database and server components manually at system startup (in Windows).
● Restart your system to start the Ridgeline database and server.
After your installation is complete, you must run the License Manager to install your Ridgeline license
key(s). Clients will not be able to connect to the Ridgeline server until that is done.
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.
Server Installation Steps
To install the Ridgeline server do the following:
1 Download the Ridgeline 3.0 server software for your chosen platform (Windows, Linux or Solaris)
from the Extreme Networks software download page, and extract the contents of the zip or tar file
into a temporary directory.
or
Insert the Ridgeline server installation CD into your CD drive.
2 If you are installing from CD, you will find three installation executables, one for each platform
(Windows, Linux, and Solaris). If you downloaded from the web site, only the executable for your
platform will be included.
3 Start the installation wizard as follows:
For Windows, run
version of the operating system.
Ridgeline_3-0_win32.exe or Ridgeline_3-0_win64.exe, depending on your
Ridgeline Installation and Upgrade Guide
15
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.
For Solaris:
a If you downloaded the installation from the web site, change the permissions on the Solaris bin
file:
chmod 755 Ridgeline_3-0_solarisSPARC.bin
(Skip this if you are installing from the CD).
b Run the executable
Ridgeline_3-0_solarisSPARC.bin
InstallShield will extract the Ridgeline Installation Wizard. This may take a few minutes.
4 The Ridgeline Installer Welcome screen appears.
Click Next to continue.
Figure 1: InstallShield Wizard Welcome Screen
5 If a previous version of Ridgeline is detected, you are notified that the existing Ridgeline services
must be stopped.
16
Ridgeline Installation and Upgrade Guide
Installing the Ridgeline Server
On Windows systems, if the Ridgeline components were installed as services, select one of the
following options:
● Select Ye s 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.
6 Next, the Ridgeline Software license agreement is presented; after you read the agreement, click the
Accept button to accept the agreement, and click Next to proceed.
Figure 2: License Agreement
Ridgeline Installation and Upgrade Guide
17
NOTE
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.
Figure 3: Installation Destination
8 You are next asked to specify (verify or change) the ports to be used for communication between the
Ridgeline server and the database (default is 10553) and between the server and Ridgeline clients via
HTTP (default is 8080). 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.
If you intend to keep multiple versions of the Ridgeline server on the same computer, to avoid a port
conflict, each Ridgeline server must be configured to use a unique port number to communicate with the
database, or all but one of the Ridgeline servers must be disabled. If multiple versions of the Ridgeline server
are detected on the computer, the older versions are disabled automatically during installation.
18
Ridgeline Installation and Upgrade Guide
Loading...