Troubleshooting Guide to Ethernet Data Boards.pdf

8/14/2019 Troubleshooting Guide to Ethernet Data Boards.pdf

1/57

Document code Product name

Target readers Product version

Edited by Document version

Troubleshooting Guide to Ethernet

Data Boards

Drafted by: Date:

Reviewed by: Date:

Reviewed by: Date:

Approved by: Date:

Huawei Technologies Co, LtdAll Rights Reserved


2/57


3/57

Troubleshooting Guide to Ethernet Data BoardsConfidentiality: For

Internal Use Only

2007-10-22 Huawei secrets, no dispersion without permission Page 3 of 57

Contents

Chapter 1 Overview.......................................................................................................................... 6

Chapter 2 Background Knowledge................................................................................................. 7 2.1 Ethernet Fundamentals ........................................................................................................ 7

2.1.1 CSMA/CD................................................................................................................... 7 2.1.2 Working Mode of the Port .......................................................................................... 7 2.1.3 Various Error Frames of Ethernet (Ethernet II) .......................................................... 8 2.1.4 Ethernet Flow Control ................................................................................................ 8 2.1.5 VLAN.......................................................................................................................... 9 2.1.6 Relationship Between Ethernet II and IEEE 802.3 Frames ....................................... 9 2.1.7 Type and Precautions to Deployment for the Current EFT/EGT Board................... 10

2.1.8 Identifying the Multicast Feature and Manufacturerer Information of a MAC Address10 2.1.9 Composition of a Data Communication System ...................................................... 10 2.1.10 Concepts, Settings and Setting Principles of MTU and MRU................................ 10 U2.1.11 VLAN ID Support of Data Boards........................................................................... 11 2.1.12 Differenting a Single-Module Optical Interface from a Multiple-Mode OpticalInterface on an SS42AIUA02............................................................................................ 11 2.1.13 Locating the Channel that Generated an ATM Alarm............................................ 12 2.1.14 Querying Ethernet Performance Events of an ET1 Board..................................... 12 2.1.15 Setting Switching Time and Hold-Off Time of a VP Ring in the Case MSP and VPRing Coexist ...................................................................................................................... 13 2.1.16 Querying the Actual Working Mode of the 61ET1.................................................. 13 2.1.17 Judging the Working Status of a Network Interface According to Its Indicators .... 14 2.1.18 Whether ETHLOS Alarm will Disappear After the Network Interface of the ET1

Board Loops Back ............................................................................................................. 14 2.1.19 Use of Standard/Manufacturerer Network Cables ................................................. 14 2.1.20 Precautions to Setting the Working Mode of Ports of an EFGS Board.................. 14 2.1.21 Query Command of Actual Working Mode of Ports of a Data Attribute Board...... 15 2.1.22 Encapsulation Protocol of Each Data Attribute Version......................................... 15 2.1.23 Unshared Condition Between ET1 Inserted in Metro 3000 IU12 Slot and PQ1Board Inserted in IUP........................................................................................................ 16 2.1.24 Explanations of EPL, EVPL, EPLn and EVPLn Services ...................................... 16 2.1.25 2 M Service Transition in 2 M Tributary Card of ET1 Board.................................. 17 2.1.26 2 M Service Transition Failure in 2 M Tributary Cards of EFGS Series of Boards 17 2.1.27 Meaning of PING Command Parameters .............................................................. 17 2.1.28 Meaning of RMON Ethernet Alarms ...................................................................... 17 2.1.29 Auto-Negotiation Function of 10 M/100 M Network Interface ................................ 18

2.1.30 Not Using Network Cables Whose Both Ends are One-to-One Correspondence toTransmit 100 M Service .................................................................................................... 18 2.1.31 Introduction to 10Base5, 10Base2 and 10Base-T Cables..................................... 18 2.1.32 Explanation of Auto-Negotiation Function of Gigabit Ethernet .............................. 19 2.1.33 Introduction to PSTN, ISDN, DDN, X.25 Network and Frame Relay Network ...... 19 2.1.34 Meaning and Principle of Flow Control .................................................................. 20 2.1.35 Meaning and Principle of LPT Function................................................................. 20 2.1.36 Two Main Functions of LCAS................................................................................. 21

2.2 Knowledge Concerning the Ethernet Feature Board.......................................................... 21 2.2.1 Encapsulation and Fragmentation ........................................................................... 21 2.2.2 Common Board Performance Indices...................................................................... 21 2.2.3 Performance Event (RMON).................................................................................... 22 2.2.4 SUBCARD_ABN Alarm............................................................................................ 23 2.2.5 Common Questions on FCS_ERR Alarm................................................................ 25


4/57


Internal Use Only


Chapter 3 Usage Description of Test Frame FunctionsFull Service Flow Test for the EFGSBoard ............................................................................................................................................... 27

3.1 Introductions to Functions................................................................................................... 27 3.2 Using the Test Frame ......................................................................................................... 27

3.2.1 GFP Management Test Frame ................................................................................ 27 3.2.2 Verification Procedure.............................................................................................. 28

3.3 Custom MAC Frame........................................................................................................... 29 3.3.1 Command Line Description...................................................................................... 29 3.3.2 Test Procedure......................................................................................................... 30 3.3.3 Precautions to the Test ............................................................................................ 30

Chapter 4 Fault Location ............................................................................................................... 30 4.1 Locating the Problems of Completely Interrupted Ethernet Links ...................................... 32

4.1.1 TAG Attribute (TAG/UNTAG) Setting of the Port Changed ..................................... 33 4.1.2 Faulty Working Mode of the Port.............................................................................. 34 4.1.3 Failed Network Cables or Fiber Optics .................................................................... 37 4.1.4 VC Channel Binding................................................................................................. 37

4.1.5 Default VLAN ID of the Port ..................................................................................... 38 4.1.6 Static Route Error or Loss on the Ethernet .............................................................. 39 4.1.7 NE Pointer Justification or Clock Degrade, Resulting in BIP-OVER and TU-LOPfrom Some Channels of ET1 and Service Interruption ..................................................... 40 4.1.8 Faulty Board Hardware ............................................................................................ 40 4.1.9 Service Interruption Caused by A Great Deal of Packet Loss (Refer to theProcessing of Packet Loss Fault)...................................................................................... 40

4.2 Locating the Problems of Persistent Packet Loss on the Ethernet Link............................. 40 4.2.1 Insufficient Configuration Bandwidth Caused by Large Traffic................................ 40 4.2.2 Sufficient Bandwidth but Large Service Bursts........................................................ 41 4.2.3 Packet Loss due to Non-response of the Remote Equipment to Flow Control inCase of Too Large Service Traffic .................................................................................... 41 4.2.4 MTU Set for the Board Less Than the Real Transmission Packet Length of theEquipment ......................................................................................................................... 41 4.2.5 Abnormal Working Status Caused by Unmatched Port Mode with the RemoteEquipment ......................................................................................................................... 42 4.2.6 Failed Network Cables or Fiber Optics .................................................................... 42 4.2.7 Large ET1 Performance Decrease and Packet Loss in Case that the EthernetService Packet Lengths of Two Directions Keep Too Large Difference for a Long Time or

All the Packet Lengths Are Short Bytes (64-128 Bytes) ................................................... 42 4.2.8 Faulty Board Hardware ............................................................................................ 42

4.3 Loopback Fault Location..................................................................................................... 42 4.3.1 ET1 Loopback .......................................................................................................... 43

4.4 Performance Query ............................................................................................................ 46 4.5 Small Tools ......................................................................................................................... 52

4.5.1 Ping Command......................................................................................................... 52 4.5.2 Arp Command.......................................................................................................... 52 4.5.3 sniffer Program......................................................................................................... 52

Chapter 5 Typical Case Analysis .................................................................................................. 52 5.1 Network Service Interruption .............................................................................................. 52 5.2 Serious Service Packet Discard ......................................................................................... 53 5.3 Poor Image of the Video on Demand Service .................................................................... 54 5.4 L2 Switching Version Service Abnormality ......................................................................... 55


5/57


Internal Use Only


Keywords:

ET1, EFGS, Ethernet, locate, fault, packet loss

Abstract:This document introduces the fault locating considerations and methods,operation procedures and command lines in case an Ethernet data board inoptical network is faulty, and it also targets at guiding engineers totroubleshooting.

Abbreviations:

None.

References

None.


6/57


Internal Use Only


Chapter 1

Troubleshooting Guide to Ethernet Data Boards

Overview

With the expansion of MSTP and wide application of MSTP products, problemsinvolved in these products and in interconnection between these products andother network equipment come to be exposed in the network. To accuratelylocate all problems, you need not only to master the SDH technology, but alsodeeply understand the data communication technology and the products, to

analyze and solve the problems in the perspective of the overall network.We expect you are familiar with the following contents, but the contents in thisdocument are not represented in the sequence of troubleshooting abided in theactual problem processing. Because there are multiple types of faults whosetroubleshooting methods are different, you will have a clear idea from thedocument, and conduct the comprehensive processing to faults by combiningthe relative commands and means in the process of actual troubleshooting. Forthe troubleshooting process, refer to the relative document.

Although most commands in this document are oriented to SS61ET1 boards,but they are also applicable to most ET1 series of data boards currently used.For the relative faults, refer to the relative troubleshooting, processing idea andprinciples described in this document.

In addition, the troubleshooting approaches of the new EFGS series of databoards are the same with the ET1 series. However, there are more approachesand convenient query commands, for example, through the GFP test frame,verify whether the basic configuration and service channel between VCTRUNKports (verify whether the corresponding cross connection, channel binding andGFP protocol parameter are consistent) are enabled. Most of the followingcommands concerned are oriented to ET1 series of boards. To query thecorresponding project and content of EFGS series of boards, only need toconduct the host command, not need to compare the status difference betweenthe board side and host side through PTP.

In addition, we expect you can think over the document except understanding it,

and combine it with the actual condition in your work to put forward thecommands and suggestions, to continuously perfect, revise this document toget correct contents, thus helping us to guide our work and improve thesatisfaction of the customer.

The document summarizes the relatively typical cases in several years andcombines with the basic acknowledge of Ethernet to analyze, to help engineersto deeply understand MSTP products for improving the maintenance skills.


7/57


Internal Use Only


Chapter 2

2.1

2.1.1

2.1.2

Background Knowledge

Ethernet Fundamentals

Appropriately understand the Ethernet knowledge to deeply understand theprinciples and implementation of MSTP series of products, thus broadening theideas of networking, service configuration and troubleshooting.

Ethernet is a kind of network technology, oriented to the nonconnecting andbest-effort delivery. From the application perspective of MSTP products, thefollowing key contents should be understood.

CSMA/CD

IEEE 802.3 defines the CSMA/CD (Carrier Sense Multiple Access with CollisionDetection). CSMA/CD is very similar to the talk between people (that is, listenfirst and then speak. If there are many people talking, one person is allowed tospeak at a time). The core implementation approach is to continuously monitorthe communication medium, and delay signals and then transmit again aftertheir collision, thus implementing the sharing of communication media andcommunication among many people.

From CSMA/CD principles, we know that CSMA/CD-based Ethernet is a kind ofhalf-duplex technology, which is implemented at the cost of signal collision andtransmission again. Therefore, in case the communication requirements of thenetwork reach a certain amount, the possibility of collision increases, and thecorresponding network overall efficiency decreases.

For the detailed introduction and calculation method of CSMA/CD efficiency,refer to LAN Technologies .

Working Mode of the Port

The development of Ethernet technology contains two aspects:

a. Increase of rate, from 10 Mbps 100 Mbps 1000 Mbps 10 Gbps.

If only the frame format of Ethernet keeps unchanged, the seamless bridgingcan be implemented between Ethernets with different rates, which is helpful toincrease the forwarding rate of switch and decrease the cost.

b. Development of half-duplex technology, from half-duplex to full-duplex.

Different from the half-duplex Ethernet, the full-duplex working principle istransmitting if any, without viewing the busy or idle status of communicationmedium and without detecting collision. The full duplex is implemented basedon the following aspects: 1. The port supports the full-duplex mode. 2. Thecommunication medium is shared exclusively (point-to-point communication).

The combination of rate and duplex mode can form multiple types of portworking modes. To simplify the networking configuration and solve the portinterconnection problem, the auto-negotiation technology invented: By

handshake (pulse negotiation signal) of both parties, both parties can work inthe highest level of mode supported by them. Now, the 10/100 M electrical


8/57


Internal Use Only


2.1.3

2.1.4

interface supports the rate and duplex mode negotiation, but the fiber Ethernetdoes not support this negotiation (only supports full-duplex). Theauto-negotiation of GE is used for negotiation of flow control parameters.

The following condition should be noted : The 10/100 M electrical interface Ais in auto-sensing working mode, but the peer end B is in fixed working mode. Acan judge the rate of B is 100 Mbps or 10 Mbps by its received clock signal, butB does not transmit or respond to the negotiation pulse signal, resulting in A failsto judge the duplex mode of B, therefore generally A can only work inhalf-duplex mode. If B is in half-duplex, the service is normal. If B is infull-duplex, then its full duplex VS As half-duplex. At the same time, if both endsare in transmitting status, there must be collision on the communication medium,resulting in packet loss (in full-duplex, collision is not detected and the collisionalframe is not transmitted again). In case the communication data traffic increases,the possibility of collision increases, resulting in serious packet loss. Therefore,in case the port is set as auto-negotiation, the actual working mode of the portshould be queried after linking, to avoid the condition of half-duplex VSfull-duplex.

Various Error Frames of Ethernet (Ethernet II)

The following are common error frames of Ethernet:

1. CRC error

The end part of Ethernet frame is a 4-byte frame check sequence field, andthrough CRC (Cyclic Redundancy Check) the receiving end can check whetherframe incurs error (bit error) during transmission. Discard all the error frameschecked by CRC.

2. Extra-short frame

The frames less than 64 bytes, which are deemed as residues caused bycollision, and they must be discarded.

3. Extra-long frame

The frames exceeding the maximum value permitted by field length, which allshould be discarded. By default, the maximum frame size of ports of the MSTPseries of products is 1522 bytes (which can be set).

If the full-duplex VS half-duplex, the port receives the incomplete frames causedby a large amount of collision. The residues less than 64 bytes are deemed asextra-short frames, and should be discarded directly. Otherwise, conduct CRCcheck for the residues not less than 64 bytes, and the residues are deemed asCRC error frames caused by frame check sequence field error, and also shouldbe discarded.

4. Alignment

Byte alignment error, which seldom appears. Generally such error is caused byhardware fault or collision.

Ethernet Flow Control

In case the data processing/forwarding traffic of the equipment is less than the

traffic its port received, the congestion incurs. To pare down packet loss causedby buffer overflow, conduct the appropriate flow control.


9/57


Internal Use Only


2.1.5

2.1.6

For the CSMA/CD-based half-duplex Ethernet, the following two methods canbe adopted to implement flow control:

1. Forcibly conflict with the frame to arrive.

2. Forcibly set the channel in busy status.

Now, the half-duplex Ethernet does not play an import role, but the explicit flowcontrol of full-duplex Ethernet is implemented in various equipment: When thecongestion happens, the port transmits the specific flow control frame (PAUSEframe) to the peer end, which stops data transmission for a while upon receivingof flow control frame, to release the congestion load at the port.

PAUSE frame is a standard Ethernet frame, whose type of domain has value0x8808, and whose payload has the main content of slot time (indicating aperiod during which the peer end pauses the data transmission. If slot time is 0,it indicates the peer end can immediately resume the data transmission).

Huaweis MSTP series of Ethernet boards support to transmit flow control frameto the peer end in case they are congested, but generally slot time has the fixedvalue, which is different based on the relative product or version. Differentboards process the flow control frame received in different ways:

ET1V1/ET1V2 : Respond but do not conduct transparent transmission.

EGT : Respond and conduct transparent transmission.

EMS/EFS :

VLAN

For ET1V1 version, VLAN is used as the route flag during service convergence,that is, the convergence function of Ethernet service is implemented throughconfiguration of VLAN route. In the process, the following requirements shouldbe met:

1. Ethernet port of the center NE ET1 is set as the TAG attribute.

2. The broadband data communication equipment interconnected with thecenter NE ET1 must be capable of layer 3 functions, that is, it can divide VLAN,which is divided generally based on the destination IP address.

3. Other NEs are configured flexibly as required without requirement.

It is suggested that the port route is configured for the point-to-point service inother situation.

For ET1V2 version, VLAN performs the isolation function, that is the portisolation is implemented in VLAN filtering table, in which the frame forwarding isthen implemented through layer 2 switching.

Relationship Between Ethernet II and IEEE 802.3 Frames

In Ethernet frame Ethernet II, 2 bytes of Type domain is located after SA. IEEE802.3 is the MAC/LAN description about CSMA/CD defined by IEEE. In 802.3MAC frame, 2 bytes of Length domain is located after SA. Currently, Ethernet IItype of frame is used frequently, and 802.3 frame is only used in a few

protocols.


10/57


11/57


Internal Use Only


2.1.11

2.1.12

Mtu Discovery. The host can determine the minimum MTU passing on thepacket path through MTU Discovery. If both equipment are connected, but thereis no MTU Discovery function and their MTU values are inconsistent, the packetmay be discarded. Only if Mtu of both equipment is the minimum value of MRUof the peer end equipment, the communication is normal. Because some sitesconsider the network security problem and performance, they usually filterICMP packets, resulting in abnormal running of Mtu Discovery and Web pagecannot be opened and Internet cannot be accessed normally.

3. Setting principles

In the pure IP network, the following should be guaranteed: MTU value ofpath > the maximum user packet length.

In the pure MPLS network without VPN service, the following should beguaranteed: MTU value of path > length of eleven layers of labels of themaximum user packet (4).

For the layer 3 VPN service, the following should be guaranteed: MTUvalue of path > the maximum user packet + length of two layers of labels(8).

For the layer 2 VPN service, the following should be guaranteed: MTUvalue of path > the maximum user packet length + length of two layers oflabels (8) + length of twelve layers of frame headers (18).

VLAN ID Support of Data Boards

1. Metro 1000 ET1 series boards

42ET1 does not have VLAN filtering table, so it can configure VLAN routes inthe range of 1 to 4095. 42ET1O/D has VLAN filtering table and layer 2 switchingfunction, so it can configure in the range of 1 to 4094.

2. Metro 3000ET1 series boards

61ET1 does not have VLAN filtering table, so it can configure VLAN routes inthe range of 1 to 4095. 61ET1S has VLAN filtering table and layer 2 switchingfunction, so it can configure in the range of 2 to 4094.

3. Metro 2050ET1 series boards

11ET1 does not have VLAN filtering table, so it can configure VLAN routes inthe range of 0 to 4095. 11ET1S has VLAN filtering table and layer 2 switching

function, so it can configure in the range of 0 to 4095.4. EFGS series boards

EFGS boards support the transparent transmission and layer 2 switchingfunction, so it can configure VLAN IDs in the range of 0 to 4095.

Differenting a Single-Module Optical Interface from a Multiple-ModeOptical Interface on an SS42AIUA02

Differentiate by the optical interface location: Starting from the right, the 1st and2nd optical interfaces are multiple-mode, and the 3rd and 4 th optical interfacesare single-mode.


12/57


Internal Use Only


2.1.13

2.1.14

Differentiate by color: The opticial interfaces in black are multiple-mode, and theopticial interfaces in blue are single-mode.

In addition, you can unplug a board and observe its laser module, if 1300 nmis marked on it, then the module is a single-mode optical interface.

Locating the Channel that Generated an ATM Alarm

For example:

14 LOS critical start 2001-7-20 11:20:58 None0x0600ffb8

14 LCD major start 2001-7-20 11:20:58 None0x0600ffb8

14 OOF major start 2001-7-20 11:20:58 None0x0600ffb8

14 LCD major start 2001-7-20 11:20:58 None0x0700ffb8

Total records :4

The alarm parameters 1 to 7 correspond to MHY physical buses 0 to 6, and ATM optical interfaces on four AIU boards correspond to port1, port2, port3 andport4. Where, the corresponding physical port numbers are 0, 1, 4 and 5,and the corresponding physical port numbers of three buses at SDH side are2, 3 and 6. From the above alarms queried, we can determine that the 4thoptical interface on AIU board reports and receives no-light alarm, and No. 6bus at SDH side reports LCD alarm. The above are alarm report definitions inAIUV1 version.

The port definition in AIUV2 version is modified, and report ports queried 1,2...7 correspond to the external ports 1 to 4 and internal ports 5 to 7.

Querying Ethernet Performance Events of an ET1 Board

Taking the query of current performance events of the Ethernet as an example,

first set start time and end time with the following command:

:per-set-ethmontime:prdcur,2001-3-5,12*0*0,2088-12-31,12*0*0;

Start time can be set as any time before NE time.

Then set monitoring attribute, that is the categories to be monitored, such ascurrent performance, 30-second performance and variable period performance.For example, set the current performance monitoring of the 1st Ethernet portwith the following command: :per-set-ethmon:4,1,0,0,prdcur,perexall,1;

At that time, the performance counter on the board begins to count. To count

Ethernet performance data, query the current performance of the 1st port with

the following performance query

command: :per-get-ethcurdata:4,1,prdcur,perexall;


13/57


Internal Use Only


2.1.15

2.1.16

Setting Switching Time and Hold-Off Time of a VP Ring in the CaseMSP and VP Ring Coexist

The first version of the AIU does not provide multiplex section protection, but thesecond version provides double-layer protection for multiplex section and VPRing. Generally, we first start multiplex section protection, and then start VPRing protection, to implement the layered protection. If the multiplex sectionprotection is invalid, the AIU cannot receive ATM cell, and the board will reportalarms such as LCD and VP-AIS. After a period of delay, VP Ring protection isstarted, and it selectively receives the standby path to recover ATM service.Because ATM alarm needs 3 seconds, the delay time should be longer than 3seconds. In data setting specifications, it is required that the delay time ofVPring protection switching is set as 10 seconds (100 100 milliseconds )and note that the command line is set in the unit of 100 milliseconds.

During the recovery of protection switching, we stagger the recovery time ofmultiplex section protection and recovery time of VP Ring protection. In datasetting specifications, it is required that the recovery time of VPringprotection switching is set as 12 minutes (12 minutes), and note that therecovery time of VPring protection switching in the command line is in theunit of minute.

Querying the Actual Working Mode of the 61ET1

When setting the working mode of Ethernet interface in Ethernetinterconnection, use a command line to query the result which is only theworking mode set by the host. If the peer end or Metro equipment is set asauto-negotiation, use ptp command to query the actual working mode ofEthernet interface:

ptp:bid,ce,0,port,14; (ports 0 to 7, indicating No. 1 to No. 8 Ethernet interfaces)

Return: cmd 0: 04 ce 00 xx yy ff ff ff;

Query the actual working mode and status of the port.

Where, xxyy is the value of 16-bit register, and the meanings of bits 0 to 15 fromright to left are as follows:

Bit 13: 1 indicates there is link and 0 indicates there is no link.

Bit 12: 1 indicates full-duplex and 0 indicates half-duplex.

Bit 11: 1 indicates 100 M and 0 indicates 10 M.

For example, if xxyy is 38c8, it indicates that the register is in 100 M full duplexmode and its link status is normal.

Remarks: In 1.44 version and higher, the :ptp:bid,12,86,02 command can bedirectly used to query the actual working mode of all the network interfaces ofthe board.


14/57


Internal Use Only


2.1.17

2.1.18

2.1.19

2.1.20

Judging the Working Status of a Network Interface According to ItsIndicators

There are two indicators on each network interface of an Ethernet board, andthey are used to indicate the working status of the network interface. The upperindicator is link indicator (green), and the lower indicator is data indicator(yellow).

The link indicator only indicates a connection has been established, and notindicate the communication is normal. If the link indicator is off, then generallythe network cable is faulty or the working modes of Ethernet ports at both endsare unmatched. For example, if the mode at one end is set as 10 M, but themode at the other end is set as 100 M, then the link indicator is off.

The following data indicator will be on in case there is data transmitted onEthernet interface. Note that the data indicator is also on under the following

circumstances: The tag attributes at both interconnection ends are unmatchedor Ethernet data is discarded caused by its error frame structure after theEthernet port receives data.

Whether ETHLOS Alarm will Disappear After the Network Interface ofthe ET1 Board Loops Back

ETHLOS alarm will disappear if the ET1 board loops back in 100 M mode, butthe alarm still exists if the ET1 board loops back in 10 M mode. The reason liesin that the chip loopback operation is conducted in different locations in 10 Mand 100 M modes, resulting in the values of LINK bit in the register aredifferent. In 100 M mode, the loopback operation sets LINK bit as 1, and the

system deems a link has been established after the software tests, thereforethere is no ETHLOS alarm. But in 10 M mode, LINK bit is still 0 during theloopback operation, so there is alarm. This problem is caused by hardware,which is only for knowing.

Use of Standard/Manufacturerer Network Cables

The data communication equipment can be divided into two categories:Terminal equipment and convergence equipment. The principles for networkcable selection are: A crossover network cable is used for interconnectionbetween both terminal equipment, such as interconnection between both PCs.

A crossover network cable is used for interconnection of data interfacesbetween both convergence equipment, such as interconnection between HUBand L2 (a standard network cable is used for interconnection between theUPLINK interface and data interface). A standard network cable is used forinterconnection between terminal equipment and convergence equipment, suchas interconnection between PC and L2.

The common terminal equipment contains PC, router and Ethernet board.

The common convergence equipment contains HUB and L2.

Precautions to Setting the Working Mode of Ports of an EFGS Board

After the configuration of an interface board, the working mode configurationshould be delivered after the board reports the interface board event, otherwise


15/57


Internal Use Only


2.1.21

2.1.22

the chip will be set as auto-negotiation. After init-all, delivery of the commandused to configurate the interface and delivery of port working modeconfiguration may cause the port to be set as auto-negotiation. Theauto-negotiation port and full-duplex port are negotiated to the half-duplex. It isrecommended that you use :ethn-cfg-get-bdpara:bid,allport notuse :ethn-cfg-get-workmode:bid,allport to query the actual working mode ofthe port after delivery of the configuration. The query result is the working modeof the configured port. After the problem appears, use :ethn-cfg-set-workmode to set the working mode of the port again.

Query Command of Actual Working Mode of Ports of a Data AttributeBoard

Many Ethernet problems are caused by the working mode setting of the port. Tolocate a problem, query the actual working mode of the board. The following are

some examples:1. The ET1D in Metro 1000 queries its actual working mode:

:eth-cfg-get- portbdpara:bid,allport

2. The ET1D in Metro 500 queries its actual working mode:

:ethn-cfg-get-portbdpara:6,allport

3. The ET1 V2 board queries its actual working mode:

:eth-cfg-get- portbdpara:bid,allport;

4. The EFGS board queries its actual working mode:

:ethn-cfg-get-portbdpara:bid,allport

5. The ET1V1 queries its actual working mode:

1) In Metro 3000 host of 4.5.6.10 and higher version, use:

:ethn-cfg-get-portbdpara:bid,allport;

2) In other cases, use ptp command to query:

:ptp:bid,12,86,0,2

Lets take an example to illustrate it:

:ptp:4,12,86,0,2

cmd 0: 04 12 86 00 01 00 01 00 01 00 01 00 01 00 01 00 01 01 04

The first byte in color indicates whether the port is enabled: char[1]: where 1indicates the network interface is enabled, and 0 indicates disabled. The secondbyte indicates the working mode: char[2]: whose value is in the range of 0 to 4,where 0 indicates auto-negotiation (this mode does not exist in the actualworking modes), 1 indicates 10 M half duplex, 2 indicates 10 M full duplex, 3indicates 100 M half duplex and 4 indicates 100 M full duplex.

Encapsulation Protocol of Each Data Attribute Version

I. ET1 V1 series - - - ML-PPP


16/57


Internal Use Only


2.1.23

2.1.24

1. ET1 boards in Metro 1000, 3000 and 2050.

II. ET1 V2 series - - - ML-PPP

1. Metro 500: ET1D.2. Metro 1000: ET1O, EF1 and ET1D.

3. Metro 2050: ET1S and EF1.

4. Metro 3000: ET1S.

III. 100 M and gigabit pure transparent transmission series

1. EGT/EFT in Metro 3000: LAPS/HDLC/GFP.

2. FE08 and GE02 in Metro 5000: Nonstandard HDLC.

IV. EFGS V1 series - - - LAPS/GFP/HDLC

1. Metro 1000: EFS

2. Metro 3000: EFS and EMS

3. OSN2500/3500: EFS and EGS

4. Metro 5000: EGS.

V. EFGS V2 series - - - GFP

1. Metro 1000: EFS

2. Metro 3000: EFS and EMS

3. OSN2500/3500: EFS and EGS

4. Metro 5000: EGS.

Unshared Condition Between ET1 Inserted in Metro 3000 IU12 Slotand PQ1 Board Inserted in IUP

The IU12 and IUP slots of the Metro 3000 equipment share 4 buses. In casePQ1 is inserted in the IUP, the IU12 cannot share 4 and more of VC4 buses. IfSS61ET1.2 and SS61ET1.3 share 4 VC4 buses, the configuration must befailed. If the SS61ET1.3REV0 board shares 2 VC4 buses, normally it can workwith IUP PQ1. But the host does not differentiate 2VC4 from 4VC4, and both aredeemed as 4VC4, therefore the SS61ET1 board cannot be inserted in IU12 andIUP slots with PQ1 simultaneously. This condition can be avoided by changingslots of the ET1 board.

Explanations of EPL, EVPL, EPLn and EVPLn Services

EPL: Ethernet Private Line

EVPL: Ethernet Virtual Private Line

EPLn: Ethernet Private Line network

EVPLn: Ethernet Virtual Private Line network


17/57


Internal Use Only


2.1.25

2.1.26

2.1.27

2.1.28

2 M Service Transition in 2 M Tributary Card of ET1 Board

The ET1 adopts the ML-PPP protocol and its encapsulation granule is VC12,which adopts the multi-channel binding protocol, over which each Ethernetframe is fragmentized by the 64-byte length, and then the frame headerinformation, which used in the peer-end reassembly, of ML-PPP is added beforeeach fragment. At last, the fragment is directly placed in VC12 payload fortransmission. Therefore, after 2 M transition, the payload reaches the peer endwithout change, and the peer end equipment reassembles the information ofeach fragment to implement the communication.

2 M Service Transition Failure in 2 M Tributary Cards of EFGS Seriesof Boards

Although the encapsulation granule of the EFGS board is also VC12, but itadopts the Ethernet protocol LAPS or GFP, which are associated with theinformation between fragments or Ethernet frames based on the virtualconcatenation information. The virtual concatenation adopts H4 or K4 byte, andits overhead is terminated after 2 M transition, and then the information reachesthe peer end, resulting in failure of reassembly, thus the communication fails tobe implemented.

Meaning of PING Command Parameters

Common parameters: -t send packages ceaselessly, and pressCtrl+C to stop

-l size set the length of the packages to be sent

-n count times, for which packages are to be sent

Example: Ping 129.9.0.4 -l 500 -n 10 means sending packages of 500bytes to 129.9.0.4 for 10 times.

Meaning of RMON Ethernet Alarms

Alarm event identifier Alarm ID Alarm event nameDropOv 0x129 Times for packet loss is higher than the upper-bound alarm value.DropUd 0x12a Times for packet loss is lower than the lower-bound alarm value.RxBadOctOv 0x12b Bad packet bytes received are higher than the upper-bound alarm value.

RxBadOctUd 0x12c Bad packet bytes received are lower than the lower-bound alarm value.TxBadOctOv 0x12d Bad packet bytes transmitted are higher than the upper-bound alarm

value.TxBadOctUd 0x12e Bad packet bytes transmitted are lower than the lower-bound alarm

value.ColOv 0x12f Number of conflicts detected is higher than the upper-bound alarm value.ColUd 0x130 Number of conflicts detected is lower than the lower-bound alarm value. AligErrOv 0x131 Number of alignment errors is higher than the upper-bound alarm value. AligErrUd 0x132 Number of alignment errors is lower than the lower-bound alarm value.FCSErrOv 0x133 Number of checksum errors is higher than the upper-bound alarm value.FCSErrUd 0x134 Number of checksum errors is lower than the lower-bound alarm value.LateColOv 0x135 Times for detected collisions in the timeslot time after sending is higher

than the upper-bound alarm value.LateColUd 0x136 Times for detected collisions in the timeslot time after sending is lower

than the lower-bound alarm value.


18/57


Internal Use Only


Alarm event identifier Alarm ID Alarm event nameExcColOv 0x137 Number of frames failed to be sent due to continuous collisions is higher

than the upper-bound alarm value.ExcColUd 0x138 Number of frames failed to be sent due to continuous collisions is lower

than the lower-bound alarm value.DefTxOv 0x139 Number of frames to be deferred transmission is higher than the

upper-bound alarm value.DefTxUd 0x13a Number of frames to be deferred transmission is lower than the

lower-bound alarm value.CarErrOv 0x13b Number of carrier errors detected is higher than the upper-bound alarm

value.CarErrUd 0x13c Number of carrier errors detected is lower than the lower-bound alarm

value.

2.1.29

2.1.30

2.1.31

Auto-Negotiation Function of 10 M/100 M Network Interface

Because Ethernet rates and types of duplex are diversified, the auto-negotiationmechanism is introduced to pare down the failed interconnection andcomplexity of manual configuration. The auto-negotiation commonly mentionedrefers to the rate and duplex auto-negotiation. The interconnected Ethernetinterfaces supported auto-negotiation adopt a kind of standard FLP (for fastEthernet) or NLP (for Ethernet) to set their working modes as the highest ratesupported by both interfaces through a negotiation mechanism. For example, ifboth interfaces support the auto-negotiation, and their highest rates are all 100M full-duplex, then the negotiation result should 100 M full-duplex. If bothinterfaces support the auto-negotiation, but the highest rate at one end is 100 Mfull-duplex, and the rate at the other end is 100 M half-duplex, then thenegotiation result should be 100 M half-duplex. The same is true of 10 Mfull/half-duplex. The auto-negotiation mechanism can be adopted to ensure theconsistency of rates and duplex modes of both interfaces and reach the highestrate supported by both interfaces, thus ensuring the transmission efficiency.

Not Using Network Cables Whose Both Ends are One-to-OneCorrespondence to Transmit 100 M Service

The standard cable sequence of standard network cables is as follows: Yellowwhite, yellow, green white, blue, blue white, green, brown white and brown, andboth ends of the cables are consistent. Such network cables are capable of 10M/100 M line connection. Even though the cable sequence of network cablesare consistent at both ends, the network cables are only capable of 10 M lineconnection. If 100 M ports are connected with 10 M network cables, packet

collision will incur, resulting in unsteady connection and disconnection, evencomplete disconnection.

Introduction to 10Base5, 10Base2 and 10Base-T Cables

The 10Base5 thick coax cable adopts the plug-in connector, indicating that theworking rate is 10 Mb/s, the baseband signals are adopted, the longest segmentlength supported is 500 m, and the maximum number of segments is 100. The10Base5 thick coax cable has thick core diameter, and is not bent easily, so it isinstalled very inconveniently.

The 10Base2 thin coaxial cable adopts the industry standard BNC connectors toform a T type of socket with flexibility and high reliability, and its price is


19/57


Internal Use Only


2.1.32

2.1.33

relatively cheap. But it can only be used in the range of 200 meters, and only 30computers can be used in each segment whose highest amount is 30.

The 10Base-T is a kind of currently most widely applied Ethernet cable standard.One of its obvious advantages is it is liable to expand, simple to maintain, and itsprice is cheap. A concentrator, several 10Base-T cables and several computerscan form a practical small-sized LAN. The 10Base-T has the followingdisadvantage: The longest valid transmission distance between it andconcentrator is 100 m. Even though it is a high-quality C5 cable, the longestdistance is only 150 m.

Explanation of Auto-Negotiation Function of Gigabit Ethernet

The IEEE 802.3z standard defines the relative contents of Gigabit Ethernet. TheGigabit Ethernet has auto-negotiation function, which only contains negotiationof half-duplex or full-duplex flow control and determines whether control frameis supported. The rate cannot be determined by negotiation with low-speedEthernet. The working mode negotiation is related to optical modules of differentfactories. To guarantee the successful interconnection, set to the same at bothends, that is auto-negotiation to auto-negotiation, and full duplex to full duplex.Frequently, the unsuccessful interconnection is caused by inconsistencybetween auto-negotiation at one end and 1000MFULL at the other on thenetwork.

Introduction to PSTN, ISDN, DDN, X.25 Network and Frame RelayNetwork

PSTN (Public Switched Telephone Network) may be a public narrowbandnetwork we commonly met. Currently it provides telephony and fax services,and implements some limited data transmission services through modem.

ISDN (Integrated Services Digital Network) provides fully digitalized services,including voice, data, graphics and video, between terminal users.

DDN (Digital Data Network) is a widely used narrowband public data networkbased on point-to-point connection.

X.25 network is an international standard WAN, and it is the unique availableWAN technology in many regions, especially in Europe. Its built-in errorcorrection, flow control as well as packet loss and re-transmission mechanismsprovides high reliability for it, which is applicable to toll noise line. The maximum

rate is only 64 Kbps, which limits the range of services provided. Each site onthe way has to reassembly the packets to decrease the data throughout, so thepacket delay is large. Obviously, X.25 is inapplicable to the channel with hightransmission quality.

Frame relay is a kind of widely used service, which adopts E-1 circuit, andwhose rate changes in the range of 64 K to 2 M. Because the rate is high, errordetection decreases, and simple signaling in the current MAN connection canbe used. Delay of medium nodes is much smaller than X.25 network. The lengthof frame relay is variable, so conveniently applies for any packet or frame inLAN, to provide transparency for users. Frame relay is liable to be affected bynetwork congestion, and it cannot specially guarantee the time-sensitive realtime communication. In case the line is interrupted by noise, it will re-transmitpackets.


20/57


21/57


22/57


Internal Use Only


4. Back-to-back: The allowed maximum length of the data frames successivelyappearing at the minimum legal frame interval in case of no frame lost duringtransmission, reflecting the data bursting tolerance of a system

Due to the complementary relation between throughput and frame loss rate,throughput and latency need attention in general cases. Try to make the usernot measure back-to-back of a board. During fault location, the impact of allthese indices on service is certainly worth consideration.

Moreover the long-term stability test can help discern the reliability degree of asystem that operates under a certain load for long. In the case that the userreports there are a few packets lost, you can judge whether MSTP product faultis accountable finally through this test.

On the whole, the MSTP product provides link-layer and physical-layerfunctions, and so any test in a real sense must be based on these two layers.The performance indices of the MSTP product measured by means of software

are indicative of partial performance to some extent, and thus inaccurate andnot recommended because software test involves upper-layer protocols,software implementation and some other external factors.

Question : Why do test results vary with the frame length used inthroughput test?

Answer : The interFrameGap, leading code and so on are not transmitted through SDH, butre-generated at the peer end, and thus no bandwidth bound to the channel is used.

2.2.3 Performance Event (RMON)

The boards with different Ethernet features offer different performance monitorfunctions. The board with RMON feature can provide performancethreshold-crossing alarms. Performance events (RMON) are very helpful indaily maintenance and fault location.

Among a multitudes of performance events, you need to attach greatimportance to the following:

1. Various types of error packets

a. CRC error and extra-short frame: As described in Section 2.3, first check ifport modes are matched, then if network cables are of good quality or interfered,and finally if there is any hardware fault of network ports.

b. Alignment: Check if collision happens. In presence of many error packets,you are recommended to replace the hardware (the peer equipment is morelikely to have problems).

c. Sent error packets: Processing capacity bottleneck of the local FIFO andhardware fault are generally the reasons. In presence of many error packetsappearing frequently, you are recommended to replace the board.

2. Flow control frame

The frame is indicative of overly large network traffic. In this case, suggest theuser to adjust service load or perform traffic shaping.

3. Collision and back-off


23/57


Internal Use Only


2.2.4

Collision and back-off events show that the local port works in the half-duplexmode. You are recommended to query if the peer port also works in thehalf-duplex mode.

It is unnecessary to pay much attention to other performance events duringdaily maintenance.

SUBCARD_ABN Alarm

In presence of an subcard_abn alarm, make sure if the :cfg-create-subboard command is already used to create an interface board successfully. If so, resortto the following commands for the reason.

Query a logically installed interface board (ET1 command)

Name cfg-get-subboard

Function Query a logically installedinterface board.

Command level Query level

Target user Internal/Customer service/Customer

Version 4.05.04.10 and later versions

Input format Two parameters, repeated parameters

Parameterlocation

Parameter value

1 The No. of a processing board, which can be 0, 1, 2, 3, 4, 5, 6, 9, 10, 11, 12, 13 or 14

Input parameter

2 The No. of aninterface board, which can be 0, 1 or 2. The value 0 indicates allinterfaceboards of a processing board are to be queried.

Output format SUB BOARDSBID SUBID ATTRIBUTEBoard slot No. sub-board slot No.interface board typeIn absence of records, error codes will be output.

Example :cfg-get-subboard:1,1

Precautions

Remarks If theinterface board type is shown null in the query result, it indicates nointerface board is installed.

Query a physically installed interface board (ET1 command)Name cfg-get-physubboard

Function Query a physically installedinterface board.

Command level Query level

Target user Internal/Customer service/Customer

Version 4.05.04.10 and later versions

Input format Two parameters, repeated parameters

Input parameter Parameterlocation

Parameter value


24/57


Internal Use Only


1 The No. of a processing board, which can be 0, 1, 2, 3, 4, 5, 6, 9, 10, 11, 12, 13 or 14

2 The No. of aninterface board, which can be 0, 1 or 2. The value 0 indicates allinterfaceboards of a processing board are to be queried.

Output format SUB BOARDSBID SUBID ATTRIBUTEBoard slot No. sub-board slot No.interface board typeIn absence of records, error codes will be output.

Example :cfg-get-physubboard:1,1

Precautions

Remarks If theinterface board type is shown null in the query result, it indicates nointerface boardis installed.

You may use this command:

:ptp:bid,12,28,2,0Function: Configure interface board type.

Format: para[0]: Slot No.: The value 1 indicates interface board slot A, 2indicates interface board slot B and 0 indicates all boards slots.

para[1]: Interface board code. 0x00 indicates the interface board slotholds no board. There are interface boards of types 03, 04, 05, 06 and 07currently.

12 Command format;

para[1]: Query command type: The value 1 indicates logical query and 2indicates the physical interface board installed is to be queried.

para[2]: Query board slot.: The value 1 indicates board slot A, 2 indicatesboard slot B and 0 indicates all board slots.

Return;

para[1]: Query command type: The value 1 indicates logical query and 2indicates physical query.

Para[2]: Interface slot No.

para[3]: Interface board type

The interface board types that can be deployed on the 2500+ and 3100 arelisted as below:

Code Interface board type

0 No interface board configured

0x03 SS61ETF4 (4-port electrical interface board)3100

0x04 SS61EFF4 (4-port optical interface board) 3100

0x05 SS61EMF801 (8-port optical interface board) 2500+

0x06 SS61EMF802 (4-port optical interface board) 2500+

0x07 SS61EMT8 (8-port electrical interface board) 2500+


25/57


Internal Use Only


2.2.5 Common Questions on FCS_ERR Alarm

1. When does a board report an FCS_ERR alarm?

The FCS alarm is the only GFP-related alarm the EFGS board supportscurrently, and an important means of locating problems.

An FCS alarm is raised when the following conditions are all available:

1) The GFP frame delineation state is SYNC, that is, the PL215 can identifyGFP frames.

2) As the received GFP frame has a payload FCS field, but the IDLE frame hasno such field, service data packets must be sent to generate an FCS_ERRalarm.

3) There is FCS check error for the received GFP frames.

The major reasons for the EFGS board reporting an FCS_ERR alarm are:1) Inconsistent GFP parameters of two sides

2) Bit error codes caused by line, cross connection and SDH protectionswitching. Since GFP parameters of two sides are generally consistent, bit errorcode is the principal reason for FCS_ERR alarms.

2. When is an FCS_ERR alarm generated in case of inconsistent GFPparameters on two sides?

Under the following circumstances, an FCS_ERR alarm is generated in case ofinconsistent GFP parameters on two sides:

1) The peer GFP parameter FCS is set to FCS32, because only in this case thelocal will conduct FCS check and an FCS_ERR alarm may be reported.

Thanks to the FCS adaptive function of the board, the PL215 is able to decidewhether to perform FCS check according to the PFI flag in the type field in thereceived GFP frame. Therefore, the peer GFP parameter decides whether toperform FCS check locally. Local FCS check will be done only when the peerGFP parameter is set to FCS32. An FCS_ERR is likely to appear only whenFCS check is performed.

2) The scramble parameter of one side is set to x43 and that of the other side isdisable. If the peer FCS option is set to FCS32, for example, there will be anFCS_ERR alarm on the local side; otherwise, there will be no such alarms.

3) If the GFP parameter extension header is set to disable on one side and toenable on the other side, services cannot be transmitted successfully and thusthere will be no FCS_ERR alarm.

4) Suppose the GFP parameter ENDIAN-MODE is set to big on one side andto little on the other side. If the peer FCS is set to FCS32, there will FCS_ERRalarms on the local side; otherwise, there will be no such alarms.

FCS_ERR(0XF857)Interface name FCS check error alarmRequirement description In presence of FCS check error, this alarm needs to be reported.Concerned board/module EGS EFSCode 0XF857Level 3

Parameter Parameter location Parameter description


26/57


Internal Use Only


para[0] Logical port No., which is always 1para[1-2]VC-TRUNK No.

Alarm source FCS check error Active suppression NoPassive suppression NoNMS version supported T2000V1R6Host version supportedBoard version supportedDifference between versions No differenceReferences NoneRemarks NoneRevision description NoneDefinition date 2003-03-26Person-in-charge Zhou Jianwei

Examples:

The following alarms are reported by the efs board, to which it belongs (metro

1000 or 3000) is unknown now.882 13 FCS_ERR critical end2004-09-03 02:03:25 2004-09-03 02:03:26 0x01ff57ff

883 13 VCDELAYTL critical end2004-09-03 02:03:26 2004-09-03 02:03:27 0x01ff32ff

884 13 ILL_MFI_VC3 major end2004-09-03 02:03:27 2004-09-03 02:03:28 0x01ff61ff

FCS_ERR and VCDELAYTL are VCTRUNK-type alarms. 01 in the parameter0x01ff57ff is the VCTRUNK No., and 57 is alarm code, which can be ignored.

ILL_MFI_VC3 is an alarm of the channel level. 01 in 0x01ff61ff is channel No.(namely, the No. of the VC3), and 61 is alarm code, which can be ignored.

As the old product has no optical port No., you need to remove the first opticalport No. when checking against the interface document.

The following alarms are raised by the 5.0 platform-based efgs board:

#9-9:w37061 [][][2004-10-29 16:21:50]>

EVENT_ALM_AUTO_REPORT -- 0

NUM BID EID SEVERITY STATETIME PARA1 PARA2 PARA3 PARA4 PARA5

1629 2 FCS_ERR CR end2004-10-29 16:21:40 0x01 0000 0x01 0xff 0xff

PARA1 indicates a logical port No., and PARA2-PARA3 indicates a VC-TRUNKNo.

After comparison and checking related documents, we can know that:

For the alarm reported by the efgs board of the 4.0 platform-based product,para1 and para2 denote vctrunk No. or channel No., and para3 and para4denote alarm codes.

The alarm of the efgs board of the 5.0 platform-based product has fiveparameters. The parameter para1 is logical port No. and para2 para3 is vctrunkNo. or channel No. On the 5.0 platform, 0xff, instead of para4 and para5, is usedto display alarm code.


27/57


Internal Use Only


Chapter 3

3.1

Usage Description of Test FrameFunctionsFull Service Flow Test for the EFGS

Board

Introductions to Functions

There are two types f test frames on the EFGS board: GFP management frameused to verify interoperability between VCTRUNK ports, custom MAC framesent by an IP port or a VCTRUNK port to the outside.

Management frame

Figure 1 Verification through a GFP management frame

CustomMAC frame

Figure 2 Sending direction of a custom MAC frame

CustomMAC frame

Figure 3 Verification path of a custom MAC frame

3.2

3.2.1

Using the Test Frame

GFP Management Test Frame

The GFP management test frame can be used to verify the configuration of theVCTRUNK between boards, namely, SDH service configuration and VCTRUNKchannel binding configuration.


28/57


Internal Use Only


3.2.2 Verification Procedure

1. Issue service configuration, check for any obvious configuration problems byeyes.

2. Issue the command to enable the GFP management test frame.Name ethn-cfg-set-testenFunction Set sending parameters for the test frame.Version Supporting the host version of the EFGS boardInput format : ethn-cfg-set-testen:bid,vctrunk,enable,direction,number; parameters number = 5, parameter block repeated &

parameter repeatedInputparameter

Parameterlocation

Parameter value Parameterrepeated or not

1 Slot No. MML repeated2 VC-Trunk:

vctrunk1-vctrunkM: Indicates VC-Trunk MML repeated

3 Enable flag: 2 = Continue, 1 = Burst, 0 = Disable4 Sending direction: 0 = SDH direction, valid only when enabled5 Number of sent test packets: 1-255,

valid only when the enable flag is set to 1 = Burst.Output format Success or error information is returned.Example : ethn-cfg-set-testen:1,vctrunk2,0,0,89Precautions The database is not saved, and board configuration is directly issued.

At present, the configuration of sending direction is not supported.

In normal cases, use:

:ethn-cfg-set-testen:bid,vctrunkport,1,0,1; //Send a packet to the SDHdirection in the burst manner.

3. Query test results

In presence correct service configuration, the following information is returnedunder the Navigator:

ETH TEST COUNT EVENT:

BOARD-ID PORT-ID COUNT-2 COUNT-3 COUNT-1END-FLAG

Bid vctrunk1 1 0 1 1

In the returned information, COUNT-1 indicates the number of sent test frames,COUNT-2 is the number of the reply frames to the received test frames, andCOUNT-3 is the number of the received test frames. Note the sequence of the

three values. COUNT-2 indicates when receiving a test frame from the local end,the peer VCTRUNK port will automatically return a reply frame. If the local endreceives the reply frames in the same number as the sent frames, theinter-board SDH service configuration and VCTRUNK configuration must becorrect.

For the later developed host software, COUNT-1, COUNT-2 and COUNT-3 aremodified to TOTAL-SEND, RESPOND-RECV and NORMAL-RECV.

In addition, you can use :ethn-cfg-get-testcount:bid,vctrunkport; to query thetest frame counter.


29/57


Internal Use Only


3.3

3.3.1

Custom MAC Frame

Command Line Description

1. Set the contents of custom MAC frameName ethn-cfg-set-testpktparaVersion All host versions supporting the EFGS boardInput format :ethn-cfg-set-testpktpara:bid,vctrunk,length,testtype,datatype,dstmac,srcmac,dstip,srcip,vlanid;

number of parameters=10, parameter block repeat & parameter repeatInputparameter

Parameterlocation


1 Slot No.: 1-20 MML repeated2 Port No.:

ip1 ~ ipN: Indicates the Ethernet port.vctrunk1 ~ vctrunkM: Indicates the VC-Trunk.

MML repeated

3 Test packet length (bytes):In the range of 64 ~ MAX_PORT_MTU; default value = 64MAX_PORT_MTU: Customized for the Ethernet port and fixed to 9600 for theVCTRUNK.

4 Test packet type: 1 = Custom, 2 = IP packet; default value = Custom5 Test packet data type: (default value = 4)

1 = transmitted data fixed to AA2 = transmitted data fixed to 553 = transmitted data fixed to FF4 = transmitted data fixed to 005 = transmitted data increased by 1 (0~255 in ascending order)6 = transmitted data decreased by 1 (255~0 in descending order)

6 Destination MAC address: Defaults to all-Fs7 Source MAC address: Defaults to all-Fs8 Destination IP address: Defaults to all-0s

(for the type of Custom, it is invalid and fixed to all-0s)9 Source IP address: Defaults to all-0s

(for the type of Custom, it is invalid and fixed to all-0s)10 Test packet VLAN ID: In the range of 0~4095; default value = 0xFFFF

(0xFFFF indicates no VLAN ID)Output format Success is returned or error information is given.Example :ethn-cfg-set-testpktpara:1,vctrunk2,128,2,5,01-02-03-04-05-06,

01-02-03-04-05-07,10.01.02.03,10.01.02.04,0xffff;Remarks Preconditions for executing this command:

1. The according board has been installed on the slot.

2. Send the custom MAC frameName ethn-cfg-set-testpktenVersion All host versions supporting the EFGS boardInput format : ethn-cfg-set-testpkten:bid,vctrunk,number; number of parameters=3, parameter block repeat & parameter repeatInputparameter

Parameterlocation


1 Slot No.: 1-20 MML repeated2 Port No.:

ip1 ~ ipN: Indicates the Ethernet port.vctrunk1 ~ vctrunkM: Indicates the VC-Trunk.

MML repeated

3 Number of test packets transmitted: 0 = Not transmit (Stop), 1~0xFFFE =Number of packets transmitted (Burst), 0xFFFF = Transmit without limit(Continue)

Output format Success is returned or error information is given.Example :ethn-cfg-set-testpkten:1,vctrunk1,500;

Set the number of test packets transmitted from the vctrunk1 in slot 1 to 500.Remarks Preconditions for executing this command:


30/57


Internal Use Only


1. The according board has been installed on the slot.

3.3.2

3.3.3

Chapter 4

Test Procedure

1. Check service configurations for any obvious problems, and then issue theconfigrations.

2. Test the availability of the VCTRUNK with the GFP management test frame(refer to Section 2.1 of this document).

3. Customize the test procedure of the MAC frame, as shown in Figure 3:

a. Set NE1s MAC1 inloop (with phy/mac loop for example):

:ethn-cfg-set-loop:4,ip1,mac,rlb;

b. View the RMON performance count on the MAC ports of NE1 and NE2:

:rmon-get-curdata:4,1,ch1,grp1;//Query packet receiving count on port 1

:rmon-get-curdata:4,2,ch1,grp2;/Query packet sending count on port 1

Write down the performance data.

c. Issue the :ethn-cfg-set-testpkten:4,ip1,10; command//Set to send 10default MAC frames from port IP1

d. View the RMON performance count on the MAC ports of NE1 and NE2 again,calculate the increase of packets sent from NE2s port MAC1, and compare thisincrease with the number of MAC frames (bytes) sent from NE1s port MAC1. In

this example, items txpkt64, txbrdcast and txbok of RMON grp2 are 0x0a, 0x0aand 0x0280 respectively.

Precautions to the Test

1. In setting the MAC frame, if the port is a Tag aware port, you need set the VID(VLAN ID in a VLAN frame) of the frame to Trunk allow VLAN ID in the boardsservice settings.

2. In viewing the performance count of the peer NE port, you shall decide whatitems to check based on the MAC frame to be sent.

3. In sending a custom MAC frame, you can (if possible) use a portablecomputer to access the NEs FE port, and detect any outgoing data with Sniffer(a packet capturer). In Figure 3 for example, the portable computer shall beconnected to NE2s port MAC1.

Fault Location

What data to be queried in case of failure is always a difficult point inmaintaining the Ethernet board. The following summarizes some commonlocation methods, query commands and their description to help future

maintenance.


31/57


Internal Use Only


Similar to the SDH fault location idea, the Ethernet fault location also complieswith the principle of External Internal, Software Hardware, Board System.The technical methods (such as performance event, loop and test frame) should

be used for the planed and stepped location in combination with tool softwareand test meters.

It is necessary to locate the fault preliminarily to exclude the problem at the SDHlayer by querying relevant alarms and performances. And then, turn to locatethe problem at the Ethernet layer.

For the fault location of Ethernet services, check relevant alarms to the ET1board at first, focusing on some lower-order alarms such as BIP-EXEC, TU-LOPand LP-SLM. It is better to use the alarm query command at the board side:

:ptp:bid,16,0

In case of lower-order service alarms, check the SDH layer or the connectedrouter/Ethernet switch for any errors. It is difficult to perform this location andthere are few methods.

Remember to adopt the performance query tool in locating the Ethernet fault.The query results of performance events can easily lead to some conclusions.

Loop is also a good way for fault location. See section 4 for some commoncommands relevant to the loop. It is important to ask help from the datamaintenance personnel of the customer, and use the method ofPING+loop. For example, ping the IP address of the remote router/switchthrough the ET1 network interface. If the operation succeeds, it indicates thatthere is no problem basically at the local side. It is recommended to adopt thefollowing format:

ping xxx.xxx.xxx.xxx l 1000 tl 1000 indicates the packet length is 1000 bytes, and -t indicates persistentping operation. Try the ping operation with multiple packet lengths and multipleping windows. The successful ping operation cannot exclude the problem of theMetro equipment completely, because the ping operation can also succeed withsmall traffic in case the port works in faulty mode. It just proves that the Ethernetlink is well configured and there is no problem at the SDH layer. At first, it isnecessary to check and confirm there is no problem in the configuration andchannel at the SDH layer. And then, focus on the Ethernet data layer to locateproblems.

Let us see the common fault types.

Generally, the Ethernet involves two fault types:

The link is completely disconnected.

There is persistent packet loss on the link.

The fault causes may be:Fault symptom

Possible fault causes

Ethernet link completely disconnected Persistent packet loss on the link

1 The setting of TAG attribute (TAG/UNTAG) ofthe port is changed.

Large traffic leads to insufficient configurationbandwidth.

2 The physical layer fails. Specifically, the real

port works in faulty mode, some parameters ofthe port are abnormal, the interface board fails,

The bandwidth is sufficient, but there are large

service bursts.


32/57


Internal Use Only


Fault symptom

Possible fault causes

Ethernet link completely disconnected Persistent packet loss on the link

or the register of the physical layer is arbitrarilyrewritten.

3 The network cables or fiber optics fail. When there is too large service traffic, theremote equipment does not respond to the flowcontrol.

4 The data of Ethernet static routes is lost. The Maximum Transmission Unit (MTU) set forthe board is less than the real transmissionpacket length of the equipment.

5 In case of NE pointer justification, BIP-OVERand TU-LOP are reported from some channelsof ET1, and the service is interrupted. Boardreplacement or reset can only transfer the faultychannel, but not solve the problem completely.

The port mode does not match that of theremote equipment, thus the equipment works inabnormal status.

6 The board hardware fails. The network cables or fiber optics fail.7 A great deal of packet loss causes service

interruption. Refer to the processing of thesecond fault type.

When the Ethernet service packet lengths oftwo directions keep too large difference for along time, or all the packet lengths are shortbytes (64-128 bytes), it may cause large ET1performance decrease and packet loss.

8 The current spanning tree is based on user. Ifthere are more than one MP connection at twostations, VLAN isolation only may causebroadcast storm of BPDU packets.

The board hardware fails.

9 Huawei equipment has only one MAC addresslearning table, and all the users and VLANsshare it. Because the layer 3 equipment uses itsown MAC address to forward packets, be surenot to connect more than one port of the layer 3equipment that has only one MAC address. (It

cannot be avoided in both user and VLANisolations because Huawei equipment has onlyone MAC learning table)

10 Transmitting/receiving excessive BPDU packetsmay lead to resetting.

11 ETH-LOS is reported during normal runningprocess due to coupling interference, and theservice is interrupted. It may be automaticallyrestored or not. ETH-LOS may be reportedtransiently at the interval of 5 seconds (errorreport).

Note: The text in blue is only applicable to ET1V2 (layer 2 switching version),and the text in red describes the problems only found on the Metro 3100currently.

4.1 Locating the Problems of Completely InterruptedEthernet Links

For the failure of completely interrupted links, the specific symptoms include:connecting router and switch receiving no packets, service completelyinterrupted, and failed ping operation to the remote equipment. The followingitems should be checked:


33/57


Internal Use Only


4.1.1 TAG Attribute (TAG/UNTAG) Setting of the Port Changed

This fault occurs with large probability in case of software upgrade and boardreset. For example, there is a bug in the 4.5.3.40 host version of the 2500+. Thehost version defaults the ET1 MP port attribute to UNTAG, while the boarddefaults it to TAG. Finding that UNTAG is set (default attribute) when issuing theconfiguration, the host will not issue it to the board. When resetting, the boarddefaults to the TAG attribute. Thus the service is interrupted.

The host query commands include:

Querying TAG attribute of the Ethernet port (ET1 command)

Name cfg-get-ethtag

Format Location definition; number of parameters = 1

Authority

Query level

Description

Serial No. Parametermeaning

Parameter value Remarks Parameter

1 Board ID 1-4; 11-14; 0 indicates to queryall boards.

Example :cfg-get-ethtag:3;Note: Query theTAG setting of board 3.

Querying TAG attribute of the Ethernet port (ET1S command)

Name eth-cfg-get-tag Function Query TAG attribute of the Ethernet port Command level Query level Open range Internal level/customer service level/user level Version 4.05.04.10 and above versionsInput format Location definition. Number of parameters = 1; repeatability = unrepeatable

Parameterlocation

Parameter value Input parameter

1 Actual board ID: 0,1,2,3,4,11,12,13,14; 0 indicates all boards. Output format TAG DEFINE

Board-id port-idtag-state

Board ID; port ID;tag statusWhy the service cannot yet get through?

The following may tell you the truth:

:ptp:bid,12,83,port

Function: Set whether the MAC frame of Ethernet interface complies with theVLAN frame structure.

Format: CHAR[2];

CHAR[0]: Indicates the port ID, in the range of 0 to 8. 0 indicates all ports, 1-8indicate physical network ports 1-8, and 0x81-0x90 (bit 7 is 1) indicate binding

channels 1-16.


34/57


Internal Use Only


4.1.2

char[1]: Its value is 0 or 1. 0 indicates non-VLAN frame structure, and 1indicates VLAN frame structure. The default value is 1.

Query whether the actual port attribute of the board is consistent with that set bythe host NMS.

Two returned parameters: para[1] is the port ID, and para[2] is the attribute. 0indicates UNTAG and 1 indicates TAG.

Is the actual TAG attribute of the port consistent with the one you want?

Faulty Working Mode of the Port

The physical layer fails. Specifically, the real port works in faulty mode, someparameters of the port are abnormal, the interface board fails, or the register ofthe physical layer is arbitrarily rewritten.

This fault also occurs with large probability. It should be located by queryingrelevant register at the physical layer. The specific query commands include:

Querying the enabled status and working mode of the Ethernet port (ET1command)

Name cfg-get-ethport

Format Location definition; number of parameters = 1

Authority Setting level

Description

SerialNo. Parametermeaning Parameter value Remarks Parameter

1 Board ID Actual board ID: 1-4; 11-14; 0 indicates all boards.

Example :cfg-get-ethport:2;Note: Query the working mode of the Ethernet port on board 2.

Querying the working mode of the Ethernet port (ET1S command)

Name eth-cfg-get-workmode Function Query the working mode of the port. Command level Query level Open range Internal level/customer service level/user level Version 4.05.04.10 and above versionsInput format Location definition. Number of parameters = 1; repeatability = unrepeatable

Parameterlocation

Parameter value Input parameter

1 Actual board ID: 0, 1, 2, 3, 4, 5, 6, 9, 10, 11, 12, 13, 14; 0 indicates all boards. Output format WORK MODE DEFINE

Board-id port-id work-modeBoard ID; port ID; working mode

For example: :eth-cfg-get-workmode:2;

Of course, the NMS is mostly used to query relevant attributes.


35/57


Internal Use Only


In addition, the ET1V2 featured board provides a host command for queryingthe actual port status of the board.

Name eth-cfg-get-portattrib Function Query all attributes of the Ethernet port Command level Query level Open range Internal level/customer service level/user level Version 4.05.04.10 and above versionsInput format Location definition. Number of parameters = 2; repeatability = unrepeatable

Parameterlocation

Parameter value

1 Actual board ID: 0, 1, 2, 3, 4, 11, 12, 13, 14; 0 indicates all boards.

Input parameter

2 Port ID: allport indicates all ports;ip1-ip8 indicate physical network ports ip1-ip8; mp1-mp16 indicate MP ports MP1-MP16.

Output format PORT ATTRIBLE DEFINEBoard-id port-id user-id enable-state work-mode tag-state vlan-id Board ID; port ID; user; enabled status;working mode; TAG status; VLAN IDPriority mac-loop-mode phy-loop-mode flowcontrol-stateVLAN priority; MAC loop; physical loop; flow control status

Example :eth-cfg-get-portattrib:2,ip2;

The following may be used:

0x86: MBCMD_ETHPORT_SET (in coordination with 12 command)

Function: Set the enabled status and working rate/working mode of the Ethernetport (in coordination with 12 command to query the actual port status).

For example: :ptp:bid,12,86,0//Query the working mode of port received by thecontrol logic of the board from the host (compare it with the query results of thehost command)

Format: CHAR[3];

CHAR[0]: Indicates the Ethernet port. 0 indicates all network ports.

char[1]: 1 indicates the network port is enabled, and 0 indicates disabled.

char[2]: Indicates the setting of working rate/working mode, in the range of 0 to4. 0 indicates auto-negotiation, 1 indicates 10 M half-duplex, 2 indicates 10 Mfull-duplex, 3 indicates 100 M half-duplex, and 4 indicates 100 M full-duplex.

For the use of 86 command, query the description of the port working status

register of ET1.1) ptp:bid,12,86,0,2 indicates to query the status register of theboard, that is, the actual working mode of the port. Withoutparameter 2, ptp:bid,12,86,0 indicates to query the control register,that is, the issued configuration (above mentioned).

The command with parameter 2 has requirements for the board version:V1.23 is not supported, and V1.44 and above versions are supported.

2) The query results of two commands have different interpretation methods,but it is identical that the data of two bytes indicates a port. They are interpretedrespectively as follows:

#590338:ptp:0d,12,86,0


36/57


Internal Use Only


cmd 0: 0d 12 86 01 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Counted from 86, every two bytes indicate a port. In this example, 01 in 01 04indicates the port is enabled, and 04 indicates 100 M full-duplex.

#590338:ptp:0d,12,86,0,2

cmd 0: 0d 12 86 00 04 00 01 00 01 00 01 00 01 00 01 00 01 00 01

Counted from 86, every two bytes indicate a port. In this example, 00 in 00 04indicates whether the negotiation succeeds (not disabled port), and 04 indicates100 M full-duplex. It is different from the description in the document. The boardsoftware code indicates the register showing whether the negotiation succeeds.In case of auto-negotiation, 1 represents successful negotiation and 0represents other status. While this byte indicates the enabled status in thedocument.

:ptp:bid,ce,0,port-1,0 (port-1 indicates port ID minus 1)

Function: Query relevant parameters of the 974 chip register to find the actualworking mode of the port (generally it is recommended to use 86 commandabove).

:ptp:bid,ce,0,port-1,1





:ptp:bid,ce,0,port-1,6:ptp:bid,ce,0,port-1,10





In case of failure, it is possible to feed back all the failures to the R&D Center.Generally it is necessary to attend to registers 1, 13 and 14, where the actualworking settings of the board can be queried such as working mode, portenabled status, and link status. For the specific values, refer to ET1 PhysicalLayer Register Description .

For example, use the most common query method for the actual working modeof the board:

:ptp:bid,ce,0,port-1,14 //(port-1 indicates port ID minus 1; 1 for port 2, 2 for port3)

The returned data is two bytes, such as 0b ce 00 xx xx ff ff ff.

38,ca is the current status register value of the port, and its binary value is0011,1000,1100,1010.


37/57


Internal Use Only


4.1.3

4.1.4

Bits 4 and 5 from left to right respectively indicate the current duplex mode andrate. For bit 4, 1 indicates full-duplex and 0 indicates half-duplex. For bit 5, 1indicates 100 M and 0 indicates 10 M.

xx,xx: Indicates the value of 16-bit register.

Bit 13: 1 indicates there is link, and 0 indicates there is no link.

bit 12: 1 indicates full-duplex, and 0 indicates half-duplex.

Bit 11: 1 indicates 100 M, and 0 indicates 10 M.

For example, 38,c8 for xxyy indicates 100 M, full-duplex and normal linkstatus.

Note: Counted from right to left, 38c8 contains 16 digits of 0, 1, , 15 (the firstdigit

Documents

Troubleshooting Guide to Ethernet Data Boards.pdf