WARNING: L01
EXAMPLE: Port doesn't match: 1 <> 0 
SEVERITY: low 
DESCRIPTION:
Usually this is usually script problem, basically it means in spas printouts for the certain board, siliport mentioned in SwitchInternalLink MO is not found.
IMPACT:
Unknown
HOW TO FIX:
Try to run script several times, if problem is still there - manual check is required.

WARNING: H01
EXAMPLE: Remote slot mismatch - MO: 010100  RO : 010200 
SEVERITY: high 
DESCRIPTION:
This means there is a mismatch between RgRo and MO regarding external SCB board. Can be checked only on MS side.
IMPACT:
PCN408. Might lead to loss of subrack. If target subrack is still visible, it's reliability issue: if something happens with other plane target subrack will be lost
HOW TO FIX:
Check cables connections. This problem is result of incorrect cable configuration. Basically ISL cable from SCB in MS is connected to SCB board in wrong subrack. 

WARNING: H02
EXAMPLE: Remote port mismatch - MO:0 RO:3 
SERVERITY: high  
IMPACT:
PCN408. Might lead to loss of subrack. If target subrack is still visible, it's reliability issue: if something happens with other plane target subrack will be lost 
DESCRIPTION:
This means on MS side, there is a mismatch between RgRo and MO regarding siliport2 - port on external SCB. Can be checked only on MS side.
HOW TO FIX:
Check cables connections. This problem is result of incorrect cable configuration. Basically ISL cable from SCB in MS is connected to SCB board in wrong subrack. If everything is right please refer to SCS1081221

WARNING: M01
EXAMPLE: RO port state is not consistent 
SEVERITY: medium  
IMPACT:
Unknown
DESCRIPTION
This means in RgRo on MS side, for certain port MaintStatOwn and MainStatOwnPhysLink  or MaintStatOther and MainStatOtherPhysLink  have different values
HOW TO FIX:
This warning might come with "Port is down" or "Active port is down" warnings, in that case deal with "Port is down" warnings first. If this is stand alone warning, please contact PLM for support

WARNING: H03
EXAMPLE: Another plane: 000000 is using different port: 1
SEVERITY: high
IMPACT:
PCN408. Cable connections on planes are different - not reference configuration or RgRo corruption. Might lead to loss of subrack. Reliability issue
DESCRIPTION:
This means plane A and B are using different ports to connect to ES. This usually is sign of typical RgRo misconfiguration. This is checked only on RgRo supervision board (state 4)
HOW TO FIX:
Check cables connections for both planes. If ISL cable connection is right, please refer to SCS1081221

WARNING: L02
EXAMPLE: Port for inactive RgRO is out of range, check active RgRo settings
SEVERITY: low
IMPACT:
Minor reliability issue
DESCRIPTION:
Inactive RgRo extention port is out of range (>4). It's not a big issue as long as active RgRo has all values right
HOW TO FIX:
No action is needed. Warm restart of affected board.

WARNING: H04
EXAMPLE: Active RgRo SCB has misconfiguration - another plane port is out of range
SEVERITY: high
IMPACT:
PCN408. Reliability issue. Might lead to loss of subrack
DESCRIPTION:
RgRo obvious misconfiguration is detected. Information about external port on other SCB is wrong
HOW TO FIX:
Please refer to SCS1081221

WARNING: H05
EXAMPLE: Active RgRo SCB has misconfiguration - another plane APN is out of range
SEVERITY: high
IMPACT:
PCN408. Reliability issue. Might lead to loss of subrack
DESCRIPTION:
RgRo obvious misconfiguration is detected. Information about external SCB is wrong
HOW TO FIX:
Please refer to SCS1081221


WARNING: M02
EXAMPLE: ISL link is down 
SEVERITY: medium  
IMPACT:
PC408. Might lead to loss of subrack. Reliability issue.  
DESCRIPTION:
SwitchInternalLink MO is disabled(OperationalStateTraffic). ISL link is not operational
HOW TO FIX:
Depends on other sympthoms. No exact fix procedure

WARNING: M03
EXAMPLE: Time sync over ISL is down 
SEVERITY: medium/low  
IMPACT:
PCN408(only if warning is related to SCB port). Time plane reliability(only if warning is related to SCB port)
DESCRIPTION:
SwitchInternalLink MO has disabled OperationalStateSync, which means that time syc. over this link to certain ES is not possible for some reason. If this warning is stated only for ISL link over SXB it's normal behaviour, nothing to be concern about
HOW TO FIX:
Depends on other sympthoms. No exact fix procedure. In case of SXB is normal behaviour

WARNING: H06
EXAMPLE: Port is down
SEVERITY: high/medium 
IMPACT:
PCN408. Might lead to loss of subrack. Reliability issue
DESCRIPTION:
SILIPORT1 on current plane in MS is disabled according to SPAS printouts. Usually this warning shows for passive plane port
HOW TO FIX:
Check cables connections. If ISL cable connection is right, please refer to SCS1081221. Might depend on other sympthoms


WARNING: H07
EXAMPLE: Active Port is down 
SEVERITY: high/medium
PCN408. Might lead to loss of subrack. c
DESCRIPTION
SILIPORT1 on current in MS is disabled according to SPAS printouts. Usually this warning shows for active plane port
HOW TO FIX:
Check cables connections. If ISL cable connection is right, please refer to SCS1081221. Might depend on other sympthoms


WARNING: L03
EXAMPLE: Ext Port doesn't match
SEVERITY: low
IMPACT:
Unknown
DESCRIPTION
This is usually script problem, basically it means in spas printouts for the certain board, siliport mentioned in SwitchInternalLink is not found. Manual check is required
HOW TO FIX:
Try to run script several times, if problem is still there - manual check is required.


WARNING: M04
EXAMPLE: Ext. RO port state is not consistent
SEVERITY: medium 
DESCRIPTION:
This means in RgRo on ES side, for certain port MaintStatOwn and MainStatOwnPhysLink  or MaintStatOther and MainStatOtherPhysLink  have different values
HOW TO FIX:
Please contact PLM for support



WARNING: H08
EXAMPLE: Ext Another plane 010000 is using different port: 1
SEVERITY: high
IMPACT:
PCN408. Cable connections on planes are different - not reference configuration or RgRo corruption. Might lead to loss of subrack. Reliability issue
DESCRIPTION:
This means plane A and B are using different ports to connect to MS. This usually is sign of typical RgRo misconfiguration. This is checked only on RgRo supervision board (state 4)
HOW TO FIX:
Check cables connections for both planes. If ISL cable connection is right, please refer to SCS1081221



WARNING: H09
EXAMPLE: 000100 port:1 - 2 counter(s) looks bad
SEVERITY: high
IMPACT:
PCN408. Traffic degradation. Reliability issue
DESCRIPTION:
One or several discards counters from spashwinfo printout for certain port has value more than 100. This usually means there is a possible problem with ISL cable or board
HOW TO FIX:
Consider ISL cable replacement. Contact PLM for support



WARNING: L04
EXAMPLE: Inactive RgRo doesn't have right info about other plane, picked 000100 
SEVERITY: low
IMPACT:
None
DESCRIPTION:
SCB board with inactive RgRo supervision has wrong information about other plane. This is not a real problem. Usually it happens when this board gets restarted, so when it come up it has no clue about RgRo configuration and completely relies on other plane. However if RgRo supervision plane will change it get refreshed.
HOW TO FIX:
In general case no actions is necessary. Warm restart of active RgRo board



WARNING: L05
EXAMPLE: Port mismatch inactive RgRO:0:MO:1 
SEVERITY: low 
IMPACT:
Minor reliability issue
DESCRIPTION:
SCB board with inactive RgRo supervision has wrong information about port in other plane. This is not a real problem. Usually it happens when this board gets restarted, so when it come up it has no clue about RgRo configuration and completely relies on other plane. However if RgRo supervision plane will change it get refreshed.
HOW TO FIX:
In general case no actions is necessary. Warm restart of active RgRo board



WARNING: H10
EXAMPLE: Plane lost maintenance cells, ... status:00001FFF 
SEVERITY: high  
IMPACT:
Node outage, Traffic disturbances, board outages, 
DESCRIPTION:
SCB board is reporting loosing maintenance cells in the subrack. This is critical issue, might cause unexpected board restarts and even node restart. SCB replacement should be considered
HOW TO FIX:
Please contact PLM. Consider SCB replacement



WARNING: H11
EXAMPLE: Board 000000 and 000100 see different board setup 0bffffa7 <> 0bfffff7
SEVERITY: high  
IMPACT:
Reliability, board outages
DESCRIPTION:
This basically means that one of SCB see more boards then another. This is critical issue, becuase in case of plane swithcover "missing" board might disappear.
HOW TO FIX:
Please contact PLM. Identify in spastopologyinfo missing slot, check slot connection, do power cycle of the slot



WARNING: H12
EXAMPLE: No active plane selected 
SEVERITY: impossible/high  
IMPACT:
Unknown
DESCRIPTION:
This should never happen
HOW TO FIX:
RUn script one more time, if warning is still there, contact PLM



WARNING: M05
EXAMPLE: Too many plane changes 
SEVERITY: medium  
IMPACT:
PCN408, Reliability issue, traffic degradation
DESCRIPTION:
It means there are lot of non-ordered plane changes in subrack. It might be due to congestion or time synch. problems.  This is dangerous but not critical condition
HOW TO FIX:
Depends on the root cause. Check TUB and clock references status, Check load level, Contact PLM



WARNING: L06
EXAMPLE: Plane is Lock 
SEVERITY: low  
IMPACT:
Reliability(minor)
DESCRIPTION:
SCB is locked
HOW TO FIX:
Depends on the reason of lock. Not a problem.



WARNING: H13
EXAMPLE: Plane is Disable
SEVERITY: high
IMPACT:
PCN408, Reliability issue, Might lead to loss of subrack
DESCRIPTION:
SCB is mulfunctioning and considered as disabled
HOW TO FIX:
Depends on condition. Consider SCB replacement



WARNING: M06
EXAMPLE: Plane is not reliable 
SEVERITY: medium
IMPACT:
PCN408. Reliability issue, Might cause unexpected board restarts during plane switchover or SCB board crashes
DESCRIPTION:
SCB is not aware about status of other plane, which might cause big problems if it goes down. This is dangerous but not critical condition. If SCB is locked, it's normal behaviour
HOW TO FIX:
It's not a problem if you see this just after SCB board restart or node restart. Mkae sure that warning is there for more then 20 minutes. Warm restart another SCB


WARNING: M07
EXAMPLE: Plane is not ok
SEVERITY: medium/high   
IMPACT:
PCN408. Clock plane reliability issue, traffic disturbances
DESCRIPTION:
SCB consider it's plane as not ok. It usually due to clock synch. on the plane in bad shape.
HOW TO FIX:
Depends on condition. Please contact PLM



WARNING: M08
EXAMPLE: Another plane is not ok
SEVERITY: medium/high   
IMPACT:
PCN408. Clock plane reliability issue, traffic disturbances
DESCRIPTION:
SCB consider remote plane as not ok. It usually due to clock synch. on the plane in bad shape. In case of both warnings it's critical issue, there is no clock synch
HOW TO FIX:
Depends on condition. Please contact PLM



WARNING: M10
EXAMPLE: Plane status is not OK, ... status: 00F3542A
SEVERITY: medium/high
IMPACT:
PCN408. Clock plane reliability issue, traffic disturbances
DESCRIPTION:
Related to previous warnings, shows error status of the plane. In case of this warning, SCB replacement should be considered.
HOW TO FIX:
SCB replacement should be considered



WARNING: H14
EXAMPLE: Remote plane 000100 is unavailable
SEVERITY: high
IMPACT:
PCN408. Reliability issue, Might lead to loss of subrack
DESCRIPTION: 
Another SCB in the same subrack is not accessible
HOW TO FIX:
Depends on conditions. Power cycle of SCB. Consider SCB replacement



WARNING: H15
EXAMPLE: Remote plane 000000 has different opinion about active plane
SEVERITY: high
IMPACT:
PCN408. Reliability issue, Might lead to loss of subrack
DESCRIPTION: 
There is serious misunderstanding between both SCB's in subrack about who is active and who is not
HOW TO FIX:
Depends on conditions. Any action with SCB might cause loss of subrack or node. Lock one of SCB's. Contact PLM



WARNING: M11
EXAMPLE: Board: 000000 - Running on internal clock 
SEVERITY: medium/high
IMPACT:
Traffic degradation
DESCRIPTION:
This means board couldn't select any clock synch. planes which might be dangerous depending on board role. If there are a lot of this warnings it means there is a big issue with clock synch. in the subrack or node
HOW TO FIX:
If it's a single warning - Board restart. Otherwise check TUB and clock references. Contact PLM



WARNING: M12
EXAMPLE: Board: 000200 - On clock plane ... has too many 800 errors occured
SEVERITY: medium
IMPACT:
Traffic disturbances, unexpected board restarts
DESCRIPTION:
Reports about high amount of clock synch. errors on the plane
HOW TO FIX:
Depends on condition. Please contact PLM



WARNING: M13
EXAMPLE: Board: 000200 - Experienced too many 1170 clock plane changes 
SEVERITY: medium
IMPACT:
Traffic disturbances, unexpected board restarts
DESCRIPTION:
Reports about high number of clock plane switches,  usually results in crashes and traffic disturbances
HOW TO FIX:
Depends on condition. Please contact PLM



WARNING: M14
EXAMPLE: Board 000200 - Selected internal clock more often 112 times then plane A and B all together
SEVERITY: medium
IMPACT:
Traffic disturbances, unexpected board restarts
DESCRIPTION:
Report about big issues with selecting clock plane on this certain board
HOW TO FIX:
Depends on condition. Please contact PLM


WARNING: M15
EXAMPLE: 000000 port:0 - 2 counter(s) looks bad
SEVERITY: medium
IMPACT:
Traffic disturbances, unexpected board restarts
DESCRIPTION:
Internal error counters on certain SCB port(SILI PORT) have too high value. This warning is applicable only for RNC3810
HOW TO FIX:
Check for overloads. Consider ISL cable replacement.


WARNING: H16
EXAMPLE: Link is locked according to LEDs, but not according to MO
SEVERITY: high/medium
IMPACT:
PCN408, ISL link is down, Reliability issue
DESCRIPTION:
Link seems to be not operational and locked according to LED's on both sides, but from MO perspective it's not locked.
HOW TO FIX:
Check ISL cable, Try to lock ISL link and unlock it. If that doesn't help contact PLM

WARNING: M16
EXAMPLE: No connection
SEVERITY: medium
IMPACT:
PCN408, ISL link is down, Reliability issue
DESCRIPTION:
According to LED indication, there is no cable connected to configured port on both sides
HOW TO FIX:
Check ISL cable, Connect ISL cable

WARNING: H17
EXAMPLE: Wrong cable connection
SEVERITY: high
IMPACT:
PCN408, ISL link is down, Reliability issue
DESCRIPTION:
According to LED indication, there is no cable connection to configured port on one side and there is inactive connection on other. This usually means cable is connected by mistake to a wrong port or there is RgRo misconfiguration
HOW TO FIX:
Check ISL cable connection. If everything is right please follow SCS1081221


WARNING: ER
EXAMPLE: Unable to find remote plane 00000 script error !; Script failed to parse RgRo configuration for this port 2; Script failed to parse RgRo configuration for another board
SEVERITY: N/A
IMPACT: N/A
DESCRIPTION:
Script has failed to parse log files. This might happen from time to time during new releases when coli command output syntax has changed
HOW TO FIX:
Run once again. If problem is still there please send log files to CPP PLM.

