Database failure

Database failure

Connectivity to the database has been lost.

Yes. Port By-pass is automatically enabled after multiple failed restarts.

Alarm

Critical

Either the database is down or connectivity to the database has been lost.

The database failure being cleared either automatically by the system or manually by the Security Administrator.

Yes. Required if automatic self-start is not successful.

Database Failure

Data Replication is broken

Database replication is broken between the HA SBC systems or the active-active EMS systems

No. But if the alarm does not get user attention and if ignored in the long run could lead to disk space issues and could cause the SBC to go down. Also, in case if the SBC displays the alarm ‘Database replication pg_xlog usage more than 1 GB then it needs immediate attention.

Alarm

Critical

Database Replication has stopped working between HA SBC’s or the active-active EMS and needs attention.

1. If this alarm pops up in the middle of upgrade / rollback, it is safe to ignore the alarm.

2. If this alarm pops up in a working system on 8.1 where both SBC’s or EMS’s are at the same version, the alarm is cleared after manual intervention is successful.

1. No

2. Yes

Database Failure

Peer SBC is Unreachable

The Peer HA SBC or EMS is down.

No. But in case if the SBC displays the alarm ‘Database replication pg_xlog usage more than 1GB’ then it needs immediate attention.

Alarm

Critical

If this alarm is seen on HA SBC, it means the peer SBC is not reachable. If this alarm shows up for EMS, it means the peer EMS is down.

Alarm gets cleared automatically once the peer SBC comes back online.

If the peer SBC was kept down intentionally, power on the SBC and make sure it comes back up again.

Manual intervention is also needed in case if the SBC has hard disk failure and is never going to come back again.