Operational NUT on the indicated cross-connection is inconsistent across all tributaries on the cross-connection. For example, in an STS-3c cross-connection, the three tributaries do not share a consistent protection behavior; Tributary 1 and 2 are PROT and Tributary 3 is NOTPR.
|
Alarm Data |
Value/Meaning |
|---|---|
|
Severity Levels |
Critical (CR), Major (MJ), Minor (MN), Not Alarmed (NA), Not Reported (NR) Default: Minor (MN) |
|
ASAP Type |
BLSR Protection Group |
|
AID Type |
STS-n Ring Channel |
|
Date |
Month/day/year that the condition was detected |
|
Time |
Hour:minute:second that the condition was detected |
|
Probable Cause |
NUTINXCGRN (NUT inconsistent cross connect granularity) |
|
Effect on Service |
NSA |
|
Alarm Entity Type |
COM |
|
Description |
NUT Inconsistent XC Granularity |
|
Likely Cause |
Local NUT was provisioned at a remote node in the BLSR which results in inconsistent operational NUT on an existing cross-connection at the local node. |
|
Visible Indication |
Lighted CR, MJ, or MN LED on the SYSCTL faceplate (when the severity level is provisioned to Critical, Major, or Minor, respectively) |
|
Action |
Proceed to Procedure 5-105: Clear "NUT Inconsistent XC Granularity" alarm. |
| November 2011 | Copyright © 2011 Alcatel-Lucent. All rights reserved. |