HUAWEI CX600 Metro Service Platform V600R007C00
Commissioning Guide Issue
04
Date
2014-04-01
HUAWEI TECHNOLOGIES CO., LTD.
Copyright © Huawei Technologies Co., Ltd. 2014. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd. Address:
Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China
Website:
http://www.huawei.com
Email:
[email protected]
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
i
HUAWEI CX600 Metro Service Platform Commissioning Guide
About This Document
About This Document Purpose This document is a guide to CX600 commissioning and verification. It describes how to commission hardware, links, services, and maintenance and management during deployment, ensuring stable and reliable operation of CX600 on networks. The intended audience of this document includes installation and commissioning engineers. NOTE
l This document takes interface numbers and link types of the CX600-X8 as an example. In working situations, the actual interface numbers and link types may be different from those used in this document. l In CX600 series (except for the CX600-X1/X2), line processing boards are called Line Processing Units (LPUs) and switching fabric boards are called Switching Fabric Units (SFUs). The CX600-X1/ X2 has no LPU and SFU, and packet switching and forwarding are centrally performed by the Network Processing Unit (NPU).
NOTICE Note the following precautions: l Currently, the device supports the AES and SHA2 encryption algorithms. AES is reversible, while SHA2 is irreversible. A protocol interworking password must be reversible, and a local administrator password must be irreversible. l If the plain parameter is specified, the password will be saved in plaintext in the configuration file, which has a high security risk. Therefore, specifying the cipher parameter is recommended. To further improve device security, periodically change the password. l Do not set both the start and end characters of a password to "%$%$." This causes the password to be displayed directly in the configuration file.
Related Versions The following table lists the product versions related to this document.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
ii
HUAWEI CX600 Metro Service Platform Commissioning Guide
About This Document
Product Name
Version
HUAWEI CX600 Metro Services Platform
V600R007C00
Intended Audience This document is intended for: l
Data configuration engineers
l
Commissioning engineers
l
Network monitoring engineers
l
System maintenance engineers
Symbol Conventions The symbols that may be found in this document are defined as follows. Symbol
Description Indicates an imminently hazardous situation which, if not avoided, will result in death or serious injury. Indicates a potentially hazardous situation which, if not avoided, could result in death or serious injury. Indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate injury. Indicates a potentially hazardous situation which, if not avoided, could result in equipment damage, data loss, performance deterioration, or unanticipated results. NOTICE is used to address practices not related to personal injury. Calls attention to important information, best practices and tips. NOTE is used to address information not related to personal injury, equipment damage, and environment deterioration.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
iii
HUAWEI CX600 Metro Service Platform Commissioning Guide
About This Document
Command Conventions The command conventions that may be found in this document are defined as follows. Convention
Description
Boldface
The keywords of a command line are in boldface.
Italic
Command arguments are in italics.
[]
Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... }
Optional items are grouped in braces and separated by vertical bars. One item is selected.
[ x | y | ... ]
Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected.
{ x | y | ... }*
Optional items are grouped in braces and separated by vertical bars. A minimum of one item or a maximum of all items can be selected.
[ x | y | ... ]*
Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.
&
The parameter before the & sign can be repeated 1 to n times.
#
A line starting with the # sign is comments.
Change History Changes between document issues are cumulative. The latest document issue contains all the changes made in earlier issues.
Changes in Issue 04 (2014-04-01) The fourth commercial release.
Changes in Issue 03 (2013-11-30) The third commercial release.
Changes in Issue 02 (2013-09-30) The second commercial release.
Changes in Issue 01 (2013-06-15) This issue is the first official release. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
iv
HUAWEI CX600 Metro Service Platform Commissioning Guide
Contents
Contents About This Document.....................................................................................................................ii 1 Commissioning Flow....................................................................................................................1 2 Logging In to the CX600...............................................................................................................3 2.1 Logging In to the CX600 by Using the Console Interface.............................................................................................4 2.2 Logging In to the CX600 by Using Telnet.....................................................................................................................7 2.3 Logging In to the CX600 by Using SSH......................................................................................................................10 2.4 Configuring NAP for Remote Deployment..................................................................................................................20
3 Connecting a Device to the NMS.............................................................................................25 4 Checking the Hardware..............................................................................................................29 4.1 Checking the Software Version....................................................................................................................................30 4.2 Checking the Health Status of the CX600....................................................................................................................31 4.3 Checking the Board Registration Status.......................................................................................................................31 4.4 Checking the Fan Status...............................................................................................................................................34 4.5 Checking the Power Status...........................................................................................................................................34 4.6 Checking System Time.................................................................................................................................................35 4.7 Checking the Interface Status.......................................................................................................................................35 4.8 Checking Alarm Information........................................................................................................................................37 4.9 Checking the Voltage of Each Board...........................................................................................................................38 4.10 Checking the Temperature of Each Board..................................................................................................................39
5 Commissioning the Link Layer................................................................................................41 5.1 Checking Ethernet Interfaces........................................................................................................................................42 5.2 Checking POS Interfaces..............................................................................................................................................44 5.3 Checking CPOS Interfaces...........................................................................................................................................47 5.4 Checking E-Carrier and T-Carrier Interfaces...............................................................................................................50 5.5 Checking ATM Interfaces............................................................................................................................................53 5.6 Checking FR Interfaces................................................................................................................................................55 5.7 Checking the Optical Power of Interfaces....................................................................................................................57
6 Commissioning Services and Protocols..................................................................................59 6.1 Commissioning Static Routes.......................................................................................................................................61 6.2 Commissioning 1588v2................................................................................................................................................63 Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
v
HUAWEI CX600 Metro Service Platform Commissioning Guide
Contents
6.3 Commissioning OSPF Routes......................................................................................................................................67 6.4 Commissioning IS-IS Routes.......................................................................................................................................74 6.5 Commissioning IBGP Routes.......................................................................................................................................78 6.6 Commissioning EBGP Routes......................................................................................................................................84 6.7 Commissioning MPLS LDP.........................................................................................................................................90 6.8 Commissioning MPLS TE............................................................................................................................................95 6.9 Commissioning BGP/MPLS IP VPN...........................................................................................................................99 6.10 Commissioning VPWS.............................................................................................................................................106 6.11 Commissioning VPLS..............................................................................................................................................111 6.12 Commissioning BFD................................................................................................................................................116 6.13 Commissioning IP FRR on the Public Network.......................................................................................................119 6.14 Commissioning VPN IP FRR...................................................................................................................................120 6.15 Commissioning OSPF FRR......................................................................................................................................124 6.16 Commissioning RSVP GR.......................................................................................................................................126 6.17 Commissioning MPLS TE FRR...............................................................................................................................130 6.18 Commissioning CR-LSP Hot Standby.....................................................................................................................136 6.19 Commissioning VPN FRR.......................................................................................................................................140
7 Commission Examples.............................................................................................................143 7.1 Example for Commissioning an IP Bearer Network..................................................................................................144
A List of Interface Attributes.....................................................................................................155 A.1 Interface Attributes of 10Base-T/100Base-TX/1000Base-T-RJ45............................................................................157 A.2 Interface Attributes of 100Base-FX...........................................................................................................................157 A.3 Interface Attributes of 100/1000Base-CSFP.............................................................................................................158 A.4 Interface Attributes of 1000Base-X-SFP...................................................................................................................159 A.5 Interface Attributes of 10GBase LAN/WAN-XFP....................................................................................................160 A.6 Interface Attributes of 10GBase LAN-SFP+.............................................................................................................161 A.7 Interface Attributes of 40GBase-CFP........................................................................................................................162 A.8 Interface Attributes of 100GBase-CFP......................................................................................................................163 A.9 Interface Attributes of OC-3c/STM-1c cPOS-SFP....................................................................................................164 A.10 Interface Attributes of OC-3c/STM-1c POS-SFP...................................................................................................165 A.11 Interface Attributes of OC-12c/STM-4c POS-SFP.................................................................................................166 A.12 Interface Attributes of OC-48c/STM-16c POS-SFP...............................................................................................167 A.13 Interface Attributes of OC-192c/STM-64c POS-XFP.............................................................................................168 A.14 Interface Attributes of OC-768c/STM-256c POS-LC.............................................................................................169 A.15 Interface Attributes of OC-3c/STM-1c ATM-SFP..................................................................................................170 A.16 Interface Attributes of OC-12c/STM-4c ATM-SFP................................................................................................171 A.17 Interface Attributes of CE1/CT1.............................................................................................................................172 A.18 Interface Attributes of E3/T3...................................................................................................................................172
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
vi
HUAWEI CX600 Metro Service Platform Commissioning Guide
1 Commissioning Flow
1
Commissioning Flow
This chapter describes the CX600 commissioning flow. Users can know the entire process of CX600 commissioning in site deployment after reading this section. Figure 1-1 shows the commissioning flow. Figure 1-1 Commissioning flow Logging In to the CX600 Checking the Hardware Commissioning the Link Layer Commissioning Services and Protocols
Table 1-1 describes commissioning procedures. Table 1-1 Commissioning procedures
Issue 04 (2014-04-01)
Commissioning Procedure
Description
Logging In to the CX600
Describes how to log in to the CX600 for later commissioning. Three login methods, login by using the console interface, Telnet, and Secure Shell (SSH), are introduced.
Checking the Hardware
Describes how to check the power supply, fans, boards, and interfaces to prepare for CX600 commissioning.
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
1
HUAWEI CX600 Metro Service Platform Commissioning Guide
Issue 04 (2014-04-01)
1 Commissioning Flow
Commissioning Procedure
Description
Commissioning the Link Layer
Describes how to commission the link layer when the CX600 is connected to otherrouters ortransport devices.
Commissioning Services and Protocols
Describes how to commission services and protocols, especially routing protocols, tunnel services, VPN services, and BFD functions, when the CX600 is connected to other routers or transport devices.
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
2
HUAWEI CX600 Metro Service Platform Commissioning Guide
2 Logging In to the CX600
2
Logging In to the CX600
About This Chapter This chapter describes how to log in to the CX600 for later commissioning. Three login methods, login by using the console interface, Telnet, and SSH, are introduced. NOTE
Command levels are associated with user privilege levels. A user can run only the commands at the same or lower level than the user privilege level. This mechanism ensures device security. For more information about user privilege level configurations, see HUAWEI CX600 Metro Services Platform Configuration Guide - Basic Configurations - Configuring User Login..
2.1 Logging In to the CX600 by Using the Console Interface This section describes how to use the HyperTerminal in Windows on the PC to log in to the CX600 after setting up a local configuration environment with the console interface. 2.2 Logging In to the CX600 by Using Telnet This section describes how to log in to the CX600 by using Telnet. A Telnet operation allows you to log in to a remote device for device management. 2.3 Logging In to the CX600 by Using SSH This section describes how to log in to the CX600 by using SSH. SSH is a secure remote login protocol developed based on the traditional Telnet protocol. Compared with Telnet, SSH is greatly improved in terms of the authentication mode and data transmission security. 2.4 Configuring NAP for Remote Deployment By using NAP, you can log in to a remote new device with empty configuration from a local device to deploy the new device.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
3
HUAWEI CX600 Metro Service Platform Commissioning Guide
2 Logging In to the CX600
2.1 Logging In to the CX600 by Using the Console Interface This section describes how to use the HyperTerminal in Windows on the PC to log in to the CX600 after setting up a local configuration environment with the console interface.
Context Figure 2-1 shows the networking diagram for logging in to the NE80E/40E by using the console interface Figure 2-1 Networking diagram for logging in to the CX600 by using the console interface
PC
CX600
Prerequisite l
The CX600 is running properly.
l
The PC is connected to the CX600 through an asynchronous interface.
l
Installing terminal emulation program on the PC (such as Windows XP HyperTerminal) NOTE
Perform the following configurations on the HyperTerminal on the PC.
Procedure Step 1 Use a serial cable to connect the serial interface on the PC and the console interface on the CX600. For more information about the console interface, see the HUAWEI CX600 Metro Services Platform Hardware Description. Step 2 Start the HyperTerminal on the PC. Choose Start > Programs > Accessories > Communications to start the HyperTerminal in Windows. Step 3 Set up a connection. As shown in Figure 2-2, enter the name of the new connection in the Name text box, and select an icon. Then, click OK.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
4
HUAWEI CX600 Metro Service Platform Commissioning Guide
2 Logging In to the CX600
Figure 2-2 Setting up a connection
Step 4 Set a connection port. In the Connect To dialog box shown in Figure 2-3, select a port from the drop-down list box of Connect using according to the port actually used on the PC or terminal. Then, click OK. Figure 2-3 Setting a connection port
Step 5 Set communication parameters. When the COM1 Properties dialog box is displayed as shown in Figure 2-4, set the COM1 properties according to the description in Figure 2-4 or by clicking Restore Defaults. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
5
HUAWEI CX600 Metro Service Platform Commissioning Guide
2 Logging In to the CX600
NOTE
l Setting the COM1 properties according to the description in Figure 2-4 and setting them by clicking Restore Defaults have the same effect. The default settings of the console interface will be used. l When you log in to the CX600 by using the console interface, ensure that the COM1 properties on the HyperTerminal are consistent with the interface attribute settings on the CX600. Otherwise, the login will fail. This means that if default settings are not used for the interface attributes on the CX600, the COM1 properties on the HyperTerminal must be changed to be consistent with the interface attribute settings on the CX600.
Figure 2-4 Setting communication parameters
----End
Commissioning Result Press Enter. At the following command-line prompt, set an authentication password. The system automatically saves the set password. An initial password is required for the first login via the console. Set a password and keep it safe! Otherwise you will not be able to login via the console. Please configure the login password (6-16) Enter Password: Confirm Password:
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
6
HUAWEI CX600 Metro Service Platform Commissioning Guide
2 Logging In to the CX600
NOTE
l After the password for the user interface is set successfully during the first login, you must enter this password for authentication when you relog in to the system in password authentication mode using this user interface. l The passwords must meet the following requirements: l Password input is in man-machine interaction mode, and the system does not display the entered password. l The password is a string of 6 to 16 case-sensitive characters. The password must contain at least two of the following characters: upper-case character, lower-case character, digit, and special character. Any special character except the question mark (?) and space can be used. The configured password is displayed in ciphertext in the configuration file.
If the login fails, click Disconnect and then Call. If the login still fails, repeat Step 1 to check whether the parameters or physical connections are correct. If they are correct, log in to the CX600 again.
2.2 Logging In to the CX600 by Using Telnet This section describes how to log in to the CX600 by using Telnet. A Telnet operation allows you to log in to a remote device for device management. Figure 2-5 shows the networking diagram for logging in to the CX600 by using Telnet. Figure 2-5 Networking diagram for logging in to the CX600 by using Telnet
network Telnet Client
Telnet Server
Prerequisite l
The CX600 is running properly.
l
The CX600 has been logged in using the console interface and an IP address for each interface has been configured on the CX600.
l
A direct or reachable route exists between the Telnet client and the CX600. NOTE
Use the IP address 129.0.0.1 to telnet to the CX device that is powered on for the first time. Perform the following configurations on the CX600 that serves as the Telnet server:
Procedure Step 1 Set the maximum number of users that are allowed to log in to the CX600 at the same time. 1. Issue 04 (2014-04-01)
Run the system-view command to enter the system view. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
7
HUAWEI CX600 Metro Service Platform Commissioning Guide
2.
2 Logging In to the CX600
Run the user-interface maximum-vty number command to set the maximum number of login users that can use VTY user interfaces on the CX device.
Step 2 Configure a user authentication mode. Two authentication modes are available: password authentication and AAA authentication.One of them can be selected as needed. NOTE
l On the CX device, the default authentication mode is password authentication. l If users with passwords need to be created and managed on the CX device, AAA authentication is recommended.
l Configure password authentication. 1.
Run the system-view command to enter the system view.
2.
Run the user-interface [ ui-type ] first-ui-number [ last-ui-number ] command to enter the user interface view.
3.
Run the set authentication password [ cipher password ] command to set the password used in authentication.
l Configure AAA authentication. 1.
Run the system-view command to enter the system view.
2.
Run the user-interface [ ui-type ] first-ui-number [ last-ui-number ] command to enter the user interface view.
3.
Run the authentication-mode aaa command to configure AAA authentication.
4.
Run the aaa command to enter the AAA view.
5.
Run the local-user user-name password { cipher cipher-password | irreversible-cipher irreversible--password } command to configure the local user name and password. NOTE
Passwords for the administrative FTP, Telnet, SSH, or terminal users can only be in irreversiblecipher. Even if you specify the password in cipher, the device automatically changes it to irreversible-cipher.
6.
Run the quit command to exit from the AAA view.
Step 3 Run the user privilege level level command in the user interface view to control the user rights. ----End
Commissioning Results After the preceding configurations are complete, perform the following operations to check whether the configurations are correct. 1.
Run the Telnet client program on the PC, and enter the IP address of the interface to which you want to connect to.
2.
Enter the user name and password in the login window. If the user is authenticated, a command line prompt such as is displayed. It indicates that you have entered the user view.
Troubleshooting If the Telnet login fails, perform the following operations: Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
8
HUAWEI CX600 Metro Service Platform Commissioning Guide
1.
2 Logging In to the CX600
Check that network connections are proper. Run the ping command on the client to check network connections. If ping results are negative, network connections are faulty and Telnet connections cannot be set up. Check whether unstable connections that cause packet loss or occasional login failures exist in the network. If network connections are faulty, follow the procedure described in "The Ping Operation Fails" in the HUAWEI CX600 Metro Services Platform Troubleshooting to locate and rectify the fault and ensure that the Telnet client can successfully ping the Telnet server.
2.
Check whether login users on the CX600 have reached the maximum. Log in to the CX600 by using the console interface. Then, run the display users command to check whether the VTY user interfaces are all used. By default, a maximum of five VTY user interfaces are available to login users. You can run the display user-interface maximum-vty command to view the allowed maximum number of login users. display user-interface maximum-vty Maximum of VTY user:5 display users User-Intf Delay Type Network Address 34 VTY 0 03:31:35 TEL 10.138.81.138 Username : Unspecified 35 VTY 1 03:51:58 TEL 10.137.128.126 Username : Unspecified 36 VTY 2 00:10:14 TEL 10.138.81.184 Username : Unspecified 37 VTY 3 02:31:58 TEL 10.138.80.199 Username : Unspecified + 38 VTY 4 00:00:00 TEL 10.138.78.80 Username : Unspecified
AuthenStatus pass
AuthorcmdFlag no
pass
no
pass
no
pass
no
pass
no
If login users on the CX600 have reached the maximum, the user-interface maximumvty vty-number command can be run to increase the allowed maximum number of login users that can use VTY user interfaces to 15, and you should configure authentication modes for newly added VTY user interfaces. system-view [HUAWEI] user-interface maximum-vty 15 [HUAWEI] user-interface vty 5 14 [HUAWEI-ui-vty5-14] authentication-mode aaa
3.
Check that an ACL is configured in the VTY user interface view. [HUAWEI] user-interface vty 0 4 [HUAWEI-ui-vty0-4] display this user-interface vty 0 4 acl 2000 inbound authentication-mode aaa user privilege level 3 idle-timeout 0 0
If an ACL is configured but the IP address of a client from which the access is permitted is not specified in ACL rules, the client cannot telnet to the CX600. This means that to allow a client to telnet to the CX600, you must specify the IP address of the client in the permit rule of the ACL bound to VTY user interfaces. 4.
Check that the access protocol has been correctly configured in the VTY user interface view. [HUAWEI] user-interface vty 0 4 [HUAWEI-ui-vty0-4] display this user-interface vty 0 4 authentication-mode aaa user privilege level 3 idle-timeout 0 0 protocol inbound ssh
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
9
HUAWEI CX600 Metro Service Platform Commissioning Guide
2 Logging In to the CX600
The protocol inbound { all | ssh | telnet } command is used to specify protocols supported by the current user interface. telnet is the default parameter. If ssh is specified, Telnet login is prohibited. If all is specified, both Telnet login and SSH login are allowed. 5.
Check whether extended VTY user interfaces 16 to 20 are available to login users. These user interfaces are reserved for NMS users. Whether VTY user interfaces 0 to 14 are all used, VTY user interfaces 16 to 20 are open to NMS users (whose user type is netmanager) only, not common login users. The display users command can be used to check the user login information of every VTY user interface.
6.
Check that a password has been set in the user interface view. If the authentication-mode password command has been run in the VTY user interface view to set the authentication mode to password, the set authentication password command must be run to set an authentication password. The authentication mode can also be set to aaa by running the authentication-mode aaa command.
7.
Check that the user level is correct. If the authentication mode in the VTY user interface view is set to password or none, you need to check the user level. Low-level users, after login, are not allowed to run high-level commands such as the system-view command. If you use an administrator account to log in to the CX600, you can run the user privilege level level command to configure the level of commands that the user logging in through the current user interface can use. NOTE
By default, command levels are 0, 1, 2, and 3. Before the upgrade of command levels, user levels 3 to 15 are the same, which are all management levels.
8.
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
2.3 Logging In to the CX600 by Using SSH This section describes how to log in to the CX600 by using SSH. SSH is a secure remote login protocol developed based on the traditional Telnet protocol. Compared with Telnet, SSH is greatly improved in terms of the authentication mode and data transmission security. Figure 2-6 shows the networking diagram for logging in to the CX600 by using SSH. Figure 2-6 Networking diagram for logging in to the CX600 by using SSH
network
SSH Client
Issue 04 (2014-04-01)
SSH Server
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
10
HUAWEI CX600 Metro Service Platform Commissioning Guide
2 Logging In to the CX600
Prerequisite l
The CX600 is running properly.
l
The CX600 has been logged in using the console interface and an IP address for each interface has been configured on the CX600.
l
A direct or reachable route exists between the SSH client and the CX600. NOTE
Perform the following configurations on the CX600 that serves as the SSH server:
Procedure Step 1 Configure a VTY user interface to support SSH. 1.
Run the system-view command to enter the system view.
2.
Run the user-interface [ ui-type ] first-ui-number [ last-ui-number ] command to enter the user interface view.
3.
Run the authentication-mode aaa command to specify AAA authentication as the authentication mode.
4.
Run the protocol inbound ssh command to configure SSH as the access protocol in the VTY user interface view. NOTE
AAA authentication must be configured in the VTY user interface view; otherwise, the protocol inbound ssh command does not take effect.
Step 2 Run the ssh user user-name command in the system view to create an SSH user. Step 3 In password or RSA authentication mode, create a local user with the SSH user name in the AAA view. 1.
Run the aaa command in the system view to enter the AAA view.
2.
Run the local-user user-name password { cipher cipher-password | irreversible-cipher irreversible--password } command to configure the local user name and password. NOTE
l Passwords for the administrative FTP, Telnet, SSH, or terminal users can only be in irreversiblecipher. Even if you specify the password in cipher, the device automatically changes it to irreversible-cipher. l A default user name root and password Changeme_123 for the initial login have been loaded to the configuration file of the device before delivery. After you log in for the first time, change the user name and password for security.
3.
Run the local-user user-name level level command to configure the priority of the local user.
4.
Run the local-user user-name service-type ssh command to configure the local user access type.
5.
Run the quit command to exit from the AAA view.
Step 4 Create an RSA, DSA, or ECC key pair. Two methods are available. Method 1: Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
11
HUAWEI CX600 Metro Service Platform Commissioning Guide
2 Logging In to the CX600
l Run the rsa local-key-pair create command to create a local RSA key pair. NOTE
l Configure the rsa local-key-pair create command to generate a local key pair before completing other SSH configurations. The minimum length of the server key pair and the host key pair is 512 bits, and the maximum length is 2048 bits. The default length of a local key pair is 2048 bits. After an upgrade, if the original key pair length is shorter than 1024 bits, running the rsa local-key-pair create command to generate a new local key pair is recommended. l After a local key pair is generated, you can run the display rsa local-key-pair public command to view the public key in the local key pair. l To clear the local RSA key pair, run the rsa local-key-pair destroy command to destroy all local RSA key-pairs, including the local key-pair and server key-pair. Check whether all local RSA key pairs are destroyed after running the rsa local-key-pair destroy command. The rsa local-key-pair destroy command configuration takes effect only once and therefore will not be saved in the configuration file.
l Run the dsa local-key-pair create command to generate the RSA local-key-pair. NOTE
l You must configure the dsa local-key-pair create command to generate a local key pair before completing other SSH configurations. The length of the server key pair and the host key pair can be 512 bits, 1024 bits and 2048 bits. By default, the length of the key pair is 2048 bits. l After a local key pair is generated, you can run the display dsa local-key-pair public command to view the public key in the local key pair. l To clear the local DSA key pair, run the dsa local-key-pair destroy command to destroy all local DSA key-pairs, including the local key-pair and server key-pair. Check whether all local DSA key pairs are destroyed after running the dsa local-key-pair destroy command. The dsa local-key-pair destroy command configuration takes effect only once and therefore will not be saved in the configuration file.
l Run the ecc local-key-pair create command to generate the ECC local-key-pair. NOTE
l You must configure the ecc local-key-pair create command to generate a local key pair before completing other SSH configurations. The length of the server key pair and the host key pair can be 256 bits, 384 bits and 521 bits. By default, the length of the key pair is 521 bits. l After a local key pair is generated, you can run the display ecc local-key-pair public command to view the public key in the local key pair. l To clear the local ECC key pair, run the display ecc local-key-pair public command to destroy all local ECC key-pairs, including the local key-pair and server key-pair. Check whether all local ECC key pairs are destroyed after running the ecc local-key-pair destroy command. The ecc local-key-pair destroy command configuration takes effect only once and therefore will not be saved in the configuration file.
Method 2: 1.
Run the rsa key-pair label, dsa key-pair label, or ecc key-pair label command in the system view to create an RSA, DSA, or ECC key pair.
2.
Run the ssh server assign { rsa-host-key | rsa-server-key | dsa-host-key | ecc-hostkey } key-name command in the system view to assign an RSA host key, RSA server key, DSA host key, or ECC host key to an SSH server.
After the key pair is generated, run the display rsa key-pair, display dsa key-pair, or display ecc key-pair command to check information about the RSA, DSA, or ECC key pair. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
12
HUAWEI CX600 Metro Service Platform Commissioning Guide
2 Logging In to the CX600
Step 5 Perform the operations as described in Table 2-1 based on the configured SSH user authentication mode. Table 2-1 Configuring an authentication mode for the SSH user
Issue 04 (2014-04-01)
Operation
Command
Description
Configure Password Authentication
1. Run the ssh user user-name authentication-type password command
If local or HuaWei Terminal Access Controller Access Control System (HWTACACS) authentication is used and there are only a few users, use password authentication.
2. Run the aaa command to enter the AAA view.
-
3. Run the local-user user-name password { cipher | irreversiblecipher } password command to configure the username and the password for the local user.
The username must be the same to the SSH user.
4. Run the local-user user-name service-type ssh command to set the access type of the local user to SSH.
-
Configure the Default Password Authentication
Run the ssh authentication-type default password command
When you log in using SSH and use a TACACS server for authentication, the network administrator needs to specify the information about an SSH user on the TACACS server. In most cases, however, the SSH server cannot obtain the user information from the TACACS server. To resolve this problem, you can run the ssh authentication-type default password command to set the authentication mode as password authentication. Then, you can log in to the device on the SSH server safely.
Configure RSA authentication
1. Run the ssh user user-name authentication-type rsa command to configure RSA authentication.
-
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
By default, the administrators are all in the domain default_admin.
13
HUAWEI CX600 Metro Service Platform Commissioning Guide
Operation
2 Logging In to the CX600
Command
Description
2. Run the rsa peer-public-key keyname [ encoding-type { der | openssh | pem } ] command to configure an encoding format for an RSA public key and enter the RSA public key view.
Huawei data communications devices support only the DER format for RSA keys before V600R006C00 version. If you use an RSA key in non-DER format, use a third-party tool to convert the key into a key in DER format.
The default encoding format is distinguished encoding rules (DER) for an RSA public key.
Because a third-party tool is not released with Huawei system software, RSA usability is unsatisfactory. In addition to DER, RSA keys need to support the privacy-enhanced mail (PEM) and OpenSSH formats to improve RSA usability after V600R006C00 version. Third-party software, such as SecureCRT, PuTTY, OpenSSH, and OpenSSL, can be used to generate RSA keys in different formats. The details are as follows: l The SecureCRT and PuTTY generate RSA keys in PEM format. l The OpenSSH generates RSA keys in OpenSSH format. l The OpenSSL generates RSA keys in DER format.
3. Run the public-key-code begin command to enter the public key edit view.
-
4. Enter hex-data to edit the public key.
l In the public key edit view, only hexadecimal strings complying with the public key format can be typed in. Each string is randomly generated on an SSH client. For detailed operations, see manuals for SSH client software. l After entering the public key edit view, paste the RSA public key generated on the client to the server.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
14
HUAWEI CX600 Metro Service Platform Commissioning Guide
Operation
2 Logging In to the CX600
Command
Description
5. Run the public-key-code end command to exit from the public key edit view.
-
6. Run the peer-public-key end command to return to the system view.
l Running the peer-public-key end command generates a key only after a valid hex-data complying with the public key format is entered. l If the peer-public-key end command is used after the key key-name specified in Step 2 is deleted in another window, the system prompts a message, indicating that the key does not exist, and the system view is displayed.
Configure DSA authentication
7. Run the ssh user user-name assign rsa-key key-name command to assign the SSH user a public key.
-
1. Run the ssh user user-name authentication-type dsa command to configure DSA authentication.
-
2. Run the dsa peer-public-key key-name encoding-type { der | openssh | pem } command to configure an encoding format for a DSA public key and enter the DSA public key view.
Huawei data communications devices support the DER and PEM formats for DSA keys before V600R006C00 version. If you use an RSA key in non-DER/ PEM format, use a third-party tool to convert the key into a key in DER or PEM format. Because a third-party tool is not released with Huawei system software, DSA usability is unsatisfactory. In addition to DER and PEM, DSA keys need to support the OpenSSH format to improve DSA usability after V600R006C00 version.
3. Run the public-key-code begin command to enter the public key edit view.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
-
15
HUAWEI CX600 Metro Service Platform Commissioning Guide
Operation
2 Logging In to the CX600
Command
Description
4. Enter hex-data to edit the public key.
l In the public key edit view, only hexadecimal strings complying with the public key format can be typed in. Each string is randomly generated on an SSH client. For detailed operations, see manuals for SSH client software. l After entering the public key edit view, paste the RSA public key generated on the client to the server.
5. Run the public-key-code end command to exit from the public key edit view.
-
6. Run the peer-public-key end command to return to the system view.
l Running the peer-public-key end command generates a key only after a valid hex-data complying with the public key format is entered. l If the peer-public-key end command is used after the key key-name specified in Step 2 is deleted in another window, the system prompts a message, indicating that the key does not exist, and the system view is displayed.
7. Run the ssh user user-name assign dsa-key key-name command to assign the SSH user a public key.
-
Step 6 Run the ssh user username service-type { sftp | stelnet | all } command in the system view to configure a service type for the SSH user. Step 7 Run the stelnet server enable command in the system view to enable STelnet. ----End
Commissioning Results Log in to the CX600 by using SSH. This section describes only the SSH login by using the PuTTY program. In this example, the IP address of the CX600 is 192.168.1.1; the SSH user name is client001; the password is huawei. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
16
HUAWEI CX600 Metro Service Platform Commissioning Guide
1.
2 Logging In to the CX600
As shown in the following figure, set the IP address of the CX600 to 192.168.1.1 and the login protocol to SSH. Figure 2-7 Login by using the PuTTY program
2.
Issue 04 (2014-04-01)
Enter the user name client001 and the password huawei.
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
17
HUAWEI CX600 Metro Service Platform Commissioning Guide
2 Logging In to the CX600
Figure 2-8 Login by using the PuTTY program
Troubleshooting If the SSH login fails, perform the following operations: 1.
Check that network connections are proper. Check whether unstable connections that cause packet loss or occasional login failures exist in the network. If network connections are improper, follow the procedure described in "The Ping Operation Fails" in the HUAWEI CX600 Metro Services Platform Troubleshooting to locate and rectify the fault and ensure a stable connection between the SSH client and the SSH server.
2.
Check that SSH services are enabled. Run the display ssh server status command to view configurations on the SSH server. display ssh server status SSH version SSH connection timeout SSH server key generating interval SSH Authentication retries SFTP server Stelnet server
:1.99 :60 seconds :0 hours :3 times :Disable :Disable
The command output shows that the SFTP and STelnet servers are not enabled. A user can log in to the CX600 by using SSH only after SSH services are enabled on the CX600. Run the following command to enable the SSH server. system-view [HUAWEI] stelnet server enable
3.
Check that the access protocol has been correctly configured in the VTY user interface view. [HUAWEI] user-interface vty 0 4 [HUAWEI-ui-vty0-4] display this
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
18
HUAWEI CX600 Metro Service Platform Commissioning Guide
2 Logging In to the CX600
user-interface vty 0 4 authentication-mode aaa user privilege level 3 idle-timeout 0 0 protocol inbound ssh
The protocol inbound { all | ssh | telnet } command is used to specify protocols supported by the current user interface. telnet is the default parameter. If telnet is specified, SSH login is prohibited. If ssh or all is specified, SSH login is allowed. 4.
Check that the RSA public key is configured. The CX600 that serves as an SSH server must be configured with a local key pair. Run the display rsa local-key-pair public command to check whether a key pair has been configured on the SSH server. If no key pair has been configured, run the rsa local-keypair create command to create one. [HUAWEI] rsa local-key-pair create The range of public key size is (512 ~ 2048). NOTES: If the key modulus is greater than 512, It will take a few minutes. Input the bits in the modulus[default = 512]: 768 Generating keys... ...........................++++++++ .++++++++ ...............+++++++++ ......+++++++++
5.
Check that the user service type, authentication type, and authentication service type (for password authentication only) have been configured. l Create an SSH user. [HUAWEI] [HUAWEI] [HUAWEI] [HUAWEI]
ssh ssh ssh ssh
user user user user
[email protected] [email protected] authentication-type all
[email protected] service-type all
[email protected] sftp-directory cfcard:/ssh
Configure the same SSH user in the AAA view and set the authentication service type. [HUAWEI] aaa [HUAWEI-aaa] local-user hello@163 password simple abc-pass [HUAWEI-aaa] local-user
[email protected] service-type ssh
l Configure default password authentication for the SSH user. [HUAWEI] ssh authentication-type default password
Configure the same SSH user in the AAA view and set the authentication service type. [HUAWEI] aaa [HUAWEI-aaa] local-user hello@163 password simple abc-pass [HUAWEI-aaa] local-user
[email protected] service-type ssh
6.
Check whether login users on the CX600 have reached the maximum. Like Telnet users, SSH users use VTY user interfaces when logging in to the CX600. The number of available VTY user interfaces ranges from 5 to 15. If the number of login users is greater than 15, a new connection request will be denied by the CX600. Log in to the CX600 by using the console interface. Then, run the display users command to check whether the VTY user interfaces are all used. By default, a maximum of five VTY user interfaces are available to login users. display user-interface maximum-vty Maximum of VTY user:5 display users User-Intf Delay Type Network Address 34 VTY 0 03:31:35 TEL 10.138.81.138 Username : Unspecified 35 VTY 1 03:51:58 TEL 10.137.128.126
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
AuthenStatus pass pass
AuthorcmdFlag no no
19
HUAWEI CX600 Metro Service Platform Commissioning Guide Username : Unspecified 36 VTY 2 00:10:14 Username : Unspecified 37 VTY 3 02:31:58 Username : Unspecified + 39 VTY 4 00:00:00 Username : Unspecified
2 Logging In to the CX600
TEL
10.138.81.184
pass
no
TEL
10.138.80.199
pass
no
TEL
10.138.78.80
pass
no
If login users on the CX600 have reached the maximum, the user-interface maximumvty vty-number command can be run to increase the allowed maximum number of login users that can use VTY user interfaces to 15. system-view [HUAWEI] user-interface maximum-vty 15
7.
Check that an ACL is configured in the VTY user interface view. If an ACL is configured but the IP address of a client from which the access is permitted is not specified in ACL rules, the client cannot log in to the CX600 by using SSH. This means that to allow a client log in to the CX600 by using SSH, you must specify the IP address of the client in the permit rule of the ACL bound to the user interface.
8.
Check the SSH version. Run the display ssh server status command to check the SSH version. display ssh server status SSH version :1.99 SSH connection timeout :60 seconds SSH server key generating interval :0 hours SSH Authentication retries :3 times SFTP server :Disable Stelnet server :Disable
l If the client logs in to the server by using SSHv1, the version compatible capability needs to be enabled on the server. system-view [HUAWEI] ssh server compatible-ssh1x enable
l If the client logs in to the server by using SSHv2, the version compatible capability does not need to be enabled on the server. system-view [HUAWEI] undo ssh server compatible-ssh1x enable
9.
Enable first-time authentication on the SSH client. system-view [HUAWEI] ssh client first-time enable
10. 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
2.4 Configuring NAP for Remote Deployment By using NAP, you can log in to a remote new device with empty configuration from a local device to deploy the new device. Figure 2-9 shows the networking diagram for configuring NAP for remote deployment.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
20
HUAWEI CX600 Metro Service Platform Commissioning Guide
2 Logging In to the CX600
Figure 2-9 Networking diagram for configuring NAP for remote deployment
Network PC
CX-A
CX-B
CX-C
Prerequisite l
Connecting the remote device with empty configuration to a local device directly
l
Making sure that the interfaces connecting the remote device with empty configuration to the local device are Up and support NAP NOTE
If the IP addresses used for establishing NAP connections need to be configured, you need the IP addresses of the master and slave interfaces (the IP addresses must be on the same network segment) before configuring NAP. If the IP addresses for establishing NAP connections are automatically allocated, you do not need any data. Perform the following configurations on the CX device where a NAP function needs to be configured and started.
NOTICE If commands (such as commands related to the VPN, Eth-Trunk, IP-Trunk, or Layer 2 interface) affecting IP address configuration or IP packet forwarding have been run on the NAP master interface, the NAP function will not take effect. In this case, delete these commands and reenable NAP. The IP address of a NAP master interface can be configured or automatically allocated by the system. After the local interface is specified as the NAP master interface, NAP automatically allocates IP addresses from the default address pool 10.167.253.0/24 to the master and slave interfaces. If the address conflict, manually configure addresses for them. There are two configuration modes: to specify a NAP IP address pool, IP addresses from which will be automatically allocated based on a NAP address allocation algorithm, or to configure IP addresses of the same network segment for the master and slave interfaces.
Procedure Step 1 Allocate the IP addresses l
Automatic allocation of IP addresses 1.
Run: system-view
The system view is displayed. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
21
HUAWEI CX600 Metro Service Platform Commissioning Guide
2.
2 Logging In to the CX600
Run: interface interface-type interface-number
The interface view is displayed. 3.
Run: nap port master
The NAP Master interface is configured and started. l
Manual allocation of IP addresses Two methods are available for manually allocating IP addresses. You can choose the method according to actual needs. – You can specify the NAP IP address pool. Then, IP addresses are automatically allocated to the IP address pool. To use this method, do as follows. 1.
Run: system-view
The system view is displayed. 2.
Run: nap ip-pool ip-address mask-length
An IP address pool is configured for NAP. By default, the IP address pool is 10.167.253.0/24. The default value can be modified by running the nap ip-pool ip-address mask-length command. NOTE
The configured IP address pool cannot be changed after NAP has been enabled on the master device.
3.
Run: interface interface-type interface-number
The interface view is displayed. 4.
Run: nap port master
The NAP Master interface is configured and started. – You can also specify the NAP IP addresses. To use this method, do as follows. 1.
Run: system-view
The system view is displayed. 2.
Run: interface interface-type interface-number
The interface view is displayed. 3.
Run: nap port master
The NAP Master interface is configured and started. 4.
Run: nap ip-address local local-ip peer peer-ip mask-length
IP addresses are configured for establishing NAP connections. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
22
HUAWEI CX600 Metro Service Platform Commissioning Guide
2 Logging In to the CX600
Step 2 Logging in to a remote device 1.
Run: system-view
The system view is displayed. 2.
Run: interface interface-type interface-number
The interface view is displayed. 3.
Run: nap login neighbor
Log in to the NAP slave device from the NAP master device. l If the slave device does not have any configuration, you can log in to the slave device from the master device with having to input a user name and a password. l If a user name and a password have been configured on the slave device, you must input the user name and password to log in to the slave device. NOTE
The passwords must meet the following requirements: l The password is a string of 8 to 16 case-sensitive characters. l The password must contain at least two of the following characters: upper-case characters, lower-case characters, numbers, and special characters (excluding question marks and spaces).
After the user name and password are configured for the slave device, NAP will be automatically disabled if the device is restarted. NOTE
The slave device with empty configurations checks the Telnet source address of the Telnet login. If the Telnet source address is the NAP address of the master device, the slave device will require a user to enter the password for login authentication. This is because the user level of the remote login using the NAP address is the same as that (the highest user level) of the login using a console interface.
Step 3 Disabling NAP on the Slave Device 1.
Run: system-view
The system view is displayed. 2.
Run: undo nap slave enable
NAP is disabled on the slave device. ----End
Commissioning Results After NAP has been configured for remote deployment, you can view the current NAP status and the NAP status on an interface. 1.
Run the display nap status command to view the current NAP status. display nap status
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
23
HUAWEI CX600 Metro Service Platform Commissioning Guide Slave port status Nap IP-pool/Mask
2.
2 Logging In to the CX600 : Enable : 10.167.253.0/255.255.255.0
Run the display nap interface [ interface-type interface-number ] command to view the NAP status on an interface. display nap interface gigabitethernet1/0/1
l If the NAP master interface is not assigned an IP address, the following information is displayed: -----------------------------------------------------Port property : Master Current status : DETECTING Local port : GigabitEthernet1/0/1 Peer port : unknown Local IP : NULL Peer IP : NULL Hello time : 3s Linked time : 00:00:00 ------------------------------------------------------
l If the NAP master interface is assigned an IP address, the following information is displayed: -----------------------------------------------------Port property : Master Current status : IP-ASSIGNED Local port : GigabitEthernet1/0/1 Peer port : GigabitEthernet1/0/2 Local IP : 1.1.1.1 Peer IP : 1.1.1.2 Hello time : 3s Linked time : 00:00:08 ------------------------------------------------------
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
24
HUAWEI CX600 Metro Service Platform Commissioning Guide
3
3 Connecting a Device to the NMS
Connecting a Device to the NMS
This chapter describes three methods to connect a device to the NMS. You can connect a device to the NMS using SNMPv1, SNMPv2c, or SNMPv3.
Prerequisite l
The device is running properly.
l
An IP address has been configured for the interface connecting the device to the NMS.
l
A reachable route exists between the CX600 and the NMS.
Data preparation Table 3-1 lists the data required for connecting the device to the NMS. Table 3-1 Data required for connecting the CX600 to the NMS
Issue 04 (2014-04-01)
Item
Data
Remarks
SNMP version of the CX600
V1/V2C/V3
The value can be v1, v2c, or v3.
IP address of the NMS
192.167.1.10
None.
Parameters of SNMPv1, including SNMP read and write community names and the ACL number.
l read community name: comaccess
None.
Parameters of SNMPv2c, including SNMP read and write community names and the ACL number.
l read community name: comaccess
l write community name: mgr l ACL number: 2000 None.
l write community name: mgr l ACL number: 2001
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
25
HUAWEI CX600 Metro Service Platform Commissioning Guide
3 Connecting a Device to the NMS
Item
Data
Remarks
Parameters of SNMPv3, including SNMP group and user names and the ACL number.
l SNMP group name: NMS
None.
l SNMP user name: John l ACL number: 2002
NOTE
SNMPv3 is recommended because it provides more secure functions than other SNMP protocols.
Procedure l
Configure SNMPv1. 1.
Configure basic functions of SNMPv1 on the CX600. # Configure SNMP version. system-view [HUAWEI] snmp-agent [HUAWEI] snmp-agent sys-info version v1
# Set the SNMP community name: the read community name of CX600 is comaccess comaccessand the write community name is mgr. For details, see snmp-agent community. [HUAWEI] snmp-agent community read comaccess acl 2000 [HUAWEI] snmp-agent community write mgr acl 2000
2.
Configure access control in SNMPv1. For more information, please refer to rule (ACL view). [HUAWEI] acl 2000 [HUAWEI-acl-basic-2000] rule permit source 192.167.1.10 0 [HUAWEI-acl-basic-2000] quit
3.
Configure trap functions and set the IP address of the trap server to be the IP address of the NMS, 192.167.1.10. NOTE
The trap function must be configured so that the NMS can receive the alarms from the device. [HUAWEI] snmp-agent trap enable [HUAWEI] snmp-agent target-host trap address udp-domain 192.167.1.10 params securityname comaccess v1 private-netmanager
l
Configure SNMPv2c. 1.
Configure basic functions of SNMPv2c on the CX600. # Configure SNMP version. system-view [HUAWEI] snmp-agent [HUAWEI] snmp-agent sys-info version v2c
# Set the SNMP community name: the read community name of CX600 is comaccess and the write community name is mgr. For details, see snmp-agent community. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
26
HUAWEI CX600 Metro Service Platform Commissioning Guide
3 Connecting a Device to the NMS
[HUAWEI] snmp-agent community read comaccess acl 2001 [HUAWEI] snmp-agent community write mgr acl 2001
2.
Configure Community-Name-based access control in SNMPv2c. For more information, see rule (ACL view). [HUAWEI] acl 2001 [HUAWEI-acl-basic-2001] rule permit source 192.167.1.10 0 [HUAWEI-acl-basic-2001] quit
3.
Configure trap functions and set the IP address of the trap server to be the IP address of the NMS, 192.167.1.10. For more information, see snmp-agent target-host trap. NOTE
The trap function must be configured so that the NMS can receive the alarms from the device. [HUAWEI] snmp-agent trap enable [HUAWEI] snmp-agent target-host trap address udp-domain 192.167.1.10 params securityname comaccess v1 private-netmanager
l
Configure SNMPv3. 1.
Configure basic functions of SNMPv3 on the CX600. CX600 # Configure SNMP version. system-view [HUAWEI] snmp-agent [HUAWEI] snmp-agent sys-info version v3
2.
Configure User-based access control in SNMPv3. # Configure an SNMP user group, and the user group name is NMS. [HUAWEI] snmp-agent group v3 NMS
# Configure user information. For example, Add a user named John to the SNMP group named Johngroup, with the security level being authentication, the authentication protocol being HMAC-MD5-96 and the password being hello. For more information, see the command snmp-agent usm-user. [HUAWEI] snmp-agent usm-user v3 John Johngroup authentication-mode md5 hello
# Configure a basic ACL. For more information, see the command rule (ACL view). [HUAWEI] acl 2002 [HUAWEI-acl-basic-2002] rule permit source 192.167.1.10 0 [HUAWEI-acl-basic-2002] quit
# Apply the ACL based on the user. For more information, see the command snmpagent usm-user. [HUAWEI] snmp-agent usm-user v3 John NMS acl 2002
3.
Configure trap functions and set the IP address of the trap server to be the IP address of the NMS, 192.167.1.10. For more information, see the command snmp-agent target-host trap. NOTE
The trap function must be configured so that the NMS can receive the alarms from the device. [HUAWEI] snmp-agent trap enable [HUAWEI] snmp-agent target-host trap address udp-domain 192.167.1.10 params securityname comaccess v3 private-netmanager
----End Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
27
HUAWEI CX600 Metro Service Platform Commissioning Guide
3 Connecting a Device to the NMS
Commissioning Results After the configurations of the CX600 and the NMS are complete, you can access the CX600 through the NMS.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
28
HUAWEI CX600 Metro Service Platform Commissioning Guide
4 Checking the Hardware
4
Checking the Hardware
About This Chapter This chapter describes how to check the power supply, fans, boards, and interfaces prior to commissioning the CX600. 4.1 Checking the Software Version This section describes how to determine if the software version meets the deployment requirements. 4.2 Checking the Health Status of the CX600 This section describes how to verify whether the current status of the CX600 meets the deployment requirements. 4.3 Checking the Board Registration Status This section describes how to determine whether the boards are properly installed and function normally. 4.4 Checking the Fan Status This section describes how to check whether fans function properly. 4.5 Checking the Power Status This section describes how to verify whether power modules function properly. 4.6 Checking System Time This section describes how to verify whether the system time meets the system requirements. 4.7 Checking the Interface Status This section describes how to verify the interface status. 4.8 Checking Alarm Information This section describes how to verify alarms and faults about the CX600. 4.9 Checking the Voltage of Each Board This section describes how to verify board voltages. 4.10 Checking the Temperature of Each Board This section describes how to verify the board temperature.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
29
HUAWEI CX600 Metro Service Platform Commissioning Guide
4 Checking the Hardware
4.1 Checking the Software Version This section describes how to determine if the software version meets the deployment requirements.
Prerequisites The CX600 has been logged in to. For more information, see 2 Logging In to the CX600.
Procedure Step 1 Run the display version [ slot slot-id ] command to view the version information. display version Huawei Versatile Routing Platform Software VRP (R) software, Version 5.13 (CX600 V600R007C00) Copyright (C) 2000-2010 Huawei Technologies Co., Ltd. HUAWEI CX600-X8 uptime is 0 day, 10 hours, 15 minute CX600 version information:
---- More ---If the version displayed in boldface in the preceding information on the CX600 is consistent with the version required for deployment, go on with the subsequent commissioning. Step 2 Run the display startup command to view the system software and configuration files for the current and next startup. display startup MainBoard: Configured startup system software: Startup system software: Next startup system software: Startup saved-configuration file: Next startup saved-configuration file: Startup paf file: Next startup paf file: Startup license file: Next startup license file: Startup patch package: Next startup patch package: SlaveBoard: Configured startup system software: Startup system software: Next startup system software: Startup saved-configuration file: Next startup saved-configuration file: Startup paf file: Next startup paf file: Startup license file: Next startup license file: Startup patch package: Next startup patch package:
cfcard:/V600R007C00.cc cfcard:/V600R007C00.cc cfcard:/V600R007C00.cc cfcard:/vrpcfg.zip cfcard:/vrpcfg.zip cfcard:/paf-V600R007C00.txt cfcard:/paf-V600R007C00.txt cfcard:/license-V600R007C00.txt cfcard:/license-V600R007C00.txt cfcard:/patch.bat cfcard:/patch.bat cfcard:/V600R007C00.cc cfcard:/V600R007C00.cc cfcard:/V600R007C00.cc cfcard:/vrpcfg.zip cfcard:/vrpcfg.zip cfcard:/paf-V600R007C00.txt cfcard:/paf-V600R007C00.txt cfcard:/license-V600R007C00.txt cfcard:/license-V600R007C00.txt cfcard:/patch.bat cfcard:/patch.bat
If the names of system software and configuration files, displayed in boldface in the preceding information, for the next startup are consistent with that required for deployment, go on with the subsequent commissioning. ----End Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
30
HUAWEI CX600 Metro Service Platform Commissioning Guide
4 Checking the Hardware
Troubleshooting If the software version does not meet the deployment requirement, it needs to be upgraded. NOTE
Before upgrading the software version, contact Huawei technical support personnel or visit http:// support.huawei.com to download the reference documents, including the Version Upgrade Guide, Release Notes, Patch Operation Guide, and Paf&License Selection Guide, and system software that may be used during the upgrade.
4.2 Checking the Health Status of the CX600 This section describes how to verify whether the current status of the CX600 meets the deployment requirements.
Prerequisites The CX600 has been logged in to. For more information, see 2 Logging In to the CX600.
Procedure Step 1 Run the display health command to view the health status of the CX600. display health -----------------------------------------------------------Slot CPU Usage Memory Usage (Used/ Total) -----------------------------------------------------------18 MPU(Master) 16% 43% 438MB/ 1008MB 2 LPU 12% 16% 164MB/ 988MB 6 LPU 26% 27% 275MB/ 988MB 11 LPU 4% 15% 152MB/ 988MB 16 LPU 14% 27% 275MB/ 988MB 19 SFU 18% 48% 13MB/ 28MB 20 SFU 18% 48% 13MB/ 28MB 21 SFU 18% 48% 13MB/ 28MB 22 SFU 16% 48% 13MB/ 28MB 17 MPU(Slave) 9% 34% 350MB/ 1008MB ------------------------------------------------------------
If the CPU usage and memory usage of the boards on the CX600 remain under 80%, as shown by the percentages in boldface in the displayed information, go on with the subsequent commissioning. ----End
Troubleshooting In normal situations, CPU or memory usage should be lower than 80%. If CPU or memory usage remains high before services are deployed in a large scale, contact Huawei technical support personnel.
4.3 Checking the Board Registration Status This section describes how to determine whether the boards are properly installed and function normally. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
31
HUAWEI CX600 Metro Service Platform Commissioning Guide
4 Checking the Hardware
Prerequisites The CX600 has been logged in to. For more information, see 2 Logging In to the CX600.
Procedure Step 1 Run the display device [ pic-status | slot-id ] command to view information about the components installed on the CX600. If [ pic-status | slot-id ] is specified, the command will display information about the Physical Interface Cards (PICs) on all LPUs and information about a specified slot for the LPU, MPU, SFU, power module, or fan module. display device CX600's Device status: Slot # Type Online Register Status Primary --------------------------------------------------------------------------2 LPU Present Registered Normal NA 3 LPU Present Registered Normal NA 4 LPU Present Registered Normal NA 6 LPU Present Registered Normal NA 9 MPU Present Registered NA Master 10 MPU Present Registered Normal Slave 11 SFU Present Registered Normal NA 12 SFU Present Registered Normal NA 13 SFU Present Registered Normal NA 14 SFU Present Registered Normal NA 15 CLK Present Registered Normal Master 16 CLK Present Registered Normal Slave 18 PWR Present Registered Normal NA 19 FAN Present Registered Normal NA 20 FAN Present Registered Normal NA 21 LCD Present Registered Normal NA ---------------------------------------------------------------------------
Pay attention to the Register and Status fields in the displayed information. l Register field: indicates whether a component is successfully registered. The field value can be NA, Registered, or Unregistered. NA indicates that the component must be used during the CX600 startup. Registered indicates that a component is successfully registered. Unregistered indicates that a component is not registered. l Status field: indicates the component status. The field value can be Normal or Abnormal. If the Register field values are Registered or NA and the Status field values are Normal, as shown by the characters in boldface in the preceding displayed information, go on with the subsequent commissioning. ----End
Troubleshooting If the board is not registered, perform the following operations: 1.
Check that the start-up time of the board has expired. The time required for a board to complete registration after it is powered on is called the start-up time. Normally, an LPU can complete the start-up process within 5 minutes. If the system software and related files need to be updated, an LPU can complete the start-up process within 10 minutes.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
32
HUAWEI CX600 Metro Service Platform Commissioning Guide
4 Checking the Hardware
Normally, an SFU can complete the start-up process within 2 minutes. If the system software and related files need to be updated, an SFU can complete the start-up process within 5 minutes. Wait until the start-up time expires. If the board is still unregistered when the start-up time expires, go to Step 2. 2.
Check that the board type is supported by the system software. Supported board types vary with system software versions. For the types of boards that are supported by this software version, see the chapter titled "Boards" in the HUAWEI CX600 Metro Services Platform Hardware Description. If the board type is supported by this system software version but the board cannot be registered, go to Step 3.
3.
Check that the board has been powered on. Run the power on slot ? command in the user view. If "" is displayed, all boards have been powered on. If the slot number of the board is displayed, the board is not powered on. Check whether the power supply of the slot where the board resides is normal. If the indicator on the board is on, the power supply of this slot is normal. l If the power supply of the slot is abnormal, contact Huawei technical support personnel. l If the power supply of the slot is normal but the system still informs that the board is not powered on, the power module on the board is faulty. In this case, you need to replace the board. If the power supply of the board is normal but the board still cannot be registered, go to Step 4.
4.
Upgrade the EPLD of the board. Run the upgrade lpu by-testbus slot-id startup mbus_epld, upgrade lpu by-testbus slot-id startup fad_epld, and upgrade lpu by-testbus slot-id startup lpu_epld commands in the user view to upgrade the EPLD of the LPU. Run the upgrade sfu by-testbus slot-id startup mbus_epld, upgrade sfu by-testbus slotid startup sfu_epld1, and upgrade sfu by-testbus slot-id startup sfu_epld2 commands in the user view to upgrade the EPLD of the SFU. If the board still cannot be registered after the EPLD is upgraded, go to Step 5.
5.
Upgrade the basic BootROM and advanced BootROM of the board. Run the upgrade lpu by-testbus slot-id startup lpu_bootrom, upgrade lpu by-testbus slot-id startup lpu_bootload, upgrade lpu by-testbus slot-id startup fad_bootrom, and upgrade lpu by-testbus slot-id startup fad_bootload commands in the user view to upgrade the basic BootROM and advanced BootROM of an LPU. Run the upgrade sfu by-testbus slot-id startup sfu_bootrom and upgrade sfu bytestbus slot-id startup sfu_bootload commands in the user view to upgrade the basic BootROM and advanced BootROM of the concerned SFU. If the board still cannot be registered after the upgrade, go to Step 6.
6.
If a new board cannot be registered, remove the board and then install it again. If the board still cannot be registered, go to Step 7.
7.
Collect the following information and contact Huawei technical support personnel: l Results of the preceding operation procedure
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
33
HUAWEI CX600 Metro Service Platform Commissioning Guide
4 Checking the Hardware
l Configuration files, log files, and alarm files of the CX600. For more information, see Maintenance Items and Operations to collect the information.
4.4 Checking the Fan Status This section describes how to check whether fans function properly.
Prerequisites The CX600 has been logged in to. For more information, see 2 Logging In to the CX600.
Procedure Step 1 Run the display fan command to check the fan status. display fan Slotid : 19 Present : YES Registered: YES Status : AUTO FanSpeed : [No.]Speed [1]45% Slotid : 20 Present : YES Registered: YES Status : AUTO FanSpeed : [No.]Speed [1]45%
If fan modules are properly installed and successfully registered, as shown by the characters in boldface in the displayed information, go on with the subsequent commissioning. ----End
Commissioning Result The displayed information may be different in real-world situations. For more information, see display fan.
4.5 Checking the Power Status This section describes how to verify whether power modules function properly.
Prerequisites The CX600 has been logged in to. For more information, see 2 Logging In to the CX600.
Procedure Step 1 Run the display power command to check the power status. display power No Present mode State Num ------------------------------------------------------------------------------17 Yes DC Normal 1 18 Yes DC Normal 1
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
34
HUAWEI CX600 Metro Service Platform Commissioning Guide
4 Checking the Hardware
Power monitor cable state: Plug
If the power modules are properly installed and work normally as shown by the characters in boldface in the displayed information, go on with the subsequent commissioning. ----End
Commissioning Result The displayed information may be different in real-world situations. For more information, see display power.
4.6 Checking System Time This section describes how to verify whether the system time meets the system requirements.
Prerequisites The CX600 has been logged in to. For more information, see 2 Logging In to the CX600.
Procedure Step 1 Run the display clock command to view system time. display clock 2010-10-31 19:16:14 Sunday Time Zone(DefaultZoneName) : UTC
If the system time and time zone displayed in boldface in the preceding information are consistent with the local time and time zone, go on with the subsequent commissioning. ----End
Troubleshooting If the system time and time zone displayed in the display clock command output are inconsistent with the local time and time zone, follow the procedure below to reconfigure the system time: 1.
Run the clock datetime [ utc ] HH:MM:SS YYYY-MM-DD command in the user view to set the Universal Time Coordinated (UTC).
2.
Run the clock timezone time-zone-name { add | minus } offset command in the user view to set the time zone based on an offset. (The CX600 obtains the current system time by subtracting an offset from or adding an offset to the UTC.)
3.
(Optional) Run the clock daylight-saving-time time-zone-name repeating start-time { { { first | second | third | fourth | last } weekday month } | start-date } end-time { { { first | second | third | fourth | last } weekday month } | end-date } offset command in the user view to set the daylight saving time.
4.7 Checking the Interface Status This section describes how to verify the interface status. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
35
HUAWEI CX600 Metro Service Platform Commissioning Guide
4 Checking the Hardware
Prerequisites The CX600 has been logged in to. For more information, see 2 Logging In to the CX600.
Procedure Step 1 Run the display interface brief [ main ] command to view brief information about all interfaces on the CX600. The information includes the physical status, protocol status, latest bandwidth usage in the inbound or outbound direction, and number of received or transmitted incorrect packets. display interface brief PHY: Physical *down: administratively down ^down: standby (l):loopback (s):spoofing (b):BFD down (e):EFM down (d):Dampening Suppressed InUti/OutUti: input utility/output utility Interface PHY Protocol InUti Eth-Trunk0 up up 3% GigabitEthernet3/0/0 up up 50% GigabitEthernet3/0/3 *down down 40% GigabitEthernet3/0/1 up up 0% GigabitEthernet3/0/2.1 up up 0% Ip-Trunk1 up up 0%
OutUti 7% 60% 30% 0% 0% 0%
inErrors 12 23 0 0 0 0
outErrors 0 125 0 0 0 0
Ensure that the physical status and protocol status are Up. ----End
Troubleshooting If the physical status is Down, perform the following operations: 1.
Run the display this command on both the local and remote interfaces to check whether they have been shut down. If either one of them or both of them have been shut down, run the undo shutdown command in the interface view. After that, run the display this interface command to check whether the interfaces have gone Up.
2.
At this step, Ethernet interfaces and non-Ethernet interfaces are handled differently. l If Ethernet interfaces are used for connection, check that the rate and duplex mode have been configured on the peer device. Then, set the same rate and duplex mode on the local interface as that on the peer device. After that, run the display this interface command to check whether the interface status is Up. The available commands are as follows: – Run the duplex { full | half | auto } command to configure the half-duplex mode on an Ethernet interface. – Run the speed { 10 | 100 | 1000 | auto } command to configure the rate on an Ethernet interface. l If non-Ethernet interfaces are used for connection, skip this step.
3.
At this step, optical interfaces and electrical interfaces are handled differently. l If optical interfaces are used for connection, skip this step.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
36
HUAWEI CX600 Metro Service Platform Commissioning Guide
4 Checking the Hardware
– Check that the fiber is properly installed. If the fiber is improperly installed, reinstall the fiber. After that, run the display this interface command to check whether the interface status is Up. If the fiber is properly installed but the interface status is Down, perform the next step. – Check that the optical modules on the interfaces of the local match that of peer devices, including interface types, wavelengths, and optical powers of optical modules. If they are not matched, replace optical modules. Then, run the display this interface command to check whether the interface status is Up. l If electrical interfaces are used for connection, check that the network cable is properly installed. If the network cable is improperly installed, reinstall the network cable. After that, run the display this interface command to check whether the interface status is Up. If the network cable is properly installed but the interface status is Down, perform the next step. 4.
If optical interfaces are used for connection, use a fiber or optical modules. If electrical interfaces are used for connection, use a network cable or electrical modules. After that, run the display this interface command to check whether the interface status is Up.
5.
Run the display trapbuffer command to check whether interface-related alarms have been generated. If such alarms have been generated, consult the Alarm Reference of the CX600.
6.
Contact Huawei technical support personnel.
4.8 Checking Alarm Information This section describes how to verify alarms and faults about the CX600.
Prerequisites The CX600 has been logged in to. For more information, see 2 Logging In to the CX600.
Procedure Step 1 Run the display alarm { slot-id | all } command to view all alarms on the CX600 to determine if faults have occurred on the CX600. display alarm all ---------------------------------------------------------------------------NO alarm ----------------------------------------------------------------------------
If the preceding information is displayed, the hardware is not faulty. Otherwise, locate and rectify any found fault based on the contents of the Info field in the command output. Step 2 Run the display trapbuffer[ size value ] [ | count ] [ | { begin| include| exclude} regularexpression] command to view alarms recorded in the trap buffer. Pay attention to the important alarms. display trapbuffer Trapping Buffer Configuration and contents:enabled allowed max buffer size : 1024 actual buffer size : 256 channel number : 3 , channel name : trapbuffer dropped messages : 0 overwritten messages : 131 current messages : 1
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
37
HUAWEI CX600 Metro Service Platform Commissioning Guide
4 Checking the Hardware
#Nov 16 2010 15:33:06 HUAWEI SRM_BASE/1/ENTITYRESUME: OID 1.3.6.1.4.1.2011.5.25 .129.2.1.10 Physical entity is detected resumed from failure. (EntityPhysicalInd ex=16908289, BaseTrapSeverity=2, BaseTrapProbableCause=67719, BaseTrapEventType= 5, EntPhysicalContainedIn=16908288, EntPhysicalName="LPU 2", RelativeResource="S FP", ReasonDescription="LPU 2 is failed, EAGF SFP 0 of PIC0 is abnormal, Resume")
The part displayed in boldface in the preceding information indicates the alarm severity. Note down the alarms and immediately handle the alarms whose alarm severities are 3 or higher. ----End
4.9 Checking the Voltage of Each Board This section describes how to verify board voltages.
Prerequisites The CX600 has been logged in to. For more information, see 2 Logging In to the CX600.
Procedure Step 1 Run the display voltage[ [ lpu | mpu | sfu ] slot slot-id [ pic pic-id ] ] command to view the status of the voltage sensor on each board. display voltage SlotID2 : SlotID: 2 Base-Board, Unit: Volt, Slot2 PCB I2C Addr Chl Status Required LowAlmThreshold HighAlmThreshold Vol Ratio Major Fatal Major Fatal ------------------------------------------------------------------------------FADB 1 0 0 NORMAL 1.50 1.20 1.05 1.80 1.95 1.50 1.00 FADB 1 0 1 NORMAL 1.80 1.44 1.26 2.16 2.34 1.85 1.00 FADB 1 0 2 NORMAL 2.50 2.00 1.75 3.00 3.25 2.77 0.68 FADB 1 0 6 NORMAL 5.00 4.05 3.55 6.07 6.57 5.02 0.38 LPUA 1 0 3 NORMAL 1.30 1.04 0.91 1.56 1.69 1.33 1.00 LPUA 1 0 4 NORMAL 1.30 1.04 0.91 1.56 1.69 1.32 1.00 LPUA 1 0 5 NORMAL 2.50 2.00 1.75 3.00 3.25 2.53 0.76 EAGF 1 3 0 NORMAL 1.80 1.62 1.44 1.98 2.16 1.89 1.00 EAGF 1 3 1 NORMAL 2.50 2.25 2.00 2.75 3.00 2.50 0.76 EAGF 1 3 2 NORMAL 3.30 3.00 2.67 3.67 4.00 3.39 0.58 EAGF 1 3 6 NORMAL 5.00 4.55 4.05 5.57 6.07 5.02 0.38
Pay attention to the values of boldfaced fields displayed. The Required field indicates the ideal voltage. The Vol field indicates the current voltage. The Low_Alam_Threshold Major field indicates the threshold of a low voltage for a minor alarm. If the voltage is below this threshold, a minor alarm will be generated. The Low_Alam_Threshold Fatal field indicates the threshold of a low voltage for a critical alarm. If the voltage is below this threshold, the CX600 may work abnormally or be damaged. The High_Alam_Threshold Major field indicates the threshold of a high voltage for a minor alarm. If the voltage is higher than this threshold, a minor alarm will be generated. The High_Alam_Threshold Fatal field indicates the threshold of a high voltage for a critical alarm. If the voltage is higher than this threshold, the CX600 may work abnormally or be damaged. If the displayed value of the Vol field is between the value of the Low_Alam_Threshold Major field and the value of the High_Alam_Threshold Major field, the board voltage is normal. Then, go on with the subsequent commissioning. ----End Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
38
HUAWEI CX600 Metro Service Platform Commissioning Guide
4 Checking the Hardware
Troubleshooting If the board voltage is below the lower voltage threshold, perform the following operations: 1.
Check that the voltage of power supply is sufficient.
2.
Replace the board and check that the board voltage increases above the lower voltage threshold.
3.
If the fault persists after the preceding operations are complete, contact Huawei technical support personnel.
If the board voltage is higher than the upper voltage threshold, perform the following operations: 1.
Replace the board and check that the board voltage drops below the upper voltage threshold.
2.
If the fault persists after the preceding operations are complete, contact Huawei technical support personnel.
4.10 Checking the Temperature of Each Board This section describes how to verify the board temperature.
Prerequisites The CX600 has been logged in to. For more information, see 2 Logging In to the CX600.
Procedure Step 1 Run the display temperature[ [ lpu | mpu | sfu ] slot slot-id [ pic pic-id ] ] command to view the temperature status on each board. display temperature SlotID2 Base-Board, Unit:C, Slot2 PCB I2C Addr Chl Status Minor Major Fatal Adj_speed Temp TMin Tmax (C) ----------------------------------------------------------------LPUF 1 1 0 NORMAL 70 80 90 60 70 36 LPUF 1 2 0 NORMAL 60 70 80 50 60 33 LPUF 1 4 0 NORMAL 70 80 90 60 70 35 LPUF 1 5 0 NORMAL 80 90 100 70 80 39 LPUF 1 6 0 NORMAL 70 80 90 60 70 38 LPUF 2 76 1 NORMAL 90 96 102 80 90 39 LPUF 2 76 2 NORMAL 90 96 102 80 90 40 TCMB 1 3 0 NORMAL 70 80 90 60 70 34 TCMB 1 7 0 NORMAL 60 70 80 50 60 31
Pay attention to the values of boldfaced fields displayed. The Temp(C) field indicates the current temperature. The Minor field indicates the threshold of a high temperature for a minor alarm. The Major field indicates the threshold of a high temperature for a major alarm. The Fatal field indicates the threshold of a high temperature for a critical alarm. If the board temperature reaches or exceeds the value of the Fatal field, the CX600 may work abnormally or be damaged. If the displayed value of the Temp(C) field is lower than that of the Minor field, the board temperature is normal. Then, go on with the subsequent commissioning. ----End Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
39
HUAWEI CX600 Metro Service Platform Commissioning Guide
4 Checking the Hardware
Troubleshooting If the board temperature exceeds the threshold, perform the following operations: 1.
Check whether fans are faulty and replace any faulty fans.
2.
Check whether the air filter is clogged. If it is clogged, clean it.
3.
Check whether the ambient temperature is too high. If the ambient temperature is too high, lower the temperature in the equipment room.
4.
If the board temperature is still high after the preceding operations, it is due to the high chip temperature. In this case, no action is required or contact Huawei technical support personnel.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
40
HUAWEI CX600 Metro Service Platform Commissioning Guide
5
5 Commissioning the Link Layer
Commissioning the Link Layer
About This Chapter This section describes how to commission the link layer when the CX600 is connected to other routers or transport devices. 5.1 Checking Ethernet Interfaces This section describes how to check the link layer on Ethernet interfaces. 5.2 Checking POS Interfaces This section describes how to check the link layer on POS interfaces. 5.3 Checking CPOS Interfaces This section describes how to check the link layer on CPOS interfaces. 5.4 Checking E-Carrier and T-Carrier Interfaces This section describes how to check the link layer on E-Carrier and T-Carrier interfaces. In this section, a CE1 interface is used as an example. 5.5 Checking ATM Interfaces This section describes how to check the link layer on ATM interfaces. 5.6 Checking FR Interfaces This section describes how to check the link layer on Frame Relay (FR) interfaces. 5.7 Checking the Optical Power of Interfaces This section describes how to verify whether the optical power of SFP optical modules meets requirements.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
41
HUAWEI CX600 Metro Service Platform 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: display interface ethernet brief PHY: Physical *down: administratively down ^down: standby (l): loopback (b): BFD down InUti/OutUti: input utility/output utility Interface Physical Auto-Neg Duplex Trunk GigabitEthernet0/0/0 up enable half -GigabitEthernet2/0/0 up disable full -GigabitEthernet2/0/1 up disable full -GigabitEthernet3/0/2 up enable full --
Bandwidth
InUti
OutUti
100M
0%
0%
1000M
0.01%
0.01%
1000M
0%
0%
1000M
0.01%
0.01%
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: 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
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
42
HUAWEI CX600 Metro Service Platform 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: 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.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
43
HUAWEI CX600 Metro Service Platform 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. l
If the fault persists after the preceding operations are complete, contact Huawei technical support personnel.
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. display interface brief | include Pos PHY: Physical
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
44
HUAWEI CX600 Metro Service Platform Commissioning Guide
5 Commissioning the Link Layer
*down: administratively down ^down: standby (l): loopback (s): spoofing (b): BFD down (e): EFM down (d): Dampening Suppressed InUti/OutUti: input utility/output utility 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: display interface pos 1/0/0 Pos1/0/0 current state : UP Line protocol current state : UP Last line protocol up time : 2011-03-12 22:16:41 Description:HUAWEI, Quidway Series, Pos1/0/0 Interface Route Port,The Maximum Transmit Unit is 4470, Hold timer is 10(sec) Internet Address is 1.0.0.1/24 Link layer protocol is PPP LCP opened, IPCP opened The Vendor PN is FTRJ8519P1BNL-HW The Vendor Name is FINISAR CORP. Port BW: 2.5G, Transceiver max BW: 2.5G, Transceiver Mode: SingleMode WaveLength: 1310nm, Transmission Distance: 5km Rx Power: -5.51dBm, Tx Power: -6.00dBm Physical layer is Packet Over SDH, Scramble enabled, clock master, CRC-32, loopback: none Flag J0 "NetEngine " Flag J1 "NetEngine " Flag C2 22(0x16) The setted port-tx-enabling delay time is: 0 ms The remanent time of enabling port-tx is: 0 ms Last physical up time : 2011-03-12 22:16:35 Last physical down time : 2011-03-12 22:16:34 Current system time: 2011-03-12 22:16:43 SDH alarm: section layer: none line layer: none path layer: none SDH error: section layer: B1 0 line layer: B2 0 REI 0 path layer: B3 0 Statistics last cleared:2010-01-08 17:00:08 Last 30 seconds input rate 22026736 bits/sec, 23333 packets/sec Last 30 seconds output rate 23520304 bits/sec, 23333 packets/sec Input: 800011 packets, 94402078 bytes Input error: 0 shortpacket, 0 longpacket, 0 CRC, 0 lostpacket Output: 800005 packets, 100801469 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets Input bandwidth utilization : 0.01% Output bandwidth utilization : 0.01%
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. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
45
HUAWEI CX600 Metro Service Platform 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: 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.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
46
HUAWEI CX600 Metro Service Platform Commissioning Guide
3.
5 Commissioning the Link Layer
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: 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)
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
47
HUAWEI CX600 Metro Service Platform Commissioning Guide
5 Commissioning the Link Layer
section layer: alarm: none error: B1 0 line layer: alarm: none error: B2 0 REI 0 path layer: alarm: none error: B3 0 REI 0 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: 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 Link layer protocol is PPP LCP initial clock master, loopback none CRC: CRC-32 Current system time: 2011-01-21 17:45:40 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 Traffic statistics: Input: 0 packets Output: 0 packets Output error: 0 underrun count, 0 overrun count 0 misorder packets, 0 malformed packets 0 los packets, 0 dummy packets ES: 0, SES: 0, UAS: 0 Input bandwidth utilization : 0.00% Output bandwidth utilization : 0.00%
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: 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
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
48
HUAWEI CX600 Metro Service Platform 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.
2.
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.
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
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
49
HUAWEI CX600 Metro Service Platform 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. If PPP is started after LCP and IPCP negotiation but the serial interfaces on the two ends still cannot ping each other, check statistics on the serial interfaces to find if the transmission of other types of packets is faulty. NOTE
Authentication is required between LCP negotiation and IPCP negotiation, which can be Password Authentication Protocol (PAP) authentication or Challenge Handshake Authentication Protocol (CHAP) authentication. If authentication fails, the link is disconnected. It is supposed that no authentication is configured in the preceding steps. If authentication is configured in real-world situations, check that the user name and password of the authenticated are correct. In addition, to check that the authentication messages are correctly transmitted and received, enable debugging and check the statistics on the interface.
6.
If the fault persists, contact Huawei technical support personnel.
5.4 Checking E-Carrier and T-Carrier Interfaces This section describes how to check the link layer on E-Carrier and T-Carrier interfaces. In this section, a CE1 interface is used as an example.
Prerequisites l
Issue 04 (2014-04-01)
Hardware installation is complete. For more information, see 4 Checking the Hardware. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
50
HUAWEI CX600 Metro Service Platform Commissioning Guide
l
5 Commissioning the Link Layer
The CX600 is running properly.
Procedure Step 1 Run the display controller e1 command to check the status of a CE1 interface. For example: display controller e1 1/0/0 E1 1/0/0 current state : UP Description : HUAWEI, Quidway Series, E1 1/0/0 Interface Physical layer is Packet Over NO-CRC4 clock master, linecode hdb3 , loopback none section layer: alarm: none line layer: alarm: none path layer: alarm: none 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 CE1 interface status is UP when the CE1 interface is correctly configured, and no alarms or errors are displayed. Step 2 Run the display interface serial command to view the operating status of and statistics on the serial interface. For example: 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 Link layer protocol is PPP LCP initial clock master, loopback none CRC: CRC-32 Current system time: 2011-01-21 17:45:40 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 Traffic statistics: Input: 0 packets Output: 0 packets Output error: 0 underrun count, 0 overrun count 0 misorder packets, 0 malformed packets 0 los packets, 0 dummy packets ES: 0, SES: 0, UAS: 0 Input bandwidth utilization : 0.00% Output bandwidth utilization : 0.00%
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 CE1 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 CE1 link connectivity. For example: 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
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
51
HUAWEI CX600 Metro Service Platform Commissioning Guide Reply Reply Reply Reply
from from from from
192.168.1.2: 192.168.1.2: 192.168.1.2: 192.168.1.2:
5 Commissioning the Link Layer bytes=56 bytes=56 bytes=56 bytes=56
Sequence=2 Sequence=3 Sequence=4 Sequence=5
ttl=255 ttl=255 ttl=255 ttl=255
time=1 ms time=1 ms time=1 ms 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 E-carrier or T-carrier interfaces on both ends of a link cannot communicate with each other after the interfaces are configured, perform the following operations: 1.
Check that the physical layer is Up. a.
Run the display controller e1 command to view interface information on each end. If the physical status is displayed as Administratively Down, the shutdown command has been run on the interface. Run the undo shutdown command to enable the interface. If the physical status is displayed as Down, check the following items: l Fiber is properly connected to the local interface and the indicator for the interface is in a normal state. l Fiber is properly connected to the peer interface. Run the display this interface command in the interface view to check if the physical status of the peer interface is Administratively Down and if loopback is configured on the peer interface. l Interface configurations, such as the operation mode and line coding/decoding format, on the two ends are consistent, and the clock modes configured on the two ends are correct.
b.
If the fault persists, run the link-protocol command in the CE1, serial, CT1, E3, or CT3 interface view to set the link layer protocol to HDLC and then run the loopback command in the CE1, CT1, E3, or CT3 interface view. If the physical status of the interface is Up, the hardware on the local end works properly. The problem lies in the cable, and you need to replace the cable. If the physical status of the interface is Down, the board where the interface resides is faulty. The board needs to be repaired.
2.
Check that the link layer is Up. If the link status is Down, run the display interface serial command on each end to check the link status.
Issue 04 (2014-04-01)
a.
Check whether the two ends use the same link layer protocol. The link layer can go Up only when the two ends of the link use the same link layer protocol.
b.
If the physical layer is Up, check whether correct IP addresses are configured for the interfaces on the two ends.
c.
If the LCP negotiation status is not opened, LCP negotiation has not been completed yet. LCP negotiation is completed only when the LCP negotiation status is opened. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
52
HUAWEI CX600 Metro Service Platform Commissioning Guide
d.
3.
5 Commissioning the Link Layer
If the LCP negotiation status is opened and the IPCP negotiation status is not opened, IPCP negotiation has not been completed. IPCP negotiation is completed only when the IPCP negotiation status is opened.
If the interfaces on the two ends of the link still cannot ping each other even if all configurations are correct, run the display interface serial command to view statistics on the interfaces and contact Huawei technical support personnel.
5.5 Checking ATM Interfaces This section describes how to check the link layer on ATM 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 atm command to check the configurations, physical status, and link layer protocol status on an ATM interface. For example: display interface atm 1/0/0 Atm1/0/0 current state : UP Line protocol current state : UP Last line protocol up time: 2010-11-03, 17:24:24 Description : Atm1/0/0 Interface Route Port, The Maximum Transmit Unit is 1500 Internet protocol processing : disabled AAL enabled: AAL5, Maximum VCs: 2048 VCs on main-interface: 1 (Total VCs: 1) VPs on main-interface: 0 (Total VPs: 1 ) The Vendor Name is FINISAR CORP. , The Vendor PN is FTRJ1321P1BTL Transceiver BW: 2.5G, Transceiver Mode: Single Mode WaveLength: 1310nm, Transmission Distance: 5km Rx Optical Power: -24.95dBm, Tx Optical Power: -1.99dBm Physical layer is Packet Over SDH UBR: 1, CBR: 0, VBR: 0, USED BandWidth: 0Kbps VPI Max: 255, VCI Max: 2047 Scramble enabled, clock master, CRC-32, loopback: none Flag: J0 "NetEngine " Flag: J1 "NetEngine " Flag: C2 19(0x13) SDH alarm: section layer: OOF LOF LOS line layer: AIS path layer: AIS RDI SDH error: section layer: B1: 24 line layer: B2: 0 M1: 0 path layer: B3: 0 G1: 0 Statistics last cleared:never Send good cell: 0 cells Send idle cell: 25099462530 cells Receive idle cell: 0 cells Receive corrected cell: 0 Receive uncorrected cell: 97 Dropped receive cell: 0 cells Last dropped receive cell connection: 0/0 Last 30 seconds input rate: 0 bits/sec, 0 Packets/sec
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
53
HUAWEI CX600 Metro Service Platform Commissioning Guide
5 Commissioning the Link Layer
Last 30 seconds output rate: 0 bits/sec, 0 Packets/sec Input: 0 Bytes, 0 Packets Output: 0 Bytes, 0 Packets
As shown by the characters displayed in boldface, the physical status and link layer protocol status of the ATM interface are UP when the ATM interface is correctly configured. The command output also displays the frame format, clock mode, statistics interval, and whether scrambling is enabled. Step 2 Run the display atm map-info command to check whether information in the upper layer protocol mapping table is correct. display atm map-info Atm1/0/0, PVC 1/33, IP, State UP100.11.1.1, vlink 1 Atm1/0/0, PVC 2/101, ETH, Virtual-Ethernet1/0/0, UP
Step 3 Run the display atm pvc-info command to view PVC information. display atm pvc-info VPI/VCI |STATE|PVC-NAME |INDEX |ENCAP|PROT |INTERFACE --------|-----|----------------|--------|-----|-----|------------------0/40 |UP | |1 |SNAP |IP |Atm1/0/0 (UP) 0/60 |UP |to_adsl_a |2 |SNAP |ETH |Atm1/0/0.1 (UP) VPI/VCI |STATE|PVC-NAME |INDEX |ENCAP|PROT |INTERFACE --------|-----|----------------|--------|-----|-----|------------------1/10 |UP | |2 |SNAP |None |Atm2/0/0.1 (UP) 1/100 |UP | |1 |SNAP |IP |Atm2/0/0 (UP)
Check the boldfaced fields displayed in the preceding information to see if the PVC status is Up, the application mode is correct (in the PROT field, IP indicates IPoA, and ETH indicates IPoEoA), and the interface where the PVC resides is Up. Step 4 Run the display atm pvp-info command to view PVP information. display atm pvp-info VPI | STATE | PVP-NAME | INDEX | ENCAP | PORT | INTERFACE -------------------------------------------------------------------10 | UP | | 0 | AAL0 | None | Atm2/0/0.1(UP)
Check the fields displayed in boldface in the preceding information to see if the PVP status is Up, the application mode is correct (in the PROT field, IP indicates IPoA, and ETH indicates IPoEoA), and the interface where the PVP resides is Up. Step 5 Run the ping command to test ATM link connectivity. For example: 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
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
54
HUAWEI CX600 Metro Service Platform Commissioning Guide
5 Commissioning the Link Layer
Troubleshooting If ATM interfaces on the two ends of a link cannot communicate with each other after the interfaces are configured, perform the following operations: 1.
Enter the ATM interface view and run the display this interface command to check the physical status and link layer protocol status of the ATM interface on each end. If both statuses are Down, go to Step 2. If they are Up, go to Step 3.
2.
Check the physical status, link layer protocol status, and clock mode on the ATM interface on each end. l Check that fiber is correctly connected to the ATM interface. An ATM interface is connected to two fibers. One is used for signal receiving and connected to the receive optical module, and the other is used for signal transmission and connected to the transmit optical module. Ensure that the fiber connections are correct. If the fiber connections are incorrect, the physical status of the ATM interface is Down. If the fiber connections are correct, the Link indicator on the ATM interface is On. l The fiber connected to an ATM interface can be multimode or single-mode fiber. If some ping packets are lost or the ping fails, check whether the ATM interfaces on the two ends are multimode or single-mode interfaces. In most cases, a multimode interface and a single-mode interface that are directly connected can communicate with each other, but sometimes a great number of packets will be discarded or CRC errors will occur. l If two CX600s are directly connected, check whether the internal clocks are not enabled on two ATM interfaces. By default, one CX600 uses a line clock. If the CX600s are directly connected or connected through a WDM device, run the clock master command on one of the CX600s to provide an internal clock. l If the physical status of the interface remains Down, contact Huawei technical support personnel.
3.
Check that the PVCs on the interfaces on both ends are the same. Since ATM interfaces use PVCs for communication, the PVCs on the interfaces on both ends must be the same. For IPoA, check that the protocol address mapping is correctly configured. If two CX600s are directly connected, the PVC mapped from the local to the peer IP address must be the same as the PVC mapped from the peer to the local IP address. Check whether the authentication configurations on both ends are the same for PPPoA.
4.
Check that the configurations and protocol types on the ATM interfaces on the two ends are the same. Check that the protocols (IPoA, PPPoA, IPoEoA, or PPPoEoA) over the PVCs on the ATM interfaces on the two ends are the same. If the routing protocol over ATM is Open Shortest Path First (OSPF), the mapping information configured on the ATM interfaces must contain broadcast. If the ATM interfaces on the two ends can use short packets, but not long packets, to ping each other, check whether the MTUs on the ATM interfaces are the same.
5.
If the ATM interfaces on the two ends still cannot communicate with each other, contact Huawei technical support personnel.
5.6 Checking FR Interfaces This section describes how to check the link layer on Frame Relay (FR) interfaces. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
55
HUAWEI CX600 Metro Service Platform Commissioning Guide
5 Commissioning the Link Layer
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 fr interface command to view the physical status and link layer protocol status of FR interfaces and whether the FR interfaces are DTE or DCE interfaces. The command output also includes the type and link layer protocol status of the sub-interface. display fr interface Pos1/0/0, DCE, physical up, protocol up Pos1/0/0.1, point-to-point, protocol up
Check the information displayed in boldface in the preceding information to ensure that: l The working mode of the FR interface is correct. DTE indicates the working mode of the interface on the user side; DCE indicates the working mode of the interface on the network side. l The physical status and link layer protocol status are Up. l The network layer protocol is Up. l The sub-interface type is point-to-point. Step 2 Run the display fr map-info command to check the FR address mapping table. display fr map-info Map Statistics for interface Pos1/0/0 (DCE) DLCI 20, Point-to-Point DLCI, Pos1/0/0.1 created at: 2010/02/12 11:17:37, status: ACTIVE
Check the information displayed in boldface in the preceding information to ensure that the configured Data-Link Connection Identifier (DLCI) is correct and dynamic address mapping works properly (ACTIVE). Step 3 Run the ping command to test FR link connectivity. For example: 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 an FR interface is Down, check whether the interface is properly connected to a cable. If the network layer protocol status is Down, check whether no DLCI is Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
56
HUAWEI CX600 Metro Service Platform Commissioning Guide
5 Commissioning the Link Layer
configured on the FR interface or its peer interface or the DLCIs configured on both ends are not the same. After changing the link layer configuration of an FR interface, run the shutdown command and then the undo shutdown command to restart the interface and make the configuration take effect. When configuring a DLCI on a sub-interface, you must shut down the sub-interface, configure a DLCI on the sub-interface, and then restart the sub-interface to make the configuration take effect.
5.7 Checking the Optical Power of Interfaces This section describes how to verify whether the optical power of SFP optical modules meets requirements. You need to check whether the optical power of SFP optical modules meets requirements. If the output optical power of SFP optical modules on the boards of the NE80E/40E does not meet requirements, packets will be lost and communication will be interrupted on the network layer.
Prerequisite 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 interface-type interface-number command to view the operating status and statistics on each of two connected interfaces. Go on with the subsequent commissioning, if the maximum transmission distance and central wavelength of the optical modules on the two connected interfaces are consistent and the input optical power and output optical power of the optical modules are within the allowed range. In the following example, the display on a GE interface is used. NOTE
The display this interface command can also be run in the interface view to display interface information. The output of the display interface command and that of the display this interface command are the same. 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
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
57
HUAWEI CX600 Metro Service Platform Commissioning Guide
5 Commissioning the Link Layer
Statistics last cleared: never 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%
Check boldfaced items displayed and ensure that the interface bandwidth, fiber mode, maximum transmission distance, and central wavelength of the optical module are the same as that of its connected optical module on the peer end. Check the output optical power of optical modules on the two ends against the "List of LPU Interface Attributes" to determine if the input optical power is within the allowed range. NOTE
See "List of LPU Interface Attributes" in the appendix. To use the optical module on the local end, the following two conditions for the input optical power of the optical module must be met: l The input optical power must be greater than the receiver sensitivity of the optical module (3dBm). Otherwise, the peer end will not receive any signals. l The input optical power must be lower than the overload optical power (3dBm). Otherwise, the optical module may be damaged.
----End
Troubleshooting If the output optical power of an optical module is beyond the allowed range, replace the optical module.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
58
HUAWEI CX600 Metro Service Platform Commissioning Guide
6
6 Commissioning Services and Protocols
Commissioning Services and Protocols
About This Chapter This chapter describes how to commission services and protocols, specifically, routing protocols, tunnel services, VPN services, and BFD functions used when the CX600 is connected to other routers or transport devices.
Service and Protocol Commissioning Figure 6-1 Flowchart for commissioning services and protocols Commissioning IGP(Static Route, OSPF, ISIS) Commissioning BGP (IBGP, EBGP) Commissioning MPLS LDP, MPLS TE Commissioning VPN (L3VPN, L2VPN) Commissioning BFD
6.1 Commissioning Static Routes This section describes how to commission static routes. 6.2 Commissioning 1588v2 You can select the clock synchronization configuration based on network planning. This section describes how to commission 1588v2. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
59
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
6.3 Commissioning OSPF Routes This section describes how to commission OSPF routes. 6.4 Commissioning IS-IS Routes This section describes how to commission IS-IS routes. 6.5 Commissioning IBGP Routes This section describes how to commission IBGP routes. 6.6 Commissioning EBGP Routes This section describes how to commission EBGP routes. 6.7 Commissioning MPLS LDP This section describes how to commission MPLS LDP. 6.8 Commissioning MPLS TE This section describes how to commission MPLS TE. 6.9 Commissioning BGP/MPLS IP VPN This section describes how to commission BGP/MPLS IP VPN. 6.10 Commissioning VPWS This section describes how to commission VPWS. 6.11 Commissioning VPLS This section describes how to commission VPLS. 6.12 Commissioning BFD This section describes how to commission BFD. 6.13 Commissioning IP FRR on the Public Network This section describes how to commission IP FRR on the public network. 6.14 Commissioning VPN IP FRR This section describes how to commission VPN IP FRR. 6.15 Commissioning OSPF FRR This section describes how to commission OSPF FRR. 6.16 Commissioning RSVP GR This section describes how to commission RSVP GR. 6.17 Commissioning MPLS TE FRR This section describes how to commission MPLS TE FRR. 6.18 Commissioning CR-LSP Hot Standby This section describes how to commission CR-LSP Hot Standby. 6.19 Commissioning VPN FRR In the networking of CE dual-homing, you can configure VPN FRR to ensure the end-to-end VPN service fast switchover if the PE fails, This section describes how to commission VPN FRR.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
60
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
6.1 Commissioning Static Routes This section describes how to commission static routes. You can choose to configure a routing protocol based on the actual network plan.
Prerequisite l
The hardware has been checked. For more information, see 4 Checking the Hardware.
l
The link layer has been commissioned. For more information, see 5 Commissioning the Link Layer.
Context On the network shown in Figure 6-2, static routes are configured on the network to ensure successful communication between the commissioning device and the network connected to CX- B. Figure 6-2 Typical networking for commissioning static routes 1.1.1.1/32
Console PC
2.2.2.2/32
192.168.1.1 / 24 GE1/0/0 network GE2/0/0 GE3/0/0 192.168.1.2 / 24 192.167.1.10 / 24
CX600-A
CX600-B
Procedure Step 1 Run the display ip routing-table command on the commissioning device to check whether the routing table contains static routes. display ip routing-table Route Flags: R - relay, D - download to fib -----------------------------------------------------------------------------Routing Tables: Public Destinations : 6 Routes : 6 Destination/Mask Proto Pre Cost Flags NextHop Interface 1.1.1.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0 192.168.1.0/24 Direct 0 0 D 192.168.1.1 GigabitEthernet0/0/0 127.0.0.0/8 127.0.0.1/32 127.255.255.255/32 192.167.1.0/24
Direct Direct Direct Static
0 0 0 60
0 0 0 0
D D D D
127.0.0.1 127.0.0.1 127.0.0.1 192.168.1.2
InLoopBack0 InLoopBack0 InLoopBack0 GigabitEthernet1/0/0
The boldfaced items in the command output show the information about the static route between the commissioning device and the network connected to CX- B. Step 2 Run the display ip routing-table protocol command on the commissioning device to check route information about the specified routing protocol. display ip routing-table protocol static Route Flags: R - relay, D - download to fib
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
61
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
-----------------------------------------------------------------------------Public routing table : Static Destinations : 1 Routes : 1 Configured Routes : 1 Static routing table status : Destinations : 1 Routes : 1 Destination/Mask Proto Pre Cost Flags NextHop Interface 192.167.1.0/24 Static 60 0 RD 192.168.1.2 GigabitEthernet1/0/0 Static routing table status : Destinations : 0 Routes : 0
The boldfaced items in the command output show the information about the activated static routes. Then check the number of activated static routes, destination network addresses, preferences, costs, next-hop addresses, and outbound interfaces. Step 3 Run the ping command on the commissioning device to test the availability of the static routes. ping 192.167.1.10 PING 192.167.1.10: 56 data Reply from 192.167.1.10: Reply from 192.167.1.10: Reply from 192.167.1.10: Reply from 192.167.1.10: Reply from 192.167.1.10:
bytes, press CTRL_C bytes=56 Sequence=1 bytes=56 Sequence=2 bytes=56 Sequence=3 bytes=56 Sequence=4 bytes=56 Sequence=5
to break ttl=254 time=60 ttl=254 time=65 ttl=254 time=36 ttl=254 time=93 ttl=254 time=23
ms ms ms ms ms
--- 192.167.1.10 ping statistics --5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 23/55/93 ms
The preceding command output shows that the commissioning device has a reachable IS-IS route to the CX- B. ----End
Troubleshooting If static routes are correctly configured but the commissioning device fails to receive some or all routes, complete the following: 1.
Check that static route parameters are correctly configured. Run the display current-configuration | include route-static command to check whether static route parameters are correct and destination addresses, outbound interfaces, and next hops of IPv4 static routes are configured.
2.
Check that the precedence of static routes is correctly configured. Run the display ip routing-table command to check the precedence of static routes in the IPv4 routing table. The precedence of static routes is 60 by default, being lower than OSPF routes (10) and IS-IS routes (15). Therefore, if OSPF or IS-IS is also configured, to make static routes take effect, run the ip route-static default-preference preference command to set the default precedence of static routes to be higher than that of OSPF routes or IS-IS routes before configuring static routes. The smaller the preference value, the higher the preference.
3.
Issue 04 (2014-04-01)
If the fault persists after the preceding operations are complete, contact Huawei technical support personnel.
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
62
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
6.2 Commissioning 1588v2 You can select the clock synchronization configuration based on network planning. This section describes how to commission 1588v2.
Prerequisites The following configurations are complete, and the device functions normally. l
4 Checking the Hardware
l
5 Commissioning the Link Layer
Context On the network shown in Figure 6-3, 1588v2 is configured, and CX-A, CX-B, and CX-C are BC devices. CX-A synchronizes frequency and time signals with the BITS through the clock cable connecting to the MPU. CX-B synchronizes frequency and time signals with CX-A using 1588v2. CX-C synchronizes frequency and time signals with CX-B using 1588v2. Figure 6-3 Commissioning 1588v2
BITS
CX600-A
CX600-B
CX600-C
NodeB
Procedure Step 1 Check whether the GrandMaster device (CX-A) synchronizes frequency and time signals with the BITS. 1.
Run the display clock source command on CX-A to check whether the frequency and time signals are successfully input from the BITS to CX-A. system-view [HUAWEI] sysname CX-A [CX-A] display clock source Master clock source: Source Description Priority Sa-bit * 1 BITS0 19 sa4 2 BITS1 1 sa4 4 LPU2 19 -5 LPU3 19 -6 LPU4 19 --
Issue 04 (2014-04-01)
Input SSM Forcessm Sourcestate unknown on normal unknown on abnormal unknown on normal unknown on normal unknown on normal
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
63
HUAWEI CX600 Metro Service Platform Commissioning Guide 8 11
2.
LPU6 PTP
6 Commissioning Services and Protocols 19 19
---
unknown unknown
abnormal abnormal
Run the display clock config command on CX-A to check whether the CX-A frequency is locked. [CX-A] display clock config Current source: 1 Workmode: manual SSM control: off Primary source: 1 Output SSM Level:bits0:unknown bits1:unknown Current source step into pull-in range Clock is in lock mode
3.
on on
bits2:--
bits3:--
Run the display ptp all command on CX-A to check whether the time source of the 1588v2 module tracks the BITS. [CX-A] display ptp all Device config info -----------------------------------------------------------------PTP state :enabled Domain value :200 Slave only :no Device type :BC Set port state :no Local clock ID :000112fffe345678 Acl :no BMC run info -----------------------------------------------------------------Source port :bits2 Leap :None UTC Offset :0 UTC Offset Valid :True Port info Name State Delay-mech Ann-timeout Type Domain -----------------------------------------------------------------------GigabitEthernet3/0/8 master delay 9 BC 200 Clock source info Clock Pri1 Pri2 Accuracy Class TimeSrc Signal Switch Direction In-Status -----------------------------------------------------------------------local 128 128 0x31 187 0xa0 bits0 128 128 0x20 6 0x20 none on -/abnormal bits1 128 128 0x20 6 0x20 dcls on in/out abnormal bits2 0 128 0x20 6 0x20 1pps on in/normal
Step 2 Run the display ptp all command on CX-A, CX-B, and CX-C to check the 1588v2 protocol status and master and slave status of the 1588v2 interfaces. The bold part in the following command output shows the following information: l CX-A tracks the clock signals output by the BITS, and the 1588v2 interface on CX-A is in the master state. l CX-B tracks the PTP clock signals output by CX-A. The 1588v2 interface connecting CXB to CX-A is in the slave state, and the 1588v2 interface connecting CX-B to CX-C is in the master state. l CX-B tracks the PTP clock signals output by CX-B. The 1588v2 interface connecting CXC to CX-B is in the slave state. On CX-A: [CX-A] display ptp all Device config info -----------------------------------------------------------------PTP state :enabled Domain value :200 Slave only :no Device type :BC
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
64
HUAWEI CX600 Metro Service Platform Commissioning Guide Set port state Acl
6 Commissioning Services and Protocols :no :no
Local clock ID
:000112fffe345678
BMC run info -----------------------------------------------------------------Source port :bits2 Leap :None UTC Offset :0 UTC Offset Valid :True Port info Name State Delay-mech Ann-timeout Type Domain -----------------------------------------------------------------------GigabitEthernet3/0/8 master delay 9 BC 200 Clock source info Clock Pri1 Pri2 Accuracy Class TimeSrc Signal Switch Direction In-Status -----------------------------------------------------------------------local 128 128 0x31 187 0xa0 bits0 128 128 0x20 6 0x20 none on -/abnormal bits1 128 128 0x20 6 0x20 dcls on in/out abnormal bits2 0 128 0x20 6 0x20 1pps on in/normal
On CX-B: system-view [HUAWEI] sysname CX-B [CX-B] display ptp all Device config info -----------------------------------------------------------------PTP state :enabled Domain value :200 Slave only :no Device type :BC Set port state :no Local clock ID :00ffaafffeffbbff Acl :no BMC run info -----------------------------------------------------------------Grand clock ID :000112fffe345678 Receive number :GigabitEthernet4/1/7 Parent clock ID : 000112fffe345678 Parent portnumber :8455 Priority1 :0 Priority2 :128 Step removed :2 Clock accuracy :32 Clock class :6 Time Source :32 UTC Offset :0 UTC Offset Valid :True Time Scale :PTP Time Traceable :True Leap :None Frequence Traceable:False
Port info Name State Delay-mech Ann-timeout Type Domain -----------------------------------------------------------------------GigabitEthernet4/1/7 slave delay 9 BC 200 GigabitEthernet4/1/0 master pdelay 9 BC 200 Time Performance Statistics(ns): Slot 4 Card 1 Port 7 -----------------------------------------------------------------------Realtime(T2-T1) :63 Pathdelay :0 Max(T2-T1) :86 Min(T2-T1) :48 Clock source info Clock Pri1 Pri2 Accuracy Class TimeSrc Signal Switch Direction In-Status -----------------------------------------------------------------------local 128 128 0x31 187 0xa0 bits0 128 128 0x20 6 0x20 none off -/abnormal bits1 128 128 0x20 6 0x20 none off -/abnormal bits2 128 128 0x20 6 0x20 1pps off -/out abnormal
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
65
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
On CX-C: system-view [HUAWEI] sysname CX-C [CX-C] display ptp all Device config info -----------------------------------------------------------------PTP state :enabled Domain value :200 Slave only :no Device type :BC Set port state :no Local clock ID :001882fffe53a56c Acl :no BMC run info -----------------------------------------------------------------Grand clock ID :000112fffe345678 Receive number :GigabitEthernet8/0/0 Parent clock ID :00ffaafffeffbbff Parent portnumber :4352 Priority1 :0 Priority2 :128 Step removed :2 Clock accuracy :32 Clock class :6 Time Source :32 UTC Offset :0 UTC Offset Valid :True Time Scale :PTP Time Traceable :True Leap :None Frequence Traceable:False Port info Name State Delay-mech Ann-timeout Type Domain -----------------------------------------------------------------------GigabitEthernet8/0/0 slave pdelay 9 BC 200 Time Performance Statistics(ns): Slot 8 Card 0 Port 0 -----------------------------------------------------------------------Realtime(T2-T1) :125 Pathdelay :2 Max(T2-T1) :420 Min(T2-T1) :63 Clock source info Clock Pri1 Pri2 Accuracy Class TimeSrc Signal Switch Direction In-Status -----------------------------------------------------------------------local 129 128 0x31 187 0xa0 bits0 128 128 0x20 6 0x20 none off -/abnormal bits1 128 128 0x20 6 0x20 dcls on in/out abnormal bits2 128 128 0x20 6 0x20 1pps on -/out abnormal
Step 3 CX-B and CX-C synchronize the time with their own master devices. Run the display ptp utc command on CX-A, CX-B, and CX-C to check the UTC time. The command output shows that the UTC time synchronization on CX-A, CX-B, and CX-C reaches accuracy in seconds. [CX-A] display ptp utc UTC Time:2012-01-01 14:53:26 [CX-B] display ptp utc UTC Time:2012-01-01 14:53:26 [CX-C] display ptp utc UTC Time:2012-01-01 14:53:26
Run the display ptp all command on CX-B three to five times at an interval of several seconds and check whether the Realtime(T2-T1) field value remains at a fixed value. If so, CX-B has synchronized the time with CX-A. Repeat the preceding operation on CX-C and check whether CX-C synchronizes the time with CX-B. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
66
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
NOTE
When the slave device is in the time synchronization state, the Realtime(T2-T1) field value varies with the type of the subcard where the 1588v2 interface resides and ranges from dozens to hundreds of nanoseconds. The Max(T2-T1) and Min(T2-T1) fields in the display ptp all command output record the maximum and minimum time differences respectively. You can run the reset ptp statistics all command to reset the two fields.
Step 4 Both CX-B and CX-C restore frequency synchronization using 1588v2. On CX-B: [CX-B] display clock Master clock source: Source Description 1 BITS0 2 BITS1 6 LPU4 8 LPU6 * 19 PTP
source Priority 19 19 19 19 19
Sa-bit sa4 sa4 ----
Input SSM unknown unknown unknown unknown unknown
Forcessm on on on on on
Sourcestate abnormal abnormal normal normal normal
Sa-bit sa4 sa4 ----
Input SSM unknown unknown unknown unknown unknown
Forcessm on on on on on
Sourcestate abnormal abnormal normal normal normal
On CX-C: [CX-C] display clock Master clock source: Source Description 1 BITS0 2 BITS1 5 LPU3 10 LPU8 * 11 PTP
source Priority 19 19 19 19 19
----End
6.3 Commissioning OSPF Routes This section describes how to commission OSPF routes. You can choose to configure a routing protocol based on the actual network plan.
Prerequisite l
The hardware has been checked. For more information, see 4 Checking the Hardware.
l
The link layer has been commissioned. For more information, see 5 Commissioning the Link Layer.
Context On the network shown in Figure 6-4, OSPF is configured on the network to ensure successful communication between the commissioning device and the network connected to CX- B. Figure 6-4 Typical networking for commissioning OSPF routes 1.1.1.1/32
Console PC
Issue 04 (2014-04-01)
2.2.2.2/32
192.168.1.1 / 24 GE1/0/0 network GE2/0/0 GE3/0/0 192.168.1.2 / 24 192.167.1.10 / 24
CX600-A
CX600-B
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
67
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Procedure Step 1 Run the display ospf peer command on the commissioning device to view its OSPF neighbor information. display ospf peer OSPF Process 1 with Router ID 1.1.1.1 Neighbors Area 0.0.0.0 interface 192.168.1.1(GigabitEthernet1/0/0)'s neighbors Router ID: 2.2.2.2 Address: 192.168.1.2 State: Full Mode:Nbr is Slave Priority: 1 DR: 192.168.1.1 BDR: 192.168.1.2 MTU: 0 Dead timer due in 35 sec Retrans timer interval: 5 Neighbor is up for 00:00:05 Authentication Sequence: [ 0 ]
The boldfaced items in the command output show the OSPF neighbor information. Then check the number of neighbors, whether or not the neighbor relationships are in the Full state (indicating that the neighbors have finished LSDB synchronization and established the Full adjacency) and whether or not the neighbors can remain in the Up state for a long time. If a neighbor stays in the Up state for a short period of time, the OSPF neighbor relationship has been recently interrupted. Pay attention to such a symptom. Step 2 Run the display ospf routing command on the commissioning device to view information about the OSPF routing table. Intra-area OSPF routes: display ospf routing OSPF Process 1 with Router ID 1.1.1.1 Routing Tables Routing for Network Destination Cost Type NextHop 192.168.1.0/24 1 transit 192.168.1.1 2.2.2.2/32 1 Stub 192.168.1.2 192.167.1.0/24 2 Stub 192.168.1.2 Total Nets: 3 Intra Area: 3 Inter Area: 0 ASE: 0 NSSA: 0
AdvRouter 1.1.1.1 2.2.2.2 2.2.2.2
Area 0.0.0.0 0.0.0.0 0.0.0.0
In the command output, check the destination network addresses, route costs, destination network types, next-hop addresses, routers advertising the routes, AS numbers, and total number of networks of each type. The OSPF routes in the preceding command output are intra-area routes. Inter-area OSPF routes: display ospf routing OSPF Process 1 with Router ID 1.1.1.1 Routing Tables Routing for Network Destination Cost 192.168.1.0/24 1 2.2.2.2/32 1 192.167.1.0/24 2 Routing for ASEs Destination 190.120.0.0/16
Issue 04 (2014-04-01)
Cost 3
Type transit Stub Inter-area
Type Type1
NextHop 192.168.1.1 192.168.1.2 192.168.1.2
Tag 1
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
AdvRouter 1.1.1.1 2.2.2.2 2.2.2.2
Area 0.0.0.0 0.0.0.0 0.0.0.0
NextHop 192.168.1.2
AdvRouter 3.3.3.3
68
HUAWEI CX600 Metro Service Platform Commissioning Guide 200.0.0.0/24
6 Commissioning Services and Protocols 3
Total Nets: 5 Intra Area: 2
Inter Area: 1
Type1
ASE: 2
1
192.168.1.2
3.3.3.3
NSSA: 0
If the commissioning device has learned routes from other areas using OSPF, the routing table will contain them. The boldfaced items in the command output show that there are two intraarea routes, one inter-area route, and two AS external routes. Step 3 Run the display ospf interface command on the commissioning device to view its OSPF interface information. display ospf interface OSPF Process 1 with Router ID 1.1.1.1 Interfaces Area: 0.0.0.0 IP Address 1.1.1.1 192.168.1.1
(MPLS TE not enabled) Type State Cost P2P P-2-P 0 Broadcast DR 1
Pri 1 1
DR 0.0.0.0 192.168.1.1
BDR 0.0.0.0 192.168.1.2
The boldfaced items in the command output show the OSPF interface information. Check that the type, state, and cost of the OSPF-enabled interface are correct. Step 4 Run the display current-configuration command on the commissioning device to check the configurations that have taken effect. display current-configuration # ospf 1 vpn-instance comm_signal default-route-advertise always cost 1024 type 2 import-route direct import-route static route-tag 100 area 0.0.0.0 network 192.168.1.0 0.0.0.255 network 1.1.1.1 0.0.0.0 #
The boldfaced items in the command output show the configurations that have taken effect. Check that the OSPF VPN is correctly configured by checking the configurations of the OSPF process ID, tag value, and default route delivery. Step 5 Run the display ospf error command on the commissioning device to view OSPF errors. display ospf error OSPF Process 1 with Router ID 1.1.1.1 OSPF error statistics General packet errors: 0 : IP: received my own packet 0 : Bad version 0 : Bad area id 0 : Bad virtual link 0 : Bad authentication key 0 : Packet size > ip length 0 : Interface down
0 0 0 0 0 0 0
: : : : : : :
Bad packet Bad checksum Drop on unnumbered interface Bad authentication type Packet too small Transmit error Unknown neighbor
HELLO packet errors: 0 : Netmask mismatch 0 : Dead timer mismatch 0 : Router id confusion 0 : NBMA neighbor unknown
0 0 0 0
: : : :
Hello timer mismatch Extern option mismatch Virtual neighbor unknown Invalid Source Address
DD packet errors: 0 : Neighbor state low
0
: Router id confusion
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
69
HUAWEI CX600 Metro Service Platform Commissioning Guide 0 0
6 Commissioning Services and Protocols
: Extern option mismatch : MTU option mismatch
0
: Unknown LSA type
0
: Unknown LSA type
LS REQ packet errors: 0 : Neighbor state low 0 : Bad request
0
: Empty request
LS UPD packet errors: 0 : Neighbor state low 0 : LSA checksum bad 0 : Unknown LSA type
0 0
: Newer self-generate LSA : Received less recent LSA
Opaque errors: 0 : 9-out of flooding scope 0 : 11-out of flooding scope type
0 0
: 10-out of flooding scope Unkown TLV
LS ACK packet errors: 0 : Neighbor state low
Retransmission for packet over Limitation errors: 0 : Number for DD Packet 0 : Number for Update Packet 0 : Number for Request Packet Receive Grace LSA errors: 0 : Number of invalid LSAs 0 : Number of wrong period LSAs Configuration errors: 0 : Tunnel cost mistake
0
: Number of policy failed LSAs
To locate OSPF faults, you can run this command to view OSPF error information. OSPF error information is a basis for OSPF fault diagnosis. Step 6 Run the ping command on the commissioning device to test the availability of OSPF routes. ping 192.167.1.10 PING 192.167.1.10: 56 data Reply from 192.167.1.10: Reply from 192.167.1.10: Reply from 192.167.1.10: Reply from 192.167.1.10: Reply from 192.167.1.10:
bytes, press CTRL_C bytes=56 Sequence=1 bytes=56 Sequence=2 bytes=56 Sequence=3 bytes=56 Sequence=4 bytes=56 Sequence=5
to break ttl=255 time=3 ttl=255 time=3 ttl=255 time=2 ttl=255 time=3 ttl=255 time=3
ms ms ms ms ms
--- 192.167.1.10 ping statistics --5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 2/2/3 ms
The preceding command output shows that the commissioning device has a reachable OSPF route to the network connected to CX- B. ----End
Troubleshooting If the OSPF neighbor relationship is Down after OSPF is configured, complete the following: 1.
Check logs to find the cause of the Down OSPF neighbor relationship. Run the display logbuffer command to view the following log information: NBR_DOWN_REASON(l): Neighbor state leaves full or changed to Down. (ProcessId= [USHORT], NeighborRouterId=[IPADDR], NeighborAreaId=[ULONG], NeighborInterface=[STRING],NeighborDownImmediate reason=[STRING], NeighborDownPrimeReason=[STRING], NeighborChangeTime=[STRING])
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
70
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Check the NeighborDownImmediate reason field which records the cause of the Down OSPF neighbor relationship. Possible causes are as follows: l Neighbor Down Due to Inactivity It indicates that the local end does not receive any Hello packet from its neighbor within the deadtime, and hence the OSPF neighbor relationship becomes Down. In this case, go to Step 2. l Neighbor Down Due to Kill Neighbor It indicates that the interface or BFD session is in the Down state, or the reset ospf process command is run and hence the OSPF neighbor relationship becomes Down. In this case, check the NeighborDownPrimeReason field to find the specific cause of the fault. – If the NeighborDownPrimeReason field displays Physical Interface State Change, the interface status has changed. In this case, run the display interface [ interface-type [ interface-number ] ] command to check the interface status, and then rectify the interface fault. – If the NeighborDownPrimeReason field displays OSPF Process Reset, the reset ospf process command has been executed. Whether or not this command has been run can be ensured by checking the operation records or log information. – If the NeighborDownPrimeReason field displays BFD Session Down, the BFD session status has become Down. In this case, rectify the BFD fault. l Neighbor Down Due to 1-Wayhello Received or Neighbor Down Due to SequenceNum Mismatch It indicates that the OSPF status on the remote end becomes Down before the remote end sends a 1-Way Hello packet to the local end, causing the OSPF status on the local end to become Down as well. In this case, rectify the fault on the remote end. l In other cases, go to Step 9. 2.
Check that the link between the two ends works normally. Check that the link between the two ends is working normally, including the transmission devices. If the link works properly, go to Step 3.
3.
Check that the CPU usage is within the normal range. Check whether or not the CPU usage on the MPU or LPU of the faulty device is too high. If the CPU usage is too high, OSPF fails to receive and send protocol packets, causing the neighbor relationship to flap. In this case, rectify the high CPU usage fault. If the CPU usage is within the normal range, go to Step 4.
4.
Check that the interface status is Up. Run the display interface [ interface-type [ interface-number ] ] command to check the physical status of the interface. If the physical status of the interface is Down, rectify the interface fault. If the physical status of the interface is Up, run the display ospf interface command to check that the OSPF status of the interface is Up. display ospf interface OSPF Process 1 with Router ID 1.1.1.1 Interfaces Area: 0.0.0.0 IP Address
Type
(MPLS TE not enabled) State Cost
Pri
DR
BDR
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
71
HUAWEI CX600 Metro Service Platform Commissioning Guide 192.168.1.1
6 Commissioning Services and Protocols Broadcast
DR
1
1
192.168.1.1
0.0.0.0
l If the OSPF status of the interface is Down, run the display ospf cumulative command to check whether or not the number of interfaces enabled with OSPF in the OSPF process exceeds the limit. If so, reduce the number of interfaces enabled with OSPF. display ospf cumulative OSPF Process 1 with Router ID 1.1.1.1 Cumulations IO Statistics Type Input Output Hello 28310 134625 DB Description 32 25 Link-State Req 17 9 Link-State Update 1051 657 Link-State Ack 606 982 ASE: (Disabled) LSAs originated by this router Router: 1 Network: 11 Sum-Net: 0 Sum-Asbr: 0 External: 0 NSSA: 0 Opq-Link: 0 Opq-Area: 20 Opq-As: 0 LSAs Originated: 32 LSAs Received: 1448 Routing Table: Intra Area: 11 Inter Area: 0 ASE: 0 Up Interface Cumulate: 6 Neighbor Cumulate: ======================================================= Neighbor cumulative data. (Process 88) ------------------------------------------------------Down: 0 Init: 0 Attempt: 0 2-Way: 0 Exstart: 0 Exchange: 0 Loading: 0 Full: 1 Retransmit Count: 0 Neighbor cumulative data. (Total) ------------------------------------------------------Down: 0 Init: 0 Attempt: 0 2-Way: 0 Exstart: 0 Exchange: 0 Loading: 0 Full: 1 Retransmit Count: 0
l If the OSPF status of the interface is normal (for example, DR, BDR, DR Other, or P2P), go to Step 5. 5.
Check that the IP addresses of the two ends are on the same network segment. l If the IP addresses of the two ends are on different network segments, modify the IP address of one end. l If the IP addresses of the two ends are on the same network segment, go to Step 6.
6.
Check that MTUs of the interfaces on both ends are consistent. If ospf mtu-enable is enabled on the interfaces, the interface MTUs must be consistent. Otherwise, OSPF neighbors cannot negotiate with each other successfully. l If MTUs of the interfaces on both ends are inconsistent, run the mtu mtu command in the interface view to change MTUs of the interfaces to be consistent on both ends. l If the MTUs of the interfaces on both ends are consistent, go to Step 7.
7.
Check that there is at least one interface whose priority is not 0. On the broadcast and NBMA networks, there should be at least one interface whose priority is not 0, which ensures that a DR is elected correctly. Otherwise, the state of the OSPF neighbor relationship can only reach 2-Way.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
72
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Run the display ospf interface command to view the interface priority. display ospf interface OSPF Process 100 with Router ID 1.1.1.41 Interfaces Area: 0.0.0.0 (MPLS TE not enabled) IP Address Type State Cost BDR 192.168.1.1 Broadcast DR 1 0.0.0.0
8.
Pri
DR
1
192.168.1.1
Check that OSPF configurations on both ends are correct. a.
Check whether the OSPF router IDs of the two ends conflict. display ospf brief OSPF Process 1 with Router ID 1.1.1.1 OSPF Protocol Information
If OSPF router IDs of the two ends conflict, correct the configurations. Otherwise, proceed with the following check. b.
Check whether the OSPF area configurations on both ends are consistent. display ospf interface OSPF Process 1 with Router ID 111.1.1.1 Interfaces Area: 0.0.0.0 (MPLS TE not enabled) IP Address Type State Cost BDR 192.168.1.1 Broadcast DR 1 0.0.0.0
c.
Pri
DR
1
192.168.1.1
Check whether other OSPF configurations on both ends are consistent. Run the display ospf error command every 10s for 5 minutes. display ospf error OSPF Process 1 with Router ID OSPF error statistics General packet errors: 0 : IP: received my own packet 0 : Bad version 0 : Bad area id interface 0 : Bad virtual link 0 : Bad authentication key 0 : Packet size > ip length 0 : Interface down HELLO packet errors: 0 : Netmask mismatch 0 : Dead timer mismatch 0 : Router id confusion 0 : NBMA neighbor unknown
1.1.1.1
0 0 0
: Bad packet : Bad checksum : Drop on unnumbered
0 0 0 0
: : : :
Bad authentication type Packet too small Transmit error Unknown neighbor
0 0 0 0
: : : :
Hello timer mismatch Extern option mismatch Virtual neighbor unknown Invalid Source Address
l Check the Bad authentication type field. If the value of this field continually increases, the OSPF authentication types of the two ends that establish the neighbor relationship are different. In this case, you need to set the same authentication type for both ends. l Check the Hello timer mismatch field. If the value of this field continually increases, the values of the Hello timers on the two ends that establish the neighbor relationship are different. In this case, you need to check the interface configurations of the two ends and set the same value for their Hello timers. l Check the Dead timer mismatch field. If the value of this field continually increases, the dead timers on the two ends that establish the neighbor relationship
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
73
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
are different. In this case, you need to check the interface configurations of the two ends and set the same value for their dead timers. l Check the Extern option mismatch field. If the value of this field continually increases, the area types of the two ends that establish the neighbor relationship are different (the area type of one device is common area, and that of the other device is stub area or NSSA). In this case, you need to set the same area type for both ends. If the fault persists, proceed to Step 9. 9.
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 devices
6.4 Commissioning IS-IS Routes This section describes how to commission IS-IS routes. You can choose to configure a routing protocol based on the actual network plan.
Prerequisites l
The hardware has been checked. For more information, see 4 Checking the Hardware.
l
The link layer has been commissioned. For more information, see 5 Commissioning the Link Layer.
Context On the network shown in Figure 6-5, IS-IS is configured on the network to ensure successful communication between the commissioning device and the network connected to CX- B. Figure 6-5 Typical networking for commissioning IS-IS routes 1.1.1.1/32
Console PC
2.2.2.2/32
192.168.1.1 / 24 GE1/0/0 network GE2/0/0 GE3/0/0 192.168.1.2 / 24 192.167.1.10 / 24
CX600-A
CX600-B
Procedure Step 1 Run the display isis peer command on the commissioning device to view its IS-IS neighbor information. display isis peer Peer information for ISIS(1) System Id Interface Circuit Id State HoldTime Type PRI ------------------------------------------------------------------------------0000.0000.0002 GE1/0/0 0000.0000.0002.01 Up 24s L2 64 Total Peer(s): 1
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
74
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
The boldfaced items in the command output show IS-IS neighbor information. Check the number of IS-IS neighbors, whether or not the neighboring interface is in the Up state, and the IS-IS type. Step 2 Run the display isis interface command on the commissioning device to view its IS-IS interface information. display isis interface Interface information for ISIS(1) ----------------------------------Interface Id IPV4.State IPV6.State Loop0 001 Up Down GE1/0/0 001 Up Down
MTU Type DIS 1500 L1/L2 -1497 L1/L2 No/No
The boldfaced items in the command output show the IS-IS interface information. Check that OSPF-enabled interfaces are correctly configured, the number of OSPF-enabled interfaces is correct, and that the IPv4.State of the interfaces is Up. Step 3 Run the display isis route command on the commissioning device to view IS-IS routing information. display isis route Route information for ISIS(1) ------------------------------ISIS(1) Level-2 Forwarding Table ---------------------------------IPV4 Destination IntCost ExtCost ExitInterface NextHop Flags ------------------------------------------------------------------------------192.167.1.0/24 20 NULL GE1/0/0 192.168.1.2 A/-/-/192.168.1.0/24 10 NULL GE1/0/0 Direct D/-/L/Flags: D-Direct, A-Added to URT, L-Advertised in LSPs, S-IGP Shortcut, U-Up/Down Bit Set
Focus on checking that the destination IP addresses, internal costs, outbound interfaces, nexthop addresses, and routing information flags are correct. Step 4 Run the display current-configuration command on the commissioning device to check the configurations that have taken effect. display current-configuration # isis 1 graceful-restart cost-style wide timer lsp-generation 1 level-2 flash-flood level-2 network-entity 0000.0000.0001.01 is-name ngn-r2-b-sxxa-2 import-route isis level-2 into level-1 //Route leaking is required only on the BR but not the AR. nexthop 192.168.1.2 weight 100 //An IS-IS weight is set correctly. (The next hop indicates the peer IP address.) timer spf 1 50 50 traffic-eng level-2 //Enable different levels of TE for different IS-IS processes. On the BR with TE not deployed, this command is not required. log-peer-change #
There is a description following each field in the command output to emphasize the point that needs to be paid attention to. Step 5 Run the ping command on the commissioning device to test the availability of IS-IS routes. ping 192.167.1.10 PING 192.167.1.10: 56 data bytes, press CTRL_C to break Reply from 192.167.1.10: bytes=56 Sequence=1 ttl=255 time=3 ms
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
75
HUAWEI CX600 Metro Service Platform Commissioning Guide Reply Reply Reply Reply
from from from from
192.167.1.10: 192.167.1.10: 192.167.1.10: 192.167.1.10:
6 Commissioning Services and Protocols bytes=56 bytes=56 bytes=56 bytes=56
Sequence=2 Sequence=3 Sequence=4 Sequence=5
ttl=255 ttl=255 ttl=255 ttl=255
time=2 time=2 time=2 time=2
ms ms ms ms
--- 192.167.1.10 ping statistics --5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 2/2/3 ms
The preceding command output shows that the commissioning device has a reachable IS-IS route to the network connected to CX- B. ----End
Troubleshooting If the IS-IS neighbor relationship cannot be established after IS-IS is configured, complete the following: 1.
Check that IS-IS can receive and send Hello packets properly. Run the display isis statistics packet [ interface interface-type interface-number ] command to check that IS-IS can normally receive and send Hello packets. NOTE
The default interval at which IS-IS sends Hello packets is 10s. Therefore, run this command every 10s to check whether or not the packet statistics increase. On a broadcast interface, IS-IS Hello packets have IS-IS levels, and therefore you can view Hello packet statistics based on the levels of established neighbor relationships. On a P2P interface, IS-IS Hello packets have no IS-IS levels and are recorded as L2 IIH packets.
l If the number of received Hello packets does not increase for a certain period, check whether or not packet loss has occurred at the lower layer or at the link between the two ends. l If the number of received Hello packets increases gradually, perform the following operations based on interface types: – If the interfaces on both ends are trunk interfaces, check that the numbers of the trunk member interfaces in the Up state are the same on both ends. – If the interfaces on both ends are not trunk interfaces, go to Step 2. 2.
Check that the interface status is Up. Run the display ip interface [ interface-type interface-number ] command to check the status of a specified interface. l If the interface status is not Up, rectify the interface fault. For detailed troubleshooting procedures, see "Interface & Physical Connection Troubleshooting" and "Layer 2 Network Troubleshooting." l If the interface status is Up, go to Step 3.
3.
Check the status of IS-IS interfaces. Run the display isis interface command to check the status of the interfaces enabled with IS-IS. l If the interface status is Mtu:Dn/Lnk:Up/IP:Up, run the display currentconfiguration interface interface-type [ interface-number ] command to check the MTUs of the interfaces. Run the display current-configuration configuration isis
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
76
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
command to check the LSP length configured in the IS-IS process. On a P2P interface, the LSP length should not be greater than the MTU. On a broadcast interface, the value obtained by subtracting the LSP length from the MTU should be greater than or equal to 3. If these conditions are not met, change the MTU of the interface or the LSP length. l If the interface status is Down, run the display current-configuration configuration isis command to check the configuration of the IS-IS process. Check that the NET is configured in the IS-IS process. If not, configure the NET in the IS-IS process. l If the interface status is Mtu:Up/Lnk:Dn/IP:Dn, check that IS-IS interfaces are configured with IP addresses. l If the interface status is Up, go to Step 4. 4.
Check that the IP addresses of the two ends are on the same network segment. l If the IP addresses of the two ends are on different network segments, modify the IP address of one end. l If the IP addresses of the two ends are on the same network segment, go to Step 5.
5.
Check that both ends are configured with different system IDs. Run the display current-configuration configuration isis command to check whether or not the system IDs of the two ends are the same. l If the system IDs of the two ends are the same, set different system IDs for each end. l If the system IDs of the two ends are different, go to Step 6.
6.
Check that the IS-IS levels of the two ends are consistent. Run the display current-configuration configuration isis | include is-level command to check the levels of the IS-IS processes on both ends. Then, run the display currentconfiguration interface interface-type interface-number | include isis circuit-level command to check whether or not the IS-IS levels of the interfaces at both ends are consistent. The IS-IS neighbor relationship can only be established when the IS-IS levels of the two interfaces are consistent. l If the IS-IS levels of the interfaces at both ends are inconsistent, run the is-level command in the IS-IS view to change the IS-IS level of one end, or run the isis circuitlevel command in the interface view to change the IS-IS level of the interface. l If the IS-IS levels of the interfaces at both ends are consistent, go to Step 7.
7.
Check that the area addresses of the two ends are the same. When the area addresses of the two ends are different, the alarm isisAreaMismatch is generated. NOTE
If the two ends establish a Level-1 neighbor relationship, ensure that they are both in the same area. An IS-IS process can be configured with a maximum of three area addresses. As long as one of the area addresses of the local IS-IS process is the same as one of the area addresses of the remote IS-IS process, the Level-1 neighbor relationship can be established. When an IS-IS Level-2 neighbor relationship is established between two ends, you do not need to determine whether or not the area addresses of the two ends are the same.
l If the area addresses of the two ends are different, run the network-entity command in the IS-IS view to set the same area address for both ends. l If the area addresses of the two ends are the same, go to Step 8. 8. Issue 04 (2014-04-01)
Check that the authentication configurations on the two ends are the same. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
77
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
If the authentication modes configured on the two ends are different, the alarm isisAuthenticationTypeFailure or isisAuthenticationFailure is generated. Run the display current-configuration interface interface-type interface-number | include isis authentication-mode command to check IS-IS authentication configurations on the interfaces of the two ends. l If the authentication modes configured on both are different, run the isis authenticationmode command in the IS-IS interface view on both ends to set the same authentication mode. l If the authentication password configured on both are different, run the isis authentication-mode command in the IS-IS interface view on both ends to set the same authentication password. l If the authentication modes configured on both ends are the same, go to Step 9. 9.
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 devices
6.5 Commissioning IBGP Routes This section describes how to commission IBGP routes. You can choose to configure the BGP routing protocol based on the actual network plan.
Prerequisites l
The hardware has been checked. For more information, see 4 Checking the Hardware.
l
The link layer has been commissioned. For more information, see 5 Commissioning the Link Layer.
Context On the network shown in Figure 6-6, IBGP is configured on the network to ensure successful communication between the commissioning device and the network connected to CX- B. Figure 6-6 Typical networking for commissioning IBGP routes 1.1.1.1/32
Console PC
2.2.2.2/32
192.168.1.1 / 24 GE1/0/0 network GE2/0/0 GE3/0/0 192.168.1.2 / 24 192.167.1.10 / 24
CX600-A
CX600-B
AS100
Procedure Step 1 Run the display bgp peer command to view IBGP peer information. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
78
HUAWEI CX600 Metro Service Platform Commissioning Guide display BGP local router Local AS number Total number of Peer V PrefRcv 2.2.2.2 4
6 Commissioning Services and Protocols
bgp peer ID : 1.1.1.1 : 100 peers : 1 AS MsgRcvd 100
MsgSent
274
7
Peers in established state : 1 OutQ Up/Down State 14
03:07:01 Established
3
The boldfaced items in the command output show the IBGP peer information. Check that the IBGP peer address and AS number are correct. Normally, the IBGP peer relationship should be in the Established state. Step 2 Run the display bgp routing-table command on the commissioning device to view IBGP routing information. l View all IBGP routing information: display bgp routing-table BGP Local router ID is 1.1.1.1 Status codes: * - valid, > - best, d - damped, h - history, i - internal, s - suppressed, S Stale Origin : i - IGP, e - EGP, ? - incomplete ............................................................. Total Number of Routes: 1 Network NextHop MED LocPrf PrefVal Path/ Ogn *> 2.2.2.2/32 0.0.0.0 1 0 ? *> 192.168.1.0/24 0.0.0.0 0 0 ? * i 2.2.2.2 0 0 i *> 192.168.1.1/32 0.0.0.0 0 0 ? *> 192.167.1.0/24 0.0.0.0 0 0 ? * i 2.2.2.2 0 100 0 i *> 1.1.1.1/32 0.0.0.0 0 0 ? *> 127.0.0.0 0.0.0.0 0 0 ? *> 127.0.0.1/32 0.0.0.0 0 0 ?
Check that the network addresses, next-hop addresses, metrics, and local preferences of BGP routes are correct. The boldfaced items in the command output show the default route and specific routes received from AS 300, summarized routes received from AS 400, and that the local preference of the routes received from AS 300 and AS 400 is set to 100 by the configured routing policy. l View detailed information about the specified IBGP routes: display bgp routing-table 192.167.1.0 BGP local router ID : 1.1.1.1 Local AS number : 100 Paths: 1 available, 1 best, 1 select BGP routing table entry information of 192.167.1.0/24: Imported route. From: 2.2.2.2 (2.2.2.2) Route Duration: 00h14m33s Direct Out-interface: GigabitEthernet1/0/0 Original nexthop: 2.2.2.2 Qos information : 0x0 Community:no-export AS-path Nil, origin igp, MED 0, localpref 100, pref-val 0, valid, internal, best, select, pre 255 Not advertised to any peer yet
The boldfaced items in the command output show the detailed information about the specified IBGP routes. Check that the local router IDs, AS numbers, sources of IBGP routes, outbound interfaces, and next-hop addresses are correct. The IBGP routes in the command output have community attributes, which prevents CX- A from advertising the routes received from CX- B to other ASs. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
79
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
l View information about the routes with community attributes: display bgp routing-table community BGP Local router ID is 1.1.1.1 Status codes: * - valid, > - best, d - damped, h - history, i - internal, s - suppressed, S - Stale Origin : i - IGP, e - EGP, ? - incomplete Total Number of Routes: 1 Network NextHop *>i 192.167.1.0 2.2.2.2
MED 0
LocPrf 100
PrefVal Community 0 no-export
l Commissioning the RR of IBGP routes: CX- B is the RR of cluster 1 and CX- A is the client of CX- B. 192.167.1.0/24 is the network address of non-clients. display bgp routing-table 192.167.1.0 BGP local router ID : 1.1.1.1 Local AS number : 100 Paths: 1 available, 1 best, 1 select BGP routing table entry information of 192.167.1.0/24: From: 2.2.2.2 (2.2.2.2) Route Duration: 00h14m33s Direct Out-interface: GigabitEthernet1/0/0 Original nexthop: 2.2.2.2 Qos information : 0x0 Community:no-export AS-path Nil, origin igp, MED 0, localpref 100, pref-val 0, valid, internal, best, select, pre 255 Originator: 4.4.4.4 Cluster list: 0.0.0.1 Not advertised to any peer yet
The boldfaced items in the command output show that CX- A has learned routes of the network segment 192.167.1.0 advertised by CX- B, and shows the Originator and Cluster_ID of the learned routes. Step 3 Run the display bgp peer ipv4-address verbose command to view the configurations of GTSM and GR functions for IBGP. display bgp peer 2.2.2.2 verbose BGP Peer is 2.2.2.2, remote AS 100 Type: IBGP link BGP version 4, Remote router ID 2.2.2.2 Update-group ID : 1 BGP current state: Established, Up for 00h49m35s BGP current event: KATimerExpired BGP last state: OpenConfirm BGP Peer Up count: 1 Received total routes: 1 Received active routes total: 1 Advertised total routes: 2 Port: Local - 179 Remote - 52876 Configured: Active Hold Time: 180 sec Keepalive Time:60 sec Received : Active Hold Time: 180 sec Negotiated: Active Hold Time: 180 sec Keepalive Time:60 sec Peer optional capabilities: Peer supports bgp multi-protocol extension Peer supports bgp route refresh capability Peer supports bgp 4-byte-as capability Graceful Restart Capability: advertised Address family IPv4 Unicast: advertised and received Received: Total 59 messages Update messages 0 Open messages 2 KeepAlive messages 57 Notification messages 0 Refresh messages 0
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
80
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Sent: Total 79 messages Update messages 5 Open messages 2 KeepAlive messages 71 Notification messages 1 Refresh messages 0 Authentication type configured: None Last keepalive received: 2010-02-20 13:54:58 Minimum route advertisement interval is 30 seconds Optional capabilities: Route refresh capability has been enabled 4-byte-as capability has been enabled Connect-interface has been configured GTSM has been enabled, valid-ttl-hops: 1 Peer Preferred Value: 0 Routing policy configured: No routing policy is configured
The boldfaced items in the command output show that the GTSM function has been enabled, the number of valid hops is 1, the BGP peer relationship is in the Established state, and the GR function is enabled for IBGP. Step 4 Run the ping command on the commissioning device to test the availability of IBGP routes. ping 2.2.2.2 PING 2.2.2.2: 56 data bytes, press CTRL_C to break Reply from 2.2.2.2: bytes=56 Sequence=1 ttl=254 time=70 Reply from 2.2.2.2: bytes=56 Sequence=2 ttl=254 time=65 Reply from 2.2.2.2: bytes=56 Sequence=3 ttl=254 time=64 Reply from 2.2.2.2: bytes=56 Sequence=4 ttl=254 time=90 Reply from 2.2.2.2: bytes=56 Sequence=5 ttl=254 time=25
ms ms ms ms ms
--- 2.2.2.2 ping statistics --5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 25/63/90 ms
2.2.2.2 is the loopback address of CX- B. ----End
Troubleshooting If the BGP peer relationship cannot be established on a BGP-deployed network, complete the following: 1.
Run the ping command to check that BGP peers can ping each other successfully. l If they can ping each other successfully, it indicates that there are available routes between the BGP peers and that link transmission is normal. Proceed to Step 2. NOTE
Run the ping -a source-ip-address -s packetsize host command to detect the connectivity of each end. Because the source address is specified in this command, you can check whether or not routes between the two ends are accessible. By specifying the size of a Ping packet, you can also check whether or not long Ping packets can be normally transmitted over the link.
l If the ping fails, follow the procedure described in "The Ping Operation Fails" in the HUAWEI CX600 Metro Services Platform Troubleshooting to find whether or not the routing tables on each end have available routes to each other. 2. Issue 04 (2014-04-01)
Check that no ACL is configured to filter packets whose destination port is TCP port 179. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
81
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Run the display acl all command on both ends to check whether or not an ACL is configured to filter packets whose destination port is TCP port 179. display acl all Total nonempty ACL number is 1 Advanced ACL 3001, 2 rules Acl's step is 5 rule 5 deny tcp source-port eq bgp rule 10 deny tcp destination-port eq bgp
l If an ACL is configured to filter packets whose destination port is TCP port 179, delete the ACL configuration. l If no ACL is configured to filter packets whose destination port is TCP port 179, go to Step 3. 3.
Check that the peer router ID does not conflict with the local router ID. Check information about BGP peers to ensure that their router IDs do not conflict. For example, if the IPv4 unicast peer relationship fails to be established, you can run the display bgp peer command to check whether or not the peer router ID conflicts with the local router ID. Use the following command output as an example: display BGP local router Local AS number Total number of Peer PrefRcv 8.9.0.8 10000 9.10.0.10 9999
bgp peer ID : 223.5.0.109 : 41976 peers : 12
Peers in established state : 4
V
AS
MsgRcvd
4
100
1601
4
200
1565
MsgSent 1443 1799
OutQ
Up/Down
State
0 23:21:56 Established 0 23:15:30 Established
NOTE
To check information about BGP peers in the BGP-VPNv4 address family or the BGP-VPN instance address family, you can run the display bgp vpnv4 all peer command.
l If the peer router ID conflicts with the local router ID, run the router id command in the BGP view to modify the router IDs to agree. Generally, a loopback interface address is used as the local router ID. l If the peer router ID does not conflict with the local router ID, go to Step 4. 4.
Check that the peer AS number is configured correctly. Run the display bgp peer command on each end to check that the displayed peer AS number is the same as that of the remote end. display bgp peer BGP local router ID : 223.5.0.109 Local AS number : 41976 Total number of peers : 12 Peer PrefRcv 8.9.0.8 10000 9.10.0.10 9999
Peers in established state : 4
V
AS
MsgRcvd
4
100
1601
4
200
1565
MsgSent 1443 1799
OutQ
Up/Down
State
0 23:21:56 Established 0 23:15:30 Established
NOTE
To check information about BGP peers in the BGP-VPNv4 address family or the BGP-VPN instance address family, you can run the display bgp vpnv4 all peer command.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
82
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
l If the peer AS number is configured incorrectly, change it to be the same as that of the remote end. l If the peer AS number is configured correctly, go to Step 5. 5.
Check whether or not BGP configurations affect the establishment of the BGP peer relationship. Run the display current-configuration configuration bgp command to check BGP configurations. Table 6-1 describes the checklist for BGP configurations. Table 6-1 Checklist for BGP configurations Item
Description
peer connect-interface interfacetype interface-number
If two ends use loopback interfaces to establish the BGP peer relationship, you need to run the peer connect-interface command to specify the associated loopback interface as the source interface that sends BGP packets.
peer valid-ttl-hops hops
If the peer valid-ttl-hops hops command is configured, check that the hops value is correct. The valid TTL range of the detected packet is [255 - hops + 1, 255]. hops specifies the hop count between BGP peers, and the hop count between two directly connected devices is 1. NOTE The peer valid-ttl-hops command must be configured on both ends before setting up the BGP session.
Issue 04 (2014-04-01)
peer route-limit limit
If the peer route-limit limit limit command is configured, check whether or not the number of routes sent by the peer exceeds the limit that is specified by limit. If it is exceeded, you need to reduce the number of routes sent from the peer, and run the reset bgp ip-address command to reset the BGP peer relationship and trigger the reestablishment of the BGP peer relationship.
peer ignore
If the peer ignore command is configured on the peer, it indicates that the peer is not required to establish the BGP peer relationship with the local end temporarily. To establish the BGP peer relationship between the remote peer and local peer, run the undo peer ignore command on the peer.
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
83
HUAWEI CX600 Metro Service Platform Commissioning Guide
6.
6 Commissioning Services and Protocols
Item
Description
Address family capability
Check that the address family capabilities of the two ends match. For example, before establishing the BGP VPNv4 peer relationship, you need to configure the peer enable command in the BGP-VPNv4 address families of the two ends. If the peer enable command is only configured on one end, the BGP peer relationship of the other end is displayed as No neg.
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 devices
6.6 Commissioning EBGP Routes This section describes how to commission EBGP routes. You can choose to configure the BGP routing protocol based on the actual network plan.
Prerequisite l
The hardware has been checked. For more information, see 4 Checking the Hardware.
l
The link layer has been commissioned. For more information, see 5 Commissioning the Link Layer.
Context On the network shown in Figure 6-7, EBGP is configured on the network to ensure successful communication between the commissioning device and the network connected to CX- B. Figure 6-7 Typical networking for commissioning EBGP routes
1.1.1.1/32
Console PC
Issue 04 (2014-04-01)
192.168.1.1 / 24 GE1/0/0 network GE3/0/0 GE2/0/0 192.168.1.2 / 24 192.167.1.10 / 24
CX600-A AS100
2.2.2.2/32
CX600-B
AS200
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
84
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Procedure Step 1 Run the display bgp peer command to view EBGP peer information. BGP local router ID : 1.1.1.1 Local AS number : 100 Total number of peers : 1 Peer V AS MsgRcvd MsgSent 2.2.2.2 4 200 9 19
Peers in established state : 1 OutQ Up/Down State 0 03:07:01 Established
PrefRcv 1
The boldfaced items in the command output show the EBGP peer information. Check that the EBGP peer address and AS number are correct. Normally, the EBGP peer relationship should be in the Established state. Step 2 Run the display bgp routing-table command on the commissioning device to view EBGP routing information. l View all EBGP routing information: display bgp routing-table BGP Local router ID is 1.1.1.1 Status codes: * - valid, > - best, d - damped, h - history, i - internal, s - suppressed, S Stale Origin : i - IGP, e - EGP, ? - incomplete Total Number of Routes: 4 Network NextHop Ogn *> 2.2.2.2/32 0.0.0.0 *> 192.168.1.0/24 0.0.0.0 * i 2.2.2.2 *> 192.168.1.1/32 0.0.0.0 *> 192.167.1.0/24 0.0.0.0 * 2.2.2.2 *> 1.1.1.1/32 0.0.0.0 *> 127.0.0.0 0.0.0.0 *> 127.0.0.1/32 0.0.0.0 *> 0.0.0.0 200.1.2.1 *> 9.1.1.0 200.1.2.1 *> 10.0.0.0 200.1.2.1
MED 1 0 0 0 0 0 0 0 0 0 0
LocPrf
100
100 100 100
PrefVal Path/ 0 0 0 0 0 0 0 0 0 0 0 0
? ? i ? ? 200i ? ? ? 300? 300? 400?
Check that the network addresses, next-hop addresses, metrics, and local preferences of BGP routes are correct. The boldfaced items in the command output show the specific routes received from AS 200, default route and specific routes received from AS 300, summarized routes received from AS 400, and that the local preference of the routes received from AS 300 and AS 400 is set to 100 by the configured routing policy. l View detailed information about the specified EBGP routes: display bgp routing-table 192.167.1.0 BGP local router ID : 1.1.1.1 Local AS number : 100 Paths: 2 available, 1 best, 1 select BGP routing table entry information of 192.167.1.0/24: Imported route. From: 2.2.2.2 (2.2.2.2) Route Duration: 00h14m33s Direct Out-interface: GigabitEthernet1/0/0 Original nexthop: 2.2.2.2 Qos information : 0x0 Community:no-export AS-path 200, origin igp, MED 0, pref-val 0, valid, external, best, select, pre 255 Not advertised to any peer yet
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
85
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
The boldfaced items in the command output show the detailed information about the specified IBGP routes. Check that the local router IDs, AS numbers, sources of EBGP routes, outbound interfaces, and next-hop addresses are correct. The EBGP routes in the command output have community attributes, which prevents CX- A from advertising the routes received from CX- B to other ASs. l View information about the routes with community attributes: display bgp routing-table community BGP Local router ID is 1.1.1.1 Status codes: * - valid, > - best, d - damped, h - history, i - internal, s - suppressed, S - Stale Origin : i - IGP, e - EGP, ? - incomplete Total Number of Routes: 1 Network NextHop *> 192.167.1.0 2.2.2.2
MED 0
LocPrf 100
PrefVal Community 0 no-export
Step 3 Run the display bgp peer ipv4-address verbose command to view the configurations of GTSM and GR functions for EBGP. display bgp peer 2.2.2.2 verbose BGP Peer is 2.2.2.2, remote AS 200 Type: EBGP link BGP version 4, Remote router ID 2.2.2.2 Update-group ID : 2 BGP current state: Established, Up for 00h49m35s BGP current event: RecvKeepalive BGP last state: OpenConfirm BGP Peer Up count: 1 Received total routes: 1 Received active routes total: 1 Advertised total routes: 3 Port: Local - 179 Remote - 52876 Configured: Active Hold Time: 180 sec Keepalive Time:60 sec Received : Active Hold Time: 180 sec Negotiated: Active Hold Time: 180 sec Keepalive Time:60 sec Peer optional capabilities: Peer supports bgp multi-protocol extension Peer supports bgp route refresh capability Peer supports bgp 4-byte-as capability Graceful Restart Capability: advertised Address family IPv4 Unicast: advertised and received Received: Total 59 messages Update messages 0 Open messages 2 KeepAlive messages 57 Notification messages 0 Refresh messages 0 Sent: Total 79 messages Update messages 5 Open messages 2 KeepAlive messages 71 Notification messages 1 Refresh messages 0 Authentication type configured: None Last keepalive received: 2010-02-20 13:54:58 Minimum route advertisement interval is 30 seconds Optional capabilities: Route refresh capability has been enabled 4-byte-as capability has been enabled Connect-interface has been configured Multi-hop ebgp has been enabled GTSM has been enabled, valid-ttl-hops: 1 Peer Preferred Value: 0 Routing policy configured: No routing policy is configured
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
86
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
The boldfaced items in the command output show that the GTSM function has been enabled, the number of valid hops is 1, the BGP peer relationship is in the Established state, and the GR function is enabled for EBGP. Step 4 Run the display bgp routing-table dampening parameter command and the display bgp routing-table dampened command to view the configured EBGP route dampening parameters, and dampened EBGP routes respectively. display bgp routing-table dampening parameter Maximum Suppress Time(in second) : 3973 Ceiling Value : 16000 Reuse Value : 750 HalfLife Time(in second) : 900 Suppress-Limit : 2000 Route-policy : dampen-policy display bgp routing-table dampened Total Number of Routes: 1 BGP Local router ID is 1.1.1.1 Status codes: * - valid, > - best, d - damped, h - history, i - internal, s - suppressed, S - Stale Origin codes: i - IGP, e - EGP, ? - incomplete Network From Reuse Path d 192.168.1.0 2.2.2.2 00:09:33 200 i
Step 5 Run the ping command on the commissioning device to test the availability of EBGP routes. ping 2.2.2.2 PING 2.2.2.2: 56 data bytes, press CTRL_C to break Reply from 2.2.2.2: bytes=56 Sequence=1 ttl=254 Reply from 2.2.2.2: bytes=56 Sequence=2 ttl=254 Reply from 2.2.2.2: bytes=56 Sequence=3 ttl=254 Reply from 2.2.2.2: bytes=56 Sequence=4 ttl=254 Reply from 2.2.2.2: bytes=56 Sequence=5 ttl=254
time=70 time=65 time=64 time=90 time=25
ms ms ms ms ms
--- 2.2.2.2 ping statistics --5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 25/63/90 ms
2.2.2.2 is the loopback address of CX- B. ----End
Troubleshooting If the BGP peer relationship cannot be established on a BGP-deployed network, complete the following: 1.
Run the ping command to check that BGP peers can ping each other successfully. l If they can ping each other successfully, it indicates that there are available routes between the BGP peers and that link transmission is normal. Proceed to Step 2. NOTE
Run the ping -a source-ip-address -s packetsize host command to detect the connectivity of each end. Because the source address is specified in this command, you can check whether or not routes between the two ends are accessible. By specifying the size of a Ping packet, you can also check whether or not long Ping packets can be normally transmitted over the link.
l If the ping fails, follow the procedure described in "The Ping Operation Fails" in the HUAWEI CX600 Metro Services Platform Troubleshooting to find whether or not the routing tables of each end have available routes to each other. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
87
HUAWEI CX600 Metro Service Platform Commissioning Guide
2.
6 Commissioning Services and Protocols
Check that no ACL is configured to filter packets whose destination port is TCP port 179. Run the display acl all command on both ends to check whether or not an ACL is configured to filter packets whose destination port is TCP port 179. display acl all Total nonempty ACL number is 1 Advanced ACL 3001, 2 rules Acl's step is 5 rule 5 deny tcp source-port eq bgp rule 10 deny tcp destination-port eq bgp
l If an ACL is configured to filter packets whose destination port is TCP port 179, delete the ACL configuration. l If no ACL is configured to filter packets whose destination port is TCP port 179, go to Step 3. 3.
Check that the peer router ID does not conflict with the local router ID. Check information about BGP peers to ensure that their router IDs do not conflict. For example, if the IPv4 unicast peer relationship fails to be established, you can run the display bgp peer command to check whether or not the peer router ID conflicts with the local router ID. Use the following command output as an example: display BGP local router Local AS number Total number of Peer PrefRcv 8.9.0.8 10000 9.10.0.10 9999
bgp peer ID : 223.5.0.109 : 41976 peers : 12
Peers in established state : 4
V
AS
MsgRcvd
4
100
1601
4
200
1565
MsgSent 1443 1799
OutQ
Up/Down
State
0 23:21:56 Established 0 23:15:30 Established
NOTE
To check information about BGP peers in the BGP-VPNv4 address family or the BGP-VPN instance address family, you can run the display bgp vpnv4 all peer command.
l If the peer router ID conflicts with the local router ID, run the router id command in the BGP view to modify the router IDs to agree. Generally, a loopback interface address is used as the local router ID. l If the peer router ID does not conflict with the local router ID, go to Step 4. 4.
Check that the peer AS number is configured correctly. Run the display bgp peer command on each end to check that the displayed peer AS number is the same as that of the remote end. display bgp peer BGP local router ID : 223.5.0.109 Local AS number : 41976 Total number of peers : 12 Peer PrefRcv 8.9.0.8 10000 9.10.0.10 9999
Peers in established state : 4
V
AS
MsgRcvd
4
100
1601
4
200
1565
MsgSent 1443 1799
OutQ
Up/Down
State
0 23:21:56 Established 0 23:15:30 Established
NOTE
To check information about BGP peers in the BGP-VPNv4 address family or the BGP-VPN instance address family, you can run the display bgp vpnv4 all peer command.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
88
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
l If the peer AS number is configured incorrectly, change it to be the same as that of the remote end. l If the peer AS number is configured correctly, go to Step 5. 5.
Check whether or not BGP configurations affect the establishment of the BGP peer relationship. Run the display current-configuration configuration bgp command to check BGP configurations. Table 6-2 describes the checklist for BGP configurations. Table 6-2 Checklist for BGP configurations Item
Description
peer connect-interface interfacetype interface-number
If two ends use loopback interfaces to establish the BGP peer relationship, you need to run the peer connect-interface command to specify the associated loopback interface as the source interface that sends BGP packets.
peer ebgp-max-hop hop-count
If two directly connected devices use loopback interfaces to establish the EBGP peer relationship or two indirectly connected devices establish the EBGP peer relationship, you need to run the peer ebgp-max-hop command to specify the maximum hop count between them. l If two directly connected devices use loopback interfaces to establish the EBGP peer relationship, the hop count can be any number greater than 1. l If two indirectly connected devices establish the EBGP peer relationship, you need to specify the actual hop count.
peer valid-ttl-hops hops
If the peer valid-ttl-hops hops command is configured, check that the hops value is correct. The valid TTL range of the detected packet is [255 - hops + 1, 255]. hops specifies the hop count between BGP peers, and the hop count between two directly connected devices is 1. NOTE The peer valid-ttl-hops command must be configured on both ends before setting up the BGP session.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
89
HUAWEI CX600 Metro Service Platform Commissioning Guide
6.
6 Commissioning Services and Protocols
Item
Description
peer route-limit limit
If the peer route-limit limit command is configured, check whether or not the number of routes sent by the peer exceeds the limit specified by limit. If it is exceeded, you need to reduce the number of routes sent from the peer, and run the reset bgp ip-address command to reset the BGP peer relationship and trigger the reestablishment of the BGP peer relationship.
peer ignore
If the peer ignore command is configured on the peer, it indicates that the peer is not required to establish the BGP peer relationship with the local end temporarily. To establish the BGP peer relationship between the remote peer and local peer, run the undo peer ignore command on the peer.
Address family capability
Check that the address family capabilities of on both ends match. For example, before establishing the BGP VPNv4 peer relationship, you need to configure the peer enable command in the BGP-VPNv4 address families of the two ends. If the peer enable command is only configured on one end, the BGP peer relationship of the other end is displayed as No neg.
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 devices
6.7 Commissioning MPLS LDP This section describes how to commission MPLS LDP. You can choose to configure a type of MPLS tunnel based on the actual network plan.
Prerequisite l
The hardware has been checked. For more information, see 4 Checking the Hardware.
l
The link layer has been commissioned. For more information, see 5 Commissioning the Link Layer.
Context On the network shown in Figure 6-8, MPLS LDP is configured on the network.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
90
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Figure 6-8 Typical networking for commissioning MPLS LDP 1.1.1.1/32
Console PC
2.2.2.2/32
192.168.1.1 / 24 GE1/0/0 network GE2/0/0 GE3/0/0 192.168.1.2 / 24 192.167.1.10 / 24
CX600-A
CX600-B
Procedure Step 1 Run the display mpls ldp peer command to view LDP peer information. display mpls ldp peer LDP Peer Information in Public network A '*' before a peer means the peer is being deleted. ------------------------------------------------------------------------Peer-ID Transport-Address Discovery-Source ------------------------------------------------------------------------2.2.2.2:0 2.2.2.2 GigabitEthernet1/0/0 -------------------------------------------------------------------------TOTAL: 1 Peer(s) Found.
Check that the number of LDP peers is correct. Step 2 Run the display mpls ldp session command to check information about the session between LDP peers. display mpls ldp session LDP Session(s) in Public Network Codes: LAM(Label Advertisement Mode), SsnAge Unit(DDDD:HH:MM) A '*' before a session means the session is being deleted. -------------------------------------------------------------------------Peer-ID Status LAM SsnRole SsnAge KASent/Rcv -------------------------------------------------------------------------2.2.2.2:0 Operational DU Active 0000:00:22 12984/12991 -------------------------------------------------------------------------TOTAL: 1 Session(s) Found.
The Status field in the preceding command output is commonly displayed as Operational, indicating that an LDP session has been established. The LAM field is commonly displayed as DU, indicating that the label distribution mode is Downstream Unsolicited. The SsnRole field can be displayed as Passive, indicating the responder of an LDP session, or as Active, indicating the initiator of an LDP session. Step 3 Run the display mpls ldp interface command on the commissioning device to view information about the interfaces enabled with MPLS LDP. display mpls ldp interface LDP Interface Information in Public Network Codes:LAM(Label Advertisement Mode), IFName(Interface name) A '*' before an interface means the entity is being deleted. ------------------------------------------------------------------------------IF-Name Status LAM Transport-Address HelloSent/Rcv ------------------------------------------------------------------------------GE1/0/0 Active DU 1.1.1.1 56259/0 -------------------------------------------------------------------------------
Check whether LDP-enabled interfaces are correctly configured and the number of LDP-enabled interfaces is correct. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
91
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Step 4 Run the display mpls ldp lsp command on the commissioning device to view information about the outbound interfaces of LDP LSPs, next-hop addresses, number of LDP LSPs, and types of LDP LSPs. display mpls ldp lsp LDP LSP Information -----------------------------------------------------------------------------DestAddress/Mask In/OutLabel UpstreamPeer NextHop OutInterface -----------------------------------------------------------------------------3.3.3.3/32 NULL/2075 192.168.1.2 GE1/0/0 3.3.3.3/32 1657/2075 2.2.2.2 192.168.1.2 GE1/0/0 2.2.2.2/32 NULL/3 192.168.1.2 GE1/0/0 2.2.2.2/32 1656/3 2.2.2.2 192.168.1.2 GE1/0/0 1.1.1.1/32 3/NULL 2.2.2.2 127.0.0.1 InLoop0 *1.1.1.1/32 Liberal/2078 DS/2.2.2.2 -----------------------------------------------------------------------------TOTAL: 5 Normal LSP(s) Found. TOTAL: 1 Liberal LSP(s) Found. TOTAL: 0 Frr LSP(s) Found. A '*' before an LSP means the LSP is not established A '*' before a Label means the USCB or DSCB is stale A '*' before a UpstreamPeer means the session is in GR state A '*' before a DS means the session is in GR state A '*' before a NextHop means the LSP is FRR LSP
Step 5 Run the display mpls lsp command on the commissioning device to view LSP information. display mpls lsp ---------------------------------------------------------------------LSP Information: LDP LSP ---------------------------------------------------------------------FEC In/Out Label In/Out IF Vrf Name 1.1.1.1/32 3/NULL -/2.2.2.2/32 NULL/3 -/GE1/0/0 2.2.2.2/32 1656/3 -/GE1/0/0 3.3.3.3/32 NULL/2075 -/GE1/0/0 3.3.3.3/32 1657/2075 -/GE1/0/0
Step 6 Run the display mpls lsp verbose command on the commissioning device to view detailed LSP information. display mpls lsp verbose ---------------------------------------------------------------------LSP Information: LDP LSP ---------------------------------------------------------------------No : 1 VrfIndex : Fec : 1.1.1.1/32 Nexthop : 127.0.0.1 In-Label : 3 Out-Label : NULL In-Interface : ---------Out-Interface : ---------LspIndex : 72704 Token : 0x0 FrrToken : 0x0 LsrType : Egress Outgoing token : 0x0 Label Operation : POP Mpls-Mtu : -----TimeStamp : 204745sec Bfd-State : --BGPKey : -----No VrfIndex Fec Nexthop
Issue 04 (2014-04-01)
: : : :
2 2.2.2.2/32 192.168.1.2
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
92
HUAWEI CX600 Metro Service Platform Commissioning Guide
Issue 04 (2014-04-01)
6 Commissioning Services and Protocols
In-Label Out-Label In-Interface Out-Interface LspIndex Token FrrToken LsrType Outgoing token Label Operation Mpls-Mtu TimeStamp Bfd-State BGPKey
: : : : : : : : : : : : : :
NULL 3 ---------GigabitEthernet1/0/0 72705 0x8000007 0x0 Ingress 0x0 PUSH -----944sec --------
No VrfIndex Fec Nexthop In-Label Out-Label In-Interface Out-Interface LspIndex Token FrrToken LsrType Outgoing token Label Operation Mpls-Mtu TimeStamp Bfd-State BGPKey
: : : : : : : : : : : : : : : : : :
3
No VrfIndex Fec Nexthop In-Label Out-Label In-Interface Out-Interface LspIndex Token FrrToken LsrType Outgoing token Label Operation Mpls-Mtu TimeStamp Bfd-State BGPKey
: : : : : : : : : : : : : : : : : :
4
No VrfIndex Fec Nexthop In-Label Out-Label In-Interface Out-Interface LspIndex Token FrrToken LsrType Outgoing token Label Operation
: : : : : : : : : : : : : :
5
2.2.2.2/32 192.168.1.2 1656 3 ---------GigabitEthernet1/0/0 72706 0x8000008 0x0 Transit 0x0 SWAP -----944sec --------
3.3.3.3/32 192.168.1.2 NULL 2075 ---------GigabitEthernet1/0/0 72707 0x8000009 0x0 Ingress 0x0 PUSH 1500 944sec --------
3.3.3.3/32 192.168.1.2 1657 2075 ---------GigabitEthernet1/0/0 72708 0x800000a 0x0 Transit 0x0 SWAP
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
93
HUAWEI CX600 Metro Service Platform Commissioning Guide Mpls-Mtu TimeStamp Bfd-State BGPKey
6 Commissioning Services and Protocols : : : :
1500 944sec --------
The boldfaced items in the command output show the LDP LSP lifetime. If the lifetime is too short, LSP flapping may occur. Step 7 Run the ping lsp command to check the LSP connectivity and whether LSP forwarding is normal. ping lsp -a 1.1.1.1 ip 3.3.3.3 32 LSP PING FEC: IPV4 PREFIX 3.3.3.3/32 : 100 data bytes, press CTRL_C to break Reply from 3.3.3.3: bytes=100 Sequence=1 time = 26 ms Reply from 3.3.3.3: bytes=100 Sequence=2 time = 27 ms Reply from 3.3.3.3: bytes=100 Sequence=3 time = 25 ms Reply from 3.3.3.3: bytes=100 Sequence=4 time = 24 ms Reply from 3.3.3.3: bytes=100 Sequence=5 time = 24 ms --- FEC: IPV4 PREFIX 3.3.3.3/32 ping statistics --5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 24/25/27 ms
This step is to check that the packets to loopback0 on HUAWEI B are transmitted along an LSP. All the PEs related to services need to be checked. ----End
Troubleshooting If the established LDP session is in the Down state on an LDP-deployed network, complete the following: 1.
Check whether the interface on which the LDP session is established is shut down. Run the display this command in the interface view. If the command output contains shutdown, the interface is shut down. l If the interface is shut down, run the undo shutdown command in the interface view to start the interface. l If the interface is not shut down, go to Step 2.
2.
Check whether commands for deleting MPLS configurations have been executed. Run the display current-configuration command to check whether commands for deleting MPLS configurations have been executed. l If the command output does not contain mpls, MPLS is disabled. l If the command output does not contain mpls ldp, MPLS LDP is disabled. l If the command output does not contain mpls ldp remote peer, the session established with the remote LDP peer has been deleted. l If any command for deleting MPLS configurations has been run, run corresponding commands to restore the deleted configurations. l If no command for deleting MPLS configurations has been run but the fault persists, go to Step 3.
3. Issue 04 (2014-04-01)
Check that routes are available. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
94
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Run the display ip routing-table command and check the Destination/Mask field in the command output to find out whether there is a route to the peer device. If there is no route to the peer device, the TCP connection cannot be established. l If the route to the peer device is unreachable, follow the procedure described in "The Ping Operation Fails" in the HUAWEI CX600 Metro Services Platform Troubleshooting to rectify the IGP route fault. l If the route to the peer device is reachable, go to Step 4. 4.
Check whether an LDP Hello-hold timer expires. Run the display mpls ldp interface command to check that both ends of the LDP session can send Hello messages. It is recommended that the display mpls ldp interface command be run every 3 seconds. If the statistics on sent or received messages remain unchanged, the transmission of Hello messages is abnormal, and the Hello-hold timer expires. l If the Hello-hold timer expires, see the troubleshooting of high CPU usage. l If the Hello-hold timer does not expire, go to Step 5.
5.
Check whether the LDP Keepalive-hold timer expires. Run the display mpls ldp session command to check that both ends of the LDP session can send Keepalive messages. It is recommended that the display mpls ldp session command be run every 5 seconds. If the statistics on sent or received messages remain unchanged, the transmission of Keepalive messages is abnormal, and the Keepalive-hold timer expires. l If the Keepalive-hold timer expires, follow the procedure described in "The Ping Operation Fails" in the HUAWEI CX600 Metro Services Platform Troubleshooting to rectify the fault in message forwarding. l If the Keepalive-hold timer does not expire, go to Step 6.
6.
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 devices.
6.8 Commissioning MPLS TE This section describes how to commission MPLS TE. You can choose to configure a type of MPLS tunnel based on the actual network plan.
Prerequisite l
The hardware has been checked. For more information, see 4 Checking the Hardware.
l
The link layer has been commissioned. For more information, see 5 Commissioning the Link Layer.
Context On the network shown in Figure 6-9, MPLS TE is configured on the network.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
95
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Figure 6-9 Typical networking for configuring MPLS TE 1.1.1.1/32
Console PC
2.2.2.2/32
192.168.1.1 / 24 GE1/0/0 network GE2/0/0 GE3/0/0 192.168.1.2 / 24 192.167.1.10 / 24
CX600-A
CX600-B
Procedure Step 1 Run the display interface tunnel command on the commissioning device to view basic information about tunnel interfaces. display interface tunnel Tunnel1/0/0 current state : UP Line protocol current state : UP Last line protocol up time : 2010-02-05 15:12:16 Description: HUAWEI, Quidway Series, Tunnel1/0/0 Interface Route Port,The Maximum Transmit Unit is 1500 Internet Address is unnumbered, using address of LoopBack0(1.1.1.1/32) Encapsulation is TUNNEL, loopback not set Tunnel destination 3.3.3.3 Tunnel up/down statistics 1 Tunnel protocol/transport MPLS/MPLS, ILM is available, primary tunnel id is 0x6000001, secondary tunnel id is 0x0 Current system time: 2010-02-05 15:16:34 300 seconds output rate 0 bits/sec, 0 packets/sec 0 seconds output rate 0 bits/sec, 0 packets/sec 0 packets output, 0 bytes 0 output error 0 output drop ct0:0 packets output, 0 bytes 0 output error 0 packets output drop Input bandwidth utilization : -Output bandwidth utilization : --
The boldfaced items in the command output show that the tunnel interface status and link-layer protocol status are both Up. Step 2 Run the display mpls te tunnel-interface command on the commissioning device to view information about the tunnel interfaces on the local node. display mpls te tunnel-interface ================================================================ Tunnel1/0/0 ================================================================ Tunnel State Desc : Up Active LSP : Primary LSP Session ID : 100 Ingress LSR ID : 1.1.1.1 Egress LSR ID: 3.3.3.3 Admin State : UP Oper State : UP Primary LSP State : UP Main LSP State : READY LSP ID : 1
Check that the tunnel configurations on the local node are correct. If Up is displayed in the command output, it indicates that the tunnel has been established successfully. Step 3 Run the display mpls te cspf tedb command to view TEDB information. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
96
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
display mpls te Maximum Nodes Supported: Maximum Links Supported: Maximum SRLGs supported: Id 1 2 3
Router-Id 1.1.1.1 2.2.2.2 3.3.3.3
cspf tedb all 2000 Current Total Node Number: 3 8000 Current Total Link Number: 4 10000 Current Total SRLG Number: 0
IGP ISIS ISIS ISIS
Process-Id 1 1 1
Area Level-2 Level-2 Level-2
Link-Count 1 2 1
Check that the link information in the TEDB is correct. Step 4 Run the display mpls rsvp-te interface command on the commissioning device to view RSVPTE configurations on the interface. display mpls rsvp-te interface Interface: GigabitEthernet1/0/0 Interface Address: 192.168.1.1 Interface state: UP Interface Index: 0x6 Total-BW: 100000 Used-BW: 20000 Hello configured: NO Num of Neighbors: 1 SRefresh feature: DISABLE SRefresh Interval: 30 sec Mpls Mtu: 1500 Retransmit Interval: 5000 msec Increment Value: 1 Authentication: DISABLE Bfd Enabled: DISABLE Bfd Min-Tx: 10 Bfd Min-Rx: 10 Bfd Detect-Multi: 3
The boldfaced items in the command output show the RSVP-TE configurations. Check whether or not the interface enabled with RSVP-TE is configured correctly and is in the Up state. In addition, check that the total TE bandwidth on the interface and the used TE bandwidth meet the corresponding requirement. Step 5 Run the display mpls rsvp-te peer command on the commissioning device to check whether or not an RSVP-TE neighbor relationship has been established between the interfaces enabled with RSVP-TE. display mpls rsvp-te peer Remote Node id Neighbor Neighbor Addr ----SrcInstance: 0x8277E43C PSB Count: 1 Hello Type Sent: NONE SRefresh Enable: NO Last valid seq # rcvd: NULL Interface GigabitEthernet1/0/0 Neighbor Addr: 192.168.1.2 SrcInstance: 0x8277E43C PSB Count: 0 Hello Type Sent: NONE SRefresh Enable: NO Last valid seq # rcvd: NULL
NbrSrcInstance: 0x0 RSB Count: 0
NbrSrcInstance: 0x0 RSB Count: 1
Step 6 Run the ping lsp command on the commissioning device to test the availability of the TE tunnel. ping lsp te tunnel 1/0/0 LSP PING FEC: RSVP IPV4 SESSION to break Reply from 20.1.1.2: bytes=100 Reply from 40.1.1.2: bytes=100 Reply from 20.1.1.2: bytes=100 Reply from 40.1.1.2: bytes=100 Reply from 20.1.1.2: bytes=100
QUERY Tunnel1/0/0 : 100 Sequence=0 Sequence=1 Sequence=2 Sequence=3 Sequence=4
time time time time time
= = = = =
data bytes, press CTRL_C
50 ms 28 ms 33 ms 52 ms 8 ms
--- FEC: RSVP IPV4 SESSION QUERY Tunnel1/0/0 ping statistics ---
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
97
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 8/34/52 ms
----End
Troubleshooting If the established TE tunnel is in the Down state on a TE-deployed network, complete the following: 1.
Check that the commit command has been executed to commit tunnel configurations. Run the display current-configuration command on the ingress that is configured with the TE tunnel. l If the commit command has not been executed, run it in the tunnel view. l If the commit command has been executed in the tunnel view, go to Step 2.
2.
Check that CSPF has been successfully calculating paths. Run the display mpls te cspf destination ip-address explicit-path path-name command on the TE tunnel ingress. If command output is displayed, CSPF has been successfully calculating paths; if no command output is displayed, CSPF failed to calculate a path. l If CSPF failed to calculate a path, check that routes to the destination of the TE tunnel exist. – If no route exists, follow the procedure described in "The Ping Operation Fails" in the HUAWEI CX600 Metro Services Platform Troubleshooting to rectify the route fault. – If reachable routes exist and they satisfy the requirements to establish a TE tunnel, rectify the fault by referring to the section "CSPF Calculation Fails." l If CSPF has been successfully calculating paths but the fault persists, go to Step 3.
3.
Check that RSVP is enabled on every device along the TE tunnel. The command output of display mpls te cspf destination ip-address explicit-path pathname in Step 2 contains a series of IP addresses. These IP addresses indicate the hops along the TE tunnel. On the interface mapped to each IP address, run the display currentconfiguration interface interface-name command to check if RSVP is enabled. l If an interface is not enabled with RSVP, enable RSVP on the interface. l If all interfaces are enabled with RSVP but the fault persists, go to Step 4.
4.
Check that devices along the TE tunnel have been successfully exchanging RSVP Path and Resv messages. Run the display mpls te tunnel-interface command on the TE tunnel ingress and check fields Ingress LSR ID, LSP ID, and Session ID in the command output. In Step 3, LSR A, LSR B, and LSR C represent the nodes along the TE tunnel. Complete the following to check that the RSVP Path message and RSVP Resv message are correctly transmitted: l Check that RSVP Path messages are correctly sent and received on every node along the LSP in the sending direction (LSR A -> LSR B -> LSR C). Run the display mpls rsvp-te psb-content command on every node the RSVP Path message travels through.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
98
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
– If the command output is not empty on any node, it can be concluded that RSVP Path messages are correctly sent and received between these nodes. – If the command output is empty on a node, it can be concluded that the node fails to receive RSVP Path messages from the upstream node. l Check that RSVP Resv messages are correctly transmitted in the sending direction (LSR C -> LSR B -> LSR A). Run the display mpls rsvp-te rsb-content command on every node the RSVP Resv message travels through. – If the command output is not empty on any node, it can be concluded that RSVP Resv messages are correctly transmitted. – If the command output is empty on a node, it can be concluded that the node fails to receive RSVP Resv messages from the upstream node. l If messages fail to be properly exchanged, follow the procedure described in "The Ping Operation Fails" in the HUAWEI CX600 Metro Services Platform Troubleshooting to rectify the message forwarding fault. l If messages are properly exchanged but 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
6.9 Commissioning BGP/MPLS IP VPN This section describes how to commission BGP/MPLS IP VPN.
Prerequisites l
The hardware has been checked. For more information, see 4 Checking the Hardware.
l
The link layer has been commissioned. For more information, see 5 Commissioning the Link Layer.
Context On the network shown in Figure 6-10, BGP/MPLS IP VPN is configured on the network. Figure 6-10 Typical networking for commissioning BGP/MPLS IP VPN 1.1.1.1/32
2.2.2.2/32
192.168.1.1/24 100.1.1.1/24 100.1.2.1/24 GE1/0/0 GE1/0/0 GE2/0/0 GE2/0/0 GE1/0/0 192.168.1.2/24 100.1.2.2/24 100.1.1.2/24 GE2/0/0 CE1 CE2 PE1 PE2
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
99
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Procedure Step 1 Run the display ip vpn-instance verbose command on the commissioning device to check that VPN instance configurations are correct. display ip vpn-instance verbose Total VPN-Instances configured : 1 VPN-Instance Name and ID : vpna, 1 Interfaces : GigabitEthernet1/0/0 Address family ipv4 Create date : 2010/01/21 11:30:35 UTC+08:00 Up time : 0 days, 00 hours, 05 minutes and 19 seconds Route Distinguisher : 100:1 Export VPN Targets : 111:1 Import VPN Targets : 111:1 Label policy: label per route The diffserv-mode Information is : uniform The ttl-mode Information is : pipe Log Interval : 5
Step 2 Run the display bgp peer command on the commissioning device to view BGP peer information. display BGP local router Local AS number Total number of
bgp vpnv4 all peer ID : 1.1.1.1 : 100 peers : 2
Peers in established state : 2
Peer V AS MsgRcvd MsgSent 2.2.2.2 4 274 10 12 Peer of IPv4-family for vpn instance : VPN-Instance vpna, router ID 1.1.1.1: 100.1.1.1 4 65410 454 418
OutQ 0
Up/Down 03:24:40
State PrefRcv Established 0
0
03:12:16
Established
9
Check that the number of BGP peers and the number of configured VPN instances are correct. The boldfaced items in the command output show that the BGP peer relationship is in the Established state, indicating that a BGP peer relationship has been successfully established between PEs. Step 3 Run the display bgp vpnv4 routing-table command on the commissioning device to view BGP VPNv4 routing information. display bgp vpnv4 vpn-instance vpna routing-table peer 100.1.1.1 advertised-routes BGP Local router ID is 1.1.1.1 Status codes: * - valid, > - best, d - damped, h - history, i - internal, s - suppressed, S - Stale Origin : i - IGP, e - EGP, ? incomplete Total Number of Routes: 6 Network NextHop MED LocPrf PrefVal Path/ Ogn *>i 2.2.2.2/32 1.1.1.1 0 100 0 65420? *> 100.1.1.0/24 0.0.0.0 0 0 ? *>i 100.1.2.0/24 1.1.1.1 0 100 0 ? *>i 192.168.1.0 1.1.1.1 0 100 0 65420? display bgp vpnv4 vpn-instance vpna routing-table peer 100.1.1.1 receivedroutes BGP Local router ID is 1.1.1.1 Status codes: * - valid, > - best, d - damped, h - history, i - internal, s - suppressed, S - Stale Origin : i - IGP, e - EGP, ? - incomplete VPN-Instance vpna, router ID 1.1.1.1: Total Number of Routes: 6
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
100
HUAWEI CX600 Metro Service Platform Commissioning Guide
Ogn *> *> * *>
6 Commissioning Services and Protocols
Network
NextHop
1.1.1.1/32 2.2.2.2/32 100.1.1.0/24 192.168.1.0
100.1.1.1 100.1.1.1 100.1.1.1 100.1.1.1
MED
LocPrf
PrefVal Path/
0 0 0 0
0 0 0 0
65410? 65410? 65410? 65410?
Check that the sent and received BGP routes are correct. First check whether the routes sent by the PE are correct, meaning whether some necessary routes are not sent but some unnecessary routes are sent. Then do the same for the routes received from the peer PE. Step 4 Run the display ip routing-table vpn-instance command on the commissioning device to view the routing table of the VPN instance. display ip routing-table vpn-instance vpna Route Flags: R - relay, D - download to fib -----------------------------------------------------------------------------Routing Tables: vpna Destinations : 3 Routes : 3 Destination/Mask Proto Pre Cost Flags NextHop Interface 100.1.1.0/24 Direct 0 0 D 10.1.1.2 GigabitEthernet1/0/0 100.1.1.2/32 Direct 0 0 D 127.0.0.1 InLoopBack0 100.1.1.255/32 Direct 0 0 D 127.0.0.1 InLoopBack0 100.1.2.0/24 BGP 255 0 RD 2.2.2.2 GigabitEthernet1/0/0 255.255.255.255/32 Direct 0 0 D 127.0.0.1 InLoopBack0
The command output shows whether the received BGP routes are injected into the routing table of the VPN instance. If BGP routes are received but are not injected into the routing table of the VPN instance, the probable cause is that the public network tunnel is not established, or the routes are filtered by a routing policy. The boldfaced items in the command output show the route to the interface on the remote CE. Step 5 Run the ping command on CE1 to test the connectivity of the link between CE1 and CE2. ping -vpn-instance vpna 100.1.2.2 PING 100.1.2.2: 56 data bytes, press CTRL_C to break Reply from 100.1.2.2: bytes=56 Sequence=1 ttl=255 time=56 ms Reply from 100.1.2.2: bytes=56 Sequence=2 ttl=255 time=4 ms Reply from 100.1.2.2: bytes=56 Sequence=3 ttl=255 time=4 ms Reply from 100.1.2.2: bytes=56 Sequence=4 ttl=255 time=52 ms Reply from 100.1.2.2: bytes=56 Sequence=5 ttl=255 time=3 ms --- 100.1.2.2 ping statistics --5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 3/23/56 ms
The preceding command output shows that two CEs in the same VPN can communicate with each other. ----End
Troubleshooting If BGP traffic in the VPN is interrupted, complete the following: 1.
Check that next hops of routes are reachable. Run the display bgp vpnv4 vpn-instance vpn-instance-name routing-table ipv4address [ mask | mask-length ] command on the PE that sends routes (the local PE) to check that the target route exists. ipv4-address specifies the prefix of the target route.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
101
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
l If the target route does not exist, check whether the route of a CE is advertised to the local PE. l If the target route exists, check that it is active. The following is an example: Assume that the target route is a route to 1.1.1.1/32. The following command output shows that this route is active and selected. The original next hop and iterated next hop of this route are 3.3.3.3 and 20.1.1.2 respectively. display bgp vpnv4 vpn-instance vpna routing-table 1.1.1.1 BGP local router ID : 20.1.1.2 Local AS number : 100 VPN-Instance vpna, router ID 20.1.1.2: Paths: 1 available, 1 best, 1 select BGP routing table entry information of 1.1.1.1/32: Imported route. From: 20.1.1.1 (1.1.1.1) Route Duration: 00h00m03s Relay IP Nexthop: 20.1.1.2 Relay IP Out-Interface: GigabitEthernet1/0/0 Original nexthop: 3.3.3.3 Qos information : 0x0 AS-path Nil, origin incomplete, MED 0, localpref 100, pref-val 0, valid, internal, best, select, active, pre 255 Not advertised to any peer yet
l If the target route is inactive, check whether there is a route to the original next hop in the IP routing table. If there is no route to the original next hop, the BGP route is not advertised, because its next hop is unreachable. Then, find out why there is no route to the original next hop (this fault is generally associated with IGP or static routes). l If the target route is active but not selected, check whether there is a route with a higher protocol preference in the IP routing table. If there is a route with a higher protocol preference, import it into BGP or adjust its protocol preference. If there is no route with a higher protocol preference, contact Huawei technical support personnel. NOTE
In the BGP routing table, multiple routes may have the same prefix. One of these routes can be selected at most, and only the selected route is added to the IP routing table and sent to the peer. When an optimal route needs to be selected from among BGP routes and other protocol routes, the route with the highest protocol preference is selected.
l If the target route is active but not selected, contact Huawei technical support personnel. NOTE
If there are active BGP routes, one of them is preferred.
l If the target route is active and selected but there is no information indicating that this route is sent to the remote PE, perform Step 2 to check the outbound policy applied to the local PE. Run the display bgp vpnv4 all routing-table network { mask | mask-length } command on the remote PE to check that it has received the target route. – If the remote PE has received the target route, perform Step 1 again to check whether the next hop of the route is reachable and whether this route is selected. – If the remote PE has not received the target route, perform Step 2 to check the inbound policy applied to the remote PE. 2.
Check that the routing policies are configured correctly. Run the display current-configuration configuration bgp command on the local PE and remote PE to check that inbound and outbound policies are configured.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
102
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
NOTE
You only need to focus on peers of the BGP-VPNv4 address family or BGP-VPN instance address family when private network traffic is interrupted. display current-configuration configuration bgp # bgp 100 peer 1.1.1.1 as-number 200 peer 2.2.2.1 connect-interface LoopBack0 # ipv4-family unicast undo synchronization peer 1.1.1.1 enable # ipv4-family vpnv4 policy vpn-target peer 1.1.1.1 enable peer 1.1.1.1 filter-policy acl-name acl-name import peer 1.1.1.1 filter-policy acl-name acl-name export peer 1.1.1.1 as-path-filter 1 import peer 1.1.1.1 as-path-filter 1 export peer 1.1.1.1 ip-prefix prefix-name import peer 1.1.1.1 ip-prefix prefix-name export peer 1.1.1.1 route-policy policy-name import peer 1.1.1.1 route-policy policy-name export # ipv4-family vpn-instance vpna import-route direct peer 10.1.1.1 as-number 300 peer 10.1.1.1 filter-policy acl-name acl-name import peer 10.1.1.1 filter-policy acl-name acl-name export peer 10.1.1.1 as-path-filter 1 import peer 10.1.1.1 as-path-filter 1 export peer 10.1.1.1 ip-prefix prefix-name import peer 10.1.1.1 ip-prefix prefix-name export peer 10.1.1.1 route-policy policy-name import peer 10.1.1.1 route-policy policy-name export # return
l If inbound and outbound policies are configured on the two devices, you need to check whether the target route is filtered by these policies. For detailed configurations of a routing policy, see the HUAWEI CX600 Metro Services Platform Configuration Guide - IP Routing. l If inbound and outbound policies are not configured on the two ends, go to Step 3. 3.
Check that routes can be iterated to a tunnel. Run the display bgp vpnv4 all routing-table ipv4-address [ mask | mask-length ] command on the remote PE to check whether the target route can be iterated to a tunnel. Assume that the target route is a route to 50.1.1.2/32. If the Relay Tunnel Out-Interface field and Relay token field in the command output are not empty, this route can be iterated to a tunnel. display bgp vpnv4 all routing-table 50.1.1.2 BGP local router ID : 2.2.2.2 Local AS number : 100 Total routes of Route Distinguisher(1:2): 1 BGP routing table entry information of 50.1.1.2/32: Imported route. Label information (Received/Applied): 13316/NULL From: 1.1.1.1 (1.1.1.1) Route Duration: 00h00m08s Relay IP Nexthop: 20.1.1.1 Relay IP Out-Interface: GigabitEthernet1/0/0
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
103
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Relay Tunnel Out-Interface: GigabitEthernet1/0/0 Relay token: 0x1002 Original nexthop: 1.1.1.1 Qos information : 0x0 Ext-Community:RT AS-path Nil, origin incomplete, MED 0, localpref 100, pref-val 0, valid, internal, best, select, pre 255 Not advertised to any peer yet VPN-Instance vpna, router ID 2.2.2.2: Total Number of Routes: 1 BGP routing table entry information of 50.1.1.2/32: Imported route. Label information (Received/Applied): 13316/NULL From: 1.1.1.1 (1.1.1.1) Route Duration: 00h00m07s Relay Tunnel Out-Interface: GigabitEthernet1/0/0 Relay token: 0x1002 Original nexthop: 1.1.1.1 Qos information : 0x0 Ext-Community:RT AS-path Nil, origin incomplete, MED 0, localpref 100, pref-val 0, valid, internal, best, select, active, pre 255 Not advertised to any peer yet
l If the target route fails to be iterated to a tunnel, check that the associated tunnel exists and MPLS LDP is configured correctly. For more information, see the section "MPLS" in HUAWEI CX600 Metro Services Platform Troubleshooting. l If the target route can be iterated to a tunnel, go to Step 4. 4.
Check whether routes fail to be added to the VPN routing table because the configured import RT and export RT do not match. Run the display current-configuration configuration vpn-instance command on the local PE and remote PE to check if routes fail to be added to the VPN routing table of the remote PE after being sent to the remote PE because the export RT of the local VPN instance does not match the import RT of the remote VPN instance. export-extcommunity indicates an export RT, and import-extcommunity indicates an import RT. display current-configuration configuration vpn-instance # ip vpn-instance vpna ipv4-family route-distinguisher 1:1 vpn-target 111:1 export-extcommunity vpn-target 111:1 import-extcommunity apply-label per-instance vpn-target 1:1 export-extcommunity vpn-target 1:1 import-extcommunity ip vpn-instance vpnb ipv4-family route-distinguisher 1:2 vpn-target 1:1 export-extcommunity vpn-target 1:1 import-extcommunity # return
l If the export RT of the local VPN instance does not match the import RT of the remote VPN instance, configure matching VPN-targets in the VPN instance. l If the export RT of the local VPN instance matches the import RT of the remote VPN instance, go to Step 5. 5.
Issue 04 (2014-04-01)
Check that the number of labels does not exceed the limit.
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
104
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Check that MPLS is enabled on the local PE. Then, run the display bgp vpnv4 all routingtable ipv4-address [ mask | mask-length ] command to check whether the target route has been assigned a VPN label. If there is no Label information field in the command output, labels may be insufficient. As a result, the target route is not assigned a label and is not advertised to the peer. display bgp vpnv4 all routing-table 100.1.1.1 BGP local router ID : 10.1.1.2 Local AS number : 100 Total routes of Route Distinguisher(1:1): 1 BGP routing table entry information of 100.1.1.0/24: Imported route. Label information (Received/Applied): NULL/13312 From: 0.0.0.0 (0.0.0.0) Route Duration: 00h21m24s Direct Out-interface: NULL0 Original nexthop: 100.1.1.1 Qos information : 0x0 Ext-Community:RT AS-path Nil, origin incomplete, MED 0, pref-val 0, valid, local, best, select, pre 255 Advertised to such 1 peers: 1.1.1.1 VPN-Instance vpna, router ID 10.1.1.2: Total Number of Routes: 1 BGP routing table entry information of 100.1.1.0/24: Imported route. From: 0.0.0.0 (0.0.0.0) Route Duration: 00h21m24s Direct Out-interface: NULL0 Original nexthop: 100.1.1.1 Qos information : 0x0 AS-path Nil, origin incomplete, MED 0, pref-val 0, valid, local, best, select, pre 60 Not advertised to any peer yet
l If labels are insufficient, run the apply-label per-instance command in the VPN instance view to configure the device to assign a label to each instance to save labels. You can also configure route summarization to reduce the number of routes. l If labels are sufficient, go to Step 6. 6.
Check that the number of routes does not exceed the limit. Run the display current-configuration configuration bgp | include peer destinationaddress command and the display current-configuration configuration bgp | include peer group-name command (if the peer is added to a peer group) on the remote PE to check whether the limit on the number of routes to be received is configured on the remote PE. For example, if the limit is set to 5, subsequent routes are dropped and a log is recorded after the remote PE receives five routes from the local PE at 1.1.1.1. display current-configuration configuration bgp | include peer 1.1.1.1 peer 1.1.1.1 as-number 100 peer 1.1.1.1 route-limit 5 alert-only peer 1.1.1.1 enable
If the peer is added to a peer group, there may be no configurations about the route limit in the command output. display current-configuration configuration bgp | include peer 1.1.1.1 peer 1.1.1.1 as-number 100 peer 1.1.1.1 group IBGP peer 1.1.1.1 enable
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
105
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
In this case, you need to run the display current-configuration configuration bgp | include peer group-name command to check the configurations of this peer group. display current-configuration configuration bgp | include peer IBGP peer IBGP route-limit 5 alert-only peer IBGP enable
If the log BGP/3/ROUTPRIX_EXCEED is generated when traffic is interrupted, the target route is dropped because the route limit has been exceeded, and the limit needs to be increased. NOTE
Changing the limit on the number of routes to be received from a peer interrupts the BGP peer relationship. Therefore, it is recommended to reduce the number of sent routes by configuring route summarization on the local device.
7.
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 devices
6.10 Commissioning VPWS This section describes how to commission VPWS. MPLS L2VPN contains VPWS and VPLS technologies.
Prerequisite l
The hardware has been checked. For more information, see 4 Checking the Hardware.
l
The link layer has been commissioned. For more information, see 5 Commissioning the Link Layer.
Context On the network shown in Figure 6-11, VPWS is deployed on the network and CX- A is a PE. Figure 6-11 Typical networking for commissioning VPWS 1.1.1.1/32 100.1.1.1/24 GE1/0/0.1 GE1/0/0.1 CE1
2.2.2.2/32
192.168.1.1/24 GE1/0/0
100.1.1.2/24 GE2/0/0.1 GE2/0/0.1
192.168.1.2/24 GE2/0/0 PE1
PE2
CE2
Procedure Step 1 Run the display mpls l2vc command on the commissioning device to view information about the L2VCs using the LDP as the signaling protocol. display mpls l2vc total LDP VC : 1 1 up
Issue 04 (2014-04-01)
0 down
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
106
HUAWEI CX600 Metro Service Platform Commissioning Guide *client interface : Administrator PW : session state : AC status : VC state : Label state : Token state : VC ID : VC type : destination : local VC label : control word : forwarding entry : local group ID : manual fault : active state : link state : local VC MTU : tunnel policy name : traffic behavior name: PW template name : primary or secondary : create time : up time : last change time : VC last up time : VC total up time : CKey : NKey : AdminPw interface : AdminPw link state : Diffserv Mode : Service Class : Color : DomainId : Domain Name :
6 Commissioning Services and Protocols GigabitEthernent1/0/0.1 up up up up 0 0 101 VLAN 2.2.2.2 21504 remote VC label : 21504 disable existent 0 not set active up 1500 remote VC MTU : 1500 to2 --primary 0 days, 0 hours, 6 minutes, 4 seconds 0 days, 0 hours, 4 minutes, 34 seconds 0 days, 0 hours, 4 minutes, 34 seconds 2010/07/24 12:31:31 0 days, 0 hours, 4 minutes, 34 seconds 16 15 --uniform -----
The command output shows L2VC information. Check that the number of Up L2VCs is correct, the AC interface of each L2VC is correctly configured, and the AC status, VC status, session status, link status, VC ID, encapsulation type, and destination address of the L2VC are correct. Step 2 Run the display l2vpn ccc-interface vc-type command on the commissioning device to view information about the interfaces that had set up an L2VPN connection. display l2vpn ccc-interface vc-type all Total ccc-interface of LDP VC: 1 up (1), down (0) Interface Encap Type State GigabitEthernet1/0/0.1 vlan up
VC Type ldp-vc
The command output shows information about the interfaces that had set up an L2VPN connection. Check that the encapsulation type, status, and VC type of the interfaces are correct. Step 3 Run the ping command on CE1 to test the connectivity of the link between CE1 and CE2. ping 100.1.1.2 PING 100.1.1.2: 56 data bytes, press CTRL_C to break Reply from 100.1.1.2: bytes=56 Sequence=1 ttl=255 Reply from 100.1.1.2: bytes=56 Sequence=2 ttl=255 Reply from 100.1.1.2: bytes=56 Sequence=3 ttl=255 Reply from 100.1.1.2: bytes=56 Sequence=4 ttl=255 Reply from 100.1.1.2: bytes=56 Sequence=5 ttl=255
time=56 ms time=4 ms time=4 ms time=52 ms time=3 ms
--- 100.1.1.2 ping statistics --5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 3/23/56 ms
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
107
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
The preceding command output shows that two CEs in the same VPN can communicate with each other. ----End
Troubleshooting If the VC of a Martini VLL cannot become Up, complete the following: 1.
Check that the two ends of the VC are configured with the same encapsulation type and MTU. Run the display mpls l2vc vc-id command to view VC information. display mpls l2vc 102 total LDP VC : 1 1 up 0 down *client interface : GigabitEthernet1/0/0.5 session state : up AC status : up VC state : up VC ID : 102 VC type : VLAN destination : 2.2.2.2 local VC label : 146433 remote VC label : 146432 control word : disable forwarding entry : exist local group ID : 0 manual fault : not set active state : active link state : up local VC MTU : 1500 remote VC MTU : 1500 tunnel policy name : -traffic behavior name: -PW template name : -primary or secondary : primary create time : 1 days, 1 hours, 14 minutes, 17 seconds up time : 0 days, 0 hours, 3 minutes, 16 seconds last change time : 0 days, 0 hours, 3 minutes, 16 seconds VC last up time : 2010/02/17 08:23:07 VC total up time : 0 days, 21 hours, 43 minutes, 43 seconds CKey : 16 NKey : 15 AdminPw interface : -AdminPw link state : -Diffserv Mode : uniform Service Class : -Color : -DomainId : -Domain Name : --
If the two ends are configured with different encapsulation types or MTUs, change the encapsulation type or MTU of one end to be the same as that of the other. If the two ends are configured with the same encapsulation type and MTU but the fault persists, go to Step 2. NOTE
A VC can only be Up when the two ends of the VC are configured with the same encapsulation type and MTU.
2.
Check that the VC IDs of the two ends of the VC are the same. display mpls l2vc 102 total LDP VC : 1 1 up 0 down *client interface : GigabitEthernet1/0/0.5
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
108
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
session state : AC status : VC state : VC ID : VC type : destination : local VC label : control word : forwarding entry : local group ID : manual fault : active state : link state : local VC MTU : tunnel policy name : traffic behavior name: PW template name : primary or secondary : create time : up time : last change time : VC last up time : VC total up time : CKey :
up up up 102 VLAN 2.2.2.2 146433 remote VC label : 146432 disable exist 0 not set active up 1500 remote VC MTU : 1500 ---primary 1 days, 1 hours, 14 minutes, 17 seconds 0 days, 0 hours, 3 minutes, 16 seconds 0 days, 0 hours, 3 minutes, 16 seconds 2010/02/17 08:23:07 0 days, 21 hours, 43 minutes, 43 seconds
16 NKey AdminPw interface AdminPw link state Diffserv Mode Service Class Color DomainId Domain Name
: : : : : : : :
15 --uniform -----
If the VC IDs of the two ends of the VC are different, change the VC ID of one end to be the same as that of the other. If the VC IDs of the two ends of the VC are the same but the fault persists, go to Step 3. NOTE
A VC can only be Up when the VC IDs of the two ends of the VC are the same.
3.
Check that the LDP session between the two ends is Up. display mpls l2vc 102 total LDP VC : 1 1 up 0 down *client interface : GigabitEthernet1/0/0.5 session state : up AC status : up VC state : up VC ID : 102 VC type : VLAN destination : 2.2.2.2 local VC label : 146433 remote VC label : 146432 control word : disable forwarding entry : exist local group ID : 0 manual fault : not set active state : active link state : up local VC MTU : 1500 remote VC MTU : 1500 tunnel policy name : -traffic behavior name: -PW template name : -primary or secondary : primary create time : 1 days, 1 hours, 14 minutes, 17 seconds up time : 0 days, 0 hours, 3 minutes, 16 seconds last change time : 0 days, 0 hours, 3 minutes, 16 seconds
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
109
HUAWEI CX600 Metro Service Platform Commissioning Guide VC last up time VC total up time CKey
6 Commissioning Services and Protocols : 2010/02/17 08:23:07 : 0 days, 21 hours, 43 minutes, 43 seconds :
16 NKey AdminPw interface AdminPw link state Diffserv Mode Service Class Color DomainId Domain Name
: : : : : : : :
15 --uniform -----
If the LDP session is Down, see the section "An LDP Session Is Down" in HUAWEI CX600 Metro Services Platform Troubleshooting to locate the fault and make the LDP session Up. If the LDP session is Up, go to Step 4. NOTE
A VC can only be set up when the LDP session is Up.
4.
Check that the PW has selected a tunnel. Run the display mpls l2vc vc-id command. l Check the VC tunnel/token info field in the command output. If VC tunnel/token info is displayed as 0 tunnels/tokens, no tunnel has been selected by the PW. l Check the tunnel policy name field in the command output. – If tunnel policy name is displayed as -, an LDP LSP is used as the tunnel for the PW, or no tunnel policy is configured. An MPLS TE tunnel can only be used for a PW after a tunnel policy is configured. – If tunnel policy name is not displayed as "-", a tunnel policy has been adopted. In this case, run the display this command in the tunnel policy view to view the tunnel policy configuration. [HUAWEI-tunnel-policy-p1] display this # tunnel-policy p1 tunnel select-seq cr-lsp load-balance-number 1 # NOTE
If the tunnel binding destination dest-ip-address te { tunnel interface-number } command is configured in the tunnel policy view, you also need to run the mpls te reserved-for-binding command on the tunnel interface.
If the tunnel is Down, see the section "An LSP Is Down" or "A TE Tunnel Is Down" in HUAWEI CX600 Metro Services Platform Troubleshooting to locate the fault and make the tunnel Up. If the tunnel is Up and the TE interfaces are correctly configured, go to Step 5. NOTE
A VC can only be Up when the tunnel that bears the VC is also Up.
5.
Check that the AC interfaces on the two ends are Up. Run the display mpls l2vc vc-id command on the two ends of the VC to check whether or not the AC status field is displayed as Up.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
110
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
l If the AC interfaces on the two ends are Down, see the section "Physical Interface Interconnection" in HUAWEI CX600 Metro Services Platform Troubleshooting to locate the fault and make the AC interfaces Up. l If the AC interfaces on the two ends are Up, go to Step 6. NOTE
A VC can only be Up when the AC interfaces on the two ends of the VC are also Up.
6.
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 devices
6.11 Commissioning VPLS This section describes how to commission VPLS. MPLS L2VPN contains VPWS and VPLS technologies.
Prerequisite l
The hardware has been checked. For more information, see 4 Checking the Hardware.
l
The link layer has been commissioned. For more information, see 5 Commissioning the Link Layer.
Context On the network shown in Figure 6-12, VPLS is deployed on the network and CX- A is a PE. Figure 6-12 Typical networking for commissioning VPLS 1.1.1.1/32 100.1.1.1/24 GE1/0/0.1 GE1/0/0.1 CE1
2.2.2.2/32
192.168.1.1/24 GE1/0/0
100.1.1.2/24 GE2/0/0.1 GE2/0/0.1
192.168.1.2/24 GE2/0/0 PE2
PE1
CE2
Procedure Step 1 Run the display vsi command on the commissioning device to view VSI information. display vsi name v1 ***VSI Name : Administrator VSI : Isolate Spoken : VSI Index : PW Signaling : Member Discovery Style : PW MAC Learn Style : Encapsulation Type : MTU :
Issue 04 (2014-04-01)
verbose v1 no disable 0 ldp static unqualify vlan 1500
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
111
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Diffserv Mode Service Class Color DomainId Domain Name Ignore AcState Multicast Fast Swicth Create Time VSI State
: : : : : : : : :
uniform --255
VSI ID *Peer Router ID primary or secondary ignore-standby-state VC Label Peer Type Session Tunnel ID Broadcast Tunnel ID Broad BackupTunnel ID CKey NKey StpEnable PwIndex
: : : : : : : : : : : : : :
10 2.2.2.2 primary no 23552 dynamic up 0x10002000 0x10002000 0x0 6 5 0 0
: : : :
GigabitEthernet1/0/0.1 up 2010/08/15 15:41:59 0 days, 0 hours, 19 minutes, 18 seconds
: : : : : : : : : : : : : :
2.2.2.2 up 23552 23552 label 0x10002000 0x10002000 0x0 0x6 0x5 0x10002000 0x0 LSP
Interface Name State Last Up Time Total Up Time
disable enable 0 days, 0 hours, 50 minutes, 23 seconds up
**PW Information: *Peer Ip Address PW State Local VC Label Remote VC Label PW Type Tunnel ID Broadcast Tunnel ID Broad BackupTunnel ID Ckey Nkey Main PW Token Slave PW Token Tnl Type OutInterface GigabitEthernet2/0/0 Backup OutInterface Stp Enable Mac Flapping PW Last Up Time PW Total Up Time
: : : : :
0 0 2010/08/15 15:41:59 0 days, 0 hours, 15 minutes, 3 seconds
Pay attention to the values of boldfaced fields displayed. l PW Signaling is the signaling type of the PW, which can be LDP or BGP. l Member Discovery Style is the member discovery mode, which can be dynamic or static discovery. l Encapsulation Type is the encapsulation type for the VSI, or the encapsulation type of the packets transmitted over the VC. l VSI State is the VSI status. The VSI status should be Up after a VPLS connection is established successfully.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
112
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
l State is the status of the AC bound to the VSI. The AC status should be Up after a VPLS connection is established successfully. l Peer Ip Address is the IP address of a peer. l PW State is the PW status. The PW status should be Up after a VPLS connection is established successfully. Step 2 Run the display vpls forwarding-info command on the commissioning device to view forwarding information of all VSIs. display vpls forwarding-info Total Number : 2, 2 up, 0 down Vsi-Name V1
PeerIP 2.2.2.2
VcOrSiteId 1
PwState UP
The command output shows forwarding information of all VSIs. Check that the PW status of each VSI is Up. Step 3 Run the display l2vpn vsi-list tunnel-policy command on the commissioning device to view the tunnel policy name used in each VSI. display l2vpn vsi-list tunnel-policy p1 Using Tunnel-Policy p1 VSI Instance statistics: ---------------------------------------------------------------------vsi v1
Step 4 Run the ping command on CE1 to test the connectivity of the link between CE1 and CE2. ping 100.1.1.2 PING 100.1.1.2: 56 data bytes, press CTRL_C to break Reply from 100.1.1.2: bytes=56 Sequence=1 ttl=255 Reply from 100.1.1.2: bytes=56 Sequence=2 ttl=255 Reply from 100.1.1.2: bytes=56 Sequence=3 ttl=255 Reply from 100.1.1.2: bytes=56 Sequence=4 ttl=255 Reply from 100.1.1.2: bytes=56 Sequence=5 ttl=255
time=56 ms time=4 ms time=4 ms time=52 ms time=3 ms
--- 100.1.1.2 ping statistics --5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 3/23/56 ms
The preceding command output shows that two CEs in the same VPN can communicate with each other. ----End
Troubleshooting If the VSI of Martini VPLS cannot become Up, complete the following: 1.
Check that the encapsulation types of the two ends are the same. display vsi name tt Vsi Mem PW Mac Encap Mtu Vsi Name Disc Type Learn Type Value State -------------------------------------------------------------------------tt static ldp unqualify vlan 1500 up
l If the encapsulation types of the two ends are different, run the encapsulation { ethernet | vlan } command in the VSI view to change the encapsulation type of one end to be the same as that of the other. l If the encapsulation types of the two ends are the same, go to Step 2. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
113
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
NOTE
A VSI can only be Up when the encapsulation types configured for both ends are the same.
2.
Check that MTUs of the two ends are the same. display vsi name tt Vsi Mem PW Mac Encap Mtu Vsi Name Disc Type Learn Type Value State -------------------------------------------------------------------------tt static ldp unqualify vlan 1500 up
l If the MTUs of the two ends are different, run the mtu mtu-value command in the VSI view to change the MTU of one end to be the same as that of the other. l If the MTUs of the two ends are consistent, go to Step 3. NOTE
A VSI can only be Up when MTUs configured for both ends are the same.
3.
Check that the VSI IDs or negotiation-VC-IDs of the two ends are the same. display vsi name tt verbose ***VSI Name Administrator VSI Isolate Spoken VSI Index PW Signaling Member Discovery Style PW MAC Learn Style Encapsulation Type MTU Diffserv Mode Service Class Color DomainId Domain Name Tunnel Policy Name Ignore AcState Create Time VSI State VSI ID *Peer Router ID VC Label Peer Type Session Tunnel ID Broadcast Tunnel ID CKey NKey StpEnable PwIndex Interface Name State Last Up Time Total Up Time
: : : : : : : : : : : : : : : : : :
tt no disable 3 ldp static unqualify vlan 1500 uniform --255
: : : : : : : : : : :
101 2.2.2.2 187393 dynamic up 0xc0060401 0xc0060401 6 5 0 0
: : : :
GigabitEthernet1/0/0.12 up 2010/02/05 06:36:57 2 days, 2 hours, 40 minutes, 19 seconds
p1 disable 2 days, 2 hours, 47 minutes, 40 seconds up
l If the VSI IDs or negotiation-VC-IDs configured for both ends are different, run the pwsignal ldp command in the VSI-LDP view to change the VSI ID on one end, or run the peer peer-address negotiation-vc-id vc-id command in the VSI-LDP view to change the negotiation-VC-ID on one end, ensuring that the VSI IDs or negotiationVC-IDs of the two ends are the same. l If the VSI IDs or negotiation-vc-ids of the two ends are the same, go to Step 4. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
114
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
NOTE
A VSI can only be Up when the VSI IDs or negotiation-VC-IDs of the two ends are the same.
4.
Check that the LDP session between the two ends is Up. Run the display vsi namevsi-name verbose command to check whether or not the Session field is displayed as Up. display vsi name tt verbose ***VSI Name Administrator VSI Isolate Spoken VSI Index PW Signaling Member Discovery Style PW MAC Learn Style Encapsulation Type MTU Diffserv Mode Service Class Color DomainId Domain Name Tunnel Policy Name Ignore AcState Create Time VSI State VSI ID *Peer Router ID VC Label Peer Type Session Tunnel ID Broadcast Tunnel ID CKey NKey StpEnable PwIndex Interface Name State Last Up Time Total Up Time
: : : : : : : : : : : : : : : : : :
tt no disable 3 ldp static unqualify vlan 1500 uniform --255
: : : : : : : : : : :
101 2.2.2.2 187393 dynamic up 0xc0060401 0xc0060401 6 5 0 0
: : : :
GigabitEthernet1/0/0.12 up 2010/02/05 06:36:57 2 days, 2 hours, 40 minutes, 19 seconds
p1 disable 2 days, 2 hours, 47 minutes, 40 seconds up
l If the LDP session between the two ends is Down, see the section "An LDP Session Is Down" in HUAWEI CX600 Metro Services Platform Troubleshooting to locate the fault and make the LDP session Up. l If the LDP session between the two ends is Up, go to Step 5. NOTE
The two ends can only perform L2VPN negotiation after the LDP session is in the Up state.
5.
Check that the VSI has selected a tunnel. Run the display vsi name vsi-name verbose command. l Check whether or not the Tunnel ID field is displayed as 0x0. If the Tunnel ID field is displayed as 0x0, the VSI has not selected a tunnel. l Check the Tunnel Policy Name field. If this field is not displayed, the VSI has selected an LDP LSP, or no tunnel policy is configured for the VSI. If the VSI selects an MPLSTE tunnel, the tunnel policy must be configured. The Tunnel Policy Name field value indicates the VSI tunnel policy. You can see details of the tunnel policy by running the display this command in the corresponding tunnel policy view.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
115
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
[HUAWEI-tunnel-policy-p1] display this # tunnel-policy p1 tunnel select-seq cr-lsp load-balance-number 1 # NOTE
If the tunnel binding destinationdest-ip-address te { tunnel interface-number } command is configured in the tunnel policy view, you also need to run the mpls te reserved-for-binding command on the tunnel interface.
If the tunnel between the two ends is Down, see the section "An LSP Is Down" or "A TE Tunnel Is Down" in HUAWEI CX600 Metro Services Platform Troubleshooting to locate the fault and make the tunnel Up. If the tunnel between the two ends is Up and the TE interface is correctly configured, go to Step 6. NOTE
A VSI can only be Up when the tunnel between the two ends is also in the Up state.
6.
Check that the AC interfaces on the two ends are Up. Run the display vsi name vsi-name verbose command on the two ends to check that the state of the interface corresponding to the Interface Name field is displayed as Up. l If the AC interfaces on the two ends are Down, see the section "Physical Interface Interconnection" in HUAWEI CX600 Metro Services Platform Troubleshooting to locate the fault and make the AC interfaces Up. l If the AC interfaces on the two ends are Up, go to Step 7. NOTE
A VSI can only be Up when AC interfaces on the two ends are also in the Up state.
7.
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 devices
6.12 Commissioning BFD This section describes how to commission BFD. BFD sessions can quickly detect link faults on a network.
Prerequisite l
The hardware has been checked. For more information, see 4 Checking the Hardware.
l
The link layer has been commissioned. For more information, see 5 Commissioning the Link Layer.
Context On the network shown in Figure 6-13, BFD is configured on the network.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
116
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Figure 6-13 Typical networking for commissioning BFD 1.1.1.1/32
Console PC
2.2.2.2/32
192.168.1.1 / 24 GE1/0/0 network GE2/0/0 GE3/0/0 192.168.1.2 / 24 192.167.1.10 / 24
CX600-A
CX600-B
Procedure Step 1 Run the display current-configuration command on the commissioning device to check if BFD parameters have taken effect. display current-configuration | begin peer-ip bfd to_net_comm bind default-ip interface GigabitEthernet1/0/0 discriminator local 1 discriminator remote 2 detect-multiplier 10 wtr 5 process-interface-status process-pst commit
If a single-hop BFD session is set up, process-pst must be configured. The boldfaced items in the command output show that process-pst has been configured. Step 2 Run the display bfd session command on the commissioning device to view BFD session information. display bfd session all -------------------------------------------------------------------------------Local Remote PeerIpAddr State Type InterfaceName -------------------------------------------------------------------------------1 2 192.168.0.2 Up S_IP_IF GigabitEthernet1/0/0 -------------------------------------------------------------------------------Total UP/DOWN Session Number : 1/0
The boldfaced items in the command output show the BFD session information. Check that the number of BFD sessions is correct, the BFD session status is Up, and the values of Local and Remote are correct. display bfd session all verbose -------------------------------------------------------------------------------Session MIndex : 16384 (One Hop) State : Up Name : atob -------------------------------------------------------------------------------Local Discriminator : 1 Remote Discriminator : 2 Session Detect Mode : Asynchronous Mode Without Echo Function BFD Bind Type : Interface(GigabitEthernet1/0/0) Bind Session Type : Static Bind Peer Ip Address : 192.168.1.2 NextHop Ip Address : 192.168.1.2 Bind Interface : GigabitEthernet1/0/0 FSM Board Id : 6 TOS-EXP : 7 Min Tx Interval (ms) : 10 Min Rx Interval (ms) : 10 Actual Tx Interval (ms): 10 Actual Rx Interval (ms): 10 Local Detect Multi : 10 Detect Interval (ms) : 100 Echo Passive : Disable Acl Number : Destination Port : 3784 TTL : 255 Proc interface status : Enable Process PST : Disable WTR Interval (ms) : 5
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
117
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Active Multi : 3 Last Local Diagnostic : Neighbor Signaled Session Down(Receive AdminDown) Bind Application : IFNET Session TX TmrID : Session Detect TmrID : Session Init TmrID : Session WTR TmrID : Session Echo Tx TmrID : PDT Index : FSM-5000000|RCV-0|IF-0|TOKEN-0 Session Description : ---------------------------------------------------------------------------------Total UP/DOWN Session Number : 1/0
The boldfaced items in the command output show that after single-hop BFD is enabled, a singlehop BFD session is set up in the Up state. If multi-hop BFD is enabled, the command output will show that a multi-hop BFD session is set up in the Up state. If the BFD is associated with interface status successfully, the Proc interface status field will be displayed as Enable. ----End
Troubleshooting If the BFD session cannot become Up, complete the following: 1.
Run the display current-configuration configuration bfd-session command to check whether or not BFD session configurations have been committed. l If the commit field is displayed, BFD session configurations have been committed. Then go to Step 2. l If the commit field is not displayed, BFD session configurations have not been committed. In this case, run the commit command in the BFD session view, and then run the display bfd session all command to check that the BFD session is Up. – If the State field is displayed as Up, the BFD session has been created and no action is required. – If the State field is not Up, go to Step 2.
2.
Run the display bfd statistics session all slot slot-id command repeatedly to check statistics about BFD packets. l If the Received Packets value does not increase, go to Step 3. l If the Send Packets value does not increase, go to Step 4. l If both the Received Packets and Send Packets values increase properly, go to Step 7. l If none of the Received Packets, Send Packets, Received Bad Packets, and Send Bad Packets values increases, go to Step 5. l If the Down Count value increases, the BFD session flaps. In this case, go to Step 5.
3.
Run the display bfd statistics session all slot slot-id command repeatedly to check that the Received Bad Packets value increases properly. l If the Received Bad Packets value increases, the local end receives but discards the BFD packets sent from the remote end. In this case, go to Step 7. l If the Received Bad Packets value does not increase, the local end does not receive BFD packets. In this case, go to Step 5.
4.
Run the display bfd statistics session all slot slot-id command repeatedly to check that the Send Bad Packets value increases properly. l If the Send Bad Packets value increases, the BFD packets are sent but discarded. In this case, go to Step 7.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
118
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
l If the Send Bad Packets value does not increase, the local end does not send BFD packets to the remote end. In this case, go to Step 5. 5.
Run the display bfd statistics session all slot slot-id command repeatedly. If the BFD session still does not go Up, run the ping command on one end to ping the other end of the BFD session. l If the ping fails, follow the procedure described in "The Ping Operation Fails" in the HUAWEI CX600 Metro Services Platform Troubleshooting to rectify the packet forwarding fault. l If the ping succeeds, go to Step 6.
6.
Run the display current-configuration configuration bfd-session command to check the min-tx-interval and min-rx-interval values and determine whether or not the detection time value is larger than the delay value. l If the detection time value is smaller than the delay value, run the detect-multiplier, min-rx-interval, or min-tx-interval command to change the detection time value of the BFD session to be larger than the delay value. l If the detection time value of the BFD session is larger than the delay value, go to Step 7.
7.
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 devices
6.13 Commissioning IP FRR on the Public Network This section describes how to commission IP FRR on the public network. IP FRR can be configured on the public network based on the network planning.
Prerequisites The following configurations are complete and the device is running normally: l
4 Checking the Hardware
l
5 Commissioning the Link Layer
Context IP FRR is configured on the public network shown in Figure 6-14.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
119
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Figure 6-14 Configuring IP FRR on the public network
GE2/0/0 2002::1/64
GE1/0/0 2000::2/64 GE1/0/0 2000::1/64
GE2/0/0 2002::2/64
CX600-A Link A
CX600-T GE2/0/0 2001::1/64
Loopback1 2::2/128 CX600-C
GE1/0/0 2003::2/64
Link B
GE1/0/0 2003::1/64
GE2/0/0 2001::2/64 CX600-B
Procedure Step 1 Check the backup outbound interface and backup next hop on CX- T. [CX-T] display ip routing-table 172.17.1.0 verbose Route Flags: R - relay, D - download to fib -----------------------------------------------------------------------------Routing Table : Public Summary Count : 1 Destination: 172.17.1.0/24 Protocol: OSPF Process ID: 1 Preference: 10 Cost: 3 NextHop: 192.168.10.2 Neighbour: 0.0.0.0 State: Active Adv Age: 00h06m49s Tag: 0 Priority: low Label: NULL QoSInfo: 0x0 IndirectID: 0x0 RelayNextHop: 0.0.0.0 Interface: GigabitEthernet2/0/0 TunnelID: 0x0 Flags: D BkNextHop: 192.168.20.2 BkInterface: GigabitEthernet3/0/0 BkLabel: NULL SecTunnelID: 0x0 BkPETunnelID: 0x0 BkPESecTunnelID: 0x0 BkIndirectID: 0x0
If IP FRR has been configured on the public network, the backup outbound interface and backup next hop are displayed in BkNextHop and BkInterface. ----End
6.14 Commissioning VPN IP FRR This section describes how to commission VPN IP FRR.
Prerequisites The following configurations are complete and the device is running normally: Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
120
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
l
4 Checking the Hardware
l
5 Commissioning the Link Layer
Context On the network shown in Figure 6-15, HUAWEI A and HUAWEI B function as PEs, and HUAWEI C functions as a CE. VPN IP FRR is deployed on this network. Figure 6-15 BGP/MPLS IP VPN networking GE1/0/10 20.1.1.2/24
CX-B GE1/0/11 40.1.1.1/24
GE1/0/10 20.1.1.1/24 CX-A GE6/0/4 30.1.1.1/24
GE1/0/11 40.1.1.2/24 GE1/0/4 30.1.1.2/24 CX-C
Procedure Step 1 Configure a VPN instance and an OSPF multi-instance on HUAWEI A and HUAWEI B. Run the display ip routing-table vpn-instance vpn1 command on HUAWEI A. The command output shows that HUAWEI A has learned routes using OSPF. # Configure HUAWEI A. [HUAWEIA] ip vpn-instance vpn1 [HUAWEIA-vpn-instance-vpn1] route-distinguisher 111:1 [HUAWEIA-vpn-instance-vpn1] vpn-target 100:1 [HUAWEIA-vpn-instance-vpn1] quit [HUAWEIA] interface GigabitEtherent 1/0/10 [HUAWEIA-GigabitEthernet1/0/10] ip binding vpn-instance vpn1 [HUAWEIA-GigabitEthernet1/0/10] ip address 20.1.1.1 24 [HUAWEIA-GigabitEthernet1/0/10] quit [HUAWEIA] interface GigabitEthernet 6/0/4 [HUAWEIA-GigabitEthernet6/0/4] ip binding vpn-instance vpn1 [HUAWEIA-GigabitEthernet6/0/4] ip address 30.1.1.1 24 [HUAWEIA] ospf 1 vpn-instance vpn1 [HUAWEIA-ospf-1] area 0 [HUAWEIA-ospf-1-area-0.0.0.0] network 20.1.1.0 0.0.0.255 [HUAWEIA-ospf-1-area-0.0.0.0] network 30.1.1.0 0.0.0.255
# Configure HUAWEI B. [HUAWEIB] ip vpn-instance vpn1 [HUAWEIB-vpn-instance-vpn1] route-distinguisher 111:1 [HUAWEIB-vpn-instance-vpn1] vpn-target 100:1 [HUAWEIB-vpn-instance-vpn1] quit [HUAWEIB] interface GigabitEthernet 1/0/10 [HUAWEIB-GigabitEthernet1/0/10] ip binding vpn-instance vpn1 [HUAWEIB-GigabitEthernet1/0/10] ip address 20.1.1.2 24
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
121
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
[HUAWEIB-GigabitEthernet1/0/10] quit [HUAWEIB] interface GigabitEthernet 1/0/11 [HUAWEIB-GigabitEthernet1/0/11] ip binding vpn-instance vpn1 [HUAWEIB-GigabitEthernet1/0/11] ip address 40.1.1.1 24 [HUAWEIB] ospf 1 vpn-instance vpn1 [HUAWEIB-ospf-1] area 0 [HUAWEIB-ospf-1-area-0.0.0.0] network 20.1.1.0 0.0.0.255 [HUAWEIB-ospf-1-area-0.0.0.0] network 40.1.1.0 0.0.0.255
Run the display ip routing-table vpn-instance vpn1 command on HUAWEI A. The command output shows that HUAWEI A has learned two routes destined for 40.1.1.0 using OSPF. display ip routing-table vpn-instance vpn1 Route Flags: R - relay, D - download to fib -----------------------------------------------------------------------------Routing Tables: vpn1 Destinations : 10 Routes : 11 Destination/Mask Proto ...... 40.1.1.0/24 OSPF GigabitEthernet1/0/10
Pre
Cost
10 OSPF
Flags NextHop
2
D
10
2
Interface 20.1.1.2 D
30.1.1.2
GigabitEthernet6/0/4 ......
Step 2 Configure OSPF on HUAWEI C. Then run the display ip routing-table command. The command output shows that HUAWEI C has learned two routes destined for 20.1.1.0 using OSPF. The two routes implement load balancing. [HUAWEIC] ospf 1 [HUAWEIC-ospf-1] area 0 [HUAWEIC-ospf-1-area-0.0.0.0] network 30.1.1.0 0.0.0.255 [HUAWEIC-ospf-1-area-0.0.0.0] network 40.1.1.0 0.0.0.255 [HUAWEIC] display ip routing-table Route Flags: R - relay, D - download to fib -----------------------------------------------------------------------------Routing Tables: Public Destinations : 7 Routes : 8 Destination/Mask ...... 20.1.1.0/24
Proto
Pre
Cost
OSPF OSPF
10 10
2 2
Flags D D
NextHop
Interface
40.1.1.1 GigabitEthernet1/0/11 30.1.1.1 GigabitEthernet1/0/4
......
Step 3 Set the cost values for OSPF interfaces to allow the link from HUAWEI A to HUAWEI B to be preferred among all links from HUAWEI A to 40.1.1.0. Then run the display ip routing-table vpn-instance vpn1 command. The command output shows that HUAWEI A has learned routes using OSPF and that GE 6/0/4 is the backup outbound interface. # Set the cost value for GE 6/0/4 on HUAWEI A to 100 so that OSPF prefers the link from HUAWEI A to HUAWEI B. [HUAWEIA] interface GigabitEthernet 6/0/4 [HUAWEIA-GigabitEthernet6/0/4] ospf cost 100
# Set the cost value for GE 1/0/4 on HUAWEI C to 100 so that OSPF prefers the link from HUAWEI A to HUAWEI B. [HUAWEIC] interface GigabitEthernet 1/0/4 [HUAWEIC-GigabitEthernet1/0/4] ospf cost 100 display ip routing-table vpn-instance vpn1 Route Flags: R - relay, D - download to fib -----------------------------------------------------------------------------Routing Tables: vpn1
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
122
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Destinations : 10 Routes : 10 Destination/Mask Proto ...... 40.1.1.0/24 OSPF GigabitEthernet1/0/10 ......
Pre 10
Cost 2
Flags NextHop D
Interface 20.1.1.2
Step 4 Run the ping–vpn-instance vpn1 40.1.1.1 command on HUAWEI A while removing the optical fiber of GE 1/0/10 on HUAWEI A. Then check the ping result. The ping is successful before the optical fiber of GE 1/0/10 is removed and fails temporarily after the optical fiber is removed. After traffic is switched to the link from HUAWEI A to HUAWEI C, the ping becomes successful again. [HUAWEIA] ping –vpn-instance vpn1 40.1.1.1 PING 40.1.1.1: 56 data bytes, press CTRL_C to break Reply from 40.1.1.1: bytes=56 Sequence=1 ttl=255 time=1 ms Reply from 40.1.1.1: bytes=56 Sequence=2 ttl=255 time=2 ms Request time out Request time out Request time out Request time out Reply from 40.1.1.1: bytes=56 Sequence=7 ttl=255 time=2 ms Reply from 40.1.1.1: bytes=56 Sequence=8 ttl=255 time=1 ms Reply from 40.1.1.1: bytes=56 Sequence=9 ttl=255 time=2 ms
Step 5 Insert the optical fiber of GE 1/0/10 on HUAWEI A. Configure a routing policy, a backup next hop, and a backup outbound interface, configure an if-match clause, and enable VPN IP FRR on HUAWEI A. [HUAWEIA] ip ip-prefix frr1 permit 40.1.1.0 24 [HUAWEIA] route-policy ip_frr_rp permit node 10 [HUAWEIA-route-policy] if-match ip-prefix frr1 [HUAWEIA-route-policy] apply backup-nexthop 30.1.1.2 [HUAWEIA-route-policy] apply backup-interface GigabitEthernet 6/0/4 [HUAWEIA-route-policy] quit [HUAWEIA] ip vpn-instance vpn1 [HUAWEIA-vpn-instance-vpn1] ip frr route-policy ip_frr_rp [HUAWEIA-vpn-instance-vpn1] quit
Step 6 Run the display ip routing-table vpn-instance vpn1 40.1.1.0 24 verbose command on HUAWEI A to check the backup outbound interface and backup next hop. The command output shows that the backup outbound interface is GE 6/0/4 and the IP address of the backup next hop is 30.1.1.2. display ip routing-table vpn-instance vpn1 40.1.1.0 24 verbose Destination: 40.1.1.0/24 Protocol: OSPF Process ID: 1 Preference: 10 Cost: 2 NextHop: 20.1.1.2 Neighbour: 0.0.0.0 State: Active Adv Age: 00h01m18s Tag: 0 Priority: low Label: NULL QoSInfo: 0x0 IndirectID: 0x0 RelayNextHop: 0.0.0.0 Interface: GigabitEthernet1/0/10 TunnelID: 0x0 Flags: D BkNextHop: 30.1.1.2 BkInterface: GigabitEthernet6/0/4 BkLabel: NULL SecTunnelID: 0x0 BkPETunnelID: 0x0 BkPESecTunnelID: 0x0 BkIndirectID: 0x0
Step 7 Run the ping–vpn-instance vpn1 40.1.1.1 command on HUAWEI A while removing the optical fiber of GE 1/0/10 on HUAWEI A. Then check the ping result. The command output shows a lower packet loss rate during link switching. [HUAWEIA] ping –vpn-instance vpn1 40.1.1.1 PING 40.1.1.1: 56 data bytes, press CTRL_C to break
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
123
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Reply from 40.1.1.1: bytes=56 Sequence=1 ttl=255 time=1 ms Reply from 40.1.1.1: bytes=56 Sequence=2 ttl=255 time=2 ms Reply from 40.1.1.1: bytes=56 Sequence=3 ttl=255 time=2 ms Request time out Reply from 40.1.1.1: bytes=56 Sequence=5 ttl=255 time=2 ms Reply from 40.1.1.1: bytes=56 Sequence=6 ttl=255 time=1 ms Reply from 40.1.1.1: bytes=56 Sequence=7 ttl=255 time=2 ms
----End
6.15 Commissioning OSPF FRR This section describes how to commission OSPF FRR.
Prerequisites The following configurations are complete and the device is running normally: l
4 Checking the Hardware
l
5 Commissioning the Link Layer
Context On the network shown in Figure 6-16, OSPF FRR is deployed on the network. Figure 6-16 Typical networking for commissioning OSPF FRR
CX-B Router-id 2.2.2.2
GE1/0/1 1.2.1.1/24
co st =
9
GE1/0/1 1.2.1.2/24
GE1/0/2 2.3.1.2/24 co st = 5 GE1/0/3 2.3.1.3/24
cost = 4 cost = 55 GE1/0/2 GE1/0/1 GE1/0/2 GE1/0/1 CX-A 1.3.1.1/24 1.3.1.3/24 CX-C 3.4.1.3/24 3.4.1.4/24 CX-D Router-id Router-id Router-id 4.4.4.4 1.1.1.1 3.3.3.3
Procedure Step 1 Run the display ospf [ process-id ] routing command to check information about the primary and backup links after OSPF IP FRR is enabled. display ospf routing router-id 4.4.4.4 OSPF Process 1 with Router ID 1.1.1.1 Destination : 4.4.4.4
Issue 04 (2014-04-01)
Route Type : Intra-area
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
124
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Area : 0.0.0.1 Type : ASBR URT Cost : 59 NextHop : 1.3.1.3 Backup Nexthop : 1.2.1.2 Backup Type : LFA LINK
AdvRouter Age
: 4.4.4.4 : 00h31m27s
Interface : GigabitEthernet1/0/2 Backup Interface : GigabitEthernet1/0/1
The preceding display shows that a backup route is generated on CX-, including information about the backup next hop: Backup NextHop is address of the backup next hop, Backup Interface is outbound interface of the backup next hop, Backup Type is type of the backup next hop. ----End
Troubleshooting If OSPF FRR forwarding fails, perform the following steps: 1.
Run the display ospf peer command to check whether the OSPF neighbor relationship has been established. display ospf peer OSPF Process 1 with Router ID 1.1.1.1 Neighbors Area 0.0.0.0 interface 1.3.1.1(GigabitEthernet1/0/2)'s neighbors Router ID: 4.4.4.4 Address: 1.3.1.3 GR State: Normal State: Full Mode:Nbr is Slave Priority: 1 DR: 1.3.1.3 BDR: None MTU: 0 Dead timer due in 35 sec Retrans timer interval: 5 Neighbor is up for 00:00:05 Authentication Sequence: [ 0 ]
In the preceding command output, check whether the number of neighbors is correct, whether the State field displays Full, and whether the neighbor is Up for a long time. If the State field displays Full, LSDB synchronization is complete, and the OSPF neighbor relationship is Full. If the neighbor is Up for a short period of time, the OSPF neighbor relationship was recently interrupted. l If the OSPF neighbor relationship has not been established, see the chapter OSPF in HUAWEI CX600 Metro Services Platform Troubleshooting. l If the OSPF neighbor relationship has been established, go to Step 2. 2.
Run the display current-configuration configuration ospf command to check whether OSPF IP FRR has been enabled. display current-configuration configuration ospf # ospf 1 router-id 1.1.1.1 frr frr-policy route route-policy abc loop-free-alternate area 0.0.0.1 network 1.2.1.0 0.0.0.255 network 1.3.1.0 0.0.0.255
If OSPF IP FRR has been enabled, go to Step 3. If OSPF IP FRR has not been enabled, see the chapter "Configuring OSPF IP FRR" in HUAWEI CX600 Metro Services Platform Configuration Guide - IP Routing. 3. Issue 04 (2014-04-01)
Collect the following information and contact Huawei technical support personnel: Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
125
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
l Results of the preceding operation procedure l Configuration files, log files, and alarm files of the devices
6.16 Commissioning RSVP GR This section describes how to commission RSVP GR.
Prerequisites l
The hardware has been checked. For more information, see 4 Checking the Hardware.
l
The link layer has been commissioned. For more information, see 5 Commissioning the Link Layer.
Context On the network shown in Figure 6-17, LSRA, LSRB, and LSRC are equipped with dual main control boards. Three LSRs learn routes from one another using the IS-IS protocol and then use the RSVP protocol to establish a TE tunnel from LSRA to LSRC. RSVP GR is required to ensure that MPLS forwarding is not interrupted when ae master/slave switchover of main control boards occurs on LSRA, LSRB, or LSRC. Figure 6-17 Networking diagram for RSVP GR Loopback1 Loopback1 Loopback1 2.2.2.2/32 3.3.3.3/32 1.1.1.1/32 GE2/0/0 GE1/0/0 GE2/0/0 GE1/0/0 10.1.1.1/24 10.1.1.2/24 20.1.1.1/24 20.1.1.2/24 LSRA
LSRB
LSRC
Procedure Step 1 Configure basic IS-IS functions on LSRA, LSRB and LSRC. # Configure LSRA. [LSRA] isis 1 [LSRA-isis-1] network-entity 00.0005.0000.0000.0001.00 [LSRA-isis-1] is-level level-2 [LSRA-isis-1] quit [LSRA] interface gigabitethernet 1/0/0 [LSRA-GigabitEthernet1/0/0] isis enable 1 [LSRA-GigabitEthernet1/0/0] quit [LSRA] interface loopback 1 [LSRA-LoopBack1] isis enable 1 [LSRA-LoopBack1] quit
# Configure LSRB. [LSRB] isis 1 [LSRB-isis-1] network-entity 00.0005.0000.0000.0002.00 [LSRB-isis-1] is-level level-2 [LSRB-isis-1] quit [LSRB] interface gigabitethernet 1/0/0
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
126
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
[LSRB-GigabitEthernet1/0/0] isis enable 1 [LSRB-GigabitEthernet1/0/0] quit [LSRB] interface gigabitethernet 2/0/0 [LSRB-GigabitEthernet2/0/0] isis enable 1 [LSRB-GigabitEthernet2/0/0] quit [LSRB] interface loopback 1 [LSRB-LoopBack1] isis enable 1 [LSRB-LoopBack1] quit
# Configure LSRC. [LSRC] isis 1 [LSRC-isis-1] network-entity 00.0005.0000.0000.0003.00 [LSRC-isis-1] is-level level-2 [LSRC-isis-1] quit [LSRC] interface gigabitethernet 2/0/0 [LSRC-GigabitEthernet2/0/0] isis enable 1 [LSRC-GigabitEthernet2/0/0] quit [LSRC] interface loopback 1 [LSRC-LoopBack1] isis enable 1 [LSRC-LoopBack1] quit
After completing the configuration, run the display ip routing-table command on each LSR. LSRs have learned routes from each other. Step 2 Configure basic MPLS capability and enable MPLS TE, RSVP-TE, and CSPF. Configure maximum bandwidth and maximum reservable bandwidth of interfaces. # Configure LSRA. [LSRA] mpls lsr-id 1.1.1.1 [LSRA] mpls [LSRA-mpls] mpls te [LSRA-mpls] mpls rsvp-te [LSRA-mpls] mpls te cspf [LSRA-mpls] quit [LSRA] interface gigabitethernet [LSRA-GigabitEthernet1/0/0] mpls [LSRA-GigabitEthernet1/0/0] mpls [LSRA-GigabitEthernet1/0/0] mpls [LSRA-GigabitEthernet1/0/0] mpls [LSRA-GigabitEthernet1/0/0] mpls [LSRA-GigabitEthernet1/0/0] quit
1/0/0 te rsvp-te te bandwidth max-reservable-bandwidth 100000 te bandwidth bc0 100000
# Configure LSRB. [LSRB] mpls lsr-id 2.2.2.2 [LSRB] mpls [LSRB-mpls] mpls te [LSRB-mpls] mpls rsvp-te [LSRB-mpls] quit [LSRB] interface gigabitethernet [LSRB-GigabitEthernet1/0/0] mpls [LSRB-GigabitEthernet1/0/0] mpls [LSRB-GigabitEthernet1/0/0] mpls [LSRB-GigabitEthernet1/0/0] quit [LSRB] interface gigabitethernet [LSRB-GigabitEthernet2/0/0] mpls [LSRB-GigabitEthernet2/0/0] mpls [LSRB-GigabitEthernet2/0/0] mpls [LSRB-GigabitEthernet2/0/0] mpls [LSRB-GigabitEthernet2/0/0] mpls [LSRB-GigabitEthernet2/0/0] quit
1/0/0 te rsvp-te 2/0/0 te rsvp-te te bandwidth max-reservable-bandwidth 100000 te bandwidth bc0 100000
# Configure LSRC. [LSRC] mpls lsr-id 3.3.3.3
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
127
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
[LSRC] mpls [LSRC-mpls] mpls te [LSRC-mpls] mpls rsvp-te [LSRC-mpls] quit [LSRC] interface gigabitethernet 2/0/0 [LSRC-GigabitEthernet2/0/0] mpls [LSRC-GigabitEthernet2/0/0] mpls te [LSRC-GigabitEthernet2/0/0] mpls rsvp-te [LSRC-GigabitEthernet2/0/0] quit
Step 3 Configure IS-IS TE and enable IS-IS GR. # Configure LSRA. [LSRA] isis 1 [LSRA-isis-1] [LSRA-isis-1] [LSRA-isis-1] [LSRA-isis-1] [LSRA-isis-1]
cost-style wide is-name LSRA traffic-eng level-2 graceful-restart quit
# Configure LSRB. [LSRB] isis 1 [LSRB-isis-1] [LSRB-isis-1] [LSRB-isis-1] [LSRB-isis-1] [LSRB-isis-1]
cost-style wide is-name LSRB traffic-eng level-2 graceful-restart quit
# Configure LSRC. [LSRC] isis 1 [LSRC-isis-1] [LSRC-isis-1] [LSRC-isis-1] [LSRC-isis-1] [LSRC-isis-1]
cost-style wide is-name LSRC traffic-eng level-2 graceful-restart quit
Step 4 Configure an MPLS TE tunnel on LSRA. [LSRA] interface tunnel 1/0/0 [LSRA-Tunnel1/0/0] ip address unnumbered interface loopback 1 [LSRA-Tunnel1/0/0] tunnel-protocol mpls te [LSRA-Tunnel1/0/0] destination 3.3.3.3 [LSRA-Tunnel1/0/0] mpls te tunnel-id 100 [LSRA-Tunnel1/0/0] mpls te signal-protocol rsvp-te [LSRA-Tunnel1/0/0] mpls te bandwidth ct0 20000 [LSRA-Tunnel1/0/0] mpls te commit [LSRA-Tunnel1/0/0] quit
After completing the configuration, run the display interface tunnel command on LSRA. The interface status of the MPLS TE tunnel is Up. [LSRA] display interface tunnel Tunnel1/0/0 current state : UP Line protocol current state : UP Last up time: 2007-10-29, 16:35:10 Description : Tunnel1/0/0 Interface ...
Step 5 Enable RSVP GR. # Configure LSRA. [LSRA] mpls [LSRA-mpls] mpls rsvp-te hello [LSRA-mpls] mpls rsvp-te hello full-gr
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
128
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
[LSRA-mpls] quit [LSRA] interface gigabitethernet 1/0/0 [LSRA-GigabitEthernet1/0/0] mpls rsvp-te hello
# Configure LSRB. [LSRB] mpls [LSRB-mpls] mpls rsvp-te hello [LSRB-mpls] mpls rsvp-te hello full-gr [LSRB-mpls] quit [LSRB] interface gigabitethernet 1/0/0 [LSRB-GigabitEthernet1/0/0] mpls rsvp-te hello [LSRB] interface gigabitethernet 2/0/0 [LSRB-GigabitEthernet2/0/0] mpls rsvp-te hello
# Configure LSRC. [LSRC] mpls [LSRC-mpls] mpls rsvp-te hello [LSRC-mpls] mpls rsvp-te hello full-gr [LSRC-mpls] quit [LSRC] interface gigabitethernet 2/0/0 [LSRC-GigabitEthernet2/0/0] mpls rsvp-te hello
Step 6 After completing the configuration, run the display mpls rsvp-te graceful-restart command on LSRB to view the local GR status, restart time, and recovery time. [LSRB] display mpls rsvp-te graceful-restart Display Mpls Rsvp te graceful restart information LSR ID: 2.2.2.2 Graceful-Restart Capability: GR-Self GR-Support Restart Time: 90060 Milli Second Recovery Time: 0 Milli Second GR Status: Gracefully Restart Not going on Number of Restarting neighbors: 0 Number of LSPs recovered: 0 Received Gr Path message count: 0 Send Gr Path message count: 0 Received RecoveryPath message count: 0 Send RecoveryPath message count: 0
Run the display mpls rsvp-te graceful-restart peer command on LSRB to view the GR status of the neighboring LSR. [LSRB] display mpls rsvp-te graceful-restart peer Neighbor on Interface GigabitEthernet1/0/0 Neighbor Addr: 10.1.1.1 SrcInstance: 47860 NbrSrcInstance: 49409 Neighbor Capability: Can Do Self GR Can Support GR GR Status: Normal Restart Time: 90060 Milli Second Recovery Time: 0 Milli Second Stored GR message number: 0 PSB Count: 0 RSB Count: 0 Total to be Recover PSB Count: 0 Recovered PSB Count: 0 Total to be Recover RSB Count: 0 Recovered RSB Count: 0 P2MP PSB Count: 0 P2MP RSB Count: 0 Total to be Recover P2MP PSB Count: 0 Recovered P2MP PSB Count: 0 Total to be Recover P2MP RSB Count: 0 Recovered P2MP RSB Count: 0
Run the display this interface command on LSRA. The Tunnel up/down statistics value is 0, indicating that the tunnel has never flapped. [LSRA] display this interface Tunnel1/0/0 current state : UP Line protocol current state : UP
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
129
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Last line protocol up time : 2010-07-13 16:10:09 Description: Tunnel1/0/0 Interface Route Port,The Maximum Transmit Unit is 1500 Internet protocol processing : disabled Encapsulation is TUNNEL, loopback not set Tunnel destination 3.3.3.3 Tunnel up/down statistics 0 Tunnel protocol/transport MPLS/MPLS, ILM is available, ...
Step 7 Run the slave switchover command on LSRB to forcibly perform a master/slave switchover of main control boards. [LSRB] slave switchover enable [LSRB] slave switchover Caution!!! Confirm switch slave to master[Y/N] ? [LSRB] y
Run the display this interface command on LSRA again to view that the value of Tunnel up/ down statistics is still 0, indicating that the tunnel did not flap after the master/slave switchover of main control boards on LSRB. This means that RSVP GR has been configured successfully. [LSRA] display this interface Tunnel1/0/0 current state : UP Line protocol current state : UP Last line protocol up time : 2010-07-13 16:13:53 Description: Tunnel1/0/0 Interface Route Port,The Maximum Transmit Unit is 1500 Internet protocol processing : disabled Encapsulation is TUNNEL, loopback not set Tunnel destination 3.3.3.3 Tunnel up/down statistics 0 Tunnel protocol/transport MPLS/MPLS, ILM is available, ...
----End
6.17 Commissioning MPLS TE FRR This section describes how to commission MPLS TE FRR.
Prerequisites The following configurations are complete and the device is running normally: l
4 Checking the Hardware
l
5 Commissioning the Link Layer
Context On the network shown in Figure 6-18, MPLS TE FRR is deployed on the network.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
130
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Figure 6-18 Typical networking for commissioning MPLS TE FRR
3.3.3.3/32 GE1/0/1 23.23.1.3/24
GE1/0/0 13.13.1.3/24 CX-C
2.2.2.2/32
1.1.1.1/32 GE1/0/1 13.13.1.1/24 CX-A
GE1/0/0 12.12.1.1/24
GE1/0/1 23.23.1.2/24 GE1/0/0 12.12.1.2/24
CX-B
Procedure Step 1 Configure a primary TE tunnel named Tunnel1/1/1 on CX- A, with the destination IP address as the LSR ID of CX- B; configure an explicit path for the primary TE tunnel; enable FRR. Configure a bypass TE tunnel named Tunnel1/1/2 and configure an explicit path for the bypass TE tunnel to protect the primary LSP's outbound interface GE 1/0/0. Then run the display mpls te tunnel command to check Tunnel1/1/1 and Tunnel1/1/2 configurations. The tunnels are Up. display mpls te tunnel name Tunnel1/1/1 verbose Tunnel Name : Tunnel1/1/1 Tunnel State Desc : CR-LSP is Up Tunnel Attributes : Session ID : 1 Ingress LSR ID : 1.1.1.1 Egress LSR ID: 2.2.2.2 Admin State : UP Oper State : UP Signaling Protocol : RSVP Tie-Breaking Policy : None Metric Type : None BypassBW Flag : Not Supported BypassBW Type : Bypass BW : Bfd Cap : None Retry Int : 10 sec Reopt : Disabled Reopt Freq : Auto BW : Disabled Current Collected BW: Auto BW Freq : Min BW : Max BW : Tunnel Group : Primary Interfaces Protected: Excluded IP Address : Is On Radix-Tree : Yes Referred LSP Count: 0 Primary Tunnel : Pri Tunn Sum : Backup Tunnel : Group Status : Up Oam Status : Up IPTN InLabel : BackUp Type : None BestEffort : Disabled Secondary HopLimit : BestEffort HopLimit : Secondary Explicit Path Name: Secondary Affinity Prop/Mask: 0x0/0x0 BestEffort Affinity Prop/Mask: 0x0/0x0 IsConfigLspConstraint: No Primary LSP ID Setup Priority
Issue 04 (2014-04-01)
: :
1.1.1.1:1 7
Hold Priority:
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
7
131
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Affinity Prop/Mask : 0x0/0x0 Configured Bandwidth Information CT0 Bandwidth(Kbit/sec) : 0 CT1 CT2 Bandwidth(Kbit/sec) : 0 CT3 CT4 Bandwidth(Kbit/sec) : 0 CT5 CT6 Bandwidth(Kbit/sec) : 0 CT7 Actual Bandwidth Information CT0 Bandwidth(Kbit/sec) : 0 CT1 CT2 Bandwidth(Kbit/sec) : 0 CT3 CT4 Bandwidth(Kbit/sec) : 0 CT5 CT6 Bandwidth(Kbit/sec) : 0 CT7 Explicit Path Name : primary Record Route : Enabled Route Pinning : Disabled FRR Flag : Enabled IdleTime Remain : [CX-A] display mpls te tunnel name Tunnel1/1/2 Tunnel Name : Tunnel1/1/2 Tunnel State Desc : CR-LSP is Up Tunnel Attributes : Session ID : 2 Ingress LSR ID : 1.1.1.1 Admin State : UP Signaling Protocol : RSVP Tie-Breaking Policy : None BypassBW Flag : Supported BypassBW Type : Bfd Cap : None Reopt : Disabled Auto BW : Disabled Current Collected BW: Min BW : Tunnel Group : Primary Interfaces Protected: GE1/0/2 Excluded IP Address : Is On Radix-Tree : Yes Primary Tunnel : Backup Tunnel : Group Status : Up IPTN InLabel : BackUp Type : None Secondary HopLimit : BestEffort HopLimit : Secondary Explicit Path Name: Secondary Affinity Prop/Mask: 0x0/0x0 BestEffort Affinity Prop/Mask: 0x0/0x0 IsConfigLspConstraint: No Primary LSP ID : 1.1.1.1:1 Setup Priority : 7 Affinity Prop/Mask : 0x0/0x0 Configured Bandwidth Information CT0 Bandwidth(Kbit/sec) : 0 CT2 Bandwidth(Kbit/sec) : 0 CT4 Bandwidth(Kbit/sec) : 0 CT6 Bandwidth(Kbit/sec) : 0 Actual Bandwidth Information CT0 Bandwidth(Kbit/sec) : 0 CT2 Bandwidth(Kbit/sec) : 0 CT4 Bandwidth(Kbit/sec) : 0 CT6 Bandwidth(Kbit/sec) : 0 Explicit Path Name : bypass Record Route : Enabled Route Pinning : Disabled FRR Flag : Disabled IdleTime Remain : -
Issue 04 (2014-04-01)
Resv Style
:
SE
Bandwidth(Kbit/sec) Bandwidth(Kbit/sec) Bandwidth(Kbit/sec) Bandwidth(Kbit/sec)
: : : :
0 0 0 0
Bandwidth(Kbit/sec) : 0 Bandwidth(Kbit/sec) : 0 Bandwidth(Kbit/sec) : 0 Bandwidth(Kbit/sec) : 0 Hop Limit : Record Label : Enabled
verbose
Egress LSR ID: Oper State :
2.2.2.2. UP
Metric Type
:
None
Bypass BW Retry Int Reopt Freq
: : :
10 sec -
Auto BW Freq : Max BW :
-
Referred LSP Count: Pri Tunn Sum : -
0
Oam Status
:
Up
BestEffort
:
Disabled
Hold Priority: Resv Style :
7 SE
CT1 CT3 CT5 CT7
Bandwidth(Kbit/sec) Bandwidth(Kbit/sec) Bandwidth(Kbit/sec) Bandwidth(Kbit/sec)
CT1 CT3 CT5 CT7
Bandwidth(Kbit/sec) : 0 Bandwidth(Kbit/sec) : 0 Bandwidth(Kbit/sec) : 0 Bandwidth(Kbit/sec) : 0 Hop Limit : Record Label : Disabled
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
: : : :
0 0 0 0
132
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
[CX-A] display mpls lsp statistics Lsp Type Total Ingress Transit Egress STATIC LSP 0 0 0 0 STATIC CRLSP 0 0 0 0 LDP LSP 0 0 0 0 RSVP CRLSP 2 2 0 0 BGP LSP 0 0 0 0 ASBR LSP 0 0 0 0 BGP IPV6 LSP 0 0 0 0 L3VPN IPV6 LSP 0 0 0 0 ---------------------------------------------------------------------LSP 0 0 0 0 CRLSP 2 2 0 0 ---------------------------------------------------------------------Lsp Type IngressLspBypassState TransitLspBypassState ExistNotUsed InUse ExistNotUsed InUse RSVP CRLSP 1 0 0 0 -----------------------------------------------------------
Step 2 Run the ping lsp -c 100 -m 100 te Tunnel 1/1/1 command on CX- A. Then open another window on CX- A and run the shutdown command to disable GE 1/0/0 during the ping operation. The display command output shows that the LSP is still Up and few packets are discarded because FRR is enabled. [CX-A] ping lsp -c 100 -m 100 te Tunnel 1/1/1 LSP PING FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel1/1/1 : 100 CTRL_C to break Reply from 2.2.2.2: bytes=100 Sequence=1 time = 11 ms Reply from 2.2.2.2: bytes=100 Sequence=2 time = 11 ms Reply from 2.2.2.2: bytes=100 Sequence=3 time = 10 ms Reply from 2.2.2.2: bytes=100 Sequence=4 time = 10 ms Reply from 2.2.2.2: bytes=100 Sequence=5 time = 12 ms Reply from 2.2.2.2: bytes=100 Sequence=6 time = 11 ms Reply from 2.2.2.2: bytes=100 Sequence=7 time = 11 ms Reply from 2.2.2.2: bytes=100 Sequence=8 time = 9 ms Reply from 2.2.2.2: bytes=100 Sequence=9 time = 9 ms Reply from 2.2.2.2: bytes=100 Sequence=10 time = 13 ms Reply from 2.2.2.2: bytes=100 Sequence=11 time = 10 ms Reply from 2.2.2.2: bytes=100 Sequence=12 time = 11 ms Reply from 2.2.2.2: bytes=100 Sequence=13 time = 9 ms Reply from 2.2.2.2: bytes=100 Sequence=14 time = 12 ms Reply from 2.2.2.2: bytes=100 Sequence=15 time = 9 ms Request time out Reply from 2.2.2.2: bytes=100 Sequence=17 time = 13 ms Reply from 2.2.2.2: bytes=100 Sequence=18 time = 9 ms Reply from 2.2.2.2: bytes=100 Sequence=19 time = 12 ms Reply from 2.2.2.2: bytes=100 Sequence=20 time = 11 ms Reply from 2.2.2.2: bytes=100 Sequence=21 time = 9 ms Reply from 2.2.2.2: bytes=100 Sequence=22 time = 14 ms Reply from 2.2.2.2: bytes=100 Sequence=23 time = 12 ms Reply from 2.2.2.2: bytes=100 Sequence=24 time = 11 ms Reply from 2.2.2.2: bytes=100 Sequence=25 time = 13 ms Reply from 2.2.2.2: bytes=100 Sequence=26 time = 13 ms Reply from 2.2.2.2: bytes=100 Sequence=27 time = 10 ms Reply from 2.2.2.2: bytes=100 Sequence=28 time = 9 ms Reply from 2.2.2.2: bytes=100 Sequence=29 time = 9 ms Reply from 2.2.2.2: bytes=100 Sequence=30 time = 11 ms Reply from 2.2.2.2: bytes=100 Sequence=31 time = 10 ms Reply from 2.2.2.2: bytes=100 Sequence=32 time = 11 ms Reply from 2.2.2.2: bytes=100 Sequence=33 time = 13 ms Reply from 2.2.2.2: bytes=100 Sequence=34 time = 11 ms Reply from 2.2.2.2: bytes=100 Sequence=35 time = 10 ms Reply from 2.2.2.2: bytes=100 Sequence=36 time = 9 ms Reply from 2.2.2.2: bytes=100 Sequence=37 time = 9 ms Reply from 2.2.2.2: bytes=100 Sequence=38 time = 11 ms Reply from 2.2.2.2: bytes=100 Sequence=39 time = 12 ms Reply from 2.2.2.2: bytes=100 Sequence=40 time = 10 ms
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
data bytes, press
133
HUAWEI CX600 Metro Service Platform Commissioning Guide Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply Reply
from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from from
2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2: 2.2.2.2:
6 Commissioning Services and Protocols bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100 bytes=100
Sequence=41 time = 9 ms Sequence=42 time = 11 ms Sequence=43 time = 11 ms Sequence=44 time = 12 ms Sequence=45 time = 11 ms Sequence=46 time = 9 ms Sequence=47 time = 10 ms Sequence=48 time = 9 ms Sequence=49 time = 10 ms Sequence=50 time = 13 ms Sequence=51 time = 11 ms Sequence=52 time = 9 ms Sequence=53 time = 9 ms Sequence=54 time = 11 ms Sequence=55 time = 13 ms Sequence=56 time = 11 ms Sequence=57 time = 9 ms Sequence=58 time = 11 ms Sequence=59 time = 12 ms Sequence=60 time = 10 ms Sequence=61 time = 9 ms Sequence=62 time = 11 ms Sequence=63 time = 9 ms Sequence=64 time = 9 ms Sequence=65 time = 10 ms Sequence=66 time = 11 ms Sequence=67 time = 12 ms Sequence=68 time = 8 ms Sequence=69 time = 9 ms Sequence=70 time = 13 ms Sequence=71 time = 9 ms Sequence=72 time = 10 ms Sequence=73 time = 10 ms Sequence=74 time = 11 ms Sequence=75 time = 10 ms Sequence=76 time = 12 ms Sequence=77 time = 10 ms Sequence=78 time = 18 ms Sequence=79 time = 11 ms Sequence=80 time = 11 ms Sequence=81 time = 13 ms Sequence=82 time = 10 ms Sequence=83 time = 11 ms Sequence=84 time = 10 ms Sequence=85 time = 19 ms Sequence=86 time = 9 ms Sequence=87 time = 15 ms Sequence=88 time = 11 ms Sequence=89 time = 11 ms Sequence=90 time = 11 ms Sequence=91 time = 11 ms Sequence=92 time = 13 ms Sequence=93 time = 10 ms Sequence=94 time = 12 ms Sequence=95 time = 10 ms Sequence=96 time = 9 ms Sequence=97 time = 9 ms Sequence=98 time = 17 ms Sequence=99 time = 12 ms Sequence=100 time = 10 ms
--- FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel1/1/1 ping statistics --100 packet(s) transmitted 99 packet(s) received 1.00% packet loss round-trip min/avg/max = 8/10/19 ms
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
134
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
[CX-A] display mpls lsp statistics Lsp Type Total Ingress Transit Egress STATIC LSP 0 0 0 0 STATIC CRLSP 0 0 0 0 LDP LSP 0 0 0 0 RSVP CRLSP 2 2 0 0 BGP LSP 0 0 0 0 ASBR LSP 0 0 0 0 BGP IPV6 LSP 0 0 0 0 L3VPN IPV6 LSP 0 0 0 0 ---------------------------------------------------------------------LSP 0 0 0 0 CRLSP 2 2 0 0 ---------------------------------------------------------------------Lsp Type IngressLspBypassState TransitLspBypassState ExistNotUsed InUse ExistNotUsed InUse RSVP CRLSP 0 1 0 0 ---------------------------------------------------------------------
Step 3 Run the undo shutdown command on CX- A to enable GE 1/0/0 and delete Tunnel1/1/2. The display command output shows that Tunnel1/1/1 is Up and is not bound to FRR and that Tunnel1/1/2 is deleted, [CX-A] display ip interface brief Tunnel *down: administratively down !down: FIB overload down (l): loopback (s): spoofing Interface IP Address/Mask Physical Protocol Tunnel1/1/1 1.1.1.1/32 up up [CX-A] display mpls lsp statistics Lsp Type Total Ingress Transit Egress STATIC LSP 0 0 0 0 STATIC CRLSP 0 0 0 0 LDP LSP 0 0 0 0 RSVP CRLSP 1 1 0 0 BGP LSP 0 0 0 0 ASBR LSP 0 0 0 0 BGP IPV6 LSP 0 0 0 0 L3VPN IPV6 LSP 0 0 0 0 ---------------------------------------------------------------------LSP 0 0 0 0 CRLSP 1 1 0 0 ---------------------------------------------------------------------Lsp Type IngressLspBypassState TransitLspBypassState ExistNotUsed InUse ExistNotUsed InUse RSVP CRLSP 0 0 0 0 ----------------------------------------------------------------------
Step 4 Run the ping lsp -c 30 te Tunnel 1/1/1 command on CX- A. Then open another window on CX- A and run the shutdown command to disable GE 1/0/0 during the ping operation. The display command output shows that the LSP goes Down and packets are discarded because FRR is not enabled. [CX-A] ping lsp -c 30 te Tunnel 1/1/1 LSP PING FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel1/1/1 : 100 CTRL_C to break Reply from 2.2.2.2: bytes=100 Sequence=1 time = 14 ms Reply from 2.2.2.2: bytes=100 Sequence=2 time = 5 ms Reply from 2.2.2.2: bytes=100 Sequence=3 time = 13 ms Reply from 2.2.2.2: bytes=100 Sequence=4 time = 12 ms Error: The specified tunnel or lsp is invalid. [CX-A] display ip interface brief *down: administratively down !down: FIB overload down (l): loopback
Issue 04 (2014-04-01)
data bytes, press
Tunnel 1/1/1
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
135
HUAWEI CX600 Metro Service Platform Commissioning Guide (s): spoofing Interface Tunnel1/1/1
6 Commissioning Services and Protocols
IP Address/Mask 1.1.1.1/32
Physical Protocol up down
----End
6.18 Commissioning CR-LSP Hot Standby This section describes how to commission CR-LSP Hot Standby.
Prerequisites l
The hardware has been checked. For more information, see 4 Checking the Hardware.
l
The link layer has been commissioned. For more information, see 5 Commissioning the Link Layer.
Context Figure 6-19 illustrates an MPLS VPN. A TE tunnel originates from the ingress PE1 and terminates at the egress PE2. CR-LSP hot backup and best-effort LSPs need to be configured. The following LSPs need to be established: l
Primary CR-LSP along the path PE1 --> P1 --> PE2
l
Backup CR-LSP along the path PE1 --> P2 --> PE2
If the primary CR-LSP fails, traffic switches to the backup CR-LSP. After the primary CR-LSP recovers from the fault, traffic switches back to the primary CR-LSP in 15 seconds. If both the primary and backup CR-LSPs fail, traffic switches to the best-effort LSP. If both the primary and backup CR-LSPs fail, traffic switches to the best-effort path. Explicit paths can be configured for the primary and backup CR-LSPs. A best-effort path can be generated automatically. In this example, the best-effort path is PE1 -> P2 -> P1 -> PE2. The calculated best-effort path varies according to the faulty node.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
136
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Figure 6-19 Networking diagram for CR-LSP hot backup
Loopback1 1.1.1.1/32 GE1/0/0 P1 10.1.1.1/30 GE3/0/0 GE2/0/0 10.2.1.1/30 10.4.1.2/30
Loopback1 2.2.2.2/32 GE1/0/0 P2 10.1.1.2/30 GE3/0/0 GE2/0/0 10.3.1.2/30 10.5.1.1/30
GE2/0/0 10.5.1.2 /30
GE2/0/0 10.4.1.1/30 GE1/0/0 10.3.1.1/30
PE1
Loopback1 4.4.4.4/32
GE1/0/0 10.2.1.2/30
PE2
Loopback1 3.3.3.3/32 : Primary path : Backup path : Best-effort path
Procedure Step 1 Assign an IP address to each interface. Assigne an IP address and mask to each interface, create loopback interfaces on LSRs, and configure the IP addresses of loopback interfaces as MPLS LSR IDs, according to Figure 6-19. Step 2 Configure an IGP. Configure OSPF or IS-IS on each LSR to enable communication between LSRs. In this example, IS-IS is configured. Step 3 Configure basic MPLS functions. On each LSR, configure an LSR ID and enable MPLS in the system view and in the interface view. Step 4 Configure basic MPLS TE functions. Enable MPLS-TE and MPLS RSVP-TE in the MPLS view and the interface view on each LSR. Set the maximum reservable bandwidth of links to 100 Mbit/s and the bandwidth of BC0 to 100 Mbit/s. Step 5 Configure IS-IS TE and CSPF. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
137
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Configure IS-IS TE on each LSR and CSPF on PE1. Step 6 Configure the explicit paths for the primary and backup CR-LSPs respectively. # Configure the explicit path for the primary CR-LSP on PE1. system-view [PE1] explicit-path main [PE1-explicit-path-main] [PE1-explicit-path-main] [PE1-explicit-path-main] [PE1-explicit-path-main]
next hop 10.4.1.2 next hop 10.2.1.2 next hop 3.3.3.3 quit
# Configure the explicit path for the backup CR-LSP on PE1. [PE1] explicit-path backup [PE1-explicit-path-backup] [PE1-explicit-path-backup] [PE1-explicit-path-backup] [PE1-explicit-path-backup]
next hop 10.3.1.2 next hop 10.5.1.2 next hop 3.3.3.3 quit
# Display information about the explicit path on PE1. [PE1] display explicit-path main Path Name : main Path Status : Enabled 1 10.4.1.2 Strict Include 2 10.2.1.2 Strict Include 3 3.3.3.3 Strict Include [PE1] display explicit-path backup Path Name : backup Path Status : Enabled 1 10.3.1.2 Strict Include 2 10.5.1.2 Strict Include 3 3.3.3.3 Strict Include
Step 7 Configure the tunnel interfaces. # Configure a tunnel interface on PE1; specify the explicit path; set the tunnel bandwidth to 10 Mbit/s. [PE1] interface tunnel 1/0/0 [PE1-Tunnel1/0/0] ip address unnumbered interface loopback 1 [PE1-Tunnel1/0/0] tunnel-protocol mpls te [PE1-Tunnel1/0/0] destination 3.3.3.3 [PE1-Tunnel1/0/0] mpls te tunnel-id 100 [PE1-Tunnel1/0/0] mpls te path explicit-path main [PE1-Tunnel1/0/0] mpls te bandwidth ct0 10000
# Configure hot standby on the tunnel interface, set the switch delay time to 15 seconds, specify the explicit path, and configure the best-effort LSP. [PE1-Tunnel1/0/0] [PE1-Tunnel1/0/0] [PE1-Tunnel1/0/0] [PE1-Tunnel1/0/0] [PE1-Tunnel1/0/0]
mpls mpls mpls mpls quit
te te te te
backup hot-standby wtr 15 path explicit-path backup secondary backup ordinary best-effort commit
Run the display mpls te tunnel-interface tunnel 1/0/0 command on PE1. The command output shows that the primary and backup CR-LSPs have been established. [PE1] display mpls te tunnel-interface tunnel 1/0/0 ---------------------------------------------------------------Tunnel1/0/0 ---------------------------------------------------------------Tunnel State Desc : UP Active LSP : Primary LSP Session ID : 100 Ingress LSR ID : 4.4.4.4 Egress LSR ID: 3.3.3.3
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
138
HUAWEI CX600 Metro Service Platform Commissioning Guide Admin State : Primary LSP State Main LSP State Hot-Standby LSP State Main LSP State
6 Commissioning Services and Protocols UP : UP : READY : UP : READY
Oper State
:
UP
LSP ID
: 1
LSP ID
: 32770
# Display information about hot backup. [PE1] display mpls te hot-standby state interface Tunnel 1/0/0 ---------------------------------------------------------------Verbose information about the Tunnel1/0/0 hot-standby state ---------------------------------------------------------------session id : 100 main LSP token : 0x100201a hot-standby LSP token : 0x100201b HSB switch result : Primary LSP WTR : 15s using same path : no
# Run the ping lsp te command to check the connection of the backup CR-LSP. [PE1] ping lsp te tunnel 1/0/0 hot-standby LSP PING FEC: TE TUNNEL IPV4 SESSION QUERY CTRL_C to break Reply from 3.3.3.3: bytes=100 Sequence=1 Reply from 3.3.3.3: bytes=100 Sequence=2 Reply from 3.3.3.3: bytes=100 Sequence=3 Reply from 3.3.3.3: bytes=100 Sequence=4 Reply from 3.3.3.3: bytes=100 Sequence=5
Tunnel1/0/0 : 100 time time time time time
= = = = =
data bytes, press
380 ms 130 ms 70 ms 120 ms 120 ms
--- FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel1/0/0 ping statistics --5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 70/164/380 ms
# Run the tracert lsp te command to trace the path of the backup CR-LSP. [PE1] tracert lsp te tunnel 1/0/0 hot-standby LSP Trace Route FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel1/0/0 , press CTRL_C to break. TTL Replier Time Type Downstream 0 Ingress 10.3.1.2/[13313 ] 1 10.3.1.2 90 ms Transit 10.5.1.2/[3 ] 2 3.3.3.3 130 ms Egress
Step 8 Verify the configuration. Connect port 1 and port 2 on a tester to PE1 and PE2, respectively. Inject MPLS traffic destined for Port 2 into Port 1. After the cable attached to GE 2/0/0 on PE1 or P1 is removed, the fault rectified within milliseconds. Run the display mpls te hot-standby state interface tunnel 1/0/0 command on PE1. The command output shows that traffic has switched to the backup CRLSP. [PE1] display mpls te hot-standby state interface tunnel 1/0/0 ---------------------------------------------------------------Verbose information about the Tunnel1/0/0 hot-standby state ---------------------------------------------------------------session id : 100 main LSP token : 0x0 hot-standby LSP token : 0x100201b HSB switch result : Hot-standby LSP WTR : 15s using same path : no
After the cable is reconnected to GE 2/0/0, traffic switches back to the primary CR-LSP after a 15–second delay. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
139
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
After you remove the cable from GE 2/0/0 on PE1 or P1 and the cable from GE 2/0/0 on PE2 or P2, the tunnel interface goes Down and then Up. This means that the best-effort path has been established, and traffic has switched to the best-effort path. [PE1] display mpls te tunnel-interface tunnel 1/0/0 ---------------------------------------------------------------Tunnel1/0/0 ---------------------------------------------------------------Tunnel State Desc : UP Active LSP : Best-Effort LSP Session ID : 100 Ingress LSR ID : 4.4.4.4 Egress LSR ID: 3.3.3.3 Admin State : UP Oper State : UP Primary LSP State : DOWN Main LSP State : SETTING UP Hot-Standby LSP State : DOWN Main LSP State : SETTING UP Best-Effort LSP State : UP Main LSP State : READY LSP ID : 32773 [PE1] display mpls te tunnel path Tunnel Interface Name : Tunnel1/0/0 Lsp ID : 4.4.4.4 :100 :32776 Hop Information Hop 0 10.3.1.1 Hop 1 10.3.1.2 Hop 2 2.2.2.2 Hop 3 10.1.1.2 Hop 4 10.1.1.1 Hop 5 1.1.1.1 Hop 6 10.2.1.1 Hop 7 10.2.1.2 Hop 8 3.3.3.3
----End
6.19 Commissioning VPN FRR In the networking of CE dual-homing, you can configure VPN FRR to ensure the end-to-end VPN service fast switchover if the PE fails, This section describes how to commission VPN FRR.
Prerequisites The following configurations are complete and the device is running normally: l
4 Checking the Hardware
l
5 Commissioning the Link Layer
Context On the network shown in Figure 6-20, VPN FRR is deployed on the network.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
140
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
Figure 6-20 Typical networking for commissioning VPN FRR Loopback1 2.2.2.2/32
VPN backbone Loopback1 POS1/0/0 1.1.1.1/32 AS100 100.1.1.2/30 POS2/0/0 100.1.1.1/30
PE2 GE2/0/0 10.1.1.2/30
vpn1 site
GE1/0/0 10.1.1.1/30
Link_A
AS65410
CE
PE1
Link_B
GE3/0/0 10.3.1.1/24
GE2/0/0 10.2.1.1/30
POS3/0/0 100.2.1.1/30 POS1/0/0 100.2.1.2/30
PE3
GE2/0/0 10.2.1.2/30
Loopback1 3.3.3.3/32
Procedure Step 1 Run the display bgp vpnv4 vpn-instance command on the PEs. You can view that the EBGP peer is established between the PEs and the CEs, and the peer status is "Established". [PE2] display bgp vpnv4 vpn-instance vpn1 peer BGP local router ID : 2.2.2.2 Local AS number : 100 VPN-Instance vpna, Router ID 2.2.2.2: Total number of peers : 1 Peer PrefRcv 10.1.1.1
Peers in established state : 1
V
AS
MsgRcvd
MsgSent
4
65401
3
5
OutQ
Up/Down
State
0 00:00:10 Established
1
Step 2 Run the display bgp vpnv4 all peer command on the PEs. You can view that the peer is established between the PEs, and the peer status is "Established". [PE1] display bgp vpnv4 all peer BGP local router ID : 1.1.1.1 Local AS number : 100 Total number of peers : 2 Peer V AS MsgRcvd 2.2.2.2 4 100 20 3.3.3.3 4 100 24
MsgSent 17 19
Peers in established state : 2 OutQ Up/Down State PrefRcv 0 00:13:26 Established 5 0 00:17:18 Established 5
Step 3 Run the display ip routing-table vpn-instance command to check the information about the backup next hop, the backup label and the backup Tunnel ID. display ip routing-table vpn-instance vpn1 10.3.1.0 verbose Route Flags: R - relay, D - download to fib -----------------------------------------------------------------------------Routing Table : vpn1 Summary Count : 1 Destination: 10.3.1.0/24 Protocol: IBGP Process ID: 0 Preference: 255 Cost: 0 NextHop: 2.2.2.2 Neighbour: 2.2.2.2
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
141
HUAWEI CX600 Metro Service Platform Commissioning Guide
6 Commissioning Services and Protocols
State: Active Adv Relied Age: 00h15m06s Tag: 0 Priority: low Label: 15361 QoSInfo: 0x0 IndirectID: 0x13 RelayNextHop: 0.0.0.0 Interface: Pos2/0/0 TunnelID: 0x6002002 Flags: RD BkNextHop: 3.3.3.3 BkInterface:Unknown BkLabel: 15362 SecTunnelID: 0x0 BkPETunnelID: 0x6002000 BkPESecTunnelID: 0x0 BkIndirectID: 0x15 NOTE
In this example, both PE2 and PE3 advertise the route 10.3.1.1/24 with the same BGP attribute to PE1. The router ID of PE2 is smaller than that of PE3 so that PE1 preferentially selects the route advertised by PE2, that is, Link_A. If the router ID of PE2 is greater than that of PE3 in a real-world situation, PE1 preferentially selects the route advertised by PE2, that is, Link_B. In this case, VPN FRR fails if the preceding configurations are followed. To prevent the problem from occurring, you can modify VPNv4 route attributes in the BGP-VPNv4 address family view, ensuring that PE1 preferentially selecting Link_A. There are many methods to modify VPNv4 route attributes. The following part shows the most common two methods: l In the BGP-VPNv4 address family view of PE1, set a higher PrefVal for the routes learnt from PE2. The relevant configuration is as follows: route-policy policy1 permit node 10 apply preferred-value 100 # bgp 100 # ipv4-family vpnv4 peer 2.2.2.2 route-policy policy1 import
l In the BGP-VPNv4 address family view of PE2, set a higher Local_Pref for the advertised routes. The relevant configuration is as follows: route-policy policy2 permit node 10 apply local-preference 200 # bgp 100 # ipv4-family vpnv4 peer 1.1.1.1 route-policy policy2 export
----End
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
142
HUAWEI CX600 Metro Service Platform Commissioning Guide
7 Commission Examples
7
Commission Examples
About This Chapter This chapter provides several typical commission examples. 7.1 Example for Commissioning an IP Bearer Network This section provides an example about how to commission an IP bearer network.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
143
HUAWEI CX600 Metro Service Platform Commissioning Guide
7 Commission Examples
7.1 Example for Commissioning an IP Bearer Network This section provides an example about how to commission an IP bearer network.
Prerequisites The CX600s are installed, cabled, and loaded with configuration scripts.
Networking Figure 7-1 shows an IP core bearer network that provides multiple services such as 3G, Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), and Internet services. This network consists of two layers, the core layer and the access layer. l
Core layer – This layer has two planes with each plane having five nodes that are fully meshed and located in five cities. The nodes on different planes are connected to each other through 10 Gbit/s Ethernet links, and backup paths are provided. – Intermediate System-to-Intermediate System (IS-IS) is used as an Interior Gateway Protocol (IGP) at the core layer, and Traffic Engineering (TE) tunnels are established between Ps on the same plane.
l
Access layer – Each NGW is dual-homed to two switches. Each switch is separately connected to a PE. The Virtual Router Redundancy Protocol (VRRP) runs between the PEs and switches, ensuring high availability of the link between the two switches. – EBGP peer relationships are established between the PEs and RRs at the core layer. – Remote LDP sessions are established between the PEs at different sites. – The PEs at the same site are connected to each other, switches, and core nodes by GE links. On each PE, the interface connected to a switch is called the user-side interface, and the interface connected to the backbone network is called the network-side interface. The user-side interface contains multiple sub-interfaces with each sub-interface being bound to a VPN instance and serving as the gateway for the corresponding CE. BFD runs on main interfaces.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
144
HUAWEI CX600 Metro Service Platform Commissioning Guide
7 Commission Examples
Figure 7-1 IP core network topology Site 14
Site 1
Site 13
RR
Site 2
Site 12
IGW P3 P1
Site 3
Site 11
Site 4
P5
P7
P2
P4
IGW
Site 5 P8
P6
Site 7
Site 6
Site 10
Site 8 RR Site 9
Whole topologies 10G GE
Site topologies Switch PE IP core network
NGW
Switch
PE
Procedure Step 1 1. Commission the hardware of each device. The detailed procedures are as follows: 1.
2.1 Logging In to the CX600 by Using the Console Interface
2.
4.1 Checking the Software Version
3.
4.2 Checking the Health Status of the CX600
4.
4.3 Checking the Board Registration Status
5.
4.4 Checking the Fan Status
6.
4.5 Checking the Power Status
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
145
HUAWEI CX600 Metro Service Platform Commissioning Guide
7.
4.6 Checking System Time
8.
4.7 Checking the Interface Status
9.
4.8 Checking Alarm Information
7 Commission Examples
10. 4.9 Checking the Voltage of Each Board 11. 4.10 Checking the Temperature of Each Board Step 2 Commission the link layer. The detailed procedures are as follows: NOTE
Commission the link layer after the hardware of each device is commissioned and the devices at the two ends of every link are normally started. The links between PEs and Ps need to be commissioned.
1.
5.1 Checking Ethernet Interfaces
Step 3 Commission services and protocols. The detailed procedures are as follows: NOTE
After ensuring that all links work properly, commission routing protocols and services such as VPN services.
1.
6.4 Commissioning IS-IS Routes Commission IS-IS between IS-IS-capable Ps and PEs. IS-IS is enabled on the following interfaces: l All interfaces on Ps, including Loopback 0 interfaces l All interfaces on RRs, including Loopback 0 interfaces l Network-side interfaces on PEs, which connect the PEs to the MPLS backbone network l Loopback 0 interfaces on PEs l Interfaces connecting PEs and Ps
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
146
HUAWEI CX600 Metro Service Platform Commissioning Guide
7 Commission Examples
Figure 7-2 IS-IS interfaces RR1 P3
P1
PE3
PE1
SW3
SW1 P5
P7
P2
SW2 PE2
P4
P6
P8
RR2
2.
SW4 PE4
ISIS interface
6.5 Commissioning IBGP Routes Figure 7-3 shows BGP connections at two sites as an example. At each of the two sites, two PEs are deployed to provide access services. In fact, there are 14 sites in the network, and each RR sets up MP-IBGP connections with 28 PEs.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
147
HUAWEI CX600 Metro Service Platform Commissioning Guide
7 Commission Examples
Figure 7-3 BGP connections RR1
RR2
P3 P1 PE3
PE1
P5
P7
PE2 P2
P4
PE4
P6 P8 MP-IBGP peer
3.
6.8 Commissioning MPLS TE Commission the following tunnels. l Tunnel paths Not more than four primary tunnels exist between each P and the other Ps. Figure 7-4 shows the primary tunnels between Ps on the same plane. All tunnel paths are defined based on the tunnel planning.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
148
HUAWEI CX600 Metro Service Platform Commissioning Guide
7 Commission Examples
Figure 7-4 Primary tunnels P3
P1
P7
P5
P2
P4
P8
P6
In the figure, P1, P2, P5, and P6 each serves as the ingress of three primary tunnels; P3, P4, P7, and P8 each serves as the ingress of two primary tunnels. In all, there are 20 primary tunnels. Based on the general tunnel design principle, all tunnels (including primary tunnels and backup tunnels) use strict explicit paths. Each primary tunnel has another tunnel as its backup. The primary and backup tunnels do not share the direct links between cities. Figure 7-5 shows the deployment of backup tunnels.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
149
HUAWEI CX600 Metro Service Platform Commissioning Guide
7 Commission Examples
Figure 7-5 Backup tunnels P3
P1
P7
P5
P2
P4
P8
P6
Primary tunnel Backup tunnel
Backup tunnels cannot use the direct links that have been used by the corresponding primary tunnels between cities. For example, the primary tunnel P1->P5 cannot have P1->P2->P6->P5 as its backup tunnel. Its backup tunnel can be P1->P2->P8->P6->P5 or P1->P2->P4->P6->P5. Table 7-1 lists the backup tunnel paths on the upper plane. Table 7-1 Backup tunnel paths on the upper plane
Issue 04 (2014-04-01)
Primary Tunnel Path
Backup Tunnel Path
P1-P3
P1-P2-P6-P4-P3
P1-P5
P1-P2-P8-P6-P5
P1-P7
P1-P2-P6-P8-P7
P7-P1
P7-P8-P6-P2-P1
P7-P5
P7-P8-P2-P6-P5
P5-P7
P5-P6-P2-P8-P7
P5-P1
P5-P6-P8-P2-P1
P5-P3
P5-P6-P2-P4-P3
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
150
HUAWEI CX600 Metro Service Platform Commissioning Guide
7 Commission Examples
Primary Tunnel Path
Backup Tunnel Path
P3-P5
P3-P4-P2-P6-P5
P3-P1
P3-P4-P6-P2-P1
Table 7-2 lists the backup tunnel paths on the lower plane. Table 7-2 Backup tunnel paths on the lower plane Primary Tunnel Path
Backup Tunnel Path
P2-P4
P2-P1-P5-P3-P4
P2-P6
P2-P1-P3-P5-P6
P2-P8
P2-P1-P5-P7-P8
P8-P2
P8-P7-P5-P1-P2
P8-P6
P8-P7-P1-P5-P6
P6-P8
P6-P5-P1-P7-P8
P6-P2
P6-P5-P3-P1-P2
P6-P4
P6-P5-P1-P3-P4
P4-P6
P4-P3-P1-P5-P6
P4-P2
P4-P3-P5-P1-P2
There is no direct link between P7 and P3. The path for the primary tunnel from P7 to P3 is shown in Figure 7-6. Hot backup and best-effort paths are configured to protect each link along the path. The design on the primary tunnel between P8 and P4 is similar to that on the primary tunnel between P7 and P3, and is not provided here.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
151
HUAWEI CX600 Metro Service Platform Commissioning Guide
7 Commission Examples
Figure 7-6 Primary tunnel path from P7 to P3 P3
P1
P5
P7
P2
P4
P8
4.
P6
6.9 Commissioning BGP/MPLS IP VPN Commission VPN instances on all PEs and user-side interfaces on PEs. Table 7-3 describes VPN parameters. Table 7-3 VPN parameters Parameter
Value
VPN name
l NGN_Media l NGN_Signal l NGN_Other
Issue 04 (2014-04-01)
VPN label allocation mode
Each VPN instance is assigned a label, and all the routes of a VPN instance use the same label.
VPN tunnel
LDP LSP
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
152
HUAWEI CX600 Metro Service Platform Commissioning Guide
7 Commission Examples
Parameter
Value
RD
The value is in the format of AAAAA:BBBBCCCDE. l AAAAA: indicates the BGP AS number (65000). l BBBB: indicates the VPN type. If the VPN is an enterprise VPN, the first two Bs identify the enterprise and the last two Bs identify the department. l CCC: indicates the site. l D: indicates the number of a PE on a plane at a site l E: indicates the site. The value 1 indicates plane A; the value 2 indicates plane B. See Table 4.
RT
Table 7-4 describes RDs and RTs. Table 7-4 RDs and RTs VPN
Import RT
Export RT
Media stream
65000:0100
65000:0100
65000:0200 65000:0300 Signaling stream
65000:0100
65000:0200
65000:0200 65000:0300 Others
65000:0100
65000:0300
65000:0200 65000:0300 5.
6.12 Commissioning BFD BFD configurations consist of the following items: l BFD for TE hot-standby l BFD for VPN FRR l BFD for VRRP Commission BFD for TE hot-standby on all Ps. Establish BFD sessions between PEs at different sites on the same plane and commission BFD for VPN FRR.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
153
HUAWEI CX600 Metro Service Platform Commissioning Guide
7 Commission Examples
Commission BFD for VRRP on all PEs. ----End
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
154
HUAWEI CX600 Metro Service Platform Commissioning Guide
A
A List of Interface Attributes
List of Interface Attributes
This chapter presents the list of Interface Attributes. NOTE
To use the optical module on the local end, the following two conditions for the input optical power of the optical module must be met: l
The input optical power must be greater than the receiver sensitivity of the optical module (3dBm). Otherwise, the peer end will not receive any signals.
l
The input optical power must be lower than the overload optical power (3dBm). Otherwise, the optical module may be damaged.
A.1 Interface Attributes of 10Base-T/100Base-TX/1000Base-T-RJ45 This section describes the interface attributes of 10Base-T/100Base-TX/1000Base-T-RJ45. A.2 Interface Attributes of 100Base-FX This section describes the interface attributes of 100Base-FX. A.3 Interface Attributes of 100/1000Base-CSFP This section describes the interface attributes of the interface attributes of 100/1000Base-CSFP, the attributes of 100M CSFP optical modules, and the attributes of 1000M CSFP optical modules. A.4 Interface Attributes of 1000Base-X-SFP This section describes the interface attributes of 1000Base-X-SFP and the attributes of 1000M SFP optical modules. A.5 Interface Attributes of 10GBase LAN/WAN-XFP This section describes the interface attributes of 10GBase LAN/WAN-XFP and the attributes of 10G XFP optical modules. A.6 Interface Attributes of 10GBase LAN-SFP+ This section describes the interface attributes of 10GBase LAN-SFP+ and the attributes of 10GBase SFP+ optical modules. A.7 Interface Attributes of 40GBase-CFP This section describes the interface attributes of 40GBase-CFP and the attributes of 40GBaseCFP optical modules. A.8 Interface Attributes of 100GBase-CFP This section describes the interface attributes of 100GBase-CFP and the attributes of 100GBaseCFP optical modules. A.9 Interface Attributes of OC-3c/STM-1c cPOS-SFP Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
155
HUAWEI CX600 Metro Service Platform Commissioning Guide
A List of Interface Attributes
This section describes the interface attributes of OC-3c/STM-1c cPOS-SFP and the attributes of 155M SFP optical modules. A.10 Interface Attributes of OC-3c/STM-1c POS-SFP This section describes the interface attributes of OC-3c/STM-1c POS-SFP and the attributes of 155M SFP optical modules. A.11 Interface Attributes of OC-12c/STM-4c POS-SFP This section describes the interface attributes of OC-12c/STM-4c POS-SFP and the attributes of 622M SFP optical modules. A.12 Interface Attributes of OC-48c/STM-16c POS-SFP This section describes the interface attributes of OC-48c/STM-16c POS-SFP and the attributes of 2.5G SFP optical modules. A.13 Interface Attributes of OC-192c/STM-64c POS-XFP This section describes the interface attributes of OC-192c/STM-64c POS-XFP. A.14 Interface Attributes of OC-768c/STM-256c POS-LC A.15 Interface Attributes of OC-3c/STM-1c ATM-SFP This section describes the interface attributes of the OC-3c/STM-1c ATM-SFP. A.16 Interface Attributes of OC-12c/STM-4c ATM-SFP This section describes the interface attributes of the OC-12c/STM-4c ATM-SFP. A.17 Interface Attributes of CE1/CT1 This section describes the interface attributes of the CE1/CT1. A.18 Interface Attributes of E3/T3 This section describes the interface attributes of the E3/T3.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
156
HUAWEI CX600 Metro Service Platform Commissioning Guide
A List of Interface Attributes
A.1 Interface Attributes of 10Base-T/100Base-TX/1000BaseT-RJ45 This section describes the interface attributes of 10Base-T/100Base-TX/1000Base-T-RJ45. Table A-1 lists the interface attributes of 10Base-T/100Base-TX/1000Base-T-RJ45. Table A-1 The Interface attributes of the 10Base-T/100Base-TX/1000Base-T-RJ45 Attributes
Description
Connector type
RJ45
Working mode
10M/100M/1000M auto-sensing and half-duplex and full-duplex
Cable specification
Super category 5 Shielded Twisted Pair (STP) cable is recommended.
Frame format
Ethernet_II, Ethernet_SAP, and Ethernet_SNAP
Network protocol
IP
A.2 Interface Attributes of 100Base-FX This section describes the interface attributes of 100Base-FX. Table A-2 lists the interface attributes of 100Base-FX. Table A-2 The Attributes of 100M SFP optical modules
Issue 04 (2014-04-01)
Attributes
Description
Transmission distance
2 km (1.24 mi.)
15 km (9.32 mi.)
40 km (24.86 mi.)
80 km (49.71 mi.)
Center wavelength
1310 nm
1310 nm
1310 nm
1550 nm
Minimum transmitting power
-19.0 dBm
-15.0 dBm
-5.0 dBm
-5.0 dBm
Maximum transmitting power
-14.0 dBm
-8.0 dBm
0 dBm
0 dBm
Receiving sensitivity
-30.0 dBm
-31.0 dBm
-37.0 dBm
-37.0 dBm
Overload power
-14.0 dBm
-8.0 dBm
-10.0 dBm
-10.0 dBm
Optical fiber type
Multi-mode
Single-mode
Single-mode
Single-mode
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
157
HUAWEI CX600 Metro Service Platform Commissioning Guide
A List of Interface Attributes
A.3 Interface Attributes of 100/1000Base-CSFP This section describes the interface attributes of the interface attributes of 100/1000Base-CSFP, the attributes of 100M CSFP optical modules, and the attributes of 1000M CSFP optical modules. Table A-3 lists the interface attributes of the 100/1000Base-CSFP. Table A-3 Interface attributes of the 100/1000Base-CSFP Attributes
Description
Connector type
LC/PC
Interface attributes
Compliant with the selected CSFP optical module.
Working mode
Full-duplex
Frame format
Ethernet_II, Ethernet_SAP, and Ethernet_SNAP
Network protocol
IP
Table A-4 lists the attributes of the 100M CSFP optical modules. Table A-4 Attributes of the 100M CSFP optical modules Attributes
Description
Transmission distance
10 km (6.21 mi.)
Transmitting center wavelength
1550 nm
Receiving center wavelength
1310 nm
Minimum transmitting power
-14.0 dBm
Maximum transmitting power
-8.0 dBm
Receiving sensitivity
-28.2 dBm
Overload power
-8.0 dBm
Optical fiber type
Single-mode
Table A-5 lists the attributes of the 1000M CSFP optical modules. Table A-5 Attributes of the 1000M CSFP optical modules
Issue 04 (2014-04-01)
Attributes
Description
Transmission distance
10 km (6.21 mi.)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
158
HUAWEI CX600 Metro Service Platform Commissioning Guide
A List of Interface Attributes
Attributes
Description
Transmitting center wavelength
1490 nm
Receiving center wavelength
1310 nm
Minimum transmitting power
-9.0 dBm
Maximum transmitting power
-3.0 dBm
Receiving sensitivity
-19.5 dBm
Overload power
-3.0 dBm
Optical fiber type
Single-mode
A.4 Interface Attributes of 1000Base-X-SFP This section describes the interface attributes of 1000Base-X-SFP and the attributes of 1000M SFP optical modules. Table A-6 lists the interface attributes of 1000Base-X-SFP. Table A-6 The Interface attributes of the 1000Base-X-SFP Attributes
Description
Connector type
LC/PC
Interface attributes
Compliant with the selected SFP optical module (for the attributes of SFP modules, see Table A-7)
Working mode
Full-duplex
Frame format
Ethernet_II, Ethernet_SAP, and Ethernet_SNAP
Network protocol
IP
Table A-7 lists the attributes of 1000M SFP optical modules. Table A-7 The Attributes of 1000M SFP optical modules
Issue 04 (2014-04-01)
Attributes
Description
Transmission distance
0.5 km (0.31 mi.)
10 km (6.21 mi.)
40 km (24.86 mi.)
40 km (24.86 mi.)
80 km (49.71 mi.)
100 km (62.14 mi.)
Center wavelength
850 nm
1310 nm
1310 nm
1550 nm
1550 nm
1550 nm
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
159
HUAWEI CX600 Metro Service Platform Commissioning Guide
A List of Interface Attributes
Attributes
Description
Minimum transmitting power
-9.5 dBm
-9.5 dBm
-4.5 dBm
-4.0 dBm
-2.0 dBm
0 dBm
Maximum transmitting power
-2.5 dBm
-3.0 dBm
3.0 dBm
1.0 dBm
5.0 dBm
5.0 dBm
Receiving sensitivity
-17.0 dBm
-20.0 dBm
-22.5 dBm
-21.0 dBm
-23.0 dBm
-30.0 dBm
Overload power
0 dBm
-3.0 dBm
-3.0 dBm
-3.0 dBm
-3.0 dBm
-9.0 dBm
Optical fiber type
Multimode
Singlemode
Singlemode
Singlemode
Singlemode
Singlemode
A.5 Interface Attributes of 10GBase LAN/WAN-XFP This section describes the interface attributes of 10GBase LAN/WAN-XFP and the attributes of 10G XFP optical modules. Table A-8 lists the interface attributes of the 10GBase LAN/WAN-XFP. Table A-8 Interface attributes of the 10GBase LAN/WAN-XFP Attributes
Description
Connector type
LC/PC
Interface attributes
Compliant with the selected XFP optical module (for the attributes of XFP modules, see Table A-9)
Working mode
Full-duplex
Frame format
Ethernet_II, Ethernet_SAP, and Ethernet_SNAP
Network protocol
IP
Table A-9 lists the attributes of the 10G XFP optical modules. Table A-9 Attributes of 10G XFP optical modules
Issue 04 (2014-04-01)
Attributes
Description
Transmission distance
0.3 km (0.19 mi.)
10 km (6.21 mi.)
40 km (24.86 mi.)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
80 km (49.71 mi.)
160
HUAWEI CX600 Metro Service Platform Commissioning Guide
A List of Interface Attributes
Attributes
Description
Center wavelength
850 nm
1310 nm
1550 nm
1550 nm
Minimum transmitting power
-7.3 dBm
-6.0 dBm
-1.0 dBm
0 dBm
Maximum transmitting power
-1.3 dBm
-1.0 dBm
2.0 dBm
4.0 dBm
Receiving sensitivity
-7.5 dBm
-11.0 dBm
-15.0 dBm
-24.0 dBm
Overload power
-1.0 dBm
0.5 dBm
-1.0 dBm
-7.0 dBm
Optical fiber type
Multi-mode
Single-mode
Single-mode
Single-mode
A.6 Interface Attributes of 10GBase LAN-SFP+ This section describes the interface attributes of 10GBase LAN-SFP+ and the attributes of 10GBase SFP+ optical modules. Table A-10 lists the interface attributes of the 10GBase LAN-SFP+. Table A-10 Interface attributes of the 10GBase LAN-SFP+ Attributes
Description
Connector type
LC/PC
Interface attributes
Compliant with the selected SFP+ optical module (for the attributes of SFP+ modules, see Table A-11)
Working mode
Full-duplex
Frame format
Ethernet_II, Ethernet_SAP, and Ethernet_SNAP
Network protocol
IP
Table A-11 lists the attributes of the 10GBase SFP+ optical modules.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
161
HUAWEI CX600 Metro Service Platform Commissioning Guide
A List of Interface Attributes
Table A-11 Attributes of 10GBase SFP+ optical modules Attributes
Description
Transmission distance
0.3 km (0.19 mi.)
10 km (6.21 mi.)
40 km (24.86 mi.)
80 km(49.71 mi.)
Center wavelength
850 nm
1310 nm
1550 nm
1550 nm
Minimum transmitting power
-7.3 dBm
-8.2 dBm
-4.7 dBm
0 dBm
Maximum transmitting power
-1 dBm
0.5 dBm
4.0 dBm
4.0 dBm
Receiving sensitivity
-11.1 dBm
-12.6 dBm
-14.1 dBm
-24 dBm
Overload power
-1.0 dBm
0.5 dBm
0.5 dBm
-7 dBm
Optical fiber type
Multi-mode
Single-mode
Single-mode
Single-mode
A.7 Interface Attributes of 40GBase-CFP This section describes the interface attributes of 40GBase-CFP and the attributes of 40GBaseCFP optical modules. Table A-12 lists the interface attributes of 40GBase-CFP. Table A-12 Interface attributes of the 40GBase-CFP Attributes
Description
Connector type
SC
Interface attributes
Compliant with the selected CFP optical module (for the attributes of CFP modules, see Table A-13)
Working mode
Full-duplex
Frame format
Ethernet_II, Ethernet_SAP, and Ethernet_SNAP
Network protocol
IP
Table A-13 lists the attributes of 40GBase-CFP optical modules.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
162
HUAWEI CX600 Metro Service Platform Commissioning Guide
A List of Interface Attributes
Table A-13 Attributes of 40GBase-CFP optical modules Attributes
Description
Transmission distance
10 km (6.21 mi.)
Center wavelength
1310 nm
Minimum transmitting power
-4 dBm
Maximum transmitting power
3.5 dBm
Receiving sensitivity
-13.7 dBm
Overload power
3.5 dBm
Optical fiber type
Single-mode
A.8 Interface Attributes of 100GBase-CFP This section describes the interface attributes of 100GBase-CFP and the attributes of 100GBaseCFP optical modules. Table A-14 lists the interface attributes of 100GBase-CFP. Table A-14 Interface attributes of the 100GBase-CFP Attributes
Description
Connector type
SC/LC
Interface attributes
Compliant with the selected CFP optical module (for the attributes of SFP modules, see Table A-15)
Working mode
Full-duplex
Frame format
Ethernet_II, Ethernet_SAP, and Ethernet_SNAP
Network protocol
IP
lists the attributes of 100GBase-CFP optical modules. Table A-15 lists the attributes of the 100GBase-CFP optical modules. Table A-15 Attributes of 100GBase-CFP optical modules
Issue 04 (2014-04-01)
Attributes
Description
Transmission distance
10 km (6.21 mi.)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
10 km (6.21 mi.) 163
HUAWEI CX600 Metro Service Platform Commissioning Guide
A List of Interface Attributes
Attributes
Description
Center wavelength
1310 nm
1550 nm
Minimum transmitting power
-4.3 dBm
-2.8 dBm
Maximum transmitting power
4.5 dBm
3.5 dBm
Receiving sensitivity
-8.6 dBm
-8.8 dBm
Overload power
4.5 dBm
3.5 dBm
Optical fiber type
Single-mode
Single-mode
A.9 Interface Attributes of OC-3c/STM-1c cPOS-SFP This section describes the interface attributes of OC-3c/STM-1c cPOS-SFP and the attributes of 155M SFP optical modules. Table A-16 lists the interface attributes of OC-3c/STM-1 cPOS-SFP. Table A-16 Interface attributes of the OC-3c/STM-1 cPOS-SFP Attributes
Description
Connector type
LC/PC
Interface attributes
Compliant with the selected SFP optical module (for the attributes of SFP modules, see Table A-17)
Working mode
Full-duplex
Link protocol
PPP, MP, HDLC, and cRTP
Network protocol
IP
Table A-17 lists the attributes of the 155M SFP optical modules. Table A-17 Attributes of the 155M SFP optical modules
Issue 04 (2014-04-01)
Attributes
Description
Transmission distance
2 km (1.24 mi.)
15 km (9.32 mi.)
40 km (24.86 mi.)
80 km (49.71 mi.)
Center wavelength
1310 nm
1310 nm
1310 nm
1550 nm
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
164
HUAWEI CX600 Metro Service Platform Commissioning Guide
A List of Interface Attributes
Attributes
Description
Minimum transmitting power
-19.0 dBm
-15.0 dBm
-5.0 dBm
-5.0 dBm
Maximum transmitting power
-14.0 dBm
-8.0 dBm
0 dBm
0 dBm
Receiving sensitivity
-30.0 dBm
-31.0 dBm
-37.0 dBm
-37.0 dBm
Overload power
-14.0 dBm
-8.0 dBm
-10.0 dBm
-10.0 dBm
Optical fiber type
Multi-mode
Single-mode
Single-mode
Single-mode
A.10 Interface Attributes of OC-3c/STM-1c POS-SFP This section describes the interface attributes of OC-3c/STM-1c POS-SFP and the attributes of 155M SFP optical modules. Table A-18 lists the interface attributes of the OC-3c/STM-1c POS-SFP. Table A-18 Interface attributes of the OC-3c/STM-1c POS-SFP Attributes
Description
Connector type
LC/PC
Interface attributes
Compliant with the selected SFP optical module (for the attributes of SFP modules, see Table A-19)
Working mode
Full-duplex
Link protocol
PPP and HDLC
Network protocol
IP
Table A-19 lists the attributes of the 155M SFP optical modules. Table A-19 Attributes of 155M SFP optical modules
Issue 04 (2014-04-01)
Attributes
Description
Transmission distance
2 km (1.24 mi.)
15 km (9.32 mi.)
40 km (24.86 mi.)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
80 km (49.71 mi.)
165
HUAWEI CX600 Metro Service Platform Commissioning Guide
A List of Interface Attributes
Attributes
Description
Center wavelength
1310 nm
1310 nm
1310 nm
1550 nm
Minimum transmitting power
-19.0 dBm
-15.0 dBm
-5.0 dBm
-5.0 dBm
Maximum transmitting power
-14.0 dBm
-8.0 dBm
0 dBm
0 dBm
Receiving sensitivity
-30.0 dBm
-31.0 dBm
-37.0 dBm
-37.0 dBm
Overload power
-14.0 dBm
-8.0 dBm
-10.0 dBm
-10.0 dBm
Optical fiber type
Multi-mode
Single-mode
Single-mode
Single-mode
A.11 Interface Attributes of OC-12c/STM-4c POS-SFP This section describes the interface attributes of OC-12c/STM-4c POS-SFP and the attributes of 622M SFP optical modules. Table A-20 lists the interface attributes of OC-12c/STM-4c POS-SFP. Table A-20 Interface attributes of the OC-12c/STM-4c POS-SFP Attributes
Description
Connector type
LC/PC
Interface attributes
Compliant with the selected SFP optical module (for the attributes of SFP modules, see Table A-21)
Working mode
Full-duplex
Link protocol
PPP and HDLC
Network protocol
IP
Table A-21 lists the attributes of the 622M SFP optical modules.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
166
HUAWEI CX600 Metro Service Platform Commissioning Guide
A List of Interface Attributes
Table A-21 Attributes of the 622M SFP optical modules Attributes
Description
Transmission distance
15 km (9.32 mi.)
40 km (24.86 mi.)
80 km (49.71 mi.)
Center wavelength
1310 nm
1310 nm
1550 nm
Minimum transmitting power
-15.0 dBm
-3.0 dBm
-3.0 dBm
Maximum transmitting power
-8 dBm
2.0 dBm
2.0 dBm
Receiving sensitivity
-31.0 dBm
-30.0 dBm
-30.0 dBm
Overload power
-8.0 dBm
-8.0 dBm
-8.0 dBm
Optical fiber type
Single-mode
Single-mode
Single-mode
A.12 Interface Attributes of OC-48c/STM-16c POS-SFP This section describes the interface attributes of OC-48c/STM-16c POS-SFP and the attributes of 2.5G SFP optical modules. Table A-22 lists the interface attributes of OC-48c/STM-16c POS-SFP. Table A-22 Interface attributes of the OC-48c/STM-16c POS-SFP Attributes
Description
Connector type
LC/PC
Interface attributes
Compliant with the selected SFP optical module (for the attributes of SFP modules, see Table A-23)
Working mode
Full-duplex
Link protocol
PPP and HDLC
Network protocol
IP
Table A-23 lists the attributes of the 2.5G SFP optical modules.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
167
HUAWEI CX600 Metro Service Platform Commissioning Guide
A List of Interface Attributes
Table A-23 Attributes of the 2.5G SFP optical modules Attributes
Description
Transmission distance
2 km (1.24 mi.)
15 km (9.32 mi.)
40 km (24.86 mi.)
80 km (49.71 mi.)
Center wavelength
1310 nm
1310 nm
1310 nm
1550 nm
Minimum transmitting power
-10.0 dBm
-5.0 dBm
-2.0 dBm
-2.0 dBm
Maximum transmitting power
-3.0 dBm
0 dBm
3.0 dBm
3.0 dBm
Receiving sensitivity
-21.0 dBm
-21.0 dBm
-30.0 dBm
-30.0 dBm
Overload power
-3.0 dBm
0 dBm
-9.0 dBm
-9.0 dBm
Optical fiber type
Multi-mode
Single-mode
Single-mode
Single-mode
A.13 Interface Attributes of OC-192c/STM-64c POS-XFP This section describes the interface attributes of OC-192c/STM-64c POS-XFP. Table A-24 lists the interface attributes of the OC-192c/STM-64c POS-XFP. Table A-24 Interface attributes of the OC-192c/STM-64c POS-XFP Attributes
Description
Connector type
LC/PC
Interface attributes
Compliant with the selected XFP optical module (for the attributes of XFP modules, see Table A-25)
Working mode
Full-duplex
Link protocol
PPP and HDLC
Network protocol
IP
Table A-25 lists the interface attributes of the 10G XFP optical modules.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
168
HUAWEI CX600 Metro Service Platform Commissioning Guide
A List of Interface Attributes
Table A-25 Attributes of the 10G XFP optical modules Attributes
Description
Transmission distance
10 km (6.21 mi.)
40 km (24.86 mi.)
80 km (49.71 mi.)
Center wavelength
1310 nm
1550 nm
1550 nm
Minimum -6.0 dBm transmitting power
-1.0 dBm
0 dBm
Maximum -1.0 dBm transmitting power
2.0 dBm
4.0 dBm
Receiving sensitivity
-11.0 dBm
-15.0 dBm
-24.0 dBm
Overload power
0.5 dBm
-1.0 dBm
-7.0 dBm
Optical fiber type
Single-mode
Single-mode
Single-mode
The 10G XFP multi-mode optical transceiver supports two types of multi-mode optical fibers with different cores. Table A-26 lists the relationship between the core, the modal/bandwidth, and the transmission distance. During configuration, the length of optical fibers is restricted by the transmission distance. In addition, the optical fiber with the 50 um core and 2000 MHz*km modal/bandwidth is a special type, which is not delivered by Huawei. If this type of optical fiber is required, you need to purchase it additionally. Table A-26 Transmission distance of the 10G XFP optical modules Core Fiber (μm)
Modal/Bandwidth (Mhz*km)
Transmission Distance (km)
50
2000
2 ~300 (1.24 ~ 186.42)
50
500
2 ~82 (1.24 ~50.95)
62.5
200
2 ~33 (1.24 ~ 20.51)
A.14 Interface Attributes of OC-768c/STM-256c POS-LC Table A-27 lists the interface attributes of the OC-768c/STM-256c POS-LC. Table A-27 Interface attributes of the OC-768c/STM-256c POS-LC
Issue 04 (2014-04-01)
Attributes
Description
Connector type
LC
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
169
HUAWEI CX600 Metro Service Platform Commissioning Guide
A List of Interface Attributes
Attributes
Description
Compliant standard
STM-256c/OC-768c SONET
Link protocol
PPP and HDLC
Table A-28 lists the attributes of the 40G optical modules. Table A-28 Attributes of the 40G optical modules Attributes
Description
Transmission distance
2 km (1.24 mi.)
Center wavelength
1550 nm
Minimum transmitting power
0 dBm
Maximum transmitting power
3 dBm
Receiving sensitivity
-6 dBm
Overload power
3 dBm
Optical fiber type
Single-mode
A.15 Interface Attributes of OC-3c/STM-1c ATM-SFP This section describes the interface attributes of the OC-3c/STM-1c ATM-SFP. Table A-29 lists the interface attributes of the OC-3c/STM-1c ATM-SFP. Table A-29 Interface attributes of the OC-3c/STM-1c ATM-SFP Attributes
Description
Connector type
LC/PC
Interface attributes
Compliant with the selected SFP optical module (for the attributes of SFP modules, see Table A-30)
Working mode
Full-duplex
Link protocol
IPoA
Network protocol
IP
Table A-30 lists the attributes of the 155M SFP optical modules. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
170
HUAWEI CX600 Metro Service Platform Commissioning Guide
A List of Interface Attributes
Table A-30 Attributes of the 155M SFP optical modules Attributes
Description
Transmission distance
2 km (1.24 mi.)
15 km (9.32 mi.)
40 km (24.86 mi.)
80 km (49.71 mi.)
Center wavelength
1310 nm
1310 nm
1310 nm
1550 nm
Minimum transmitting power
-19.0 dBm
-15.0 dBm
-5.0 dBm
-5.0 dBm
Maximum transmitting power
-14.0 dBm
-8.0 dBm
0 dBm
0 dBm
Receiving sensitivity
-30.0 dBm
-31.0 dBm
-37.0 dBm
-37.0 dBm
Overload power
-14.0 dBm
-8.0 dBm
-10.0 dBm
-10.0 dBm
Optical fiber type
Multi-mode
Single-mode
Single-mode
Single-mode
A.16 Interface Attributes of OC-12c/STM-4c ATM-SFP This section describes the interface attributes of the OC-12c/STM-4c ATM-SFP. Table A-31 lists the interface attributes of the OC-12c/STM-4c ATM-SFP. Table A-31 Interface attributes of the 2-port OC-12c/STM-4c ATM-SFP FPIC Attributes
Description
Connector type
LC/PC
Optical interface attributes
Compliant with the selected SFP optical module (for the attributes of SFP modules, see Table A-32)
Working mode
Full-duplex
Link protocol
IPoA
Network protocol
IP
Table A-32 lists the attributes of the 622M SFP optical modules.
Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
171
HUAWEI CX600 Metro Service Platform Commissioning Guide
A List of Interface Attributes
Table A-32 Attributes of the 622M SFP optical modules Attributes
Description
Transmission distance
15 km (9.32 mi.)
40 km (24.86 mi.)
80 km (49.71 mi.)
Center wavelength
1310 nm
1310 nm
1550 nm
Minimum transmitting power
-15.0 dBm
-3.0 dBm
-3.0 dBm
Maximum transmitting power
-8 dBm
2.0 dBm
2.0 dBm
Receiving sensitivity
-31.0 dBm
-30.0 dBm
-30.0 dBm
Overload power
-8.0 dBm
-8.0 dBm
-8.0 dBm
Optical fiber type
Single-mode
Single-mode
Single-mode
A.17 Interface Attributes of CE1/CT1 This section describes the interface attributes of the CE1/CT1. Table A-33 lists the interface attributes of the CE1/CT1. Table A-33 Interface attributes of the CE1/CT1 Attributes
Description
Type
CE1
CT1
Rate
2.048 Mbit/s
1.544 Mbit/s
Working mode
Full-duplex
Full-duplex
Maximum transmission distance
270 m (885.82 ft)
270 m (885.82 ft)
Link protocol
PPP, HDLC, MLPPP, cRTP, FR
A.18 Interface Attributes of E3/T3 This section describes the interface attributes of the E3/T3. Issue 04 (2014-04-01)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
172
HUAWEI CX600 Metro Service Platform Commissioning Guide
A List of Interface Attributes
Table A-34 lists the interface attributes of the E3/T3. Table A-34 Interface attributes of the E3/T3
Issue 04 (2014-04-01)
Attributes
Description
Connector type
SMB
SMB
Type
E3
T3
Rate
34.368 Mbit/s
44.736 Mbit/s
Working mode
Full-duplex
Full-duplex
Maximum transmission distance
100 m (328.08 ft)
100 m (328.08 ft)
Link protocol
PPP and HDLC
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
173
