This section describes how to verify whether the optical power of SFP optical modules meets requirements.
Commissioning Guide 5 Commissioning the Link Layer
5.1 Checking Ethernet Interfaces
This section describes how to check the link layer on Ethernet interfaces.
Prerequisites
l Hardware installation is complete. For more information, see 4 Checking the Hardware.
l The CX600 is running properly.
Procedure
Step 1 Run the display interface ethernet brief command to view the physical status, auto-negotiation mode, duplex mode, rate, and latest average inbound and outbound bandwidth usage of Ethernet interfaces. For example:
--In normal situations, the physical status of interfaces are up, as shown by the characters displayed in boldface.
Step 2 Run the display interface command to view the MTU, IP address, mask, rate, and operation mode of an Ethernet interface. For example:
<HUAWEI> display interface gigabitethernet 2/0/0 GigabitEthernet2/0/0 current state : UP
Line protocol current state : UP
Last line protocol up time : 2010-02-09 04:26:01
Description:HUAWEI, Quidway Series, GigabitEthernet2/0/0 Interface Route Port,The Maximum Transmit Unit is 1500
Internet Address is 192.168.1.1/24
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc7d-a49d The Vendor PN is FTRJ8519P1BNL-HW
The Vendor Name is FINISAR CORP.
Port BW: 1G, Transceiver max BW: 1G, Transceiver Mode: MultiMode WaveLength: 850nm, Transmission Distance: 550m
Rx Power: -6.72dBm, Tx Power: -6.28dBm
Loopback:none, full-duplex mode, negotiation: disable, Pause Flowcontrol:Receive Enable and Send Enable
The setted port-tx-enabling delay time is: 0 ms The remanent time of enabling port-tx is: 0 ms Last physical up time : 2010-03-21 15:35:04 Last physical down time : 2010-03-21 15:35:04 Current system time: 2010-02-10 23:49:52 Statistics last cleared: never
Commissioning Guide 5 Commissioning the Link Layer
Last 300 seconds input rate: 240 bits/sec, 0 packets/sec Last 300 seconds output rate: 88 bits/sec, 0 packets/sec Input: 4763528 bytes, 61864 packets
Output: 1718640 bytes, 5208 packets Input:
Unicast: 0 packets, Multicast: 30932 packets Broadcast: 30932 packets, JumboOctets: 0 packets CRC: 0 packets, Symbol: 0 packets
Overrun: 0 packets, LongPacket: 0 packets Jabber: 0 packets, Alignment: 0 packets
Fragment: 0 packets, Undersized Frame: 0 packets RxPause: 0 packets
Output:
Unicast: 0 packets, Multicast: 5208 packets Broadcast: 0 packets, JumboOctets: 0 packets
Lost: 0 packets, Overflow: 0 packets, Underrun: 0 packets System: 0 packets, Overruns: 0 packets
TxPause: 0 packets
Input bandwidth utilization : 0.01%
Output bandwidth utilization : 0.01%
In normal situations, the physical status and protocol status of an Ethernet interface are up, and the link status on the local end are the same as that on the peer end, as shown by the characters displayed in boldface.
Step 3 Run the ping command to test Ethernet link connectivity. For example:
<HUAWEI> ping 192.168.1.2
PING 192.168.1.2: 56 data bytes, press CTRL_C to break
Reply from 192.168.1.2: bytes=56 Sequence=1 ttl=255 time=2 ms Reply from 192.168.1.2: bytes=56 Sequence=2 ttl=255 time=1 ms Reply from 192.168.1.2: bytes=56 Sequence=3 ttl=255 time=1 ms Reply from 192.168.1.2: bytes=56 Sequence=4 ttl=255 time=1 ms Reply from 192.168.1.2: bytes=56 Sequence=5 ttl=255 time=113 ms 192.168.1.2 ping statistics
5 packet(s) transmitted 5 packet(s) received 0.00% packet loss
round-trip min/avg/max = 1/23/113 ms
In normal situations, the ping operation should succeed.
----End
Troubleshooting
l If the physical status of an Ethernet interface is Down after the interface is configured, perform the following operations:
1. Check that the peer device is started. If the peer device is not started, start it.
2. Run the display interface interface-type interface-number command to view the optical module information and interface configurations on the local and peer ends.
– Check that the optical modules on the local and peer interfaces are matched, including interface types, rate, wavelengths, and optical powers of optical modules.
Check the fiber connected the optical modules and the power of connected optical modules meet the requirement. If the fiber or either of the optical modules does not meet the requirement, replace it.
– Check that the auto-negotiation modes on the local and peer interfaces are consistent. If they are inconsistent, run the duplex command to make the two interfaces use the same duplex mode.
Commissioning Guide 5 Commissioning the Link Layer
– Check that the interface configurations such as the MTU, TTL of packets, format of transmitted Ethernet frames, and maximum QoS bandwidth on the local and peer ends are consistent. If they are inconsistent, adjust them to ensure consistency.
– Check that the traffic is normal.
3. Check that the fiber is properly and correctly installed. This means that the fiber is connected to the correct transmit optical module and receive optical module.
4. Perform self-loop detection on interfaces to check whether the interfaces are normal.
After you run the undo shutdown command in the interface view, connect the RX end and TX end of an optical module on the local interface using a fiber. Check whether the interface is Up. If the interface is Up, the local interface is normal. Perform the same operation on the remote interface. If the remote physical layer is Up, the remote interface is normal. You need to replace the fiber.
5. If the fault persists after the preceding operations are complete, contact Huawei technical support personnel.
l If an Ethernet interface cannot be pinged, perform the following operations:
1. Check that the local end is correctly connected to the peer end. Observe the Link indicator on the LPU where the local Ethernet interface resides. If the indicator is on, the link works properly. If the indicator is off, check the optical module, interface, fiber, and the device.
2. Check that the auto-negotiation modes on the local and peer Ethernet interfaces are consistent.
3. Check that the IP address of the local Ethernet interface belongs to the same subnet as that of the peer Ethernet interface. This means that the two IP addresses must have the same network address and different host addresses. If the two IP addresses do not belong to the same subnet, reconfigure the IP addresses.
4. Check that the link layer protocols on the local and peer ends are consistent. Reliable communication between two Ethernet devices is available only when they use the same link layer protocol.
5. If the fault persists after the preceding operations are complete, contact Huawei technical support personnel.
5.2 Checking POS Interfaces
This section describes how to check the link layer on POS interfaces.
Prerequisites
l Hardware installation is complete. For more information, see 4 Checking the Hardware.
l The CX600 is running properly.
Procedure
Step 1 Run the display interface brief command to view brief information about POS interfaces, including the physical status, link layer protocol status, bandwidth usage, and statistics about incorrect packets.
<HUAWEI> display interface brief | include Pos PHY: Physical
Commissioning Guide 5 Commissioning the Link Layer
*down: administratively down
Interface PHY Protocol InUti OutUti inErrors outErrors Pos1/0/0 up up 0.01% 0.01% 3795064053 0 Pos1/0/1 down down 0% 0% 343911292 0 Pos1/0/2 down down 0% 0% 343913408 0 Pos1/0/3 down down 0% 0% 343915353 0
This command can quickly display the physical status and link layer protocol status of all POS interfaces on the CX600.
Step 2 Run the display interface pos command to view the physical status, link layer protocol status, clock mode on a POS interface. For example:
<HUAWEI> display interface pos 1/0/0
As shown by the characters displayed in boldface, in normal situations, the physical status and link layer protocol status on a POS interface are UP; link configurations on the local POS interface are the same as those on the peer POS interface; no alarms and errors are displayed.
Commissioning Guide 5 Commissioning the Link Layer
If the alarm count and error count are not 0, run the command several times to check whether the counts increase. Or, run the reset counters interface command to clear the statistics and then run the command several times.
Step 3 Run the ping command to test POS link connectivity. For example:
<HUAWEI> ping 192.168.1.2
PING 192.168.1.2: 56 data bytes, press CTRL_C to break
Reply from 192.168.1.2: bytes=56 Sequence=1 ttl=255 time=2 ms Reply from 192.168.1.2: bytes=56 Sequence=2 ttl=255 time=1 ms Reply from 192.168.1.2: bytes=56 Sequence=3 ttl=255 time=1 ms Reply from 192.168.1.2: bytes=56 Sequence=4 ttl=255 time=1 ms Reply from 192.168.1.2: bytes=56 Sequence=5 ttl=255 time=113 ms 192.168.1.2 ping statistics
5 packet(s) transmitted 5 packet(s) received 0.00% packet loss
round-trip min/avg/max = 1/23/113 ms
In normal situations, the ping operation should succeed.
----End
Troubleshooting
If the physical status of a POS interface does not go Up after it is connected, perform the following operations:
1. Check that the local and peer POS interfaces are enabled, the input and output optical power of the interfaces are normal, and there are no SDH alarms.
Run the display interface pos [ interface-number ] command.
l If the value of the current state field is Administratively down, the POS interface is not enabled. Run the undo shutdown command in the interface view.
l If the output optical power is not within the allowed range, replace the optical module.
l If the input optical power is smaller than the receiver sensitivity, adjust the link or replace the peer optical module.
l If the values of the fields under the SDH alarm field are not none and B1, B2, and B3 error code counts displayed under the SDH error fields increase, note the following points:
–If B1, B2, and B3 error code counts all increase, check the direct link between the optical modules as well as these modules on the two ends. If the link is a WDM link, ensure that it is stable.
–If only the B3 error code count increases, check the link directly connecting the peer device and an SDH device because this problem often occurs when a routing device is connected to an SDH device. If the link between the concerned SDH devices is a WDM link, you also need to check the entire WDM link to ensure stable
transmission.
If the fault persists, go to Step 2.
2. Check that the fiber and optical modules are properly installed.
An optical module or a fiber connector has a fastener. If you hear a click when installing the fiber or an optical module, the fiber or optical module is properly installed.
If the fault persists, go to Step 3.
Commissioning Guide 5 Commissioning the Link Layer
3. Check that the fiber is connected to the correct transmit optical module and receive optical module.
Remove the fiber and connect it to a different module of the original interface on each end (for example, if the fiber is connected to the transmit optical module of an interface on the local end, remove it and then connect the fiber to the receive optical module of that interface on the local end). If the fault is not rectified, restore the original fiber connection.
If the fault persists, go to Step 4.
4. Use a fiber to perform local loopback.
Use a good fiber to connect the transmit and receive optical modules of the local interface.
l If the physical layer is Up and SDH alarms are all cleared and B1, B2, and B3 error code counts do not increase on the interface, the local optical modules and the board where the interface resides work properly. You need to check the link and the peer device.
l If the physical layer is not Up, the local optical modules or the board where the modules reside works abnormally. Switch the services of the board or the concerned interface to another board and then replace the optical modules or the board to see if the fault will be rectified.
NOTE
Before using a fiber to perform local loopback, run the clock master command to set the clock mode of an interface to master.
If the fault persists, go to Step 5.
5. Collect the following information and contact Huawei technical support personnel:
l Results of the preceding operation procedure
l Configuration files, log files, and alarm files of the CX600
5.3 Checking CPOS Interfaces
This section describes how to check the link layer on CPOS interfaces.
Prerequisites
l Hardware installation is complete. For more information, see 4 Checking the Hardware.
l The CX600 is running properly.
Procedure
Step 1 Run the display controller cpos command to check the status of a CPOS interface. For example:
<HUAWEI> display controller cpos 1/0/0 Cpos1/0/0 current state : UP
Description : Cpos1/0/0 Interface The Vendor Name is AGILENT
The Vendor PN is QFCT-5736TP
Port BW: 155M, Transceiver max BW: 155M, Transceiver Mode: SingleMode WaveLengh: 1310nm, Transmission Distance: 15km
Physical layer is Packet Over SDH
clock master, Multiplex AU-4, loopback none
TX:Flag J0: "NetEngine ", Flag J1: "NetEngine ", Flag C2: 2(0x2) RX:Flag J0: "NetEngine ", Flag J1: "NetEngine ", Flag C2: 2(0x2)
Commissioning Guide 5 Commissioning the Link Layer
section layer:
The setted port-tx-enabling delay time is: 0 ms The remanent time of enabling port-tx is: 0 ms
As shown by the characters displayed in boldface, the CPOS interface status is UP when the CPOS interface is correctly configured, and no alarms or errors are displayed.
If the alarm count and error count are not 0, run the command several times to check whether the counts increase. Or, clear the statistics and then run the command several times.
Step 2 Run the display interface serial command to view the operating status of and statistics on the serial interface. For example:
<HUAWEI> display interface serial 1/0/0/0:0 Serial1/0/0/0:0 current state : Up
Line protocol current state : Up
Description:HUAWEI, Quidway Series, Serial1/0/0/0:0 Interface Route Port,The Maximum Transmit Unit is 1500, Hold timer is 10(sec)
Derived from CPOS 1/0/0 e1 1, Timeslot(s) Used: 1-31, baudrate is 1984000 bps Internet protocol processing : enabled Framer LOS Alarm Status(0-NONE 1-ALARM): 0 Framer LOF Alarm Status(0-NONE 1-ALARM): 1 Framer PAIS Alarm Status(0-NONE 1-ALARM): 1 Framer PRDI Alarm Status(0-NONE 1-ALARM): 0 PSN2TDM PW Alarm status(0-NONE 1-RDI 2-AIS): 0 Statistics last cleared:2011-01-21 10:18:07 09:25:21
As shown by the characters displayed in boldface, the physical status and link layer protocol status of the serial interface are Up when the serial interface channelized from a CPOS interface is correctly configured. If the IP addresses of the serial interfaces on both ends of the link and routes are correctly configured, the network layer protocol status on the local serial interface is enabled.
Step 3 Run the ping command to test CPOS link connectivity. For example:
<HUAWEI> ping 192.168.1.2
PING 192.168.1.2: 56 data bytes, press CTRL_C to break
Reply from 192.168.1.2: bytes=56 Sequence=1 ttl=255 time=2 ms Reply from 192.168.1.2: bytes=56 Sequence=2 ttl=255 time=1 ms Reply from 192.168.1.2: bytes=56 Sequence=3 ttl=255 time=1 ms Reply from 192.168.1.2: bytes=56 Sequence=4 ttl=255 time=1 ms Reply from 192.168.1.2: bytes=56 Sequence=5 ttl=255 time=113 ms
Commissioning Guide 5 Commissioning the Link Layer
192.168.1.2 ping statistics 5 packet(s) transmitted
5 packet(s) received 0.00% packet loss
round-trip min/avg/max = 1/23/113 ms
In normal situations, the ping operation should succeed.
----End
Troubleshooting
If serial interfaces on the two ends of a link cannot communicate with each other after the interfaces are configured, perform the following operations:
1. Check the physical status of the CPOS interfaces on both ends.
a. Check the type of fiber connecting the CPOS interfaces and whether the fiber is correctly installed.
b. If the fiber is correctly and properly installed, run the undo shutdown command and then the display this interface command on the local serial interface. You can see that the physical status of the interface is Up.
c. If the physical status of the interface is Down, run the clock master command and then the loopback local command on the CPOS interface on each end. If the physical status of the interface on each end is Up, the fiber may be faulty. If the physical status of the interface on either end is still Down, the board where the interface resides may be faulty. In this case, seek technical support.
2. Check that the link layer protocol configurations on both ends of the link are consistent.
a. Run the display this interface command on the serial interface on each end to view the configured link layer protocol. If PPP is configured on one end and HDLC is configured on the other end, change the link layer protocol configurations to ensure consistency on both ends.
b. Check whether the MTUs on the serial interfaces on both ends are the same.
Run the display interface interface-type interface-number command on the serial interface on each end to view the MTU. If the MTUs on the serial interfaces on the two ends are not the same, run the mtu command on one end to ensure MTU consistency.
If the fault persists, proceed with the following operations. If the link layer protocol is HDLC, go to Step 3. If the link layer protocol is PPP, go to Step 4.
3. Check that the HDLC configuration is correct.
a. Check whether IP address unnumbered is configured on the serial interfaces on both ends.
Run the display this command on the serial interface on each end to check whether the ip address unnumbered interface interface-type interface-number command has been configured. If that command has been configured, ensure that the IP address borrower can learn the route to its peer. Otherwise, the ping operation will fail.
b. Check whether the same hold time is configured on the two ends.
Run the display interface interface-type interface-number command on the serial interface on each end to view the value of the hold timer field. If different values of
Commissioning Guide 5 Commissioning the Link Layer
the hold timer field are configured on the two ends, run the timer hold command on one end to change the field value and ensure value consistency.
If the fault persists, contact Huawei technical support personnel.
4. Check that PPP works properly between the serial interfaces on the two ends.
Verify that IP addresses are correctly configured for the serial interfaces on the two ends.
Then, run the display this interface command on the serial interface on each end. If the command output shows that the link layer protocol is Down, perform the following operations to find the reason why PPP is not started:
a. Check whether Link Control Protocol (LCP) negotiation goes smoothly.
LCP negotiation is the first phase of the setup of a PPP connection. If LCP negotiation between the two ends succeeds, a link will be set up and some basic link characteristics on the two ends will reach consistency.
Run the display this interface command on the serial interface on either end. The command output shows the LCP negotiation status. If the status is opened, LCP negotiation is completed. Otherwise, LCP negotiation has not been completed yet.
b. Check whether Internet Protocol Control Protocol (IPCP) negotiation goes smoothly.
IPCP negotiation follows successful LCP negotiation and authentication. In this phase, the IP addresses of serial interfaces are negotiated between the two ends. As a prerequisite, the serial interfaces on the two ends must be configured with IP addresses.
Otherwise, the IPCP negotiation status cannot be checked.
After confirming that the IP addresses configured on the serial interfaces on the two ends are correct, run the display this interface command on the serial interface on either end. The command output shows the IPCP negotiation status. If the status is opened, IPCP negotiation is completed. Otherwise, IPCP negotiation has not been completed yet.
5. Check statistics on the serial interfaces on the two ends.
5. Check statistics on the serial interfaces on the two ends.