ATN 910&910I&910B&950B V200R003C10 Configuration Guide 01(U2000)

ATN 910&910I&910B&950B Multi-Service AccessEquipmentV200R003C10

Configuration Guide

Issue 01Date 2014-01-31

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 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.comEmail: [email protected]

Issue 01 (2014-01-31) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

i

About This Document

PurposeThis manual describes configuration of U2000 for ATN.The usage precautions are as follows:l A device can store keys in plaintext, reversible algorithm encryption, or irreversible

algorithm encryption mode. The plaintext mode has the low security level, and theirreversible algorithm encryption mode has the highest security level. Use different storagemodes for different scenarios. Exercise caution when using an insecure storage mode. Thesystem automatically selects the irreversible algorithm encryption mode to store local userkeys. Generally, the reversible algorithm encryption mode is used to store protocol keys tomeet interworking requirements.

l If the plaintext mode is used, a password is stored in plaintext in the configuration file. Thisresults in high security risks. The plaintext mode applies only to scenarios with specialrequirements, such as compatibility and interworking requirements.

Related VersionThe following table lists the product version related to this document.

Product Name Versionl ATN 910l ATN 910Il ATN 910Bl ATN 950B

V200R003C10

Huawei iManager U2000 V200R001C00

Intended AudienceThis document is intended for:l Commissioning Engineer

ATN 910&910I&910B&950B Multi-Service AccessEquipmentConfiguration Guide About This Document


ii

l Data Configuration Engineerl Network Monitoring Engineerl System Maintenance Engineer

Symbol ConventionsSymbol Description

Indicates an imminently hazardous situation which, if notavoided, will result in death or serious injury.

Indicates a potentially hazardous situation which, if notavoided, could result in death or serious injury.

Indicates a potentially hazardous situation which, if notavoided, may result in minor or moderate injury.

Indicates a potentially hazardous situation which, if notavoided, could result in equipment damage, data loss,performance deterioration, or unanticipated results.NOTICE is used to address practices not related to personalinjury.Calls attention to important information, best practices andtips.NOTE is used to address information not related to personalinjury, equipment damage, and environment deterioration.

Command ConventionsConvention DescriptionBoldface 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.



iii

Convention Description{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of allitems can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated byvertical bars. Several items or no item can be selected.

GUI ConventionsConvention DescriptionBoldface Buttons, menus, parameters, tabs, window, and dialog titles

are 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 01 (2014-01-31)This document is the first release of the V200R003C10 version.



iv

Contents

About This Document.....................................................................................................................ii1 Network Deployment...................................................................................................................11.1 Overview........................................................................................................................................................................11.2 Creating a Topology.......................................................................................................................................................21.3 Deploying a Network Using the Plug-and-Play Management.....................................................................................111.3.1 IP LCT Overview......................................................................................................................................................111.3.2 IP LCT Operation Tasks............................................................................................................................................181.3.3 Common Maintenance Operations............................................................................................................................371.4 Deploying a Network Using the NE Explorer..............................................................................................................671.4.1 Panorama of NE management features......................................................................................................................671.4.2 General Instructions for the NE Explorer..................................................................................................................721.5 Verifying Basic Configuration.....................................................................................................................................762 Service Deployment (End-to-End Mode)................................................................................792.1 Support for End-to-End function..................................................................................................................................792.2 Automatically Discovering IP Services........................................................................................................................792.2.1 Automatically Discovering Single IP Services.........................................................................................................792.2.2 Automatically Discovering Composite Services.......................................................................................................822.3 Deploying a Tunnel......................................................................................................................................................842.3.1 Tunnel Service Function Panorama...........................................................................................................................852.3.2 Creating a Tunnel......................................................................................................................................................882.3.3 Creating Tunnel Protection......................................................................................................................................1002.4 Deploying L3VPN Services.......................................................................................................................................1032.4.1 L3VPN Service Function Panorama........................................................................................................................1032.4.2 Creating an L3VPN Service....................................................................................................................................1062.5 Deploying VPLS Services..........................................................................................................................................1082.5.1 VPLS Service Function Panorama..........................................................................................................................1082.5.2 Creating a VPLS Service.........................................................................................................................................1112.6 Deploying PWE3 Services.........................................................................................................................................1182.6.1 Service Function Panorama.....................................................................................................................................1182.6.2 Creating Pwe3 Service.............................................................................................................................................1222.7 Deploying Composite Services..................................................................................................................................1412.7.1 Composite Service Function Panorama...................................................................................................................141

ATN 910&910I&910B&950B Multi-Service AccessEquipmentConfiguration Guide Contents


v

2.7.2 Creating a Composite Service.................................................................................................................................1432.7.3 Modifying a Composite Service..............................................................................................................................1522.8 Deploying Network Reliability..................................................................................................................................1522.8.1 Configuring BFD.....................................................................................................................................................1532.8.2 Configuring VRRP..................................................................................................................................................1583 Service Deployment (Single-Station Mode)........................................................................1623.1 Setting Telnet/STelnet Parameters.............................................................................................................................1623.1.1 Configuring a Telnet/STelnet Parameter Template.................................................................................................1623.1.2 Setting Telnet/STelnet Parameters with a Template...............................................................................................1633.1.3 Manually Modifying Equipment Telnet/STelnet Parameters..................................................................................1643.2 Managing Devices......................................................................................................................................................1653.2.1 Setting and Viewing System Information...............................................................................................................1653.2.2 Setting the IP Address of an NE..............................................................................................................................1663.2.3 NE Panel Management............................................................................................................................................1663.2.4 Viewing Subrack Information.................................................................................................................................1813.2.5 Configuring Global System Attributes....................................................................................................................1813.2.6 Managing Historical Resources...............................................................................................................................1823.3 Interface Management................................................................................................................................................1843.3.1 Universal Interface Configuration...........................................................................................................................1843.3.2 Configuring Service Interfaces................................................................................................................................1873.3.3 Configuring a Service Feature for an Interface.......................................................................................................2023.4 NE Channel Management...........................................................................................................................................2053.4.1 Configuring the VTY Service..................................................................................................................................2053.4.2 Configuring the Status of the FTP Server...............................................................................................................2053.4.3 Creating a Local User..............................................................................................................................................2063.4.4 Configuring the Syslog Service...............................................................................................................................2073.4.5 Configuring the Trap Service..................................................................................................................................2083.4.6 Configuring the SSH Service..................................................................................................................................2123.5 ACL Management......................................................................................................................................................2143.5.1 Process of Configuring an ACL Service.................................................................................................................2143.5.2 Configuring a Time Range......................................................................................................................................2153.5.3 Creating an ACL Group..........................................................................................................................................2183.5.4 Configuring ACL Rules...........................................................................................................................................2183.6 Ethernet Feature Management....................................................................................................................................2223.6.1 VLAN Management................................................................................................................................................2223.6.2 MAC Address Forwarding Management................................................................................................................2253.7 Ethernet OAM Management......................................................................................................................................2293.7.1 Processes of Configuring Ethernet OAM................................................................................................................2293.7.2 Configuring Ethernet OAM Globally......................................................................................................................2313.7.3 Configuring 802.1ag OAM......................................................................................................................................2323.7.4 Configuring 802.3ah OAM......................................................................................................................................245



vi

3.7.5 Configuring Test Diagnosis.....................................................................................................................................2503.7.6 Creating an OAM Statistics Task............................................................................................................................2533.8 MPLS-TP OAM Management....................................................................................................................................2533.8.1 Creating an MEG.....................................................................................................................................................2543.9 Clock Configuration...................................................................................................................................................2563.9.1 Process of Configuring a Clock...............................................................................................................................2563.9.2 Clock Operation Tasks............................................................................................................................................2593.9.3 GUI Description......................................................................................................................................................2703.10 Route Management...................................................................................................................................................2943.10.1 Viewing Global Route Parameters........................................................................................................................2943.10.2 Viewing Routing Information...............................................................................................................................2953.10.3 Creating a Static Route..........................................................................................................................................2953.10.4 Creating a BGP Route...........................................................................................................................................2963.10.5 Creating an OSPF Route........................................................................................................................................3063.10.6 Creating an IS-IS Route.........................................................................................................................................3103.10.7 Creating an IP Prefix.............................................................................................................................................3133.10.8 Creating a Policy...................................................................................................................................................3133.10.9 Viewing Running Information...............................................................................................................................3143.11 MPLS Management..................................................................................................................................................3183.11.1 Configuring MPLS Globally.................................................................................................................................3183.11.2 Configuring MPLS on an Interface.......................................................................................................................3253.11.3 Creating a Tunnel..................................................................................................................................................3313.11.4 Creating a Static LSP Segment..............................................................................................................................3333.11.5 Creating a Protection Group..................................................................................................................................3343.11.6 Configuring MPLS Detection................................................................................................................................3353.11.7 Maintaining an MPLS Service..............................................................................................................................3363.12 LLDP Management..................................................................................................................................................3403.12.1 Configuring an LLDP Service...............................................................................................................................3403.12.2 Synchronizing LLDP Neighbor Information.........................................................................................................3433.13 BFD Management.....................................................................................................................................................3443.13.1 Configuring Global BFD Attributes......................................................................................................................3443.13.2 Configuring a BFD Global TTL............................................................................................................................3453.13.3 Configuring Service Detection..............................................................................................................................3463.14 QoS Management.....................................................................................................................................................3573.14.1 Configuring HQoS.................................................................................................................................................3583.14.2 Creating and Deploying a DS Domain Policy.......................................................................................................3613.14.3 Configuring Interface QoS....................................................................................................................................3623.14.4 Generating a Global QoS Profile...........................................................................................................................3653.15 BRAS Management..................................................................................................................................................3663.15.1 Configuring AAA..................................................................................................................................................3663.16 VPN Management....................................................................................................................................................370



vii

3.16.1 Creating a Tunnel Policy.......................................................................................................................................3703.16.2 Creating a PW Template........................................................................................................................................3713.16.3 Creating a PW........................................................................................................................................................3723.16.4 Creating a PW APS Protection Group...................................................................................................................3753.16.5 Creating a VSI.......................................................................................................................................................3753.16.6 Creating a VRF......................................................................................................................................................3773.16.7 Creating a CCC Connection..................................................................................................................................3793.17 Accessing NEs Through a Tool................................................................................................................................3803.17.1 Ping........................................................................................................................................................................3803.17.2 Tracert....................................................................................................................................................................3813.17.3 Telnet.....................................................................................................................................................................3823.17.4 SSH........................................................................................................................................................................3823.17.5 ICMP Ping.............................................................................................................................................................3833.17.6 ICMP Trace...........................................................................................................................................................3844 IPTime MBB Backhaul ATN+CX Solution Configuration Guide...................................3854.1 IPTime MBB ATN+CX (Hierarchy VPN) Solution Configuration...........................................................................3854.1.1 Preparations for Service Configuration...................................................................................................................3854.1.2 Deploying MPLS LSPs...........................................................................................................................................3864.1.3 Creating a Template.................................................................................................................................................3994.1.4 Deploying Ethernet Services and Protection Protocols...........................................................................................4054.1.5 Deploying Dual-Homing TDM Services and Protection........................................................................................4394.1.6 Deploying Single-homed 2G TDM Services and Protection..................................................................................4524.1.7 Deploying Dual-Homing ATM Services and Protection........................................................................................4614.1.8 Deploying Single-homed 3G ATM Services and Protection..................................................................................4754.1.9 (Optional) Detecting SD Bit Errors.........................................................................................................................4844.1.10 Deploying Clock Synchronization.........................................................................................................................4874.1.11 Deploying QoS......................................................................................................................................................5024.2 IPTime MBB ATN+CX (Mixed VPN) Solution Configuration................................................................................5094.2.1 Preparations for Service Configuration...................................................................................................................5094.2.2 Deploying MPLS LSPs...........................................................................................................................................5104.2.3 Creating a Template.................................................................................................................................................5224.2.4 Deploying Ethernet Services and Protection Protocols...........................................................................................5284.2.5 Deploying Dual-Homing TDM Services and Protection........................................................................................5584.2.6 Deploying Single-homed 2G TDM Services and Protection..................................................................................5714.2.7 Deploying Dual-Homing ATM Services and Protection........................................................................................5804.2.8 Deploying Single-homed 3G ATM Services and Protection..................................................................................5944.2.9 (Optional) Detecting SD Bit Errors.........................................................................................................................6034.2.10 Deploying Clock Synchronization.........................................................................................................................6064.2.11 Deploying QoS......................................................................................................................................................621



viii

1 Network Deployment1.1 Overview

This topic describes the deployment task, implementation modes, and applicable scenarios atthe network deployment stage. Network deployment must be complete before servicedeployment.

Table 1-1 Deployment taskConfigurationItem

Description

Configuring themanagementchannel

To configure basic channel parameters such as Telnet/STelnet and SNMPparameters.

Configuring theinterface

To create and configure interface IP addresses and logical interfaces (loopbackinterfaces and subinterfaces).

Configuring IGPand BGP

To create basic routes, for example, IS-IS routes.

Configuring MPLS

To configure MPLS and LDP globally and on interfaces.

Configuring thetunnelpolicy

To configure the tunnel selection policy.

ATN 910&910I&910B&950B Multi-Service AccessEquipmentConfiguration Guide 1 Network Deployment


1

ConfigurationItem

Description

Configuring theroutingpolicy

To configure the route selection policy.

The U2000 provides two modes to implement the preceding deployment task.

Table 1-2 Implementation modesImplementationMode

Applicable Scenario

1.3Deployinga NetworkUsing thePlug-and-PlayManagement

This mode is recommended if large-size deployment needs to be completed inbatches.For example, there may be more than one hundred CSGs at each site in the IPRAN deployment scenario and the Plug-and-Play Management isrecommended to implement batch deployment. The U2000 Plug-and-PlayManagement supports plug-and-play (devices must support this function too).After devices are powered on and connected to fibers, the Plug-and-PlayManagement automatically completes the network deployment based onpredefined configurations. The software commissioning engineers do not needto go to the site and the deployment is of high efficiency.

1.4Deployinga NetworkUsing theNEExplorer

l Deploy configurations during network deployment or routine maintenancewhen not so many devices are located on the live network.

l Check configurations. After the U2000 Plug-and-Play Management is usedto deploy basic configurations, the U2000 NE Manager can be used to checkwhether the deployed configurations are correct.

l Modify basic configuration for a single NE.

1.2 Creating a TopologyThis topic describes how to create a topology when creating a large amount of NEs in batches.Creating a topology is the prerequisite for network deployment. A topology view helps to learnabout the real-time status of the entire network. The U2000 uses a topology view to display thestatus of all the managed NEs as well as the links between the NEs. In addition, the U2000provides the subnet management function for you to manage the topological objects that are inthe same area of a network or with similar attributes.



2

ContextNetwork deployment can be implemented using the Plug-and-Play Management or NE Explorer.If the Plug-and-Play Management is used, the following configurations are optional for NEs thatsupport automatic NE configuration. In other cases, the following configurations are mandatory.The topology creation procedure varies according to the usage scenario and habit. If a largenumber of NEs need to be created in a scenario such as deployment, the topology creationprocedure shown in Table 1-3 is recommended.

Table 1-3 Recommended topology creation procedureOperation DescriptionCreate a subnet. To facilitate management, you can put topological objects that are in

the same area of a network or with similar attributes to the sametopology subnet.

Create NEs inbatches.

Every physical device is displayed as an NE on the U2000. To use theU2000 to manage these devices, you must create the relevant NEs onthe U2000. If a large number of NEs need to be created in a scenariosuch as deployment, creating NEs in batches is recommended.NOTEl When creating NEs in batches, you can use SNMP and Telnet/STelnet

templates to automatically apply the parameter settings.l Using SNMPv3 is recommended because of its higher security than

SNMPv1 and SNMPv2c.l Using STelnet is recommended because of its higher security than Telnet.

Select an NE layout. The U2000 provides various NE layouts in order to vividly show theactual network topology.

Create links. The communication between the U2000 and managed NEs andbetween these NEs is implemented based on links. You can configureservices or manage NEs only after creating the associated links in thetopology view.

Synchronize NEdata.

In routine maintenance, NE data may be inconsistent with U2000data. In this case, you can synchronize NE data to the U2000.

Prerequisitesl The U2000 communicates with NEs successfully. That is, correct IP addresses are

configured for NEs and the U2000 and managed NEs can ping each other.l Before automatic ICMP NE searches, disable ICMP packet blocking in the firewall of the

U2000 server, because the ICMP packet blocking interrupts communication between theU2000 and ICMP NEs.

l Interworking between NEs to be managed and the U2000 has been commissioned. Telnet/STelnet, SNMP, and NetConf parameters have been set.



3

Procedure1. Create a subnet.

a. Right-click in the Main Topology and choose Create > Subnet from the shortcutmenu.

b. In the dialog box that is displayed, select Property and set Name for the subnet to becreated.

NOTEFor example, set Name to IPRAN.

c. Click OK.2. Create NEs in batches.

a. Choose File > Discovery > NE from the main menu.b. Click ... on the right of the NE Type text box. In the dialog box that is displayed,

specify the desired NE type.c. Click Default SNMP Parameter. In the dialog box that is displayed, set SNMP

parameters and ensure that the parameters are consistent with those on the NE side.a. Click the tab associated with the desired SNMP version. Then click Add.b. Set Template Name and other parameters as needed.

NOTE

l The SNMP parameter values must be the same as those on NEs.l Using SNMPv3 is recommended because of its higher security than SNMPv1 and

SNMPv2c. This snapshot uses an SNMPv3 template as an example. The parametersto be set for SNMPv1 and SNMPv2c templates are different from those for anSNMPv3 template.

l The U2000 uses SNMPv2c or SNMPv3 to communicate with NEs to ensure propercollection of service performance data. However, SNMPv3 is recommended as it ismore secure than SNMPv2c.

l SNMPv2c parameters must be used to add the RM9000s in batches, and the parametervalues are fixed. The details are as follows: Set Template Name to rm, GetCommunity and Set Community to v2cUser, and NE Port to 8000.

c. Click OK.



4

d. Click OK.d. Optional:

Set Ping Times, Timeout, and Layers as needed.NOTE

If many NEs need to be searched on the network, setting Ping Times to 3 and Timeout to 5 isrecommended. Otherwise, some NEs may fail to be searched out.

e. Optional:(Optional) If an SNMP version is not required, select the desired version inVersion, right-click, and choose Delete from the shortcut menu.

NOTEDeleting the SNMP version that is not required improves NE search efficiency.

f. Select Automatically Create NEs.g. Click Advanced and set Telnet/STelnet or NetConf parameters for NEs. Using

STelnet is recommended because of its higher security than Telnet.a. Click ... on the right of Telnet/STelnet Settings. In the dialog box that is

displayed, configure a Telnet/STelnet parameter template with the parametervalues consistent with those on NEs. Telnet/STelnet parameter settings in thetemplate are automatically applied to created NEs.1) Click Create.2) In the dialog box that is displayed, set Protocol Name and Template

Name.3) Click OK.4) Select the newly created template. In the Details area, set the relevant

parameters and click Apply.NOTE

If the AAA user needs to be used, set Auth. Mode to User Auth. In addition, setUser Name and Password.



5

b. Optional: Click the ... button on the right of NetConf Settings. In the dialog boxthat is displayed, configure a NetConf parameter template with the parametervalues consistent with those on NEs. NetConf parameter settings in the templateare automatically applied to created NEs.

NOTENetConf parameters need to be set only when VRP V8-based routers are to be created.

1) Click Create.2) In the dialog box that is displayed, set Template Name.3) Click OK.4) Select the newly created template. In the Details area, set the relevant

parameters and click Apply.c. Click OK.

h. Check whether xFTP service status is normal: Choose Administration > Settings >xFtpWatcher from the main menu to check whether configuration items in the listare marked green. If the xFTP service status is abnormal or not configured, configurethe xFTP service by performing operations described in Configure a xFTPwatcher in the follow-up procedure section.

i. Click ... on the right of the Physical Path text box. Then select the created IPRANsubnet.

j. In the IP Address Range area, click Add. In the dialog box that is displayed, set startIP address, end IP address and a mask as need and click OK.



6

k. Click Next. The U2000 begins to search for NEs. The U2000 automatically createsNEs after finding NEs that meet the search criteria.

l. Click Close. The NE Discovery dialog box is closed.NOTE

If you still need to create some NEs, repeat the preceding steps.3. Select an NE layout.

a. Double-click in the Main Topology to access the IP RAN. Right-click and chooseLayout from the shortcut menu.

b. In the Layout dialog box, set the layout type of NEs. Click OK.



7

4. Create links.a. Choose File > Discovery > Link from the main menu.b. Optional: Choose to select Do you want to synchronize LLDP data on the

equipment? above the object list.c. Select one or more NEs or subnets from the list on the left and click .d. In the LLDP Status Management dialog box, perform the following operations:

a. Set LLDP Status to Open and click OK.NOTE

If LLDP has been enabled for NEs, links will be automatically created when NEs arebeing searched. LLDP needs to be enabled because it is disabled by default.

b. In the dialog box that is displayed, click Close.c. The dialog box indicating It takes 30s before the enabled LLDP takes effect.

Are you sure to perform search? is displayed. Click OK. A progress bar isdisplayed indicating the search progress.

e. After the search is complete, a dialog box is displayed indicating that the operation issuccessful. Click Close. Link search results are displayed.

f. In the Link Search window, select all the links that have been searched out and clickCreate. A progress bar is displayed indicating the link creation progress.

g. After creation, a confirmation dialog box is displayed. Click Close.h. The dialog box indicating Are you sure to import links as fibers/cables is displayed.

Click OK. The Import Link dialog box is displayed.

i. Select links and click to import all the link information to Selected Link. ClickOK. The U2000 then automatically creates fibers.

j. Drag the NE icon to adjust the structure of the network topology.



8

5. Synchronize NE data.Select all NEs in the Main Topology, right-click, and choose Synchronize NE Data fromthe shortcut menu.In the dialog box that is displayed, NE data is then automaticallysynchronized from the NEs to the U2000.

NOTE

After NEs are created on the U2000, the NE data is automatically synchronized to the U2000. If someconfigurations are delivered to NEs using commands or other methods, perform the precedingoperations to synchronize NE data to the U2000.

Follow-up ProcedureConfigure a xFTP watcher.1. Choose Administration > Settings > xFtpWatcher from the main menu.2. In the xFtpWatcher dialog box, click Add.3. In the dialog box that is displayed, set the parameters.



9

NOTE

l The default values of Username, Password, and Root path of the U2000 xFTP service areftpuser, Changeme_123, d: (Windows-based server. If the server does not have drive D, set thedrive where the U2000 is installed as the root directory.) or /opt/backup/ftpboot (Linux-basedserver or Solaris-based server for single-server system) or /opt/sybase/data (Solaris-based serverfor backup system) respectively.

l If the user password and path of the xFTP service are changed, make sure that Password andRoot path in the xFtpWatcher dialog box are also changed.

l IP address cannot be set to 127.0.0.1.l In the case of a single-server system, IP address is the IP address of the xFTP server that can

communicate with NEs, that is, the IP address of the U2000 server. In the case of a distributedsystem, IP address is the IP address that is configured by means of the network addresstranslation (NAT).

l Port: Please use the default port ID, and ensure that the port is not occupied.l The value of Root path must be correct. In addition, Root path must be an absolute path and

cannot end with / or \ or contain a space. On Windows OS, the default value of Root path is "d:"disk, if the "d:" disk does not exist, please set the non-system disk as the root path of the FTPserver manually.

4. Optional: In the xFtpWatcher dialog box, click FTP Server Setting to set FTP serverparameters such as the password and root path and start or shut down the FTP server.

NOTE

l Click next to Password and change the password for the FTP server in the dialog box thatis displayed.

l By default, the FTP server of the U2000 is started. If you want to stop it, click Stop.l By default, the root directory of the FTP server is d: on a PC running Windows. If d: does not

exist, set the root directory of the FTP server in a non-system disk.



10

1.3 Deploying a Network Using the Plug-and-PlayManagement

The Plug-and-Play Management deploys initial configurations during deployment andimplements plug-and-play of new NEs using the automatic NE configuration function.

1.3.1 IP LCT OverviewThis topic describes IP LCT in terms of the following items: functions, usage scenarios,principles, and GUIs.

System OverviewThe IP LCT can be used to complete remote commissioning and basic configuration for a largenumber of NEs, freeing software commissioning engineers from going to sites and improvingthe deployment efficiency.l The IP LCT provides system-defined templates and baseline templates. You need to set

only a few parameters for generating basic NE configuration scripts.l The IP LCT supports remote commissioning using the Dynamic Host Configuration

Protocol (DHCP) or through the data communication network (DCN) to rapidly enablemanagement channels for new NEs. Software commissioning engineers can remotely addNEs and assign management IP addresses to the NEs, without going to sites. Theconfiguration scripts are automatically applied to the NEs for site deployment. Currently,CX600-X1, CX600-X2, CX600-X8-D0, ATN910, ATN950, ATN950B, ATN980, andATN990 support automatic NE configuration.

Figure 1-1 Typical usage scenario for the IP LCT

Network planning engineer

Software commissioning engineer

U2000 plug-and-play management

Perform remote commissioning in

DCN mode

Deploy IP services

Install hardware

Perform remote commissioning in

DHCP mode

Hardware installation engineer

Plan data

Customize a template

Configure a scenario and a management channel



11

During deployment, the IP LCT is mainly used to perform DCN configurations for new NEs sothat the U2000 can manage the NEs. The IP LCT can be used to apply basic configurations toNEs in different networking scenarios to complete batch NE deployment.U2000 operators can use the IP LCT or UniSTAR for network planning. The plug-and-playfunction can be implemented after a planning list is imported to the IP LCT.

System FunctionsThis topic describes the functions of the IP LCT.

System-defined TemplateConfiguration templates are defined in the system for IPRAN scenarios. You can select a desiredtemplate and set a few parameters to generate a script.

Remote CommissioningThe IP LCT supports two remote commissioning methods:l Remote commissioning using DCN: An NE automatically negotiates a route using a routing

protocol after it is powered on. The U2000 connects to the NE through the gateway NE byTelnet and applies basic configurations to the NE.

l Remote commissioning using DHCP:The IP LCT integrates with a DHCP server. After an NE is powered on, it exchanges DHCPpackets with the IP LCT through the upstream NE and obtains an IP address. The IP LCTapplies basic configurations to the NE.

Interconnection to the UnistarThe .xls file generated by exporting the network information that network planning engineersplan in the Unistar can be imported to the IP LCT to generate link planning and NE information.

Offline Script VerificationThe IP LCT allows you to modify scripts in offline mode. The IP LCT automatically verifiesgenerated scripts and displays verification results in different colors to ensure that allconfigurations are compliant with command line standards. This function supports onlycommand syntax check, rather than service logic check.

Quick Template GenerationScripts can be used to generate templates in one-click mode, facilitating the similar configurationin subsequent operations.

Basic ConceptsThis topic describes the basic concepts related to the IP LCT.

DHCPDHCP is a technology used to dynamically manage and configure users in a centralized manner.



12

DHCP adopts the C/S communication mode, in which the DHCP client sends the configurationrequest (requesting for the IP address, subnet mask, or default gateway) to the DHCP server,and the DHCP server returns the corresponding configuration according to the predefined policy.

DHCP ServerThe DHCP server is responsible for assigning IP addresses to DHCP clients. After a DHCPclient sends a configuration-requesting packet (requesting for the IP address, subnet mask, ordefault gateway) to the DHCP server, the DHCP server returns a packet carrying the requestedconfiguration according to the predefined policy. The request and reply packets are bothencapsulated with UDP.

DHCP RelayDHCP relay is introduced to transmit packets between the DHCP client and DHCP server thatare on different network segments. The DHCP relay agent can transparently transmit DHCPbroadcast packets between the DHCP client and DHCP server that are on different networksegments.In the actual network environment, the DHCP relay function is generally implemented on aspecific interface of a router. You need to configure an IP relay address on this interface tospecify the DHCP server.The IP relay address refers to the IP address of the DHCP server specified on the DHCP relayagent. After the DHCP relay function is configured on an interface, the DHCP broadcast packetsreceived on this interface are sent to the specified DHCP server.

Upstream NENE role relationships should be described in the IP LCT link planning table according to theorder for making NEs online. If an NE at one end of a link is planned to go online earlier thanthe other end, this NE can be regarded as the upstream NE.

The preceding figure shows that ASG3 and ASG4 are the NEs that have been made online onthe network. CSG1 and CSG2 are the plug-and-play NEs to go online. All the NEs are planned



13

to go online in the following time order: ASG3 -> CSG1 -> CSG2 -> ASG4. Port configurationis also implemented in the same order. In this case, CSG1 is the upstream NE for CSG2. If theNEs go online in the order of ASG4 -> CSG2 -> CSG1 -> ASG3, CSG2 is the upstream NE forCSG1.Note that specifying ASGs as upstream NEs is recommended in any cases. In the precedingorder examples, ASG4 is the upstream NE for CSG2 and ASG3 is the upstream NE for CSG1.NEs deployed at both ends of a link between ASGs, ASGs and RSGs, and RSGs can act asupstream NEs.The upstream NE concept indicating the relationship between NEs on the same link is used forfilling the planning table and implementing remote commissioning only. It is not an absoluteconcept. The relationship between a pair of NEs can be exchanged by changing the upstreamand downstream NEs' functions during remote commissioning. The upstream NE in this scenariois irrelevant to the upstream NE for services.

IP LCT Window OverviewThis topic describes the main window on the IP LCT, helping to find navigation paths quicklyand increase operation efficiency.

Main WindowThis topic describes main window components of the IP LCT as well as the functions of eachcomponent.



14

Deployment Overview Elements

1. Main menu: The main menu options for the IP LCT are: Deployment Configuration,

Script Management, Template Management, System Management, and Help.2. Global information: The global information includes the networking scenarios and NE

information for sites.3. Process: The whole process ranges from network planning to service configuration

deployment.

Shortcut IconsThis topic describes the functions of shortcut icons used for the configuration of scripts ortemplates.

Icon Name FunctionShortcut icons for script configuration



15

Icon Name FunctionModify Locks a script and synchronizes the script information.

If you click this shortcut icon when modifying a script, onlythe current client can be used to modify the script and otherclients are locked. This prevents concurrent operations bymultiple clients.

Save Saves script information.A script can be verified, deployed, or converted to a templateonly after the script is saved. In a saved script, the informationis displayed in colors. If an incorrect command is entered, theentire line of the command is displayed in red.

Find/Replace Finds and replaces script information matching the specifiedkeyword.

Previous Error Locates the previous incorrect command line in the currentscript.

Next Error Locates the next incorrect command line in the current script.

Deploy Deploys a script to an NE.Verify Script Verifies whether the script information is syntactically correct

and displays the verification result. The commands withVerification Result being Failure are displayed in red. Forthe incomplete commands with Verification Result beingFuzzy match, reference commands are displayed for the userto enter a complete commands.

GenerateTemplate

Converts script information to a template to facilitate thesimilar configuration in subsequent operations.

Query Queries the commands related to a command keyword enteredin the query box.NOTEl A maximum of 200 commands (the first 200 commands) related

to the specified command keyword can be displayed.l When querying commands, you can enter only a command

keyword, not command parameters.

Shortcut icons for template configurationNOTEl indicates a predefined template. Predefined templates do not support command modification.

l indicates a custom project template.

Copy Copies a command or view selected from the current templateor another template.

Paste Pastes the copied command or view to a new location.



16

Icon Name FunctionUp Moves the selected command/view and its subnodes upwards.

Down Moves the selected command/view and its subnodesdownwards.

Insert Inserts a command into a template.

Delete Deletes the selected command from a template.ModifyDescription

Updates the description about a command.

ModifyCommand

Modifies the selected command.

Mark Parameter Associates parameters in a template with extended parameters.

Apply Applies the current template to an NE for script generation.Save Saves template information.Save as Saves the current settings as a new template.Restore Defaults Restores the commands and parameter values in the system-

defined template to their default status.NOTE

Only the system-defined template can be restored to its default status.

Expand Expands all commands under the selected node.Collapse Collapses all commands under the selected node.Search Searches for commands in the template based on the

configuration item, default value, reference command, orparameter mark and locates the specific position.

DHCP Alarm NotificationThis topic describes the icons and meanings of Dynamic Host Configuration Protocol (DHCP)alarm notifications. If deployment configuration is used to add an NE and the DHCP serverreceives a packet that does not match NE planning information, an alarm notification is displayedin the graphical user interface (GUI).

Icon Name DescriptionAbnormalpackets of theDHCP server

Total number of abnormal packets among packetsexchanged between the DHCP server and clientsduring NE discovery.To view details about the abnormal packets, click thisbutton.



17

Icon Name DescriptionOnline A management channel has been established between

the IP LCT and the new NE. The IP LCT has deployedbasic configurations to the new NE.

Already onlineBasicconfigurationdeploymentfailure

A management channel has been established betweenthe IP LCT and the new NE.The basic configuration script has errors and failed tobe deployed.

Offline After the NE goes online, the communication betweenthe IP LCT and the NE is interrupted becauseconfigurations of the NE or network are changed.

To be online Initial status of the NE. The NE has not been establishan connection to the IP LCT.

1.3.2 IP LCT Operation TasksThis topic describes how to configure NEs in typical scenarios where the IP LCT is used.

Setting a Network ScenarioConfigure a service scenario used for the live network and set global parameters.

ProcedureStep 1 Log in to the U2000 client.Step 2 Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play

Management from the main menu.The U2000 IP Plug-and-Play Management window is displayed.Enter a user name and a password for logging in to the U2000 and click Login.

Step 3 On the Deployment Overview tab, click Set a Network Scenario.Step 4 In the Set a Network Scenario dialog box, select a service scenario.Step 5 Click OK.Step 6 Optional: Choose System Management > Set Global Options from the main menu. In the

dialog box that is displayed, click the Options for Remote Commissioning tab and set remotecommissioning parameters.



18

Table 1-4 Parameter descriptionParameter DescriptionDeploy ASG NE's access ringscript automatically whenCSG NE belongs to it is gettingonline

If the check box is selected, the IP LCT applies basic access-side configurations to aggregation site gateways (ASGs)after cell site gateways (CSGs) go online. The check boxneeds to be selected when ASGs do not have basicconfigurations.By default, this check box is selected.

Deploy ASG NE's Peer scriptautomatically when CSG NEbelongs to it is getting online

If the check box is selected, the IP LCT applies BorderGateway Protocol (BGP) peer configurations to ASGs afterCSGs go online.By default, this check box is selected.

DHCP OptionsDeploy Script Automatically If this check box is selected, the IP LCT applies a script after

establishing a management channel with an NE by meansof plug-and-play.If this check box is not selected, you can apply scriptsmanually.By default, this check box is selected.



19

Parameter DescriptionEnable Relay Automatically The prerequisite for using plug-and-play to create an NE is

to enable Dynamic Host Configuration Protocol (DHCP)relay for the interface on the upstream NE.If this check box is selected, the IP LCT enables DHCP relayfor the interface on the upstream NE based on planninginformation about the new NE.NOTE

If the upstream NE is a third-party NE, DHCP relay cannot beautomatically enabled.

By default, this check box is selected.Disable Relay Automatically If this check box is selected, DHCP relay is automatically

disabled for the upstream NE after the IP LCT assigns an IPaddress to and configures a default route for the new NE.NOTE

If multiple new NEs are connected to the upstream NE, do not selectthis check box. Otherwise, DHCP relay is disabled for the upstreamNE and other NEs cannot communicate with the IP LCT usingDHCP after one of the new NEs is connected to the IP LCT.

By default, this check box is selected.Remove Default PnP RouteConfiguration Automatically

During the process of using plug-and-play to create an NE,a default route destined for the IP LCT is configured for thenew NE.If this check box is selected, the IP LCT deletes this defaultroute after a script is applied to the new NE.By default, this check box is not selected.

No check for Interfaces ofUplink NEs (available whenESN is configured)

The IP LCT matches information in a DHCP packet sent bya new NE with information in the NE planning table. If theinformation is the same, the IP LCT assigns an IP addressto the new NE.If this check box is selected and some NE information doesmatch, the IP LCT continues matching the equipment serialnumbers (ESN) in the DHCP packet and NE planning table.If the ESNs are the same, the IP LCT ignores the mismatchinformation and assigns an IP address to the new NE.By default, this check box is not selected.

Synchronize Uplink NEsysname Automatically

If the sysname for the upstream NE is different from that inthe planning table, the IP LCT changes the sysname in theplanning table to the one for the upstream NE.By default, this check box is not selected.

Update Relay Interface IPAddresses of Uplink NEAutomatically

If this check box is selected, the IP LCT updates the IPaddress of the relay interface on the upstream NE after ascript is applies to a new NE.By default, this check box is not selected.



20

Parameter DescriptionRoute Isolation If the route between the IP LCT and the management IP

address of the DHCP relay agent, not the relay interface, isreachable, you can select this check box to forward DHCPpackets from the management IP address to the IP addressof the relay interface.By default, this check box is not selected.

Step 7 Optional: On the Extend Script Settings tab, set related parameters and click OK.

Table 1-5 Parameter descriptionName DescriptionMerge Extend Script toBasic Configuration ScriptAutomatically

If this check box is selected, the extended script generated usingthe extended template selected when the planning table isexported is automatically integrated into the basicconfiguration script.By default, this check box is selected.

Sort DCN Configuration byRing Automatically

If this check box is selected, the query result is sorted by ringwhen you view the data communication network (DCN) linklist.NOTE

Navigation path for viewing the DCN link list: Choose DataPlanning > DCN Planning from the navigation tree on the AutomaticNE Configuration tab.

By default, this check box is not selected.

Step 8 Click OK.----End

Setting a DCN TypeSelect a DCN type which can be public or private DCN.

ContextA DCN type needs to be set only when NEs get online in DCN mode, but not DHCP mode.


Management from the main menu.The U2000 IP Plug-and-Play Management window is displayed.



21

Enter a user name and a password for logging in to the U2000 and click Login.Step 3 In the Deployment Overview area, click Set DCN Type.Step 4 On the DCN Mode Settings dialog box, select a DCN deployment mode.

l DCN Public Mode: The management packets between the U2000 and NEs are forwardedusing the service route.

l DCN Private Mode: The management packets between the U2000 and NEs are forwardedusing an independent private IGP route. The route is logically isolated from the service route. Local VRF: All NEs are bound to the same VRF to establish private management channels

for packet transmission. DCN VPN: Private management channels provided at delivery are used to transmit

packets. All NEs must support the DCN management function.Step 5 Click OK.

----End

Customizing TemplatesThis topic describes how to use the IP LCT to customize a basic NE configuration template anda BGP peer configuration template.

Creating a Site-specific TemplateTo create a site-specific template, select the desired basic configuration template based on thenetwork scenario and NE role, modify the template, and set template parameters, and save thesettings.

Contextl Available network scenarios are hierarchy virtual private network (HVPN), L2+L3,

Gateway, multiprotocol label switching transport profile (MPLS-TP), and Native IP. Oneof the network scenarios is deployed at an IP radio access network (IPRAN) site.

l Available NE roles are aggregation site gateway (ASG), cell site gateway (CSG), radioservice gateway (RSG), ACCESS-P and AGG-P. If multiple NE roles need to be deployedat a site, create multiple site-specific templates. The procedure for creating a basicconfiguration template for ASGs is used as an example.

l The feature you have purchased may obtain or use some personal information of users whenproviding services or maintenance. Therefore, you are obliged to formulate a privacy policyaccording to the applicable law and take sufficient measures to keep the personalinformation secure.





22

Enter a user name and a password for logging in to the U2000 and click Login.Step 3 On the Deployment Overview tab, click Customize a Template.Step 4 Click Create Basic Configuration Template if it is the first time you use Customize a

Template.If a site-specific template has been created, click Modify Basic Configuration Template.A site-specific template can be modified as needed. For example, you can insert commands intoor delete commands from the template, or make extended marks on parameters.For details about how to modify a template, see Modifying a Template.

Step 5 In the dialog box that is displayed, select a network scenario and an NE role, set an IP addressfor the master server of the U2000, and click Next.

NOTEYou can select multiple NE roles in this step and set template parameters in follow-up steps.

Step 6 Enter a template name and set required parameters.NOTE

l If multiple NE roles have been selected, click associated NE tabs and set template parameters.l The basic configuration template includes basic NE configurations, such as basic NE information, and

authentication, authorization and accounting (AAA) user, global MPLS, Interior Gateway Protocol(IGP), loopback interface, ring interface, and Simple Network Management Protocol (SNMP)configurations.



23

Step 7 Modify the basic configuration template based on service planning.

1. Click Show Detail.2. Click to expand the template. Select desired check boxes based on service planning to

choose configurations to be applied to NEs.To delete unwanted configurations, click .

3. Set or modify values in the Default Value column. The parameters for which the DefaultValue column are marked yellow are mandatory.

4. Optional: Select the Show Parameter check box. In the template, select the desiredparameter and click . In the dialog box that is displayed, select an extended parameterand click OK.



24

You can select an extended parameter predefined in the template or create an extendedparameter as needed.a. In the Select Parameter dialog box, click Create Parameter.b. In the dialog box that is displayed, enter the parameter ID, name, type, and description,

and click OK.

Step 8 Click Finish.----End

Creating Peer Configuration TemplatesThis topic describes how to create BGP peer configuration templates for different NEs.

Contextl The basic configuration template does not contain BGP peer configuration commands.

Therefore, BGP peer configuration templates must be created to deploy BGP peerconfigurations.

l The feature you have purchased may obtain or use some personal information of users whenproviding services or maintenance. Therefore, you are obliged to formulate a privacy policyaccording to the applicable law and take sufficient measures to keep the personalinformation secure.



Step 3 Click Custom Template Design in the Deployment Overview area.Step 4 Click Create New Peer Template.

If a peer configuration template has been created, click Modify Peer Template.



25

A peer configuration template can be modified as needed. For example, you can insert commandsinto or delete commands from the template, or make extended marks on parameters.

Step 5 In the dialog box that is displayed, select route reflector type and desired peer configurationtemplate type, enter the local AS number.

NOTE

l The available options of Route Reflector (RR) Type are Independent RR, RSG As RR, and WithoutRR.

l If a global AS number is available, enter this AS number. Alternatively, enter AS numbers for eachBGP peer configuration template at the next step.

Step 6 Optional: Configure default peer rules.This step is required only for an HVPN service scenario.1. Click Set Peer Default Rule.2. In the dialog box that is displayed, configure automatic peer generation rules for the access

and aggregation sides.3. Click OK.

Step 7 Click Next.Step 8 Set Template name, AS Number, and BGP Group Name for each peer configuration template.Step 9 Optional: Modify the peer configuration templates based on service planning.

1. Click Show Detail.2. Click to expand the template. Select desired check boxes based on service planning to

choose configurations to be applied to NEs.To delete unwanted configurations, click .

3. Set or modify values in the Default Value column. The parameters for which the DefaultValue column are marked yellow are mandatory.

4. Optional: Select the Show Parameter check box. In the template, select the desiredparameter and click . In the dialog box that is displayed, select an extended parameterand click OK.You can select an extended parameter predefined in the template or create an extendedparameter as needed.a. In the Select Parameter dialog box, click Create Parameter.b. In the dialog box that is displayed, enter the parameter ID, name, type, and description,

and click OK.



26

Step 10 Click Finish.----End

Planning DataPlan link data, data communication network (DCN) data, and Border Gateway Protocol (BGP)peer relationships.

PrerequisitesA project template has been configured.



Step 3 Optional: Plan IP address pools.Step 4 Export the link planning template.

1. On the Deployment Overview tab, click Plan Data.2. Click Export the link excel planning template and then design it.3. In the dialog box that is displayed, click Export Link Planning Table.

To apply configurations except the basic configuration template, click Choose ExtendTemplate. To configure a routing policy and a clock priority, select an extended template.In the dialog box that is displayed, select the extended template to be applied and clickOK.

4. In the dialog box that is displayed, click Save File.5. Click OK.6. Select a path for saving the link planning table, enter the planning table name, and click

Save.



27

7. Open the link planning table and enter link planning information based on Note.The parameters marked with asterisks (*) on each sheet are mandatory.

Table 1-6 Description of sheets in the link planning tableSheet DescriptionNetworkLayout An upstream NE is specified for each NE based on networking

conditions. This sheet needs to be filled in with NE Information, suchas the sysname, NE role, interface name, and interface IP addresses.MandatoryNOTE

If the NE script needs to be exported or merged in the future, the NE sysnameand ring name cannot contain special characters \ / : * ? < > |.

Aggregate_NE_INFO

This sheet needs to be filled in with aggregation NE information isentered to specify master/slave relationships between aggregationsite gateways (ASGs).Mandatory

DCN_Layout This sheet needs to be filled in with DCN information.Optional

Trunk If interfaces on an upstream NE are trunk interfaces, this sheet needsto be filled in to differentiate the interfaces from physical interfacesconnected to new NEs.Optional

Vlanif If interfaces on an upstream NE are VLANIF interfaces, this sheetneeds to be filled in to differentiate the interfaces from physicalinterfaces connected to new NEs.Optional

Template_List This sheet contains the list of extended planning templates. It isgenerated only after you select extended planning templates whenexporting the planning table.Optional

Other_Configuration

This sheet contains mandatory parameters in extended planningtemplates.Optional

8. Click Save.

Step 5 Import the link planning table.1. On the Deployment Overview tab, click Plan Data.2. Click Import Link Plan.3. In the dialog box that is displayed, click Browse and select the planning table that has been

filled in.



28

4. Click Open.5. Click Next.

If the selected planning table is not exported from the IP LCT or UniSTAR, specify themappings for each field in the planning table.

6. In the Configuration Rules for Link Planning area, select the Automatic

configuration check box and click Configure. In the dialog box that is displayed, set thelabel switching router (LSR) ID network segment, IP network segment, and access interfaceparameters.

NOTEIf the LSR ID and the IP address of the interconnected interface have been entered in the planningtable, clear the Automatic configuration check box.

7. In the DCN Mode area, set DCN Mode and IGP Type.8. Optional: In the DCN Address Pool Planning area, select the Automatic

configuration check box and click Advanced. In the dialog box that is displayed, plan theDCN address pool.



29

NOTE

l DCN Address Pool Planning needs to be set only when DCN Mode is set to Private (localVRF in private DCN mode).

l If DCN Mode is set to Local VRF, Management Channel Name must be set.9. Click OK.10. Click Next. In the dialog box that is displayed, click OK.11. In the dialog box that is displayed, select a template for each NE and click Next.12. On the Select Peer Template tab, modify the peer configuration templates mapping to the

NEs based on site conditions, and click Finish.Step 6 Optional: Plan peer relationships.

If peer relationships are not generated using default rules, manually create peer relationshipsbased on planning information.

Step 7 View configuration scripts.1. On the Deployment Overview tab, click Plan Data.2. Click View Scripts.

The desired NEs are displayed under NE List in the navigation tree, and the scripts to beapplied to these NEs are available under these NEs.

3. Ensure that configurations in each script are the same as those planned.The scripts are automatically generated based on project templates and planning tables andcannot be manually modified. To adjust configurations in a script, modify the template orplanning table and re-import the planning table.

----End

Result1. Click the Automatic NE Configuration tab.2. After you choose Configuration Data > Link Planning from the navigation tree, you can

find that the information has been imported from the planning table to the IP LCT.



30

Example

Figure 1-2 Network topology example

Figure 1-3 Interface planning example

The examples of filling in link planning tables in four typical interface scenarios are as follows:l Scenario in which interfaces are connected, with the link between CSG1 and CSG2 as an

example



31

Figure 1-4 Example of filling in the NetworkLayout sheet

NOTE

l gi is short for gigabitethernet.l The IP addresses and names (marked red) of interfaces on the local and upstream NEs are

consistent with those in the figure.l Scenario in which subinterfaces are connected, with the link between ASG3 and ASG4 as

an example


NOTE

l gi is short for gigabitethernet.l The Link VLAN field must be set.l The IP addresses and names (marked red) of interfaces on the local and upstream NEs are

consistent with those in the figure.l Scenario in which trunk interfaces are connected, with the link between RSG5 and RSG6

as an example


Figure 1-7 Example of filling in the Trunk sheet



32

NOTE

l gi is short for gigabitethernet.l The Link VLAN field must be set.l The Information about member interfaces must be entered in the Trunk sheet.l The IP addresses and names (marked red) of interfaces on the local and upstream NEs are

consistent with those in the figure.l Scenario in which virtual local area network (VLAN) interfaces are connected, with the

link between RSG5 and RSG6 as an example


Figure 1-9 Example of filling in the Trunk sheet

NOTE

l gi is short for gigabitethernet.l The Link VLAN field must be set.l The information about VLAN interfaces must be entered in the Vlanif sheet.l The IP addresses and names (marked red) of interfaces on the local and upstream NEs are

consistent with those in the figure.

Remote Commissioning in DCN ModeThis topic describes how to remotely commission the plug-and-play NEs in DCN mode.

Prerequisitesl The U2000 client has been started and is unlocked.l Gateway NEs have been managed by the U2000.l The gateway NEs are not third-party NEs.





33

Enter a user name and a password for logging in to the U2000 and click Login.Step 3 In the Deployment Overview area, click DCN Type.Step 4 Click Monitor NE Online Process.Step 5 In the dialog box that is displayed, click OK.

The DCN view is displayed on the U2000 client.

Step 6 Click , or right-click the Gateway NE Tree node in the navigation tree, and choose Set GateNE from the shortcut menu.

Step 7 In the dialog box that is displayed, click Add Gateway NE to select the desired gateway NEs.Select an NE IP address pool if the private DCN mode is used.

Step 8 Click Telnet Template to set Telnet or STelnet parameters. Click OK.NOTE

You are advised to use the more secure STelnet mode if this mode is supported.

After the operation succeeds, the added gateway NEs are displayed under the Gateway NETree node. The non-gateway NEs to go online are displayed in the DCN view in the right paneof the window. In this case, these NEs are dimmed.

Step 9 Power on the non-gateway NEs to go online.Step 10 Right-click in a blank area in the DCN view and choose Synchronize from the shortcut menu.

The DCN view can be updated by clicking . The non-gateway NEs have been online aftertheir colors are changed to blue or Status on the NE tab is displayed as Online.

Step 11 Select the online non-gateway NE, right-click, and choose Apply Basic Configuration fromthe shortcut menu.

Step 12 In the dialog box that is displayed, browse the scripts to be applied and click Apply.View associated logs after the scripts are applied. If some commands are failed to be applied,use Telnet or STelnet to log in to the NEs and re-apply these commands to the NEs.

NOTE

Views logs, you can search for logs by search forward, circle search, or case matching.

The colors of the non-gateway NEs in the DCN view are changed from blue to green after scriptsare successfully applied to them.----End

Remote Commissioning in DHCP ModeThis topic describes how to remotely commission the plug-and-play NEs in DHCP mode.

Set Telnet Parameters for Upstream NEsThis topic describes how to set Telnet or STelnet parameters for upstream NEs.

PrerequisitesThe upstream NEs have been managed by the U2000.



34

ContextConfigurations must be applied to the upstream NEs during remote commissioning. Therefore,the Telnet or STelnet parameters must be configured for these NEs in advance.



Step 3 In the Deployment Overview area, click DHCP Type.Step 4 Click Conf

Documents

ATN 910&910I&910B&950B V200R003C10 Configuration Guide 01(U2000)