Specifications

Important Information about Using EPICenter
EPICenter Release Note
7
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.0, the Client software is launched automatically when you point a browser to
the EPICenter Server and click the Log on to EPICenter link. There is no longer a separate
installation or upgrade procedure for the EPICenter Client software.
● Installation as Windows services or Solaris/Linux daemons only. In version 7.0, EPICenter can no
longer be installed as an application, but only as services in Windows or daemons in Solaris/Linux.
During the Windows installation process, you can select whether to run the EPICenter services
automatically at startup or start them manually.
● Features removed from the product. The following EPICenter 6.0 features do not exist in version 7.0.
Where noted below, the functionality provided by these features now appears elsewhere in the
product.
■ Browser-based client. To launch the EPICenter Client application, you point a browser to the
EPICenter Server and click the Log on to EPICenter link. The client application files are then
downloaded from the server, installed on the local machine, and the EPICenter Client application
is started. In EPICenter 7.0, there is no longer a version of the EPICenter Client that runs within a
browser.
■ VLAN Manager applet. In EPICenter 7.0 you can configure VLANs using the new VLAN
configuration script. VLAN topology information is now available using Map Views
■ VLAN Reports. Information displayed in VLAN reports is now available on the VLAN tab in
Network Views.
■ Grouping Applet. Device groups and port groups can now be configured using the new
hierarchical grouping feature.
Important Information about Using EPICenter
The following describes some important caveats about how EPICenter should be used within your
network.
The EPICenter RADIUS Server
EPICenter’s built-in RADIUS server should not be used to provide authentication services for your
network devices in a production environment. It should be used only for demonstration or testing
purposes. The built-in server is not sufficiently robust to be used in a production environment. For
RADIUS authentication, EPICenter can be configured to function as a client of an external RADIUS
authentication server.
The EPICenter TFTP Server
EPICenter’s built-in TFTP server is intended only for uploading and downloading switch configuration
files and software image files under EPICenter’s control. It is not intended for use as a general purpose
TFTP server.