Ridgeline Service Advisor Release Note Software Version 2.0 Extreme Networks, Inc. 3585 Monroe Street Santa Clara, California 95051 (888) 257-3000 (408) 579-2800 http://www.extremenetworks.com Part number: 120579-00 Rev.
AccessAdapt, Alpine, Altitude, BlackDiamond, 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, the Extreme Networks logo, the Alpine logo,
Contents Chapter 1: Overview ........................................................................................................................ 3 New Hardware Supported in Ridgeline SA 2.0 ...............................................................................3 Key Features in Ridgeline SA 2.0 .................................................................................................3 Important Information about Using Ridgeline SA..........................................................
Message about Ridgeline SA’s digital signature appears twice ...........................................26 Multibyte-encoded characters display incorrectly in Ridgeline SA Client .............................27 Connection error when Ridgeline SA server and client are in different domains....................27 General—Server ..................................................................................................................27 TFTP port remains in use after Ridgeline SA TFTP server disabled ....
1 Overview This release note contains a summary of the requirements and new features for the Ridgeline Service Advisor™ Management Suite, version 2.0. ● See “New Hardware Supported in Ridgeline SA 2.0” for a list of the new Extreme Networks devices supported in this release. ● See Table 3 for a full list of the Extreme Networks devices supported by Ridgeline SA 2.0. Please refer to the Ridgeline Service Advisor Reference Guide for detailed descriptions of the features in the Ridgeline SA 2.0 release.
Overview Windows platforms, as well as the 32-bit and 64-bit versions of the supported Red Hat Enterprise Linux platform. ● Map view of all devices in your network. The new All Map option under Network Views displays a graphical view of all of the devices managed by Ridgeline SA. From the All Map view, you can see a map view, navigation table, and details panel containing information about all the managed devices in your network. ● Customizable Ridgeline SA Home Page.
Important Information about Using Ridgeline SA ● EAPS provisioning. You can use the EAPS provisioning feature to configure new EAPS domains, including specifying member links, the EAPS master node, primary and secondary ports, control VLAN, hello timer, and fail timer parameters. Your configuration is validated by the software before it is deployed to managed devices. EAPS provisioning is supported on Extreme switches running ExtremeXOS 12.4 and higher.
Overview 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.
Important Information about Using Ridgeline SA You can also display the serial numbers of devices in your network by running a Device Details report in Ridgeline SA.
Overview To display the serial numbers of individual modules, run the Card Summary report. For example: Figure 4: All Cards Card Summary Report Providing Serial Numbers to Extreme Networks eSupport To provide serial numbers to Extreme Networks eSupport, do the following: 1 Go to www.extremenetworks.com 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.
Important Information about Using Ridgeline SA 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. Figure 7: Serial number entry box NOTE For chassis devices, you must provide the serial number of a Management Module or I/O Module. 4 Accept the terms of the software license agreement and click Submit.
Overview 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 SA 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 SA server.
Ridgeline SA Server Requirements The Ridgeline SA TFTP Server Ridgeline SA’s built-in TFTP server is intended only for uploading and downloading switch configuration files and software image files under Ridgeline SA’s control. It is not intended for use as a general purpose TFTP server.
Overview ● 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. ● 1 GHz or greater Pentium-compatible processor (2 GHz recommended). The Ridgeline SA server software requires the 1.6.0_10 (or higher) Java runtime package. The 1.6.0_10 Java runtime package is included in the server installation, and that is the version we recommend you use. NOTE Additional disk space may be needed to hold alarm logs and other runtime data.
Ridgeline SA Client 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. ● A GUI/Desktop environment must be installed on the server machine. The Ridgeline SA server software requires the 1.6.0_10 (or higher) Java runtime package. The 1.6.0_10 Java runtime package is included in the server installation, and that is the version we recommend you use.
Overview Microsoft Windows The system requirements for the Ridgeline SA client under Microsoft Windows are as follows: ● Windows Vista, XP Professional with SP1 or later, Windows 2003 Server, or Windows 2008 Server 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 (1 GB recommended).
ExtremeWare/ExtremeXOS Support Requirements Table 1: Ridgeline SA 2.0 Supported Browsers Platform Minimum Browser Configuration Microsoft Windows Internet Explorer™ 6.0, 7.0, 8.0; Mozilla Firefox 1.5, 2.0, 3.0 Sun Solaris 10 Mozilla Firefox 1.5, 2.0, 3.0 Red Hat Enterprise Linux 5 Mozilla Firefox 3.0 NOTE For the Mozilla Firefox browser, you must install the Java Plug-In, then link the plug-in to the Firefox browser. See the Ridgeline SA Installation and Upgrade Guide for instructions.
Overview Table 2: ExtremeWare/ExtremeXOS Versions Supported by Ridgeline SA 2.0 (continued) Extreme Switch Platform ExtremeWare Versions Supported Summit 300-48 6.2a or later 7.3e or later required for 802.1x and SNMPv3 support Summit 400-24 7.4 or later Summit 400-48 7.2e or later 7.3e or later required for 802.1x and SNMPv3 support 7.4 or later required for S400s stacking support. All “i” Series switches, Alpine, MSM64i 6.2 or later 7.1 or later required for 802.
Ridgeline SA 2.0 Device Support ● SNMP must be enabled on the switch for Ridgeline SA to discover the device, and for Ridgeline SA to manage the switch. ● If you use access profiles to control SNMP, Telnet and SSH access to your switches, you must ensure that the Ridgeline SA host’s IP address is permitted in those access profiles. Ridgeline SA 2.0 Device Support With a Base 20 license, Ridgeline SA 2.0 supports up to 20 managed devices.
Overview Table 3: Extreme Networks Devices Supported by Ridgeline SA 2.0 (continued) Switches/Modules Summit X480 series: * Summit X480-24x Summit X480-24x-SS Summit X480-24xSS128 Summit X480-24x10G4X Summit X480-48t Summit X480-48t-SS Summit X480-48t-SS128 Summit X480-48t-10G4X Summit X480-48x Summit X480-48x-SS Summit X480-48xSS128 Summit X480-48x10G4X Ridgeline SA 2.
Ridgeline SA Software Licensing Table 5 provides a summary of Ridgeline SA’s basic support for non-Extreme devices. Table 5: Third-Party Device Support by Feature Feature Third-Party Device Support Inventory MIB-2 compatible devices: status only, SNMP v1 only. Integrated support for devices included through the Integration Framework. Alarms MIB-2 compatible devices: standard traps. Integrated alarm support for devices included through the Integration Framework.
Overview ● The Advanced Services Pack license adds VPLS and PBB features to Ridgeline SA. Both permanent and evaluation license keys are 14-character keys that start with EP and are followed by 12 additional upper- and lower-case alphabetic characters, numbers, and special characters such as “+”. If you have purchased the product, you should have received an activation key, found on the License Agreement that accompanies your software package.
Ridgeline SA Software Documentation The Ridgeline SA Concepts and Solutions Guide provides discussions and examples of how to use Ridgeline SA to manage your Extreme Networks installation. It is available in Acrobat PDF format, accessed from the Programs > Extreme Networks > Ridgeline Service Advisor 2.0 submenu on the Windows Start menu. It can also be found in the extreme.war\helptext\docs subdirectory of the Ridgeline SA installation.
Overview 22 Ridgeline Service Advisor Release Note
2 Clarifications, Known Behaviors, and Resolved Issues This section describes known problems with the Ridgeline SA 2.0 release, including recommendations for workarounds when available. It also lists problems that existed in previous versions of Ridgeline SA that have been fixed in this release. Numbers in parentheses are for internal tracking. For the latest release notes, patches, and bug list, see: http://www.extremenetworks.com/go/esupport.htm.
Clarifications, Known Behaviors, and Resolved Issues Clarifications and Known Problems The following known problems and clarifications apply to this release: 1 Inventory: Single VLAN data collection does not occur for devices with version ExtremeXOS 12.4.1.5 or 12.4.1.9. When VLANs are created or modified on a device and SmarTraps are sent to Ridgeline SARidgeline. Ridgeline SA then polls the device for the new/modified VLAN related configuration changes and updates the new/modified VLAN data.
Clarifications and Known Problems 20 EAPS Control VLAN: An EAPS control VLAN does not have to be assigned a QP8 by Ridgeline EAPS provisioning. (PD4-1364407944) 21 VPLS Status: VPLS status (admin, operational) is shown as Up for VPLS instances that are in a signal state on a device. (PD4-1360898185) 22 vMAN Provisioning: vMAN provisioning should validate whether the same ethertype is used in all the switches that are being provisioned.
Clarifications, Known Behaviors, and Resolved Issues still detects the previous installation. To solve this problem the InstallShield Vital Product Data (VPD) registry may need to be cleaned up. This registry is a directory that resides at \Program Files\Common Files\InstallShield\Universal (in Windows) or in ~/InstallShield in Linux or Solaris. You need to remove the directory extremenetworks\epicenter under this VPD registry.
Clarifications and Known Problems Multibyte-encoded characters display incorrectly in Ridgeline SA Client If you create a device group that includes multibyte-encoded characters (such as Japanese characters) in its name, the device group name may not display correctly in Ridgeline SA. The Ridgeline SA Client does not support character sets that use multibyte encoding.
Clarifications, Known Behaviors, and Resolved Issues Error when disabling EAPS primary port if EAPS ring was displayed in the Map View If the primary port in an EAPS node was disabled while the EAPS ring was displayed in the Ridgeline SA Map View, it resulted in an IllegalArgumentException error. (PD4-707645154) Updated EAPS information not displayed in the Table View When the status of an EAPS domain changed, the updated information was displayed in the Map View, but not the Table View.
Clarifications and Known Problems Changing the Diff or Config file viewer settings does not work properly Changing the settings for the configuration file viewer or the Diff viewer does not work properly when the client is connected to a Linux server. For the configuration viewer it will attempt to use the viewer configured on the server; for a Diff it uses sdiff, which is available locally.
Clarifications, Known Behaviors, and Resolved Issues Inventory Management Modify Device changed fields are not updated after Apply When a change is made in the Modify Device dialog, after clicking Apply the change is not reflected in the fields in the Modify Device window. You must close and re-open the Modify Device dialog to see the changes.
Clarifications and Known Problems its subgroups at the same level, then changes the display to show only the ports in the top level group. (PD3-40487688) Reports User Defined Reports link does not appear the first time Reports are invoked When you display the Reports feature for the first time after installing Ridgeline SA 2.0, the User Defined Reports link does not appear. Once you refresh the browser, the link appears and works properly from then on. (PD3-106204511).
Clarifications, Known Behaviors, and Resolved Issues Avaya-Ridgeline SA Integration NOTE These items apply only to customers with the Avaya Integrated Management server version 3.1 co-resident with the Ridgeline SA server. Ridgeline SA complains about missing device when launched from AIM When Ridgeline SA is launched from the Avaya Integrated Management software, it complains that “Device 127.0.0.1” is not in Inventory. You can ignore this message.
