huawei optix ptn 950 commissioning guide(v100r005)

OptiX PTN 950 Packet Transport Platform of PTNSeriesV100R005C01

Commissioning Guide

Issue 02

Date 2013-08-10

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent 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. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 02 (2013-08-10) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

i

http://www.huawei.commailto:[email protected]

About This Document

Related VersionsThe following table lists the product versions related to this document.

Product Name Version

OptiX PTN 950 V100R005C01

Huawei iManager U2000 V100R009C00

Intended AudienceThis document describes the commissioning process of the OptiX PTN 950 in terms ofpreparations for commissioning and system commissioning.

This document describes the commissioning flow and method.

This document is intended for:

l Installation and commissioning engineers

Symbol ConventionsThe symbols that may be found in this document are defined as follows.

Symbol Description

DANGERDANGER indicates a hazard with a high level or mediumlevel of risk which, if not avoided, could result in death orserious injury.

WARNINGWARNING indicates a hazard with a low level of risk which,if not avoided, could result in minor or moderate injury.

CAUTIONCAUTION indicates a potentially hazardous situation that,if not avoided, could result in equipment damage, data loss,performance deterioration, or unanticipated results.

OptiX PTN 950 Packet Transport Platform of PTN SeriesCommissioning Guide About This Document


ii

Symbol Description

TIP TIP indicates a tip that may help you solve a problem or savetime.

NOTE NOTE provides additional information to emphasize orsupplement important points of the main text.

GUI ConventionsThe GUI conventions that may be found in this document are defined as follows.

Convention Description

Boldface Buttons, menus, parameters, tabs, window, and dialog titlesare in boldface. For example, click OK.

> Multi-level menus are in boldface and separated by the ">"signs. For example, choose File > Create > Folder.

Change HistoryUpdates between document issues are cumulative. Therefore, the latest document issue containsall updates made in previous issues.

Changes in Issue 02 (2013-08-10) Based on Product Version V100R005C01Compared with issue 01 of the V100R005C01 version, this issue has the following updates:

Update Description

Whole manual Known bugs are fixed.


Update Description





iii

Update Description


Changes in Issue 01 (2012-10-30) Based on Product Version V100R005C00This document of the V100R005C00 version is the first release.



iv

Contents

About This Document.....................................................................................................................ii

1 Equipment Commissioning Flow..............................................................................................1

2 Preparations for the Commissioning.........................................................................................32.1 Checking Commissioning Conditions............................................................................................................................42.2 References and Instruments Required for the Commissioning......................................................................................4

3 Network Commissioning.............................................................................................................63.1 Checking the Connection between the Equipment and the NMS Computer..................................................................83.2 Starting the U2000..........................................................................................................................................................83.3 Creating the Network Topology.....................................................................................................................................93.3.1 Creating NEs................................................................................................................................................................93.3.2 Uploading NE Data...................................................................................................................................................153.3.3 Setting NE Name, NE IP Address, NE ID and LSR ID............................................................................................173.3.4 Creating Links...........................................................................................................................................................193.4 Setting the VLAN ID and Bandwidth Used by Inband DCN.......................................................................................233.5 Synchronizing NE Time...............................................................................................................................................253.6 Enabling the NE Performance Monitoring Function....................................................................................................263.7 Checking the Optical Power of Optical Interface.........................................................................................................273.8 Configuring Services....................................................................................................................................................293.9 Testing Service Connectivity........................................................................................................................................293.9.1 Testing Connectivity of an E-Line Service...............................................................................................................303.9.2 Testing Connectivity of an E-LAN Service..............................................................................................................313.9.3 Testing Connectivity of a UNIs-NNI ATM Service.................................................................................................353.9.4 Testing Connectivity of a CES Service.....................................................................................................................383.9.5 Testing Connectivity of a CES Service (VC3/VC4).................................................................................................413.9.6 Testing Connectivity of an IP over PW Service........................................................................................................433.9.7 Testing Connectivity of a UNI-NNI L3VPN Service...............................................................................................463.10 Testing the Network Protection Switching.................................................................................................................483.10.1 Testing MPLS Tunnel APS Protection....................................................................................................................483.10.2 Testing LMSP Protection........................................................................................................................................503.10.3 Test on Ring Protection Switching..........................................................................................................................51

A Glossary........................................................................................................................................53

OptiX PTN 950 Packet Transport Platform of PTN SeriesCommissioning Guide Contents


v

1 Equipment Commissioning FlowThis section describes the flow of commissioning the equipment. The commissioning flowcovers preparation and network commissioning.

Figure 1-1 shows the equipment commissioning flow.

OptiX PTN 950 Packet Transport Platform of PTN SeriesCommissioning Guide 1 Equipment Commissioning Flow


1

Figure 1-1 Equipment commissioning flow

Preparation

Required

Optional

Required

Create the network topology

Test the protection switching

Check the connection between the

equipment and NMS computer

Check the optical power of optical

interface

Synchronize NE time

Enable the NE performance

monitoring function

Commissioning items

Start the U2000

Configure the services

NetworkCommissioning

Setup commissioning enivronment

Test service connectivity

Set VLAN ID and Bandwidth Used by

Inband DCN

Prepare tools and references

Checking commissioning

conditions

OptiX PTN 950 Packet Transport Platform of PTN SeriesCommissioning Guide 1 Equipment Commissioning Flow


2

2 Preparations for the CommissioningAbout This Chapter

Before starting the commissioning, make sure that the equipment is ready for commissioningand prepare the required documents and tools.

2.1 Checking Commissioning ConditionsThis section describes the conditions required for the commissioning.

2.2 References and Instruments Required for the CommissioningThis section describes the references and tools prepared for the commissioning in advance. Thereferences include reference manuals and engineering design documents, and the tools includeinstruments and materials required for the commissioning.

OptiX PTN 950 Packet Transport Platform of PTN SeriesCommissioning Guide 2 Preparations for the Commissioning


3

2.1 Checking Commissioning ConditionsThis section describes the conditions required for the commissioning.

Network Commissioning Conditionsl The U2000 must be installed in the NMS center and the installation must be checked.

Refer to the OptiX iManager U2000 Installation Guide.l The equipment must be installed and the installation must be checked.

Refer to the OptiX PTN 950 Packet Transport Platform of PTN Series Quick InstallationGuide.

l The board configuration of the equipment should be consistent with the board configurationdiagram.

l Fibers and cables must be connected to interfaces on the equipment and routed to thedistribution frame. The fiber and cable connections must be consistent with the fiber andcable connection table.

l NEs must be correctly connected according to the fiber and cable connection table, and thenetworking diagram.

l The required instruments, tools and materials must be ready.

2.2 References and Instruments Required for theCommissioning

This section describes the references and tools prepared for the commissioning in advance. Thereferences include reference manuals and engineering design documents, and the tools includeinstruments and materials required for the commissioning.

Reference manualsPrepare the following references for equipment commissioning:

l OptiX PTN 950 Packet Transport Platform of PTN Series Configuration Guidel OptiX PTN 950 Packet Transport Platform of PTN Series Feature Descriptionl OptiX PTN 950 Packet Transport Platform of PTN Series Maintenance Guidel OptiX PTN 950 Packet Transport Platform of PTN Series Product Descriptionl OptiX PTN 950 Packet Transport Platform of PTN Series Hardware Descriptionl OptiX iManager U2000 Installation Guide

Engineering design documentsThe engineering design document should contain engineering information required forequipment commissioning. Engineering information required for equipment commissioningincludes the following:l Networking diagraml NE name, NE ID and NE IP address allocation table



4

l NE board configuration diagraml NE software version (The software is installed correctly before delivery)l Fiber and cable connection tablel Resource allocation table

ToolsTable 2-1 lists the tools required for the commissioning.

Table 2-1 Tool list

Type Description

Common tool Adjustable wrench

Special tool Anti-static glove, Anti-static wrist strap,telescope, walkie-talkie , hex key wrench-set

Meter Multimeter (with a BNC connecter preparedat one end for future tests), laptop computer,SDH analyzer or BER tester, Ethernet servicetester, Network cable tester

Materials Fiber flange, Fiber jumper, Straight through/crossover cable, 2M jumper

NOTE

Number of optical attenuators required for each station:

l Five to ten optical attenuators of each specification of 5 dB, 7 dB, or 10 dB

l Two to five optical attenuators of each specification of 2 dB or 15 dB



5

3 Network CommissioningAbout This Chapter

This chapter describes the network commissioning items and the commissioning methods.

1. 3.1 Checking the Connection between the Equipment and the NMS ComputerThe NMS runs on the NMS computer to manage the NEs. If the NMS computer isincorrectly connected to the equipment, the NMS cannot manage the NEs. Check theconnection between the equipment and the NMS computer to ensure that the connection iscorrect. This section describes how to check the connection between the equipment and theNMS computer.

2. 3.2 Starting the U2000During network commissioning, use the U2000 to configure the equipment in the network.

3. 3.3 Creating the Network TopologyAccording to the connections among NEs in the network, create a network topology on theU2000. After the topology is configured, you can use the U2000 to configure services oneach NE and perform each commissioning task.

4. 3.4 Setting the VLAN ID and Bandwidth Used by Inband DCNThe network management (NM) center manages the OptiX PTN equipment through theinband DCN scheme. That is, the service information and NM information (DCN packet)are transmitted in the same physical link. When the Ethernet port is used to carry the DCNpackets, the NE distinguishes the DCN packets from the service packets by an NM-dedicated VLAN ID. Therefore, you need to set the bandwidth used by inband DCN andthe VLAN ID for the inband DCN packets according to the actual planning duringengineering commissioning.

5. 3.5 Synchronizing NE TimeAdjust the NE time to make it synchronous with the U2000 time so that the U2000 canaccurately record the time when an alarm, a performance event, or an abnormal eventoccurs.

6. 3.6 Enabling the NE Performance Monitoring FunctionEnabling the performance monitoring function for an NE helps perform the followingcommissioning operations and monitor new performance events in the commissioningprocess. If the performance monitoring function is enabled, you can obtain detailedperformance records during the operation process of this NE so that you can easily monitorand analyze the running status of the NE. This task is optional.

OptiX PTN 950 Packet Transport Platform of PTN SeriesCommissioning Guide 3 Network Commissioning


6

7. 3.7 Checking the Optical Power of Optical InterfaceIf the transmitted or received optical power at an optical interface is excessively low orhigh, bit errors may be generated on the equipment, and the optical component may evenbe damaged. This section describes how to check the transmitted and received optical powerat optical interfaces to ensure that the transmitted and received optical powers at all theoptical interfaces are within the normal range.

8. 3.8 Configuring ServicesWhen the U2000 complete to maintain and manage the network for commissioning, youcan use the U2000 to configure all kinds of services that the equipment supports. Thissection describes how to configure services for conducting the tests of these services.

9. 3.9 Testing Service ConnectivityAfter services are configured on the U2000, test the connectivity of the services to ensurethat the services are created correctly. This section describes how to test the connectivityof various basic network services.

10. 3.10 Testing the Network Protection SwitchingAfter the network protection is configured on the U2000, the network protection switchingshould be tested to ensure the effectiveness of the network protection. This section describeshow to test the network protection schemes supported by the PTN equipment.



7

3.1 Checking the Connection between the Equipment andthe NMS Computer

The NMS runs on the NMS computer to manage the NEs. If the NMS computer is incorrectlyconnected to the equipment, the NMS cannot manage the NEs. Check the connection betweenthe equipment and the NMS computer to ensure that the connection is correct. This sectiondescribes how to check the connection between the equipment and the NMS computer.

Prerequisitesl The NMS computer must be connected to the equipment through a network cable or LAN.l The equipment and the NMS computer must be powered on.l The NMS computer must start up normally.

Tools, Instruments and MaterialsNone

Procedurel The NMS computer is connected to the equipment through a network cable.

1. Check the connection of the network cable.

One end of the network cable should be connected to the network interface card ofthe NMS computer and the other end should be connected to the network managementinterface of the gateway NE.

2. Observe the indicator for the network interface card of the NMS computer and theindicator for the network management interface of the gateway NE.

The LINK indicator should stay on and green. If there are packets to be sent orreceived, the orange ACT indicator should flash.

l The NMS computer is connected to the equipment through LAN.1. Check the connection of the network cable.

On the NMS side, one end of the network cable should be connected to the networkinterface card of the NMS computer and the other end should be connected to theLAN switch.

On the equipment side, one end of the network cable should be connected to thenetwork management interface of the gateway NE and the other end to the LANswitch.

2. Observe the indicators beside the interfaces with connection.

The LINK indicator should stay on and green. If there are packets to be sent orreceived, the orange ACT indicator should flash.

----End

3.2 Starting the U2000During network commissioning, use the U2000 to configure the equipment in the network.



8

For details on how to start the U2000, see Huawei iManager U2000 Operator Guide .

3.3 Creating the Network TopologyAccording to the connections among NEs in the network, create a network topology on theU2000. After the topology is configured, you can use the U2000 to configure services on eachNE and perform each commissioning task.

3.3.1 Creating NEsEach equipment is represented as an NE on the U2000. Before the U2000 manages the actualequipment, you need to create the corresponding NEs on the U2000. There are two methods ofcreating NEs: creating a single NE and creating NEs in batches. When you need to create a largenumber of NEs, for example, during deployment, it is recommended that you create NEs inbatches. When you need to create only a few NEs, it is recommended that you create the NEsone by one.

Automatically Discovering NEsDuring network construction or expansion, many NEs may be created. The U2000 canautomatically discover connected NEs and create these NEs on itself in batches, which facilitatesnetwork planning.

PrerequisitesThe U2000 server must have been configured for gateways.

DCN must have been enabled on ports.

ContextIf PTN NEs need to be deployed in a large quantity or for network expansion, usually, fieldmaintenance engineers have to ensure that the NEs have been connected to the network beforeinstructing engineers at the network management center to manually acknowledge the NEs andcreate them on the U2000. Moreover, resources are wasted and efficiency is low if many NEsneed to connect to the network and the process takes a long time. If the automatic NE connectionfunction is configured, engineers at the network management center do not need to manuallyacknowledge NEs. Instead, the U2000 automatically identifies the NEs, creates them on itself,and uploads configuration data. NE creation in this manner is faster and more reliable.



9

Figure 3-1 Inband DCN networking

Network management on the DCN plane

Gateway NMS

Third-party network

IP tunnel

Management interface

Figure 3-1 shows the networking scheme for automatic NE connection. The PTN equipmentare configured for network deployment or expansion and are connected by fibers/cables or IPtunnels. DCN is enabled on ports on the two sides of each link after the PTN NEs are connectedto the network, or DCN is enabled on IP tunnels after these tunnels are configured, to transmitNE information over the inband DCN and third-party network. The U2000 manages the PTNNEs on the DCN plane by using gateways that report information about new non-gateway NEsto the U2000.

Procedure

Step 1 Operation and maintenance engineers can set a U2000 server IP address and Enable theautomatic NE reporting function for gateways.1. In the NE Explorer, select an NE and choose Communication > NMS Server from the

Function Tree.2. Set NE Automatic Reporting to Enabled and set a U2000 server IP address for gateways.

Click Apply.

Step 2 Choose File > Discovery > NE Auto Discovery from the shortcut menu.

Step 3 In the Auto Discovery Configuration area, select the Discovery Automatically check box.

Step 4 Optional: Click Filter. In the dialog box that is displayed, set filter criteria for automatic NEdiscovery. Click OK.

Step 5 Optional: In the Auto Discovery Configuration area, select the Create Automatically checkbox. Set NE User, NE password, and Connection Mode.

Step 6 Optional: In the Auto Discovery Configuration area, select the Upload Automatically checkbox.

Step 7 Click Apply.NOTE

In the NE Found area, information about automatically discovered NEs is displayed. If the CreateAutomatically and Upload Automatically check boxes are selected, the U2000 automatically creates anduploads in batches the NEs that are discovered but not created.

----End



10

Follow-up ProcedureIf the Create Automatically check box is not selected, you can manually create an NE that isdiscovered but not created as follows:

1. In the NE Found area, select an NE that is not created, and then click Create NE.2. In the dialog box that is displayed, enter information about the NE and click OK.

Creating NEs in BatchesIf the U2000 communicates with the gateway NE normally, you can search out all the NEs thatnormally communicate with the gateway NE and create these NEs in batches on the U2000.Creating NEs in batches is quicker than creating NEs manually. This section describes how tocreate NEs in batch.

Prerequisitesl The U2000 server and U2000 client must start up normally.l You must be a U2000 user with "Maintenance Group" authority or higher.l The U2000 must normally communicate with the gateway NE and the gateway NE must

normally communicate with the other NEs in the network.

Tools, Instruments and MaterialsU2000

Procedure

Step 1 Choose File > Search > Auto Discovery ... from the Main Menu. The Auto Discovery windowis displayed.

Step 2 Click the Transport NE Search tab.

Step 3 Select the search mode from the drop-down list of Search Mode.l Set the Search Mode to Search for NE:

1. Enter the network segment or IP addresses of NEs to search for the NEs.

a. Click Add and the Input Search Domain dialog box is displayed.b. Set the address type to IP Address Range of GNE, IP Address of GNE, or

NSAP Address. Enter the Search Address, User Name, and Password. ClickOK.



11

NOTE

l The device supports to search and create NEs by using the LSR ID as the IP address.

l The default NE user is root. The default password is password.

l If you search by IP address:

l Only the NEs (not across routers) in the same network segment can be searchedout normally if you select the IP Address Range of GNE because broadcastingis usually disabled for the routers in the network (to prevent network storm).

l Search out the NEs in the network segment by using the IP Address of GNE ifyou need to search for the NEs across routers.

l Only NSAP Address can be selected If you search for NEs by using the NSAPaddress.

l Repeat the above steps to add more search domains. You can also delete the system-default search domain.

2. In the Search for NE area, perform the following operations: Select Create NE after search, click Common Connection Mode or Security

SSL Connection Mode, and then enter the NE User and Password.

NOTE

Security SSL is recommended because of its higher security than Common

The default NE user is root. The default password is password.

Select Upload after being created. The NE data is uploaded to the U2000 afterthe NEs are created.

NOTE

You can select all options in the Search for NE area to search for NEs, create NEs, and uploadthe NE data at a time.

l Set the Search Mode to IP auto discovery:

NOTE

If you fail to enter a network segment correctly, enable IP auto discovery. After enabling IP autodiscovery, you can obtain the IP address of the GNE and search out all the NEs related to the GNE.

CAUTIONIn the case of NEs that are connected to the U2000 through the router, these NEs cannotbe searched out by IP auto discovery. They can be searched out only by network segment.

Step 4 Click Next and the Result area is displayed.TIP

You can select the Display uncreated NEs to only display the uncreated NEs.

Step 5 Optional: If you select Search for NE only, you can select the NEs, which are not yet created,in the Results list after the search for NEs is complete. Click Create and then the Create dialogbox is displayed. Enter User Name and Password in the Create dialog box, and then clickOK.



12

Step 6 Optional: Click Change NE ID. Then, the Change NE ID dialog box is displayed. Users cancheck against the Bar Code List by the value of Bar Code, and then modify the NE Name,Extend NE ID, Base NE ID, and IP Address fields accordingly.

CAUTIONChange NE ID will make NEs unreachable from the U2000.

NOTE

The Bar Code List is provided by the hardware installation personnel to the software commissioningpersonnel. The list contains the bar codes of stations.

Step 7 Optional: Select the NEs from the Results list and click Set Gateway NE. The Set GatewayNE dialog box is displayed. Enter the message, and click OK.

Step 8 In this case, the NE is in the un-configured state. Choose Configuration > NE ConfigurationData Management from the Main Menu to display the NE Configuration DataManagement interface.

Step 9 Select the NE for verification and click . Right-click the selected NE in the configurationdata management list and choose Verify from the shortcut menu. Then, click OK to display theOperation Result dialog box, indicating that the operation is successful. Click Close.

----End

ResultWhen the verification is complete, the NE is still in the un-configured state. In this case, the NEscreated in batches are grayed out.

Make sure that the number of NEs to be created by searching is consistent with the planning. Ifcertain NEs cannot be searched out, it indicates that the DCN channels between the NEs and thegateway NE are unavailable, or the NEs are faulty. In this case, troubleshoot the fault withreference to "Configuring an Inband DCN" of the OptiX PTN 950 Packet Transport Platformof PTN Series Feature Description and "Inband DCN Troubleshooting" of the OptiX PTN 950Packet Transport Platform of PTN Series Maintenance Guide.

Follow-up ProcedureAfter an NE is created, if you fail to log in to the NE, possible causes are listed as follows:

l The password for the NE user is incorrect. Enter the correct password for the NE user.l The NE user is invalid or the NE user is already logged in. Change to use a valid NE user.

Creating a Single NEThe U2000 can manage an NE after the NE is created. Although creating a single NE is not asfast and accurate as creating NEs in batches, you can perform this operation regardless of whetherthe data is configured on the NE or not.



13

Prerequisites

You must be an NM user with "Operator Group" authority or higher.

The license must be installed and the license must support creating the NE of the type.

Background Information

First create a GNE, and then create a non-gateway NE.

If the NE is not created properly or the communication between the NE and the U2000 isabnormal, the NE is displayed in gray color.

Procedure

Step 1 Right-click in the blank space of the Main Topology and choose New > Device from the shortcutmenu. The Create NE dialog box is displayed.

Step 2 Select the NE type from the Object Type tree.

Step 3 Complete the following information: ID, Extended ID, Name and Remarks.

Step 4 To create a GNE, proceed to Step 5. To create a non-gateway NE, proceed to Step 6.

Step 5 Choose Gateway Type, Protocol and set the IP address.1. Select Gateway from the Gateway Type drop-down list.2. Select the Protocol type.

If the U2000communicates withNEs through

Do...

IP protocol Select IP from the Protocol drop-down list. Enter the IPAddress and use the default value for the Port number ofthe GNE.

Step 6 Select Non-Gateway from the Gateway Type drop-down list. Select the GNE to which the NEis associated to from the Affiliated Gateway drop-down list.

Step 7 Enter the NE User and Password.



14

NOTEThe default NE user is root, and the default password is password.

Step 8 Click OK. Then, click in the blank space of the Main Topology and the NE icon appears in theposition where you clicked.

----End

ResultAfter an NE is successfully created, the system automatically saves the information, such as theIP address, subnet mask to the U2000 database.

Follow-up ProcedureAfter an NE is created, if you fail to log in to the NE, possible causes are listed as follows:

l The communication between the U2000 and the NE is abnormal. Check the settings ofcommunication parameters, such as the IP address of the NE.

l The password for the NE user is incorrect. Enter the correct password for the NE user.l The NE user is invalid or the NE user is already logged in. Change to use a valid NE user.

3.3.2 Uploading NE DataUploading NE data is a common method of configuring NE data. When uploading NE data, youcan upload the current configuration data of the NE to the U2000, such as NE configuration data,and alarm and performance data.

Prerequisitesl The NEs in the network must be created successfully.l You must be an NM user with "Operator Group" authority or higher.


Procedurel Upload:

1. Double-click the unconfigured NE on the Main Topology.The NE Configuration Wizard dialog box is displayed.

2. Choose Upload and click Next.



15

The Confirm dialog box is displayed indicating that the upload may take a long time.

3. Click OK to start the upload.Wait for a whiles. The Operation Result dialog box is displayed.

4. Click Close.

----End

Result

When uploading the NE data is complete, indications of the colors of the NE icon are as follows:

l If the NE icon is green, it indicates that the NE is normal without an alarm.

l If the NE icon is red, it indicates critical alarms on the NE. In this case, check and handlethe alarms.

1. On the Main Topology, double-click the NE icon and click in the toolbar.

2. Choose Display Latest Alarms.

3. Check for alarms of the equipment category, such as theBD_STATUS,BUS_ERR,FAN_FAIL,HARD_BAD,HARD_ERR,OUT_PWR_ABN,TEMP_OVER.

For details on the alarms and on how to handle the alarms, see the OptiX PTN 950Packet Transport Platform of PTN Series Maintenance Guide.

l If the NE icon turns to other colors, it indicates major, minor, or warning alarms on the NE.In this case, check and handle the alarms by performing the preceding steps.



16

NOTE

An interface without any cable connection reports alarms. For example, an optical interface reports the R_LOSalarm. Reporting these alarms in this case is normal and does not affect monitoring of other alarms. You can setalarm reversion so that these alarms, when generated, are not reported. For details on how to set alarm reversion,see the Online Help of the Huawei iManager U2000.

3.3.3 Setting NE Name, NE IP Address, NE ID and LSR IDIf you commission the NE by downloading data from the CF card, skip this step. When the NMcenter manages an NE, it marks the NE by the NE name and addresses the NE by using the NEIP address and the NE ID. Before delivery, the default NE Name, NE IP and NE ID are set. Afterlogging in to the NE, you need to set the NE Name, NE IP and NE ID according to the actualplanning. In a PSN network, each NE is allocated with a unique LSR ID. You need to set theLSR ID according to the actual planning.

Prerequisitesl You must be an NM user with "Maintenance Group" authority or higher.l The PCB electronic label of each NE at each site must be provided to the software

commissioning engineer by the installation personnel.


ProcedureStep 1 Confirm the NE name, NE IP address, and NE ID to be set for the NE.

1. Choose Inventory > Project Document > Board Manufacturer Information from theMain Menu to display the Board Manufacturer Information interface.

2. Select the system control board of the NE for confirmation and click to displaythe slot information of the system control board. Then, click Query in the right corner todisplay the Queryprogress dialog box. When the query is complete, the OperationResult dialog box, indicating that the operation is successful. Click Close.

3. Check and record the electronic label of the PCB of the system control board. Then,compare the recorded electronic label with the PCB electronic label table provided by thehardware engineer to determine the NE name, NE IP address, and NE ID to be set for theNE.

Step 2 Set the NE IP address.1. On the Main Topology, select and right-click the desired NE. In the shortcut menu, choose

NE Explorer to display the NE Explorer window.2. Choose Communication > Communication Parameters from the Function Tree on the

left. The Set NE Parameter is displayed on the right.3. Modify the IP address and subnet mask according to the engineering planning, and then

click Apply.



17

NOTE

The IP address of the NE should be unique in the entire network.

Modifying NE ID or NE IP address does not result in an NE being reset or unreachable by the NMS.

4. In the Warning dialog box that is displayed, click OK. In the Warning dialog boxdisplayed, click OK.

Step 3 Set the NE name and NE ID.1. On the Main Topology, select and right-click the desired NE. In the shortcut menu, choose

NE Explorer to display the NE Explorer window.2. Choose Configuration > NE Attribute in the Function Tree.3. According to the actual engineering planning, modify Name of the NE, and then click

Apply. The Operation Result dialog box is displayed, indicating that the operation issuccessful. Click Close.

4. Click Modify NE ID to display the Modify NE ID dialog box.5. According to the actual planning, enter values for the New ID and New Extended ID fields

and then click OK. In the Warning dialog box that is displayed, click OK.

NOTE

The ID ranges from 1 to 49135 and the extended ID ranges from 1 to 254.

The NE ID consists of the ID and extended ID. An NE ID should be unique in the entire network.

Step 4 Change the LSR ID.1. On the Main Topology, select and right-click the desired NE. In the shortcut menu, choose

NE Explorer to display the NE Explorer window.2. Choose Communication > MPLS Management > Basic Configuration from the

Function Tree on the left.3. Modify the LSR ID according to the engineering planning, and then click Apply.

CAUTIONLSR ID of an NE with services cannot be changed.The LSR ID cannot be the same as the IP address of the NE, nor can they be configuredwithin the same network segment.



18

4. In the Hint dialog box that is displayed, click OK. In the Operation Result dialog boxdisplayed, click Close.

----End

Result

When setting the NE name, NE IP address, NE ID, and LSR ID is complete, you can query andverify the settings on the NMS.

Query the NE name, NE IP address, and NE ID to check whether they are set correctly.

1. On the Main Topology, right-click the NE and choose Attributes to display the ObjectAttributes interface.

2. Check the NE name, NE IP address, and NE ID on the NE Attributes tab to see whetherthey are consistent with the planning.

Query the LSR ID to check whether it is set correctly.

1. On the Main Topology, right-click the NE and choose NE Explorer to display the NEExplorer interface.

2. Choose Configuration > MPLS Management > General Configuration from theFunction Tree on the left.

3. Check whether the LSR ID is consistent with the project planning.

3.3.4 Creating LinksYou can create fibers/cables, Ethernet lines, serial port lines by using the U2000.

Creating Links Automatically

Using the link search function, you can know whether any links are connected at a specifiedinterface. This helps you quickly create links in batches at the interface. For a newly creatednetwork, you can search for all the interfaces network-wide to create links after you completethe board configuration on the U2000. In this way, you can monitor the actual working state ofeach link.

Prerequisitesl You are an NMS user with "Operator Group" authority or higher.

l Link search has been enabled. and the boards to be connected with fibers or cables mustbe added.

Procedure

Step 1 Choose File > Discovery > Link from the Main Menu.

Step 2 On the left-hand Object Tree, select one or more NEs, and click .

Step 3 In the dialog box that prompts the success, click Close. In the window, the search results foreach links are displayed.



19

Step 4 Optional: You can select Links not exist in the NMS, Links exist in the NMS, or Conflictinglinks to view the status of links. You can select a conflicting link and click Delete ErrorLinks to delete the link.

NOTE

l Links not exist in the NMS: The link exists only in NEs and is not created in the NMS.l Links exist in the NMS: The link exists in the NMS and in the NEs.l Conflicting links: The link has certain different data on NEs and the NMS.

Step 5 Select one or more links whose Status is Not exist and click Create.

Step 6 In the dialog box that prompts the success, click Close.The Are you sure to import links as fibers/cables dialog box is displayed.

Step 7l Click OK in the Confirm dialog box.

1. The Import Link dialog box is displayed.2. In the Import Link dialog box, select one or more links and do as follows:

Click . The selected link is moved to the Selected Link area.

Click . All links in the Available Link area are moved to the Selected Linkarea. This operation is applicable to batch import.

Click . The selected link is moved to the Available Link area.

Click . All links in the Selected Link area are moved to the Available Linkarea.NOTE

For PTN series NEs, when import the link, you can set whether to allot IP address automaticon the ports of the link.

3. Click OK. The dialog box for the operation result is displayed. Click Close.

NOTE

l After you successfully create a link in the U2000, the status of the link is displayed as Exist.l The created links are displayed in the Link Management area. Navigation path: Choose

Inventory > Link Management from the Main Menu.l The imported fibers/cables are displayed in the Fiber/Cable/Microwave Link Management

area. Navigation path: Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave Link Management from the Main Menu.

l Click Cancel in the Confirm dialog box.NOTE

l After you successfully create a link in the U2000, the status of the link is displayed as Exist.l The created links are displayed in the Link Management area. Navigation path: Choose

Inventory > Link Management from the Main Menu.

Step 8 Optional: Select conflicted links and click Error Links to delete the records.

----End

Follow-up ProcedureIf you want to import links as fibers/cables after clicking the Cancel in the Import Linkdisplayed dialog box, you can perform the follow steps:



20

1. Choose Inventory > Fiber/Cable > Fiber/Cable Management from the Main Menu.2. In the Fiber/Cable/Microwave Link Management area, right-click, and choose Import

Link from the shortcut menu.3. In the Import Link dialog box, select one or more links and do as follows:

l Click . The selected link is moved to the Selected Link area.

l Click . All links in the Available Link area are moved to the Selected Link area.This operation is applicable to batch import.

l Click . The selected link is moved to the Available Link area.

l Click . All links in the Selected Link area are moved to the Available Link area.NOTE

For PTN/ATN series NEs, when import the link, you can set whether to allot IP address automaticon the ports of the link.

4. Click OK. The dialog box for the operation result is displayed. Click Close. The importedfibers/cables are displayed in the Fiber/Cable/Microwave Link Management area.

Creating Fibers for PTN Equipment ManuallyNEs communicate with each other through fibers. After creating boards for each NE, you needto create fibers for further configuration of services. In this situation, you can manually createfibers one by one.

Prerequisitesl You are an NMS user with "Maintenance Group" authority or higher.l The boards to be connected with fibers or cables must be added.l Before setting the parameter Automatically Allocate IP Address to No, make sure that

the port is not used by services or logical ports.

Procedure

Step 1 Method 1:1. Choose File > Create > Link from the Main Menu.2. In the dialog box that is displayed, choose Fiber/Cable > Fiber from the Object Type tree.3. Set Create Ways to Common Ways in the right pane.4. In the Name text box, enter the name of the fiber.5. Select the source NE from the Source NE drop-down list.

NOTE

You can also click next to Source NE. Then the cursor is display as + and you canclick the source NE of the fiber in the Main Topology. In the dialog box displayed, select the sourceboard and source port and click OK. The Create Link dialog box is displayed.You can also select a port from the Source NE Shelf-Slot-Board Type-Port drop-down list.

TIP

When selecting an incorrect source or sink NE, right-click and click OK in the CoordinateSelection dialog box to exit.

6. Select the fiber medium type from the Medium Type drop-down list.



21

7. Select the sink NE of the fiber from the Sink NE drop-down list.

NOTE

You can also click next to Sink NE. Then the cursor is display as +, and you can clickthe sink NE of the fiber in the Main Topology. In the dialog box displayed, select the sink board andsink port. Click OK. The Create Link dialog box is displayed.

You can also select a port from the Sink NE Shelf-Slot-Board Type-Port drop-down list.

8. In the Create Link dialog box, set the attributes of the fiber, such as Direction, Length,Attenuation, Creator, Maintainer, and Automatically Allocate IP Address.

NOTE

If both ends of the fiber/cable are the PTN equipment, when the Automatically Allocate IPAddress is set to Yes and the Port IP Address Management is configured, the system automaticallyallocates IP addresses to the ports on the two ends of a fiber after the fiber is created. For details,refer to Allocating IP Addresses to Ports Automatically.

The virtual NE do not support automatically allocate IP address.

9. Click OK.The created fiber is displayed between the source and sink NEs in the Main Topology.

Step 2 Method 2:

1. Click the shortcut icon in the Main Topology tab. The cursor is displayed as "+".

2. Click the source NE of the fiber in the Main Topology.

3. In the dialog box displayed, select the source board and source port.

4. Click OK. The Main Topology is displayed and the cursor is displayed as "+" again.

5. Click the sink NE of the fiber in the Main Topology.



22

6. In the dialog box displayed, select the sink board and sink port.

7. Click OK and set the attributes of the fiber in the Create Fiber/Cable dialog box.

8. Click OK.The new fiber is displayed between the source and sink NEs in the Main Topology.

----End

3.4 Setting the VLAN ID and Bandwidth Used by InbandDCN

The network management (NM) center manages the OptiX PTN equipment through the inbandDCN scheme. That is, the service information and NM information (DCN packet) are transmittedin the same physical link. When the Ethernet port is used to carry the DCN packets, the NEdistinguishes the DCN packets from the service packets by an NM-dedicated VLAN ID.Therefore, you need to set the bandwidth used by inband DCN and the VLAN ID for the inbandDCN packets according to the actual planning during engineering commissioning.

Prerequisitesl Configuring NE data must be performed.

l You must be an NM user with "Operator Group" authority or higher.

Contextl When the Ethernet port is used to carry the DCN packet, the NE distinguishes the DCN

packet from the service packet by an NM-dedicated VLAN ID. When the E1 port is used,the NE distinguishes the DCN packet from the service packet by a special MPLS label. TheMPLS label of the DCN packet cannot be modified.

l The bandwidth used by inband DCN is set to limit the bandwidth used to carry the in-bandDCN information on the physical port.

l If the set bandwidth is not fully occupied by the DCN packet, the remaining bandwidth canbe used by the service packets.

Tools, Instruments, and Materials

U2000

Procedure

Step 1 On the Main Topology, select and right-click the desired NE. In the shortcut menu, choose NEExplorer to display the NE Explorer window.

Step 2 Choose Communication > DCN Management from the Function Tree in the NE Explorerwindow.

Step 3 Click the Bandwidth Management tab, and set the VLAN ID for the inband DCN packets andthe bandwidth used by inband DCN according to the actual planning.



23

For description of bandwidth management parameters of the inband DCN, see Table 3-1.

Table 3-1 Description of bandwidth management parameters of the inband DCN

Parameter Value Description

Ethernet Board VLAN ID 2-4094Default:4094

Sets the VALN ID used by the DCN packet.When Ethernet ports are used to carry DCNpackets, you can set this parameter.Generally, the default VLAN ID isrecommended. When the VLAN ID of theservice packets conflicts with the VLAN IDof the DCN packets, you can customize theVLAN ID for the DCN packets. Note thatVLAN IDs of the DCN packets in the entirenetwork must be consistent.

Bandwidth (kbps) 64-2048Default:1024

Sets the bandwidth used by the DCN. WhenEthernet ports are used to carry DCN packetsamong NEs, you can set this parameter.The default value is recommended.

Tunnel Bandwidth (kbps) 64-2048Default:1024

Set the bandwidth used by the DCN. Set thisparameter when the Tunnel is used to carryservices between NEs.The default value is recommended.

E1 Port Bandwidth (kbps) 64-2048Default: 192

Sets the bandwidth used by the DCN. WhenE1 ports are used to carry DCN packetsamong NEs, you can set this parameter.The default value is recommended.

Step 4 Click Apply.

----End

Result

When the configuration of the VLAN ID and the bandwidth for the inband DCN is complete,verify the configuration by performing the preceding steps.



24

3.5 Synchronizing NE TimeAdjust the NE time to make it synchronous with the U2000 time so that the U2000 can accuratelyrecord the time when an alarm, a performance event, or an abnormal event occurs.

Prerequisitesl All the NEs in the network must be properly configured according to 3.3 Creating the

Network Topology.l You must be an NM user with "Maintenance Group" authority or higher.

l You must log in to the NE as an NE user with system level authority or higher.

NOTEThe default NE user root is of system level.


U2000

Procedure

Step 1 Make sure that the time zone of the computer where the U2000 server and the U2000 clientoperate is correct and the time of this computer is accurately set.

Step 2 Choose Configuration > NE Batch Configuration > NE Time Synchronization from theMain Menu on the U2000. Then, the NE Time Synchronization window is displayed.

Step 3 Select all the NEs in the left-hand object tree and click . Then, the selected NEs aredisplayed in the right-hand list of the NE Time Synchronization window.

Step 4 Select all the NEs in the list and right-click the Synchronous Mode field. Choose NM from theshortcut menu to set Synchronous Mode of all the NEs to NM.

Step 5 Click Apply. The Result dialog box is displayed indicating that the operation is successful. ClickClose.

Step 6 Select all the NEs in the list and right-click them. Choose Synchronize with NM Time fromthe shortcut menu.

Step 7 Click Yes in the displayed Time Synchronization Operation dialog box. Then, the Resultdialog box is displayed indicating that the operation is successful. Click Close.

----End



25

Result

Click the NE in the NE list and choose Current NE Time to check whether the current time isconsistent with that of the NMS. If yes, it indicates successful operations. If not, repeat thepreceding steps.

3.6 Enabling the NE Performance Monitoring FunctionEnabling the performance monitoring function for an NE helps perform the followingcommissioning operations and monitor new performance events in the commissioning process.If the performance monitoring function is enabled, you can obtain detailed performance recordsduring the operation process of this NE so that you can easily monitor and analyze the runningstatus of the NE. This task is optional.

Prerequisitesl All the NEs in the network must be properly configured according to Synchronizing NE

Time.l You must be an NM user with "Operator Group" authority or higher.l You must log in to the NE as an NE user with system level authority or higher.

NOTE

The default NE user root is of system level.


U2000

Procedure

Step 1 In the NE Explorer, select the NE and choose Performance > NE Performance MonitoringTime from the Function Tree.

Step 2 Enable the 15-minute performance monitoring for the NE.1. Select the NE in the Performance Monitor Time.2. Select the check box before 15-Minute.

3. Select the option button before Enable in the Set 15-Minute Monitoring group box.

4. Click to set from. The starting time must be later than the current time of the NE andNM.



26

5. If you need to set the ending time, you can select the check box before To and then click

to set To for the performance monitoring.6. Click Apply. Then, the Operation Result dialog box is displayed, indicating that the

operation is successful. Click Close.

Step 3 Follow Step 2 to enable the 24-hour performance monitoring for the NE.

----End

Result

After the NE starts performance monitoring, you can check whether performance monitoring isstarted on the NMS.

1. In the NE Explorer, select the NE and choose Performance > NE PerformanceMonitoring Time from the Function Tree.

2. Select the NE in the Performance Monitor Time interface.3. Click Query in the right corner to display Query Monitoring Time progress bar. When

the progress is 100% complete, the Operation Result dialog box is displayed, indicatingthat the operation is successful. Then, click Close.

4. The 15-Minute Performance Monitoring or 24-Hour Performance Monitoring fieldshows that the performance monitoring starts.

Follow-up Procedure

After the commissioning tasks for the entire network are complete, keep the performancemonitoring function of the NE enabled or disable it according to the customer requirement.

3.7 Checking the Optical Power of Optical InterfaceIf the transmitted or received optical power at an optical interface is excessively low or high, biterrors may be generated on the equipment, and the optical component may even be damaged.This section describes how to check the transmitted and received optical power at opticalinterfaces to ensure that the transmitted and received optical powers at all the optical interfacesare within the normal range.

Prerequisitesl All the NEs in the network must be properly enabling the NE performance monitoring

function.l You must be a U2000 user with the "Monitor Group" authority or higher.l The fibers must be routed to the ODF on all the stations.

Tools, Instruments and Materialsl Fiber cleaning toolsl Optical attenuatorl Fiber flangel U2000



27

Operation Criteria

The mean transmitted optical power and received optical power must be in the correspondingvalue ranges that are listed in Technical Specifications of Boards in the OptiX PTN 950 PacketTransport Platform of PTN Series Product Description manual.

Procedure

Step 1 In NE Explorer, click the target board and choose Configuration > Optical Power Operatiofrom the Function Tree.

Query networkwide optical power: choose Configuration > Optical Power Operation fromthe main menu.

Step 2 Click Query to read and record the current transmitted or received optical power value. Then,the Operation Result dialog box is displayed, indicating that the operation is successful.

Step 3 Check the optical port type with reference to related engineering documents.

Step 4 Check whether the transmitted and received optical powers are within the normal range.

NOTE

The received optical power must follow the standard: receiver sensitivity + 3 dBm < received optical power(tested) < overload threshold - 5 dBm.

Step 5 Optional: If the transmitted optical power is not within the normal range, handle the fault withreference to the following.

1. Clean the fiber connector if the fiber connector is not clean.

2. Restore the fiber connection at the tested optical port.

3. Check the transmitted optical power of the optical port again, until the transmitted opticalpower obtained is within the normal range.

Step 6 Optional: If the received optical power is not within the normal range, handle the fault withreference to the following.

l If the received optical power is less than sensitivity + 3 dBm

1. Check whether the fiber connector, the optical attenuator, and the fiber flange areclean.

2. If the fiber connector is not clean, clean it.

3. Restore the fiber connection at the tested optical port.

4. If the fiber flange or the optical attenuator on the ODF side is not clean, replace thefiber flange or the optical attenuator.

5. Check the received optical power of the optical port again, until the received opticalpower obtained is within the normal range.

l If the received optical power is larger than overload threshold - 5 dBm

1. Check whether the optical attenuator is normal.

2. If the optical attenuator is normal, add an optical attenuator on the ODF side.

3. If the optical attenuator is not normal, replace the optical attenuator.

4. Check the received optical power of the optical port again, until the received opticalpower obtained is within the normal range.



28

Step 7 Check whether the transmitted and received optical powers at all the other optical ports of theequipment are within the normal range one by one with reference to the previous steps.

----End

3.8 Configuring ServicesWhen the U2000 complete to maintain and manage the network for commissioning, you can usethe U2000 to configure all kinds of services that the equipment supports. This section describeshow to configure services for conducting the tests of these services.

Prerequisites

3.3 Creating the Network Topology must be performed on the U2000.

Tools, Instruments and Materials

U2000

Operation Procedure

Table 3-2 lists details on configuration of the network services.

Table 3-2 Configuration of services

Configuration items Reference

E-Line service "Configuration Flow for the E-Line Service" in the ConfigurationGuide.

E-LAN service "Configuration Flow for E-LAN Service" in the ConfigurationGuide.

ATM service "ATM Service Configuration Flow" in the ConfigurationGuide.

CES service "Configuration Flow of CES Services" in the ConfigurationGuide.

L3VPN service "Configuration Flow of BGP/MPLS L3VPN Services" in theConfiguration Guide.

3.9 Testing Service ConnectivityAfter services are configured on the U2000, test the connectivity of the services to ensure thatthe services are created correctly. This section describes how to test the connectivity of variousbasic network services.



29

3.9.1 Testing Connectivity of an E-Line ServiceTest the connectivity of an E-Line service by running Ethernet service OAM to ensure that theE-Line service is normal.

Prerequisitesl An end-to-end E-Line service must be configured.


U2000

Test Connection Diagram

Figure 3-2 shows the connection diagram for testing connectivity of an E-Line service.

Figure 3-2 Connection diagram for testing connectivity of an E-Line service

MEP1 MEP2

MD MA

PE 1 PE 2

MA: Maintenance association

MD: Maintenance domain

MEP: Maintenance end point

RMEP:MEP2 RMEP:MEP1

PSN

RMEP: Remote maintenance end point

Procedure

Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the Main Menu to displaythe Manage PWE3 Service and Set Filter Criteria windows.

Step 2 In the Set Filter Criteria window, specify the criteria for filtering E-Line services under testand then click Filter.

Step 3 Right-click an E-Line service and choose Ethernet OAM > Ethernet Test to display the LBTest window.

Step 4 In theTest type , ChooseLB.

Step 5 Click Run in the lower right corner. When Progress is 100% complete, check Test Result. IfTest Result is Test Succeeded, it indicates that the E-Line service passes the LB test.



30

Step 6 Check LB Statistic Information.l If Packet Loss Ratio (%) is 0, it indicates that the E-Line service is available.l If Packet Loss Ratio (%) is not 0, it indicates that the E-Line service has a connectivity

fault. In this case, handle the fault with reference to Ethernet Service Troubleshooting in theOptiX PTN 950 Packet Transport Platform of PTN Series Maintenance Guide.

----End

3.9.2 Testing Connectivity of an E-LAN ServiceUse the Ethernet OAM function to test the connectivity of an E-LAN service to ensure that anE-LAN service works normally.

Prerequisites

You must be an NM user with "Operator Group" authority or higher.

E-LAN service must be configured.

The Ethernet service must be configured with the Ethernet OAM.

Context

As shown in Figure 3-3, to verify the correctness of service configuration, the Ethernet OAMshould be configured.

Figure 3-3 OAM of the E-LAN service

NE 1

NE 2

NE 3

CE 2

CE 1

CE 3PSN

MEP

MEP

MD

MA3MEP

MA2

MA1

PW

MA: Maintenance Association

MD: Maintenance Domain

MEP: Maintenance End Point



31

As shown in the preceding figure, services carried by PWs are available among CE networks.To verify the configuration correctness of the service configuration, the Ethernet OAM shouldbe configured.


Procedure

Step 1 On the U2000, select NE1 to create the maintenance domain. For the creation method, seeCreating an MD.The parameters of the maintenance domain are as follows:l Maintenance Domain Name: MDl Maintenance Domain Level: 4



NOTEThe MD name and MD level for each NE should be consistent. In this way, the NEs belong to the samemaintenance domain.

Step 4 On the U2000, select NE1 and NE2 separately to create the maintenance association for theservice between NE1 and NE2. For the creation method, see Creating an MA.The parameters of the maintenance association are as follows:l Maintenance Domain Name: MDl Maintenance Association Name: MA1l Relevant Service: 1-E-LAN-1l CC Test Transmit Period (ms): 3.33 ms




32


Step 7 On the U2000, select NE1 to create the MEP. For the creation method, see Creating a MEPMaintenance Point.The parameters of the MEP of MA1 are as follows:l Maintenance Domain Name: MDl Maintenance Association Name: MA1l Board:

3-EF8Tl Port: 1 (Port-1)l VLAN: 100l MEP ID: 1l Direction: Ingressl CC Status: ActiveThe parameters of the MEP of MA3 are as follows:l Maintenance Domain Name: MDl Maintenance Association Name: MA3l Board:

3-EF8Tl Port: 2 (Port-2)l VLAN: 300l MEP ID: 1l Direction: Ingressl CC Status: Active





33

The parameters of the MEP of MA2 are as follows:l Maintenance Domain Name: MDl Maintenance Association Name: MA2l Board:



3-EF8Tl Port: 1 (Port-1)l VLAN: 200l MEP ID: 3l Direction: Ingressl CC Status: ActiveThe parameters of the MEP of MA3 are as follows:l Maintenance Domain Name: MDl Maintenance Association Name: MA3l Board:


Step 10 On the U2000, select NE1 to create the remote MEP. For the creation method, see Adding aRemote MEP of the MA.The parameters of the remote MEP of MA1 are as follows:l Maintenance Domain Name: MDl Maintenance Association Name: MA1l Remote Maintenance Point ID: 2The parameters of the remote MEP of MA3 are as follows:l Maintenance Domain Name: MD



34

l Maintenance Association Name: MA3

l Remote Maintenance Point ID: 3

Step 11 On the U2000, select NE2 to create the remote MEP. For the creation method, see Adding aRemote MEP of the MA.The parameters of the remote MEP of MA1 are as follows:

l Maintenance Domain Name: MD



The parameters of the remote MEP of MA2 are as follows:




Step 12 On the U2000, select NE3 to create the remote MEP. For the creation method, see Adding aRemote MEP of the MA.The parameters of the remote MEP of MA2 are as follows:




The parameters of the remote MEP of MA3 are as follows:




Step 13 Optional: If you configure MEP with CC unactivated, you need to activate CC. For the creationmethod, see Performing a Continuity Check.

NOTE

After the CC is activated at the source and sink of a service, the source periodically builds and sends CCcells. The end automatically reports the ETH_CFM_LOC alarm if it does not receive the CC cells fromthe source within the required time.

If a link is already faulty when CC is initiated, TND1CXP boards will report the ETH_CFM_FAILalarm. TND2CXP, and TND2CXPC boards will report the ETH_CFM_LOC alarm.

----End

3.9.3 Testing Connectivity of a UNIs-NNI ATM ServiceUse the ATM OAM function to test the connectivity of the UNIs-NNI ATM service to ensurethat the ATM service works normally. This section describes how to test the connectivity of theATM service by performing loopback (LB) test.

Prerequisitesl An end-to-end ATM service must be configured.




35

Tools, Instruments and Materials

U2000


Figure 3-4 shows the connection diagram for testing the connectivity of the ATM service.

Figure 3-4 Connection diagram for ATM service connectivity test

PSN

PE2

Inloop

PE1

Inloop

Procedure

Step 1 Set the loopback automatic disabling function to Disabled for the UNI interfaces accessing thetested ATM service on the PE1 and PE2 equipment.1. Choose Configuration > NE Batch Configuration > Automatic Disabling of NE

Function from the Main Menu to display the Automatic Disabling of NE Function dialogbox.

2. Select the PE1 and PE2 in the left-hand object tree and click . The selected NEsare displayed in Automatic Disabling of NE Function on the right.

3. Set Auto Disabling to Disabled for SDH Optical/Electrical Interface Loopback of thePE1 and PE2.

NOTE

When the automatic disabling function of SDH Optical/Electrical Interface Loopback on the NE is setto Disabled, the loopback automatic disabling function for all of the SDH optical interfaces, PDH electricalinterfaces and ATM IMA groups on the NE is disabled.

Step 2 Set inloop for the UNI interface (to be tested) accessing the ATM service on PE1 by using theU2000.

l The UNI interface accessing the ATM service is IMA group.

1. On the Main Topology, select and right-click the PE1 NE. In the shortcut menu, chooseNE Explorer to display the NE Explorer window.

2. In the NE Explorer window, select the NE, and choose Configuration > InterfaceManagement > ATM IMA Management from the Function Tree.



36

3. Select the ATM Interface Management tab and then select the IMA group carryingthe tested ATM service.

4. Double-click the Loopback of the IMA group, and then select Inloop in the shortcutmenu.

5. Click Apply. A dialog box is displayed for confirmation, click OK. The OperationResult dialog box is displayed indicating that the operation is successful. Click Close.

l The UNI interface accessing the ATM service is ATM interface.

1. On the Main Topology, select and right-click the PE1 NE. In the shortcut menu, chooseNE Explorer to display the NE Explorer window.

2. In the NE Explorer window, select the ATM carrying the tested ATM service, andchoose Configuration > Interface Management > SDH Interface from the FunctionTree.

3. Select the Advanced Attributes tab and then select the ATM interface carrying theATM service.

4. Double-click the Loopback of ATM interface, and then select Inloop in the shortcutmenu.


Step 3 Set inloop for the UNI interface (to be tested) accessing the ATM service on PE2 with referenceto Step 2.

Step 4 In the NE Explorer window, select the PE1 NE, and choose Configuration > ATM OAMManagement from the Function Tree.

Step 5 Select the Remote Loopback Test tab, and then select the tested ATM service.

Step 6 Set Segment and End Attribute of the service whose Connection Direction is Sink toSegment point.

NOTE

Segment End Attribute of ATM service specifies the type of the transmitted OAM cells during the LB test.

l If Segment End Attribute is set to Segment point, seg_LB cells is transmitted.

l If Segment End Attribute is set to Endpoint, e-t-e_LB cells is transmitted.

Step 7 Set the Loopback Point NE of the tested ATM service to PE2 NE.

Step 8 Click Test to start the LB test. Then, a progress bar is displayed. After the test is complete, theOperation Result dialog box, indicating that the operation is successful, is displayed. Then,click Close.



37

Step 9 After the test is finished, check the Test Result of the tested ATM service. Normally, the TestResult should be Test succeeded.

l Normally, Test Result should be Test Succeeded. After a message indicating that the testis successful is displayed, view the new performance events to determine whether the LBtest is successful.

1. In the Main Topology, click the icon to display the Query Event Logs window.Then, select the Reporting of LB status information performance event.

2. Right-click Reporting of LB status information. In the displayed menu, chooseDetails .... Then, a window indicating detailed information is displayed. You can checkthe additional information to confirm the test result.

l If the test result is Test Failed or another failure message, handle the fault with reference tothe Test Result hint and "IMA Troubleshooting" in the OptiX PTN 950 Packet TransportPlatform of PTN Series Maintenance Guide.

Step 10 Release the inloop of the UNI interface accessing the ATM service on PE1 and PE2 withreference to Step 2.

Step 11 Follow Step 2 - Step 10 to test the connectivity of all the other ATM services on PE1 and PE2.

Step 12 Set Automatic Disabling to Enabled for SDH Optical/Electrical Interface Loopback on PE1and PE2 with reference to Step 1.

Step 13 Test the connectivity of the ATM services on all the other NEs with reference to Step 1 - Step12.

----End

3.9.4 Testing Connectivity of a CES ServiceTest connectivity of an end-to-end CES service, which works normally only when it isconnective. This section describes how to test connectivity of a CES service by using the PRBSfunction.

Prerequisitesl An end-to-end CES service must be configured.


l The board under test, which carries CES services, must support the PRBS function.

Tools, Instruments and Materialsl U2000



38

Precautions

CAUTIONOn an NE, when using the PRBS function to test connectivity of a CES service, make sure thatno activated service is running at the optical port or E1 port where a loopback is performed.Otherwise, the service is interrupted.

NOTE

On the UNI/NNI side of the equipment, connectivity of an E1 service in framed or unframed mode can be testedby using the PRBS function.

On the UNI/NNI side of the equipment, connectivity of a VC-12 service in framed or unframed mode can betested by using the PRBS function.

Fractional E1 services do not support the connectivity test.


Figure 3-5 shows the connection diagram for testing connectivity of a CES service.

Figure 3-5 Connection diagram for testing connectivity of a CES service

PSN

PE2

Inloop

PE1

Procedure

Step 1 Set the loopback automatic disabling function to Disabled for the CES service interface undertest on PE2 by using the U2000.

1. Choose Configuration > NE Batch Configuration > Automatic Disabling of NEFunction from the Main Menu to display the Automatic Disabling of NE Functionwindow.

2. Select PE2 in the left-hand object tree and click . The selected NE is displayed inAutomatic Disabling of NE Function on the right.

3. Set Auto Disabling to Disabled for SDH Optical/Electrical Interface Loopback.



39

The loopback automatic disabling function for all PDH electrical interfaces and otherwiseof PE2 is set to Disabled.

4. Click Apply. The Operation Result dialog box is displayed indicating that the operationis successful. Click Close.

Step 2 On the U2000, perform an inloop at the UNI port for the CES service under test on PE2.1. On the Main Topology, right-click PE2. In the shortcut menu, choose NE Explorer to

display the NE Explorer window.2. In the NE Explorer window, select the NE, and choose Configuration > Interface

Management > PDH Interface from the Function Tree.

NOTE

At this step, the test is based on the condition that an inloop is performed at the E1 port. If the port undertest is a VC-12 port, choose Configuration > Interface Management > SDH Interface from theFunction Tree.

3. Select the Advanced Attributes tab and then select the interface receiving/transmittingthe CES service under test.

4. Right-click the Loopback Mode field of the interface, and then select Inloop from theshortcut menu.


Step 3 Start the PRBS test at the corresponding port for the CES service under test on PE1.1. On the U2000, right-click PE1 in the Main Topology. Then, choose NE Explorer to display

the NE Explorer.2. Choose the board under test from the Object Tree on the upper right side and choose

Configuration > PRBS Test from the Function Tree on the lower left side.3. Select the CES service port under test. Then, set PRBS Frame Modeto Frame or No

Frame. The framing modes of interconnected service ports must be consistent.4. In the Set Test Parameters areaon the lower right side,set Direction, Duration, and

Measured in times for the CES service under test.5. Click Start to test to display the confirmation dialog box. Then, click OK. The Operation

Result dialog box is displayed. Then, click Close.

6. WhenProgressis displayed as 100%, click Query and observe the test result.l If bit errors are indicated in the test result, go to Step 4.l If no bit error is indicated in the test result, go to Step 5.



40

Step 4 Check for abnormal CES-related alarms and rectify faults by referring to CES ServiceTroubleshooting in the OptiX PTN950 Packet-Based Transport Platform of Optical PTNSeries Maintenance Guide.

Step 5 Release the inloop at the port under test on PE2 by referring to Step 2.

Step 6 Set Auto Disabling on the loopback at the optical/electrical interface on PE2 to Enabled byreferring to Step 1.

Step 7 Test connectivity of CES services on other NEs by referring to Step 1 to Step 6.

----End

3.9.5 Testing Connectivity of a CES Service (VC3/VC4)Test connectivity of an end-to-end CES service, which works normally only when it isconnective. This section describes how to test connectivity of a CES service by using the PRBSfunction.

Prerequisitesl An end-to-end CES service must be configured.l You must be an NM user with "Operator Group" authority or higher.l The board under test, which carries CES services, must support the PRBS function.

Tools, Instruments and Materialsl U2000

Precautions

CAUTIONWhen using the NE's PRBS function to check CES connectivity,make sure that no active serviceis running at the interface to be loopbacked, otherwise, the service is interrupted.

Test Connection DiagramFigure 3-6 shows the connection diagram for testing connectivity of a CES service.

Figure 3-6 Test Connection Diagram

PSNPE2PE1 CE

Remote Loopback



41

Procedure

Step 1 On the U2000, configure a CE side remote loopback for the CES service under testing, at PE2'sUNI.1. On the main topology of the U2000, right-click and select the PE2 NE. Right-click and

select NE Explorer. The NE Explorer window is displayed.2. Select the TND1CQ1 board to be tested on the upper left of the window and then select

Configuration > Remote Loopback on the lower left function tree of the window.3. Select the CES service port in the displayed window, and set Remote Loopback to

Enabled on the lower right of the window.Click Apply.

Figure 3-7 shows the bit sequence of the Z2 byte.

huawei optix ptn 950 commissioning guide(v100r005)

Documents

huawei trademarks

huawei proprietary

huawei industrial basebantian

versionoptix ptn

commissioning process

system commissioning

commissioning flow

additional information