List of Generic Faults: LG F-H I T7 0 80 - R4 - 15 - 2 0 10 - W 7 Su R Pass Hit7 0 80 R4. 15.1

List of Generic Faults
LGF-hiT70 80-R4. 15 -20 10 -w 7

SURPASS
hiT70 80
R4. 15.1
© Nokia Siemens Networks Company Confidential 1 (21)

Table of Contents
1. Generic faults.................................................................................................................................. 3
1.1 Overview................................................................................................................................... 3
1.2 6GE+4FEGE/A..........................................................................................................................5
1.3 1 x 10 GE + 10 x GE/L2............................................................................................................ 7
1.4 LCAS recovery time.................................................................................................................. 8
1.5 Interworking...............................................................................................................................8
1.6 EOW........................................................................................................................................10
1.7 Transmission Protection..........................................................................................................11
1.8 Fault........................................................................................................................................ 12
1.9 LCT......................................................................................................................................... 12
1.10 GMPLS....................................................................................................................................13
Contact:
Contact your local Nokia Siemens Networks support
Summary of changes:
Date Version Reason for Changes Author

27-Nov-2008 1.0 Initial version for SURPASS hiT7080 R4.15 Daphne.Popescu,
Zhao Peng
7-Feb-2010 2.0 Initial version for SUPRASS hiT7080 R4.15.1 Pan Lizhou

PURPOSE
The List of Generic Faults is a summary of outstanding system faults containing the
problem description and the target correction schedule.
1. GENERIC FAULTS
1.1 Overview
Impact to Impact to
Problem-ID Description
Operator End User
In the 6 x GE + 4 x FEGE/A card, if traffic

consisting of similar packets is sent to LACP
7080 R4.15_4742 None Minor
FE WAN port, the LACP bandwidth could be
reduced
In the 6 x GE + 4 x FEGE/A card, when
multiple streams of traffic with the same
priority are sent from multiple ports to one port,
7080 R4.15_4759 None Minor
the egress packet ratio over a short period of
time for these streams is not as expected (e.g.
1:1:1).
In the 6 x GE + 4 x FEGE/A card, when there
is a case of broadcast traffic and heavy traffic
7080 R4.15_4753 None Minor
load there might be frames lost if flow control
is switched off
In the 6 x GE + 4 x FEGE/A card, traffic block
may occur when there is traffic congestion
7080 R4.15_4809 None Minor
between two LAN to LAN ports with flow
control enabled
Addition of multiple TPs will cause packets
loss in the case when there is WAN
7080 R4.15_5556 interworking between a 1 x 10 GE + 10 x None Minor
GE/L2 card and an 8 x GE/T card or an 6 x
GE + 4 x FEGE/A card
7080 R4.15_4751 In the case when overall MS-SPRing, MSP, and/or
7080 R4.15_4752 SNCP protection switch, the LCAS recovery time None Minor
7080 R4.15_4758 will be extended
MS-SPRing interworking issues between
7080 R4.15_4808 None Minor
SURPASS hiT 7070 and SURPASS hiT 7080
The MS-SPRing Squelch function cannot
7080 R4.15_4806 interwork with SURPASS hiT Minor None
7020/30/25/35/60/60HC in some slots

Impact to Impact to
Operator End User
7080 R4.15_4629
7080 R4.15_4630
7080 R4.15_4631
7080 R4.15_4632
7080 R4.15_4638
7080 R4.15_5973
7080 R4.15_6057
7080 R4.15_6058
On all data cards, LCAS interworking between
7080 R4.15_6059
SURPASS hiT 7080 and SURPASS hiT 7070 None Major
7080 R4.15_6059
cards is not released.
7080 R4.15_6060
7080 R4.15_6067
7080 R4.15_6084
7080 R4.15_4733
7080 R4.15_4734
7080 R4.15_4735
7080 R4.15_4736
7080 R4.15_4796
Whole EOW connection is blocked if there is

7080 R4.15_4785 Minor None
a fiber break on the 8 x STM-4/1 link
In the case where multiple MS-SPRings are
7080 R4.15_4807 configured on the same NE the switching time None Minor
may exceed 50 ms in certain cases
If the traffic is protected by both SNCP and
MSP/MS-SPRing, and the hold off time is not
7080 R4.15_4810 None Minor
configured to SNCP, these two protections
will switch simultaneously
LP-DEG is unexpectedly reported on the TP
7080 R4.15_5456 of the E1 port after receiving TU-AIS status Minor None
changes.
Two windows of the SURPASS hiT 7035 4.01
7080 R4.15_6470
extension shelf can not be accessed via the Minor None
7080 R4.15_6471
SURPASS hiT 7080 R4.15 element manager
7080 R4.15_3445 Protection Switch Events None None
7080 R4.15_5309
Forced Switch to Protection (FS-P) None None
7080 R4.15_5492
7080 R4.15_5418 TP Sharing Minor None
7080 R4.15_5659 Actual routed Hops None None
7080 R4.15_5745 LSP Information Minor None
7080 R4.15_5799 Path Constraints Minor None
7080 R4.15_5417
Relocation Minor None
7080 R4.15_6186

Impact to Impact to
Operator End User
7080 R4.15_7329
Crankback None Minor
7080 R4.15_7349
7080 R4.15_6165 Egress Node failures Minor None
7080 R4.15_5520 Minor Minor
Control Plane Failures
7080 R4.15_6334 Minor None
7080 R4.15_5675 Minor None
Double Failures
7080 R4.15_5903 None Minor
7080 R4.15_6019 Ethernet traffic switching time None Minor
7080 R4.15_7309 Reversion Time None Minor
1.2 6GE+4FEGE/A
1.2.1 In the 6 x GE + 4 x FEGE/A card, if the traffic consisting of similar packets is sent to LACP FE
WAN port, the LACP bandwidth could be reduced
Problem report: 7080 R4.15_4742
Resolve Ticket(s):
Severity: 2
If traffic is send to the LACP group (direction to FE WAN) the traffic will be distributed
among the LACP group according to the Hash algorithm. In the special case where
packets have the same distribution parameters (DA, SA …), all traffic will distribute into
one physical port of the LACP group. This will likely cause the physical port to overflow
This overflow will cause an LACP protocol interrupt of this physical WAN port and lead to a
reduction of bandwidth for this LACP group.
In real field application, the parameters for distributing the packets will be random. This
means the problem is very rare in any condition other than when using an analyzer for
generating the traffic.
Solution / Workaround:
N/A
Impact to Operator (Management Limitation)

N
Impact to End User (Traffic Limitation)

Minor
1.2.2 In the 6 x GE + 4 x FEGE/A card, when multiple streams of traffic with the same priority are
sent from multiple ports to one port, the egress packet ratio over a short period of time for these
streams is not as expected (e.g. 1:1:1).
Resolve Ticket(s):

Severity: 2
Description:
If there are different priority packets and “egress priority weight” is configured to WRR/SP,
the egress packet ratio of different priority packets is according to the configured weight.
If there are packets with the same priority coming from different ports with same speed and
packet length, the egress packet ratio of these streams is not regular, but the statistical
average over a long time will be correct (e.g. 1:1:1)
Configure the WRR/SP with “egress priority weight”.

N

Minor
1.2.3 In the 6 x GE + 4 x FEGE/A card, when there is a case of broadcast traffic and heavy traffic
load there might be frames lost if flow control is switched off.
Resolve Ticket(s):
Severity: 2
Description:
In the case where:
- 2 streams
- each with 100 Mbps traffic
- each with broadcast frames
- and HOL is enabled and Flow control is disabled
at the ingress port (1G LAN or 1 G WAN) frames might be lost.
Due to the fact that random sized frame traffic with bit rate < 100 Mbps can temporarily
reach 100 Mbps, the frame loss will start already with an average 90 Mbps traffic. This
depends on the distribution of the random sized frames in the streams.
1. Enable the broadcast rate limiting function at the ingress port
2. Disable the HOL and enable flow control when more than 1 stream is in the ingress
port.

N

Minor

1.2.4 In the 6 x GE + 4 x FEGE/A card, traffic block may occur when there is traffic congestion
between two LAN to LAN ports with flow control enabled.
Resolve Ticket(s):
Severity: 2
Description:
When one 6 x GE + 4 x FEGE/A card LAN port is connected to another 6 x GE + 4 x
FEGE/A (SURPASS hiT 7080) LAN port or 8xFE/L2 (SURPASS hiT 7025/35) LAN port,
traffic may be blocked when there is traffic congestion between two ports with flow control
enabled. The Layer 2 protocols (like MSTP, LACP, GVRP) will also be affected by this
block.
This issue only has the potential to occur when there is LAN interworking between:
- a 6 x GE + 4 x FEGE/A (SURPASS hiT 7080) LAN port and a 6 x GE + 4 x FEGE/A
(SURPASS hiT 7080) LAN port; or
- a 6 x GE + 4 x FEGE/A (SURPASS hiT 7080) LAN port and an 8 x FE/L2 (SURPASS hiT
7025/35) LAN port.
In normal field application, this kind of connection is rarely used.
The Flow control function must be disabled when LAN to LAN connection as described
above.

N
Impact to End user (Traffic Limitation)

Minor
1.3 1 x 10 GE + 10 x GE/L2
1.3.1 Addition of multiple TPs will cause packets loss in the case when there is WAN interworking
between a 1 x 10 GE + 10 x GE/L2 card and an 8 x GE/T card or an 6 x GE + 4 x FEGE/A card.
Resolve Ticket(s):
Severity: 2
Description:
This issue is caused by the packet buffer in the 8 x GE/T and 6 x GE + 4 x FEGE/A card.
When traffic is sent at full speed, and more TPs are added, this injects many packets into
the buffer in a short time, leading to a buffer overflow and temporary packet loss.
The problem only happens when adding multiple VC4 TPs and the total bandwidth after
adding is VC4-7v.
For traffic flow over 90%, do not add multiple VC-4 TPs to reach VC4-7v, and do it step by
step.

N

Minor
1.4 LCAS recovery time
1.4.1 In the case when overall MS-SPRing, MSP, and/or SNCP protection switch, the LCAS
recovery time will be extended.
Problem report: 7080 R4.15_4751, 7080 R4.15_4752, 7080 R4.15_4758
Resolve Ticket(s):
Severity: 2
Description:
The LCAS recovery time depends on the amount of VC-12 or VC-4 per VCG.
LCAS recovery time will be extended in the following cases:
Card TP Structure Hold Off Time LCAS Recovery Time

6 x GE + 4 x FEGE/A 46 x VC12 0ms 170~500 ms
50ms 160~500 ms
1 x 10 GE/T 64 x VC4 50ms 72~108 ms
N.A

N

Minor
1.5 Interworking
1.5.1 MS-SPRing interworking issues between SURPASS hiT 7070 and SURPASS hiT 7080.
Resolve Ticket(s):
Severity: 2
Description:
Card Type: 8 x STM-16, 2 x STM-64

MS-SPRing interworking between a SURPASS hiT 7070 and a SURPASS hiT 7080 has
the following issue:
In the case where
- there is an MS-SPRing interworking scenario where the SURPASS hiT 7070 is directly
connected to a SURPASS hiT 7080; and
- the East and West of this MS-SPRing are configured at the same SURPASS hiT 7080
card; and
- there are maintenance activities on this ring which might involve powering off of nodes;
the traffic in the ring will get lost and will be recovered after power on again.
Do not use LW (Line West) and LE (Line East) for an MS-SPRing on the same 7080 card
in the case where the neighboring node is a SURPASS hiT 7070.
This has to be considered for STM-16 and STM-64 MS-SPRing

None

Minor
1.5.2 The MS-SPRing Squelch function cannot interwork with SURPASS hiT
7020/30/25/35/60/60HC in some slots.
Resolve Ticket(s):
Severity: 2
Description:
Card Type: 8 x STM-4/1; 8 x STM-16, 2 x STM-64
The MS-SPRing Squelch function cannot interwork with a SURPASS hiT
7020/30/25/35/60/60HC if the slot number of the card located in hiT7080 is larger than the
maximum number of slots defined in the other products.
Products Maximum remote slot number

SURPASS hiT 7020 4
SURPASS hiT 7030 4
SURPASS hiT 7060HCR3.3 30
SURPASS hiT 7060R4.2 29
SURPASS hiT 7060R3.4 27
SURPASS hiT 7025 25
N/A

Minor

None

1.5.3 On all data cards, LCAS interworking between SURPASS hiT 7080 and SURPASS hiT 7070
cards is not released.
Problem report: 7080 R4.15_4629, 7080 R4.15_4630, 7080 R4.15_4631,7080

R4.15_4632, 7080 R4.15_4638, 7080 R4.15_5973, 7080 R4.15_6057, 7080 R4.15_6058,
7080 R4.15_6059, 7080 R4.15_6059, 7080 R4.15_6060, 7080 R4.15_6067, 7080
R4.15_6084, 7080 R4.15_4733, 7080 R4.15_4734,7080 R4.15_4735, 7080 R4.15_4736,
7080 R4.15_4796
Resolve Ticket(s):
Severity: 2
Description:
When using LCAS interworking between SURPASS hiT 7080 data cards and SURPASS
hiT 7070 data cards IF4FE4GE, IF7FE2GEL2, IF4FE4GEB, IF7FE2GEL2B frame loss
happens when the operator does adds or removes multiple TPs for a VC Group.
When there is a Cold Reboot of the SURPASS hiT 7080 data card, LCAS traffic will be
blocked.
LCAS interworking between SURPASS hiT 7080 and SURPASS hiT 7070 cards is not
officially released until the SURPASS hiT 7070 R3.4.1.
Interworking will be released in SURPASS hiT 7070R3.4.1

None

Major
1.6 EOW
1.6.1 Whole EOW connection is blocked if there is a fiber break on the 8 x STM-4/1 link
Resolve Ticket(s):
Severity: 2
Description:
When operator uses the RS E1 byte of the 8 x STM-4/1 to setup the EOW function, the
EOW function will be blocked if there is a fiber break on the 8 x STM-4/1 link. The EOW
connection will be re-established after the 8 x STM-4/1 link is recovered
The MS E2 byte will work in case of fiber break.

Minor

N

1.7 Transmission Protection
1.7.1 In the case where multiple MS-SPRings are configured on the same NE the switching time
may exceed 50 ms in certain cases
Resolve Ticket(s):
Severity: 2
Description:
Card Type: 8 x STM-4/1, 8xSTM-16
In this case, there are multiple MS-SPRings configured on the same NE, and the MS-
SPRing switches are requested at the same time (e.g. pull out CC card), the switching time
can sometimes exceed 50 ms.
When using 6 MS-SPRing groups on 4 nodes, the switch time is within 50 ms
This table contains the switch time for up to 6 MS-SPRing groups at one NE
Service Interruption time
Action
1 2 3 4 5 6
Remove card 36-37.6 33.8-40.2 xx 31.4-35 xx 33-37.7
Cold reboot card 36-37 xx 32-40.7 xx 33-40 xx
Power off node 29-38 20-32.5 28-37.5 xx xx xx
Cold reboot node 10-16 8.2-15 9.6-17.5` xx xx xx
When using 8 MS-SPRing groups on 4 nodes, the switch time will be longer than 50 ms when plugging
out the card.
This table contains the switch time for up to 6 MS-SPRing groups on one NE
Service Interruption time
Action
1 2 3 4 5 6
Pull out card 32-48, 86 43-44, 53 38-48 31.4-35 xx 36-48, 53.5
Cold reboot card 43.3-46.5 xx 22.5-51.2 xx 43.8-49.4 xx
Power off node xx xx xx xx xx xx
cold reboot node xx xx xx xx xx xx

None

Minor
1.7.2 If the traffic is protected by both SNCP and MSP/MS-SPRing, and the hold off time is not
configured to SNCP, these two protections will switch simultaneously.
Resolve Ticket(s):

Severity: 2
Description:
Card Type: 8 x STM-4/1, 8 x STM-16, 2 x STM-64
If the traffic is protected by both SNCP and MSP/MS-SPRing and the hold off time is not
configured to SNCP, these two protections will switch simultaneously.
Configure the Hold off time for SNCP, and configure the DEG threshold to no less than
10E-6.

None

Minor
1.8 Fault
1.8.1 LP-DEG is unexpectedly reported on the TP of the E1 port after receiving TU-AIS status
changes.
Resolve Ticket(s):
Severity: 2
Description:
LP DEG is reported incorrectly at the VC-12 termination on the E1 port when
- fiber plug/insert-
- insert/remove TU-AIS
A side effect is that LO SNCP switch is now caused by the DEG.
N/A

Minor

N
1.9 LCT
1.9.1 Two windows of the SURPASS hiT 7035 4.01 extension shelf can not be accessed via the
SURPASS hiT 7080 R4.15 element manager
Problem report: 7080 R4.15_6470, 7080 R4.15_6471
Resolve Ticket(s):
Severity: 2

Description:
The NE Property window does not display the cards, as expected.
The TP configuration window is empty and does not allow any configuration.
Connect to the SURPASS hiT 7035 extension shelf directly to access both windows and
configure the TPs there.

Minor

N
1.10 GMPLS
1.10.1 Protection Switch Events
Severity: 3
Description:
In case the protection class 1+1 PP is configured for a call there will be no SNCP switching
events reported into the call event list.
Check the NE event log for SNCP switching events.

None

None
1.10.2 Forced Switch to Protection (FS-P)
Severity: 2
Description:
Protection Class: Permanent 1+1 PP, revertive
If executing a Forced Switch to Protection (FS-P) command and then a Clear (CLR)
command the traffic remains on the protection path. The reason is that the SNCP for
GMPLS is always non-revertive even if the call is configured as revertive.

Execute Lockout of Protection (LP) before the Clear (CLR) command to revert to the
working path.

None

None
Severity: 3
Description:
Protection class: Restoration / Permanent Restoration
If executing a FS-P command, a new LSP is created. For permanent restoration three
LSPs exist (W-LSP, P-LSP, new P-LSP) and for Restoration the W-LSP is deleted
because the FS-P is treated as "failure on working".
The temporary third LSP is deleted when executing a LP or CLR command.

None

None
1.10.3 TP Sharing
Severity: 2
Description:
Protection Type: Preplanned Shared Restoration
TPs can be shared only for out-segments (i.e. in outgoing direction) of protection LSPs. In
a scenario where two LSPs are created in the opposite direction, TP sharing would require
that the out-segment of the second LSP can share resources with the in-segment of the
first LSP. This is not supported.
Thus, LSPs that are created in opposite directions cannot share common TPs and
therefore use more resources.
For pre-planned LSPs, create calls always in the same direction.

Minor

None
1.10.4 Actual routed Hops
Severity: 2
Description:
The label of the ingress (i.e. the timeslot information) is not recorded in the RSVP resv
message (RRO) that is stored as the actual routed hop (ARhop) list in the NE MIB. Thus,
the ingress label information is not displayed in the LCT ARhop list window at ingress (LSP
Details window).
Check the CC window for the cross connection at ingress.

None

None
1.10.5 LSP Information
Severity: 2
Description:
LSP tunnel information is only displayed at the ingress node of a LSP. Transit and egress
nodes just show cross connection and TP information for the LSP.
View the LSP tunnel information and actual routed hops at ingress node.

Minor

None
1.10.6 Path Constraints

Severity: 3
Description:
If the operator creates and activates a call then the calculated and routed hop list is saved
persistently. After an NE reboots, this same route is taken to re-establish the LSPs on this
same path. The effect is that this path is now visible as constraints in the Working /
Protecting Path set-up window and the Call Details window.
Manually delete the W/P path constraints if the operator wants to auto re-route the initial
LSPs (i.e. disable call administrative state, delete W/P hoplist, and enabled calls).

Minor

None
1.10.7 Relocation
Severity: 2
Description:
Protection class: 1+1 PP or Permanent 1+1 PP
Scenario: There is a failure on the working path and the traffic runs on the protecting path.
If the operator wants to relocate the failed working path, he has to execute a LP command
first which obviously leads to traffic loss.
To replace the failed working path and avoid traffic loss, execute a FS-P and change the
protection type to unprotected. Then, by setting the protection type back to the previous
protection class, a new protection LSP is created automatically along a route without
failures.

Minor

None
Severity: 2
Description:
Failed LSPs cannot be relocated.
If a call with a failed LSP needs to be relocated, then change the protection class of the
affected call to unprotected and then back to the previous protection scheme.

Minor

None
1.10.8 Crankback
Problem reports: 7080 R4.15_7329, 7080 R4.15_7349
Severity: 2
Description:
If multiple DSR calls are simultaneously affected by a transport plane failure, the
restoration time of some calls might be increased by an unexpected crankback in the
cases where:
- the new LSPs of the DSR calls are routed over a bundled TE-link, which is a local link of
the ingress node
- at least one of the component links of the said TE-link does not have enough bandwidth
to take all LSPs.
None

None

Minor
1.10.9 Egress Node failures
Severity: 2
Description:
Protection Types: Permanent 1+1 + DSR, Preplanned Restoration + DSR, DSR
In DSR mode, if the current traffic is not on the initial working path and the egress node
goes down, then the traffic will not be automatically recovered after restart of egress.
Disable and Enable the call administrative state at the ingress after the egress node restart
has finished.

Minor

None
1.10.10 Control Plane Failures
Severity: 2
Description:
In case of a control plane (CP) failure of a node (e.g. SC card removal or reboot), other
nodes are not notified about the node failure. Adjacent TE-links are not removed from the
other node's TE-link routing database. Using these TE-links for LSP path creation results
in crankback and periodical path set-up re-attempts.
In case of a CP failure with long expected downtime, manually set the failed node's
adjacent TE-links to disabled (or delete them) to avoid that other ingress nodes are using
these adjacent TE-links for path computation.
It is highly recommended to use SC 1+1 to avoid control plane failures.

Minor

Minor
Severity: 2
Description:
By default, cross connection resources that could not be freed due to a control plane
failure (e.g. the SC card of a transit node is absent and calls are deleted/relocated at the
same time) are released automatically after 45 minutes. The refresh multiple value (RR) of
a TE-Link (default=60) should not be changed except during special scenarios such as
MIB download to force faster freeing of resources. In cases where the control plane is not
responding (e.g. SC card failure in transit nodes) a change of this parameter has no effect.
Use SC 1+1 to protect against control plane failures

Minor

None

1.10.11 Double Failures
Severity: 2
Description:
In a double failure scenario where both ingress and egress were powered off and powered
on, the following behavior is observed:
Unprotected, 1+1 PP and DSR calls recover successfully, but Permanent 1+1 + DSR,
Restoration and Permanent Restoration + DSR calls' operational status is disabled, and
protected cross connections of Permanent 1+1 +DSR calls are deleted.
After ingress restart has completed, re-enable the affected calls manually.

Minor

None
Severity: 2
Description:
In a scenario where both working and protection paths are affected by a failure at the
same time the GMPLS control plane cannot recover in all cases. In RFC3945 it is stated
that "P&R mechanisms are in general designed to handle single failures". E.g. if working
and protection path (Permanent Restoration) go through the same transit node and this
node goes down, then the traffic will not be recovered automatically.
For Permanent 1+1 PP + DSR use node diversity or manually route the W/P LSPs so that
they are node diverse if it is likely that complete node failures can happen.

None

Minor
1.10.12 Ethernet traffic switching time
Severity: 2

Description:
Protection Class: Permanent 1+1 PP or 1+1 PP.
Due to LCAS/VCAT synchronization and recovery the 1+1 PP switching time for 1 GBit/s
Ethernet traffic is higher (300ms) than the SDH switching time (50ms) during alarm
scenarios.
When using manual switching (e.g. LP / FS-P) for GMPLS Ethernet bearer services the
Ethernet switching time is 500ms ~ 1300ms .
None.

None

Minor
1.10.13 Reversion Time
Severity: 2
Description:
To achieve the shortest possible switching time (traffic interruption time < 1ms) during
reversion from a protecting path back to the initial working path, the GMPLS controller
creates a temporary SNCP 1+1 at both ingress and egress to perform the switch. If a
failure occurs on the protection path during the WTR process then the traffic is switched
back immediately to the initial working path using the same procedure. However, due to
signaling the reversion time is > 1s.
Choose a short GMPLS WTR time to reduce the likelihood of a link failure during WTR.

None

Minor

Disclaimer
The information in this document is subject to change without notice and describes only the product
defined in the introduction of this documentation. This documentation is intended for the use of Nokia
Siemens Networks customers only for the purposes of the agreement under which the document is
submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means
without the prior written permission of Nokia Siemens Networks. The documentation has been
prepared to be used by professional and properly trained personnel, and the customer assumes full
responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the
process of continuous development and improvement of the documentation.
The information or statements given in this documentation concerning the suitability, capacity, or
performance of the mentioned hardware or software products are given “as is” and all liability arising
in connection with such hardware or software products shall be defined conclusively and finally in a
separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens
Networks has made all reasonable efforts to ensure that the instructions contained in the document
are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed
necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT
WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR
FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT,
INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF
PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT
MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights and other
intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of
Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective owners, and
they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2008. All rights reserved.

List of Generic Faults: LG F-H I T7 0 80 - R4 - 15 - 2 0 10 - W 7 Su R Pass Hit7 0 80 R4. 15.1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

List of Generic Faults: LG F-H I T7 0 80 - R4 - 15 - 2 0 10 - W 7 Su R Pass Hit7 0 80 R4. 15.1

Uploaded by

Copyright:

Available Formats

List of Generic Faults

LGF-hiT70 80-R4. 15 -20 10 -w 7

© Nokia Siemens Networks Company Confidential 1 (21)

Contact your local Nokia Siemens Networks support

Date Version Reason for Changes Author

© Nokia Siemens Networks Company Confidential 2 (21)

In the 6 x GE + 4 x FEGE/A card, if traffic

© Nokia Siemens Networks Company Confidential 3 (21)

Whole EOW connection is blocked if there is

© Nokia Siemens Networks Company Confidential 4 (21)

Problem report: 7080 R4.15_4742

Impact to Operator (Management Limitation)

Impact to End User (Traffic Limitation)

Problem report: 7080 R4.15_4759

© Nokia Siemens Networks Company Confidential 5 (21)

Impact to Operator (Management Limitation)

Impact to End User (Traffic Limitation)

Problem report: 7080 R4.15_4753

Impact to Operator (Management Limitation)

Impact to End User (Traffic Limitation)

© Nokia Siemens Networks Company Confidential 6 (21)

Problem report: 7080 R4.15_4809

Impact to Operator (Management Limitation)

Impact to End user (Traffic Limitation)

Problem report: 7080 R4.15_5556

© Nokia Siemens Networks Company Confidential 7 (21)

Impact to End user (Traffic Limitation)

1.4 LCAS recovery time

Problem report: 7080 R4.15_4751, 7080 R4.15_4752, 7080 R4.15_4758

Card TP Structure Hold Off Time LCAS Recovery Time

Impact to Operator (Management Limitation)

Impact to End user (Traffic Limitation)

Problem report: 7080 R4.15_4808

© Nokia Siemens Networks Company Confidential 8 (21)

Impact to Operator (Management Limitation)

Impact to End User (Traffic Limitation)

Problem report: 7080 R4.15_4806

Products Maximum remote slot number

Impact to Operator (Management Limitation)

Impact to End user (Traffic Limitation)

© Nokia Siemens Networks Company Confidential 9 (21)

Problem report: 7080 R4.15_4629, 7080 R4.15_4630, 7080 R4.15_4631,7080

Impact to Operator (Management Limitation)

Impact to End user (Traffic Limitation)

Problem report: 7080 R4.15_4785

Impact to Operator (Management Limitation)

Impact to End user (Traffic Limitation)

© Nokia Siemens Networks Company Confidential 10 (21)

Problem report: 7080 R4.15_4807

Impact to Operator (Management Limitation)

Impact to End User (Traffic Limitation)

Problem report: 7080 R4.15_4810

© Nokia Siemens Networks Company Confidential 11 (21)

Impact to Operator (Management Limitation)

Impact to End User (Traffic Limitation)

Problem report: 7080 R4.15_5456

Impact to Operator (Management Limitation)

Impact to End User (Traffic Limitation)

Problem report: 7080 R4.15_6470, 7080 R4.15_6471

© Nokia Siemens Networks Company Confidential 12 (21)

Impact to Operator (Management Limitation)

Impact to End User (Traffic Limitation)

1.10.1 Protection Switch Events