Closed michbin closed 5 years ago
The following changes have to be made: XltsThresholdCrossAlarmType::granularityPeriod::partOfObjectKey = 2 ; writeAllowed=Create_only; avcn=No, isInvantiant=true XltsThresholdCrossAlarmType::xltsLevel::partOfObjectKey = 3 ; writeAllowed=Create_only; avcn=No, isInvantiant=true
Following stereotypes haven been set for the XltsThresholdCrossAlarmTyp::granularityPeriod attribute partOfObjectKey== 2 , writeAllowed==Create_only , avcn==No , isInvantiant==true
Following stereotypes haven been changed for the XltsThresholdCrossAlarmTyp::xltsLevel attribute partOfObjectKey==3 (has been 2 before)
The xlts-threshold-cross-alarm-list has a key consisting of the 2 attributes
The granularity period should be added to the key so that it consists of
Some network elements are able to handle 2 different power thresholds (e.g. Rx level 1+2). Such thresholds could be distinguished by the xlts-level attribute in the key. However, this would make changing the value a little bit awkward because you would have to delete the entry for the old value and then create a new entry for the new value. It would probably be better to amend the values for level-threshold-second-kind. This would allow removing xlts-level from the key.