Specifications
Clarifications, Known Behaviors, and Resolved Issues
EPICenter Release Note
24
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. (PD4-
438985853)
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. (PD4-
454351171)
3 When viewing an overlay display of a VLAN or EAPS domain on a topology map, clicking the
Refresh active window icon did not refresh the VLAN or EAPS information. As a workaround, select
the VLAN or EAPS domain in the Navigation Table again. (PD4-431245871)
4 In this release, it is not possible to create an identically named port group and device group at the
same level in the group hierarchy. (PD4-366149982)
5 If you deleted a group consisting of many subgroups, attempting to create a new group while the
deletion was in progress produced an error message. (PD4-422019493)
6 When stopping the EPICenter server, if you stop the database component prior to stopping the
server component, the Java process may still continue. Make sure that you stop the server
component prior to stopping the database component. (PD4-436834851)
7 EPICenter incorrectly displayed a single load-shared link consisting of three links as three separate
load-shared links. To work around this, update the two devices on either end of the load-shared link,
and then use the Clear inactive links function. This will show correct load sharing information.
(PD4-484009799)
8 When moving devices to a group consisting of a large number of devices (more than 200), EPICenter
produced an error message. (PD4-524358195)
9 When upgrading EPICenter 6.0 to version 7.0, if the 6.0 installation had device groups that included
| (vertical bar) or , (comma) characters in their names, EPICenter produced an error message. As a
workaround, prior to upgrading, rename your device groups in EPICenter 6.0 so they do not have |
or , characters in their names. (PD4-532855984)
10 When upgrading EPICenter 6.0 to version 7.0, if the 6.0 installation had a device group named All, it
produced errors in EPICenter 7.0. As a workaround, prior to upgrading, rename your EPICenter 6.0
device group named All to a different name. (PD4-532856282)
11 It was not possible to create a VLAN Network Name that had the same name as an existing device
or port group, nor was it possible to create a device or port group with the same name as an existing
VLAN Network Name. (PD4-487584301)
12 It was not possible to launch EPICenter Administration using a client logged on to EPICenter from a
Solaris workstation. (PD4-525184396)
13 In EPICenter Administration, Server Properties tab, Devices area, the “Save Changed Configuration
Only” setting is checked by default, while it was unchecked by default in EPICenter 6.0. Having this
setting enabled means that if there is a configuration archive schedule set, configuration files are
archived only if they are different from the previously archived configuration.
14 If you point a browser to a URL on the EPICenter server machine, it brings up the Reports login
page. Entering a valid EPICenter username and password launches the EPICenter client application,
rather than the Reports page. (PD4-704465757)
15 Upgrading firmware using SSH did not work properly, although EPICenter reported that the
firmware upgrade was successful. The firmware image is downloaded to a file on the device, but it
is not actually installed. (PD4-726485828)
16 After a Schedule Baseline operation is completed, the information in the Configuration Manager
window does not get refreshed, even after clicking the Refresh button. As a workaround, you can
restart the EPICenter client application. (PD4-695935840)