Specifications

Issues Resolved in the Service Pack 1 Release

EPICenter Release Note

To configure this on the EPICenter server, do the following:

1 Using a text editor, open the

management.properties file, which resides in

<EPICenter_install_dir>/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.* (specify the mapping between the ID and a device/network)

When the properties are configured as shown in the example above, whenever EPICenter performs a

configuration upload or download for devices in the 136.159.39.x network, the EPICenter server uses the

IP address 136.159.39.1. (PD3-123517597)

Other Resolved Issues

1 It was not possible to move a subgroup of a top-level group to the top level. (PD4-362787071)

2 After a profile configuration on a switch was changed, the Profile Manager displayed incorrect

information. (PD4-467401654)

3 After features were disabled in EPICenter Administration, those features were still visible when a

client logged into EPICenter. (PD4-530817079)

4 After migrating the EPICenter 6.0 database to version 7.0, the EPICenter TFTP root still pointed to

the EPICenter 6.0 location, causing files to be transferred there, rather than to the EPICenter 7.0

location. (PD4-531346711)

5 In the Configuration Manager, the Next Upload time was shown incorrectly when a global

configuration archive schedule is set: it is shown as None, instead of the actual next upload time.

(PD4-547591291)

6 In the Configuration Manager, the Baseline option in the Upload Configuration from Devices

window did not work properly. (PD4-547591305)

7 In Windows, when attempting to open EPICenter Reports by clicking the Reports folder under

Network Administration, it opened an empty browser window. After closing the Reports page,

clicking on the Reports folder again did not bring up the Reports page. (PD4-527819683)

8 In the Configuration Manager, when the “Use EPICenter login/password for Telnet/SSH” server

property was enabled, EPICenter used the login/password specified for the device in the “Add New

Device” window when contacting the device to perform a config archive operation, instead of the

EPICenter login/password. (PD3-75185751)

9 EPICenter was not able to compare differences in configurations between two switches. (PD3-

205211431)

10 Starting in this release, the output of the show management command entered on devices running

ExtremeXOS 12.2 or later now displays the source IP address for the EPICenter server entry in the

list of trap receivers. (PD3-205211520)

11 On a stacking device consisting of Summit X450 switches, EPICenter incorrectly displayed the

copper port of a combo port as active, when actually the fiber port was active. (PD4-404183231)

12 When attempting to upgrade the image on a switch, EPICenter incorrectly indicated that the new

image was incompatible with the version of BootROM installed on the switch. (PD4-429370451)

13 If you configured EPICenter to use a viewer other than the default viewer, and you attempted to

open a configuration file, EPICenter displayed a message indicating it could not find the file. (PD4-

437844231)