The local node has attempted to communicate with far-end node of a 1+1_OPTM protection group and has not received the expected change in K-bytes from the far-end node. Transient codes are only received while the local node is waiting for a response from the far-end node or is in the process of responding to K-byte changes from the far-end node, yet they are persisting.
|
Alarm Data |
Value/Meaning |
|---|---|
|
Severity Levels |
Critical (CR), Major (MJ), Minor (MN), Not Alarmed (NA), Not Reported (NR) Default: Major (MJ) |
|
ASAP Type |
1+1 Optimized Protection Group |
|
AID Type |
OC-N line (1+1 optimized protection group) |
|
Date |
Month/day/year that the condition was detected |
|
Time |
Hour:minute:second that the condition was detected |
|
Probable Cause |
APSUT (APS unresolved transient codes) |
|
Effect on Service |
NSA |
|
Alarm Entity Type |
OCN |
|
Description |
Automatic protection unresolved transient codes |
|
Likely Cause |
User selected Fault → Protection Switch and highlighted 1+1_OPTM Line Protection Group, and provisioned the Switch Type as Lockout. Or, the SYSCTL at the far-end network element is in the processing of resetting, therefore protection switching at the far-end is temporarily unavailable at the far end. |
|
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-10: Clear "Automatic protection switch unresolved transient codes" alarm. |
| November 2011 | Copyright © 2011 Alcatel-Lucent. All rights reserved. |