Troubleshooting Guide To Ethernet Data Boards PDF

Document code Target readers Edited by
Product name Product version Document version
Troubleshooting Guide to Ethernet Data Boards
Drafted by: Reviewed by: Reviewed by: Approved by:
Date: Date: Date: Date:
Huawei Technologies Co, Ltd

All Rights Reserved
Confidentiality: For Internal Use Only
Revision Record
Date
2005-3-29
Revision
Author
Description
Test Method of EFGS Board Service Process added to this document.
2007-10-22
Huawei secrets, no dispersion without permission
Page 2 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 2.1.11 VLAN ID Support of Data Boards........................................................................... 11 2.1.12 Differenting a Single-Module Optical Interface from a Multiple-Mode Optical Interface 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 VP Ring 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 PQ1 Board 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 to Transmit 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
U
2007-10-22
Page 3 of 57
Chapter 3 Usage Description of Test Frame FunctionsFull Service Flow Test for the EFGS Board ............................................................................................................................................... 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-LOP from 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 the Processing 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 in Case of Too Large Service Traffic .................................................................................... 41 4.2.4 MTU Set for the Board Less Than the Real Transmission Packet Length of the Equipment ......................................................................................................................... 41 4.2.5 Abnormal Working Status Caused by Unmatched Port Mode with the Remote Equipment ......................................................................................................................... 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 Ethernet Service 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
2007-10-22
Page 4 of 57
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 in optical network is faulty, and it also targets at guiding engineers to troubleshooting. Abbreviations: None. References None.
2007-10-22
Page 5 of 57
Troubleshooting Guide to Ethernet Data Boards Chapter 1 Overview

With the expansion of MSTP and wide application of MSTP products, problems involved in these products and in interconnection between these products and other network equipment come to be exposed in the network. To accurately locate all problems, you need not only to master the SDH technology, but also deeply 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 this document are not represented in the sequence of troubleshooting abided in the actual problem processing. Because there are multiple types of faults whose troubleshooting methods are different, you will have a clear idea from the document, and conduct the comprehensive processing to faults by combining the relative commands and means in the process of actual troubleshooting. For the 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 and principles described in this document. In addition, the troubleshooting approaches of the new EFGS series of data boards are the same with the ET1 series. However, there are more approaches and convenient query commands, for example, through the GFP test frame, verify whether the basic configuration and service channel between VCTRUNK ports (verify whether the corresponding cross connection, channel binding and GFP protocol parameter are consistent) are enabled. Most of the following commands concerned are oriented to ET1 series of boards. To query the corresponding project and content of EFGS series of boards, only need to conduct the host command, not need to compare the status difference between the 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 the commands and suggestions, to continuously perfect, revise this document to get correct contents, thus helping us to guide our work and improve the satisfaction of the customer. The document summarizes the relatively typical cases in several years and combines with the basic acknowledge of Ethernet to analyze, to help engineers to deeply understand MSTP products for improving the maintenance skills.
2007-10-22
Page 6 of 57
Chapter 2 Background Knowledge

2.1 Ethernet Fundamentals
Appropriately understand the Ethernet knowledge to deeply understand the principles and implementation of MSTP series of products, thus broadening the ideas of networking, service configuration and troubleshooting. Ethernet is a kind of network technology, oriented to the nonconnecting and best-effort delivery. From the application perspective of MSTP products, the following key contents should be understood.
2.1.1 CSMA/CD
IEEE 802.3 defines the CSMA/CD (Carrier Sense Multiple Access with Collision Detection). CSMA/CD is very similar to the talk between people (that is, listen first and then speak. If there are many people talking, one person is allowed to speak at a time). The core implementation approach is to continuously monitor the communication medium, and delay signals and then transmit again after their collision, thus implementing the sharing of communication media and communication among many people. From CSMA/CD principles, we know that CSMA/CD-based Ethernet is a kind of half-duplex technology, which is implemented at the cost of signal collision and transmission again. Therefore, in case the communication requirements of the network reach a certain amount, the possibility of collision increases, and the corresponding network overall efficiency decreases. For the detailed introduction and calculation method of CSMA/CD efficiency, refer to LAN Technologies.
2.1.2 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 bridging can be implemented between Ethernets with different rates, which is helpful to increase 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 is transmitting if any, without viewing the busy or idle status of communication medium and without detecting collision. The full duplex is implemented based on the following aspects: 1. The port supports the full-duplex mode. 2. The communication medium is shared exclusively (point-to-point communication). The combination of rate and duplex mode can form multiple types of port working modes. To simplify the networking configuration and solve the port interconnection problem, the auto-negotiation technology invented: By handshake (pulse negotiation signal) of both parties, both parties can work in the highest level of mode supported by them. Now, the 10/100 M electrical
2007-10-22 Huawei secrets, no dispersion without permission Page 7 of 57
interface supports the rate and duplex mode negotiation, but the fiber Ethernet does not support this negotiation (only supports full-duplex). The auto-negotiation of GE is used for negotiation of flow control parameters. The following condition should be noted: The 10/100 M electrical interface A is in auto-sensing working mode, but the peer end B is in fixed working mode. A can judge the rate of B is 100 Mbps or 10 Mbps by its received clock signal, but B does not transmit or respond to the negotiation pulse signal, resulting in A fails to judge the duplex mode of B, therefore generally A can only work in half-duplex mode. If B is in half-duplex, the service is normal. If B is in full-duplex, then its full duplex VS As half-duplex. At the same time, if both ends are in transmitting status, there must be collision on the communication medium, resulting in packet loss (in full-duplex, collision is not detected and the collisional frame 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 port should be queried after linking, to avoid the condition of half-duplex VS full-duplex.
2.1.3 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, and through CRC (Cyclic Redundancy Check) the receiving end can check whether frame incurs error (bit error) during transmission. Discard all the error frames checked by CRC. 2. Extra-short frame The frames less than 64 bytes, which are deemed as residues caused by collision, and they must be discarded. 3. Extra-long frame The frames exceeding the maximum value permitted by field length, which all should be discarded. By default, the maximum frame size of ports of the MSTP series of products is 1522 bytes (which can be set). If the full-duplex VS half-duplex, the port receives the incomplete frames caused by a large amount of collision. The residues less than 64 bytes are deemed as extra-short frames, and should be discarded directly. Otherwise, conduct CRC check for the residues not less than 64 bytes, and the residues are deemed as CRC error frames caused by frame check sequence field error, and also should be discarded. 4. Alignment Byte alignment error, which seldom appears. Generally such error is caused by hardware fault or collision.
2.1.4 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 caused by buffer overflow, conduct the appropriate flow control.
For the CSMA/CD-based half-duplex Ethernet, the following two methods can be 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 flow control of full-duplex Ethernet is implemented in various equipment: When the congestion happens, the port transmits the specific flow control frame (PAUSE frame) to the peer end, which stops data transmission for a while upon receiving of flow control frame, to release the congestion load at the port. PAUSE frame is a standard Ethernet frame, whose type of domain has value 0x8808, and whose payload has the main content of slot time (indicating a period 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 frame to the peer end in case they are congested, but generally slot time has the fixed value, which is different based on the relative product or version. Different boards 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:
2.1.5 VLAN
For ET1V1 version, VLAN is used as the route flag during service convergence, that is, the convergence function of Ethernet service is implemented through configuration of VLAN route. In the process, the following requirements should be met: 1. Ethernet port of the center NE ET1 is set as the TAG attribute. 2. The broadband data communication equipment interconnected with the center 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 in other situation. For ET1V2 version, VLAN performs the isolation function, that is the port isolation is implemented in VLAN filtering table, in which the frame forwarding is then implemented through layer 2 switching.
2.1.6 Relationship Between Ethernet II and IEEE 802.3 Frames

In Ethernet frame Ethernet II, 2 bytes of Type domain is located after SA. IEEE 802.3 is the MAC/LAN description about CSMA/CD defined by IEEE. In 802.3 MAC frame, 2 bytes of Length domain is located after SA. Currently, Ethernet II type of frame is used frequently, and 802.3 frame is only used in a few protocols.
2.1.7 Type and Precautions to Deployment for the Current EFT/EGT Board
The EFT/EGT board is a 100M or gigabit Ethernet transparent transmission board, and its external MAC interface corresponds to its internal VCG port one by one without VLAN function. In service configuration, only need to set VCGs channel bound, whose granule is VC4/VC3/VC12, and set the working mode of the port to interconnect with series of boards and EFGS boards over GFP encapsulation protocol. During the interconnection and deployment of EFGS board, note that TAG attribute of VCTRUNK port of EFGS board should be set according to the EFGT access service.
2.1.8 Identifying the Multicast Feature and Manufacturerer Information of a MAC Address
MAC address has 48 bits, but it is usually represented as a 12-bit dotted decimal notation number. Example of MAC address: 00.e0.fc.39.80.34 MAC address is unique in the whole world, and it is managed and assigned by IEEE. Each address is composed of two parts vendor ID and sequence number, where the first 24-bit binary number represents the vendor ID, and the remaining 24 bits are assigned by manufactory itself. For example, the first 24 bits of Huaweis MAC are 00.e0.fc. In case all the 48 bits are 1, it indicates the address is a broadcasting address. In case the 8th bit is 1, it indicates the address is a multicast address.
2.1.9 Composition of a Data Communication System

Generally, a data communication system is composed of 4 parts: data, DTE (Data Terminal Equipments), DCE (Data Circuit-terminal Equipment) and communication link. These equipment cooperate with each other to implement the data communication between data terminals. The data communication technology focuses on the data format and transmission mode, which largely determines whether the communication is successful and how about the communication efficiency.
2.1.10 Concepts, Settings and Setting Principles of MTU and MRU

1. Concepts MTU: Maximum Transmission Units. MRU: Maximum Receive Unit. Their values are restricted by hardware. 2. Settings If a packet is received on the router interface, and whose length is larger than MTU value of a packet received on this interface, the packet is marked with non-fragmented and then discarded. An ICMP error packet will be returned and it notifies the packet initiator reason of discarding. The packet initiator will transmit a smaller packet. Through multiple times of above packet negotiation, the minimum Mtu value on a fixed path will be gotten. This process is called
Mtu Discovery. The host can determine the minimum MTU passing on the packet path through MTU Discovery. If both equipment are connected, but there is no MTU Discovery function and their MTU values are inconsistent, the packet may be discarded. Only if Mtu of both equipment is the minimum value of MRU of the peer end equipment, the communication is normal. Because some sites consider the network security problem and performance, they usually filter ICMP packets, resulting in abnormal running of Mtu Discovery and Web page cannot be opened and Internet cannot be accessed normally. 3. Setting principles
In the pure IP network, the following should be guaranteed: MTU value of path > the maximum user packet length. In the pure MPLS network without VPN service, the following should be guaranteed: MTU value of path > length of eleven layers of labels of the maximum user packet (4). For the layer 3 VPN service, the following should be guaranteed: MTU value of path > the maximum user packet + length of two layers of labels (8). For the layer 2 VPN service, the following should be guaranteed: MTU value of path > the maximum user packet length + length of two layers of labels (8) + length of twelve layers of frame headers (18).
2.1.11 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 in the range of 1 to 4095. 42ET1O/D has VLAN filtering table and layer 2 switching function, 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 in the range of 1 to 4095. 61ET1S has VLAN filtering table and layer 2 switching function, 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 in the 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 switching function, so it can configure VLAN IDs in the range of 0 to 4095.
2.1.12 Differenting a Single-Module Optical Interface from a Multiple-Mode Optical Interface on an SS42AIUA02
Differentiate by the optical interface location: Starting from the right, the 1st and 2nd optical interfaces are multiple-mode, and the 3rd and 4th optical interfaces are single-mode.
Differentiate by color: The opticial interfaces in black are multiple-mode, and the opticial interfaces in blue are single-mode. In addition, you can unplug a board and observe its laser module, if 1300 nm is marked on it, then the module is a single-mode optical interface.
2.1.13 Locating the Channel that Generated an ATM Alarm

For example: 14 LOS 0x0600ffb8 14 LCD 0x0600ffb8 14 OOF 0x0600ffb8 14 LCD 0x0700ffb8 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 and port4. Where, the corresponding physical port numbers are 0, 1, 4 and 5, and the corresponding physical port numbers of three buses at SDH side are 2, 3 and 6. From the above alarms queried, we can determine that the 4th optical interface on AIU board reports and receives no-light alarm, and No. 6 bus at SDH side reports LCD alarm. The above are alarm report definitions in AIUV1 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. critical major major major start start start start 2001-7-20 11:20:58 2001-7-20 11:20:58 2001-7-20 11:20:58 2001-7-20 11:20:58 None None None None
2.1.14 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 as current performance, 30-second performance and variable period performance. For example, set the current performance monitoring of the 1st Ethernet port with 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;
2007-10-22
Page 12 of 57
2.1.15 Setting Switching Time and Hold-Off Time of a VP Ring in the Case MSP and VP Ring Coexist
The first version of the AIU does not provide multiplex section protection, but the second version provides double-layer protection for multiplex section and VP Ring. Generally, we first start multiplex section protection, and then start VP Ring protection, to implement the layered protection. If the multiplex section protection is invalid, the AIU cannot receive ATM cell, and the board will report alarms such as LCD and VP-AIS. After a period of delay, VP Ring protection is started, and it selectively receives the standby path to recover ATM service. Because ATM alarm needs 3 seconds, the delay time should be longer than 3 seconds. In data setting specifications, it is required that the delay time of VPring 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 of multiplex section protection and recovery time of VP Ring protection. In data setting specifications, it is required that the recovery time of VPring protection switching is set as 12 minutes (12 minutes), and note that the recovery time of VPring protection switching in the command line is in the unit of minute.
2.1.16 Querying the Actual Working Mode of the 61ET1

When setting the working mode of Ethernet interface in interconnection, use a command line to query the result which is working mode set by the host. If the peer end or Metro equipment auto-negotiation, use ptp command to query the actual working Ethernet interface: Ethernet only the is set as mode of
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 from right 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 duplex mode and its link status is normal. Remarks: In 1.44 version and higher, the :ptp:bid,12,86,02 command can be directly used to query the actual working mode of all the network interfaces of the board.
2007-10-22
Page 13 of 57
2.1.17 Judging the Working Status of a Network Interface According to Its Indicators
There are two indicators on each network interface of an Ethernet board, and they are used to indicate the working status of the network interface. The upper indicator is link indicator (green), and the lower indicator is data indicator (yellow). The link indicator only indicates a connection has been established, and not indicate the communication is normal. If the link indicator is off, then generally the network cable is faulty or the working modes of Ethernet ports at both ends are unmatched. For example, if the mode at one end is set as 10 M, but the mode 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 on Ethernet interface. Note that the data indicator is also on under the following circumstances: The tag attributes at both interconnection ends are unmatched or Ethernet data is discarded caused by its error frame structure after the Ethernet port receives data.
2.1.18 Whether ETHLOS Alarm will Disappear After the Network Interface of the ET1 Board Loops Back
ETHLOS alarm will disappear if the ET1 board loops back in 100 M mode, but the alarm still exists if the ET1 board loops back in 10 M mode. The reason lies in that the chip loopback operation is conducted in different locations in 10 M and 100 M modes, resulting in the values of LINK bit in the register are different. 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, therefore there is no ETHLOS alarm. But in 10 M mode, LINK bit is still 0 during the loopback operation, so there is alarm. This problem is caused by hardware, which is only for knowing.
2.1.19 Use of Standard/Manufacturerer Network Cables

The data communication equipment can be divided into two categories: Terminal equipment and convergence equipment. The principles for network cable selection are: A crossover network cable is used for interconnection between both terminal equipment, such as interconnection between both PCs. A crossover network cable is used for interconnection of data interfaces between both convergence equipment, such as interconnection between HUB and L2 (a standard network cable is used for interconnection between the UPLINK interface and data interface). A standard network cable is used for interconnection between terminal equipment and convergence equipment, such as interconnection between PC and L2. The common terminal equipment contains PC, router and Ethernet board. The common convergence equipment contains HUB and L2.
2.1.20 Precautions to Setting the Working Mode of Ports of an EFGS Board

After the configuration of an interface board, the working mode configuration should be delivered after the board reports the interface board event, otherwise
the chip will be set as auto-negotiation. After init-all, delivery of the command used to configurate the interface and delivery of port working mode configuration may cause the port to be set as auto-negotiation. The auto-negotiation port and full-duplex port are negotiated to the half-duplex. It is recommended that you use :ethn-cfg-get-bdpara:bid,allport not use :ethn-cfg-get-workmode:bid,allport to query the actual working mode of the port after delivery of the configuration. The query result is the working mode of the configured port. After the problem appears, use :ethn-cfg-set-workmode to set the working mode of the port again.
2.1.21 Query Command of Actual Working Mode of Ports of a Data Attribute Board
Many Ethernet problems are caused by the working mode setting of the port. To locate 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 1 indicates the network interface is enabled, and 0 indicates disabled. The second byte 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 actual working modes), 1 indicates 10 M half duplex, 2 indicates 10 M full duplex, 3 indicates 100 M half duplex and 4 indicates 100 M full duplex.
2.1.22 Encapsulation Protocol of Each Data Attribute Version

I.
2007-10-22
ET1 V1 series - - - ML-PPP

Huawei secrets, no dispersion without permission Page 15 of 57
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.
2.1.23 Unshared Condition Between ET1 Inserted in Metro 3000 IU12 Slot and PQ1 Board Inserted in IUP
The IU12 and IUP slots of the Metro 3000 equipment share 4 buses. In case PQ1 is inserted in the IUP, the IU12 cannot share 4 and more of VC4 buses. If SS61ET1.2 and SS61ET1.3 share 4 VC4 buses, the configuration must be failed. If the SS61ET1.3REV0 board shares 2 VC4 buses, normally it can work with IUP PQ1. But the host does not differentiate 2VC4 from 4VC4, and both are deemed as 4VC4, therefore the SS61ET1 board cannot be inserted in IU12 and IUP slots with PQ1 simultaneously. This condition can be avoided by changing slots of the ET1 board.
2.1.24 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
2007-10-22
Page 16 of 57
2.1.25 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 Ethernet frame is fragmentized by the 64-byte length, and then the frame header information, which used in the peer-end reassembly, of ML-PPP is added before each fragment. At last, the fragment is directly placed in VC12 payload for transmission. Therefore, after 2 M transition, the payload reaches the peer end without change, and the peer end equipment reassembles the information of each fragment to implement the communication.
2.1.26 2 M Service Transition Failure in 2 M Tributary Cards of EFGS Series of Boards

Although the encapsulation granule of the EFGS board is also VC12, but it adopts the Ethernet protocol LAPS or GFP, which are associated with the information between fragments or Ethernet frames based on the virtual concatenation information. The virtual concatenation adopts H4 or K4 byte, and its overhead is terminated after 2 M transition, and then the information reaches the peer end, resulting in failure of reassembly, thus the communication fails to be implemented.
2.1.27 Meaning of PING Command Parameters

Common parameters: -t Ctrl+C to stop -l size -n count send packages ceaselessly, and press
set the length of the packages to be sent times, for which packages are to be sent -n 10 means sending packages of 500
Example: Ping 129.9.0.4 -l 500 bytes to 129.9.0.4 for 10 times.
2.1.28 Meaning of RMON Ethernet Alarms

Alarm event identifier DropOv DropUd RxBadOctOv RxBadOctUd TxBadOctOv TxBadOctUd ColOv ColUd AligErrOv AligErrUd FCSErrOv FCSErrUd LateColOv LateColUd Alarm ID 0x129 0x12a 0x12b 0x12c 0x12d 0x12e 0x12f 0x130 0x131 0x132 0x133 0x134 0x135 0x136 Alarm event name Times for packet loss is higher than the upper-bound alarm value. Times for packet loss is lower than the lower-bound alarm value. Bad packet bytes received are higher than the upper-bound alarm value. Bad packet bytes received are lower than the lower-bound alarm value. Bad packet bytes transmitted are higher than the upper-bound alarm value. Bad packet bytes transmitted are lower than the lower-bound alarm value. Number of conflicts detected is higher than the upper-bound alarm value. Number of conflicts detected is lower than the lower-bound alarm value. Number of alignment errors is higher than the upper-bound alarm value. Number of alignment errors is lower than the lower-bound alarm value. Number of checksum errors is higher than the upper-bound alarm value. Number of checksum errors is lower than the lower-bound alarm value. Times for detected collisions in the timeslot time after sending is higher than the upper-bound alarm value. Times for detected collisions in the timeslot time after sending is lower than the lower-bound alarm value. Page 17 of 57
2007-10-22
Troubleshooting Guide to Ethernet Data Boards Alarm event identifier ExcColOv ExcColUd DefTxOv DefTxUd CarErrOv CarErrUd Alarm ID 0x137 0x138 0x139 0x13a 0x13b 0x13c
Alarm event name Number of frames failed to be sent due to continuous collisions is higher than the upper-bound alarm value. Number of frames failed to be sent due to continuous collisions is lower than the lower-bound alarm value. Number of frames to be deferred transmission is higher than the upper-bound alarm value. Number of frames to be deferred transmission is lower than the lower-bound alarm value. Number of carrier errors detected is higher than the upper-bound alarm value. Number of carrier errors detected is lower than the lower-bound alarm value.
2.1.29
Auto-Negotiation Function of 10 M/100 M Network Interface

Because Ethernet rates and types of duplex are diversified, the auto-negotiation mechanism is introduced to pare down the failed interconnection and complexity of manual configuration. The auto-negotiation commonly mentioned refers to the rate and duplex auto-negotiation. The interconnected Ethernet interfaces supported auto-negotiation adopt a kind of standard FLP (for fast Ethernet) or NLP (for Ethernet) to set their working modes as the highest rate supported by both interfaces through a negotiation mechanism. For example, if both interfaces support the auto-negotiation, and their highest rates are all 100 M full-duplex, then the negotiation result should 100 M full-duplex. If both interfaces support the auto-negotiation, but the highest rate at one end is 100 M full-duplex, and the rate at the other end is 100 M half-duplex, then the negotiation result should be 100 M half-duplex. The same is true of 10 M full/half-duplex. The auto-negotiation mechanism can be adopted to ensure the consistency of rates and duplex modes of both interfaces and reach the highest rate supported by both interfaces, thus ensuring the transmission efficiency.
2.1.30 Not Using Network Cables Whose Both Ends are One-to-One Correspondence to Transmit 100 M Service
The standard cable sequence of standard network cables is as follows: Yellow white, yellow, green white, blue, blue white, green, brown white and brown, and both ends of the cables are consistent. Such network cables are capable of 10 M/100 M line connection. Even though the cable sequence of network cables are consistent at both ends, the network cables are only capable of 10 M line connection. If 100 M ports are connected with 10 M network cables, packet collision will incur, resulting in unsteady connection and disconnection, even complete disconnection.
2.1.31 Introduction to 10Base5, 10Base2 and 10Base-T Cables

The 10Base5 thick coax cable adopts the plug-in connector, indicating that the working rate is 10 Mb/s, the baseband signals are adopted, the longest segment length supported is 500 m, and the maximum number of segments is 100. The 10Base5 thick coax cable has thick core diameter, and is not bent easily, so it is installed very inconveniently. The 10Base2 thin coaxial cable adopts the industry standard BNC connectors to form a T type of socket with flexibility and high reliability, and its price is
relatively cheap. But it can only be used in the range of 200 meters, and only 30 computers 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 its price is cheap. A concentrator, several 10Base-T cables and several computers can form a practical small-sized LAN. The 10Base-T has the following disadvantage: The longest valid transmission distance between it and concentrator is 100 m. Even though it is a high-quality C5 cable, the longest distance is only 150 m.
2.1.32 Explanation of Auto-Negotiation Function of Gigabit Ethernet

The IEEE 802.3z standard defines the relative contents of Gigabit Ethernet. The Gigabit Ethernet has auto-negotiation function, which only contains negotiation of half-duplex or full-duplex flow control and determines whether control frame is supported. The rate cannot be determined by negotiation with low-speed Ethernet. The working mode negotiation is related to optical modules of different factories. To guarantee the successful interconnection, set to the same at both ends, that is auto-negotiation to auto-negotiation, and full duplex to full duplex. Frequently, the unsuccessful interconnection is caused by inconsistency between auto-negotiation at one end and 1000MFULL at the other on the network.
2.1.33 Introduction to PSTN, ISDN, DDN, X.25 Network and Frame Relay Network
PSTN (Public Switched Telephone Network) may be a public narrowband network 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 network based on point-to-point connection. X.25 network is an international standard WAN, and it is the unique available WAN technology in many regions, especially in Europe. Its built-in error correction, flow control as well as packet loss and re-transmission mechanisms provides 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 on the way has to reassembly the packets to decrease the data throughout, so the packet delay is large. Obviously, X.25 is inapplicable to the channel with high transmission quality. Frame relay is a kind of widely used service, which adopts E-1 circuit, and whose rate changes in the range of 64 K to 2 M. Because the rate is high, error detection decreases, and simple signaling in the current MAN connection can be used. Delay of medium nodes is much smaller than X.25 network. The length of frame relay is variable, so conveniently applies for any packet or frame in LAN, to provide transparency for users. Frame relay is liable to be affected by network congestion, and it cannot specially guarantee the time-sensitive real time communication. In case the line is interrupted by noise, it will re-transmit packets.
2.1.34 Meaning and Principle of Flow Control

Flow control is a kind of congestion avoidance mechanism, and it can be implemented through PAUSE frame if Ethernet is in full-duplex working mode. Ethernet flow control mechanism is as follows: If the receiving queues of an Ethernet interface are congested (data in ingress buffer exceeds a specific domain value), and the network interface supports PAUSE flow control, then the network interface transmits PAUSE frame, whose pause-time value is N (0<N<=65535), to outside. Ethernet interface at the peer end receives the PAUSE frame and it supports PAUSE flow control, data transmission will be stopped in time N (in the unit of time of transmitting 512-bit data). Thus, packet loss is avoided because of non-congestion on the receiving port. If the receiving port is not congested (data in ingress buffer is lower than a specific domain value), but pause-time is not ended, the port will transmit a PAUSE frame with 0 pause-time and notify the peer end to begin to transmit data. The format of PAUSE frame is defined in 802.3 31B: The destination address is a multicast address 01-80-C2-00-00-01; the source address is MAC address of source port; type/length domain is 88-08, indicating MAC control frame; 2-byte MAC operation control code is 00-01, indicating PAUSE frame; 2-byte pause time indicates the time within which the peer end port pauses to transmit, and 0 indicates the port paused transmission can resume data transmission.
Destination MAC address
Source MAC address
Type
Operation control code
Pause time
Modes of flow control contain: Asymmetric PAUSE, symmetric PAUSE as well as both asymmetric and symmetric PAUSE. Where, asymmetric PAUSE indicates PAUSE frame can be transmitted in case of this port congestion, but PAUSE received cannot be processed (discarded or processed as a common multicast frame); symmetric PAUSE indicates the port can receive PAUSE and process PAUSE frame received. Both asymmetric and symmetric PAUSE mode is only applicable to auto-negotiation of flow control. Flow control of Ethernet interface can be set manually or automatically through the auto-negotiation mechanism of flow control.
2.1.35 Meaning and Principle of LPT Function

LPT (Link Status Pass-through) indicates the downstream VC-12 channel closes the corresponding IP port after receiving TU-AIS alarm, and the downstream router switches over to other router upon detection of failure of port LINK. The switching condition of LPT function is TU-AIS alarm detection, so the priority of LPT switching is lower than multiplex section/SNCP/channel protection, to avoid unnecessary service interruption.
2007-10-22
Page 20 of 57
2.1.36 Two Main Functions of LCAS

LCAS (Link Capacity Adjustment Scheme) is an expansion of virtual concatenation technology. The following two problems can be solved through LCAS: 1. Dynamically adjust (add, delete or change) service bandwidth without effect on the availability of original service. 2. If there are invalid physical channels in virtual concatenation, LCAS will shield these channels, but other channels can still be used for service transmission, thus avoiding service interruption caused by invalidation of a single physical channel.
2.2 Knowledge Concerning the Ethernet Feature Board

2.2.1 Encapsulation and Fragmentation
Data services, featuring bursting and changed length, are thus quite different from SDH frames that are synchronization critical. So a proper data link-layer adaptation protocol is needed for Ethernet data encapsulation including data buffer, queue scheduling and so on to map frames from Ethernet to SDH VC. Processing mode of ET1-series boards: The sending end first splits an Ethernet frame into N 64-byte fragments, then through ML-PPP encapsulates all the fragments and finally maps them in turn to the bound VC12s in the polling mode, one fragment to one VC12. The receiving end first recovers all the N fragments from the VC12s and then combines them into one integral Ethernet frame. The processing mode of EGT/EMS/EFS-series boards: The sending end does not fragment the Ethernet frame, but encapsulates the whole Ethernet frame through LAPS/GFP, and then maps the byte streams in turn to the bound VCs in the polling manner. The receiving end first extracts data from the VCs and then decapsulates them to restore the integral Ethernet frame. Question: How does the board respond when bit error codes appear on the SDH side during data transmission? Answer: Any encapsulation protocol will add CRC during encapsulation so that the data, when being restored to an integral Ethernet frame at the receiving end, will experience CRC. If errors are found, the error data will be directly discarded and no error Ethernet frame will be sent.
2.2.2 Common Board Performance Indices

1. Throughput: The maximum rate in case of no frame lost, the most direct indicator of bandwidth 2. Latency: Delay introduced in the equipment processing phase 3. Frame loss rate: The ratio of the data frames that fail to be forwarded due to insufficient network resources to the total data frames on a stable network, which plus throughput is equal to 100% in theory
2007-10-22
Page 21 of 57
4. Back-to-back: The allowed maximum length of the data frames successively appearing at the minimum legal frame interval in case of no frame lost during transmission, 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 user not measure back-to-back of a board. During fault location, the impact of all these indices on service is certainly worth consideration. Moreover the long-term stability test can help discern the reliability degree of a system that operates under a certain load for long. In the case that the user reports there are a few packets lost, you can judge whether MSTP product fault is accountable finally through this test. On the whole, the MSTP product provides link-layer and physical-layer functions, 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 and not 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 in throughput test? Answer: The interFrameGap, leading code and so on are not transmitted through SDH, but re-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 monitor functions. The board with RMON feature can provide performance threshold-crossing alarms. Performance events (RMON) are very helpful in daily maintenance and fault location. Among a multitudes of performance events, you need to attach great importance to the following: 1. Various types of error packets a. CRC error and extra-short frame: As described in Section 2.3, first check if port 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 more likely to have problems). c. Sent error packets: Processing capacity bottleneck of the local FIFO and hardware fault are generally the reasons. In presence of many error packets appearing 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 the user to adjust service load or perform traffic shaping. 3. Collision and back-off
2007-10-22
Page 22 of 57
Collision and back-off events show that the local port works in the half-duplex mode. You are recommended to query if the peer port also works in the half-duplex mode. It is unnecessary to pay much attention to other performance events during daily maintenance.
2.2.4 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, resort to the following commands for the reason. Query a logically installed interface board (ET1 command)
Name Function Command level Target user Version Input format Input parameter cfg-get-subboard Query a logically installed interface board. Query level Internal/Customer service/Customer 4.05.04.10 and later versions Two parameters, repeated parameters Parameter location 1 2 Output format Parameter value The No. of a processing board, which can be 0, 1, 2, 3, 4, 5, 6, 9, 10, 11, 12, 13 or 14 The No. of an interface board, which can be 0, 1 or 2. The value 0 indicates all interface boards of a processing board are to be queried.
SUB BOARDS BID SUBID ATTRIBUTE Board slot No. sub-board slot No. interface board type In absence of records, error codes will be output. :cfg-get-subboard:1,1
Example Precautions Remarks
If the interface board type is shown null in the query result, it indicates no interface board is installed.
Query a physically installed interface board (ET1 command)

Name Function Command level Target user Version Input format Input parameter cfg-get-physubboard Query a physically installed interface board. Query level Internal/Customer service/Customer 4.05.04.10 and later versions Two parameters, repeated parameters Parameter location Parameter value
2007-10-22
Page 23 of 57
Troubleshooting Guide to Ethernet Data Boards 1 2 Output format
The No. of a processing board, which can be 0, 1, 2, 3, 4, 5, 6, 9, 10, 11, 12, 13 or 14 The No. of an interface board, which can be 0, 1 or 2. The value 0 indicates all interface boards of a processing board are to be queried.
SUB BOARDS BID SUBID ATTRIBUTE Board slot No. sub-board slot No. interface board type In absence of records, error codes will be output. :cfg-get-physubboard:1,1
Example Precautions Remarks
If the interface board type is shown null in the query result, it indicates no interface board is installed.
You may use this command: :ptp:bid,12,28,2,0 Function: Configure interface board type. Format: para[0]: Slot No.: The value 1 indicates interface board slot A, 2 indicates interface board slot B and 0 indicates all boards slots. para[1]: Interface board code. 0x00 indicates the interface board slot holds no board. There are interface boards of types 03, 04, 05, 06 and 07 currently. 12 Command format; para[1]: Query command type: The value 1 indicates logical query and 2 indicates the physical interface board installed is to be queried. para[2]: Query board slot.: The value 1 indicates board slot A, 2 indicates board slot B and 0 indicates all board slots. Return; para[1]: Query command type: The value 1 indicates logical query and 2 indicates 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 are listed as below: Code 0 0x03 3100 0x04 Interface board type No interface board configured SS61ETF4 SS61EFF4 (4-port electrical interface board) 3100 2500+ 2500+ 2500+
Page 24 of 57
(4-port optical interface board) (8-port optical interface board) (4-port optical interface board) (8-port electrical interface board)
0x05 SS61EMF801 0x06 SS61EMF802
0x07 SS61EMT8
2007-10-22
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 supports currently, 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 identify GFP frames. 2) As the received GFP frame has a payload FCS field, but the IDLE frame has no such field, service data packets must be sent to generate an FCS_ERR alarm. 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 protection switching. Since GFP parameters of two sides are generally consistent, bit error code is the principal reason for FCS_ERR alarms. 2. When is an FCS_ERR alarm generated in case of inconsistent GFP parameters on two sides? Under the following circumstances, an FCS_ERR alarm is generated in case of inconsistent GFP parameters on two sides: 1) The peer GFP parameter FCS is set to FCS32, because only in this case the local 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 decide whether to perform FCS check according to the PFI flag in the type field in the received GFP frame. Therefore, the peer GFP parameter decides whether to perform FCS check locally. Local FCS check will be done only when the peer GFP parameter is set to FCS32. An FCS_ERR is likely to appear only when FCS check is performed. 2) The scramble parameter of one side is set to x43 and that of the other side is disable. If the peer FCS option is set to FCS32, for example, there will be an FCS_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 to enable on the other side, services cannot be transmitted successfully and thus there will be no FCS_ERR alarm. 4) Suppose the GFP parameter ENDIAN-MODE is set to big on one side and to little on the other side. If the peer FCS is set to FCS32, there will FCS_ERR alarms on the local side; otherwise, there will be no such alarms.
FCS_ERR(0XF857)
Interface name Requirement description Concerned board/module Code Level Parameter 2007-10-22 FCS check error alarm In presence of FCS check error, this alarm needs to be reported. EGS EFS 0XF857 3 Parameter location Parameter description Huawei secrets, no dispersion without permission Page 25 of 57
Troubleshooting Guide to Ethernet Data Boards para[0] Logical port No., which is always 1 para[1-2]VC-TRUNK No. FCS check error No No T2000V1R6 No difference None None None 2003-03-26 Zhou Jianwei
Alarm source Active suppression Passive suppression NMS version supported Host version supported Board version supported Difference between versions References Remarks Revision description Definition date Person-in-charge
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 2004-09-03 02:03:25 2004-09-03 02:03:26 0x01ff57ff 883 13 VCDELAYTL critical 2004-09-03 02:03:26 2004-09-03 02:03:27 0x01ff32ff 884 13 ILL_MFI_VC3 major 2004-09-03 02:03:27 2004-09-03 02:03:28 0x01ff61ff end end end
FCS_ERR and VCDELAYTL are VCTRUNK-type alarms. 01 in the parameter 0x01ff57ff 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 optical port 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 TIME BID EID SEVERITY PARA1 PARA2 PARA3 PARA4 PARA5 0x01 0xff CR 0xff STATE end
1629 2 FCS_ERR 2004-10-29 16:21:40 0x01 0000
PARA1 indicates a logical port No., and PARA2-PARA3 indicates a VC-TRUNK No. 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 para4 denote alarm codes. The alarm of the efgs board of the 5.0 platform-based product has five parameters. The parameter para1 is logical port No. and para2 para3 is vctrunk No. or channel No. On the 5.0 platform, 0xff, instead of para4 and para5, is used to display alarm code.
2007-10-22
Page 26 of 57
Chapter 3 Usage Description of Test Frame FunctionsFull Service Flow Test for the EFGS Board
3.1 Introductions to Functions
There are two types f test frames on the EFGS board: GFP management frame used to verify interoperability between VCTRUNK ports, custom MAC frame sent by an IP port or a VCTRUNK port to the outside.
Management frame
Figure 1 Verification through a GFP management frame
Custom MAC frame
Figure 2 Sending direction of a custom MAC frame
Custom MAC frame
Figure 3 Verification path of a custom MAC frame
3.2 Using the Test Frame

3.2.1 GFP Management Test Frame
The GFP management test frame can be used to verify the configuration of the VCTRUNK between boards, namely, SDH service configuration and VCTRUNK channel binding configuration.
2007-10-22
Page 27 of 57
3.2.2 Verification Procedure

1. Issue service configuration, check for any obvious configuration problems by eyes. 2. Issue the command to enable the GFP management test frame.
Name Function Version Input format Input parameter ethn-cfg-set-testen Set sending parameters for the test frame. Supporting the host version of the EFGS board : ethn-cfg-set-testen:bid,vctrunk,enable,direction,number; parameters number = 5, parameter block repeated & parameter repeated Parameter Parameter value Parameter location repeated or not 1 Slot No. MML repeated 2 VC-Trunk: MML repeated vctrunk1-vctrunkM: Indicates VC-Trunk 3 Enable flag: 2 = Continue, 1 = Burst, 0 = Disable 4 Sending direction: 0 = SDH direction, valid only when enabled 5 Number of sent test packets: 1-255, valid only when the enable flag is set to 1 = Burst. Success or error information is returned. : ethn-cfg-set-testen:1,vctrunk2,0,0,89 The database is not saved, and board configuration is directly issued. At present, the configuration of sending direction is not supported.
Output format Example Precautions
In normal cases, use: :ethn-cfg-set-testen:bid,vctrunkport,1,0,1;//Send a packet to the SDH direction in the burst manner. 3. Query test results In presence correct service configuration, the following information is returned under the Navigator: ETH TEST COUNT EVENT: BOARD-ID END-FLAG Bid PORT-ID vctrunk1 1 COUNT-2 0 COUNT-3 1 COUNT-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, and COUNT-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 end receives the reply frames in the same number as the sent frames, the inter-board SDH service configuration and VCTRUNK configuration must be correct. For the later developed host software, COUNT-1, COUNT-2 and COUNT-3 are modified to TOTAL-SEND, RESPOND-RECV and NORMAL-RECV. In addition, you can use :ethn-cfg-get-testcount:bid,vctrunkport; to query the test frame counter.
2007-10-22
Page 28 of 57
3.3 Custom MAC Frame

3.3.1 Command Line Description
1. Set the contents of custom MAC frame
Name Version Input format Input parameter ethn-cfg-set-testpktpara All host versions supporting the EFGS board :ethn-cfg-set-testpktpara:bid,vctrunk,length,testtype,datatype,dstmac,srcmac,dstip,srcip,vlanid; number of parameters=10, parameter block repeat & parameter repeat Parameter Parameter value location 1 Slot No.: 1-20 2 Port No.: ip1 ~ ipN: Indicates the Ethernet port. vctrunk1 ~ vctrunkM: Indicates the VC-Trunk. 3 Test packet length (bytes): In the range of 64 ~ MAX_PORT_MTU; default value = 64 MAX_PORT_MTU: Customized for the Ethernet port and fixed to 9600 for the VCTRUNK. 4 Test packet type: 1 = Custom, 2 = IP packet; default value = Custom 5 Test packet data type: (default value = 4) 1 = transmitted data fixed to AA 2 = transmitted data fixed to 55 3 = transmitted data fixed to FF 4 = transmitted data fixed to 00 5 = 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-Fs 7 Source MAC address: Defaults to all-Fs 8 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) Success is returned or error information is given. :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; Preconditions for executing this command: 1. The according board has been installed on the slot.
Parameter repeated or not MML repeated MML repeated
Output format Example Remarks
2. Send the custom MAC frame

Name Version Input format Input parameter ethn-cfg-set-testpkten All host versions supporting the EFGS board : ethn-cfg-set-testpkten:bid,vctrunk,number; number of parameters=3, parameter block repeat & parameter repeat Parameter Parameter value Parameter location repeated or not 1 Slot No.: 1-20 MML repeated 2 Port No.: ip1 ~ ipN: Indicates the Ethernet port. MML repeated vctrunk1 ~ vctrunkM: Indicates the VC-Trunk. 3 Number of test packets transmitted: 0 = Not transmit (Stop), 1~0xFFFE = Number of packets transmitted (Burst), 0xFFFF = Transmit without limit (Continue) Success is returned or error information is given. :ethn-cfg-set-testpkten:1,vctrunk1,500; Set the number of test packets transmitted from the vctrunk1 in slot 1 to 500. Preconditions for executing this command:
Output format Example Remarks

2007-10-22
1. The according board has been installed on the slot.
3.3.2 Test Procedure

1. Check service configurations for any obvious problems, and then issue the configrations. 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 10 default 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 this increase 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, 0x0a and 0x0280 respectively.
3.3.3 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 boards service settings. 2. In viewing the performance count of the peer NE port, you shall decide what items to check based on the MAC frame to be sent. 3. In sending a custom MAC frame, you can (if possible) use a portable computer 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 be connected to NE2s port MAC1.
Chapter 4 Fault Location

What data to be queried in case of failure is always a difficult point in maintaining the Ethernet board. The following summarizes some common location methods, query commands and their description to help future maintenance.
Similar to the SDH fault location idea, the Ethernet fault location also complies with the principle of ExternalInternal, SoftwareHardware, BoardSystem. The technical methods (such as performance event, loop and test frame) should be used for the planed and stepped location in combination with tool software and test meters. It is necessary to locate the fault preliminarily to exclude the problem at the SDH layer by querying relevant alarms and performances. And then, turn to locate the problem at the Ethernet layer. For the fault location of Ethernet services, check relevant alarms to the ET1 board at first, focusing on some lower-order alarms such as BIP-EXEC, TU-LOP and 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 connected router/Ethernet switch for any errors. It is difficult to perform this location and there 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 common commands relevant to the loop. It is important to ask help from the data
maintenance personnel of the customer, and use the method of PING+loop. For example, ping the IP address of the remote router/switch
through the ET1 network interface. If the operation succeeds, it indicates that there is no problem basically at the local side. It is recommended to adopt the following format:
ping xxx.xxx.xxx.xxx l 1000 t

l 1000 indicates the packet length is 1000 bytes, and -t indicates persistent ping operation. Try the ping operation with multiple packet lengths and multiple ping windows. The successful ping operation cannot exclude the problem of the Metro equipment completely, because the ping operation can also succeed with small traffic in case the port works in faulty mode. It just proves that the Ethernet link is well configured and there is no problem at the SDH layer. At first, it is necessary to check and confirm there is no problem in the configuration and channel at the SDH layer. And then, focus on the Ethernet data layer to locate problems. Let us see the common fault types. Generally, the Ethernet involves two fault types:
Fault symptom Possible fault causes 1 2
The link is completely disconnected. There is persistent packet loss on the link.
Ethernet link completely disconnected Persistent packet loss on the link
The fault causes may be:
The setting of TAG attribute (TAG/UNTAG) of the port is changed. The physical layer fails. Specifically, the real port works in faulty mode, some parameters of the port are abnormal, the interface board fails,
Large traffic leads to insufficient configuration bandwidth. The bandwidth is sufficient, but there are large service bursts.
Page 31 of 57
2007-10-22
Fault symptom Possible fault causes
Ethernet link completely disconnected
Persistent packet loss on the link
3 4 5
or the register of the physical layer is arbitrarily rewritten. The network cables or fiber optics fail. The data of Ethernet static routes is lost. In case of NE pointer justification, BIP-OVER and TU-LOP are reported from some channels of ET1, and the service is interrupted. Board replacement or reset can only transfer the faulty channel, but not solve the problem completely. The board hardware fails. A great deal of packet loss causes service interruption. Refer to the processing of the second fault type. The current spanning tree is based on user. If there are more than one MP connection at two stations, VLAN isolation only may cause broadcast storm of BPDU packets. Huawei equipment has only one MAC address learning table, and all the users and VLANs share it. Because the layer 3 equipment uses its own MAC address to forward packets, be sure not to connect more than one port of the layer 3 equipment that has only one MAC address. (It cannot be avoided in both user and VLAN isolations because Huawei equipment has only one MAC learning table) Transmitting/receiving excessive BPDU packets may lead to resetting. ETH-LOS is reported during normal running process due to coupling interference, and the service is interrupted. It may be automatically restored or not. ETH-LOS may be reported transiently at the interval of 5 seconds (error report).
When there is too large service traffic, the remote equipment does not respond to the flow control. The Maximum Transmission Unit (MTU) set for the board is less than the real transmission packet length of the equipment. The port mode does not match that of the remote equipment, thus the equipment works in abnormal status. The network cables or fiber optics fail. When the Ethernet service packet lengths of two directions keep too large difference for a long time, or all the packet lengths are short bytes (64-128 bytes), it may cause large ET1 performance decrease and packet loss. The board hardware fails.
6 7
10 11
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 3100 currently.
4.1 Locating the Problems of Completely Interrupted Ethernet Links

For the failure of completely interrupted links, the specific symptoms include: connecting router and switch receiving no packets, service completely interrupted, and failed ping operation to the remote equipment. The following items should be checked:
2007-10-22
Page 32 of 57
4.1.1 TAG Attribute (TAG/UNTAG) Setting of the Port Changed

This fault occurs with large probability in case of software upgrade and board reset. For example, there is a bug in the 4.5.3.40 host version of the 2500+. The host version defaults the ET1 MP port attribute to UNTAG, while the board defaults it to TAG. Finding that UNTAG is set (default attribute) when issuing the configuration, the host will not issue it to the board. When resetting, the board defaults to the TAG attribute. Thus the service is interrupted. The host query commands include: Querying TAG attribute of the Ethernet port (ET1 command)
Name Format Authority Description Parameter Serial No. 1
:cfg-get-ethtag:3; Note: Query the TAG setting of board 3.
cfg-get-ethtag Location definition; number of parameters = 1 Query level
Parameter meaning Board ID
Parameter value 1-4; 11-14; 0 indicates to query all boards.
Remarks
Example
Querying TAG attribute of the Ethernet port (ET1S command)

Name Function Command level Open range Version Input format Input parameter eth-cfg-get-tag Query TAG attribute of the Ethernet port Query level Internal level/customer service level/user level 4.05.04.10 and above versions Location definition. Number of parameters = 1; repeatability = unrepeatable Parameter location 1 Output format Parameter value Actual board ID: 0,1,2,3,4,11,12,13,14; 0 indicates all boards.
TAG DEFINE Board-id port-id tag-state Board ID; port ID; tag status
Why 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 the VLAN frame structure. Format: CHAR[2]; CHAR[0]: Indicates the port ID, in the range of 0 to 8. 0 indicates all ports, 1-8 indicate physical network ports 1-8, and 0x81-0x90 (bit 7 is 1) indicate binding channels 1-16.
char[1]: Its value is 0 or 1. 0 indicates non-VLAN frame structure, and 1 indicates VLAN frame structure. The default value is 1. Query whether the actual port attribute of the board is consistent with that set by the host NMS. Two returned parameters: para[1] is the port ID, and para[2] is the attribute. 0 indicates UNTAG and 1 indicates TAG. Is the actual TAG attribute of the port consistent with the one you want?
4.1.2 Faulty Working Mode of the Port

The physical layer fails. Specifically, the real port works in faulty mode, some parameters of the port are abnormal, the interface board fails, or the register of the physical layer is arbitrarily rewritten. This fault also occurs with large probability. It should be located by querying relevant register at the physical layer. The specific query commands include: Querying the enabled status and working mode of the Ethernet port (ET1 command)
Name Format Authority Description Parameter Serial No. 1 Example Parameter meaning Board ID Parameter value Actual board ID: 1-4; 11-14; 0 indicates all boards. Remarks cfg-get-ethport Location definition; number of parameters = 1 Setting level
: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 Function Command level Open range Version Input format Input parameter eth-cfg-get-workmode Query the working mode of the port. Query level Internal level/customer service level/user level 4.05.04.10 and above versions Location definition. Number of parameters = 1; repeatability = unrepeatable Parameter location 1 Output format Parameter value Actual board ID: 0, 1, 2, 3, 4, 5, 6, 9, 10, 11, 12, 13, 14; 0 indicates all boards.
WORK MODE DEFINE Board-id port-id work-mode Board ID; port ID; working mode :eth-cfg-get-workmode:2;
For example:
Of course, the NMS is mostly used to query relevant attributes.
2007-10-22
Page 34 of 57
In addition, the ET1V2 featured board provides a host command for querying the actual port status of the board.
Name Function Command level Open range Version Input format Input parameter eth-cfg-get-portattrib Query all attributes of the Ethernet port Query level Internal level/customer service level/user level 4.05.04.10 and above versions Location definition. Number of parameters = 2; repeatability = unrepeatable Parameter location 1 2 Output format Parameter value Actual board ID: 0, 1, 2, 3, 4, 11, 12, 13, 14; 0 indicates all boards. Port ID: allport indicates all ports; ip1-ip8 indicate physical network ports ip1-ip8; mp1-mp16 indicate MP ports MP1-MP16.
PORT ATTRIBLE DEFINE Board-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 ID Priority mac-loop-mode phy-loop-mode flowcontrol-state VLAN priority; MAC loop; physical loop; flow control status :eth-cfg-get-portattrib:2,ip2;
Example
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 Ethernet port (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 the control logic of the board from the host (compare it with the query results of the host 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 to 4. 0 indicates auto-negotiation, 1 indicates 10 M half-duplex, 2 indicates 10 M full-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 the board, that is, the actual working mode of the port. Without parameter 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 interpreted respectively as follows: #590338:ptp:0d,12,86,0
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 04 indicates 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 04 indicates whether the negotiation succeeds (not disabled port), and 04 indicates 100 M full-duplex. It is different from the description in the document. The board software code indicates the register showing whether the negotiation succeeds. In case of auto-negotiation, 1 represents successful negotiation and 0 represents other status. While this byte indicates the enabled status in the document. :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 actual working mode of the port (generally it is recommended to use 86 command above). :ptp:bid,ce,0,port-1,1 :ptp:bid,ce,0,port-1,2 :ptp:bid,ce,0,port-1,3 :ptp:bid,ce,0,port-1,4 :ptp:bid,ce,0,port-1,5 :ptp:bid,ce,0,port-1,6 :ptp:bid,ce,0,port-1,10 :ptp:bid,ce,0,port-1,11 :ptp:bid,ce,0,port-1,12 :ptp:bid,ce,0,port-1,13 :ptp:bid,ce,0,port-1,14 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 actual working settings of the board can be queried such as working mode, port enabled status, and link status. For the specific values, refer to ET1 Physical Layer Register Description. For example, use the most common query method for the actual working mode of the board: :ptp:bid,ce,0,port-1,14 //(port-1 indicates port ID minus 1; 1 for port 2, 2 for port 3) 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 is 0011,1000,1100,1010.
2007-10-22
Page 36 of 57
Bits 4 and 5 from left to right respectively indicate the current duplex mode and rate. For bit 4, 1 indicates full-duplex and 0 indicates half-duplex. For bit 5, 1 indicates 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 link status. Note: Counted from right to left, 38c8 contains 16 digits of 0, 1, , 15 (the first digit is bit 0 and the 16th digit is bit 15). Bits 11, 12 and 13 indicate the working mode of the port (red part in 0011100011001000).
4.1.3 Failed Network Cables or Fiber Optics

It is easier to locate this problem. At first, check the LINK indicator (Green) of the Ethernet interface connecting with the network cable on the ET1 board. If it is not on, the network cable may fail or the crossover cable and public network cable are mixed (Note that the indicator of the optical interface board is located inside the interface board). At the same time, check the other indicator (Yellow) of the interface. On indicates there is data receiving/transmitting, and off indicates there is not. In addition, query the real-time Ethernet performance. If there are a lot of error packets such as CRC errors, the network cables or fiber optics may have problems after the working mode fault of the port is excluded.
4.1.4 VC Channel Binding

Name Function Command level Open range Version Input format Input parameter eth-cfg-get-mp Query the VC channel binding. Query level Internal level/customer service level/user level 4.05.04.10 and above versions Location definition; number of parameters = 1; repeatability = unrepeatable Parameter location 1 Output format Parameter value Actual board ID: 0, 1, 2, 3, 4, 5, 6, 9, 10, 11, 12, 13, 14; 0 indicates all boards.
VCTrunk(MP) Details: Bid Index PathNum Path Board ID; MP channel; number of channels; channel list :eth-cfg-get-mp:0;
Example
0x80: MBCMD-MP (in coordination with 12 command) Function: Configure mapping from the binding channel to VC12 channel (in coordination with 12 command to query the actual channel binding status of vctrunk). Format: CHAR[ ];
2007-10-22
Page 37 of 57
CHAR[0]: Indicates the binding channel ID, in the range of 1 to 16 or 0. 0 indicates all the binding channels (only valid when binding channels are cleared). CHAR[1]: Indicates the number of VC12 channels. 0 indicates to clear the binding channel. CHAR[2]-CHAR[50]: Indicate the VC12 channel code, in the range of 1 to 48.
For example: :ptp:4,12,80,vctrunk_number 4.1.5 Default VLAN ID of the Port

If the UNTAG attribute is set for the IP port but the service type of VLAN route is configured, the default VLAN ID of the IP port must be consistent with that of the VLAN route. Otherwise, the service may be interrupted. Querying the division of Ethernet ports (by VLAN ID) (ET1V1 featured board query command)
Name Format Authority Description Parameter Serial No. 1 Example Parameter meaning VLAN ID Parameter value 1-4095; 0 indicates to query all the settings. Remarks cfg-get-vlan Location definition; number of parameters = 1 Query level
:cfg-get-vlan:345; Note: Query the ports contained in VLAN 345.
Querying the division of Ethernet ports (by board ID) (ET1V1 featured board query command)
Name Format Authority Description Parameter Serial No. 1 Example Parameter meaning Actual board ID Parameter value 1-4, 11-14; 0 indicates all boards. Remarks cfg-get-bdvlan Location definition; number of parameters = 1 Query level
:cfg-get-bdvlan:1; Note: Query the VLAN setting of board 1.
Querying the default VLAN ID of the port (by board ID) (ET1V2 featured board query command)
Name Function Command level Open range
2007-10-22
eth-cfg-get-bdvlan Query the default VLAN ID of the port by board ID. Query level Internal level/customer service level/user level
Version Input format Input parameter
4.05.04.10 and above versions Location definition. Number of parameters = 1; repeatability = unrepeatable Parameter location 1 Parameter value Actual board ID: 0, 1, 2, 3, 4, 11, 12, 13, 14; 0 indicates all boards.
Output format
VLAN DEFINE Board-id port-id vlan-id priority Board ID; port ID; VLAN ID; VLAN priority :eth-cfg-get-bdvlan:2;
Example
4.1.6 Static Route Error or Loss on the Ethernet

This problem is close to the host. The following command can be used: Querying the static route (by board ID)
Name Format Authority Description Parameter Serial No. 1 Example Parameter meaning Board ID Parameter value Actual board ID: 1-4, 11-14; 0 indicates all boards. Remarks cfg-get-route Location definition; number of parameters = 1 Query level
:cfg-get-route:3; Note: Query the route setting of board 3.
0x81: MBCMD-ROUTE Function: Configure the route. Format: CHAR[7]; CHAR[0]: Indicates the source port ID. 1-8 indicate physical network ports 1-8 (bit 7 is 0), and 0x81-0x90 (bit 7 is 1) indicate binding channels 1-16. CHAR[1] and CHAR[2] represent a VLAN ID. 0xffff indicates there is no VLAN division; otherwise, it indicates a source address together with the source port ID. CHAR[3]: Indicates the destination port ID. 1-8 indicate physical network ports 1-8 (bit 7 is 0), and 0x81-0x90 (bit 7 is 1) indicate binding channels 1-16. CHAR[4] and CHAR[5] represent a VLAN ID. 0xffff indicates there is no VLAN division; otherwise, it indicates a destination address together with the destination port ID. When the route is unidirectional, CHAR[4] and CHAR[5] are not used. CHAR[6]: 1 indicates service direction (bidirectional), and 0 indicates unidirection from the source to the destination. For example: ptp: xx, 81, 1, 1, 4, 89, 4, 2, 1 indicates the service of VLAN 0x104 is transmitted from port 1 to MP port 9, and the service of VLAN 0x402 is transmitted from MP port 9 to port 1 at the same time.
:ptp:bid,12,81,source_port,ff,ff Query the route database. In the ptp command, source_port indicates the source port ID. 1-8 indicate physical network ports 1-8, and 0x81-0x90 indicate MP channels 1-16. ff,ff indicates the port route. In case of VLAN route, the corresponding VLAN ID (hexadecimal) should be taken.
4.1.7 NE Pointer Justification or Clock Degrade, Resulting in BIP-OVER and TU-LOP from Some Channels of ET1 and Service Interruption
Board replacement or reset can only transfer the faulty channel, but not solve the problem completely. This problem is caused by a logical bug of ET1. Generally, it occurs in case that VC12 service of ET1 returns to ET1 directly through the higher-order cross-connection matrix after being optimized by the cross-connection. BIP-OVER and TU-LOP are reported from some channels, thus the service is interrupted. Board replacement or reset can only transfer the faulty channel, but not solve the problem completely. It is practical to adjust the configuration sequence of VC12 service and set the service to pass through the lower-order channel. The latest logical version has corrected the bug.
4.1.8 Faulty Board Hardware

Generally, the SDH layer alarms will be reported, such as TU-AIS and TU-LOP. So it is easier to locate this problem.
4.1.9 Service Interruption Caused by A Great Deal of Packet Loss (Refer to the Processing of Packet Loss Fault)
The problems of layer 2 switching are not analyzed here.
4.2 Locating the Problems of Persistent Packet Loss on the Ethernet Link
4.2.1 Insufficient Configuration Bandwidth Caused by Large Traffic
This problem can be located by querying the performance statistics of the remote data equipment. Generally, the remote equipment can receive a lot of PAUSE frames persistently. In addition, ordinary routers can monitor the actual traffic (at the IP layer, less than the layer 2 traffic of ET1). If the actual traffic is close to the configuration bandwidth, it also indicates the bandwidth resource is insufficient. Try to bind several 2Ms to verify it. If flow control frames are persistently transmitted from the port under observation, it indicates that the current data traffic to be transmitted is larger than the bound channel bandwidth most of time. At that time, the flow control of the corresponding port of the remote equipment should be disabled, to avoid service unavailability caused by back pressure of the flow control. But this is a temporary solution only. To stop packet loss completely, try to increase the bound channel bandwidth.
4.2.2 Sufficient Bandwidth but Large Service Bursts

This is a common problem, but it is hard to locate. Similarly, you can work out the conclusion by analyzing the performance statistics of the remote equipment (the performance statistics of the local equipment can also act as reference). It is probably that the average traffic is far less than the configuration bandwidth, but the remote equipment still receives PAUSE frames from the local equipment at intervals. It shows that there are large service bursts in the remote end, which exceeds the tolerance of the local equipment. One way is to increase the bandwidth. However, it is better to require the remote equipment for traffic shaping. Query the performance data to locate the problem. //Set the Ethernet performance monitoring :per-set-ethmontime:prdall,1990-0-0,0*0*0,2004-04-10,20*50*00 :per-set-ethmon:bid,0,0,0,prdall,perexall,1; (bid indicates board ID)
:per-get-ethmon:bid,0,0,0,prdall,perexall;
//Query the current Ethernet performance data :per-get-ethcurdata:bid,1,prdcur,perexall The GE02 board has inferior back-to-back capability. When the data of video signals is transmitted, there may be bad service applications due to large data bursts. The board has had large bandwidth bound, but the problem still occurs. So one way is to enlarge the bandwidth, and the other way is to perform traffic shaping at the signal source to decrease the data bursts.
4.2.3 Packet Loss due to Non-response of the Remote Equipment to Flow Control in Case of Too Large Service Traffic
This problem occurs when Huawei equipment enables flow control but the remote equipment does not respond to it. Thus Huawei equipment transmits useless PAUSE frames too fast, and a lot of packets are lost. For the station with large service traffic, it is recommended to enable or disable flow control simultaneously with the remote equipment. In case of serious packet loss status, it is recommended to disable flow control at both ends to keep certain channel availability. To query the setting of flow control, refer to the following commands: :ptp:bid,12,88,0;//Query :ptp:bid,88,port,1;//Set to enable flow control :ptp:bid,88,port,0;//Set to disable flow control
4.2.4 MTU Set for the Board Less Than the Real Transmission Packet Length of the Equipment
This problem does not occur frequently and it is hard to locate. The ET1 board defaults the transmission packet length to 1522 bytes, and the MTU is 1980
bytes. Generally, confirm this problem with the customer and verify whether data packets larger than 1522 bytes are received via performance events. Use the following query command: :ptp:bid,12,b9,port (The 61ET1 and 42ET1 can use the B9 command to modify the MTU value, while the 11ET1 uses the E0 command. Other usages are the same.) The returned packet has two bytes, in hexadecimal. Set the MTU by using the following command:
:ptp:bid,b9,port,xx,xx (xx,xx indicates the packet length in hexadecimal)

For the GE02 and FE08, changing the MTU value needs the coordination of the board software/FPGA version.
4.2.5 Abnormal Working Status Caused by Unmatched Port Mode with the Remote Equipment
This problem frequently occurs in case of two-end interconnection, where one end is set to 100MFULL or 10MFULL (100 M full-duplex or 10 M full-duplex) and the other is set to AUTO (auto-negotiation). As a result, the AUTO end is probably negotiated to 100MHALF. Thus the working modes cannot match each other. In this case, small traffic can be normally transmitted, but large traffic may result in a great deal of collision packets (queried via the performance statistics). So, it is recommended to set the mode to be identical with the remote equipment, that is, either auto-negotiation or 100MFULL at both ends. For detailed description about the query command, refer to the introduction in Chapter 1.
4.2.6 Failed Network Cables or Fiber Optics

Omitted.
4.2.7 Large ET1 Performance Decrease and Packet Loss in Case that the Ethernet Service Packet Lengths of Two Directions Keep Too Large Difference for a Long Time or All the Packet Lengths Are Short Bytes (64-128 Bytes) 4.2.8 Faulty Board Hardware
Generally, the SDH layer alarms will be reported, such as TU-AIS and TU-LOP. So it is easier to locate this problem.
4.3 Loopback Fault Location

Explaining loopback fault location in this section does not indicate that it should be used after the above steps have been adopted during the troubleshooting process. In fact, it can be used for preliminary location after the SDH layer and
basic Ethernet configurations have been troubleshot. And then you can further locate faults accurately, in conjunction with related host and measures and commands such as PTP. Even if nobody assists at the service remote end, you can still conduct the loopback test at related remote ports of the Ethernet, to observe received and transmitted packets in the performance event at the local service access port, and judge whether the service channel is available and the data transmission is normal. Note that the loopback results in service interruption. At present, you can use the loopback, together with performance query to judge whether the data transmission of the ET1 V1 and V2 data boards is normal. For V1 version, you can also use the loopback to conduct related Ethernet performance index tests. However, you cannot use the loopback test the performance index for the V2 version.
4.3.1 ET1 Loopback

You can judge whether the connection is normal with the method of loopback section by section and by querying the status of received and transmitted packets on the Ethernet interface. Connect the network interface of the PC to the Ethernet interface of the ET1, use the PING command to send packets to the ET1 port, and query the performance data of the ET1. If such events as RXOK and RXBOK are not naught, it means that the packets are received. Perform a loopback on the corresponding connection of the Ethernet service (loopback can be performed at this station, the relay station, or the opposite station.). If the connection is normal, the packets following the loopback should be sent again from this Ethernet interface through the ET1. At this time, query the performance data of the ET1. Such events as TXOK and TXBOK should have numerical values rather than zero, which means that some packets are being sent. In other words, the connection is normal. Otherwise, the connection fails. By altering the location where the loopback is performed, the specific faulty board of the faulty NE can be located. (the following two figures show the functions of different loopback points)
2007-10-22
Page 43 of 57
Opposite NE MAC inloop 519 inloop Check that the connection is normal
NMS
519 outloop Local NE
Check that the ET1 is normal
Query the status of the packet received and transmitted through the ET1
Transmit packets: ping X.X.X.X
ET1 fault location
Ethernet interface unit 8 10/100 M Ethernet interface
HDLC interconnection unit
Transformer
FIFO interface multiplexing/ demultiplexing HDLC interconnection XCV600E
E1-VC-4 mapping/ demapping unit
8/4 and 4/8 conversion and interface level conversion
IXP1200 minimum system Debug network interface Debug serial port SDRAM control unit 56-port scheduling Ethernet slicing Ethernet reassembly
PCI control unit
Store-andforward unit Network processor IXP1200
Control bus
Decoding logic Mailbox
Peripheral management
I. Host command
Name Format Authority
2007-10-22
cfg-set-ethportlb Location definition; the number of parameters = 4 Configuration level

Description Parameter Serial No. 1 2 3 Parameter meaning Slot No. Channel No. Loopback point setting Parameter value Remarks The actual slot number is used: 1 to 4 and 11 to 14 (the parameter cannot be 0) ipport or ip1-ip8ipport (configuring all the Ethernet interfaces) mac/phy; mac indicates loopback at the MAC end phy indicates loopback at the PHY end nolb/rlb/llb; nolb: No loopback rlb: Inloop llb: Outloop (the PHY end does not support the outloop) :cfg-set-ethportlb:1,ip2,mac,rlb; Note: The command sets Ethernet interface 2 in Slot 1 to perform the inloop at the MAC end
Loopback mode
Example
II. Board command

0x8C: Function: Set the loopback mode of the Ethernet interface :ptp:bid,8c,CHAR[0],CHAR[1],CHAR[2] Format: ptp: board No., 8c, port No., loopback point and loopback mode; CHAR[], CHAR[0]: Port No., in the range of 0 to 8. 0 indicates all the ports and 1 ~ 8 indicates physical network interfaces 1 to 8; char[1]: Loopback point. 1 indicates the MAC layer loopback, that is, loopback at the IXF440. 2 indicates the PHY layer loopback, that is, loopback at the LXT974; char[2]: 0 indicates no loop and 1 indicates inloop. Due to the limitation of the chip function, there is no outloop and only the inloop is available. Note: The port No. ranges from 0 to 8. 0 represents all the ports and 1 to 8 represents physical network interfaces 1 to 8. Loopback point: 1 represents the MAC layer loopback and 2 represents the PHY layer loopback. Usually, only the MAC layer loopback is used. Loopback mode: 0-no loopback, 1-inloop and 2-outloop. Note: The outloop is not currently supported on the MAC layer and PHY layer. Example: ptp: xx, 8C, 1, 1, 1 ptp: xx, 8C, 1, 2, 1 represents MAC layer inloop of Port 1; represents PHY layer inloop of Port 1.
0x81: The loopback function, which the 1200 chip does not provide, can be implemented by configuring the route. Function: Route configuration Format: CHAR[7]. CHAR[0]: Source port No. 1 ~ 8 (Bit7 is 0) indicates physical network interfaces 1 to 8. 0x81 ~ 0x90 (Bit7 is 1) indicates bound channels 1 to 16. CHAR[1] and CHAR[2] indicate a VLAN No. 0xffff indicates no VLAN division. Otherwise, 0xffff indicates a source address in conjunction with the source port No. CHAR[3]: Sink port No. 1 ~ 8 (Bit7 is 0) indicates physical
2007-10-22
Page 45 of 57
network interfaces 1 to 8. 0x81 ~ 0x90 (Bit7 is 1) indicates bound channels 1 to 16. CHAR[4] and CHAR[5] indicate a VLAN No. 0xffff indicates no VLAN division. Otherwise, 0xffff indicates a destination address in conjunction with the destination port No. The CHAR[4] and CHAR[5] cannot be used when the route is unidirectional. CHAR[6] indicates the service direction, with 0 being unidirectional, that is, from the source to the destination and 1 being bi-directional. Example: ptp: xx, 81, 1, ff, ff, 1, ff, ff, 1 represents the loopback of the service from Port 1. 0xD2: Function: Incrementally set the loopback mode of the E1 channel, and perform loopback at the 519 end Format: char[2]. para[0]: 0 indicates all the channels. Otherwise, it means a specific channel. It is to set the loopback mode of the E1 channel. Format: ptp: board No., d2, channel and loopback mode; Note: Channel: 0 represents all the channels. Otherwise, it means a specified channel, para[1]: Loopback mode setting. 0-no loopback; 1-inloop, that is, loopback of the 519 to the cross connection, with overhead to be processed; 2-outloop, that is, loopback of the 519 to the 1200, with no overhead to be processed. For example: :ptp:4,d2,1,2;\\set the first 2 M channel to the outloop mode. :ptp:4,d2,0,2;\\set all channels to the outloop mode. :ptp:4,12,d2,0 \\query the loopback status of all the channels Note: 1. The 0xd2 command works in terms of 2 M channels. If an MP is bound to the 1&&5 channel, five commands should be sent to perform loopback: :ptp:4,d2,1,2; :ptp:4,d2,2,2; :ptp:4,d2,3,2; :ptp:4,d2,4,2 and :ptp:4,d2,5,2. Of course, we can also send one single command :ptp:4,d2,0,2 to loop back all the channels. In this case, since the command acts on all the 48 channels, we should take its possible effects on the services of other network interfaces into consideration. 2. The 0x8c command works in terms of ports, so it is simpler. 3. In the service connection test, the local end adopts the 519 layer outloop to check the condition of the ET1 board, and the remote end adopts the MAC layer inloop to make a more thorough connection test.
4.4 Performance Query

Similarly, the performance query is also a useful tool to locate faults, through which you may learn more about what events occur at the bottom of the fault symptom. Such experiences make your instinct more and more acute. Most of the above-mentioned operations and judgements are made on the basis of the performance query result. How to query the performance of the ET1 series data boards?
2007-10-22
Page 46 of 57
In case that the NM maintenance application and deployment are increasingly popular, it is necessary to describe how to query the performance event through the NM; To query the performance of the ET1 V1 series data boards, first make related settings through [Performance/Performance Setting/Ethernet Monitoring]. Set the monitoring status as enabled, and enable the 15-minute and 24-hour performance monitoring. In case that the setting succeeds, you can view performance events of corresponding board and port through the Ethernet performance browse window after the set performance monitoring time; To query the performance of the ET1 V2 series data boards, it is unnecessary to make the above mentioned settings. You can directly view performance events of corresponding board and port through the Ethernet performance browse window. The EFGS series boards also use the same query method and window During the query, you should focus on what kinds of changes have taken place at the late stage to the observed events at the early stage. //performance query :per-set-ethmontime:30m,2003-02-08,18*30*00,2005-02-08,20*50*00;(select the time as required) :eth-per-get-hisdata:bid,ip1(select required),30s,grp1,1,10 from external ports ip1 to ip8 as
:eth-per-get-hisdata:bid,ip1,30s,grp2,1,10 :eth-per-get-hisdata:bid,ip1,30s,grp3,1,10 :eth-per-get-hisdata:bid,ip1,30m,grp1,1,10 :eth-per-get-hisdata:bid,ip1,30m,grp2,1,10 :eth-per-get-hisdata:bid,ip1,30m,grp3,1,10 :eth-per-get-ethcurdata:bid,ip1(external port),grpall
I. Common commands for Ethernet performance monitoring

1. Set the start/end time of the Ethernet performance monitoring
Name Format Parameter per-set-ethmontime Location definition; number of parameters = 5 Serial No. Parameter meaning 1 Period type
2 3
Start date Start time
Parameter value 30s: Represents 30-second performance 30m: Represents 30-minute performance prdvar: Represents period variable performance prdcur: Represents the current performance prdall: Represents all performances Format: 2001-3-5 Format: 12*0*0
Remarks
2007-10-22
Page 47 of 57
4 5 Example Name Format Parameter
End date End time
Format: 2001-3-5 Format: 12*0*0
:per-set-ethmontime:prdall,2001-3-5,12*0*0,2048-4-5,12*0*0;
2. Set the monitoring attributes of the Ethernet performance monitoring data

per-set-ethmon Location definition; number of parameters = 7 Serial No. Parameter meaning 1 Slot No. 2 3 4 5 Channel No. Reserved Reserved Period type
Parameter value Actual slot No.: 4 represents all slots 0 ~ 8: Ethernet interface No.; 0x8001 ~ 0x8010: MP port No. 0 0 30s: Represents 30-second performance 30m: Represents 30-minute performance prdvar: Represents period variable performance prdcur: Represents the current performance prdall: Represents all performances For codes, see what described later in this document; perexall represents all 0: Not monitor; 1: Monitor
Remarks
Code of the performance event Report flag
7 Example Name Format Parameter
:per-set-ethmon:4,3,0,0,30m,perexall,1;
3. Query the current performance monitoring data of the Ethernet

per-get-ethcurdata Location definition; number of parameters = 4 Serial No. Parameter meaning 1 Slot No. 2 3 4 Channel No. Period type Code of the performance event
Parameter value Actual slot No.: 4 represents all slots 0 ~ 8: Ethernet interface No.; 0x8001 ~ 0x8010: MP port No. prdcur: Represents the current performance For codes, see what described later in this document; perexall represents all
Remarks
Example Name Format Parameter
:per-get-ethcurdata:4,1,prdcur,perexall;
4. Reset the Ethernet performance counter

per-clr-ethcurdata Location definition; number of parameters = 6 Serial No. Parameter meaning 1 Slot No. 2 Channel No.
Parameter value Actual slot No. 0 ~ 8: Ethernet interface No.; 0x8001 ~ 0x8010: MP port No.
Remarks
2007-10-22
Page 48 of 57
3 4
Period type Code of the performance event Reserved Reserved
5 6 Example
prdcur: Represents the current performance For codes, see what described later in this document; perexall represents all 0 0
:per-get-ethmon:4,1,prdcur,perexall,0,0;
II. Ethernet performance eid description

Performance event ID (character string description) perexall rxok rxcrc Meaning Current performance 30-second performance 30-minute performance Period variable performance Report flag
All performance events Correct packets received Packets with the CRC errors received Report of receiving correct number of bytes Number of ultra long packets received Broadcast packets correctly received Multicast packets correctly received Flow control packets correctly received Short packets correctly received (< 64) Short packets with the CRC errors Non-broadcast packets correctly received (64 ~ MAX) Ultra long packets correctly received Ultra long packets with the CRC errors 64-byte-long
y y
y y
y y
y y
YES YES
rxbok
YES
rxtooln rxbrdok rxmok rxpause
y y y y
NO NO NO NO
rxsok
NO
rxscrc rxuok
y y
NO NO
rxlok rxlcrc rxpkt64

2007-10-22
y y y
NO NO NO
Page 49 of 57
packets received (including the errored ones) rxpkt65 65 to 127-byte-long packets received (including the errored ones) 128 to 255-byte-long packets received (including the errored ones) 256 to 511-byte-long packets received (including the errored ones) 512 to 1023-bytelong packets received (including the errored ones) 1024 to 1518-bytelong packets received (including the errored ones) 1519 to max-byte-long packets received (including the errored ones) Report of receiving incorrect number of packets y y y y NO
rxpkt128
NO
rxpkt256
NO
rxpkt512
NO
rxpkt1k
NO
rxpkt1519
NO
rxbbad
YES
txok
Report of number of packets correctly sent Report of bytes of packets correctly send Report of bytes not normally sent Number of packets correctly sent after one collision Number of packets correctly send after multiple collisions Number of packets stopped in sending
YES
txbok
YES
txbbad txscok
y y
YES NO
txmcok
NO
txlc
NO
2007-10-22
Page 50 of 57
due to late collision txdefer txpkt64 Number of packets deferred in sending 64-byte long packets sent (including the errored one) 65 to 127-byte-long packets sent (including the errored ones) 128 to 255-byte-long packets sent (including the errored ones) 256 to 511-byte-long packets sent (including the errored ones) 512 to 1023-byte-long packets sent (including the errored ones) 1024 to 1518-byte-long packets sent (including the errored ones) 1519 to max-byte-long packets sent (including the errored ones) Number of flow control packets sent Number of errored packets sent due to underflow Number of non-broadcast packets correctly sent Number of multicast packets correctly sent Number of broadcast packets correctly sent
y y
NO NO
txpkt65
NO
txpkt128
NO
txpkt256
NO
txpkt512
NO
txpkt1k
NO
txpkt1519
NO
txpause txerr
y y
NO NO
txuok
NO
txmok
NO
txbrdok
NO
2007-10-22
Page 51 of 57
txlos txcol
Report of number of packets discarded Number of collisions occurring in sending Number of packets of over 16 collisions
y y
YES NO
txxcol
NO
4.5 Small Tools

4.5.1 Ping Command
Common parameters: -t for stop. -l size -n count Sends packets continuously. Press <Ctrl+C>
Sets the length of the packets to be sent Sets the times for which packets are to be sent
For example: Ping 129.9.0.4 -l 500 -n 10 The above command indicates sending 500-byte-long packets to 129.9.0.4 for ten times.
4.5.2 Arp Command

Common parameters: -a Views the current Arp entry
-g Obtains the current Arp entry, with the same function as the above parameter -d obtained again through -g. Deletes the current Arp entry, which can be
4.5.3 sniffer Program

At present, this program is not provided. If you can obtain the program by other methods, do not use it for commercial activities, to avoid unnecessary troubles.
Chapter 5 Typical Case Analysis

This section analyzes the telecom cases one by one, in combination with the above-mentioned contents in this document.
5.1 Network Service Interruption

[Fault symptom]
One day after the network cutover, users report that the Internet access services are interrupted. However, all Internet websites can be pinged, and messages can be received and sent on occasion through the QQ. At this time, there is no abnormal alarm on the Internet. [Solution] 1. In terms of fault symptom, it is suspected that the broadband data communication product incurs some faults. First disconnect the broadband data communication product, and then connect a PC under the ET1 for a test; 2. Two PCs can ping each other successfully, but fail to visit each other normally, obviously indicating that the Ethernet channel of the ET1 incurs some faults; 3. Increase the length of the ping packet gradually, and find that the opposite PC cannot be pinged when the length of the packet is about 200 bytes, that is, successful ping in case of short packet and failed ping in case of long packet; 4. Analyze the working principle of the ET1 (refer to Section 3.1 in this document) and suspect that the MP bound VC12s at two ends of the ET1 do not match with each other, which results in that the receive end cannot recover the long packet completely; 5. Detect the configuration and find that the MP at one end binds four VC12s, and the MP at the opposite end binds five VC12s, which is a typical configuration error. [Summary] 1. The packet length should be added when you conduct the ping test after the service is available. It is recommended that the parameter should be 1500, that is, Ping IP address l 1500;
2. If the VC12s bound by the MP at one end do not correspond to those bound by the MP at the other end, it is certain that the services are abnormal; 3. Furthermore, if one VC12 or many VC12s bound by the MP incur faults, the Ethernet services of the entire MP will be abnormal; Think: How to resolve the problem that the entire channel fails because some of the VC12s incur faults? Answer: The solution to this problem is LCAS. Comments: To resolve this kind of problem, you should first define the fault, that is, decide whether the fault point is at the transmission side or the data communication side. Therefore, first disconnect the data communication product, and directly connect a PC for a test. If the problem still exists, it is very likely that there are troubles with the transmission side. Then, you should know the features of the network service and make the best of the existing tools for various tests, to find out the problem. Finally, you should know the working principle of the Ethernet feature board, and analyze the reason of the fault.
5.2 Serious Service Packet Discard

[Fault symptom]
Users report that the Internet access speed is very low and many packets are lost when you ping the external websites. [Solution] Thought: Data communication fault? Line fault? Board fault? Port mode problem? 1. If the line has bit errors, the VC where the Ethernet frame exists also generates bit errors. When the board recovers the Ethernet frame from the VC, it will perform the CRC check. In this case, it is sure that the frame will be discarded because the CRC check cannot be passed. 2. For packet discard due to board hardware faults, you can only replace the board with the hardware fault; 3. In case that packets are discarded as a result of inconsistent port mode, you can determine the problem through the Ethernet performance event: If the local end works in full duplex mode and receives a large number of packets with the CRC errors, it is decided that the opposite end works in half-duplex mode. Of course, it is also likely that the network cable has faults or there are interferences. Therefore, to resolve this kind of fault, first check that the SDH side generates bit errors. Then, check that the port modes at two ends are inconsistent through the Ethernet performance event. Finally, disconnect the data communication equipment and directly connect a PC to check whether the data communication product incurs some faults. If there is a trouble with the MSTP product, replace the Ethernet board and make further observation. [Summary] For the port mode problem that has been described previously, pay attention to the following three points: 1. Because the HUB only supports the half-duplex mode, it is forbidden to set a port as full duplex when the port is connected with the HUB; 2. Although some equipment ports (such as PC) can be set as full duplex or half-duplex, the settings actually do not take effect, that is, these ports can only work in auto-negotiation mode. 3. If the Ethernet optical interface is in full duplex VS auto-negotiation mode, the link cannot be established.
5.3 Poor Image of the Video on Demand Service

[Fault symptom] At a certain place, Gigabit Ethernet services (four VC4s are bound) are provided through the switch from the C Company and Huawei GE02 board, and users can apply video on demand services. However, the picture is often stagnant if the UDP is used and frame hop occurs from time to time if the TCP is used. [Solution] Thought: 1. Huawei products transparently transmit Ethernet frames, and do not identify the contents of Layer 3 or above. Why great differences take place between
the TCP and UDP? It looks that the problem is independent of the MSTP product, but why there is no similar problem when users obtain the same service by directly connecting with the optical fiber? Therefore, the problem results from the MSTP product that is connected with the network, probably an interconnection problem? 2. If the fault is caused by the interconnection problem, the same fault symptom should occur no matter what upper-layer protocol is used. Therefore, the fault is related to specific applications of the upper-layer protocol. At first, you should make clear what differences the data flow of the video on demand service have when the TCP and UDP are used, which is the breakthrough to the problem. 3. Perform the video on demand at customer premises respectively using the TCP and UDP, and capture packets with the Sniffer to analyze specific differences of diverse data flows. 4. Analyze and test the MSTP product based on the result of Step 3. Processing procedure: 1. Sniffer packet capture results: In case of TCP, the length of the IP packet is about 1510 bytes. In case of UDP, the length of the IP packet is more than 8000 bytes, which need to be split into about six Ethernet frames. In addition, the Sniffer shows that only the first four fragments can be received and the last two fragments are lost. Therefore, it is the MSTP product that loses some continuous fragments, resulting in stagnant pictures. 2. Analyze the differences between the TCP and UDP. The TCP works in confirm-retransmit mode, so its data burst has some limits. While the UDP is connectionless oriented, and has fiercer data burst than the TCP. Therefore, the MSTP product cannot bear the data burst generated when the UDP is used, and discards packets due to buffer overflow. 3. The B2B index reflects the tolerance capability of the product for data burst to a certain degree. Use a meter to conduct a B2B test for the GE02, and find its index is quite poor, indicating that packets are lost because the GE02 cannot bear the data flow burst. 4. Because the performance index is fixed to the product and cannot be optimized by setting the software, you can only increase the bound bandwidth from four VC4s to eight VC4s, so that the GE02 can forward the Gigabit Ethernet at wire speed. Thus, the problem is resolved. [Summary] 1. The problem requires the engineer to possess comprehensive knowledge and analyze problems in terms of the entire service. The problem cannot be resolved only from the viewpoint of the MSTP product itself. 2. The comprehensive understanding of diverse Ethernet performance indices helps to analyze the fundamental reason of the problem and find a solution.
5.4 L2 Switching Version Service Abnormality

[Fault symptom]
2007-10-22
Page 55 of 57
A certain place uses the Ethernet L2 switching version of the MSTP. One day, the actual network services are almost fully interrupted. However, the Ethernet and SDH side do not report any abnormal performance events and alarms. [Solution] Thought: If serious abnormalities suddenly occur during normal network operations, there are usually three reasons: Hardware damage, abnormal software state, and fault trigger due to some manual operations. Therefore, you should first analyze what operations have been performed on the network before the fault occurs (including the interconnected equipment), and exclude these operations one by one. Then analyze the software and hardware status information of the board. Finally, isolate the data communication equipment for further location. Note that the following cases are forbidden for the Ethernet L2 switching version: Set inloop mode for the port Directly connect two ports with the network cable (optical fiber) so that a loop is generated Any other cases where the frame may be forwarded more than once in the same switching unit
Processing procedure: 1. First exclude the above-mentioned cases. 2. The fault occurs because users connect another port of the ET1S with the same L3 during the capacity expansion. After you disconnect any of the network cables, the services of the other port restore to normal. Therefore, it is obvious that two ports of the ET1S are connected with the same L3, resulting in the Ethernet loop. 3. The opposite end is L3 and the ports are isolated from each other. Therefore, the possibility of an Ethernet loop is excluded. 4. Disconnect the MSTP at the line side, and directly connect the PC under the ET1S. Ping the opposite L3 and find out the same fault symptom. Query the ARP table of the PC, and find that the IPs corresponding to different L3 ports are mapped to the same MAC address. Query the forwarding table of the ET1S, and find that the entry corresponding to the MAC address is unstable and continuously switched between two ports, resulting in service abnormality. 5. Consult the L3 development personnel, and know that all ports of the L3 of this model share one common MAC. However, the ET1S of Huaweis MSTP only supports one forwarding table. If there is more than one interconnected port between two sides, the forwarding table of the ET1S may generate jitters, resulting in service abnormality. [Summary] 1. To resolve this kind of problem, first find out the condition that triggers the fault. Then analyze the causes of the fault based on the trigger condition. 2. A good knowledge of the MSTP product and data communication product is very important to resolve the Ethernet problem.
2007-10-22
Page 57 of 57

Troubleshooting Guide To Ethernet Data Boards PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Troubleshooting Guide To Ethernet Data Boards PDF

Transféré par

Droits d'auteur :

Formats disponibles

Document code Target readers Edited by

Product name Product version Document version

Troubleshooting Guide to Ethernet Data Boards

Drafted by: Reviewed by: Reviewed by: Approved by:

Date: Date: Date: Date:

Huawei Technologies Co, Ltd

Troubleshooting Guide to Ethernet Data Boards

Confidentiality: For Internal Use Only

Huawei secrets, no dispersion without permission

Troubleshooting Guide to Ethernet Data Boards

Confidentiality: For Internal Use Only

Huawei secrets, no dispersion without permission

Troubleshooting Guide to Ethernet Data Boards

Confidentiality: For Internal Use Only

Huawei secrets, no dispersion without permission

Troubleshooting Guide to Ethernet Data Boards

Confidentiality: For Internal Use Only

Huawei secrets, no dispersion without permission

Troubleshooting Guide to Ethernet Data Boards

Confidentiality: For Internal Use Only

Troubleshooting Guide to Ethernet Data Boards Chapter 1 Overview

Huawei secrets, no dispersion without permission

Troubleshooting Guide to Ethernet Data Boards

Confidentiality: For Internal Use Only

Chapter 2 Background Knowledge

2.1.2 Working Mode of the Port

Troubleshooting Guide to Ethernet Data Boards

Confidentiality: For Internal Use Only

2.1.3 Various Error Frames of Ethernet (Ethernet II)

2.1.4 Ethernet Flow Control

Troubleshooting Guide to Ethernet Data Boards

Confidentiality: For Internal Use Only

2.1.6 Relationship Between Ethernet II and IEEE 802.3 Frames

Troubleshooting Guide to Ethernet Data Boards

Confidentiality: For Internal Use Only

2.1.9 Composition of a Data Communication System

2.1.10 Concepts, Settings and Setting Principles of MTU and MRU

Troubleshooting Guide to Ethernet Data Boards

Confidentiality: For Internal Use Only

2.1.11 VLAN ID Support of Data Boards

Troubleshooting Guide to Ethernet Data Boards

Confidentiality: For Internal Use Only

2.1.13 Locating the Channel that Generated an ATM Alarm

2.1.14 Querying Ethernet Performance Events of an ET1 Board

Huawei secrets, no dispersion without permission

Troubleshooting Guide to Ethernet Data Boards

Confidentiality: For Internal Use Only

2.1.16 Querying the Actual Working Mode of the 61ET1

Huawei secrets, no dispersion without permission

Troubleshooting Guide to Ethernet Data Boards

Confidentiality: For Internal Use Only

2.1.19 Use of Standard/Manufacturerer Network Cables

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

Troubleshooting Guide to Ethernet Data Boards

Confidentiality: For Internal Use Only

2.1.22 Encapsulation Protocol of Each Data Attribute Version

ET1 V1 series - - - ML-PPP

Troubleshooting Guide to Ethernet Data Boards

Confidentiality: For Internal Use Only

2.1.24 Explanations of EPL, EVPL, EPLn and EVPLn Services

Huawei secrets, no dispersion without permission

Troubleshooting Guide to Ethernet Data Boards

Confidentiality: For Internal Use Only