Specifications

Clarifications, Known Behaviors, and Resolved Issues
EPICenter Release Note
32
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. This does not happen consistently, and is most likely to
happen when the browser client is running on the same system as the EPICenter and AIM servers.
(PD3-102011941)
Must restart the EPICenter server after changing the Trap Forwarding to AIM setting
When you change the state of the trap forwarding setting (Trap Forwarding to AIM enabled) in
EPICenter Administration (under Avaya Integration server properties) the new setting does not take
effect until you restart the EPICenter server. This is true for enabling or disabling trap forwarding.
(PD3-63926806)
Must restart the EPICenter server after changing Avaya trap port
If you change the Avaya trap port configuration through the Avaya Integration server Properties in
EPICenter Administration, you must restart the EPICenter server for it to take effect. (PD3-6717965)
The Reports feature does not launch properly after launching the Avaya Console
After launching the Avaya Integrated Management Console, the next time you try to launch the Reports
feature it does not launch correctly. To work around this, you can click the Reports button from the
client a second time. Setting the browser home page to about:blank will prevent this from happening.
(PD3-10228783)
Profile Manager
EPICenter does not enforce the maximum number of profiles
The Universal Port feature allows a maximum of 128 profiles on an Extreme device. However, in the
current release, EPICenter does not enforce this maximum number. EPICenter allows you to deploy
more than 128 profiles to a switch, but the configuration fails. (PD3-133538459)
Profiles bound to USER-REQUEST events are executed at the time of deployment
If you bind a profile to a USER-REQUEST event, the profile is executed at the time of deployment, even
if the profile is disabled in EPICenter.