Specifications

Clarifications, Known Behaviors, and Resolved Issues
EPICenter Release Note
22
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. (PD4-454434981)
16 Processing for Network Login related traps was not completed because the getHostIPs method was
not setting required parameters. (PD4-460896439)
17 Using the IP/MAC address finder (with the Source Type: Ports option set) to display MAC
addresses on an ExtremeXOS device did not yield any MAC addresses in the search results, even
though there actually were MAC entries on the ExtremeXOS device. (PD4-448959266)
18 Attempting to modify the Device Contact Password for a device running ExtremeXOS 12.1.2 failed.
(PD4-453346464)
19 When showing the link between ports on two devices, EPICenter may have incorrectly shown the
configured display string for the port on one side of the link as the display string configured for the
port on the other side of the link. (PD4-592970303)
20 The EPICenter Create VLAN script did not apply the QoS profile (if one was specified in the script)
when it configured the VLAN on the switch. (PD4-619711031)
21 Uploading a configuration to a device running ExtremeXOS 12.1 configured with SSH failed. (PD4-
582120259)
22 It took longer than expected to perform actions such as deleting devices from EPICenter inventory.
(PD3-210945861)
23 EPICenter did not display the ESRP State Change alarm for ExtremeXOS devices. (PD4-605886982)
24 In EPICenter Reports, a vertical bar (|) was displayed at the beginning of each group name. (PD4-
586389371)
25 EPICenter was not able to upload an ASCII text format configuration file to an ExtremeXOS switch
using SSH. (PD4-587682000)
26 After creating a baseline configuration for a device, if you then set up an archive schedule for the
device, and subsequently modified the device’s configuration, the scheduled archive failed due to a
stringindexoutofbounds exception in the server log. (PD4-564103851)
27 When the operational status of a port changed, EPICenter synced and updated all of the port
information in EPICenter displays, instead of just the port's operational status. (PD4-601852311)
28 When EPICenter encountered a high rate of SNMP traps, it did not display any information or create
an event log entry. (PD4-601852439)
29 When logged into a device using the EPICenter Telnet window, if you typed “logout” at the prompt
and pressed Enter, it did not gray-out the Telnet window, to indicate that the connection ended.
(PD4-596610867)
30 The “Modify VLAN – assign to EAPS domain” EPICenter script used an incorrect command when
adding a protected VLAN to an EAPS domain on an ExtremeWare switch. (PD4-619675761)
31 In previous releases, EPICenter was unable to forward events as SNMP traps to an external
management system. (PD4-602407090)
32 If you made changes to the Map View of a device group, then clicked the X on the device group's
tab to close it, EPICenter did not prompt you to save changes to the map. (PD4-600336601)
33 If an Admin user made changes to the Map View of a device group, then saved the changes, they
were not visible to other users when they refreshed the Map View. (PD4-600336622)
34 Errors were encountered in EPICenter when Version 6 update 12 of the Java plugin was installed.
(PD4-628697159)