Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

PSM Alarms

 

The following table lists the alarms that are raised by PSM.

Note

You can modify the severity of a PSM alarm. See the proNX Service Manager Installation and Administration Guide for details. Modifying the severity of an alarm only affects new alarms raised after the modification takes effect. Existing alarms continue to show the unmodified severity.

Table 1: PSM Alarms

Alarm

Description

Example

Client cores

This alarm indicates that the number of processors available on the machine running the PSM Client is less than the recommended minimum. The PSM Client compares the number of available processors on the client machine with the “client.minimumCores” value configured in common.properties.

Client cores available (1) lower than minimum (2).

Client RAM

This alarm indicates that the amount of RAM available on the machine running the PSM Client is less than the recommended minimum. The PSM Client compares the amount of RAM on the client machine with the “client.minimumRAMSizeMb” value configured in common.properties.

Client RAM available (2048MB) lower than minimum (4000MB).

Client - server latency

This alarm indicates that the client/server latency is more than the recommended maximum. The PSM Client compares the last measured latency time between the client and server with the “client.maximumLatencyMs” value configured in common.properties.

Client -> Server latency (850ms) higher than maximum (700ms).

Server cores

This alarm indicates that the number of processors available on the machine running the PSM server is less than the recommended minimum. The PSM server compares the number of processors on the server machine with the “widecastOS.minimumCores” value configured in common.properties.

Cores available (6) lower than minimum (8).

Server RAM

This alarm indicates that the amount of RAM available on the machine running the PSM server is less than the recommended minimum. The PSM server compares the amount of RAM on the server machine with the “widecastOS.minimumRAMSizeMb” value configured in common.properties.

RAM available (3964MB) lower than minimum (8000MB).

Server hard disk

This alarm indicates that the amount of free Hard Disk space available on the machine running the PSM server is less than the recommended minimum. The PSM server compares the amount of HDD space on the server machine with the “widecastOS.minimiumDiskSizeMb” value configured in common.properties.

HD available (24568MB) lower than minimum (150000MB).

Unreachable network element

This alarm is raised when an attempt to discover a device fails. The device will be pinged periodically to test whether it has become reachable again. If the device becomes reachable then the alarm is cleared.

Network element 10.10.10.10 is unreachable.

Notifications stopped

Connectivity to the indicated network element for receiving notifications has gone down and cannot be re-established. The NE is placed into an AUTO out-of-service mode.

If this occurs, fix the underlying problem and rediscover the network element with the correct credentials.

Notifications stopped for 10.53.4.32 on stream StatusChange

Invalid FTP server configured

This alarm is raised when the server fails to retrieve the FTP server configuration information based on the ID it is supplied from the request to perform an NE DB Backup task.

NE Database backup on PSM Server has invalid FTP server configured: 10.10.10.10:21:ftpuser

Invalid Remote ID

This alarm is raised when the server encounters an incorrectly-formatted Remote ID during topology discovery.

Invalid Remote ID format found [PVX-1-5-G2] PSM NE Invalid Remote ID

Remote ID mismatch

This alarm is raised when the server detects a Remote ID mismatch where the two endpoints are not referring to each other in bookended configurations. One alarm is raised at each endpoint.

This alarm is also raised in single-ended configurations where the frequency/wavelength associated with the multiplexer/demultiplexer channel port does not match the frequency/wavelength at the other end.

Remote ID mismatch found [PVX-1-5-G2] PSM NE Farend Mismatch

NE Link mismatch

This alarm is raised when the server detects a mismatch in topology between the LLDP data and the Remote ID configuration. The server ignores the Remote ID and shows the LLDP topology.

 

NE DB backup failure

This alarm is raised when an NE DB backup process fails (either scheduled or started manually). The cause of the alarm can be attributed with any number of PSM server or NE issues, e.g. the NE DB backup process might have exceeded the maximum time allowed (300s), communication to the NE was interrupted, or the NE is unreachable. This alarm must be cleared manually.

NE DB Backup Failure. [Timed out after 300000ms waiting for 7000’s trap.]. Last failure at Tue Aug 14 04:25:23 BST 2012.

NE DB Backup Failure. NE is unreachable. Last failure at Tue Aug 14 04:15:11 BST 2012.

NE DB restore failure

This alarm is raised when an NE DB restore process fails. The cause of the alarm can be attributed with any number of PSM server or NE issues, e.g. the NE DB restore process might have exceeded the maximum time allowed (300s), communication to the NE was interrupted, or the NE is unreachable. This alarm must be cleared manually.

NE DB Restore Failure. [Timed out after 300000ms waiting for 7000’s trap.]. Last failure at Tue Aug 14 04:25:23 BST 2012.

NE DB Restore Failure. NE is unreachable. Last failure at Tue Aug 14 04:15:11 BST 2012.

NE log collection failure

This alarm is raised when an NE Log Collection process fails. The cause of the alarm can be attributed with any number of PSM server or NE issues, e.g. the NE Log Collection process might have exceeded the maximum time allowed (500s), communication to the NE was interrupted, or the NE is unreachable. This alarm must be cleared manually.

Log Collection Failure. NE is unreachable. Last failure at Fri Jul 13 02:00:03 BST 2012.

NE software upgrade failure

This alarm is raised when an NE Software Upgrade process fails. The cause of the alarm can be attributed with any number of server or NE issues, e.g. the NE S/W Upgrade process times out, a failure of one of the upgrade steps on the NE or the NE is unreachable. This alarm must be cleared manually.

 

ERPS state change

This alarm is raised when an ERPS ring goes into protecting, pending, forced protecting, or manual protecting state. Although this alarm is raised by PSM, this alarm is also associated with the ERPS service. A change to protecting state is a major alarm, while a change to other states is a minor alarm.

ERPS Ring SUB_ERPS (SVLAN 4089) is in Protection State

ERPS Ring MAIN_RING (SVLAN 200) is in Pending State in Domain Ottawa

ERPS dynamic port

If GVRP has added ports dynamically to any ERPS rings in the network, these ports are removed from view when the ring is visualized. A minor alarm is raised indicating their presence.

ERPS Ring MAIN_RING (SVLAN 200) has Dynamically Added Ports

ERPS Ring MAIN_RING (SVLAN 200) has Dynamically Added Ports in Domain Ottawa

PSM cluster node connection lost

When running with server replication, this alarm is raised if a connection to a member of a server replication cluster is lost. The IP address of the remote member is identified in the alarm. This alarm is cleared once connection to the remote member is re-established.

PSM cluster node 10.53.4.32 connection lost

Replication processing against cluster node failed

When running with server replication, this alarm is raised if the server encounters problems while processing the replication message from another server in the cluster. The IP address of the remote member is identified in the alarm. This alarm can only be cleared manually.

Replication processing against cluster node 10.53.4.32 failed for GROUPS

Synchronization failed against cluster node

When running with server replication, this alarm is raised if the server fails to synchronize with another server in the cluster. The IP address of the remote member is identified in the alarm. This alarm is cleared when a successful synchronization with the remote member occurs. This alarm can also be cleared manually.

Synchronization failed against cluster node 10.53.4.32