Contents
1 Introduction
This document is the Operating Instruction (OPI) for the alarm DBS, NR, Configuration Invalid.
Scope
This document covers the following topics:
Target Groups
This document is intended for personnel involved in alarm handling.
1.1 Related Information
Trademark information, typographic conventions, definition, and explanation of acronyms and terminology can be found in the following documents:
2 Alarm Description
The following is a list of the alarm attributes:
|
Attribute Name |
Attribute Value/Interpretation |
|---|---|
|
Major Type |
193 |
|
Minor Type |
918533 |
|
Specific Problem |
DBS, NR, Configuration Invalid |
|
Event Type |
SA_NTF_ALARM_QOS |
|
Additional Information |
Both clusters are configured as preferred, Peer cluster's configured cluster id and used cluster id do not match |
|
Perceived Severity |
MAJOR |
|
Source |
DbsvDirector |
|
Additional Text |
DBS, NR, Configuration Invalid |
The possible causes of the alarm are as follows:
- Both clusters are configured to be the preferred cluster, which is invalid.
- The cluster ID used by the peer cluster when communicating does not match with the peer cluster ID in the configuration.
The consequences of the alarm are as follows:
- Data will not be synchronized with the peer cluster.
3 Procedure
To clear the alarm, perform the following steps:
- Fix the configuration based on the additional information
in the alarm.
If both clusters are configured to be preferred, decide which cluster shall remain preferred (not more than one) and change the preferredCluster attribute of the NetsharedConfig class to false in the other cluster(s).
If there is a mismatch between the configured and received cluster IDs, make sure that the clusterId attribute in the PeerCluster class matches the cluster ID set in the peer cluster at installation time (in the IMM object with DN dbsCfgAttr=DbsNetsharedClusterId,dbs=vDicosDBSvSite).
- If the issue persists, contact the next level of maintenance support.