Specifications

Clarifications and Known Problems
Ridgeline Service Advisor Release Note 27
Multibyte-encoded characters display incorrectly in Ridgeline SA Client
If you create a device group that includes multibyte-encoded characters (such as Japanese characters) in
its name, the device group name may not display correctly in Ridgeline SA. The Ridgeline SA Client
does not support character sets that use multibyte encoding. (PD4-314415318)
Connection error when Ridgeline SA server and client are in different domains
When the Ridgeline SA server and client were in different domains, the client was unable to connect to
the server even though the server was reachable using its fully qualified domain name. As a
workaround, you can edit the
/etc/ridgeline20.profile file and change the
EPICENTER_SERVER_ADDRESS value to the IP address of the server. (PD4-992968741)
General—Server
TFTP port remains in use after Ridgeline SA TFTP server disabled
After disabling the Ridgeline SA TFTP server, the TFTP port remains in use. Restart the system to clear
it. (PD3-24495867)
Traps may be dropped if the trap rate becomes excessive
In order to be able to reliably handle trap storms from a single or multiple devices, Ridgeline SA limits
its trap processing to 20 traps every 28 seconds from an individual device, and a total of 275 traps every
55 seconds system-wide. Any traps that occur beyond these limits are discarded, but will be noted in
the
log.txt file. If a sufficiently long burst of traps occurs, some of them may be dropped.
Exceeding the first limit (>20 traps in 28 seconds for a single device) is rare. However, if you are
managing a large number of devices, it is possible to exceed the total (275) limit. (PD3-103525231)
Stopping the Ridgeline SA database prior to stopping the server
When stopping the Ridgeline SA 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)
Network Views
Incorrect display of load-shared links
Ridgeline SA 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)