Specifications

Clarifications, Known Behaviors, and Resolved Issues
Ridgeline Service Advisor Release Note32
Avaya-Ridgeline SA Integration
NOTE
These items apply only to customers with the Avaya Integrated Management server version 3.1 co-resident with the
Ridgeline SA server.
Ridgeline SA complains about missing device when launched from AIM
When Ridgeline SA 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 Ridgeline SA from the browser-based AIM Console fails
If you launch the AIM console in a browser window, and then attempt to launch Ridgeline SA, the
Ridgeline SA 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 Ridgeline SA and AIM servers.
(PD3-102011941)
Profile Manager
Ridgeline SA 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, Ridgeline SA does not enforce this maximum number. Ridgeline SA 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 Ridgeline SA.
Scripting
Error when trying to save a Ridgeline SA script
After logging into the Ridgeline SA server using RADIUS authentication, if you created and saved a
Ridgeline SA script, then edited the script and attempted to save it again, Ridgeline SA displayed a
message indicating that the script could not be saved. As a workaround, you can select the Save As
option and overwrite the existing script. (PD4-984769971)