Release Note, EPICenter Management Suite Software Version 7.0 Service Pack 1 Extreme Networks, Inc. 3585 Monroe Street Santa Clara, California 95051 (888) 257-3000 (408) 579-2800 http://www.extremenetworks.com Published: May 2009 Part Number: 120495-00 Rev.
AccessAdapt, Alpine, Altitude, BlackDiamond, EPICenter, 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, ScreenPlay, Sentriant, ServiceWatch, Summit, SummitStack, Triumph, Unified Access Architecture, Unified Access RF Manager, UniStack, the Extreme Networks logo, the Alpine logo, the BlackDiamond logo, the Extreme Turbodriv
Contents Chapter 1: Overview ........................................................................................................................ 5 New Features/Changes in EPICenter 7.0........................................................................................5 What’s Different from Previous EPICenter Versions ...................................................................7 Important Information about Using EPICenter.......................................................................
Alarm Manager ...................................................................................................................27 Configuration Manager.........................................................................................................28 Firmware Manager...............................................................................................................28 Inventory Management.....................................................................................................
1 Overview This release note contains a summary of the requirements and new features for the EPICenter™ Management Suite, version 7.0. The EPICenter 7.0 Service Pack 1 release includes bug fixes and support for new Extreme Networks hardware; no new software features are included in this Service Pack release. ● See “Issues Resolved in the Service Pack 1 Release” on page 19 for descriptions of the fixes in this release.
Overview ● Integrated network topology maps. EPICenter’s network topology map feature is integrated with the new grouping functionality, so that when you create a device group, you have the option of selecting the Map View of the group, which causes EPICenter to generate a network topology map, populated with the devices in the group. EPICenter automatically adds any links that exist between the device nodes, and organizes them into submaps as appropriate.
Important Information about Using EPICenter What’s Different from Previous EPICenter Versions For users of previous versions of EPICenter, there are some significant changes in the way certain features work in EPICenter 7.0: ● No manual Client installation/upgrade. In previous releases, the installation or upgrade process for the EPICenter Client software required you to manually install the software application on your system. In EPICenter 7.
Overview Telnet Polling and EPICenter Although EPICenter primarily uses SNMP to retrieve switch status and configuration information, it uses Telnet polling to collect certain types of information that are not available using SNMP. This includes information about netlogins, device FDB data (if FDB polling is enabled) and other selected status.
EPICenter Server Requirements 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. Sun Microsystems Solaris 10 The EPICenter server software, version 7.0, is supported under the Sun Solaris Operating Environment, versions 10. The system requirements for the server are as follows: ● 1 GB RAM minimum, 2 GB recommended.
Overview NOTE Additional disk space may be needed to hold alarm logs and other runtime data. The amount of space depends on the number of devices and the number of traps and syslog messages generated by the managed devices. Allowing Clients Access to the Server from Behind a Firewall If the EPICenter server is located behind a firewall, you must allow EPICenter clients access through the firewall.
EPICenter Client Requirements Sun Solaris The system requirements for the EPICenter client under 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. ● A browser is required to log on to EPICenter, display reports, and view the EPICenter on-line Help.
Overview Modifying the Amount of Memory Available for Java Applets By default, Java applets can consume only up to 64MB of memory. This may not be enough to allow EPICenter to function effectively. Java applets without sufficient memory may start up and run very slowly, or may generate an Out of Memory error. You can increase the amount of memory available to applets through the Java Plug-in control Panel. The following instructions apply to JRE 1.6.0.
EPICenter 7.0 Device Support Table 2: ExtremeWare/ExtremeXOS versions supported by EPICenter 7.0 Extreme Switch Platform ExtremeWare Versions Supported ReachNXT ExtremeXOS 11.2 on the connected switch ExtremeXOS 12.2 on the connected switch required for ReachNXT firmware upgrade capability BlackDiamond 6800 6.2 or later BlackDiamond 8800 ExtremeXOS 11.1 or later ExtremeXOS 12.0 or later for 10G4Ca Module ExtremeXOS 12.
Overview Table 3: Extreme Networks devices supported by EPICenter 7.
EPICenter 7.0 Device Support Table 3: Extreme Networks devices supported by EPICenter 7.0 Switches/Modules BlackDiamond 10808 series/modules: G60T 10G6X G20X G60X 10G2H 10G2HR 10G2X BlackDiamond 12800C/12800R series/modules: MSM-5 GM-20XT MSM-5R XM-2XR GM-20T XM-2X GM-20XTR MSM-6R XFM-1 XM-8XB BlackDiamond 20808 series/modules: * MM Basic MM Advanced GM-40XB GM-40XA EPICenter 7.0 provides only limited support for the Summit24e2, SummitPx1, Summit WM 100/1000, and Summit WM 200/ 2000.
Overview NOTE Third-party device limitations also apply to the Extreme Summit24e2, the SummitPx1, the Summit WM 100/1000 and Summit WM 200/2000 devices, as well as the Sentriant AG and Sentriant NG devices. Table 5 provides a summary of EPICenter’s basic support for non-Extreme devices. Table 5: Third-Party Device Support by Feature EPICenter Feature Third-Party Device Support Inventory MIB-2 compatible devices: status only, SNMP v1 only.
Software Installation or Upgrade Overview NOTE A Base license is required to run EPICenter. Installing an Upgrade license (Silver or Gold) without a Base license does not provide access to the EPICenter Server. If you have purchased the product, you should have received an activation key, found on the License Agreement that accompanies your software package. This key starts with “AC,” and can be used to obtain a permanent license key. You do not need an activation key to obtain an evaluation license key.
Overview EPICenter Software Documentation The EPICenter software documentation set includes installation instructions, context-sensitive Online Help, two user guides, and this release note. The EPICenter Installation and Upgrade Guide contains documentation on how to install the EPICenter software, or upgrade from a previous version. This is available in PDF format on the EPICenter product CD, in the extreme.
2 Clarifications, Known Behaviors, and Resolved Issues This section describes known problems with the EPICenter 7.0 Service Pack 1 release, including recommendations for workarounds when available. It also lists problems that existed in previous versions of EPICenter 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 Configuring EPICenter to Generate Alarms for SNMP-Unreachable Devices at Each Poll Interval EPICenter periodically checks the SNMP reachability status of managed devices, using a default poll interval of 5 minutes. If a managed device is unreachable through SNMP, an alarm is generated in EPICenter (and e-mail notifications are sent, if this is part of the alarm definition).
Issues Resolved in the Service Pack 1 Release To configure this on the EPICenter server, do the following: 1 Using a text editor, open the management.properties file, which resides in /extreme.war on the EPICenter server. 2 Edit the following properties in the file: EPICENTER_ALTERNATE_IP_COUNT=1 (change to the number of IP addresses that EPICenter may use) EPICENTER_ALTERNATE_IP_1=136.159.39.1 (specify an ID for each alternate IP address) DEVICE_MAPPING_1=136.159.39.
Clarifications, Known Behaviors, and Resolved Issues 14 If a device had an IP address consisting of 15 characters, such as 192.168.191.146, and the device was managed on the vr-mgmt VLAN, uploading a configuration to the device failed. (PD4-455032021) 15 After acknowledging all of the software updates in the Display Software Images Updates window, the next time you logged into EPICenter, the EPICenter Home page still indicated that updates were available for software images on Extreme devices.
Issues Resolved in the Initial 7.0 Release 35 If you created an EPICenter script to save the primary and secondary configurations on a device, the configurations were saved successfully, but the script inserted an invalid character that generated an error message, which caused EPICenter to report that the script was unsuccessful. (PD4-664418801) 36 Resizing the Upload Configuration from Devices window caused the Device Group box in the window to display incorrectly.
Clarifications, Known Behaviors, and Resolved Issues 1 Timeout errors were encountered when attempting to synchronize a device. As a workaround, use the Modify Communications Settings window to refresh the SNMP credentials for the device. (PD4438985853) 2 When viewing information in the EAPS Domain Details window, clicking the Refresh active window icon did not refresh the screen. As a workaround, close the window and open it again.
Clarifications and Known Problems in Previous Releases 17 Copying a top-level group that includes a subgroup to another top-level group causes a Java runtime exception error. (PD4-697359803) 18 In the Link Details window, enabling the Show VLANs box did not display correct VLAN information. The VLAN information is displayed correctly in the VLAN tab.
Clarifications, Known Behaviors, and Resolved Issues Distributed Server Mode Cannot launch distributed server, incorrect password sent Distributed Server mode: when you attempt to launch a remote distributed server, the incorrect password is sent, so the auto login fails. (PD3-63873601) General—Client Auto-save is on by default when the EPICenter server starts up When the EPICenter server starts up it syncs all devices, and the auto-save feature is enabled by default.
Clarifications and Known Problems in Previous Releases TFTP port remains in use after EPICenter TFTP server disabled After disabling the EPICenter TFTP server, the TFTP port remains in use. Restart the system to clear it. (PD3-24495867) Clarification about how the EPICenter server works on a multi-homed device in version 7.0 compared with previous EPICenter versions A multi-homed device is one that has more than one network interface card (NIC) installed, and may be using multiple IP addresses.
Clarifications, Known Behaviors, and Resolved Issues Configuration Manager Downloading a config file to device fails if using SSH Downloading a configuration file to a device running ExtremeWare fails if EPICenter attempts to use SSH to the device. To successfully download a configuration through EPICenter, you must temporarily disable SSH for the device.
Clarifications and Known Problems in Previous Releases Download to BD8810 or BD10808 may fail due to timeout Downloading an image or bootrom to a Black Diamond 8810 or 10808 sometimes fails due to timeout. If this is a repeated problem you can change the Upload/Download Timeout Period property in the EPICenter Administration under Server Properties, in the Devices Properties set. The default timeout is 60 seconds. 120 seconds (2 minutes) is recommended.
Clarifications, Known Behaviors, and Resolved Issues Adding SNMP v3 devices fails In some cases SNMP v3 devices may fail to be added to the database, and a “Time Synchronization failure could have occurred” error appears in the log. Restarting the EPICenter server will correct the problem.
Clarifications and Known Problems in Previous Releases 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 EPICenter 7.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 EPICenter complains about missing device when launched from AIM When EPICenter 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. (PD3-102012039) Attempting to launch EPICenter from the browser-based AIM Console fails If you launch the AIM console in a browser window, and then attempt to launch EPICenter, the EPICenter browser window never opens.
