Contents
1 AlarmDescription
The alarm is raised when one or more Persistent Object Types (POTs) configured to be shared between the clusters are unknown to the database.
|
Alarm Cause |
Description |
Fault Reason |
Fault Location |
Impact |
|---|---|---|---|---|
|
Unknown netshared POTs configured |
One or more POTs configured to be shared between clusters are unknown to the database. |
N/A |
Configuration |
The unknown POT is not synchronized with the peer cluster. Initial synchronization is not possible with a peer knowing these POTs. |
- Note:
- The alarm can appear as part of a software upgrade procedure, as the POTs introduced by new software can temporarily be unknown to the database.
|
Attribute Name |
Attribute Value/Interpretation |
|---|---|
|
Major Type |
193 |
|
Minor Type |
918534 |
|
MO Class |
DbsService |
|
Source |
DbsvDirector |
|
Specific Problem |
DBS, NR, Unknown Object Type |
|
Event Type |
COMMUNICATIONSALARM |
|
Probable Cause |
frequencyHoppingFailure (74) |
|
Perceived Severity |
MAJOR |
|
Additional Information |
A list of the unknown POT RTIDs |
2 Procedure
2.1 Handle Alarm DBS, NR, Unknown Object Type
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
- Is the alarm raised during a software upgrade?
Yes: Wait until the software upgrade is finished. Continue with the next step.
No: Proceed with Step 3.
- Is the alarm cleared?
Yes: Proceed with Step 4.
No: Continue with the next step.
- Is the alarm raised after a
software upgrade?
Yes: Contact the provider of the upgraded software package because the upgraded configuration does not match the contained software.
No: Contact the next level of maintenance support. Further actions are outside the scope of this Operating Instruction.
- Job is completed.