Contents

1   AlarmDescription

The alarm is raised when the Geographical Network Redundancy (GeoRed) configuration is invalid.

Table 1    DBS, NR, Configuration Invalid Alarm Causes

Alarm Cause	Description	Fault Reason	Fault Location	Impact
Two preferred clusters	Both clusters are configured as preferred.	Both clusters are configured to be the preferred cluster, which is invalid.	Network Redundancy Configuration	Data is not synchronized with the peer cluster.
Mismatching peer cluster IDs	The configured cluster ID and used cluster ID of the peer cluster do not match.	The cluster ID used by the peer cluster when communicating does not match with the peer cluster ID in the configuration.

Table 2    Alarm Attributes

Attribute Name	Attribute Value/Interpretation
Major Type	193
Minor Type	918533
MO Class	DbsService
Source	DbsvDirector
Specific Problem	DBS, NR, Configuration Invalid
Event Type	QUALITYOFSERVICEALARM
Probable Cause	frequencyHoppingFailure (74)
Perceived Severity	MAJOR
Additional Information	Both clusters are configured as preferred, Peer cluster's configured cluster id and used cluster id do not match

2   Procedure

2.1   Handle Alarm DBS, NR, Configuration Invalid

Prerequisites

• No documents are required.
• No tools are required.
• Before starting this procedure, ensure that the following condition is met:
  • The alarm is raised.

Steps

1. Check the additionalInfo attribute of the alarm.
2. Select action according to the attribute text:
   • If Both clusters are configured as preferred, proceed with Section 2.2.
   • If Peer cluster's configured cluster id and used cluster id do not match, proceed with Section 2.3.

2.2   Handle Both Clusters Are Configured as Preferred

Steps

1. Decide which cluster is to remain preferred; choose only one.
2. Change the preferredCluster attribute of the NetsharedConfig class to false in the other clusters.
3. Is the alarm cleared?

   Yes: Job is completed.

   No: Consult the next level of maintenance support. Further actions are outside the scope of this Operating Instruction.

2.3   Handle Peer Cluster's Configured Cluster ID and Used Cluster ID Do Not Match

Steps

1. Make sure that the dbsNetsharedPeerClusterId attribute matches the cluster ID set in the peer cluster (DbsNetsharedClusterId) at installation time.

   Query the attributes with the following commands:

   • immlist dbsNetsharedPeerClusterId=1,dbsNetsharedConfigId=1
   • immlist dbsCfgAttr=DbsNetsharedClusterId,dbs=vDicosDBSvSite

   Note:  

   If the DbsNetsharedClusterId attribute is not defined, the default setting of 0 applies.

   
   
2. Is the alarm cleared?

   Yes: Job is completed.

   No: Consult the next level of maintenance support. Further actions are outside the scope of this Operating Instruction.