Ethernet Port Fault

OPERATING INSTRUCTIONS

11/1543-CRX 901 140/1 Uen D

Copyright

© Ericsson AB 2013, 2016. All rights reserved. No part of this document may be
reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use
of this document.

11/1543-CRX 901 140/1 Uen D | 2016-12-14

 Contents

Contents

1 Overview 1
1.1 Description 1
1.2 Prerequisites 2

2 Procedure 3
2.1 Analyze the Alarm 3
2.2 Link Down 3
2.3 Auto-negotiation Failed to Meet Minimum Requirements 5
2.4 SFP Module Mismatch 5
2.5 No SFP Module Installed 6
2.6 Unavailable 6

11/1543-CRX 901 140/1 Uen D | 2016-12-14

Ethernet Port Fault

11/1543-CRX 901 140/1 Uen D | 2016-12-14

 Overview

1 Overview

This instruction concerns alarm handling.

1.1 Description
This is a primary alarm, which is raised by the EthernetPort MO.

The alarm is raised if the Ethernet Switch detects a ‘‘port fault’’ condition. The
alarm remains as long as the port is faulty. Normally, the fault must be attended
to on site. The port fault condition can only be detected if the port configuration
is completed so the port is enabled and ready to handle traffic.

The possible alarm causes and fault locations are explained in Table 1. The
alarm causes are stated in the additionalText.

Table 1 Alarm Causes

Alarm Description Fault Reason Fault Location Impact
Cause
Link Down The traffic on the link is Restart of Board, Ethern Disruption of
disturbed. a switch et network, or Ethernet traffic
board, cable configuration. on the affected
fault, network link.
fault, or
configuration
fault.
Auto-negotia The traffic is switched Auto-nego Ethernet Ethernet traffic is
tion Failed at a lower condition tiation has network. slowed down on
to Meet (speed, duplex or both) failed to meet the affected link.
Minimum than configured. the minimum
Requireme configured
nts requirements.
SFP Module The SFP module is not The SFP SFP module on Unable to switch
Mismatch supported. module does the board. Ethernet traffic on
not meet all the affected link.
the initial
conditions.

11/1543-CRX 901 140/1 Uen D | 2016-12-14 1

 Ethernet Port Fault

Table 1 Alarm Causes

Alarm Description Fault Reason Fault Location Impact
Cause
No SFP The SFP module Missing Board. Unable to switch
Module is missing or is not or faulty Ethernet traffic on
Installed detected. hardware. the affected link.
Unavailable The port is not ready to A recent Board. Disruption of
handle traffic. configuration Ethernet traffic
change on the affected
requires a link.
board restart to
make the port
operational.

The alarm can be raised temporarily after a restart of the switch board. If so,
the alarm normally ceases within one minute.

1.2 Prerequisites
This section provides information on the documents, tools and conditions that
apply to the procedure.

1.2.1 Documents
Before starting this procedure, ensure that you have read the following
documents:

• System Safety Information

• Personal Health and Safety Information

1.2.2 Tools

Before starting this procedure, ensure that the following tool is available:

• Cleaning machine LTT 179 001/1

1.2.3 Conditions
Before starting this procedure, ensure that the following condition is met:

• You are trained to use the cleaning machine.

2 11/1543-CRX 901 140/1 Uen D | 2016-12-14

 Procedure

2 Procedure

2.1 Analyze the Alarm

Do the following:

1. Read the additionalText in the alarm notification.

2. Go to the section below that corresponds to the additionalText.

2.2 Link Down

There are traffic disturbances on the link.

Do the following:

1. If the alarm ceases within one minute, exit this procedure. If the alarm does
not cease, continue with the next step.

2. If the Ethernet port has a cable that is plugged in, follow that cable to its
remote end. Determine whether the remote port is in need of repair or
whether it is in maintenance mode, by examining any other alarms on the
remote port. If there are any such alarms, repair the remote port first. If
this alarm then ceases, exit this procedure. If the alarm does not cease,
continue with the next step.

3. If the Ethernet Port is not SFP, continue with the next step. If the
Ethernet Port is SFP and the attribute sfpPort is set to true,
examine the sfpType part of the attribute sfpInformation of the
EthernetPort MO. If the sfpType has the value GE_1000_BASE_T,
examine the autoNegotiation part of the attribute operatingMode of
theEthernetPort MO. If the autoNegotiation has the value true, set
it to false. If this alarm then ceases, exit this procedure. If the alarm does
not cease, continue with the next step.

4. If the Ethernet Port is not 1000BASE-T, continue with the next step. If the
Ethernet Port is 1000BASE-T, follow that cable to its remote end.

If the port is reserved by Synchronization MO and the remote system

is an EvoC node, the remote port must be reserved by SyncEthEgress
MO. If the remote system is not an EvoC node, the remote port must not
be configured as manual_SLAVE. More information about master-slave
configuration can be found in IEEE 802.3 Chapter 40.5.2.

If the port is reserved by SyncEthEgress MO and if the remote system is

an EvoC node, the remote port must be reserved by Synchronization
MO. If the remote system is not an EvoC node, the remote port must not
be configured as manual_MASTER. More information about master-slave
configuration can be found in IEEE 802.3 Chapter 40.5.2.

11/1543-CRX 901 140/1 Uen D | 2016-12-14 3

 Ethernet Port Fault

5. If configuration of the Ethernet port is not ready regarding routing, Ethernet

Switching or the link synchronization cannot be enabled. To finalize the
configuration, create EthernetBridgePort MO, InterfaceIpv4 MO,
VlanPort MO, Synchronization MO, or SyncEthEgress MO and let
that MO refer to the EthernetPort MO. If the Ethernet port is a member
of a link aggregation group, let the MO refer to the Lag MO.

6. If the Ethernet port is a member of a link aggregation group, verify that the
attribute availabilityStatus in the EthernetPort MO does not have
the value DEPENDENCY_FAILED on either end of the link.

7. If the Ethernet port is dependency failed, exit this procedure for this Ethernet
port and continue with another Ethernet port in this link aggregation group
that is not dependency failed. If the Ethernet port is not dependency failed,
continue with the next step.

8. Examine the attribute operatingMode in the EthernetPort MO. Compare

it to the values for the remote port. If the two ports are configured
in an incompatible way, change to a compatible configuration. Both
autoNegotiation and configuredSpeedDuplex must be considered.
If the port is an SFP module, verify that the configured speed is the same
as the speed that SFP module supports.

9. If the alarm ceases, exit this procedure. If the alarm does not cease,
continue with the next step.

10. If the port is associated with a SwitchPortStp MO, examine the event log
for the MO SwitchPortStp. If the event BPDU Guard Port Blocked
has been raised, continue with the next step. If this event has not been
raised, go to Step 15.

11. Examine the attribute edgePortMode in the MO SwitchPortStp. Change

the value of this attribute to be compatible with the remote host.

12. If the alarm ceases, exit this procedure. If the alarm does not cease,
continue with the next step.

13. Perform the action unblockEdgePort on the MO SwitchPortStp.

14. If the alarm ceases, exit this procedure. If the alarm does not cease,
continue with the next step.

15. Ensure that the cable to the remote host is connected correctly. If the
alarm ceases, exit this procedure. If the alarm does not cease, continue
with the next step.

16. If the port is optical, carefully pull the optical connector from the QSFP or
SFP+. Inspect and if necessary clean the optical fiber connector before
reconnecting it to the QSFP or SFP+.

4 11/1543-CRX 901 140/1 Uen D | 2016-12-14

 Procedure

Note: Cleaning the opto-connector in the transceiver carries the risk of

adding new contaminants and might also damage the transceiver.
Therefore, clean the transceiver only when necessary and prevent
dust from getting into the transceiver. Ensure that the cable ends
are clean. If necessary, clean the cable ends with the cleaning
machine LTT 179 001/1 by drawing them twice at a right-angle to
the cleaning cloth in the machine.

17. If the port was connected to a node-external port, consult the maintenance
center for the network. If the network problem is resolved and the alarm
ceases, exit this procedure. If the alarm does not cease, continue with
the next step.

18. Consult the next level of maintenance support. Further actions are outside
the scope of this procedure. There might be a hardware fault on the board.

2.3 Auto-negotiation Failed to Meet Minimum

Requirements
The auto-negotiated speed, duplex or both, are below the minimum configured
requirements. Consequently, the port is operating below the minimum
configured threshold. Both the Ethernet switch port and the remote host must
be able to operate at the minimum configured requirements. If not, the alarm
is raised.

Do the following:

1. Investigate the minimum configured requirements and the capability of

the network interfaces. If the hardware cannot meet the requirements,
consult the next level support and request permission to lower the minimum
requirements or to upgrade the hardware, possibly in the remote node. If
the alarm ceases, exit this procedure. If the alarm does not cease, continue
with next step.

2. If the port is electrical, replace the cable. If the alarm ceases, exit this
procedure. If the alarm does not cease, continue with the next step.

3. Consult the next level of maintenance support. Further actions are outside
the scope of this procedure. There might be a hardware fault on the board.

2.4 SFP Module Mismatch

The SFP module is not supported.

Do the following:

1. Examine the SFP module for any connection problems. Make sure that it
is securely inserted and that the Ethernet cable is correctly connected to
the board. If the alarm ceases, exit this procedure. If the alarm does not
cease, continue with the next step.

11/1543-CRX 901 140/1 Uen D | 2016-12-14 5

 Ethernet Port Fault

2. Replace the SFP module with an approved module, as specified in the Unit
Description for the board. If the alarm ceases, exit this procedure. If the
alarm does not cease, continue with the next step.

3. Consult the next level of maintenance support. Further actions are outside
the scope of this procedure. There might be a hardware fault on the board.

2.5 No SFP Module Installed

The SFP Module is missing, or is present but not detected.

Do the following:

1. If an SFP module is present, go to Section 2.4 on page 5. If not, continue

with the next step.

2. Insert an approved SFP module into the socket on the board. If the alarm
ceases, exit this procedure. If the alarm does not cease, continue with
the next step.

3. Consult the next level of maintenance support. Further actions are outside
the scope of this procedure. There might be a hardware fault on the board.

2.6 Unavailable
A configuration change of the port requires that the board is restarted. This is
because of that the board must work in a fundamentally different mode which
can only be configured when the board is started and the HW is initiated.

Do the following:

1. Lock the board, using the instruction Lock Board. The Lock type is Hard
lock. The alarm ceases during the time the board is locked but the fault is
not repaired yet.

2. Restart the faulty board, using the instruction Restart Board. The
RestartRank is RESTART_WARM and the RestartReason is
PLANNED_RECONFIGURATION. In the field, RestartInfo, write the name
of this alarm and the fault cause.

3. Unlock the board, using the instruction Unlock Board.

4. If the alarm reappears after the board is unlocked, lock, restart, and unlock
the board once more, as described above.

5. If the alarm reappears with new alarm cause, a new problem has been
identified. Start from the beginning Step 1 and follow the procedure for
the new alarm cause.

6. If the alarm with the fault cause Unavailable ceases, exit this procedure. If
the alarm does not cease, continue with the next step.

6 11/1543-CRX 901 140/1 Uen D | 2016-12-14

 Procedure

7. Consult the next level of maintenance support. Further actions are outside
the scope of this procedure. There might be a hardware fault on the board.

11/1543-CRX 901 140/1 Uen D | 2016-12-14 7