Atn 905
Atn 905
Access Equipment
V200R005C00
Commissioning Guide
Issue 03
Date 2015-08-31
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: [email protected]
Purpose
This manual describes commissioning of U2000 for ATN.
Related Versions
The following table lists the product versions related to this document.
Intended Audience
This document is intended for:
l commissioning engineers
Symbol Conventions
Symbol Description
Command Conventions
Convention Description
GUI Conventions
Convention Description
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Contents
1 IP Network Commissioning
Before service configuration and network maintenance, you must complete IP network
commissioning to ensure normal NE management on the U2000.
Configure the
Create NEs in Configure NE time
Telnet/Stelnet
batches synchronization
Template (V5)
Configure the
Netconf template Select a layout mode
(V8)
Check xFTP
configurations
Configure the NE time. The NE time must be If the time zone is not
configured before service correctly set, the alarm
configuration so that the NE generation time displayed on
time on the U2000 is the U2000 is different from
consistent with that on NEs, the actual alarm generation
which is of vital importance time.
to fault locating and network
monitoring.
Prerequisites
l SNMP parameters have been configured on NEs. For details, see the chapter NE
Interconnection in the NE commissioning guide.
l Telnet/STelent parameters must be configured on NEs.
l FTP and NETCONF parameters must be set on NEs running VRPv8. In addition, ensure
that the first-time authentication on the SSH client function has been enabled by running
the ssh client first-time enable command on the NE side.
Context
NOTICE
Modifying communication parameters may disconnect the U2000 from NEs. Therefore, modify
them based on your site plan.
l The protocol parameters on the U2000 must be the same as those on NEs.
l Precautions on SNMP configuration
– To ensure that the U2000 can properly collect service performance data, the U2000
must use SNMPv2c or SNMPv3 to communicate with NEs. SNMPv3 is more secure
than SNMPv2c; therefore, SNMPv3 is recommended.
– If multiple RM9000 NEs need to be added in batches, the SNMPv2c parameters must
be set, and the values of these parameter must be fixed. For example, Template
Name must be set to rm, Read Community Name and Write Community Name must
be set to v2cUser, and NE Port must be set to 8000.
– If the Simple Network Management Protocol version 3 (SNMPv3) is used, plan NE
communication parameters in a unified manner. Group NEs and ensure that NEs within
the same group use the same communication parameters and different NE groups use
different user names. The communication parameters include the user name, private
protocol, encryption password, authentication protocol, and authentication password.
l Precautions on Telnet/STelnet configuration
– STelnet is more secure than Telnet; therefore, STelnet is recommended.
l Precautions on xFTP configuration
– The newly installed U2000 automatically completes the configuration for the xFTP
information after being successfully started. You cannot modify the default xFTP
configuration unless otherwise specified.
Procedure
Step 1 Configure SNMP parameters.
1. Choose Administration > NE Communicate Parameter > Default Access Protocol
Parameters from the main menu (traditional style); alternatively, double-click Fix-
Network NE Configuration in Application Center and choose Administration > NE
Communicate Parameter > Default Access Protocol Parameters from the main menu
(application style).
2. In the Default Access Protocol Parameters dialog box, click the related tab to switch to
the page for configuring protocol parameters. The following figure shows how to set
SNMPv3 parameters.
3. Click Add.
4. Set parameters, such as Template Name and NE User.
1. Choose Administration > Settings > FTP Account Information Management from the
main menu (traditional style); alternatively, double-click System Management in
Application Center and choose Settings > FTP Account Information Management
from the main menu (application style).
2. In the FTP Account Information Management dialog box, click the Configure FTP
Account tab.
3. On the Configure FTP Account tab, choose Default local FTP account, right-click and
choose Test.
4. In the dialog box that is displayed, click Test FTP or Test SFTP to test the FTP or SFTP
function of the FTP server.
NOTE
----End
Context
Subnets are used to simplify the topology view without impact on NEs.
Procedure
Step 1 Choose View > Main Topology from the main menu (traditional style); alternatively, double-
click Topo View in Application Center (application style).
Step 2 Select a type of view from the Current View drop-down list.
Step 3 In the Topology, right-click in a blank area and choose New > Subnet from the shortcut menu.
Step 4 In the dialog box that is displayed, click the Property tab and set Name, Alias, Parent
Subnet, Coordinate, and Remarks.
----End
Prerequisites
l Ensure that access protocol parameter templates must be the same on the U2000 and NEs.
For details, see 1.2 Configuring the Communication Between the U2000 and NEs.
l Ensure that the IP address and MAC address used for creating an NE cannot be the same
as an existing IP address and MAC address.
Context
The way a VRPv8-based NE or NE5000E cluster is added to the U2000 is similar to that a router
or switch is created on the U2000. Note the followings when adding a VRPv8-based NE:
l Configure NETCONF on the U2000 and NEs before NE adding. For details, see 1.2
Configuring the Communication Between the U2000 and NEs.
l Select NETCONF as the protocol used in VRPv8 NE adding.
Procedure
Step 1 Choose File > Discovery > NE from the main menu (traditional style); alternatively, double-
click Topo View in Application Center and choose File > Discovery > NE from the main menu
(application style).
Step 2 In the dialog box that is displayed, set the related parameters.
NE Type Click .... In the dialog box that is displayed, select the type of the
NE to be discovered.
Ping Times If multiple NEs need to be searched for or the network quality is
poor, set Ping Times to 3 or a larger value. Otherwise, some NEs
may fail to be searched out.
Layers l 0: specifies that the U2000 searches for only the NEs with the
IP addresses within a specified IP network segment.
l 1: specifies that when routers exist on a specified IP network
segment, the U2000 searches for not only the NEs with the IP
addresses within the IP network segment but also the NEs
directly connected to the routers.
l 2, 3: specifies that the U2000 searches for not only the NEs with
the IP addresses within a specified IP network segment but also
the NEs connected to the Layer 2 or Layer 3 routers.
Default SNMP Click Default SNMP Parameter to set SNMP parameters to the
Parameter same values as those on NEs
NOTE
When creating NEs in batches, you can delete unused SNMP parameter
templates to improve the search efficiency.
Automatically create If you select the Automatically create NEs check box, NEs are
NEs created automatically in the physical root after a successful search
on the U2000.
NOTE
If you clear the Automatically create NEs check box, NEs are created
manually after a successful search. In the NE Data area, select the NE to
be created and click Create to add the NE to the physical topology.
IP Address Range click Add and the dialog box is displayed. Set Start IP Address,
End IP Address, and Subnet Mask.
Step 3 Click Next. The U2000 begins to search for NEs. The U2000 automatically creates NEs after
finding NEs that meet the search criteria.
----End
Procedure
Step 1 Double-click in the Main Topology to access the subnet. Right-click and choose Set Layout
from the shortcut menu.
----End
Prerequisites
LLDP has been enabled on NEs and ports.
Procedure
Step 1 Choose File > Discovery > Link from the main menu (traditional style); alternatively, double-
click Topo View in Application Center and choose File > Discovery > Link from the main
menu (application style).
Step 2 Choose to select Do you want to synchronize LLDP data on the equipment? above the object
list.
Step 3 Select one or more NEs or subnets from the list on the left and click .
Step 4 Optional: In the LLDP Status Management dialog box, perform the following operations:
1. Set LLDP Status to Open and click OK.
NOTE
If LLDP has been enabled for NEs, links will be automatically created when NEs are being searched.
LLDP needs to be enabled because it is disabled by default.
2. Click OK when the Warning dialog box is displayed indicating that the LLDP protocol
on the NE will be enabled.
3. A dialog box is displayed indicating that the operation is successful. Click Close.
4. 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 is displayed indicating
the search progress.
Step 5 After the search is complete, a dialog box is displayed indicating that the operation is successful.
Click Close. Link search results are displayed.
Step 6 In the dialog box that is displayed, select one or more links with Status set to Not exist. Then
click Create.
NOTICE
An interface cannot have a Layer 2 link and an IP link configured at the same time.
Step 8 The dialog box indicating Are you sure to import links as fibers/cables is displayed. Click
Yes. The Import Link dialog box is displayed.
Step 9 Select links and click to import all the link information to Selected Link. Click OK. The
U2000 then automatically creates fibers.
Step 10 Drag the NE icon to adjust the structure of the network topology.
----End
Procedure
Step 1 Choose Configuration > NE Batch Configuration > NE Time Localization Management
from the main menu (traditional style); alternatively, double-click Fix-Network NE
Configuration in Application Center and choose Configuration > NE Batch
Configuration > NE Time Localization Management from the main menu (application style).
Step 2 Select NEs from the list on the left and click .
Step 4 Click Time Zone and select a time zone from the drop-down list.
Step 8 Click OK when the Warning dialog box is displayed indicating that the time zone and DST on
the NE will be modified.
A progress bar is displayed to show the modification progress.
Step 9 A dialog box is displayed indicating that the operation is successful. Click Close.
----End
Procedure
Step 1 Refer to the following operations to synchronize the NE time.
If... Then...
Synchronize the NE time between NEs and the U2000 in batches. Refer to Steps 2 to 7.
If... Then...
Synchronize the NE time between NEs and the NTP server in Refer to Steps 8 to 16.
batches.
Step 2 Choose Configuration > NE Batch Configuration > NE Time Synchronization from the main
menu (traditional style); alternatively, double-click Fix-Network NE Configuration in
Application Center and choose Configuration > NE Batch Configuration > NE Time
Synchronization from the main menu (application style).
Step 3 In the Object Tree, select one or more NEs and click .
Step 5 Synchronize the NE time with the U2000 time, which can be performed either automatically or
manually based on actual situations.
l If both the U2000 and NE have no NTP service configured, automatically synchronize the
NE time with the U2000 time. Select a desired NE, right-click the Synchronous Mode
column, and choose NM from the shortcut menu. Then click Apply. In the dialog box that
is displayed, click Yes and set Start Time and Period.
l If only the NE has no NTP service configured, manually synchronize the NE time with the
U2000 time. Select a desired NE and click Synchronize with NM Time. Alternatively, select
a desired NE, right-click, and choose Synchronize with NM Time from the shortcut menu.
In the dialog box that is displayed, click Yes.
Step 7 A dialog box is displayed indicating that the operation is successful, Click Close.
Step 8 Choose Configuration > NE Batch Configuration > IP Network NTP from the main menu
(traditional style); alternatively, double-click Fix-Network NE Configuration in Application
Center and choose Configuration > NE Batch Configuration > IP Network NTP from the
main menu (application style).
Step 9 In the Object Tree, select one or more NEs and click .
Step 10 In the right-hand status query window, select the NE and click Configure.
NOTE
Either a single NE or multiple NEs can be selected for NTP configuration.
Step 11 Optional: On the Work Mode tab page, set the clock stratum for an NTP client.
The clock stratum ranges from 1 to 15. The smaller the clock stratum is, the higher the clock
precision is. An NTP client automatically synchronizes its clock with an NTP server that has a
smaller clock stratum. If multiple NTP servers are available, the NTP server with the smallest
clock stratum is selected for clock synchronization.
To prevent other interfaces on the NE from receiving NTP messages, specify that all NTP
messages sent by the NE use the same interface as the source interface.
After a VPN instance is configured, routing information about NTP messages can be located in
the relevant VRF table.
Step 14 Click Create. In the Create Client/Server Work Mode dialog box, configure clock source
information for the NE.
3. Optional: To enable the NTP authentication function, select the authentication key ID. The
authentication key ID can be selected only after being created on the Advanced
Information tab page.
4. Optional: Configure the source interface that the NE uses to exchange NTP packets with
the clock source.
5. Optional: Configure the VPN instance that the NE uses to synchronize time with the clock
source.
6. Optional: Configure whether the clock source information is selected by precedence.
7. Click OK to complete NTP client/server configuration.
NOTE
Multiple NTP servers can be configured for an NE. An NTP client compares clock strata of these NTP
servers and selects the NTP server with the smallest stratum as the clock source. If the clock strata of the
NTP servers are the same, the NTP client selects the server for the Preference check box is selected as the
master clock source and uses the other NTP servers as backup clock sources.
NOTICE
On networks that have high requirements on security, the verification function can be enabled
when NTP is running so that validity verification can be performed on received packets. This
configuration improves the security.
1. Click the Advanced Information tab and select the Enable NTP Authentication check
box to enable the NTP authentication function.
NOTE
The NTP authentication function takes effect only after the Enable NTP Authentication check box
is selected.
2. Click Create and create an NTP authentication rule.
NOTE
If the keys configured on NTP servers are different, the same keys must also be configured on the
client and Reliable Authentication Key is used to determine whether to enable the keys.
Step 16 Click OK to complete the configuration of the NTP authentication function and apply the settings
to the NE.
----End
Context
Network Address Translation (NAT) helps ease IP address insufficiency and facilitates address
planning inside a network. It hides computers inside a network and protects them against attacks
outside the network.
The following figure shows a network with NAT between the U2000 server and NEs. When NE
1 and NE 2 report traps or initiate xFTP service requests to the U2000 server, the traps or requests
are converted via NAT to the U2000 server IP3 address.
Procedure
Step 1 Choose Administration > Settings > NAT Configuration Management from the main menu
(traditional style); alternatively, double-click System Management in Application Center and
choose Settings > NAT Configuration Management from the main menu (application style).
l High availability system networking: An example assumes that the IP address of the primary
site is 172.16.0.1 and that of the secondary site is 172.16.0.2. The IP address of the primary
site changes to 10.168.23.25 and the IP address of the secondary site changes to 10.168.23.26
after NAT translation by the firewall. NEs are located on network segment 10. To ensure the
normal communication between the U2000 server and NEs, complete the NAT configuration
on the primary site as follows:
l High availability system networking (the U2000 server uses the dual-NIC IPMP solution):
On the primary site, an example assumes that the IP address of NIC 1 is 172.16.10.1, the IP
address of NIC 2 is 172.16.10.2, and the system IP address is 10.168.23.3. On the secondary
site, the IP address of NIC 1 is 172.16.10.11, the IP address of NIC 2 is 172.16.10.12, and
the system IP address is 10.168.23.13. Some devices are located on network segment 10,
some other devices are located on network segment 172. The devices on the two network
segments can access the system IP address of the U2000 server. Configure the IP address for
NAT configuration management on the primary site as follows:
----End
Prerequisites
The parameters for the communication between the U2000 and NEs are correct.
Background
If full synchronization is not performed, synchronization is not successfully performed due to
an FTP failure, or only some entity or interface data is automatically synchronized, an S-marked
icon, is displayed in the upper left corner of an NE that is added to the U2000 for the first time.
If full synchronization has ever been successfully performed for an initial NE, the S-marked
icon will not appear even when synchronization fails in the future. If only some of the features
are selected during manual synchronization and then successfully synchronized, the system
considers the synchronization as successful full synchronization, and the S-marked icon will not
appear.
NOTICE
NE data must be synchronous with U2000 data. If the data is not synchronous, the management
IP address, LSR ID, and link IP address of the NE may conflict with each other, causing an NE
management failure on the U2000. In the case of an address conflict, click Deployment
Configuration > Data Planning > NE Information for modification.
Procedure
l Navigation path 1: Choose View > Main Topology from the main menu (traditional style);
alternatively, double-click Topo View in Application Center (application style). In
Physical Root, select the NE to be operated, right-click, and choose Synchronize NE
Configuration Data from the shortcut menu.
l Navigation path 2: Choose Configuration > Synchronize NE Configuration Data from
the main menu (traditional style); alternatively, double-click Fix-Network NE
Configuration in Application Center and choose Configuration > Synchronize NE
Configuration Data from the main menu (application style). In the window that is
displayed, select the NE to be synchronized and click Synchronize.
2.6 FAQ
System-defined Template
Configuration templates are defined in the system for IPRAN scenarios. You can select a desired
template and set a few parameters to generate a script.
Remote Commissioning
The plug-and-play management module supports two remote commissioning methods:
DCN Solution
The DCN solution is used to address on-site software commissioning issues during deployment.
The PPPOE, VPN, and OSPF technologies are used to achieve software commissioning without
going to sites.
NE ID
On a DCN, an NE is uniquely identified by an ID but not an IP address. This ID is called an NE
ID. Every device is assigned a default NE ID before delivery.
As the unique identities of NEs on a DCN, NE IDs must be different from each other. If the NE
IDs of two NEs on a DCN are identical, route flapping occurs.
NE IP
NE IP addresses are used for connecting terminals and network devices or for addressing on an
IP network between devices. Before NE IP addresses are manually configured, the NE IP
addresses must be associated with NE IDs and change with NE IDs. Once an NE IP address is
set, it does not change with an NE ID.
On a public DCN, NE IP addresses are used only when NEs get online. The default NE IP
addresses of the NEs are used. On a private DCN, NE IP addresses function as the device
management IP addresses to manage device identifications and routes. You must reconfigure
the NE IP addresses to ensure that the NE IP addresses can reach NMS routes.
DCN negotiation succeeds only when the core routing table contains required entries. OSPF is
automatically enabled on a device after it is started. The NE ID and NE IP address of the device
are encapsulated into the Opaque LSA packet. OSPF automatically floods Type 10 LSAs(LSA
Link State Advertisement) to form a core routing table within a DCN domain. When the NMS
located on the DCN uses gateway NEs to access non-gateway NEs, the NMS searches the core
routing table based on the destination NE ID and translates the destination NE ID to a destination
NE IP address and sends a UDP packet to the NE IP address. The UDP packets are addressed
based on the IP routing table.
DHCP
Dynamic Host Configuration Protocol (DHCP) is a technology used to dynamically manage and
configure users in a centralized manner.
DHCP uses the client (an NE)/server (the U2000 server) communication mode. A DHCP client
applies to a DHCP server for configurations, such as the IP address, subnet mask, and default
gateway. The DHCP server replies with configurations.
DHCP Server
A DHCP server assigns IP addresses to DHCP clients. After a DHCP client sends the DHCP
server a configuration request to apply for configurations (such as the IP address, subnet mask,
and default gateway), the DHCP server responds with a packet carrying the requested
configurations. Both the request and response packets are encapsulated as User Datagram
Protocol (UDP) packets.
DHCP Relay
DHCP relay is a function to implement the transmission of broadcast packets between a DHCP
client and a DHCP server on different network segments.
An IP relay address refers to the IP address of the DHCP server specified on the DHCP relay
agent. When DHCP relay is enabled on an interface, broadcast DHCP packets received on this
interface are sent to the specified DHCP server.
DHCP Option
The Option field in a DHCP packet carries control information and parameters that are not
defined in common protocols. If the Option field has been configured on a DHCP server, a DHCP
client can obtain information in the Option field by receiving a DHCP packet from the DHCP
server when applying for an IP address.
Upstream NE
NE role relationships are described in the plug-and-play management module link planning table
based on the NE online sequence. Among the NEs at both ends of a link, the NE that is planned
to go online earlier can be regarded as the upstream NE.
An upstream NE is specified only between NEs at both ends of a link when you fill in the planning
table and implement remote commissioning. The roles of upstream and downstream NEs can
be exchanged during remote commissioning. An upstream NE in this scenario is irrelevant to
an upstream NE for services.
As shown in the preceding figure, ASG3 and ASG4 have been online, and CSG1 and CSG2 are
plug-and-play NEs to be online. If the NEs are planned to go online and their ports are planned
to be configured both in the sequence of CSG1 -> CSG2, CSG1 is the upstream NE for CSG2.
If the planned sequence is CSG2 -> CSG1, CSG2 is the upstream NE for CSG1.
NOTE
l On the access ring, specifying an ASG as an upstream NE is recommended, regardless of the NE online
sequence. In the preceding example, ASG4 is the upstream NE for CSG2, and ASG3 is the upstream
NE for CSG1.
l An NE at one end of a link between ASGs, an ASG and an RSG, or RSGs can act as an upstream NE.
Main Window
This topic describes main window components of the plug-and-play management module as
well as the functions of each component.
Log in to the U2000 client.
Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu (traditional style); alternatively, double-click Fix-Network
Enter a user name and a password for logging in to the U2000 and click Login.
NOTE
When you log in to the plug-and-play management module for the first time:
l Select Firefox as the default web browser as the system prompts.
l If you ensure that the NE supports TLS, disable SSL 3.0 in the Firefox browser to improve network
security. To close the Firefox browser, perform the following operations.
1. On the Firefox browser, enter about:config in the address bar.
2. Search security.tls.version.min.
3. Set security.tls.version.min to 1.
4. Restart the Firefox browser.
l Add an SSL certificate.
l Expand I Understand the Risks and click Add Exception to Confirm Security Exception when
the system indicates This Connection is Untrusted , an SSL certificate is automatically added.
l A user can also manually add an SSL certificate. Specifically, click Open menu > Options in the
upper right corner. In the Options dialog box, click Advanced > Certificates > View
Certificates. In the Certificate Manager dialog box, click Servers > Add Exception. In the Add
Security Exception dialog box, set Location to the U2000 server IP address and click Get
Certificate > Confirm Security Exception, and then click OK.
1. Main menu: The main menu options for the plug-and-play management module 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 configuration deployment.
Shortcut Icons
This topic describes the functions of shortcut icons used for script and template configuration.
receives a packet that does not match NE planning information, an alarm notification is displayed
in the graphical user interface (GUI).
To be online Initial status of the NE. The NE has not been establish
an connection to the plug-and-play management
module.
Newly Setting a Protocol for This topic describes Log in to the plug-and-play
built Making NEs Online the procedure for management module.
network DCN Scenario DHCP using the DCN to Choose NE Online
Scenario make NEs online. Protocol.
Solution Overview
The DCN networking solution uses a private network to allow NEs go online.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose NE Online Protocol from the navigation tree, select DCN networking.
----End
Prerequisites
A protocol for making NEs online has been set.
Context
After you place the cursor in the text box for entering a password, a message is displayed
indicating the password setting rule. Set a new password based on the rule.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose NE Login Parameter from the navigation tree and click the NE Login Parameters
tab.
1. In the Initial NE Login Password area, click . In the dialog box that is displayed,
enter the old password, password, and confirm password.
NOTE
The initial NE login password is Changeme_123. Change the password based on the login mode.
l STelnet mode: If an NE goes online using the DCN automatically available solution for the first
time, change the default password of the root user to this password.
l Telnet mode: If an NE goes online using the DCN automatically available solution for the first
time, change the authentication password of the NE to this password.
After the password is set, click Save.
2. Click OK.
NOTICE
If an NE40E is commissioned to go online, the value of User Password cannot contain the user
name. Otherwise, the NE fails to go online.
2. Set Security Name. Click . In the dialog box that is displayed, set a password.
NOTE
If SNMPv3 is used, ensure that the trap packets can be properly transmitted using SNMPv3 when
SNMP Trap is enabled. The user name set by the security string specifies a user in the existing group.
The group is configured with the ISO view and able to send alarms.
3. Set SNMPv1, SNMPv2c, or SNMPv3 parameters.
l If you select v1 or v2c, enter the read and write community strings and click . In the
dialog box that is displayed, set a password.
l If you select v3, set SNMPv3 parameters, including the user name of an SNMP group, SNMP
group name, Authentication password, and Encryption password. Click . In the dialog
box that is displayed, set a password.
l You can select any two of the three options including v1, v2c, and v3 or select all of them.
NOTICE
If v1, v2c, and v3 are all selected, only v3 is used by the system to add devices. Therefore, if
SNMPv3 parameters are incorrectly configured, the system fails to add devices.
In the U2000 server area, enter the network IP address and mask length.
Step 9 Optional: Click the RTN NE Login Parameters tab to set RTN login parameters and the script
configuration account.
l NE Login Parameters: sets an RTN login user name and password.
l Script Configuring Account: sets a script configuration user name and password.
Click Apply.
----End
Prerequisites
l A protocol for making NEs online has been set.
l Parameters for logging in to NEs have been set.
Context
After you place the cursor in the text box for entering a parameter value, a message is displayed
indicating the parameter setting rule. Set the parameter based on the planned solution and
specified rule.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose NE Management Channel from the navigation tree, select Public Solution or Private
Solution.
l The public network solution is used when users have no requirement on DCN isolation or
security.
l The private network solution is used when users have requirements on DCN isolation and
security.
If Private Solution is selected, configure the solution details based on the following table.
DCN VPN Indicates the DCN function, which is used when users have
requirements on DCN isolation and security.
BGP VPN + This solution applies when VRF configuration on the access ring is not
Public IGP allowed but users are concerned for the security of the public network
solution.
This solution is not recommended.
BGP VPN + This solution applies when new deployment needs to be compatible
DCN VPN with the existing deployment. When the deployed aggregation ring uses
BGP VPN as the management solution, this solution is recommended.
Public IGP + This solution is used when aggregation-side devices get online over a
DCN VPN public network and access-side devices get line over BGP VPN + DCN
VPN.
Local VRF All NEs are bound to the same virtual routing and forwarding (VRF)
to establish private management channels for packet transmission.
NOTE
IGP ID range: In the private DCN VPN solution, IGP ID range indicates the range of IGP IDs
automatically assigned to access rings. The IGP ID of an access ring is obtained by accumulating the
IGP ID step. Enter an IGP ID range in a scenario where a large-scale network needs to be partitioned.
Step 5 Optional: View the generated NE management channel template on the Verify NE
Management Channel Template tab. You can click Create Template, Modify Template, or
Delete Template to edit the current template.
NOTE
You can click Create Template to manually create a template, select NE roles, and configure the template
based on the actual scenario.
Step 6 Optional: For RTN devices, click the Customizing RTN NE Management Channel
Solution tab and select Public solution or Private solution. Then click Apply.
----End
Prerequisites
l A protocol for making NEs online has been set.
l Parameters for logging in to NEs have been set.
l An NE management channel has been customized.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Basic NE Configuration from the navigation tree, click the Customizing Basic
Configuration Solution tab.
NOTE
If you customize basic NE configuration for the first time, only the Customizing Basic Configuration
Solution tab is available. If you have customized basic NE configuration, all the Customizing Basic
Configuration Solution, Checking Basic Configuration Template, Checking Peer Configuration
Template and Extend Configuration Template tabs are available.
Step 4 In the Service Solution area, select HVPN Solution, L2+L3 Standard Solution, L2+L3
Simple Solution, Virtual Access Solution, HVPN+Label BGP Solution or Label BGP to
Edge Solution.
NOTE
l After Virtual Access Solution is selected, other service planning for CSGs is not required on the
U2000.
l Virtual Access Solution can be selected only when BGP VPN + DCN VPN or Public IGP + DCN
VPN is selected from the DCN VPN drop-down list.
l If HVPN+Label BGP Solution or Label BGP to Edge Solution is selected, no BGP routing policy
needs to be configured.
l HVPN+Label BGP Solution or Label BGP to Edge Solution can be selected only when a public
solution or a private DCN VPN solution is selected.
Step 5 In the Aggregation-side Network Solution area, set IGP Solution, MPLS Solution and Use
VLAN sub-interface on the Aggregation-Side for interconnection.
l IGP Solution: Set it to ISIS or OSPF from the drop-down list.
l MPLS Solution: Set it to MPLS TE, LDP, or both.
l MPLS TE Protect Type: When MPLS Solution is set to MPLS TE, set it to HSB or
FRR.
l The Aggregation-Side Use VLAN sub-interface for interconnection: Select it and set
Aggregation-Side Sub-interface VLAN ID if you need to configure a subinterface for the
NE to go online. This parameter is optional.
l IGP Cost of Aggregation-Side Links: Select the check box and enter an IGP cost value as
required. This parameter is optional.
Step 6 In the Access-side Network Solution area, set IGP Solution, MPLS Solution, Access IGP
distribute principle, IGP Cost Between Access-side ASGs, and Use VLAN sub-interface on
the Access-Side for interconnection.
l IGP Solution: Set it to IS-IS Multi-Process, Open Loop for OSPF Multi-Area, or Close
Loop for OSPF Multi-Area. This parameter is mandatory.
NOTE
If MPLS Solution is set to MPLS TE in the Aggregation-side Network Solution area, MPLS TE
Protect Type cannot be set. In this situation, its value is the same as that set in the Aggregation-side
Network Solution area.
l Access-side IGP Assignment Rule: Set it to Unique on the network or Unique in the
master and slave NE pair. This parameter is mandatory. Unique on the network indicates
that IGP ID uniqueness is verified on all NEs on the network. Unique in the master and
slave NE pair indicates that only the process ID and OSPF area assigned to the active or
standby NE need to be unique.
l IGP Cost Between Access-Side NEs: Enter a value in the text box. This parameter is
optional.
l IGP Cost of Access-Side Links: Select the check box and enter an IGP cost value as required.
This parameter is optional.
l The Access-Side use VLAN sub-interface for interconnection: Select it if you need to
configure a subinterface for the NE to go online, for example, in a BGP VPN+IGP public
network scenario. This parameter is optional.
l Sub-interface VLAN ID: If The Access-Side use VLAN sub-interface for
interconnection is selected, Sub-interface VLAN ID must be set.
l Area 0 ID of the VLAN between Access-Side NEs: If IGP Solution is Open Loop for
OSPF Multi-Area or Close Loop for OSPF Multi-Area, select the Area 0 ID of the VLAN
between Access-Side NEs check box to configure the parameter as required. This parameter
is optional.
Step 7 In the Set BGP route strategy area, set BGP routing policies as required.
l The route policy of Aggregation Site's MP-BGP: If the service solution is HVPN
Solution, set this parameter to RR+MED(HVPN+), RR+MED or UPE+Local-
preference. If the service solution is L2+L3 Standard Solution, L2+L3 Simple Solution
or Virtual Access Solution, set this parameter to Load Balancing or None Load
Balancing.
l If The route policy of Aggregation Site's MP-BGP is RR+MED(HVPN+), RR+MED or
Load Balancing, the following parameters must be set:
– Route Reflector(RR) Type: Set it to Independent RR, RSG As RR, or Without RR
as required.
– BGP route policy deploy type: Set it to ASG/RSG Egress on Aggregation Ring or
RR Ingress on Aggregation Ring as required.
– Local AS Number: Set it to the local AS number.
Step 8 Optional: In the NTP Time Synchronization area, configure the local time zone to synchronize
with the NTP time.
l When Configure Local Time Zone is selected, the following parameters must be set:
– Time zone name: Enter the name of the time zone.
– Increased/Decreased by (compared with UTC): Select add or minus.
– Time difference with UTC(h): Enter the difference between the local time and the UTC.
l If Configure NTP Time Synchronization is selected, the following parameters must be set:
Remote server IP address: Enter the IP address of the peer server.
Step 9 In the Trunk Interface Allocation Rule area, set trunk ID allocation principles.
1. Select Using trunk interface to interconnect on the aggregation side or Using trunk
interface to interconnect on the access side, or both.
2. Click Trunk ID Allocation Rule. In the Trunk Interface ID Allocation dialog box, set
the following parameters as required:
l Allocate trunk ID based on role: Select and set the trunk ID based on the role.
l Allocate trunk ID based on link: Enter the trunk ID range.
3. Click OK.
In a scenario where an RSG is directly connected to a CSG, you must select the RSG to allow
the delivery of RSG scripts when the CSG gets online.
Step 11 Click Apply. The Checking Basic Configuration Template, Checking Peer Configuration
Template and Extend Configuration Template tabs are displayed.
NOTE
After you click Apply, a basic NE configuration template is generated. If the template is updated later, the
U2000 will notify you of the update and synchronize the update to the default template.
Step 12 Click the Checking Basic Configuration Template tab to view the generated basic NE
configuration template. You can modify or delete the template or create a template.
Step 13 Click the Checking Peer Configuration Template tab. Create a peer configuration template,
set default peer rules, and modify or delete a created template as required.
Step 14 Click the Extend Configuration Template tab. You can create an extend configuration
template, select additional templates, and modify or delete a created template as required.
----End
Planning Links
This topic describes the procedure for planning links.
Prerequisites
l A protocol for making NEs online has been set.
l Parameters for logging in to NEs have been set.
Context
l Plan address pools if a large number of NEs need to be deployed. If you do not plan address
pools, fill in the planning table with the IP address pool information.
l If no planning list is available, perform only steps 1 through 11.
NOTICE
Before you add an NE that newly goes online to the U2000, manually check the configurations
of the NEs that have not been added to the U2000, and synchronize the configurations of all NEs
that have already been added to the U2000, ensuring that the management IP address, LSR ID,
and link IP address of the NE are unique on the network. In the case of an address conflict, click
Deployment Configuration > Data Planning > NE Information for modification, which
prevents NE management failures.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Link Plan from the navigation tree. Then click the Address Pool Planning tab.
Step 5 In the dialog box that is displayed, set the following parameters:
l IP Pool Name: Enter the name of the address pool to be created.
l IP Pool Type: Select the type of the address pool to be created from the drop-down list. The
available options are the LSR ID address pool, management IP address pool, and link IP
address pool.
l Start IP: Enter a start IP address.
l End IP: Enter an end IP address.
l Mask Length: Select a mask length from the drop-down list.
Step 6 Optional: Click Apply. You can continue to create more address pools.
Users can modify the exported address pool as needed and then import it into the U2000.
NOTE
l To modify or delete one of the created address pools, select one address pool, right-click, and choose
Modify or Delete from the shortcut menu, or select one address pool and click Modify or Delete in
the lower right corner.
l You can also click Import to import an existing address pool list, or click Export to export an address
pool list for future use.
l You can choose whether to select the Do not assign IP end with .0 or .255 check box. If this check
box is selected, the address pool does not assign IP addresses ended with ".0" or ".255".Click OK.
Step 10 In the dialog box that is displayed, configure the master and backup NEs.
Parameter Description
Primary NE
Click and create the master NE as prompted.
Mandatory.
NOTE
You can either select an NE from the Select NE list or create an NE.
Also, you can click Synchronize NE in Main Topology and select an NE in the
Main Topology as the master NE. If the LSR ID of the NE has been synchronized
to the U2000, you do not need to fill in the LSR ID or management IP address. If
the LSR ID of the NE has not been synchronized to the U2000, the LSR ID and
management IP address are empty. You can fill in the LSR ID and management IP
address, or access the global MPLS configuration window of the U2000 to
synchronize the configuration and click Synchronize NE in Main Topology again.
The LSR ID and management IP address of the selected NE must be the same as
those added to the Main Topology.
Allocate access Select it if both the master and slave NEs are ASGs.
rings
Allocate Select Allocate access rings or Allocate aggregation rings if both the
aggregation rings master and slave NEs are RSGs.
Parameter Description
Addresses
Click and create an LSR ID address pool and a link IP address pool
Allocate
as prompted.
Mandatory.
NOTE
You can either select address pools on the Address Pool Planning tab or create
address pools.
You can select multiple address pools for the primary and secondary NEs.
When Virtual Access Solution is selected, you do not need to set Addresses
Allocate.
NOTE
In the case of a private network, the Management DCN Configuration tab is generated. In the Addresses
Allocate, Aggregation-side Allocation Parameters, and Access-side Allocation Parameters areas on
the tab, set Management LSR ID Address Pool and Management IGP ID parameters as planned.
If the parameter settings are inconsistent with the tooltip-prompted type and range, an error message is
displayed, prompting you to reconfigure the parameters. If the configurations are correct, a success message
is displayed.
Step 12 Select the master and slave NE information and click Create in the Ring information on the
primary/secondary NE area to create multiple rings.
If you need to modify all the ring information of the primary/secondary NE, click Save after the
modification. If you need to modify only part of the ring information of the primary/secondary
NE, select the modified ring information and click Save Selected after the modification; if you
click Save, an error message is displayed.
NOTE
If IGP IDs, OSPF area resources, or VLAN IDs are sufficient, the system automatically allocates resources.
If IGP IDs, OSPF area resources, or VLAN IDs are insufficient, you can manually create an empty ring
and set relevant parameters as needed.
The rules for automatic IGP ID allocation are as follows:
1. If OSPF is deployed on the access side and access rings exist, the IGP ID of the first ring is used by
default. Otherwise, use the following rules for the allocation.
2. The IGP IDs, including public IGP IDs and private IGP IDs, ever used for plug-and-play management
cannot be allocated.
3. If IS-IS is deployed on both the access and aggregation sides, the existing aggregation-side IGP IDs
for plug-and-play management cannot be allocated.
4. The IGP IDs that have associated access-side protocols, IS-IS and OSPF, on the U2000 cannot be
allocated.
The rules for automatic OSPF area allocation are as follows:
1. The used OSPF areas, including public OSPF areas and private OSPF areas, corresponding to the IGP
IDs for plug-and-play management cannot be allocated.
2. The used OSPF areas corresponding to the IGP IDs on the U2000 cannot be allocated.
3. Area 0 cannot be allocated because it is located between the primary and secondary NEs.
The rules for automatic VLAN ID allocation are as follows:
1. The used VLAN IDs, including public VLAN IDs and private VLAN IDs, corresponding to the NEs
for plug-and-play management cannot be allocated.
2. The used VLAN IDs corresponding to the NEs on the U2000 cannot be allocated.
Step 14 Click Export the interconnection relationship planning template to plan. Users can modify
the exported planning table as needed and then import it into the U2000.
1. Click Export Link Planning Table Template. If the configurations except the basic
configurations need to be applied, click Choose Extend Template.
2. In the dialog box that is displayed, click Save File.
3. Click OK.
4. Select the planning table save path, enter a planning table name, and click Save.
5. Open the planning table and enter link planning information based on the Note sheet.
The columns marked with asterisks (*) on each sheet are mandatory.
Sheet Description
NetworkLayout Specify the upstream NE for every NE based on the networking and
enter the NE information, such as the sysname, role, interface name,
and interface IP address.
Mandatory.
NOTE
If NE scripts need to be exported or consolidated in future, the sysname and
ring name must not contain question marks (?) or return key characters.
Sheet Description
Trunk When the interface type of the upstream NE is the trunk interface,
enter the trunk information to distinguish from the physical interface
connected to the new NE.
Optional.
Vlanif When the interface type of the upstream NE is the VLANIF interface,
enter the VLANIF information to distinguish from the physical
interface connected to the new NE.
Optional.
Template_List Enter the information about the additional template list. This sheet is
generated only after you select an additional template when exporting
a planning table.
Optional.
6. Click Save.
b. Optional: In the DCN Mode area, set the DCN mode and IGP type.
NOTE
Only the DCN mode can be viewed. The IGP type can be set only when the DCN mode is set
to private local VRF.
c. Optional: Select the Automatic configuration check box in the DCN Address Pool
Planning area and click Configure. In the dialog box that is displayed, plan the DCN
address pool.
NOTE
l DCN Address Pool Planning needs to be set only when DCN Mode is set to Private,
including the local VRF and DCN VPN modes.
l If the DCN mode is set to Local VRF, Management Channel Name must be set.
d. Optional: In the Set Default Peer Generation Rule area, click Configure. In the
dialog box that is displayed, set default peer rules.
e. Click Next.
NOTICE
A message indicating that the data import process is irreversible is displayed. If you
determine to import the data, click OK.
After peer relationship rules are set and peer relationships are generated, select peer
templates and click Finish.
----End
Prerequisites
l A protocol for making NEs online has been set.
l Parameters for logging in to NEs have been set.
l An NE management channel has been customized.
l Basic NE configurations have been customized.
l Steps 1 through 11 in Planning Links have been performed.
l The U2000 client has started.
l Click Deployment Configuration > Deployment Configuration and select NE
Information on the navigation tree on the left side to check whether a planning list is
available for the NE to get online. If a planning list is available, right-click it and select
Delete.
Context
This method applies to scenarios where no planning list is available and NEs are online.
NOTICE
If no planning list is available, ensure that the online NE that is interconnected with the NE to
get online has been synchronized in the plug-and-play module and an NE role has been specified.
Otherwise, the link between the two NEs fails to be discovered. If the online NE has not been
synchronized in the plug-and-play module, click Deployment Configuration > Deployment
Configuration > NE Information > Create and choose Synchronize NE in Main
Topology.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 5 Ensure that the U2000 client has started. In the dialog box that is displayed, click OK.
NOTE
The DCN Management for Routers view is displayed on the U2000 client.
Step 6 Click , or right-click Gateway NE Tree in the navigation tree and choose Set Gate NE from
the shortcut menu.
Step 7 In the dialog box that is displayed, select the desired gateway NEs.
If a message is displayed indicating that the gateway NE information is different from that
imported to the planning list, ignore the message. Click OK. The automatic gateway NE report
window is displayed. Choose to select the automatic report function based on site conditions
and click OK.
NOTE
If the automatic gateway NE reporting function is enabled, when the U2000 delivers repeated
configurations, existing NEs do not report their information to the U2000. Select a GNE from the left-hand
GNE tree of the DCN Management for Routers, right-click, and choose Enable Automatic Report from
the shortcut menu. In the dialog box that is displayed, select Disable and click OK. Then select Enable
again and click OK.
After the operation succeeds, the added gateway NEs are displayed under Gateway NE Tree.
Step 9 Right-click in the blank area and choose Synchronize from the shortcut menu.
After the synchronization is complete, a success message is displayed. The synchronized DCN
topology is displayed in the DCN view, the non-gateway NEs to go online are marked blue, and
all the links are marked green.
NOTE
During the synchronization process, the colors of some links in the topology may change to gray because
link data on the U2000 client is updated every 10 seconds to check whether the latest link data has been
sent from the U2000 server. The links become gray if the Link Layer Discovery Protocol (LLDP)
relationships between NEs fail to establish.
An LLDP relationship establishment failure may occur because interconnected interfaces are shut down,
physical links are disconnected, NEs go offline, or NEs are restarted but the LLDP relationships are not
established.
If the links become gray, wait about 30 seconds and synchronize NE data. If the problem persists, check
whether the physical links work properly.
Step 10 Select the non-gateway NEs expected to be online, right-click, and choose Apply Basic
Configuration > Basic Configuration Planned and Apply from the shortcut menu.
Step 11 In the Configure NE Basic Information dialog box, select a created ring from the Ring
Name drop-down list.
NOTE
l You can modify the NE name and NE role as required. The NE name cannot be the default value,
Huawei.
l If ring information has not been planned yet, you can replan the ring information. Choose New ring
from the Ring Name drop-down list. For details about ring information planning, see steps 7 through
11 in Planning Links.
l To plan links in special scenarios, select the Special Link Layout (Contains to plan the Trunk link,
tangential link, intersectank link, the host prepares among ASG not continually the link) check
box and then click Next.
Step 12 Click Next. In the dialog box that is appeared, view or modify the current information and
planning information about the access ring. if the access ring information needs to be modified,
click Config.
If the master and backup ASGs are not directly connected, you can click Configure the
unconnected Links in ASG NEs to configure links between them. If the master and slave ASGs
are not directly connected, the ASGs can be connected only by physical interfaces, not trunk
interfaces.
To set VLAN IDs or trunk IDs in batches, click the Link Planning tab in the Ring Data
Planning area. Right-click a link, and choose Bulk Set VLAN ID, Bulk Set Trunk ID, or Bulk
Set Uplink Trunk ID from the shortcut menu.
Step 13 Click Next. Confirm the current information and planning information about the access ring, or
modify the LSR ID and link IP address as required. To modify the trunk link data, click Back.
View associated logs after the scripts are applied. If some commands fail to be applied, use
Telnet or STelnet to log in to the NEs and apply these commands.
NOTE
l If multiple NEs are selected to apply the commands, the commands are applied to the NE nearest to
the gateway NE first. The commands are applied to the NEs in ascending sequence based on the number
of hops. The progress bar shows the command applying sequence.
l To view logs, search for running logs by search forward, circle search, or case matching.
After the script is applied, you can view the status information in the running logs of related
NEs. If an NE cannot be added to the Main Topology, locate the fault based on logs.
If the script fails to be delivered, locate the fault based on the error message. If you want to clear
configurations to enable an NE to go online once again, clear the planning list of the NE on the
NMS as well.
----End
Prerequisites
l A protocol for making NEs online has been set.
l Parameters for logging in to NEs have been set.
l An NE management channel has been customized.
l Basic NE configurations have been customized.
l Link planning is complete.
l The U2000 client has started.
Context
This method applies to scenarios where a planning list is available ad link planning is complete.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Online NE Commissioning from the navigation tree, click Online NE
Commissioning.
Step 4 Ensure that the U2000 client has started. In the dialog box that is displayed, click OK.
NOTE
The DCN Management for Routers view is displayed on the U2000 client.
Step 5 Click , or right-click Gateway NE Tree in the navigation tree and choose Set Gate NE from
the shortcut menu.
Step 6 In the dialog box that is displayed, select the desired gateway NEs.
If the gateway NE information is different from the information imported in the planning table,
a message is displayed. Correct the information based on the message. Click OK. The automatic
gateway NE report window is displayed. Choose to select the automatic report function based
on site conditions and click OK.
NOTE
If the automatic gateway NE reporting function is enabled, when the U2000 delivers repeated
configurations, existing NEs do not report their information to the U2000. Select a GNE from the left-hand
GNE tree of the DCN Management for Routers, right-click, and choose Enable Automatic Report from
the shortcut menu. In the dialog box that is displayed, select Disable and click OK. Then select Enable
again and click OK.
After the operation succeeds, the added gateway NEs are displayed under Gateway NE Tree.
The imported planning links in the planning table are displayed in the right pane. All the NEs
and links, except the gateway NE, are marked orange.
Step 8 Right-click in the blank area and choose Synchronize from the shortcut menu.
After the synchronization is complete, a success message is displayed. The synchronized DCN
topology is displayed in the DCN view, the non-gateway NEs to go online are marked blue, and
all the links are marked green.
NOTE
During the synchronization process, the colors of some links in the topology may change to grey because
link data on the U2000 client is updated every 10 seconds to check whether the latest link data has been
sent from the U2000 server. The links become grey if the Link Layer Discovery Protocol (LLDP)
relationships between NEs fail to establish.
An LLDP relationship establishment failure may occur because interconnected interfaces are shut down,
physical links are disconnected, NEs go offline, or NEs are restarted but the LLDP relationships are not
established.
If the links become grey, wait about 30 seconds and synchronize NE data. If the problem persists, check
whether the physical links work properly.
If the DCN topology is the same as that in the link planning, the actual and planned links are merged after
the synchronization is complete. If they are not merged, check Telnet parameter settings of the NE to
determine whether the Telnet connection fails. For details, see Failed to Merge the Planned and Actual
Links Automatically.
Step 9 Select the non-gateway NEs expected to be online, right-click, and choose Apply Basic
Configuration > Apply Basic Configuration from the shortcut menu.
View associated logs after the scripts are applied. If some commands fail to be applied, use
Telnet or STelnet to log in to the NEs and apply these commands.
NOTE
l If multiple NEs are selected to apply the commands, the commands are applied to the NE nearest to
the gateway NE first. The commands are applied to the NEs in ascending sequence based on the number
of hops. The progress bar shows the command applying sequence.
l To view logs, search for running logs by search forward, circle search, or case matching.
After the script is applied, you can view the status information in the running logs of related
NEs. If an NE cannot be added to the Main Topology, locate the fault based on logs.
----End
Solution Overview
The DHCP solution uses DHCP to allow packets to go online. After going online, devices
automatically learn VLANs, send DHCPDISCOVER messages, and use the Option field in the
DHCP messages. The interface and VLAN information about devices enabled with the plug-
and-play function is reported to the plug-and-play module for matching. After matching on the
the deployment tool succeeds, the tool sends DHCPACK messages based on the plan. The
devices then obtain the IP address and interface information from the DHCPACK messages and
automatically configure IP addresses and default routes. In addition, Telnet is enabled on the
devices to allow remote channels. You can use Telnet to issue commands, or you can use the
deployment tool to plan and deploy configuration scripts.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose NE Online Protocol from the navigation tree, select Remote DHCP commissioning.
----End
Prerequisites
A protocol for making NEs online has been set.
Context
NOTE
After you place the cursor in the text box for entering a password, a message is displayed indicating the
password setting rule. Set a new password based on the rule.
Procedure
Step 1 Log in to the U2000 client.
Security Configuration > Plug-and-Play Management from the main menu (application
style).
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose NE Login Parameter from the navigation tree and click the NE Login Parameters
tab.
1. In the Initial NE Login Password area, click . In the dialog box that is displayed,
enter the old password, password, and confirm password.
NOTE
The initial NE login password is Changeme_123. Change the password based on the login mode.
l STelnet mode: If an NE goes online using the DCN automatically available solution for the first
time, change the default password of the root user to this password.
l Telnet mode: If an NE goes online using the DCN automatically available solution for the first
time, change the authentication password of the NE to this password.
After the password is set, click Save.
2. Click OK.
NOTICE
If an NE40E is commissioned to go online, the value of User Password cannot contain the user
name. Otherwise, the NE fails to go online.
2. Set Security Name. Click . In the dialog box that is displayed, set a password.
NOTE
If SNMPv3 is used, ensure that the trap packets can be properly transmitted using SNMPv3 when
SNMP Trap is enabled. The user name set by the security string specifies a user in the existing group.
The group is configured with the ISO view and able to send alarms.
3. Set SNMPv1, SNMPv2c, or SNMPv3 parameters.
l If you select v1 or v2c, enter the read and write community strings and click . In the
dialog box that is displayed, set a password.
l If you select v3, set SNMPv3 parameters, including the user name of an SNMP group, SNMP
group name, Authentication password, and Encryption password. Click . In the dialog
box that is displayed, set a password.
l You can select any two of the three options including v1, v2c, and v3 or select all of them.
NOTICE
If v1, v2c, and v3 are all selected, only v3 is used by the system to add devices. Therefore, if
SNMPv3 parameters are incorrectly configured, the system fails to add devices.
Step 9 Optional: Click the RTN NE Login Parameters tab to set RTN login parameters and the script
configuration account.
Click Apply.
----End
Prerequisites
l A protocol for making NEs online has been set.
l Parameters for logging in to NEs have been set.
Context
After you place the cursor in the text box for entering a parameter value, a message is displayed
indicating the parameter setting rule. Set the parameter based on the planned solution and
specified rule.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose NE Management Channel from the navigation tree, select Public Solution or Private
Solution.
l The public network solution is used when users have no requirement on DCN isolation or
security.
l The private network solution is used when users have requirements on DCN isolation and
security.
Step 4 Optional: If Private Solution is selected, configure the solution details based on the following
table.
DCN VPN Indicates the DCN function, which is used when users have requirements
on DCN isolation and security.
BGP VPN + This solution applies when VRF configuration on the access ring is not
Public IGP allowed but users are concerned for the security of the public network
solution.
This solution is not recommended.
BGP VPN + This solution applies when new deployment needs to be compatible with
DCN VPN the existing deployment. When the deployed aggregation ring uses BGP
VPN as the management solution, this solution is recommended.
Public IGP + This solution is used when aggregation-side devices get online over a
DCN VPN public network and access-side devices get line over BGP VPN + DCN
VPN.
Local VRF All NEs are bound to the same virtual routing and forwarding (VRF) to
establish private management channels for packet transmission.
NOTE
IGP ID range: In the private DCN VPN solution, IGP ID range indicates the range of IGP IDs automatically
assigned to access rings. The IGP ID of an access ring is obtained by accumulating the IGP ID step. Enter
an IGP ID range in a scenario where a large-scale network needs to be partitioned.
Step 6 Optional: View the generated NE management channel template on the Verify NE
Management Channel Template tab. You can click Create Template, Modify Template, or
Delete Template to edit the current template.
NOTE
You can click Create Template to manually create a template, select NE roles, and configure the template
based on the actual scenario.
Step 7 Optional: For RTN devices, click the Customizing RTN NE Management Channel
Solution tab and select Public solution or Private solution. Then click Apply.
----End
Prerequisites
l A protocol for making NEs online has been set.
l Parameters for logging in to NEs have been set.
l An NE management channel has been customized.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Basic NE Configuration from the navigation tree, click the Customizing Basic
Configuration Solution tab.
NOTE
If you customize basic NE configuration for the first time, only the Customizing Basic Configuration
Solution tab is available. If you have customized basic NE configuration, all the Customizing Basic
Configuration Solution, Checking Basic Configuration Template, Checking Peer Configuration
Template and Extend Configuration Template tabs are available.
Step 4 In the Service Solution area, select HVPN Solution, L2+L3 Standard Solution, L2+L3
Simple Solution, Virtual Access Solution, HVPN+Label BGP Solution or Label BGP to
Edge Solution.
NOTE
l After Virtual Access Solution is selected, other service planning for CSGs is not required on the
U2000.
l Virtual Access Solution can be selected only when BGP VPN + DCN VPN or Public IGP + DCN
VPN is selected from the DCN VPN drop-down list.
l If HVPN+Label BGP Solution or Label BGP to Edge Solution is selected, no BGP routing policy
needs to be configured.
l HVPN+Label BGP Solution or Label BGP to Edge Solution can be selected only when a public
solution or a private DCN VPN solution is selected.
Step 5 In the Aggregation-side Network Solution area, set IGP Solution, MPLS Solution and Use
VLAN sub-interface on the Aggregation-Side for interconnection.
l IGP Solution: Set it to ISIS or OSPF from the drop-down list.
l MPLS Solution: Set it to MPLS TE, LDP, or both.
l MPLS TE Protect Type: When MPLS Solution is set to MPLS TE, set it to HSB or
FRR.
l The Aggregation-Side Use VLAN sub-interface for interconnection: Select it and set
Aggregation-Side Sub-interface VLAN ID if you need to configure a subinterface for the
NE to go online. This parameter is optional.
l IGP Cost of Aggregation-Side Links: Select the check box and enter an IGP cost value as
required. This parameter is optional.
Step 6 In the Access-side Network Solution area, set IGP Solution, MPLS Solution, Access IGP
distribute principle, IGP Cost Between Access-side ASGs, and Use VLAN sub-interface on
the Access-Side for interconnection.
l IGP Solution: Set it to IS-IS Multi-Process, Open Loop for OSPF Multi-Area, or Close
Loop for OSPF Multi-Area. This parameter is mandatory.
NOTE
If MPLS Solution is set to MPLS TE in the Aggregation-side Network Solution area, MPLS TE
Protect Type cannot be set. In this situation, its value is the same as that set in the Aggregation-side
Network Solution area.
l Access-side IGP Assignment Rule: Set it to Unique on the network or Unique in the
master and slave NE pair. This parameter is mandatory. Unique on the network indicates
that IGP ID uniqueness is verified on all NEs on the network. Unique in the master and
slave NE pair indicates that only the process ID and OSPF area assigned to the active or
standby NE need to be unique.
l IGP Cost Between Access-Side NEs: Enter a value in the text box. This parameter is
optional.
l IGP Cost of Access-Side Links: Select the check box and enter an IGP cost value as required.
This parameter is optional.
l The Access-Side use VLAN sub-interface for interconnection: Select it if you need to
configure a subinterface for the NE to go online, for example, in a BGP VPN+IGP public
network scenario. This parameter is optional.
Step 7 In the Set BGP route strategy area, set BGP routing policies as required.
l The route policy of Aggregation Site's MP-BGP: If the service solution is HVPN
Solution, set this parameter to RR+MED(HVPN+), RR+MED or UPE+Local-
preference. If the service solution is L2+L3 Standard Solution or L2+L3 Simple
Solution, set this parameter to Load Balancing or None Load Balancing.
l If The route policy of Aggregation Site's MP-BGP is RR+MED(HVPN+), RR+MED or
Load Balancing, the following parameters must be set:
– Route Reflector(RR) Type: Set it to Independent RR, RSG As RR, or Without RR
as required.
– BGP route policy deploy type: Set it to ASG/RSG Egress on Aggregation Ring or
RR Ingress on Aggregation Ring as required.
– Local AS Number: Set it to the local AS number.
Step 8 Optional: In the NTP Time Synchronization area, configure the local time zone to synchronize
with the NTP time.
l When Configure Local Time Zone is selected, the following parameters must be set:
– Time zone name: Enter the name of the time zone.
– Increased/Decreased by (compared with UTC): Select add or minus.
– Time difference with UTC(h): Enter the difference between the local time and the UTC.
l If Configure NTP Time Synchronization is selected, the following parameters must be set:
Remote server IP address: Enter the IP address of the peer server.
Step 9 In the Trunk Interface Allocation Rule area, set trunk ID allocation principles.
1. Select Using trunk interface to interconnect on the aggregation side or Using trunk
interface to interconnect on the access side, or both.
2. Click Trunk ID Allocation Rule. In the Trunk Interface ID Allocation dialog box, set
the following parameters as required:
l Allocate trunk ID based on role: Select and set the trunk ID based on the role.
l Allocate trunk ID based on link: Enter the trunk ID range.
3. Click OK.
In a scenario where an RSG is directly connected to a CSG, you must select the RSG to allow
the delivery of RSG scripts when the CSG gets online.
Step 11 Click Apply. The Checking Basic Configuration Template, Checking Peer Configuration
Template and Extend Configuration Template tabs are displayed.
NOTE
After you click Apply, a basic NE configuration template is generated. If the template is updated later, the
U2000 will notify you of the update and synchronize the update to the default template.
Step 12 Click the Checking Basic Configuration Template tab to view the generated basic NE
configuration template. You can modify or delete the template or create a template.
Step 13 Click the Checking Peer Configuration Template tab. Create a peer configuration template,
set default peer rules, and modify or delete a created template as required.
Step 14 Click the Extend Configuration Template tab. You can create an extend configuration
template, select additional templates, and modify or delete a created template as required.
----End
Planning Links
This topic describes the procedure for planning links.
Prerequisites
l A protocol for making NEs online has been set.
l Parameters for logging in to NEs have been set.
l An NE management channel has been customized.
l Basic NE configurations have been customized.
Context
Plan address pools if a large number of NEs need to be deployed. If you do not plan address
pools, fill in the planning table with the IP address pool information.
NOTICE
Before you add an NE that newly goes online to the U2000, manually check the NE
configurations and synchronize the configurations to the U2000, ensuring that the management
IP address, LSR ID, and link IP address of the NE are unique on the network. In the case of an
address conflict, click Deployment Configuration > Data Planning > NE Information for
modification, which prevents NE management failures.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Link Plan from the navigation tree, then click the Address Pool Planning tab.
Step 5 In the dialog box that is displayed, set the following parameters:
l IP Pool Name: Enter the name of the address pool to be created.
l IP Pool Type: Select the type of the address pool to be created from the drop-down list. The
available options are the LSR ID address pool, management IP address pool, and link IP
address pool.
l Start IP: Enter a start IP address.
l End IP: Enter an end IP address.
l Mask Length: Select a mask length from the drop-down list.
Step 6 Optional: Click Apply. You can continue to create more address pools.
Users can modify the exported address pool as needed and then import it into the U2000.
NOTE
l To modify or delete one of the created address pools, select one address pool, right-click, and choose
Modify or Delete from the shortcut menu, or select one address pool and click Modify or Delete in
the lower right corner.
l You can also click Import to import an existing address pool list, or click Export to export an address
pool list for future use.
l You can choose whether to select the Do not assign IP end with .0 or .255 check box. If this check
box is selected, the address pool does not assign IP addresses ended with ".0" or ".255".Click OK.
Step 10 In the dialog box that is displayed, configure the master and backup NEs.
Parameter Description
Primary NE
Click and create the master NE as prompted.
Mandatory.
NOTE
You can either select an NE from the Select NE list or create an NE.
Also, you can click Synchronize NE in Main Topology and select an NE in the
Main Topology as the master NE. If the LSR ID of the NE has been synchronized
to the U2000, you do not need to fill in the LSR ID or management IP address. If
the LSR ID of the NE has not been synchronized to the U2000, the LSR ID and
management IP address are empty. You can fill in the LSR ID and management IP
address, or access the global MPLS configuration window of the U2000 to
synchronize the configuration and click Synchronize NE in Main Topology again.
The LSR ID and management IP address of the selected NE must be the same as
those added to the Main Topology.
Parameter Description
Allocate access Select it if both the master and slave NEs are ASGs.
rings
Allocate Select Allocate access rings or Allocate aggregation rings if both the
aggregation rings master and slave NEs are RSGs.
Allocate
Click and create an LSR ID address pool and a link IP address pool
Addresses
as prompted.
Mandatory.
NOTE
You can either select address pools on the Address Pool Planning tab or create
address pools.
You can select multiple address pools for the primary and secondary NEs.
NOTE
In the case of a private network, the Management DCN Configuration tab is generated. In the Addresses
Allocate, Aggregation-side Allocation Parameters, and Access-side Allocation Parameters areas on
the tab, set Management LSR ID Address Pool and Management IGP ID parameters as planned.
If the parameter settings are inconsistent with the tooltip-prompted type and range, an error message is
displayed, prompting you to reconfigure the parameters.. If the configurations are correct, a success
message is displayed.
Step 12 Select the master and slave NE information and click Create in the Ring information on the
primary/secondary NE area to create multiple rings.
If you need to modify all the ring information of the primary/secondary NE, click Save after the
modification. If you need to modify only part of the ring information of the primary/secondary
NE, select the modified ring information and click Save Selected after the modification; if you
click Save, an error message is displayed.
NOTE
If IGP IDs, OSPF area resources, or VLAN IDs are sufficient, the system automatically allocates resources.
If IGP IDs, OSPF area resources, or VLAN IDs are insufficient, you can manually create an empty ring
and set relevant parameters as needed.
The rules for automatic IGP ID allocation are as follows:
1. If OSPF is deployed on the access side and access rings exist, the IGP ID of the first ring is used by
default. Otherwise, use the following rules for the allocation.
2. The IGP IDs, including public IGP IDs and private IGP IDs, ever used for plug-and-play management
cannot be allocated.
3. If IS-IS is deployed on both the access and aggregation sides, the existing aggregation-side IGP IDs
for plug-and-play management cannot be allocated.
4. The IGP IDs that have associated access-side protocols, IS-IS and OSPF, on the U2000 cannot be
allocated.
The rules for automatic OSPF area allocation are as follows:
1. The used OSPF areas, including public OSPF areas and private OSPF areas, corresponding to the IGP
IDs for plug-and-play management cannot be allocated.
2. The used OSPF areas corresponding to the IGP IDs on the U2000 cannot be allocated.
3. Area 0 cannot be allocated because it is located between the primary and secondary NEs.
The rules for automatic VLAN ID allocation are as follows:
1. The used VLAN IDs, including public VLAN IDs and private VLAN IDs, corresponding to the NEs
for plug-and-play management cannot be allocated.
2. The used VLAN IDs corresponding to the NEs on the U2000 cannot be allocated.
Step 14 Click Export the interconnection relationship planning template to plan. Users can modify
the exported planning table as needed and then import it into the U2000.
1. Click Export Link Planning Table Template. If the configurations except the basic
configurations need to be applied, click Choose Extend Template.
2. In the dialog box that is displayed, click Save File.
3. Click OK.
4. Select the planning table save path, enter a planning table name, and click Save.
5. Open the planning table and enter link planning information based on the Note sheet.
The columns marked with asterisks (*) on each sheet are mandatory.
Sheet Description
NetworkLayout Specify the upstream NE for every NE based on the networking and
enter the NE information, such as the sysname, role, interface name,
and interface IP address.
Mandatory.
NOTE
If NE scripts need to be exported or consolidated in future, the sysname and
ring name must not contain question marks (?) or return key characters.
Sheet Description
Trunk When the interface type of the upstream NE is the trunk interface,
enter the trunk information to distinguish from the physical interface
connected to the new NE.
Optional.
Vlanif When the interface type of the upstream NE is the VLANIF interface,
enter the VLANIF information to distinguish from the physical
interface connected to the new NE.
Optional.
Template_List Enter the information about the additional template list. This sheet is
generated only after you select an additional template when exporting
a planning table.
Optional.
6. Click Save.
b. Optional: In the DCN Mode area, set the DCN mode and IGP type.
NOTE
Only the DCN mode can be viewed. The IGP type can be set only when the DCN mode is set
to private local VRF.
c. Optional: Select the Automatic configuration check box in the DCN Address Pool
Planning area and click Configure. In the dialog box that is displayed, plan the DCN
address pool.
NOTE
l DCN Address Pool Planning needs to be set only when DCN Mode is set to Private,
including the local VRF and DCN VPN modes.
l If the DCN mode is set to Local VRF, Management Channel Name must be set.
d. Optional: In the Set Default Peer Generation Rule area, click Configure. In the
dialog box that is displayed, set default peer rules.
e. Click Next.
NOTICE
A message indicating that the data import process is irreversible is displayed. If you
determine to import the data, click OK.
After peer relationship rules are set and peer relationships are generated, select peer
templates and click Finish.
----End
Online NE Commissioning
This topic describes how to commission an NE to make the NE online in a DHCP scenario.
Prerequisites
l A protocol for making NEs online has been set.
l Parameters for logging in to NEs have been set.
l An NE management channel has been customized.
l Basic NE configurations have been customized.
l Link planning is complete.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Online NE Commissioning from the navigation tree, click Online NE
Commissioning.
Step 4 On the DHCP Remote Commissioning tab, select the IP address of a DHCP server and click
Apply.
Step 5 Optional: The DHCP service will fail to start on SUSE Linux, and you need to manually start
it. If you click Start without starting the DHCP service manually, a message indicating that port
67 is used will be displayed because a non-root user is not allowed to start a port with the number
less than 1024 on SUSE Linux.
1. Log in to the U2000 System Monitor client and stop the GCLI process.
2. Log in to the SUSE Linux server as the root user. Alternatively, log in to the SUSE Linux
server as the ossuser user and run the su - root command to switch to the root user. Then
enter the password of the root user.
3. Run the following commands to start the DHCP service:
# cd /opt/oss/server
# . svc_profile.sh
# nohup $IMAP_JAVA_HOME/bin/java -Dprocname=Gcli -
Dorg.osgi.service.http.port=13061 -Dfile.encoding=UTF-8 -
DinstanceName=gcli_uflight_server -XX:MaxPermSize=256m -XX:PermSize=16m -
Xms32m -Xmx1024m -XX:+HeapDumpOnOutOfMemoryError -
DdeploymentMode=integrated -Djava.class.path=./common/uflight/bin/
com.huawei.uflight.osgistarter.jar:./common/uflight/plugins/
org.eclipse.osgi_3.5.1.R35x_v20090827.jar com.huawei.uflight.FrameworkStarter -
clean -configuration bin/gcli_uflight_server &
After this command is executed, you do not need to start the GCLI process on the U2000
System Monitor client.
Step 6 Click Start. In the dialog box that is displayed, carefully read the instructions to learn any
possible impact on services and then click OK. The DHCP server status is displayed as Start.
This operation will start the DHCP service of the U2000, automatically configure the DHCP
relay function on the upstream NE interface when the NE goes online, and delivers a
preconfigured script to the NE.
NOTICE
DHCP is an insecure protocol. The DHCP service has to be disabled after site deployment.
Step 7 On the NE Monitoring Status tab, click Refresh or Ping to check whether the NE IP address
can be pinged through and refresh the NE status.
Step 8 After the NE gets online, click Deploy.
NOTE
----End
Procedure
Step 1 Log in to the U2000 client.
Step 2 Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu (traditional style); alternatively, double-click Fix-Network
NE Configuration in Application Center and choose Configuration > Router/Switch/
Security Configuration > Plug-and-Play Management from the main menu (application
style).
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 Click Deployment Configuration > 3rd Party Remote Commissioning in Direct Mode.
Step 4 Select the IP address of the DHCP server and click Apply.
Step 5 Click Start. The DHCP server status is displayed as Start.
Step 6 Optional: Change the initial password for logging in to the NEs.
1. In the Initial NE Login Password area, click . In the dialog box that is displayed,
enter the old password, password, and confirm password.
NOTE
The initial NE login password is Changeme_123. Change the password based on the login mode.
l STelnet mode: If an NE goes online using the DCN automatically available solution for the first
time, change the default password of the root user to this password.
l Telnet mode: If an NE goes online using the DCN automatically available solution for the first
time, change the authentication password of the NE to this password.
After the password is set, click Save.
2. Click OK.
NOTICE
If an NE40E is commissioned to go online, the value of User Password cannot contain the user
name. Otherwise, the NE fails to go online.
2. Set Security Name. Click . In the dialog box that is displayed, set a password.
NOTE
If SNMPv3 is used, ensure that the trap packets can be properly transmitted using SNMPv3 when
SNMP Trap is enabled. The user name set by the security string specifies a user in the existing group.
The group is configured with the ISO view and able to send alarms.
3. Set SNMPv1, SNMPv2c, or SNMPv3 parameters.
l If you select v1 or v2c, enter the read and write community strings and click . In the
dialog box that is displayed, set a password.
l If you select v3, set SNMPv3 parameters, including the user name of an SNMP group, SNMP
group name, Authentication password, and Encryption password. Click . In the dialog
box that is displayed, set a password.
l You can select any two of the three options including v1, v2c, and v3 or select all of them.
NOTICE
If v1, v2c, and v3 are all selected, only v3 is used by the system to add devices. Therefore, if
SNMPv3 parameters are incorrectly configured, the system fails to add devices.
In the U2000 server area, enter the network IP address and mask length.
NOTICE
This operation will modify the NE login parameters set in Step 2 of the Deployment
Overview page and may affect the script generation for NEs that go online through the DCN,
DHCP, or IPRAN cell site online protocol.
Step 11 In the dialog box that is displayed, carefully read the instructions to learn any possible impact
on services and then click OK.
3. Click OK.
l Create an NE by exporting and importing the planning table.
1. Click Export NE Planning List.
NOTE
If the planning table has been obtained, fill in the table and click Import NE Planning List.
2. Click Export Link Planning Table Template. If the configurations except the basic
configurations need to be applied, click Choose Extend Template.
3. In the dialog box that is displayed, select Save File.
4. Click OK.
5. Select the planning table saving path, enter a planning table name, and click Save.
6. Set parameters, such as NE sysname, Interface Name, Planned ESN, Management
IP Address, and Interface IP Address/Mask. The columns marked * are mandatory.
7. Click Import NE Planning List.
8. In the dialog box that is displayed, select Browse. Then select the planning table.
9. Click Open.
10. Click Import.
If the imported planning table is incorrect, modify the settings and re-import the table
as prompted.
NOTE
To add, modify, or delete NE information, right-click the information and choose Create, Modify, or Delete
from the shortcut menu.
----End
Solution Overview
The DCN networking solution uses a private network to allow NEs go online.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose NE Online Protocol from the navigation tree, select IPRAN CellSite Protocol.
NOTICE
After you enable this protocol, small cells automatically go online and trigger script delivery.
----End
Prerequisites
A protocol for making NEs online has been set.
Context
After you place the cursor in the text box for entering a password, a message is displayed
indicating the password setting rule. Set a new password based on the rule.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose NE Login Parameter from the navigation tree and click the NE Login Parameters
tab.
1. In the Initial NE Login Password area, click . In the dialog box that is displayed,
enter the old password, password, and confirm password.
NOTE
The initial NE login password is Changeme_123. Change the password based on the login mode.
l STelnet mode: If an NE goes online using the DCN automatically available solution for the first
time, change the default password of the root user to this password.
l Telnet mode: If an NE goes online using the DCN automatically available solution for the first
time, change the authentication password of the NE to this password.
After the password is set, click Save.
2. Click OK.
l If you select v1 or v2c, enter the read and write community strings and click . In the
dialog box that is displayed, set a password.
l If you select v3, set SNMPv3 parameters, including the user name of an SNMP group, SNMP
group name, Authentication password, and Encryption password. Click . In the dialog
box that is displayed, set a password.
l You can select any two of the three options including v1, v2c, and v3 or select all of them.
In the U2000 server area, enter the master server IP address, slave server IP address, and mask
length. The slave server IP address is optional.
Step 9 Optional: Click the RTN NE Login Parameters tab to set RTN login parameters and the script
configuration account.
Click Apply.
----End
Prerequisites
l A protocol for making NEs online has been set.
l Parameters for logging in to NEs have been set.
Context
After you place the cursor in the text box for entering a parameter value, a message is displayed
indicating the parameter setting rule. Set the parameter based on the planned solution and
specified rule.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose NE Management Channel from the navigation tree, select CellSite Management
Type.
l Vlanif Solution: a public network solution that applies to scenarios where VLANIF
interfaces are used to manage devices.
Enter values for Management VLAN.
l DCN VPN Solution: a private network solution that applies to scenarios where a DCN VPN
is used to manage devices.
----End
Prerequisites
l A protocol for making NEs online has been set.
l Parameters for logging in to NEs have been set.
l An NE management channel has been customized.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Basic NE Configuration from the navigation tree, click the CellSite Basic
Configuration tab.
Step 4 Click Apply. The Checking Basic Configuration Template tab is displayed.
Step 5 Click the Checking Basic Configuration Template tab to view the generated basic NE
configuration template. You can modify or delete the template.
NOTE
Clicking Create on this tab to manually create a basic NE configuration template for the cell site is not
recommended.
----End
Planning Links
This topic describes the procedure for planning links.
Prerequisites
l A protocol for making NEs online has been set.
l Parameters for logging in to NEs have been set.
l An NE management channel has been customized.
l Basic NE configurations have been customized.
Procedure
Step 1 Log in to the U2000 client.
Security Configuration > Plug-and-Play Management from the main menu (application
style).
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Link Plan from the navigation tree. Then click the CellSite Resource tab.
Step 4 Optional: If DCN VPN Solution has been selected on the NE Management Channel tab,
select a management IP address pool in the Global IP Address Pool area.
Step 5 On the UPE Down Interface tab, select the downstream interface of a specified UPE.
l Find by NE Type: This check box is selected by default.
l Find by UPE Down Interface: After this check box is selected, click Add to select the
downstream interface for the new UPE.
Click OK.
Step 6 On the Business Interface tab, enter the required interface number.
l All Other Interface Except Interconnect: This check box is selected by default.
l Business Interface: After this check box is selected, click Create to select the downstream
interface for the new UPE.
Click OK.
----End
Follow-up Procedure
After the configuration is complete, click Online NE Commissioning from the navigation tree,
click Online NE Commissioning and view online NEs in the router DCN view.
Procedure
Procedure
Step 1 Log in to the U2000 client.
Step 2 Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu (traditional style); alternatively, double-click Fix-Network
NE Configuration in Application Center and choose Configuration > Router/Switch/
Security Configuration > Plug-and-Play Management from the main menu (application
style).
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 Choose Script Management > Script Management from the main menu.
Step 4 In the NE List navigation tree or folder, right-click NE List and choose Synchronize NMS and
NE > Synchronize All NMS NE or Synchronize NMS and NE > Synchronize Selected NMS
and NE from the shortcut menu.
l If Synchronize All NMS NE is selected, click OK.
l If Synchronize Selected NMS and NE is selected:
1. In the Synchronize NMS and NESync NE From VSM dialog box, set query conditions
and click Query.
2. Select the NE to be imported and click OK.
The imported NE is displayed in the NE List navigation tree and NE List.
----End
Follow-up Procedure
To check whether the NE communicates with the plug-and-play management module properly,
perform the following operations:
1. On the NE List tab page, select an imported NE.
2. Optional: In the General area, modify NE parameters and click Apply.
NOTE
Prerequisites
Routers or switches are available in the U2000 Main Topology.
Context
An .xlsx file exported by the plug-and-play management module contains the interface, IGP
route, and board information about NEs.
The file can be used as input for network expansion planning and be directly imported to the
Unistar.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Deployment Configuration > Export NMS Data from the main menu.
Step 4 In the dialog box that is displayed, click Save File and OK.
Users can modify the exported U2000 Data as needed and then import it into the U2000.
Messages that prompt you to save a file may vary with browser settings. Save the file as prompted.
----End
Procedure
7 Deploying Scripts.
Prerequisites
NEs must be added to the plug-and-play management module and the connectivity check must
be performed successfully. For details about how to add NEs, see Synchronizing NE
Configurations to the U2000.
Context
l Check whether the NE type and version are empty in the NE list. If the NE type and version
are not empty, the command sets of the NE have been obtained by the plug-and-play
management module and you do not need to click Obtain Command Set.
l If no command set is obtained, check whether the Telnet/STelnet parameters of the NE are
correct by clicking Test in the General area in the NE list. If the test failed, reset the Telnet/
STelnet parameters for the NE. Command sets can be obtained only after the test succeeds.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Script Management > Script Management from the main menu..
Step 4 In the NE List navigation tree, select the NE whose command set needs to be obtained, right-
click, and then choose Obtain Command Set from the shortcut menu.
Alternatively, choose Script Management > NE > Obtain Command Set from the main menu.
----End
Prerequisites
Inheritable scripts must be obtained.
Context
Existing scripts can be classified into the following types:
l Sample scripts in the LLD document
l Saved scripts that have been used
The feature you have purchased may obtain or use some personal information of users when
providing services or maintenance. Therefore, you are obliged to formulate a privacy policy
according to the applicable law and take sufficient measures to keep the personal information
secure.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Script Management > Script Management from the main menu.
Step 4 Choose NE List from the navigation tree. Select the NE to be configured, right-click, and then
choose Create Script from the shortcut menu.
Alternatively, choose Script Management > NE > Create Script from the main menu.
Step 5 In the Create Script dialog box, set Script Name and Description, and then click OK. The
created script is automatically generated under the associated NE node.
Step 6 Click Modify to copy sample scripts in the LLD document or saved scripts to the blank area in
the right pane and modify them as required.
NOTE
If there are a large quantity of commands in scripts, click Find/Replace to modify scripts.
Step 9 In the Verification Result dialog box, view the verification result for each command.
l If the verification result of a command is Error, take the following operations:
Click Close. In the text box for command query, enter the command and press Enter to check
whether the NE supports the command. Then, modify the command in the Script
Configuration area.
NOTE
l Enter only the keyword of the command to be queried. Do not enter any command parameter.
l If the Verification Result is displayed as an Error, this command cannot be found in the current
view. Check whether this command is correct and whether it is in the correct view.
l If the verification result of a command is Ambiguous Match, take the following operations:
Click Close. In the text box for command query, enter the command and press Enter. The
value range for the parameter in the command is displayed. Based on this range, modify the
command in the Script Configuration area.
Step 11 In the Generate Template dialog box, view the command parameter settings.
Step 13 In the dialog box that is displayed, set Template Name, Template description, and Application
scenario.
Step 14 Click OK. A message is displayed indicating that the operation is successful.
After the template is created successfully, choose Templates > Project Template to view the
template and change the parameters and commands in the template as required.
----End
Prerequisites
l NEs must be created or imported.
l A template must be created or imported.
l All the required information must be entered for the exported planning table.
Context
The feature you have purchased may obtain or use some personal information of users when
providing services or maintenance. Therefore, you are obliged to formulate a privacy policy
according to the applicable law and take sufficient measures to keep the personal information
secure.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Script Management > Script Management from the main menu.
Step 4 Choose NE List from the navigation tree. Right-click NE List and choose Import Planning
Table from the shortcut menu.
Step 5 In the dialog box that is displayed, click Browse to select the network data planning table.
If the Replace same-name script check box is selected, scripts with the same name are replaced.
If the Replace same-name script check box is not selected, scripts generated subsequently will
be named based on the previous script name. For example, if a script named Interface
Configuration(1) already exists, after a planning table is imported, the script name is Interface
Configuration(2).
----End
Deploying Scripts
This topic describes how to deploy scripts to configure NEs in batches.
Prerequisites
l NEs communicate properly with each other.
l The scripts that have been successfully verified must exist. For details about how to verify
a script, see Verifying a Script.
NOTICE
l Script deployment delivers configurations to a specified NE, which may cause service
deletion or network interruption. Exercise caution when you perform this operation.
l After you deploy a script, access the Main Topology and synchronize the data of the
associated NE to the U2000 to ensure data consistency. For details, see 1.7 Synchronizing
NE Data.
l In the storage directory, you can view deployment records of scripts deployed using
Applying a Template.
l If the size of logs recording script deployment exceeds 1G, a warning dialog box will be
displayed. In this case, you can access the log directory and delete logs by generation time.
Directories of storing script deployment logs:
l Windows: oss\server\etc\oss_cfg\ip\gcli\pnpscriptlogs.
l Linux: oss/server/etc/oss_cfg/ip/gcli/pnpscriptlogs.
l Solaris: oss/server/etc/oss_cfg/ip/gcli/pnpscriptlogs.
Context
l The feature you have purchased may obtain or use some personal information of users when
providing services or maintenance. Therefore, you are obliged to formulate a privacy policy
according to the applicable law and take sufficient measures to keep the personal
information secure.
l Scripts for multiple NEs can be selected and deployed in batches.
l Ensure that each script is deployed on the desired NE correctly. If unexpected scripts are
deployed on an NE or if scripts are deployed improperly on an NE, services may be
interrupted, or service configurations may be deleted.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Script Management > Script Management from the main menu.
Step 4 In the NE List navigation tree, right-click the script to be deployed or the NE where the script
is to be deployed and choose Deploy Script from the shortcut menu.
NOTE
l Before script deployment, you can click Deploy History Detail and then check script deployment
history status and result in the Deploy History dialog box, preventing repeated script delivery.
l Deploy Script allows a maximum of 500 scripts to be deployed concurrently.
l The Deploy Script window has to be closed during script deployment. Scripts with Deployment
Status of Deploying will be deployed to desired NEs, while those with Deployment Status of
Ready cannot be deployed to desired NEs.
Step 5 In the Batch Script Deployment or Select NE dialog box, select a script to be deployed or a
desired NE and click Next.
Step 6 Click Deploy or Deploy All.
You can select and deploy scripts of multiple NEs at the same time.
Step 7 In the confirmation dialog box, click OK.
Step 8 The progress of deploying the scripts is displayed on the Deployment Results tab page.
If a script fails to be deployed, perform any of the following operations as needed:
l Retry: The system re-executes the abnormal command.
l Ignore: The system ignores the abnormal command and continues to execute the next
command.
l Stop: The system stops deploying scripts.
Step 9 Click Save Configurations to save the configurations to NEs.
----End
Context
The reference commands are as follows:
NOTICE
The following commands are used for reference only. For the commands used for actual
deployment, contact the MBB solution staff.
system-view
aaa
authentication-scheme huawei
authorization-scheme huawei
accounting-scheme huawei
accounting-mode hwtacacs
domain default
authentication-scheme huawei
authorization-scheme huawei
accounting-scheme huawei
hwtacacs-server huawei
recording-scheme huawei
user-interface vty 0 4
authentication-mode aaa
idle-timeout 10 0
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Script Management > Script Management from the main menu.
Step 4 Select an NE on which a script is to be created from the NE List navigation tree, right-click,
and choose Obtain Command Set from the shortcut menu.
Step 5 Select the NE whose command set has been obtained, right-click, and choose Create Script
from the shortcut menu.
Step 6 In the Create Script dialog box, enter a script name and click OK.
Step 8 Paste the commands to be delivered in the text box at the bottom. Click Save.
NOTE
l If commands need to be copied from this topic, copy them to the text editor first and then from the text editor
to the script configuration window.
l The commands provided in this topic are used for reference only. For the commands used for actual
deployment, contact the MBB solution staff. If an IP address or the template name needs to be changed,
change it in the script configuration window.
l After Save is clicked, if the error count is not 0, check the command in red, change them to be in the correct
format, and save them again. Repeat these operations until the error count is 0.
Step 9 Click Verify Script to ensure that all verification results are successful.
Step 12 In the Deploy Script dialog box, select desired scripts and click Deploy or Deploy all.
Step 14 Click Save Configurations and manually save the configuration result to the NE.
----End
Procedure
1 Modifying a Template.
2 Exporting Templates.
Modifying a Template
Modify commands and parameters in a template.
Context
Custom project templates, but not system-defined templates, can be modified.
The feature you have purchased may obtain or use some personal information of users when
providing services or maintenance. Therefore, you are obliged to formulate a privacy policy
according to the applicable law and take sufficient measures to keep the personal information
secure.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Templates Management > Templates Management from the main menu.
Step 4 Choose the desired template under Project Template from the navigation tree. All commands
and parameters of the template are displayed in the right pane. You can modify the template
using the following methods:
l Double-click a command or view and modify the description.
NOTE
l For details about how to modify a Velocity Template Language (VTL) template, see the
procedure for creating a VTL template.
l Lines started with asterisks (*) indicate mandatory parameters in the command. If these
parameters are not set, the command does not take effect.
l If the descriptions of two parameters in the template are the same, the parameters are combined
in the exported template.
l If the command contains parameters of the enumerated type and the enumerated parameter values
are incomplete, modify the command to add parameter values. For example, in the
authentication-mode aaa command, aaa indicates that the authentication mode is
authentication, authorization and accounting (AAA). The other authentication modes are
password and none. If you change aaa into ENUM{aaa,none,password}, any authentication
mode can be selected when you set this parameter.
l Insert a command into the template.
1. Click . In the dialog box that is displayed, select the desired view and command.
4. Click OK.
If command verification succeeds, the command is inserted into the template. If
command verification fails, the message Failed to verify the script is displayed.
Correct the command and insert it into the template.
l Enter default parameter values. To enter or change parameter values, double-click the
Default Value column.
The cells marked with the asterisk (*) in the Configuration Item column are mandatory.
The rules of assigning some values in the Default Value column can be modified.
For example, the default value assignment rule for ISIS Name under ISIS
Configuration is =add(sysname,igpid), and the value of ISIS Name is sysname+igpid.
The rule can be changed to =sysname to meet site requirements, and the value of ISIS
Name is sysname.
l Set a command that contains no parameter in the template to be optional.
1. Select a command that contains no parameter and click Modify Command. In the
dialog box that is displayed, enclose the command in square brackets.
NOTE
Leave a space between the command and either square bracket.
2. Click OK. A check box is displayed on the right of the command. If the check box is
selected, the command will be executed. If the check box is not selected, the command
will not be executed.
l Copy and paste commands.
1. Select the commands to be copied or the view in which commands need to be copied,
and click .
NOTE
Commands or views in either the current or another template can be copied.
– If a command or parameters in the command are copied, the copy will be pasted
below the command.
– To paste the copy to a blank template, ensure that the copy contains the root node.
l Adjust the command sequence in the template.
1. Click to move the selected command or view and its subnodes upwards.
2. Click to move the selected command or view and its subnodes downwards.
l Delete a command or view.
Select the desired command or view and click .
NOTE
If you delete a selected view, all the commands in the view are deleted.
----End
Exporting Templates
This topic describes how to export templates. The tool supports the exporting and backup of all
templates for follow-up template modification or for reference.
Context
You can choose to export some templates or all templates as required.
The feature you have purchased may obtain or use some personal information of users when
providing services or maintenance. Therefore, you are obliged to formulate a privacy policy
according to the applicable law and take sufficient measures to keep the personal information
secure.
Procedure
l To export some templates, do as follows:
1. Log in to the U2000 client.
2. Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu (traditional style); alternatively, double-click Fix-
Network NE Configuration in Application Center and choose Configuration >
Router/Switch/Security Configuration > Plug-and-Play Management from the
main menu (application style).
Enter a user name and a password for logging in to the U2000 and click Login.
3. Choose Templates Management > Templates Management from the main menu.
4. Choose Template List from the navigation tree. All templates are displayed in the
right pane.
5. Hold down Ctrl while selecting the templates to be exported. Right-click these
templates and choose Export Template from the shortcut menu.
Alternatively, choose Template Management > Folder > Export Template from
the main menu.
Users can modify the exported template as needed and then import it into the U2000.
NOTE
The template is saved to a specified path depending on the settings of the FireFox browser.
You can also select a path as needed. The method of viewing or changing the save path in the
FireFox browser is as follows:
Choose Tools > Options from the main menu of the FireFox browser. On the General tab,
view or select the save path.
l To export all templates, do as follows:
1. Log in to the U2000 client.
2. Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu (traditional style); alternatively, double-click Fix-
Network NE Configuration in Application Center and choose Configuration >
Router/Switch/Security Configuration > Plug-and-Play Management from the
main menu (application style).
Enter a user name and a password for logging in to the U2000 and click Login.
3. Click Templates Management and select Templates Management.
4. Choose Template List from the navigation tree. All templates are displayed in the
right pane.
5. Select one or more templates, right-click, and choose Select All from the shortcut
menu.
6. Right-click these templates and choose Export Template.
7. A message is displayed indicating that password information cannot be imported or
exported. Click OK.
8. In the dialog box that is displayed, click the Save File option button, and then click
OK.
Users can modify the exported template as needed and then import it into the U2000.
NOTE
The template is saved to a specified path depending on the settings of the FireFox browser.
You can also select a path as needed. The method of viewing or changing the save path in the
FireFox browser is as follows:
Choose Tools > Options from the main menu of the FireFox browser. On the General tab,
view or select the save path.
----End
Importing a Template
This topic describes how to import a template. The template can be either a customized one or
a universal one provided by the plug-and-play management module.
Prerequisites
The template to be imported is included in the .zip package that is created when you use the
plug-and-play management module to export templates.
The .zip package includes template contents and related attribute information. Do not
decompress or modify the package.
Context
The feature you have purchased may obtain or use some personal information of users when
providing services or maintenance. Therefore, you are obliged to formulate a privacy policy
according to the applicable law and take sufficient measures to keep the personal information
secure.
Procedure
Step 1 Log in to the U2000 client.
Step 2 Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu (traditional style); alternatively, double-click Fix-Network
NE Configuration in Application Center and choose Configuration > Router/Switch/
Security Configuration > Plug-and-Play Management from the main menu (application
style).
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 Choose Templates Management > Templates Management from the main menu.
Step 4 Select the Template List node, right-click, and then choose Import Template from the shortcut
menu.
Alternatively, choose Template Management > Folder > Import Template from the main
menu.
Step 5 In the dialog box that is displayed, click Browse, and then select the template to be imported.
Users can modify the exported template as needed and then import it into the U2000.
Step 6 Click Import. If the template already exists, the plug-and-play management module performs
a check and asks you whether to overwrite the existing one.
----End
2.4.4 Appendix
Context
The feature you have purchased may obtain or use some personal information of users when
providing services or maintenance. Therefore, you are obliged to formulate a privacy policy
according to the applicable law and take sufficient measures to keep the personal information
secure.
You can create a script in any of the following methods. This topic focuses on the method of
creating a script manually.
l Create a script manually.
Enter commands to create a script manually.
NOTE
If a large number of commands are required for script creation, creating several scripts is
recommended, with each script containing no more than 200 commands. This is to ensure the
efficiency of script verification and deployment.
l Create a script by using a template.
The template to be used can be either universal or customized. For details, see Applying
a Template.
l Create a script by importing the planning table.
You can use existing templates to generate a planning table. After you set parameters for
the planning table and then import the planning table, the plug-and-play management
module automatically generates scripts based on planning information.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Script Management > Script Management from the main menu..
Step 4 In the NE List navigation tree, select the NE for which the script needs to be created, right-click,
and then choose Create Script from the shortcut menu.
Alternatively, choose Script Management > NE > Create Script from the main menu.
Step 5 In the Create Script dialog box, set Script Name and Description, and then click OK.
If the NE script needs to be exported or merged in the future, the script name cannot contain
special characters \ / : * ? < > |.
After entering a command keyword in the query box, click or press Enter to query
commands related to the command keyword.
All commands are displayed in colors and view commands are displayed in bold.
NOTE
l If characters in the script are displayed in black after you click to save the commands, it indicates
that the type and version of the NE have not been set. In this case, you must obtain the command set
or manually set the type and version of the NE.
l If a command is marked in red in the script, this command cannot be found in the current view. Check
whether this command is correct and whether it is in the correct view.
----End
Modifying a Script
This topic describes how to modify a script of an NE.
Prerequisites
The script must exist on the NE.
Context
The feature you have purchased may obtain or use some personal information of users when
providing services or maintenance. Therefore, you are obliged to formulate a privacy policy
according to the applicable law and take sufficient measures to keep the personal information
secure.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Script Management > Script Management from the main menu.
Step 4 Choose NE List from the navigation tree. Then, select the script to be modified under an NE
node.
If sensitive data, such as a user's password, occurs in the script modification process, click Encrypt and
enter the sensitive data in the displayed dialog box.
----End
Exporting Scripts
This topic describes how to export scripts. You can use the tool to export NE scripts. The exported
scripts can be used for follow-up script verification or fault location, and provide reference for
the configuration of other NEs.
Context
The feature you have purchased may obtain or use some personal information of users when
providing services or maintenance. Therefore, you are obliged to formulate a privacy policy
according to the applicable law and take sufficient measures to keep the personal information
secure.
You can choose to export some scripts or all scripts as required.
Procedure
l To export some scripts, do as follows:
1. Log in to the U2000 client.
2. Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu (traditional style); alternatively, double-click Fix-
Network NE Configuration in Application Center and choose Configuration >
Router/Switch/Security Configuration > Plug-and-Play Management from the
main menu (application style).
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.
3. Choose Script Management > Script Management from the main menu.
4. Choose NE List from the navigation tree. Then, click the NE whose scripts need to
be exported. All scripts of the NE are displayed in the right pane.
5. Hold down Ctrl while selecting the scripts to be exported. Right-click these scripts
and choose Export Script from the shortcut menu.
Alternatively, choose Script Management > Script > Export Script from the main
menu.
6. In the dialog box that is displayed, click the Save File option button, and then click
OK. Select the required path and click Save.
Users can modify the exported script as needed and then import it into the U2000.
NOTE
If the Internet Explorer is used, the Save As dialog box is displayed. Select the path for saving the
exported file.
l To export scripts of all NEs, do as follows:
1. Log in to the U2000 client.
2. Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu (traditional style); alternatively, double-click Fix-
Importing Scripts
This topic describes how to import scripts. You can use the tool to import the scripts of other
NEs to the target NE. If the methods of configuring different NEs are similar, this function
greatly improves the efficiency of making scripts.
Context
The feature you have purchased may obtain or use some personal information of users when
providing services or maintenance. Therefore, you are obliged to formulate a privacy policy
according to the applicable law and take sufficient measures to keep the personal information
secure.
You can import scripts for one NE or multiple NEs as required. The imported scripts do not
affect services running on NEs.
Procedure
Step 1 Log in to the U2000 client.
Step 2 Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu (traditional style); alternatively, double-click Fix-Network
NE Configuration in Application Center and choose Configuration > Router/Switch/
Security Configuration > Plug-and-Play Management from the main menu (application
style).
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 Choose Script Management > Script Management from the main menu.
Step 4 Choose NE List from the navigation tree. All NEs are displayed in the right pane.
Step 5 Select one or more NEs for which scripts need to be imported, right-click, and then choose
Import Script from the shortcut menu.
Alternatively, choose Script Management > NE > Import Script from the main menu.
Step 6 In the dialog box that is displayed, click Browse to choose the scripts to be imported.
----End
Verifying a Script
This topic describes how to verify the script for an NE in offline mode to check the script syntax
according to the related command set.
Prerequisites
l Created scripts must exist. For details about how to create a script, see Creating a Script
Manually.
l NE version and NE type must be set correctly for the specified NE.
l The command set for the NE whose script needs to be verified must exist on the plug-and-
play management module or have been imported into the plug-and-play management
module.
Context
The feature you have purchased may obtain or use some personal information of users when
providing services or maintenance. Therefore, you are obliged to formulate a privacy policy
according to the applicable law and take sufficient measures to keep the personal information
secure.
Click the Script tab and select a script under the NE. The number of errors in the script is
automatically displayed above the Script Configuration area.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Script Management > Script Management from the main menu. In the NE List
navigation tree, select the script to be verified, right-click, and then choose Verify Script from
the shortcut menu.
Alternatively, choose Script Management > Script > Verify Script from the main menu.
Step 4 In the Verification Result dialog box, view the verification result for each command.
l Enter only the keyword of the command to be queried. Do not enter any command parameter.
l If the Verification Result is displayed as an Error, this command cannot be found in the current
view. Check whether this command is correct and whether it is in the correct view.
l If the verification result of a command is Ambiguous Match, take the following operations:
Click Close. In the text box for command query, enter the command and press Enter. The
value range for the parameter in the command is displayed. Based on this range, modify the
command in the Script Configuration area.
----End
Follow-up Procedure
If some script information does not need to be verified, refer to Setting Detect Option to select
relevant check items.
Combining Scripts
This topic describes how to combine multiple NE scripts into one script.
Prerequisites
l All NE scripts must be generated .
l The NE scripts must be correct.
Context
The feature you have purchased may obtain or use some personal information of users when
providing services or maintenance. Therefore, you are obliged to formulate a privacy policy
according to the applicable law and take sufficient measures to keep the personal information
secure.
This function supports the combining of multiple scripts of a single NE or all NEs.
Procedure
l To combine multiple scripts of a single NE, do as follows:
1. Log in to the U2000 client.
2. Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu (traditional style); alternatively, double-click Fix-
Network NE Configuration in Application Center and choose Configuration >
Router/Switch/Security Configuration > Plug-and-Play Management from the
main menu (application style).
Enter a user name and a password for logging in to the U2000 and click Login.
3. Choose Script Management > Script Management from the main menu.
4. Choose NE List from the navigation tree. Then, select the NE whose scripts need to
be combined. All scripts of the NE are displayed in the Script List area in the right
pane.
5. Select a script, right-click, and then choose Select All from the shortcut menu. All
scripts are selected.
6. Right-click these scripts and choose Combine Script from the shortcut menu.
Alternatively, choose Script Management > NE > Combine Script from the main
menu.
7. In the dialog box that is displayed, view the progress of combining scripts. When the
progress bar reaches 100%, click Close.
l To combine multiple scripts of all NEs, do as follows:
1. Log in to the U2000 client.
2. Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu (traditional style); alternatively, double-click Fix-
Network NE Configuration in Application Center and choose Configuration >
Router/Switch/Security Configuration > Plug-and-Play Management from the
main menu (application style).
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.
3. Choose Script Management > Script Management from the main menu.
4. Choose NE List from the navigation tree. Select an NE under the NE List node. Then,
select All from the Attribute drop-down list.
5. Click Query. The scripts of all NEs are displayed.
6. Select a script, right-click, and then choose Select All from the shortcut menu. All
scripts are selected.
7. Right-click these scripts and choose Combine Script from the shortcut menu.
Alternatively, choose Script Management > NE > Combine Script from the main
menu.
8. In the dialog box that is displayed, view the progress of combining scripts. When the
progress bar reaches 100%, click Close.
----End
Prerequisites
An NE must be created or imported.
Context
The feature you have purchased may obtain or use some personal information of users when
providing services or maintenance. Therefore, you are obliged to formulate a privacy policy
according to the applicable law and take sufficient measures to keep the personal information
secure.
NOTICE
Scheduled script deployment delivers configurations to a specified NE at a specified time. After
you deploy a script, rollbacks are not permitted, and service deletion or network interruption
may occur. Exercise caution when you perform this operation.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Script Management > Script Management from the main menu.
Step 4 Select the NE List node, right-click, and then choose Scheduled Deployment from the shortcut
menu.
Alternatively, choose Script Management > Scheduled Script Deployment from the main
menu.
Step 6 In the dialog box that is displayed, carefully read the instructions to learn any possible impact
on services and then click OK.
Step 7 In the Create Deployment Task dialog box, select Subnet or NE as the object to which the
script will be deployed. If NE is selected, you can enter the NE name, IP address, type, or version
for filtering.
Step 10 Specify the script to be deployed in a scheduled manner. Then, click Next.
NOTE
The script will be automatically deployed in a scheduled manner. Do not enter any MML command.
l Remarks
l Period
l Deployment Date, Deployment Frequency, and Start Time
Step 12 Click Finish.
Step 13 A record about the scheduled task is displayed in the Manage Scheduled Deployment Task
dialog box.
----End
Follow-up Procedure
After creating scheduled tasks, perform the following operations as required:
l Modify a scheduled task.
1. In the Manage Scheduled Deployment Task dialog box, select the scheduled task
to be modified, right-click, and then choose Modify Task from the shortcut menu.
2. After modifying the task, click Finish.
l Download logs related to a scheduled task.
1. In the Manage Scheduled Deployment Task dialog box, select the scheduled task
whose logs need to be downloaded, right-click, and then choose Download Log from
the shortcut menu.
2. In the dialog box that is displayed, select the time range for generating logs. Then,
click OK.
3. In the dialog box that is displayed, click Save File, and then click OK.
l Delete logs related to a scheduled task.
1. In the Manage Scheduled Deployment Task dialog box, select the scheduled task
whose logs need to be deleted, right-click, and then choose Clear Log from the
shortcut menu.
2. In the dialog box that is displayed, select the time range for generating logs. Then,
click OK.
3. In the dialog box that is displayed, click OK. Logs related to the scheduled task are
deleted from the server.
Context
BGP peer relationships between NEs can be created one by one or in batches. To BGP peer
relationships in batches, select Full Mesh or RR Mode.
Procedure
Step 1 Log in to the U2000 client.
Step 2 Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu (traditional style); alternatively, double-click Fix-Network
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Deployment Configuration > Deployment Configuration from the main menu.
Select Source NE Group and Sink NE Group as required. Once Source NE Group or Sink
NE Group is selected, set the selected parameter.
3. Click OK.
----End
Prerequisites
The plug-and-play management module and new NEs are directly connected through network
cables.
Context
After the DHCP service is enabled, DHCP packets are exchanged between the plug-and-play
management module and NEs. After receiving a DHCP request packet from a new NE, the plug-
and-play management module assigns an IP address to the NE's interface directly connected to
the plug-and-play management module to enable the device management channel.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Deployment Configuration > DHCP Direct Mode Remote Commissioning from the
main menu.
Step 4 In the dialog box that is displayed, set the IP address to be assigned, mask to be assigned, and
IP address of the DHCP server, and click Start.
----End
Context
The information about some NEs or all NEs can be exported as needed.
Procedure
l To export information about some NEs into a file, perform the following operations:
1. Log in to the U2000 client.
2. Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu (traditional style); alternatively, double-click Fix-
Network NE Configuration in Application Center and choose Configuration >
Router/Switch/Security Configuration > Plug-and-Play Management from the
main menu (application style).
Enter a user name and a password for logging in to the U2000 and click Login.
3. Choose Script Management > Script Management from the main menu.
4. Choose NE List from the navigation tree.
5. Hold down Ctrl and select the desired NEs in the right-hand NE List area.
6. Right-click the selected NEs and choose Export NE from the shortcut menu.
7. In the dialog box that is displayed, click the Save File option button and click OK.
Users can modify the exported NE list as needed and then import it into the U2000.
NOTE
If the Internet Explorer is used, the Save As dialog box is displayed. Select the path for saving the
exported file.
l To export information about all NEs into a file, perform the following operations:
1. Log in to the U2000 client.
2. Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu (traditional style); alternatively, double-click Fix-
Network NE Configuration in Application Center and choose Configuration >
Router/Switch/Security Configuration > Plug-and-Play Management from the
main menu (application style).
Enter a user name and a password for logging in to the U2000 and click Login.
3. Choose Script Management > Script Management from the main menu.
4. Choose NE List from the navigation tree.
5. Click Export All NEs in the right-hand NE List area.
6. In the dialog box that is displayed, click the Save File option button and click OK.
Users can modify the exported NE list as needed and then import it into the U2000.
NOTE
If the Internet Explorer is used, the Save As dialog box is displayed. Select the path for saving the
exported file.
----End
Prerequisites
NEs must exist in the NE list.
Procedure
Step 1 Choose Deployment Configuration > DHCP Remote Commissioning (Software
Commissioning Engineer) from the main menu.
Step 2 On the NE Monitoring Status tab, select an NE and click Ping.
Step 3 In the dialog box that is displayed, click Ping.
NOTE
In this dialog box, you can also enter the IP address of another NE to perform a ping test.
----End
Result
l If the operation is successful, it indicates that the destination host is reachable. In the Result
area, the information indicating the normal connection is displayed. The information
includes the number of sent packets, number of received response packets, percentage of
no-response packets, and minimum, maximum, and average response time.
l If the operation fails, it indicates that the destination host is unreachable and the network
connectivity or line failure cannot be detected. The Request timed out message is
displayed. Check whether the route is reachable or whether the NE is online.
Context
The feature you have purchased may obtain or use some personal information of users when
providing services or maintenance. Therefore, you are obliged to formulate a privacy policy
according to the applicable law and take sufficient measures to keep the personal information
secure.
Procedure
Step 1 Log in to the U2000 client.
Step 2 Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu (traditional style); alternatively, double-click Fix-Network
NE Configuration in Application Center and choose Configuration > Router/Switch/
Security Configuration > Plug-and-Play Management from the main menu (application
style).
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 Choose Templates Management > Templates Management from the main menu.
Step 4 Optional: In the Template navigation tree, right-click Template and choose Create Folder
from the shortcut menu.
Alternatively, choose Template Management > Folder > Create Folder from the main menu.
Step 5 Optional: In the Create folder dialog box, enter a folder name and click OK.
Step 6 In the Template List navigation tree, choose Templates or Project Template, right-click, and
choose Create Template from the shortcut menu.
Alternatively, choose Template Management > Folder > Create Template from the main
menu.
Step 7 In the Create Template dialog box, click the Common Template option button.
Step 8 Select a path to which the template to be saved, specify the template name, describe the template,
set NE type, NE version, and the DCN mode for it, and click OK.
Step 10 In the Insert dialog box, select a value from the Select View drop-down list.
Step 11 In the Query Command field, enter a keyword contained in the desired command.
All commands containing this keyword are displayed in the query result area.
Step 12 Click to add the desired commands to the list of selected commands. Click OK.
Click OK.
If command verification succeeds, the commands are inserted into the template. If command
verification fails, the message Failed to verify the script is displayed. Correct the commands
and insert them into the template.
The template is displayed in the navigation tree, and details about the template are displayed in
the Template Configuration area.
----End
Prerequisites
Only engineers with knowledge and experience on the VTL can perform operations described
in this section to define command scripts for NEs.
Context
l The feature you have purchased may obtain or use some personal information of users when
providing services or maintenance. Therefore, you are obliged to formulate a privacy policy
according to the applicable law and take sufficient measures to keep the personal
information secure.
l Velocity is a Java-based template engine and can use objects defined by Java code by means
of a template language.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Templates Management > Templates Management from the main menu.
Step 4 In the Template List navigation tree, right-click Template List and choose Create Folder from
the shortcut menu.
Alternatively, choose Template Management > Folder > Create Folder from the main menu.
Step 5 In the Create folder dialog box, enter a folder name and click OK.
Step 6 In the Template List navigation tree, right-click Template List and choose Create Template
from the shortcut menu.
Alternatively, choose Template Management > Folder > Create Template from the main
menu.
Step 7 In the Create Template dialog box, click the VTL Template option button.
Step 8 Select a path to which the template to be saved, specify the template name, describe the template,
set NE type, NE version, and the DCN mode for it, and click OK.
Step 9 In the Modify dialog box, select a value from the Select View drop-down list.
Step 11 Click Check or Next. The system automatically checks the VTL. If the VTL is correct, the
verification succeeds and click Finish. If the VTL is incorrect, modify the VTL script.
Step 12 In the Set the Variables dialog box, enter values of the attributes associated with variables as
required.
The template is displayed in the navigation tree, and details about the template are displayed in
the Template Configuration area.
----End
Applying a Template
Quickly generate a configuration script by applying a template.
Context
Both custom and general templates can be applied.
NOTICE
The feature you have purchased may obtain or use some personal information of users when
providing services or maintenance. Therefore, you are obliged to formulate a privacy policy
according to the applicable law and take sufficient measures to keep the personal information
secure.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Templates Management > Templates Management from the main menu.
Step 4 In the Template navigation tree, select the desired template, right-click, and choose Apply
Template from the shortcut menu.
Alternatively, choose Template Management > Template|Systemplate > Apply Template
from the main menu.
Step 5 In the Select NE area of the Apply Template dialog box, select the desired NE and click
Next.
In the Select Template area of the Apply Template dialog box, you can select multiple
templates and apply them to an NE or select a template and apply it to multiple NEs, and click
Next.
Step 6 On the Set Parameter tab, set command parameters and click Finish.
NOTE
l In a command, a parameter must be set if it is marked with an asterisk (*) or the value of Necessary
for it is Yes. If such a parameter is not set, the generated script does not contain the command.
l If multiple templates are selected, set the parameters for each template.
Step 7 In the dialog box that is displayed, confirm whether to deploy the script immediately and then
click deploy and clear scripts or Deploy Script to jump to Deploying Scripts.
NOTE
The Deploy and Clear Script option allows a script to be automatically deleted after deployment completes
or the deployment window is closed, improving deployment efficiency.
----End
Follow-up Procedure
1. Click the Script Management tab.
2. Choose the NE to which the template has been applied from the NE List navigation tree.
You can find that the configuration script is displayed under the NE and the name of the
script is the same as that of the applied template.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose System Management > Set SYSTEM ID Rule from the main menu.
l Select Calculated according to Loopback IP Address and IGP ID, set the IGP ID and
accumulative value, and select or deselect Configure By Role. If you select Configure By
Role, configure the device role.
----End
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose System Management > Set Global Options from the main menu.
Parameter Description
Deploy master/slave NE's If the check box is selected, the plug-and-play management
access ring script module applies basic access-side configurations to
automatically when CSG NE aggregation site gateways (ASGs) after cell site gateways
belongs to it is getting online (CSGs) go online. The check box needs to be selected when
master/slave NE's do not have basic configurations.
By default, this check box is selected.
Deploy master/slave NE's Peer If the check box is selected, the plug-and-play management
script automatically when module applies Border Gateway Protocol (BGP) peer
CSG NE belongs to it is getting configurations to master/slave NE's after CSGs go online.
online By default, this check box is selected.
Link interface description If the check box is selected, the plug-and-play management
locale module generates interface description in the format of
To_Peer device name_Peer port number_Peer loopback
IP address.
By default, this check box is not selected.
When NE get online with some If the check box is selected, the plug-and-play management
link haven't been merged, module deploys configurations as planned when the NE
deploy interface scripts links are not connected.
according to link planning By default, this check box is not selected.
DHCP Options
Deploy Script Automatically If this check box is selected, the plug-and-play management
module applies a script after establishing a management
channel with an NE by means of plug-and-play.
If this check box is not selected, you can apply scripts
manually.
By default, this check box is selected.
Parameter Description
Disable Relay Automatically If this check box is selected, DHCP relay is automatically
disabled for the upstream NE after the plug-and-play
management module assigns an IP address to and configures
a default route for the new NE.
NOTE
If multiple new NEs are connected to the upstream NE, do not select
this check box. Otherwise, DHCP relay is disabled for the upstream
NE and other NEs cannot communicate with the plug-and-play
management module using DHCP after one of the new NEs is
connected to the plug-and-play management module.
By default, this check box is selected.
Remove Default PnP Route During the process of using plug-and-play to create an NE,
Configuration Automatically a default route destined for the plug-and-play management
module is configured for the new NE.
If this check box is selected, the plug-and-play management
module deletes this default route after a script is applied to
the new NE.
By default, this check box is not selected.
Synchronize Uplink NE If the sysname for the upstream NE is different from that in
sysname Automatically the planning table, the plug-and-play management module
changes the sysname in the planning table to the one for the
upstream NE.
By default, this check box is not selected.
Update Relay Interface IP If this check box is selected, the plug-and-play management
Addresses of Uplink NE module updates the IP address of the relay interface on the
Automatically upstream NE after a script is applies to a new NE.
By default, this check box is not selected.
Parameter Description
Step 4 Optional: On the Extend Script Settings tab, set related parameters and click OK.
Name Description
Merge Extend Script to If this check box is selected, the extended script generated using
Basic Configuration Script the extended template selected when the planning table is
Automatically exported is automatically integrated into the basic
configuration script.
By default, this check box is selected.
Sort DCN Configuration by If this check box is selected, the query result is sorted by ring
Ring Automatically when you view the data communication network (DCN) link
list.
NOTE
Navigation path for viewing the DCN link list: Choose Data
Planning > DCN Planning from the navigation tree on the Automatic
NE Configuration tab.
By default, this check box is not selected.
Increment update default If this check box is selected, the plug-and-play management
template module incrementally updates the default template.
By default, this check box is selected.
Display links for which no If this check box is selected, links for which no ring is planned
ring is planned in the DCN are displayed in the DCN view.
view By default, this check box is not selected.
----End
Procedure
Step 1 Log in to the U2000 client.
----End
Template introduction
Template functions: A template provides standardized configurations. You can use a template
to automatically generate a basic configuration script in batches and deploy the script to a device.
You can then use the U2000 to manage the device.
A template is displayed on an interface in the form of check boxes, configuration items, default
values, reference commands, and parameter flags (can be hidden).
l System Template: templates predefined in the system, which are mainly inherited from
earlier versions.
l MBB IPRAN Baseline Template: baseline template provided by the solution.
l Common Configuration Template: common configuration templates.
l Project Template: user-defined templates. If a "save as" operation is performed for
templates in System Template, MBB IPRAN Baseline Template, and Common
Configuration Template, the templates are placed under Project Template.
NOTE
You cannot insert, modify, or delete a command but can change the default parameter values in System
Template, MBB IPRAN Baseline Template, and Common Configuration Template. You can save a
template to Project Template as required. You can then insert, modify, and delete commands and
parameter values.
Parameter Fixed For a fixed parameter, set the default value for the configuration
values item in the template. The default value is fixed for all deployment
objects (interfaces, boards, or devices).
This rule applies to fixed parameters.
Variable For a variable parameter, retain an empty default value for the
configuration item in the template. After generating a planning
table, you can set variable parameter values in the planning table.
This rule applies to variable parameters.
Deploymen Interface When customizing a template, you can customize the configuration
t objects to be deployed as an interface-, board-, or device-level
Board configuration. To deliver the configuration to multiple interfaces,
Device boards, or devices, you can add multiple configuration items (fixed
parameters are used, which applies when few interfaces, boards, or
devices are available). You can also retain empty default values in
the template, export the template as a planning table, and set
multiple interface, board, or device names in the planning table
(variable parameters are used, which applies when a large number
of interfaces, boards, or devices are available).
Shortcut icons
Icon Name Function
Context
NOTICE
l The feature you have purchased may obtain or use some personal information of users when
providing services or maintenance. Therefore, you are obliged to formulate a privacy policy
according to the applicable law and take sufficient measures to keep the personal information
secure.
l When customizing a template configuration item or inserting a command, ensure that the
mapping command of this configuration item matches the type and version of the device to
which the command is to be delivered. This helps avoid the delivery fault due to the device's
unsurpport for the command. For example, the clock ethernet-synchronization enable
command, currently supported only by VRPv5 devices, is inserted to the template. If this
template is deployed to a VRPv8 device, an error message is returned indicating that the
command is not supported.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Click the Template Management tab. Choose Common Configuration Template > Eth-
Clock from the Templates navigation tree.
Step 4 Click Save As. Enter a template name, and set the NE type and version.
Right-click a parameter to be deleted, and then choose Delete from the shortcut menu. In this
example, the content in the red box is deleted.
Click Save.
Select Interface Name, and click Insert. In the Insert Command dialog box, set Select
View and paste the command to the blank area.
NOTE
In fixed parameter scenarios, parameter values must be set for the command inserted here.
Click OK. You can view configuration items and default values in Template Configuration.
NOTICE
Check whether the configuration items in a template match the type and version of the device
to which the template is to be delivered. For example, the clock ethernet-synchronization
enable command, currently supported only by VRPv5 devices, is inserted to the template. If this
template is deployed to a VRPv8 device, an error message is returned indicating that the
command is not supported.
----End
Procedure
Step 1 Log in to the U2000 client.
Step 2 Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu (traditional style); alternatively, double-click Fix-Network
NE Configuration in Application Center and choose Configuration > Router/Switch/
Security Configuration > Plug-and-Play Management from the main menu (application
style).
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 Select a template built in the system.
Click the Template Management tab. Choose Common Configuration Template > Eth-
Clock from the Templates navigation tree.
Step 4 Click Save As. Enter a template name, and set the NE type and version.
NOTICE
Check whether the configuration items in a template match the type and version of the device
to which the template is to be delivered. For example, the clock ethernet-synchronization
enable command, currently supported only by VRPv5 devices, is inserted to the template. If this
template is deployed to a VRPv8 device, an error message is returned indicating that the
command is not supported.
Click Save.
Step 7 Insert a command.
Select Interface Name, and click Insert. In the Insert Command dialog box, set Select
View and paste the trap-threshold crc-error packet-error-ratio alarm-threshold
INTEGER<1-9> INTEGER<1-5> [ resume-threshold INTEGER<1-9> INTEGER<1-6> ]
[ trigger-lsp ] command to the blank area.
NOTE
In variable parameter scenarios, parameter values do not need to be set for the command inserted here.
Step 8 Click OK. The following figure shows the generated configuration items, but the default values
are empty.
Set parameter values or generate a planning table based on the actual plan. Interface Name
parameters are used as an example.
l If few Interface Name parameters need to be configured, click Copy and then Paste the
Interface Name parameters to be configured. Then set default values and click Save.
l If a large number of Interface Name parameters need to be configured, skip this step. Export
the planning table and set variable parameter values in the planning table.
NOTE
l If a planning table needs to be generated, you can manually modify configuration item names as
required to help identify configuration items in the planning table. Ensure that no duplicate names exist
when modifying configuration item names. If multiple configuration items have the same name, only
one configuration item among them can be exported.
l If the planned value of a configuration item is the same for all NEs, you can configure the value as the
default value in the template.
l The planning table records the corresponding template ID. If a configuration item has a default value,
only the default value is recorded in the template and the configuration item is not exported to the
planning table. Only the configuration items with empty default values are exported to the planning
table.
Under the Project Template node of the template navigation tree, right-click the edited template
and choose Generate Planning Table from the shortcut menu.
Step 10 In the Generate Planning Table dialog box, set Template data Table to a desired value, for
example, 10.
Click OK.
NOTE
You can copy the NE sysname and interface information from the original planning table and paste it to
the newly generated planning table.
The mappings are as follows:
l The NE sysname column in the original planning table is pasted to the NE sysname column in the
new planning table.
l The Interface Name column in the original planning table is pasted to the Interface Name column in
the new planning table.
l The Uplink NE sysname column in the original planning table is pasted to the location following the
NE sysname column in the new planning table.
l The Interface Name of Uplink NE column in the original planning table is pasted to the location
following the Interface Name column in the new planning table.
After the pasting is complete, check the new planning table. If a sub-interface is available, delete the row
on which the sub-interface resides.
Click the Script Management tab. Right-click NE List and choose Import Planning Table
from the shortcut menu.
Step 15 Select the newly generated planning table and click Import.
Step 16 After the import is successful, close the message dialog box.
The configuration is complete and waits to be deployed.
----End
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Click the Script Management tab. Right-click NE List and choose Batch Script
Deployment from the shortcut menu.
NOTE
Step 4 In the Batch Script Deployment dialog box, set the edited template keyword in Match.
Step 5 Add the obtained script to the selected scripts, and click Next.
Step 6 In the Deploy Script dialog box, browse the scripts to be deployed. In the dialog box that is
displayed, click Deploy all.
Step 7 Optional: In the dialog box that is displayed, enter the NE login password again and deploy the
configuration.
NOTE
This dialog box is displayed only when NE login requires password authentication and a delivered script
involves modification of the following four modes.
l Change a VTY password.
l Change the VTY authentication mode to aaa.
l Delete the authentication mode.
l Change the current login user password in aaa mode.
----End
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Click the Script Management tab. Right-click NE List and choose Create NE from the shortcut
menu.
Step 4 In the dialog box that is displayed, set parameters, such as the NE name, IP address, NE type,
and NE version. Click OK.
NOTE
l To manage multiple NEs, repeat the preceding steps to create multiple NEs in turn.
l If the type and version of an NE to be created do not exist, you may not set them. After the creation is
complete, right-click the NE in the NE list and choose Obtain Command Set from the shortcut menu.
In the NE List navigation tree, right-click the created RAN CE NE and choose Create Script
from the shortcut menu.
Step 7 On the Script Configuration tab page, click Modify. Paste a command to be deployed on the
blank area.
NOTICE
Check whether the configuration items in a template match the type and version of the device
to which the template is to be delivered. For example, the clock ethernet-synchronization
enable command, currently supported only by VRPv5 devices, is inserted to the template. If this
template is deployed to a VRPv8 device, an error message is returned indicating that the
command is not supported.
After you click Save, check whether the number of errors is 0. If the number of errors is not 0, modify the
command format correctly and click Save.
Step 10 In the Generate Template dialog box, ensure that parameter values are set correctly and click
OK.
Step 11 In the Create Template dialog box, ensure that parameter values are set correctly and click
OK.
Click the Template Management tab, select the created template under the Project
Template node of the template navigation tree. In Template Configuration, perform the
following operations:
NOTE
l Ensure that no duplicate names exist when modifying configuration item names. If multiple
configuration items have the same name, only one configuration item among them can be exported.
l If the planned value of a configuration item is the same for all NEs, you can configure the value as the
default value in the template.
l The planning table records the corresponding template ID. If a configuration item has a default value,
only the default value is recorded in the template and the configuration item is not exported to the
planning table. Only the configuration items with empty default values are exported to the planning
table.
Under the Project Template node of the template navigation tree, right-click the edited template
and choose Generate Planning Table from the shortcut menu.
Step 14 In the Generate Planning Table dialog box, set Template data Table to a desired value, for
example, 10.
You can copy the NE sysname and interface information from the original planning table and paste it to
the newly generated planning table.
The mappings are as follows:
l The NE sysname column in the original planning table is pasted to the NE sysname column in the
new planning table.
l The Interface Name column in the original planning table is pasted to the Interface Name column in
the new planning table.
l The Uplink NE sysname column in the original planning table is pasted to the location following the
NE sysname column in the new planning table.
l The Interface Name of Uplink NE column in the original planning table is pasted to the location
following the Interface Name column in the new planning table.
After the pasting is complete, check the new planning table. If a sub-interface is available, delete the row
on which the sub-interface resides.
Click the Script Management tab. Right-click NE List and choose Import Planning Table
from the shortcut menu.
Step 20 Select the newly generated planning table and click Import.
Step 21 After the import is successful, close the message dialog box.
Right-click NE List and choose Batch Script Deployment from the shortcut menu.
Step 23 In the Batch Script Deployment dialog box, set the edited template keyword in Match.
Step 24 Add the obtained script to the selected scripts, and click Next.
Step 25 In the Deploy Script dialog box, browse the scripts to be deployed. In the dialog box that is
displayed, click Deploy all.
----End
2.6 FAQ
Procedure
Step 1 The configurations of directly connected interfaces on ASGs or CSGs going online are ignored
if one of the following conditions is met:
l Basic configurations have not been applied to the peer NE.
l An IP address has been applied to the directly connected interface on the peer NE.
----End
Prerequisites
The sysname of the gateway NE must be the same as that specified in the planning data.
Context
The planned and actual links do not meet the following automatic merge conditions:
l The NE at one end of the planned link has been merged with the counterpart of the actual
link.
l The interface name of the NE at the other end of the planned link is the same as that of the
actual link.
NOTE
In the initial state, if a gateway NE is added and the sysname for the new gateway NE is consistent with
that in the link planning table, data about the new gateway NE is merged by precedence.
Procedure
Step 1 Use either of the following methods to address this problem:
l If the sysname of the planned GNE is different from that of the actual GNE, modify the link
planning table and import it again.
If only the planned interface information is different from the actual interface information,
choose Deployment Configuration > Deployment Configuration from the main menu of
the plug-and-play management module. Select Link Plan and DCN Planning from the
navigation tree and modify interface information.
----End
Procedure
Step 1 Use any of the following methods:
l Enable the automatic report function for the added gateway NE when adding it.
l After the gateway NE is added, right-click in the blank area of the DCN view and choose
Synchronize from the shortcut menu.
l After the gateway NE is added, right-click it in the navigation tree and choose Enable
Automatic Report from the shortcut menu.
----End
Procedure
Step 1 On a private network, a gateway NE detects a new online NE, selects an IP address from the
gateway NE address pool, assigns it to the new online NE as the data communication network
(DCN) management IP address, and adds the new online NE to the DCN view.
----End
Context
Possible causes are as follows:
l The NEs discovered during the synchronization encounter a Telnet failure or NE IP address
conflict. The gateway NE cannot log in to the NEs to synchronize their link information.
l The display lldp neighbor command output shows that the NEs have no links.
Procedure
Step 1 Check whether the NEs discovered during the synchronization are in the normal or unknown
state. If the NEs fail go online, check whether the Telnet passwords are correct. If an NE IP
address conflict occurs, log in to the NEs and change their NE IP addresses. Then perform
synchronization again.
Step 2 If the NEs function properly but have no links, manually log in to the NEs and run the display
lldp neighbor command to check the NEs.
----End
Context
After gateway NE data is synchronized, an NE IP address conflict occurs between an NE and a
discovered NE or an NE added to the U2000.
Procedure
Step 1 Log in to the NEs encountering the NE IP address conflict, change their NE IP addresses.
system-view
dcn
ne-ip X.X.X.X XX
If the configured NE IP address conflicts with the IP address of another NE, the following
message is displayed. In this situation, you must enter another IP address.
Error: The specified address conflicts with another address.
Step 2 Select the NEs in the DCN view. Right-click the NEs and choose the desired shortcut menu
option to check whether an NE IP address conflict persists.
----End
Context
Resolve the problem based on the specific cause.
Procedure
Step 1 View details about each step in the application process and locate the cause.
Step 2 View the running logs about the associated NE and the commands that fail to be applied. The
running logs include the logs about applying basic configurations.
----End
Context
The Telnet parameters in the configuration template are inconsistent with those for logging in
to the NE.
Procedure
Step 1 In the DCN view, select the NE with the Telnet login failure, right-click, and choose Set NE
Telnet/STelnet Parameter from the shortcut menu. Then set Telnet login parameters.
----End
Access Ring Disappears from the DCN Pre-deployment View After a Planning
Table Is Imported to Enable Next Access Ring to Go Online
Procedure
Step 1 The DCN pre-deployment view is for making NEs go online. If all NEs on an access ring have
been online, DCN deployment is not affected even the access ring is not displayed in the pre-
deployment view. If only some of the NEs on the access ring have been online, design all the
access rings together and use the UniSTAR to export data about all the access rings. In this way,
all the access rings can be displayed in the DCN pre-deployment view.
----End
Procedure
Step 1 A new script can be applied incrementally when a DCN NE goes online.
----End
Background
When the data communication network (DCN) function is used, the number of NEs in an access
ring must be less than 500 because of Open Shortest Path First (OSPF) limitation. If the number
exceeds 500, the access ring must be partitioned, and each new ring must have a unique OSPF
process ID.
Solution
1. Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu (traditional style); alternatively, double-click Fix-
Network NE Configuration in Application Center and choose Configuration > Router/
Switch/Security Configuration > Plug-and-Play Management from the main menu
(application style).
2. Choose NE Online Protocol from the navigation tree, select DCN Networking, click
Apply.
3. Choose Commissioning NE Online from the navigation tree, click Commissioning NE
Online. In the dialog box that is displayed, click OK.
4. In DCN Management for Routers, select an aggregation site gateway (ASG) from the
navigation tree, right-click, and choose NE Explorer from the shortcut menu.
5. Choose Route Management > OSPF Route > OSPF Process from the service tree.
6. In the OSPF Process dialog box, click Create. In the dialog box that is displayed, set
parameters.
On the General tab, set the following parameters.
On the Area tab, click Create and set the following parameters.
7. Click OK twice.
8. Choose System Management > DCN Communication Management > DCN
Management from the service tree.
9. On the Port Settings tab, click the GE option button.
10. Select the interface to be connected to a new access ring, right-click, and choose Config
OSPF Process from the shortcut menu.
11. In the dialog box that is displayed, set OSPF parameters to associate the interface with the
new OSPF process.
New NEs Are Displayed as Third-party NEs When the DCN Function Is Used
Background
As the required NE mediation package is not loaded for the new NE type, newly added NEs are
displayed as third-party NEs when the DCN function is enabled.
Solution
1. Check whether the type of the managed NEs is a new NE type that requires an NE mediation
package.
2. Load the required NE mediation package.
Navigation path for loading the NE mediation package: Choose Administration > NE
Mediation Package Management from the main menu (traditional style); alternatively,
double-click Fix-Network NE Configuration in Application Center and choose
Administration > NE Mediation Package Management from the main menu (application
style).In the NE Mediation Package Management dialog box, click the Load Router/
Switch NE Mediation Package tab.
3. Delete the original third-party NEs from the topology and re-create NEs one by one or in
batches.
Procedure
Step 1 Some basic configurations deployed by the previous NE lead to route re-calculation; as a result,
an NE temporarily fails to connect to the previous NE.
Route flapping occurs temporarily. Wait about 1 minute and then re-deploy the NE
configurations.
----End
How to Solve the Problem Where Links Fail to Be Displayed in the DCN View
When Link Planning Is Inconsistent with the Actual Connection
If the link planning is inconsistent with the actual connection after NEs get online, links fail to
be displayed in the DCN view. How do I solve the problem?
Procedure
l Method 1: Modify links as planned to ensure that the actual link configurations are
consistent with the planning data.
l Method 2: In the plug-and-play planning window, modify the link information to be the
same as the planning data.
NOTE
The modification on the plug-and-play module will not be synchronized to the UniSTAR. You must
manually modify the planning data on the UniSTAR.
----End
Procedure
Step 1 The NE name is too long. The current version supports a maximum of 50 characters in an NE
name. Change the NE name to contain no more than 50 characters.
----End
Context
If the Telnet user names and passwords used before and after NE online are different, the NE
fails to get online.
Procedure
Step 1 In the DCN view, correct the Telnet user name and password of the NE marked with a blue
question mark and perform login again.
NOTE
----End
NEs in the DCN View Fail to Be Identified After Online NE Data Is Synchronized
Some NEs fail to be identified in the DCN view after the online NE data is synchronized. How
do I solve the problem?
Procedure
Step 1 Check whether an NE waiting to get online is displayed in the Main Topology. If such an NE
exists, delete it.
Step 2 Check whether the interface information in the planning table is correct. For example, the
interface GigabitEthernet1/1/0 cannot be displayed as giga or GigabitEthernet 1/1/0 which
contains too may spaces.
Step 3 Check whether the link planning data in the planning table is correct.
Step 4 Check whether the UniSTAR of an early version is used. Mark 10GE interfaces with the XGE
identifier.
----End
Some Connected Device Fibers Failed to Be Discovered in the DCN View and
Displayed in Orange
Some successfully connected device fibers fail to be discovered in the DCN view and are
displayed in orange. How do I solve the problem?
Procedure
Step 1 DCN can be enabled on only the first eight interfaces on every board. Interfaces with the last
digit as a multiply of 4 are not enabled with DCN, such as GE7/1/4 and GE5/3/8. If such an
interface needs to be enabled with DCN, log in to the device where the interface resides and
manually enable DCN on the interface.
----End
Only Core Ring But Not Aggregation Ring Displayed in the DCN Pre-deployment
Topology
After gateway NEs are added to the U2000, the core and aggregation rings are pre-deployed for
the gateway NEs. The DCN pre-deployment topology displays only the core ring instead of the
aggregation ring. How do I solve the problem?
Procedure
Step 1 During Unistar planning, the primary and secondary NEs are selected for the subnet of the core
ring. When the UniSTAR is used to export the core and aggregation planning table, the check
box of not exporting aggregation ring data is selected.
----End
Procedure
Step 1 Check whether the names of gateway NEs are changed on the U2000. Currently, NE names are
displayed as sysname in the DCN view. You must change the gateway NE names on the U2000
to be the same as those in the plug-and-play planning table and then add the gateway NEs again.
----End
Failure to Display the DCN Pre-deployment Topology of the Previous Access Ring
After the NEs on a New Access Ring Get Online
NEs get online based on the access ring. If NEs on an access ring get online and the planning
table is imported, the DCN pre-deployment topology of the previous access ring does not exist.
How do I solve the problem?
Procedure
Step 1 DCN pre-deployment is used for device online. If NEs on the previous access ring are all online,
the pre-deployment view does not need to be displayed, and the Main Topology displays the
interconnections. If not all NEs on the previous access ring are online, design the access ring
properly so that the planning tables about multiple access rings are exported by the UniSTAR,
and the DCN pre-deployment view is also contained.
----End
Procedure
Step 1 The current product versions do not support the automatic deployment of basic configurations
from gateways. Instead, gateways can deploy configurations only when an NE online alarm is
generated. If the DCN function is disabled from gateways, the basic configurations cannot be
deployed. Therefore, disable the DCN function after all devices get online.
----End
Telnet and SNMP Connection Failure After an Offline NE Gets Online Again after
Synchronization in the DCN View
An NE gets offline but is not deleted from the Main Topology. After the NE is synchronized in
the DCN view and gets online again, the Telnet and SNMP connections fail. How do I solve the
problem?
Context
If an offline NE is not deleted from the Main Topology, the default Telnet password of the NE
remains after NE synchronization. Therefore, the Telnet connection fails. The NE configurations
are empty; therefore, the SNMP connection fails.
Procedure
l Method 1 (recommended): Delete the offline NE from the Main Topology. Then make the
NE get online again in the DCN view.
l Method 2: Re-configure the initial NE login password to deploy basic configurations. If
this method is used, a message will be displayed indicating that the NE has been added to
the Main Topology.
----End
How to Handle the Problem Where the Actual and Initial Passwords Are
Inconsistent After the U2000 Is Upgraded
How to handle the problem where the actual and initial passwords are inconsistent after the
U2000 is upgraded?
Procedure
l Method 1: In the NE Login Parameters window of plug-and-play, change the initial NE
login password to the same as that of the actual password.
l Method 2: Right-click the NE password in the U2000 Main Topology and choose Tools >
Telnet from the shortcut menu to log in to the NE. Change the password on the NE.
----End
Context
If no planning data about the gateway NE exists and the system name of the gateway NE is
changed, the sysname name will be refreshed after synchronization. If planning data about the
NE exists, you must delete the gateway NE and then add it again.
Procedure
Step 1 Remove the gateway NE from the DCN view and modify the NE sysname in the Main Topology.
In addition, modify the NE sysname in the NE information on the plug-and-play management
module and add the gateway NE again.
----End
NEs Displayed in Blue in the DCN View but Gray in the Physical View
NEs are displayed in blue in the DCN view but gray in the physical view. How do I solve the
problem?
Procedure
Step 1 The loopback addresses of NEs may have not been configured and the NEs get online again.
You can delete the offline NEs from the Main Topology and make the NEs get online again.
----End
How Do I Solve the Problem Where a Route Fault in the Gateway NE Interrupts
the Process of Applying Basic Configurations
Symptom
A route fault in the gateway NE interrupts the process of applying basic configurations. In this
situation, the buttons used to apply basic configurations and preview configurations are all
grayed out, and the configurations cannot be applied again.
Fault Analysis
The NE and link status in the DCN view is not updated in a timely manner after the route fault
is rectified.
Solution
1. Restore the normal route status.
2. Close the DCN view and open it again. The button used to apply basic configurations will
automatically recover.
3. Apply the basic configurations again.
Symptom
After a Gateway NE goes offline, its status displayed in the Main Topology is Offline, but the
status displayed in the DCN view is Unknown, and the Gateway NE is marked in blue.
Fault Analysis
When only one Gateway NE is deployed, it cannot report offline messages if it goes offline. As
a result, its status displayed in the DCN view cannot be updated to Offline.
When active and standby Gateway NEs are deployed, the standby Gateway NE reports an offline
message for the active Gateway NE if the active Gateway NE goes offline and updates the active
Gateway NE status to Offline in the DCN view.
Solution
You can check the Gateway NE status in the Main Topology or on Gateway NE Tree on the
left side in the DCN view, and the displayed status is Offline.
No Link That Can Be Planned Is Displayed After an IPRAN Device Goes Online
Through the DCN
Symptom
No link that can be planned was displayed after an IPRAN device went online through the DCN.
Fault Analysis
An incorrect NE type was selected during DCN data planning in plug-and-play management.
Solution
1. Log in to the U2000 client.
2. Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu (traditional style); alternatively, double-click Fix-
Network NE Configuration in Application Center and choose Configuration > Router/
Switch/Security Configuration > Plug-and-Play Management from the main menu
(application style).
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.
3. On the Plug-and Play main menu, choose Deployment Configuration > Deployment
Configuration.
4. Click NE Information.
5. Select a record and click Modify. The Edit NE dialog box is displayed.
6. Select the correct NE type from the Role drop-down list.
Procedure
Step 1 Log in to the U2000 client.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Click the Basic NE Configuration tab on the navigation tree and select Customizing Basic
Configuration Solutions.
Step 4 Change Access-side IGP Assignment Rule to Unique in the master and slave NE pair.
----End
Symptom
NEs cannot go online through the DCN.
Fault Analysis
An excessive number of GNEs and non-GNEs exist on the live network, causing the U2000 to
frequently update NE information.
Procedure
Step 1 Partition a large-scale network as planned.
----End
Symptom
The NE types displayed in the DCN view are incorrect.
Procedure
Step 1 Delete NE-related records in the physical topology on the U2000 and in the DCN view before
deleting data of an NE and enabling the NE to go online.
----End
Solution
If an IP address allocation failure occurs during the plug-and-play management module
commissioning process in a DHCP scenario, use the following procedure to rectify the fault.
Start
Yes
Can DHCP running logs be a. Check packets and the NE
viewed? planning table.
No
Yes
Yes
No
No
End
b Check whether routes are Failed to Ping the Relay Interface on the
reachable. Upstream NE.
e Check that an IP address has been Go to the site, clear all configurations of the plug-
allocated to the NE or the NE and-play NE, and make it online again.
software is incorrect.
Solution
The following logs show the normal process that an NE goes online. Four packets are involved.
The packet does not contain Error but some information is marked red. This is because
information in the NE deployment planning table is inconsistent with packets reported by
NEs. Check the interface number of the NE to be deployed and the interface number,
VLAN, IP address, and name of the upstream NE in the planning table. The plug-and-play
management module considers packets different from planning information and does not
assign IP addresses even if the information uses different upper- or lower-case letters.
l 2011-06-01 17:40:42 Error:[Mismatch Gateway IP Address], Source
Interface:VlanIf or LoopBack 0/9/121, ESN:, Uplink NE:, Uplink Interface:,
Link VLAN:, Gateway:0.0.0.0, Datagram Type:DHCP_DISCOVER
Error packets sent by the CX600 V600R002C05 and earlier. These packets contain the
PortType0/14/442 field. Remote commissioning is supported only after NEs are upgraded.
Plug-and-Play Management Module Does Not Send a DHCP ACK Packet After
Receiving a DHCP Relay Packet
Symptom
The plug-and-play management module does not send a DHCP ACK packet after receiving a
DHCP Relay packet.
Fault Analysis
Possible causes are as follows:
l Routes are not configured on the PC where the plug-and-play management module is
installed.
l The NE running the current version does not support plug-and-play.
Solution
If the fault is generated because of cause 1, see Failed to Ping the Relay Interface on the
Upstream NE.
If the fault is generated because of cause 2, contact NE engineers to replace the NE with a later-
version one.
Fault Analysis
l The route between the plug-and-play management module and the upstream NE is
unreachable.
l The route between the NE directly connected to the plug-and-play management module
and the upstream NE is unreachable.
Solution
1. Check whether the route between the plug-and-play management module and the upstream
NE is reachable.
l On Windows, if the server has only one network interface, set the gateway IP address
of the network interface to the interface IP address of the peer device of the plug-and-
play management module.
l On Windows, if the server has multiple network interfaces, add a route: Open the CMD
window, enter route add 10.2.0.0 mask 255.255.0.0 10.3.0.0, and press Enter.
10.2.0.0 is the network segment where the IP address of the upstream NE interface
resides. 10.3.0.0 is the interface IP address of the NE connected to the network interface
on the plug-and-play management module server.
2. Check whether the route between the NE directly connected to the plug-and-play
management module and the upstream NE is unreachable.
a. IGP configurations on the network are incorrect. Check IGP configurations and
whether IGP is enabled on interfaces on each NE, especially whether an IP address
and IGP are configured for the upstream NE interface.
b. IGPs are configured at different layers based on processed on the network. The
upstream NE interface and the interface on the NE connected to the plug-and-play
management module server do not belong to the same IGP. Contact solution design
personnel to determine whether temporary route importing can be performed for IGP
to enable interworking between network-side interfaces at the access and aggregation
layers and implement the plug-and-play function.
c. Check whether the route to the plug-and-play management module server is
configured on the upstream NE of the NE to be deployed. Especially, check whether
IGP is enabled on interfaces on the NE connected to the plug-and-play management
module server.
Symptom
In the NE list on the Automatic NE Configuration tab page, the status of Interface Relay for
Uplink NE is Enable Failed.
Fault Analysis
Possible causes are as follows:
Solution
l If the fault is generated because of cause 1, perform the following operations:
1. Choose System Management > Global Options from the main menu of the plug-
and-play management module.
2. Select the Enable Relay Automatically check box.
l If the fault is generated because of cause 2, see Failed to Ping the Relay Interface on the
Upstream NE.
l If the fault is generated because of cause 3, change the upstream NE name in the planning
table to the actual name and import the planning table to the plug-and-play management
module.
Solution
Run the following commands on the upstream NE of the DHCP relay to check the DHCP packet
forwarding information, including the number of packets received by the NE to be deployed
(Client), the number of packets received by the plug-and-play management module (Server),
the number of packets sent by the NE to be deployed (Client), and the number of packets sent
by the plug-and-play management module (Server).
1. Connect to the upstream NE by means of STelnet and run the following commands:
reset dhcp relay statistics
display dhcp relay statistics
Fault Analysis
A firewall configured on an NE between the plug-and-play management module and the
upstream NE filters out DHCP packets.
Solution
Contact Huawei engineers to check whether a firewall is configured on an NE between the plug-
and-play management module and the upstream NE to filter out DHCP packets.
How to Configure the Transit NE When NEs Are Not Directly Connected
Symptom
A plug-and-play NE is connected to an upstream relay NE through a switch and the switch needs
to be configured to allow DHCP packets to pass.
Solution
Perform the following configurations on the switch to allow DHCP packets to pass:
1. Connect to the upstream NE by means of STelnet and run the following commands:
2. system-view
3. port trunk allow pass
4. port default vlan
Solution
To view plug-and-play logs on the server during fault location, perform the following operations:
Symptom
Configurations of the relay interface on the upstream NE, including the IP address, are empty.
When the plug-and-play NE is commissioned remotely, the following message is displayed in
NE running logs:
2012-05-24 17:13:04 Up link NE(ASG3)'s relay interface(eth 0/2/19)configuration is
empty, deploy the configuration immediately? Yes/No
sys
[ASG3-Ethernet0/2/19]display this
interface Ethernet0/2/19
undo shutdown
Fault Analysis
As the upstream NE interfaces are not fully planned, the applied script does not contain
configurations for the upstream NE's relay interface that connects to the plug-and-play NE going
online this time.
Solution
l In the NE running logs, click Yes. In the dialog box that is displayed, click Deploy
Script to apply a configuration script to the upstream NE's relay interface.
l Log in to the upstream NE using Telnet or STelnet to manually configure the relay interface.
Using STelnet to log in to the upstream NE is recommended.
Symptom
When the relay interface on the upstream NE goes Down, the following message is displayed
in NE running logs:
2012-05-24 17:01:05 The relay interface(gi 0/1/2,10.100.0.13/30) is physical Down,
please adjust DCN Planning or migration interface configuration of NE(RSG-ASG1)?
Fault Analysis
Possible cause 1: The upstream NE is not powered on.
Possible cause 2: The plug-and-play NE is not connected to the upstream interface as planned.
Possible cause 3: The upstream interface information provided in the planning table is incorrect.
Solution
l If the fault occurs because of possible cause 1, perform the following operation:
Check whether the plug-and-play NE goes online normally after the upstream NE is started
and its relay interface automatically goes Up.
l If the fault occurs because of possible cause 2, perform the following operation:
In the NE running logs, click adjust DCN Planning to modify the upstream NE interface
information.
l If the fault occurs because of possible cause 3, perform the following operations:
1. In the NE running logs, click migration interface configuration of NE(RSG-
ASG1) to migrate the upstream NE interface based on specific conditions.
2. In the dialog box that is displayed, select the target interface and click Migration.
3. In the dialog box that is displayed, click OK. The configurations of the original
interface are migrated to the target interface.
4. In the dialog box that is displayed, click OK. The configurations of the original
interface are deleted.
5. In the dialog box that is displayed, click OK. The configurations of the original
interface are completely migrated to the target interface.
6. Optional: If there are remaining configurations for the original interface after the
migration, contact Huawei technical support engineers.
Symptom
When the relay interface on the upstream NE goes Down or link disconnections are detected
after the plug-and-play NE goes online, the following message is displayed in NE running logs:
2012-05-24 17:28:05 Failed to check the connectivity of NE(ASG4)'s interface(gi
0/2/17,10.100.0.14/30) to NE(RSG-ASG1) interface(gi 0/1/2,10.100.0.13/30), change
the config of NE (ASG4) interface or migration interface configuration of NE(RSG-
ASG1)?
Fault Analysis
The physical connection is not implemented as planned, that is, the physical connection or
planned data is incorrect.
Solution
1. In the NE running logs, click change the config of NE (ASG4) interface or migration
interface configuration of NE(RSG-ASG1) to migrate the NE interface based on specific
conditions.
2. In the dialog box that is displayed, select the target interface and click Migration.
3. In the dialog box that is displayed, click OK. The configurations of the original interface
are migrated to the target interface.
4. In the dialog box that is displayed, click OK. The configurations of the original interface
are deleted.
5. In the dialog box that is displayed, click OK. The configurations of the original interface
are completely migrated to the target interface.
6. Optional: If there are remaining configurations for the original interface after the
migration, contact Huawei technical support engineers.
Symptom
The following message is displayed during NE status monitoring: Checking whether the
NE is offline.
Fault Analysis
When the plug-and-play NE is being commissioned remotely before it is fully connected, the
plug-and-play management module verifies whether the NE is offline. If the NE's management
IP address can be pinged or connected using Telnet, the verification succeeds and the NE is
online. If the NE's management IP address cannot be pinged or connected using Telnet, the NE
is offline.
NOTE
If the NE goes online but becomes offline later, rectify the fault on the U2000. For details, see U2000
Troubleshooting.
Solution
1. Check whether the U2000 server can ping the NE's management IP address. If the ping
fails, check and configure the route between them. For details, see Failed to Ping the Relay
Interface on the Upstream NE.
2. Check whether AAA user configurations on virtual terminals are consistent with the
planned data based on the script applying information in the NE running logs. If the AAA
authentication mode is configured for the virtual terminals but a local user related to AAA
authentication is not configured in the plug-and-play configuration template, the plug-and-
play NE will go offline. Go to the site, clear all configurations of the plug-and-play NE,
and make it online again.
3. Check information about script applying information in the NE running logs for IGP
configuration data.
l If the IGP type is IS-IS, check whether the isis circuit-type p2p command is configured
for NE interfaces. If the command is configured for the interface of the plug-and-play
NE but not for the relay interface on the upstream NE, the plug-and-play NE cannot go
online. The command must be configured for the relay interface.
l If the IGP type is OSPF, check whether the network segments of the plug-and-play NE's
interface and the upstream NE's relay interface are advertised to the area of the NE
OSPF process. If their network segment configurations are different, the plug-and-play
NE cannot go online. To address this problem, use Telnet to log in to the plug-and-play
or upstream NE to modify the related configurations.
4. Analyze IGP or BGP route configurations and ensure connectivity between the U2000
server and management IP address if the plug-and-play NE goes offline because of other
reasons.
How to Export an Extended Template to Plan the BGP Routing Policy and the
Frequency Synchronization Clock Priority of Ethernet Interfaces
How do I export an extended template to plan the BGP routing policy and the frequency
synchronization clock priority of Ethernet interfaces?
Procedure
Step 1 Choose System Management > Set Global Options > Extend Script Settings and select the
Merge Extend Script to Basic Configuration Script Automatically check box, which is
selected by default.
Step 2 On the Deployment Overview page, click Link Plan > Interconnection Relationship
Planning > Export the interconnection relationship planning template to plan.
Step 3 In the dialog box that is displayed, click Choose Extend Template.
Step 4 In the dialog box that is displayed, select an extended template, add it to the Selected
Template area, and click OK.
Step 5 In the Export Link Planning Table dialog box, click Export Link Planning Table and save
the link planning table.
Step 6 Open the link planning table and enter configurations, such as the link planning and ring
information. On the Template List tab, view the template contents. On the Other
Configuration tab, enter planning data about the extended template.
Step 8 On the Script Management tab, view extended scripts for the affected NE.
----End
Procedure
Step 1 Create a default template using one of the following methods:
l Set a template created using the wizard to a default template.
You can right-click a non-default template to specify it as a default template.
l Select a template from the template list and configure it as a default template.
Step 2 Import a link planning table. The link planning table automatically matches the default template.
----End
Fault Analysis
The baseline template or system-defined template is incorrectly modified and needs to be
restored to its default status.
Solution
1. Choose Templates Management > Templates Management from the main menu.
2. Select the desired baseline template or system-defined template from the navigation tree.
3. Click .
4. In the dialog box that is displayed, click OK.
Symptom
After a script in .doc format is copied to the plug-and-play management module and then saved,
garbled codes are displayed in the script.
Fault Analysis
The script that is copied carries information about the .doc format. The plug-and-play
management module fails to identify this format.
Solution
Copy contents in the script in .doc format to a file in .txt format, and then copy the file in .txt
format to the plug-and-play management module.
Symptom
The following figure shows a script copied from an NE. Many errors occur during script
verification.
Fault Analysis
You must delete the NE information before each command. For example, the NE information
such as [NE5000E], [NE5000E-ospf-1], and [NE5000E-GigabitEthernet1/0/0] must be
deleted.
Solution
If the script contains a great number of commands, use the finding/replacing function to delete
these characters in batches.
Symptom
1. Log in to the plug-and-play management module.
2. Choose Script Management > Script Management from the main menu. Then click NE
List in the navigation tree.
3. Right-click and choose Import Planning Table from the shortcut menu. The dialog box
that is displayed contains both Chinese and English words.
Fault Analysis
The plug-and-play management module uses the Browser/Server architecture. The GUI
language type depends on the server language and browser language. In that dialog box, the
language type of Browse depends on the browser language and the language type of other words
depends on the installation language of the server. If the server uses English but the browser
uses Chinese, both language types exist.
Solution
Change the browser language type from Chinese to English.
4. Click OK.
5. Click OK.
No Telnet and SNMP Parameter Scripts Are Generated and SNMP Read and Write
Community Strings Are Empty After the U2000 Is Upgraded and a Project Template
Is Imported
After the U2000 is upgraded and a customized project template is imported, no Telnet and Simple
Network Management Protocol (SNMP) parameter scripts are generated, and the SNMP read
and write parameters are empty. How do I resolve this problem?
Prerequisites
Parameters, such as AAA parameters and user password, have been backed up before the U2000
is upgraded, so that you can manually enter them after the U2000 is upgraded.
Procedure
Step 1 After the customized project template is imported, select it, and set Telnet parameters in the
AAA and User-interface configuration item and SNMP parameters in the SNMP
Configuration configuration item.
----End
Procedure
Step 1 On the Automatic NE Configuration tab, choose Data Planning > NE Information from the
navigation tree. In the query result area, select a desired NE and click Set Login Parameter.
Step 2 In the Set NE Telnet Parameter dialog box, correct Telnet parameter settings and click Test
Connectivity. If the test is successful, no login failure message will be displayed when a script
is applied. If the test fails, check the management IP address of the NE.
Select the NE in the query result area and click Modify. In the Edit NE dialog box, correct the
management IP address and click OK.
----End
Login Window or a Blank Page Is Displayed After the Backspace Key Is Pressed
Symptom
A user logs in to the plug-and-play management module using the Internet Explorer and presses
the Backspace key. The login window or a blank page is displayed.
Fault Analysis
The plug-and-play management module is an application embedded in a single window. The
rollback operations for websites are unavailable for it.
Solution
Logs in to the plug-and-play management module again. Alternatively, click the website refresh
button on the blank page to return to the plug-and-play management module main window.
Context
U2000 clients access NEs using the proxy service. To ensure network user security, you need
to configure an access control list (ACL) for the proxy service to allow specified U2000 clients
to access NEs. Ensure that NEs have the Telnet service enabled. Before accessing an NE by
Telnet, ensure that port 31035 is enabled between the U2000 server and client and the U2000
client is allowed by the ACL.
l If the U2000 server and client are installed on the same computer, the IP address in the
access control entry must be set to 127.0.0.1.
l If IP Address or Network Segment is set to 0.0.0.0/0 or a value in IP address/0 format
and Operation is set to Accept in the ACL, U2000 clients on all network segments can
connect to access NEs.
l If gateway devices, such as network address translation (NAT) devices, are deployed and
the U2000 client is located on the NAT network, the IP address in the access control entry
must be set to an IP address that the U2000 server can access, but not an internal network
IP address bound to the U2000 client.
Procedure
Step 1 Run the telnet server enable command on an NE to start the Telnet server so that Telnet users
can log in to the NE.
Step 2 Choose Administration > NMS Security > Proxy Service ACL from the main menu
(traditional style); alternatively, double-click Security Management in Application Center
and choose OSS Security > Settings > Proxy Service ACL from the main menu (application
style).
Step 3 In the Proxy Service ACL dialog box, view the access control entries. Click Add, Modify, or
Delete, add, modify, or delete an access control entry, and click OK.
Adding an access control entry 1. In the Proxy Service ACL dialog box, click Add.
2. In the Add Access Control Item dialog box, enter an
IP address or network segment, set Operation, and
click OK.
NOTE
l If Operation is set to Accept, the entered IP address or an
IP address on the entered network segment can be used to
access NEs using the proxy service.
l If Operation is set to Reject, the entered IP address or an IP
address on the entered network segment cannot be used to
access NEs using the proxy service.
Modifying an access control 1. In the Proxy Service ACL dialog box, select a desired
entry access control entry and click Modify.
2. In the Modify Access Control Item dialog box,
change the IP address or network segment, modify
Operation, and click OK.
NOTE
l If Operation is set to Accept, the entered IP address or an
IP address on the entered network segment can be used to
access NEs using the proxy service.
l If Operation is set to Reject, the entered IP address or an IP
address on the entered network segment cannot be used to
access NEs using the proxy service.
Deleting an access control entry 1. In the Proxy Service ACL dialog box, select a desired
access control entry and click Delete.
2. In the Confirm dialog box, click Yes.
NOTE
After NEs are connected using the proxy service and associated
operations are performed, delete the access control entry to
prevent other users from accessing the NEs.
----End
Symptom
The "The entered login information is incorrect. Please enter again." message is displayed after
a user enters a user name and a password and clicks Login to log in to the plug-and-play
management module.
Fault Analysis
Too many contents are cached on the Firefox browser. The historical records must be deleted
from the Firefox browser.
Solution
1. Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu (traditional style); alternatively, double-click Fix-
Network NE Configuration in Application Center and choose Configuration > Router/
Switch/Security Configuration > Plug-and-Play Management from the main menu
(application style).
2. Choose History > Clear History Record from the main menu of the FireFox browser.
3. In the dialog box that is displayed, select All from the drop-down list.
4. Click Clear.
5. Close the Firefox browser.
6. Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu of the U2000 client.
7. Enter the user name and password and click Login.
Context
This topic describes how to address a failure to generate script configurations in different
scenarios.
Procedure
l The associated configurations are not generated after the NE template is modified.
The selected template may be a default template instead of a project template for the site.
You can select a proper project template for the site to generate script configurations.
l The basic ASG configurations fail to be generated.
– On the NE Information tab in the plug-and-play window, the Basic Configuration
Template parameter for the NE cannot be empty.
– Plan the aggregation-side links for the NE.
l Extended scripts are not generated.
Extended scripts are generated based on the Other Configuration sheet in the planning table.
You must plan the sheet before data importing. Data planning must meet the following
conditions:
– Ensure that the template contained in the sheet exists in the plug-and-play module.
– Ensure that the NE involved in the sheet already exist in the plug-and-play module or
the links through which the NE passes have been planned.
l The extended scripts are not integrated into the basic configuration scripts.
----End
No User Name, Password, and SNMP Read and Write Settings Contained in the
Scripts Generated by a Customized Project Template During the U2000 Upgrade
How do I solve the problem where the user name and password are not contained in the scripts
generated by a customized project template during the U2000 upgrade and the SNMP read and
write parameters are empty?
Procedure
Step 1 Enter the user name, password, and SNMP parameters in the imported template and configure
the template as a default one.
----End
Procedure
Step 1 Use the UniSTAR to create a project and plan data about the interconnection between the CSG
and the ASG in normal scenarios, including interface and IGP data. After the planning is
complete, export link planning table 1.
Step 2 Use the plug-and-play module to import the link planning table exported from the UniSTAR.
Make CSGs get online. Select the first two options after choosing System Management > Set
Global Options > Options for Remote Commissioning.
Step 3 After some SCGs get online, a project needs to be re-created on the UniSTAR, the data (including
the interface and IGP data) about the interconnection between the CSG and the RSG needs to
be planned, and the RSG NE rule must be set to ASG. After the planning is complete, export
link planning table 2.
Step 4 Deselect the first two options by choosing System Management > Set Global Options >
Options for Remote Commissioning from in the plug-and-play window.
Step 5 In the Main Topology, double-click the RSG connected to the CSG to access the NE Explorer.
In the router management window, configure the IGP process on the access side. In the interface
management window, configure interface information.
Step 6 Use the plug-and-play module to import link planning table 2 exported from the UniSTAR and
make the CSG connected to the RSG get online.
----End
Context
Possible causes:
l After an upgrade of NEs or the U2000, the initial login passwords of some NEs are different
from those configured on the U2000.
l A user name and password have been configured for an NE before the NE gets online. As
a result, when the user name and password are used to log in to the NE, NE login fails.
Procedure
Step 1 After logging in to the plug-and-play module, modify the initial NE login password in the NE
Login Parameters window.
----End
Procedure
Step 1 Log in to the plug-and-play module, click Script Management, and select Script
Management.
Step 2 Right-click the NE List node and choose Scheduled Script Deployment from the shortcut
menu.
----End
How to Solve the Problem Where Some Configurations Remain on the Newly
Added NEs After the NEs Fail to Be Added to a Ring
If a major error exists on the delivered scripts when the TCAT is used to add nodes to a ring,
the basic configurations of the newly added NEs fail to be delivered, and the delivered
configurations remain on the newly added NEs. You must manually clear the remaining
configurations to allow the operation of adding nodes to a ring.
Context
If a major error exists on the delivered basic configurations when some nodes are added to a
ring, the newly added NEs cannot get online, and the nodes fail to be added to the ring. In
consideration of security concern, the U2000 does not clear the NE configurations after the
failure to add nodes to the ring.
Procedure
l Method 1 (recommended): In the router DCN management mode, Telnet to gateway NEs
and use the two-hop mode to Telnet to newly created NEs. Then manually clear the NE
configurations.
l Method 2: Use serial interfaces to connect to newly created NEs and then clear NE
configurations.
----End
Failed to Save Modified SNMP Read and Write Community Names in Plug-and-
Play
How do I solve the problem where the system fails to save modified SNMP read and write
community names in plug-and-play?
Procedure
Step 1 The cache of the browser used for plug-and-play is not cleaned up. Choose Tool > Clear History
Record from the main menu of the browser and clean up the cache of the browser.
----End
Symptom
The message The login attempts have reached maximum. The user account has been locked.
Please try again later. is displayed when an attempt was made to log in to Plug-and-Play
Management.
Fault Analysis
l The period during which no operation was performed timed out.
l The number of login attempts reached the threshold.
Solution
1. Log in to the U2000 client.
2. On the main menu, choose Administration > NMS Security > NMS User
Management.
3. Select the locked account and click the Unlock User in the lower right corner.
4. On the U2000 main menu, choose Configuration > Router/Switch/Security
Configuration > Plug-and-Play Management.
5. Enter the user name and password and click Login.
Symptom
Plug-and-Play Management cannot deliver data.
Fault Analysis
l The U2000 server is attacked by viruses and files are deleted.
l U2000 users do not have the operation rights.
Solution
1. Contact Huawei engineers to add correct files.
2. Disconnect the U2000 server from the public network to protect it from virus attacks.
3. Enable the U2000 user with the access and operation rights to log in to the U2000 and then
deliver data.
Sometimes, the parameter settings in the universal script do not match the live network after
basic network configuration is complete. You can verify the basic configuration, including IP
address conflict and link status checks.
Prerequisites
1. The NE has been added to the U2000.
2. The basic configurations related to services on the live network have been deployed to the
NEs.
Application Scenario
On the live network, the DCN Management for Routers function or the CLI mode (applicable
to an earlier U2000 version) is usually used to deploy a universal script to routers in batches in
order to deploy basic configurations. As a great number of NEs exist on the live network and
NE configurations often changes, the parameter settings in the universal script sometimes do
not match the live network. In this case, verifying the basic configuration is required. This
function helps to implement visual and batch basic configuration verification.
Procedure
Step 1 Choose Administration > IP Device Health Check from the main menu (traditional style);
alternatively, double-click Fix-Network NE Configuration in Application Center and choose
Administration > IP Device Health Check from the main menu (application style).
Step 2 Click Select NE. In the dialog box that is displayed, select the desired NEs and click OK.
NOTE
You can enter IP Device Health Check dialog box using these methods:
l Select the desired NEs in the Main Topology, right-click, and choose IP Device Health Check from
the shortcut menu.
l Choose Administration > DCN Management for Routers from the main menu (traditional style);
alternatively, double-click Fix-Network NE Configuration in Application Center and choose
Administration > DCN Management for Routers from the main menu (application style). In DCN
Management for Routers dialog box, choose the NE on the NE trees, right-click, and choose IP
Device Health Check from the shortcut menu.
The selected check items are displayed. If you move the cursor to a check item. details about the check
item are displayed.
The following figure indicates that the detection has finished and detection results are displayed.
----End
Follow-up Procedure
Based on the detection results, check the causes to items that report faults, locate and rectify the
faults, and perform the detection until all the items are passed.
Application Scenarios
1. Small-cell base station bearer scenario
Mobile networks are transforming from dominant macro base stations to co-existing macro
and small-cell base stations. In addition, small-cell base stations, with characteristics such
as low cost, wide coverage, and easy installation, will play a more and more important role
in future network construction.
In Huawei's mobile bearer solution, ATN 905 devices are used as small-cell base station
bearer NEs and connected to the access device (the CSG in the figure) at the macro base
station in chain networking mode. As an extension of the IPRAN mobile bearer solution
based on the macro base station, Huawei's mobile bearer solution integrates mobile bearer
clock and maintenance solutions in an end-to-end manner, and features low cost, easy
deployment, and easy O&M. Figure 1 shows the networking diagram of the solution using
the ATN 905 as the bearer device at the small-cell base station.
Figure 4-1 Networking diagram of the small-cell base station bearer solution
Small-cell Base IPRAN
Station Access
BSC
RNC
NOTE
The mobile bearer device at the macro base station may be a third-party device. In this topic, Huawei's
IPRAN solution (ATN + CX networking) on the macro base station side is used as an example to illustrate
the deployment configuration.
EDD Scenario
ASG RSG
CSG
EDD
RNC
ATN 905
As shown in Figure 3, an enterprise rents a 100M private line from a provider. However,
the enterprise user considers the bandwidth as lower than 100 M. In the case of a fault on
the enterprise user network, the enterprise user tends to call the provider and complain.
How can the provider divide the maintenance responsibilities? The provider can deploy an
EDD near the CPE and test the throughput using RFC 2544 before the deployment so as
to prove that the bandwidth meets the requirements. After services are provisioned, the
EDD monitors service packets in real time using IP FPM, obtains information such as the
throughput, packet loss rate, latency, and jitter, and periodically provides an SLA to the
enterprise user so as to prove the provider's network quality.
CPE PE PE CPE
EDD PE PE
ATN 905
B
A
NOTE
For easy description, the upstream network of the EDD is called aggregation network.
Networking Models
In both solutions, the ATN 905 is connected to the nearby network of the operator. If the
operator's network is regarded as an abstract "cloud", only the deployment and configuration of
the part (marked by the dotted rectangle on the left) on the access network need to be considered.
For the marked part of the access network, the configuration roadmaps and procedures in both
solutions are basically the same. Therefore, this topic only provides detailed configuration
description from the angle of the access technology. That is, scenarios are not differentiated
while only solutions are differentiated. The following typical networking models are provided
for the configuration example.
l Native IP scenario: Layer 3 IP packets are forwarded between the ATN 905 and CSG.
Micro/Pico
Macro Cell
RNC/SGW
Micro/Pico
Native IP
Traffic flow
l Native Ethernet scenario: Layer 2 Ethernet packets are forwarded between the ATN 905
and CSG.
Micro/Pico
Macro Cell
RNC/SGW
Micro/Pico
Native Eth
Traffic flow
Configuration Overview
If a used ATN 905 accesses a carrier network, to prevent ATN 905 login failures due to password forgetting,
reset the ATN 905 to clear the existing password and configurations to restore the factory configurations.
Then perform operations according to the configuration guide.
The RST button on an ATN 905 allows you to clear the password and configuration file. Once you press
the RST button, the device starts to reset. Then you press and hold down the RST button 25s to 35s until
the PWR, STA, and ALM indicators blink green. Then release the RST button so that the device starts to
automatically delete passwords and configuration files.
1. Use the native IP or native Ethernet solution for the ATN 905 to access a carrier's live
network based on the actual networking bearer solution so that you can select the ATN
905's going online mode on the iManager U2000 IP Plug-and-play Management
interface in the subsequent operations. The native Ethernet solution is recommended
because it has simplicity and high going-online efficiency.
Scenario The ATN 905 is networked with Huawei's The ATN 905 is directly connected to a third-
products. party NE.
Configurat
ion
Entrance
2. NE login parameter setting: Enter the NE's initial login password and set Telnet/STelnet
parameters, SNMP parameters, and U2000 server information.
3. NE management channel selection: Select the Public solution or Private solution as the
NE management channel based on the management solution of the macro base station
management plane.
Scenario Select the public network as the management Select the private network as the management
solution for the macro base station management solution for the macro base station management
plane. plane.
Configurat The Public solution is recommended as the NE The Private solution is recommended as the NE
ion Item management channel. management channel.
Configurat Native IP solution: Select Public solution. Native IP solution: The BGP VPN + Public
ion IGP solution or BGP VPN + DCN VPN
Entrance solution is recommended.
l If you select BGP VPN + Public IGP, the
aggregation ring uses BGP VPN, and the
access ring uses public network IGP.
Native Ethernet solution: Select Vlanif l If you select BGP VPN + DCN VPN, the
Solution. aggregation ring uses BGP VPN, and the
access ring uses DCN VPN.
NOTE
The aggregation ring consists of CX devices
functioning as ASGs, and the access ring consists of
ATN devices (at the macro base station) functioning
as CSGs.
Customizing Templates
Basic NE configurations selection: Select the basic configuration template for managing the
ATN 905 going online and service configuration templates based on the native IP or native
Ethernet solution. Customize a service extension configuration template for the ATN device at
the macro base station, and issue the extension configurations to the ATN device (at the macro
base station) that is directly connected to the ATN 905 to ensure service integrity.
NOTE
In the small-cell base station bearer solution, an ATN 905 is at the end and the outdoor cables must be
symmetrical. If the ATN clock compensation at the upstream macro base station is normal, the ATN 905
does not require clock compensation.
l In the native IP solution, when you select the public or private network solution for an NE
channel, the procedures for customizing the basic configuration template, service
configuration template, and service extension configuration template are similar. If you
select the private network solution, an additional private network configuration template
is automatically generated compared with the public network solution. The ATN 905 uses
this template to establish a management connection with the U2000 or the ATN device at
the macro base station.
l In the native Ethernet solution, when you select VLANIF or DCN VPN solution for an NE
channel, a configuration template is automatically generated.
Moreover, you can select or deselect VRF Configuration in the service template of the native
IP solution, depending on whether service isolation is required for the ATN 905. For details, see
the following table.
Scen Select Native IP solution. Select Native IP Select Native Ethernet Select Native
ario The ATN 905 is networked solution. solution. Ethernet solution.
with Huawei's products. The ATN 905 is The ATN 905 is The ATN 905 is
The NE management channel directly connected to networked with directly connected to
is the public network. a third-party NE. Huawei's products. a third-party NE.
The NE The NE management The NE management
management channel is VLANIF channel is the public
channel is the public solution. network.
network.
Tem The following three templates One template is One template is required. One template is
plate are required: required. The The configurations of required. The
l A template for managing configurations of the the management and configurations of the
the ATN 905 going online: management and service planes are management and
Choose Basic NE service planes are combined into the service planes are
Configurations > combined into the template. After the basic combined into the
Checking Basic template. On the configuration solution template. On the
Configuration Template for a small-cell base Template
Template. On the Management tab station is applied, a Management tab
Checking Basic page, customize a configuration template is page, customize a
Configuration Template template for a automatically generated template for a service
tab page, click Create to service under in Checking Basic under Common
customize the basic Common Configuration Configuration
configuration template, Configuration Template. For details, Template. Select the
which is used to configure Template. Select see Customizing specified template in
the management plane. the specified Templates. the following figure,
The procedure for creating template in the customize a template
the basic configuration following figure, for service
template is similar to that customize a template requirements, and
on the ATN device at a for service save the template as a
macro base station. For requirements, and service configuration
details, see Customizing save the template as template for the ATN
a Template for a service 905. By default, the
Managing the ATN 905 configuration template is saved
Going Online. template for the under Project
ATN 905. By Template. For
default, the template details, see
is saved under Customizing an
Project Template. Integrated Template
l A service configuration For details, see (in the Native
template for the ATN 905: Customizing an Ethernet Scenario).
On the Template Integrated
Management tab page, Template (in the
customize a template for a Native IP
service under Common Scenario).
Configuration
Template. Select the
specified template in the
following figure,
customize a template for
service requirements, and
save the template as a
service configuration
template for the ATN 905.
By default, the template is
saved under Project
Template. For details, see
Customizing a Basic
Service Configuration
Template.
l An extension
configuration template for
the ATN device at a macro
base station: On the
Template Management
tab page, customize a
template for a service
under Common
Configuration
Template. Select the
specified template in the
following figure,
customize a template for
service requirements, and
save the template as an
extension configuration
template for the ATN
device at a macro base
station. For details, see
Customizing an
Extension Configuration
Template.
Scenario Select the Native IP solution. Select the Native Ethernet solution.
The ATN 905 is networked with Huawei's The ATN 905 is networked with Huawei's
products. products.
The NE management channel is BGP VPN + The NE management channel is DCN VPN
DCN VPN solution. solution.
Template The following four templates are required: One template is required. The configurations of
l A template for managing the ATN 905 going the management and service planes are
online: Choose Basic NE Configurations > combined into the template. After the basic
Checking Basic Configuration Template. configuration solution for a small-cell base
On the Checking Basic Configuration station is applied, a configuration template is
Template tab page, click Create to automatically generated in Checking Basic
customize the basic configuration template, Configuration Template. For details, see
which is used to configure the management Customizing Templates.
plane. The procedure for creating the basic
configuration template is similar to that on
the ATN device at a macro base station. For
details, see Customizing a Template for
Managing the ATN 905 Going Online.
Issuing Configurations
Configuration issuing mode selection: Select the mode in which planning is not required, mode
in which a link planning table is not required, or mode in which a link planning table is required
based on networking scenarios and going online modes.
Huawei IPRAN self- Mode in which planning is not required: You do not need to use a planning tool to
networking plan links or fill in a link planning table. You only need to prepare the management IP
Native Ethernet access resource pool or interface resource of the ATN 905. After an ATN 905 is powered on,
the U2000 automatically discovers the ATN 905 and identifies the resource pool for
the ATN 905. The U2000 then allocates resources, generates configuration data, and
automatically delivers the data to the ATN 905. For details, see Issuing
Configurations.
Huawei IPRAN self- Mode in which a link planning table is not required: You do not need to use a
networking planning tool to plan links or fill in a link planning table. After you customize a
Native IP access template, skip Link Plan on the iManager U2000 IP Plug-and-play Management
interface and directly click Online NE Commissioning to enter the U2000's DCN
management view. Add and issue configurations. For details, see Issuing
Configurations (Without a Link Planning Table).
l In this scenario, interface IP addresses are automatically assigned using the planned
address pool.
l Service configurations are filled in the link planning table. You can import the
service configurations to the U2000 by importing the link planning table.
Direct connection Mode in which a link planning table is required: You do not need to use a planning
between the ATN 905 tool to plan links but need to fill in a link planning table. Enter 3rd Party Remote
and a third-party NE Commissioning in Direct Mode of the iManager U2000 IP Plug-and-play
Native Ethernet or Management interface, and export the link planning table. Fill the configuration
native IP access information in the link planning table, and then import the link planning table. Then
start the DHCP server to issue the script. For details, see Issuing Configurations.
Recommended Solutions
The following solutions are recommended based on common networking modes and NMS
configurations.
NE The public The public network The public network The private network
ma network or the
nag private network
em
ent
cha
nne
l
NOTE
The preceding recommended solutions are only common ones and there are also other combination types.
Scenario Overview
This section describes the networking.
For the Native Ethernet plug-and-play solution, there is no need for planning links with a
planning tool or filling a link planning table and only an ATN 905 management IP resource pool
or interface resources need to be prepared. Therefore, this solution is easy to implement and
significantly improves NE get-online efficiency. After an ATN 905 NE is powered on, the U2000
automatically discovers it, identifies the resource pool corresponding to the NE, allocates
resources, generates configuration data, and issues the configuration data to the NE. This enables
a planning-free get-online process of ATN 905.
This solution is recommended when the live network is large-scale and formed with Huawei's
IP RAN products with many ATN 905s accessed.
NOTE
This solution supports only tree networking of ATN 905, and does not ring networking of ATN 905.
In this solution, management channels between ATN 905s and CSGs uses the VLANIF solution
or the DCN VPN solution.
l VLANIF solution: uses the public network management plane to carry management
signals, allowing management signal and service signals to be carried on the same plane.
When public network management is configured for the CSG at the macro base station,
select the VLANIF solution for the ATN 905. In the VLANIF solution, you must configure
the management and service sub-interfaces on the ATN device (at the macro base station)
that is directly connected to the ATN 905 and then plan small-cell base station resources.
l DCN VPN solution: uses the DCN VPN management plane to carry management signals,
whereas service signals are carried on the public network plane. When private network
management is configured for the CSG at the macro base station, select the DCN VPN
solution for the ATN 905. In the DCN VPN solution, you must establish the IP resource
pool of the small-cell base station and then plan small-cell base station resources.
On the service plane, the HVPN or Layer 2+Layer 3 solution can be used as a macro base station
bearer solution in native Ethernet plug-and-play scenarios. When public network management
is configured, different macro base station bearer solutions require the ATN devices at the macro
base station to use different service configurations. Different services can use different VLANs.
l When the macro base station bearer solution is the HVPN solution, you must import a
service sub-interface to an L3VPN on the ATN device (at the macro base station) that is
directly connected to the ATN 905, implementing service interworking between the ATN
905 and the ATN device at the macro base station.
Figure 4-7 Networking when the macro base station bearer solution is the HVPN solution
l When the macro base station bearer solution is the Layer 2+Layer 3 solution, you must
import a service sub-interface to a service PW on the ATN device (at the macro base station)
that is directly connected to the ATN 905, implementing service interworking between the
ATN 905 and the ATN device at the macro base station.
Figure 4-8 Networking when the macro base station bearer solution is the Layer 2+Layer
3 solution
Configuration Roadmap
This section describes the configuration procedure in the planning-free scenario.
NOTE
The step numbers in the configuration procedure map those marked in the Plug-and-Play management
interface and the U2000. Each step with a specified sequence number is performed on the corresponding
interface.
Understand the macro base station management plane configurations and prepare the ATN 905
address resources. Then enter the plug-and-play management interface, configure remote
commissioning parameters to establish channels for exchange between ATN 905 NEs and the
U2000. Customize templates, including the basic configuration template for managing the ATN
905 going online, service configuration template to be issued to the ATN 905. After being
powered on, the ATN 905s automatically go online. Existing address resources are automatically
allocated, and the template automatically generates scripts and issues the scripts to the ATN 905.
In this manner, ATN 905s go online and services run normally.
1. Select the mode in which ATN 905s go online. For the Native Ethernet plug-and-play
solution, select the DCN networking mode.
2. Set NE login parameters and enter related parameters to establish connection to the U2000
and achieve authentication and network management.
3. Select the private/public network solution for the management channel based on the
management plane used by the macro base station to automatically generate a private/public
network configuration template.
4. Customize the basic configuration template.
5. Add a small-cell base station address resource pool.
6. After being powered on, the ATN 905s automatically go online. The template automatically
generates scripts and issues the scripts to the ATN 905s, so that ATN 905s go online and
service configurations are issued to the ATN 905s.
Configuration Procedure
This section describes how to deploy NEs and configure services.
Data Preparation
This section describes information that needs to be obtained before ATN 905s go online and the
U2000 navigation path to the plug-and-play interface.
Parameter Description
Parameter Description
2. Click to enter the Application Panel interface. Choose the Application Center tab
and double-click Fix-Network NE Configuration.
NOTE
The U2000 supports application and traditional styles. If the application style is used, perform this
step. If the traditional style is used, skip this step. By default, the U2000 uses the traditional style.
Procedure
Step 1 Configure the protocol for NEs going online.
In the Native Ethernet plug-and-play solution, ATN 905s go online using automatically available
DCN mode; therefore, site-visit-free software commissioning is achieved.
3. Click Apply.
If the ATN 905 login parameter settings are consistent with the ATN device at a macro base station, this
step can be skipped.
This task sets NE login parameters including the initial login password, AAA user information,
SNMP parameters, and U2000 server information.
When the U2000 enables the NE to go online in plug-and-play mode, you need to log in to
the NE first and establish communication between the NE and the U2000. The default NE
initial login password provided by the U2000 is Changeme_123. Click . In the dialog
box that is displayed, modify the default password.
3. Configure NE login parameters.
Choose Login Mode. In terms of security, the SSH mode is recommended. By default, the
login mode is SSH, the initial user name is root, and the initial password is
Changeme_123. After the first login, if you need to change the login mode to Telnet, add
the telnet authentication mode by configuring the Telnet/Stelnet parameter on the U2000.
4. Configure Simple Network Management Protocol (SNMP) parameters.
Set Security Name. A password must contain any two of uppercase/lowercase characters,
digits, and special characters. A password ranges from 8 to 32 characters.
5. Configure the IP addresses and masks for the primary and secondary NMS servers.
6. Click Apply.
3. Select the management channel solution based on the management plane used by the macro
base station. If the macro base station uses the public network management plane, select
Vlanif Solution and set Management VLAN. If the macro base station uses the private
network management plane, select DCN VPN Solution.
NOTE
The management VLAN configuration must be the same on the ATN 905 and ATN device at the
macro base station. The same management VLAN configuration is recommended for the entire
network.
4. Click Apply.
----End
Customizing Templates
A template will be automatically generated after the IP RAN small-cell base station bearer
solution is applied. This template is applicable for managing the ATN 905 going online in the
native Ethernet scenario.
Procedure
Step 1 Choose Basic NE Configurations and click the Customizing Basic Configuration
Solutions tab.
Step 2 Select Native Eth as the small-cell base station bearer solution.
Step 4 In Checking Basic Configuration Template, select the Native Ethernet plug-and-play general
configuration template, and click Modify.
Step 5 In the template, select VLANs configuration. According to actual service requirements, you
can set Business VLAN list to a VLAN range covering all used service VLAN IDs, for example,
1 to 15, or enter required service VLAN IDs separated from each other with spaces, for example,
1 5 10 to 15. The same VLAN configuration is recommended for each ATN 905.
NOTE
The management VLAN configuration must be the same on the ATN 905 and ATN device at the macro
base station. The same management VLAN configuration is recommended for the entire network.
Step 6 Optional: If the network topology is complex and the planned clock configuration for a small-
cell base station is different from the configuration in the template, deselect Clock
configuration in the template, and configure the clock after the small-cell base station goes
online. For details, see the appendix Configuring Clocks on a Per-NE Basis. If the network
topology is simple, select Clock configuration and retain the default configuration.
NOTE
By default, the sub-item Set SSM control function on is selected in Clock configuration. If you want to
trace the clock source only based on the priority of the clock source, deselect Set SSM control function
on.
Step 7 Optional: To modify a time zone, select Configure clock time zone and retain the default
configuration. Set the time zone name and time difference from the UTC.
----End
Issuing Configurations
In the Native Ethernet plug-and-play scenario, only ATN 905 management IP address resources
need to be prepared. After being powered on, ATN 905s will be automatically allocated with IP
address resources and service configurations.
?.1. Establishing a Small-cell Base Station Resource Pool (DCN VPN Solution)
This section describes how to establish a small-cell base station resource pool when a small-cell
base station management channel uses the DCN VPN solution.
Procedure
Step 1 Click Link Plan.
l If the ATN 905 management IP address pool is planned within the macro base station management IP
address pool, the preceding creation operations can be skipped and use the macro base station address
pool directly as the ATN 905 management IP address pool.
l If the ATN 905 management IP address pool is planned beyond the range of the macro base station
management IP address pool, you need to create an ATN 905 management IP address pool and ensure
that the U2000 server has a static route to the small-cell base station address segment so that the U2000
can manage the small-cell base station after it goes online.
Step 4 On the CellSite Resource tab page, click to specify the networkwide small-cell base station
address pool.
Step 5 On the Cellsite Recognition Type tab page, set the small-cell base station gateway downstream
interface. By default, Find by NE Type is selected.
Find by NE Type: The type of a device that is to go online is automatically identified.
Find by UPE Down Interface: An interface on the service gateway is specified as the
downstream interface. Click Add to specify the downstream interface.
Step 6 On the Business Interface Planning tab page, set the service interfaces (UNIs). By default, all
interfaces except for the interconnection interface are used as service interfaces. To manually
specify a service interface, select Business Interface, click Create, and enter the interface
number (for example, 0/2/0).
All Other Interface Except interconnect: Service interfaces can be specified on a large scale.
You do not need to plan service interfaces.
Business Interface: Planning is required, and the service interface of the ATN 905 is set based
on a plan.
----End
Context
Configure an upstream ASG to import the small-cell base station address segment to the
aggregation side; otherwise, the U2000 cannot learn the route to the small-cell base station.
Procedure
Step 1 Import the small-cell base station management address segment to the upstream master and slave
ASGs. If this management address segment has been imported, skip this step.
1. In the main topology of the U2000, select and right-click the upstream ASG.
2. Choose NE Explorer from the shortcut menu.
3. In the left navigation tree, choose Service Tree > Route Management > IP Prefix.
4. Select the IP prefix acc and click Configure.
NOTE
acc is the name of the route address prefix list imported by an IGP on the aggregation ring, which is
configured on the ASG.
5. Click Create to configure the IP prefix filtering rule and import the small-cell base station
management address segment. The entered index should be larger than that in the existing
rule, and the suggested mask length for the ATN 905 is 28.
6. Click OK.
Step 2 Configure the management subinterface on the ATN device at the macro base station. That is,
create a management subinterface, and enable IS-IS on the management subinterface and
configure suppression of IS-IS packet reception and transmission.
1. In the main topology of the U2000, select and right-click the gateway ATN device at the
macro base station.
2. Choose NE Explorer from the shortcut menu.
3. In the left navigation tree, choose Service Tree > Interface Management > Interface
Information.
4. On the Interface Information tab page, select a main interface and choose Create >
Create Subinterface > Ethernet Subinterface. Then, the Create Ethernet
Subinterface dialog box is displayed.
5. On the General tab page, enter the subinterface number. The subinterface number ranges
from 1 to 4096.
6. On the Subinterface Feature tab page, select encapsulation and enter the VLAN ID. The
entered VLAN ID must be the same as the Management VLAN entered when you select
the VLANIF solution as the small-cell base station management channel solution. That is,
when the public network solution is used, the VLAN ID should be unique.
7. On the IPv4 Address tab page, click Add, and enter the IPv4 address and subnet mask
(length: 28).
NOTE
The subnet mask length of the management subinterface on the gateway ATN device at the macro
base station must be consistent with that of the small-cell base station. The suggested small-cell base
station mask length is 28. If the small-cell base station mask length is a value different from 28,
change the management subinterface mask length to the same value.
The mask length of a small-cell base station is set based on the actual number of ATN 905s. The
ATN 905s that share the same gateway must be on the same network segment. If the mask length is
28, 14 IP addresses with the same network segment can be provided. That is, 14 ATN 905s can be
connected.
Step 3 (The macro base station bearer solution is the HVPN solution) Configure the service sub-
interface on the ATN device at the macro base station to access the L3VPN.
Skip this step if the subinterface of the interface that the ATN device at the macro base station
uses to interconnect with the ATN 905 is bound with VRF.
If the subinterface of the interface that the ATN device at the macro base station uses to
interconnect with the ATN 905 is not bound with VRF, perform the following steps to configure
the service subinterface:
1. In the main topology of the U2000, select and right-click the gateway ATN device at the
macro base station.
2. Choose NE Explorer from the shortcut menu.
3. In the left navigation tree, choose Service Tree > VPN Management > L3VPN
Management > VRF Management.
4. On the VRF Management tab page, select the VRF interchanged between the ATN 905
and the ATN device at the macro base station, and click Configure.
5. In the displayed Configure VRF dialog box, select Bind Interface and click Add to select
the subinterface of the interface that the ATN device at the macro base station uses to
interconnect with the ATN 905. If no subinterface has been created, create a subinterface.
Then, click OK.
6. Click OK. Then, service subinterface configuration is complete.
Step 4 (The macro base station bearer solution is the Layer 2+Layer 3 solution) Configure the service
sub-interface on the ATN device at the macro base station to access the VLL.
NOTE
Skip this step if the sub-interface of the interface that the ATN device at the macro base station uses to
interconnect with the ATN 905 is bound with a service PW.
If the sub-interface of the interface that the ATN device at the macro base station uses to interconnect with
the ATN 905 is not bound with a service PW, create a service subinterface and configure a service PW
from the ATN device at the macro base station to the ASG. For details, see the configuration information
about PWE3 service deployment on the ATN device at the macro base station in IPRAN networking.
Find by UPE Down Interface: An interface on the service gateway is specified as the
downstream interface. Click Add to specify the downstream interface.
4. On the Business Interface Planning tab page, set the service interfaces (UNIs). By default,
all interfaces except for the interconnection interface are used as service interfaces. To
manually specify a service interface, select Business Interface, click Create, and enter the
interface number (for example, 0/2/0).
All Other Interface Except interconnect: Service interfaces can be specified on a large
scale. You do not need to plan service interfaces.
Business Interface: Planning is required, and the service interface of the ATN 905 is set
based on a plan.
----End
Prerequisites
The U2000 client has been started.
The ATN device at the macro base station has gone online.
Procedure
Step 1 On the Online NE Commissioning interface, click
Step 2 Set the ATN device at the macro base station to the gateway NE (GNE). Specifically, click
or right-click Gateway NE Tree from the Navigation Tree on the left and choose Set Gate
NE from the shortcut menu. The gateway NE configuration is automatically reported, and the
downstream topology information is automatically updated.
Step 3 Optional: Right-click in the blank area and choose Synchronize from the shortcut menu.
The to-go online ATN 905 appears in the topology diagram, and configurations will be
automatically issued to the ATN 905. Once the configuration issuing progress becomes 100%,
the ATN 905 NE changes from blue to green, indicating that it successfully goes online.
----End
Appendix
Procedure
Step 1 In the main topology of the U2000, select and right-click the desired ATN 905.
Step 3 In the left navigation tree, choose Service Tree > System Management > Clock
Management.
3. On the Port Clock Source tab page of Clock Source, add a port for which a clock source
needs to be configured. Select Enable PTP Clock and click Apply.
4. Click Apply.
----End
Procedure
Step 1 In the main topology of the U2000, select and right-click the desired ATN 905.
Step 3 In the left navigation tree, choose Service Tree > Device Management > System
Information.
Step 4 In the displayed dialog box, change the device name based on the actual planning principles and
click OK.
Scenario Overview
This section describes the networking.
This solution is recommended when the live network is large-scale and formed with Huawei's
IP RAN products, and a Layer 3 access solution (such as HVPN) is used on the macro base
station side, macro base stations use the public network management plane, and services need
to be isolated. The following figure shows the networking environment.
Configuration Roadmap
This section describes the configuration procedures in the planning-free and planning scenarios.
The difference between the two scenarios is that after a template is customized, the planning-
free scenario allows a user to set parameters on the U2000 without using a planning tool to plan
paths, while the planning scenario allows the user to plan links on the Plug-and-Play management
interface and fill link and configuration parameters in the link planning table.
NOTE
The step numbers in the configuration procedure map those marked in the Plug-and-Play management
interface and the U2000. Each step with a specified sequence number is performed on the corresponding
interface.
1. Select the mode in which devices go online. On networks formed with Huawei equipment
only, devices can go online in DCN mode.
2. Set NE login parameters and enter related parameters to establish connection to the U2000
and achieve authentication and network management.
3. Select the public or private network for management based on the management plane used
by the macro base station.
4. Customize the basic configuration template. Specifically, use the basic configuration
template for the ATN 905 going online on the H-VPN established in the native IP access
scenario (using the macro base station).
5. On the template management interface, customize the ATN 905 service template based on
the [Micro]Native-IP Service Configuration Template Sample.
6. On the template management interface, customize the extension service template for the
ATN device at a macro base station based on [Micro]Native-IP CSG Extend
Configuration Template Sample.
7. Enter the DCN management view on the U2000 and issue extension configurations to the
ATN at the macro base station.
8. In the DCN management view of the U2000, enter the ATN 905 service configuration data
and issue service configurations to the ATN 905.
NOTE
The step numbers in the configuration procedure map those marked in the Plug-and-Play management
interface. Each step with a specified sequence number is performed on the corresponding interface.
1. Select the mode in which devices go online. On networks formed with Huawei equipment
only, devices can go online in DCN mode.
2. Set NE login parameters and enter related parameters to establish connection to the U2000
and achieve authentication and network management.
3. Select the public or private network for management based on the management plane used
by the macro base station.
4. Customize the basic configuration template. Specifically, use the basic configuration
template for the ATN 905 going online on the H-VPN established in the native IP access
scenario (using the macro base station).
5. On the template management interface, customize the ATN 905 service template based on
the [Micro]Native-IP Service Configuration Template Sample.
6. On the template management interface, customize the extension service template for the
ATN device at a macro base station based on [Micro]Native-IP CSG Extend
Configuration Template Sample.
7. Import the service template to the link planning table as an extension template, export the
link planning table, and enter the link relationship and service planning data. Then import
the link planning table.
8. Check whether the generated scripts are correct.
9. Issue the scripts to enable the device to go online and issue service configurations to the
device.
Configuration Procedure
This section describes how to deploy NEs and configure services in the planning-free and
planning scenarios.
Data Preparation
Management Plane Link IP address pool, management IP address pool, IGP protocol, and
Parameters IGP process number
Service Plane Service link IP address plan, service IGP protocol, service IGP
Parameter process number, service VLAN, and VRF name, Clock tracing
relationship
2. Click to enter the Application Panel interface. Choose the Application Center tab
and double-click Fix-Network NE Configuration.
NOTE
The U2000 supports application and traditional styles. If the application style is used, perform this
step. If the traditional style is used, skip this step. By default, the U2000 uses the traditional style.
Procedure
Step 1 Configure the protocol for NEs going online.
In solution 1, NEs can go online in DCN mode.
l If you choose SNMPv1 or SNMPv2c, enter the read and write community words in SNMPv1 or
SNMPv2c parameters. Then click to enter the passwords. The passwords of the read and write
community words cannot be the same. Otherwise, the device cannot go online.
l If you choose SNMPv3, enter SNMPv3 parameters including the SNMP group user name, SNMP
group, MD5 password, and DES password. Then click to enter the passwords.
l You can choose SNMPv1, SNMPv2c, and SNMPv3 concurrently.
5. Configure the IP addresses and masks for the primary and secondary NMS servers.
6. Click Apply.
Step 3 Customize an NE management channel.
Configure an NE management channel solution. The default solution is public network
management. In this solution, macro base stations are managed using the public network, so the
public network solution is selected.
----End
Customizing Templates
This topic describes how to customize templates for managing the ATN 905 going online and
issuing service configurations to the ATN 905 and customizing an extension configuration
template for the ATN device at a macro base station.
?.1. Customizing a Template for Managing the ATN 905 Going Online
This topic describes how to customize a template for managing the ATN 905 going online in
the native IP scenario.
NOTE
Procedure
Step 1 Choose Basic NE Configurations, click the Customizing Basic Configuration Solutions tab,
and enter the service plan on the macro base station side. Ensure that parameters on the access
side are consistent with those on the macro base station side.
1. Select a service solution. In the native IP access scenario, set Service Solution to HVPN
Solution.
2. Select an aggregation-side network solution based on the actual plan of the macro base
station on the live network. For the macro base station, if IGP Solution is set to ISIS,
choose ISIS; if MPLS Solution is set to MPLS TE, choose MPLS TE.
3. Match the network solution on the access side with that on the aggregation side.
Specifically, set IGP Solution to ISIS Multi-Process and MPLS Solution to MPLS
TE. Then set Access-side IGP Assignment Rule to Unique on the network.
The basic configuration template for managing the ATN 905 going online can be established
using 2 methods.
NOTE
Templates established using the 2 methods are consistent. The following uses method 1 as an example.
l Method 1: Click Create to create a template. Then save the template.
l Method 2: Execute [HVPN-CSG]Basic Configuration Template Sample that is generated
after the Customizing Basic Configuration Solutions step is complete. The template name
contains the time when the template was generated. Click Modify, modify the template based
on the ATN 905 requirements, and save the template as an ATN 905 template.
2. Configure common parameters by referring to the NE Login Parameters step and click
Next.
3. On the Configuration Template tab, enter the template name and click Show Details.
4. On the Configuration Template tab, enter configuration information and the template for
managing the ATN 905 going online is completed. Ensure that Configure clock time
zone, NE Basic Configuration, AAA and User-interface, IGP Configuration,
LoopBack Interface Configuration, Network Interface Configuration, FTP, SFTP
and NTP Configuration, and SNMP Configuration are selected and others are
deselected.
l In Configure clock time zone, enter a time zone name. Ensure that the time zone is
different from the Coordinated Universal Time (UTC).
l In NE Basic Configuration, retain the default configurations.
l In AAA and User-interface, set AAA User Name. In AAA User Password, click
Input Password, enter a password, and click OK. Other items are selected by default.
NOTE
By default, Service Type is set to SSH. Do not modify it after you log in to the device for the
first time; otherwise, later login attempts will fail.
l In SNMP Configuration, configure names for the SNMP read and write community
words, click Input Password, enter the passwords for the SNMP read and write
community words, and click OK. The passwords for the SNMP read and write
community words cannot be the same. In SNMP Configuration, retain the default
configurations for other items.
6. The procedure of customizing the template for managing the ATN 905 going online is
complete.
----End
NOTE
Procedure
Step 1 Click Template Management > Template Management.
Step 2 Choose Templates > Common Configuration Template > [Micro]Native-IP Basic
Configuration Template Sample.
Step 3 On the Template Configuration window on the right, enter configuration information.
l When services do not need to be isolated, ensure that Private IGP Configuration, Configure
a static route, Network Interface Configuration, and Clock configuration are selected
and other items are deselected.
l When services need to be isolated, select VRF Configuration.
1. Select VRF configurations in the scenario where services need to be isolated.
NOTE
This network entity must be unique for each device. The format of the value is area address (1 to 13
bytes).system ID (6 bytes).SEL(00). The area address is designed based on user demands. And it can
be defined on the tab Private IGP Configuration > ISIS Configuration > Configure ISIS for
DCNVPN > Configure BFD parameter for OSPF > Network Entity. The default value is 49.0001.
2. In VRF Configuration, enter VPN Instance Name and VPN-RD.
5. Click Save.
6. In the dialog box that is displayed, click OK. The procedure of customizing the basic service
configuration template is complete.
----End
You can modify the selected items in [Micro]Native-IP CSG Extend Configuration Template
Sample and save the template as Native-IP CSG Extend Configuration Template Sample -
upe.
NOTE
Procedure
Step 1 Click Template Management > Template Management.
Step 2 Choose Templates > Common Configuration Template > [Micro]Native-IP CSG Extend
Configuration Template Sample.
Step 3 On the Template Configuration window on the right, enter configuration information.
1. In BGP Configuration, enter the BGP AS number and VPN instance name for the upper-
layer IP RAN service and deselect Import OSPF Route. Other items are selected by
default.
2. In IGP Configuration, enter the name of the VPN instance on the upper-layer IP RAN for
Binding the ISIS process to a VPN instance. Other items are selected by default.
3. In Service Configuration, enter the name of the VPN instance on the upper-layer IP RAN
for Binding the interface to a VPN instance. Other items are selected by default.
NOTE
If services need to be isolated for the ATN device at a macro base station, select VRF
Configuration. Otherwise, retain the default configuration (deselected).
----End
Procedure
Step 1 Click Deployment Configuration > Deployment Overview > Basic NE Configurations >
Extend Configuration Template.
Step 2 Click Select Extend Configuration Template. Select Project Tempalte in the Search
Location, select configuration template for ATN 905 and the ATN device at a macro base station,
----End
?.2. Issuing Extension Configurations to the ATN Device at a Macro Base Station
This topic describes how to issue extension configurations to the ATN device at a macro base
station using the Native-IP CSG Extension Configuration Template Sample.
Prerequisites
The U2000 client has been started.
The ATN device at the macro base station has gone online.
Procedure
Step 1 On the Online NE Commissioning interface, click
Step 3 Right-click in the blank area and choose Synchronize from the shortcut menu. The to-go online
ATN 905 appears in the topology diagram.
Step 4 Choose the ATN device at the macro base station, right-click, and click Apply Basic
Configuration > Plan and Apply Additional Data.
Step 5 Select the Native-IP CSG Extend Configuration Template Sample - upe, click Next.
If there are too many templates displayed, choose the desired template by matching the attribute.
ISIS process description Enter the description based on the site plan.
Step 7 Click OK. In the dialog box that is displayed, click Apply Configuration.
----End
Prerequisites
The U2000 client has been started.
The ATN device at the macro base station has gone online.
Procedure
Step 1 On the DCN Management for Routers interface, choose the ATN 905 and click Apply Basic
Configuration > Basic Configuration Planned And Apply.
Step 2 Enable the ATN 905 to go online without a planning tool. Specifically, choose the ring where
the ATN 905 resides and click Next.
Step 3 Choose all ATN 905 devices, modify the basic configuration templates in batches, and choose
the template for managing the ATN 905 going online.
Step 4 Choose all ATN 905 devices, click Extend Configuration Template, add the Native IP service
configuration template for the ATN 905, and configure related parameters.
1. Configure IGP parameters.
Binding the ISIS process to a VPN instance Enter the name of the VRF instance bound
to services at the small-cell base station.
ISIS process description Enter the description based on the site plan.
2. Configure parameters for the static route from the ATN 905 to the service IP address of the
wireless small-cell base station.
Binding the static route to a VPN instance Enter the name of the VRF instance bound
to services at the small-cell base station.
the mask length of the destination IP Enter the service IP address mask of the
address small-cell base station.
the next-hop address Enter the IP address of the link from the
small-cell base station to the ATN 905.
Each ATN 905 supports 3 types of service links and a type needs to be defined for each
link.
Binding the interface to a VPN instance Enter the name of the VRF instance bound
to services at the small-cell base station.
Interface ISIS process ID Enter the number of the IS-IS process for
services at the small-cell base station.
Configure clock system priority Enter the priority value in the row of the
ATN 905 interface where the clock source
is introduced.
Step 5 Click OK. In the dialog box that is displayed, click Apply Configuration.
----End
Link Planning
In the link planning phase, complete the following tasks:
1. Plan address pool resources so that LSR IDs and link IP addresses can be automatically
allocated after the link planning table is imported.
2. Use the service configuration template as the extension template and export the link
planning table.
3. Enter basic information of the ATN 905 and link information of the upstream NE.
4. Enter basic information of the ATN device at the macro base station to complete the link
planning table.
Procedure
Step 1 Plan an address pool.
1. Click Deployment Configuration > Deployment Overview and choose Link Plan.
2. On the Address Pool Planning tab, click Create. In the dialog box that is displayed, click
OK. To create an address pool for the management plane LSR IDs, set IP Pool Name, set
IP Pool Type to LSR ID Address Pool, set Start IP and End IP, and set Mask Length
to 32.
3. Click Create and a dialog box is displayed. To create an address pool for link IP addresses,
set IP Pool Name, set IP Pool Type to Link IP Address Pool, set Start IP and End IP,
and set Mask Length to 30.
.
2. In the Export Link Planning Table Template dialog box that is displayed, click Choose
Extend Template. In the Choose Extend Template dialog box that is displayed, set
Search Location to Project Template (the path for saving the customized service
configuration template). Select the service configuration template and the extension
configuration template for the ATN device at the macro base station, click
and then click OK.
3. Click Export Link Planning Table Template. In the dialog box that is displayed, click
OK to save the link planning table to a local path. To differentiate this table from others,
name it as "xxx Site xxx Planning Table".
2. Plan the link connection relationship. Specifically, choose the NetworkLayout tab and
enter the ATN 905 information in the columns with a green header and the upstream NE
information in the columns with a yellow header. Address pools have been planned, so
LSR ID and Interface IP Address/mask can be left unspecified. When devices goes
online, addresses are automatically allocated for them from the address pools.
3. On the Aggregate_NE_INFO tab, enter the information about the ring where the ATN
905 resides. Set Ring Name to RING1, a new ring established based on the ATN 905.
4. On the Other Configuration tab, enter service configuration information, including the
IGP protocol, service link information, and clock tracing relationship of each ATN 905,
and the static route from the ATN 905 to the service IP address of the wireless small-cell
base station.
NOTE
If the small-cell base station uses the IP address of the interface directly connecting to the ATN 905
as the service IP address, no static route needs to be configured.
Binding the ISIS process to a VPN instance Enter the name of the VRF instance bound
to services at the small-cell base station.
ISIS process description Enter the description based on the site plan.
Table 4-9 Parameters for the static route from the ATN 905 to the service IP address of
the wireless small-cell base station
Binding the static route to a VPN instance Enter the name of the VRF instance bound
to services at the small-cell base station.
the mask length of the destination IP Enter the service IP address mask of the
address small-cell base station.
the next-hop address Enter the IP address of the link from the
small-cell base station to the ATN 905.
Binding the interface to a VPN instance Enter the name of the VRF instance bound
to services at the small-cell base station.
Interface ISIS process ID Enter the number of the IS-IS process for
services at the small-cell base station.
NOTE
Each ATN 905 supports 3 types of service links and a type needs to be defined for each link.
l Link leading upstream to the ATN device
l Link leading to the wireless small-cell base station
l Link leading downstream to the ATN 905
Configure clock system priority Enter the priority value in the row of the
ATN 905 interface where the clock source
is introduced.
5. On the Other Configuration tab, enter the configuration parameters for the ATN device
at the macro base station.
Table 4-12 Configuration parameters for the ATN device at the macro base station
ISIS process description Enter the description based on the site plan.
6. After entering the link connection relationship, ring information, and service configuration
information, save the link planning table.
----End
Procedure
Step 1 Click Link Plan. On the Interconnection Relationship Planning tab, click
Step 2 In the dialog box that is displayed, choose the link planning table and click Next.
Step 3 In the Import Parameter Set dialog box that is displayed, modify Configuration Rules for
Link Planning, select Automatic configuration, and click Configuration to perform advanced
configuration.
1. In the Advanced Configuration dialog box that is displayed, select Assign LSR ID
automatically, click Select IP Address Pool on the right, and choose the planned LSR ID
address pool.
2. Select Configure IP Address, click Select IP Address Pool on the right, choose the
planned link IP address pool, and click OK.
3. Click Next. In the dialog box that is displayed, check whether the entered data is correct
and click OK to import the data.
2. In the Select Template dialog box that is displayed, choose the created template for
managing the ATN 905 going online, and click OK. The default template for managing
the ATN 905 going online is the newly-created one.
3. Click Next.
4. In the Select Peer Template dialog box that is displayed, click Finish. The procedure of
importing a link planning table is complete.
----End
Procedure
Step 1 Click Script Management > Script Management > NE List.
1. Choose NE Name from the Attribute drop-down list, enter a filter criterion in the
Match text box, and click Query. Then choose the desired NE in the list below.
2. Modify the basic NE information, including the NE type and version.
3. Click Apply.
Step 3 In the Navigation Tree, choose an NE under the NE List node to generate configuration scripts.
Step 4 Click Basic configuration scripts. In the Script Configuration field, click Verify Script. Then
query the verification result based on Error Number and click Previous Error or Next
Error to locate errors.
You are advised to check whether the following parameter settings meet project requirements:
l AS number
l AAA parameters
l U2000 server IP address
NOTE
The verification can detect syntax errors but cannot detect semantic errors. Generally, command errors
occur when parameters are set incorrectly or the current version does not support some commands.
----End
Procedure
Step 1 On the Online NE Commissioning interface, click Online NE Commissioning. Ensure that
the U2000 client has started. In the dialog box that is displayed, click OK. The DCN
Management for Routers tab is displayed.
Step 2 Click or right-click Gateway NE Tree from the Navigation Tree on the left and choose Set
Gate NE from the shortcut menu.
Step 3 In the dialog box that is displayed, choose the desired gateway NE (GNE) and click OK. The
added GNE is displayed under the Gateway NE Tree node and the non-GNE to go online will
be displayed on the right. At this time, the color of the NE (which has not gone online yet) is
grey and that of the link is yellow.
Step 5 Right-click in the blank area on the right and choose Synchronize from the shortcut menu. In
the dialog box that is displayed, click to update the DCN view status. When the color of
the non-GNE turns from grey to blue or Status on the NE tab is displayed as Online, the non-
GNE has gone online successfully.
NOTE
During synchronization, the link color may turn to grey. One possible cause is that the foreground updates
the link status every 10s. Check whether the background transmits the latest link merging information to
the foreground.
If the inter-device Link Layer Discovery Protocol (LLDP) fails to be established, the link color turns to
grey. Other possible causes are as follows: the interconnected interfaces are shut down, the physical
connection of the link is interrupted, the device is offline, or the LLDP has not been established yet after
the device is restarted. If the link color turns grey, wait for 30s and perform synchronization again. If the
link color is still grey, check whether the physical connection of the link is normal.
Step 6 Right-click the non-GNE that has gone online and choose Apply Basic Configuration > Plan
and Apply Additional Data from the shortcut menu. After the scripts are issued, query logs. If
some commands fail to be issued, log in to the NE in manual telnet or stelnet mode and re-issue
the scripts.
NOTE
When multiple NEs are selected for issuing scripts concurrently, preferentially issue the scripts to the NE
nearest to the GNE (that is, the NE with the fewest hops to the GNE). You can query the progress bar to
obtain the NE sequence.
Step 7 When the non-GNE color turns from blue to green, the scripts are issued successfully.
----End
Scenario Overview
This section describes the networking.
This solution is recommended when the live network is large-scale and formed with non-Huawei
IP RAN products, the ATN 905 is directly connected to the third-party NE and macro base
station, and macro base stations use the public network management plane. The following shows
the networking environment.
When the macro base station uses a Layer 3 or H-VPN bearer solution, the ATN 905 uses the
native IP solution to access the macro base station.
When the macro base station uses a Layer 2 or Layer 2 + Layer 3 bearer solution, the ATN 905
uses the native Ethernet solution to access the macro base station.
Configuration Roadmap
This section describes the configuration in the planning scenario.
NOTE
The step numbers in the configuration procedure map those marked in the Plug-and-Play management
interface. Each step with a specified sequence number is performed on the corresponding interface.
Understand the macro base station management plane configurations and prepare the link
relationship data. Then enter the plug-and-play management interface, customize an integrated
template for managing device going online and issuing service configurations, enter upstream
and downstream link relationships and service configuration parameters in the link planning
table (to which the template is imported), import the link planning table, generate scripts, and
issue the scripts to the devices. In this manner, devices go online and services run normally. The
configuration principle is as follows:
Configuration Procedure
This section describes how to deploy NEs and configure services.
Data Preparation
For the U2000 client, the default user name is admin and the initial password is Changeme_123. When a
user logs in to the U2000 client for the first time, a message is displayed, prompting the user to change to
password. If pre-installation is performed before delivery, the password is changed to Admin_123. To
ensure system security, change the password in time, periodically update it, and properly save it.
2. Click to enter the Application Panel interface. Choose the Application Center tab
and double-click Fix-Network NE Configuration.
NOTE
The NMS supports application and traditional styles. If the application style is used, you need to
perform this step. If the traditional style is used, skip this step. By default, the NMS uses the traditional
style.
NOTE
Procedure
Step 1 Click Template Management on the main menu and choose Template Management from the
drop-down list.
Step 2 Choose Templates > Common Configuration Template > [Micro]Native-IP Third-Party
Configuration Template Sample.
Step 3 On the Template Configuration window on the right, enter configuration information. Ensure
that Configure clock time zone, NE Basic Configuration, AAA and User-interface, Public
IGP Configuration, Private IGP Configuration, LoopBack Interface Configuration,
Configure a static route, Network Interface Configuration, Clock configuration, and
SNMP Configuration are selected and other items are deselected.
NOTE
To ensure security, user names and passwords are required in all templates involving AAA configurations.
When the ATN 905 is directly connected to a third-party NE, AAA is configured by default and AAA and
User-interface is not required in the template for the native IP scenario. However, default system templates
cannot be saved when AAA and User-interface is deselected. Therefore, you can retain the AAA and
User-interface configuration first and delete it after saving the template to the project template.
1. In Configure clock time zone, enter a time zone name. Ensure that the time zone is different
from the Coordinated Universal Time (UTC).
3. In AAA and User-interface, set AAA User Name. In AAA User Password, click Input
Password, enter a password, and click OK.
NOTE
By default, Service Type is set to SSH. Do not modify it after you log in to the device for the first
time; otherwise, later login attempts will fail.
4. In Public IGP Configuration, retain the default configurations, as shown in the following
figure.
5. In Private IGP Configuration, retain the default configurations, as shown in the following
figure.
10. In SNMP Configuration, configure names for the SNMP read and write community words,
click Input Password, enter the passwords for the SNMP read and write community words,
and click OK. The passwords for the SNMP read and write community words cannot be
the same. In SNMP Configuration, retain the default configurations for other items.
Step 4 Choose Save As from the main menu to save the template. Then set Template name, NE
type, and NE version, select a path for saving the template, and click OK.
Step 5 The system automatically redirects to the configuration template saved in the project template.
Step 6 In the configuration template, right-click AAA and User-interface, choose Delete from the
shortcut menu, and click Save.
----End
NOTE
Procedure
Step 1 Click Template Management on the main menu and choose Template Management from the
drop-down list.
Step 2 Choose Templates > Common Configuration Template > [Micro]Native-Ethernet Thrid-
Party Configuration Template Sample.
Step 3 On the Template Configuration window on the right, enter configuration information. Deselect
LoopBack Interface Configuration, FTP, SFTP and NTP Configuration, Configure frame
loss measurement and Configure frame delay measurement. Select Clock configuration and
other items are deselected by default.
NOTE
To ensure security, user names and passwords are required in all templates involving AAA configurations. AAA
and User-interface is not required in the service configuration template, but default system templates cannot
be saved when AAA and User-interface is deselected. Therefore, you can retain the AAA and User-
interface configuration first and delete it after saving the template to the project template.
1. In Configure clock time zone, enter a time zone name. Ensure that the time zone is different
from the Coordinated Universal Time (UTC).
3. In AAA and User-interface, set AAA User Name. In AAA User Password, click Input
Password, enter a password, and click OK.
NOTE
By default, Service Type is set to SSH. Do not modify it after you log in to the device for the first
time; otherwise, later login attempts will fail.
4. In Public IGP configuration and VLANs configuration, retain the default configurations.
6. In SNMP Configuration, configure names for the SNMP read and write community words,
click Input Password, enter the passwords for the SNMP read and write community words,
and click OK. The passwords for the SNMP read and write community words cannot be
the same. In SNMP Configuration, retain the default configurations for other items.
Step 4 Choose Save As from the main menu to save the template. In the dialog box that is displayed,
click OK.
Step 5 Set Template name, NE type, and NE version, select a path for saving the template, and click
OK.
Step 6 The system automatically redirects to the configuration template saved in the project template.
Step 7 In the configuration template, right-click AAA and User-interface, choose Delete from the
shortcut menu, and click Save.
----End
Issuing Configurations
This section describes link planning and DHCP remote commissioning, involving filling and
importing the link planning table, generating verification scripts, and issuing the scripts to NEs.
Context
After configuring a template for the native IP or native Ethernet scenario, you need to configure
a link planning table. The following tasks are involved:
l Use the template for the native IP or native Ethernet scenario as the extension template and
export the link planning table.
l Enter configuration information of the ATN 905 to complete the link planning table.
Procedure
Step 1 Export the link planning table.
1. In Deployment Configuration, click 3rd Party Remote Commissioning in Direct
Mode....
2. The Remote Commissioning of Third-Party NEs in Direct Mode dialog box is displayed.
a. Choose NE Information.
b. Click Export NE Planning List and the Export Link Planning Table Template
dialog box is displayed.
c. Click Choose Extend Template, set Search Location to Project Template (path for
saving the customized template for the native IP or native Ethernet scenario).
d. Click Export Link Planning Table Template. In the dialog box that is displayed,
click OK to save the link planning table to a local path. To differentiate this table from
others, name it as "xxx Site xxx Planning Table".
e. Click Import NE Planning List....
Open the saved link planning table. On the Other Configuration and ThirdParty tabs, enter
configuration information of the ATN 905.
----End
Procedure
Step 1 On the ThirdParty tab, configure parameters such as NE Name, Interface Name, Planned
ESN, Management IP Address, and Interface IP Address/Mask for each ATN 905.
Step 2 On the Other Configuration tab, enter the IGP configuration, management and service link
information, and clock tracing relationship of each ATN 905, and the static route from the ATN
905 to the service IP address of the wireless small-cell base station.
NOTE
If the small-cell base station uses the IP address of the interface directly connecting to the ATN 905 as the
service IP address, no static route needs to be configured.
In the preceding figure, the red part indicates the management plane information while the black
part indicates the service configuration information.
1. Configure the IGP.
Configure ISIS for DCNVPN The red part indicates the number of the IS-
IS process on the manage plane for the
ATN 905. You are advised to set a unique
value for all ATN 905 devices.
ISIS process description Enter the description based on the site plan.
Binding the ISIS process to a VPN instance Enter the name of the VRF instance bound
to services at the small-cell base station.
2. Configure the static route from the ATN 905 to the service IP address of the wireless small-
cell base station.
Binding the interface to a VPN instance The value can be left unspecified.
Binding the static route to a VPN instance Enter the name of the VRF instance bound
to services at the small-cell base station.
the mask length of the destination IP Enter the service IP address mask of the
address small-cell base station.
the next-hop address Enter the IP address of the link from the
small-cell base station to the ATN 905.
Each ATN 905 at the intermediate node supports 2 types of management links, that is,
upstream and downstream links. A type needs to be defined for each link (see the red part).
Each ATN 905 supports 3 types of service links and a type needs to be defined for
each link (see the black part).
Configure clock system priority Enter the priority value in the row of the
ATN 905 interface where the clock source
is introduced.
----End
?.3. Configuring a Link Planning Table (in the Native Ethernet Scenario)
This section describes how to fill in the link planning table in the native Ethernet scenario.
Procedure
Step 1 On the ThirdParty tab, configure parameters such as NE Name, Interface Name, Planned
ESN, Management IP Address, Interface IP Address/Mask, and Subinterface VLAN ID
for each ATN 905.
Step 2 On the Other Configuration tab, enter service configuration information, including the VLAN
list, service interface information, and clock tracing relationship of each ATN 905.
1. Configure IGP.
Configure ISIS for DCNVPN The red part indicates the number of the IS-
IS process on the manage plane for the
ATN 905. You are advised to set a unique
value for all ATN 905 devices.
VLANs The VLAN list must cover the VLAN range of user packets and the
management VLAN
Eth Interface Name Enter the name of the service interface and
management plane interface in use on the
ATN 905.
Allow Pass VLAN ID For the service interface, enter the service
VLAN segment (excluding the
management VLAN) that the service
interface allows to pass.
For the management plane interface, enter
the management VLAN segment
(including the management VLAN) that
the management plane interface allows to
pass.
The default VLAN of the interface is (Optional) Enter the default VLAN ID.
configured
Configure clock system priority Enter the priority value in the row of the
ATN 905 interface where the clock source
is introduced.
After entering the preceding information, save the link planning table.
----End
Procedure
Step 2 In the dialog box that is displayed, click Browse…, choose a link planning table in a local path,
and click Import.
----End
Procedure
Step 1 Choose NE Name from the Attribute drop-down list, enter a filter criterion in the Match text
box, and click Query.
Step 3 Click View Script to generate scripts and check whether the scripts are correct.
NOTE
No. Item
2 Whether the public network IP address of the management link for the upstream and
downstream devices is correctly allocated
7 Whether service interface configurations are normally generated, whether the service
interface is correctly configured as a Layer 2 interface, and whether a VLAN segment
is correctly configured for the service interface
No. Item
9 Whether the clock priority is correctly configured for the interface where the clock is
introduced
----End
Procedure
Step 1 Choose the IP address of the specified DHCP server from the DHCP Server IP Address drop-
down list, click Apply to switch to the specified DHCP server, and click Start to start the DHCP
server.
Step 2 (Optional) Query the to-go-online ATN 905 NEs in the Attribute drop-down list. You can
choose one or more NEs.
Step 3 Click Deploy Script. You can check the NE running logs when the scripts are being applied. If
a fault occurs, locate the fault according to the prompt message.
Step 4 The NE automatically goes online, click Ping to check whether connection is established
between the NE and the U2000.
----End
Scenario Overview
This section describes a networking environment.
Huawei IPRAN solution is deployed on the live network, and the macro base station bearer
solution uses a Layer 3 access solution (for example, HVPN). DCN is deployed on the
aggregation and access rings in different modes. The aggregation ring uses BGP VPN, and the
access ring uses DCN VPN. In addition, service isolation is required. The following figure shows
a networking environment.
Configuration Roadmap
This section describes the configuration procedures in the planning-free scenarios.
NOTE
The step numbers in the configuration procedure map those marked in the Plug-and-Play management
interface and the U2000. Each step with a specified sequence number is performed on the corresponding
interface.
Understand the macro base station management plane configurations and prepare the link
relationship data. Then enter the plug-and-play management interface, configure remote
commissioning parameters, and establish a channel for exchange between the NE and the U2000.
Customize templates, including the basic configuration template for managing the ATN 905
going online, service configuration template to be issued to the ATN 905, and extension
configuration template to be issued to the ATN device at a macro base station. In the U2000's
DCN management view, select templates, add configurations, and issue these configurations to
the ATN device at a macro base station and the ATN 905.
1. Select the mode in which devices go online. On networks formed with Huawei equipment
only, devices can go online in DCN mode.
2. Set NE login parameters and enter related parameters to establish connection to the U2000
and achieve authentication and network management.
3. Select the private network solution for the management channel based on the management
plane used by the macro base station to automatically generate a private network
configuration template.
4. Customize the basic configuration template. Specifically, use the basic configuration
template for the ATN 905 going online on the H-VPN established in the native IP access
scenario (using the macro base station).
5. On the template management interface, customize the ATN 905 service template based
on the [Micro]Native-IP Service Configuration Template Sample.
6. On the template management interface, customize the extension service template for the
ATN device at a macro base station based on [Micro]Native-IP CSG Extend Configuration
Template Sample.
7. Enter the U2000's DCN management view and issue extension configurations to the ATN
device at the macro base station.
8. In the U2000's DCN management view, select the basic configuration template and private
network configuration template, add the service configuration template as an extension
template, add service configurations for the ATN 905, and issue the service configurations
to the ATN 905.
Configuration Procedure
This section describes how to deploy NEs and configure services in the planning-free scenario.
Data Preparation
Management Plane Link IP address pool, management IP address pool, IGP protocol, and
Parameters IGP process number
Service Plane Service link IP address plan, service IGP protocol, service IGP
Parameter process number, service VLAN, and VRF name, Clock tracing
relationship
2. Click to enter the Application Panel interface. Choose the Application Center tab
and double-click Fix-Network NE Configuration.
NOTE
The U2000 supports application and traditional styles. If the application style is used, perform this
step. If the traditional style is used, skip this step. By default, the U2000 uses the traditional style.
4. On the iManager U2000 IP Plug-and-Play Management interface, set User name and
Password and validate code of the U2000 client and click Login to enter the plug-and-
play management interface.
Procedure
Step 1 Configure the protocol for NEs going online.
Deploy Huawei IPRAN solution, use BGP VPN + DCN VPN as the private network solution,
and select DCN networking.
l If you choose SNMPv1 or SNMPv2c, enter the read and write community words in SNMPv1 or
SNMPv2c parameters. Then click to enter the passwords. The passwords of the read and write
community words cannot be the same. Otherwise, the device cannot go online.
l If you choose SNMPv3, enter SNMPv3 parameters including the SNMP group user name, SNMP
group, MD5 password, and DES password. Then click to enter the passwords.
l You can choose SNMPv1, SNMPv2c, and SNMPv3 concurrently.
5. Configure the IP addresses and masks for the primary and secondary NMS servers.
6. Click Apply.
Step 3 Customize an NE management channel.
Set an NE management channel solution. Select the private network solution because a macro
base station is managed using a private network.
----End
Customizing Templates
This topic describes how to customize templates for managing the ATN 905 going online and
issuing service configurations to the ATN 905 and customizing an extension configuration
template for the ATN device at a macro base station.
?.1. Customizing a Template for Managing the ATN 905 Going Online
This topic describes how to customize a template for managing the ATN 905 going online in
the native IP scenario.
NOTE
Procedure
Step 1 Choose Basic NE Configurations, click the Customizing Basic Configuration Solutions tab,
and enter the service plan on the macro base station side. Ensure that parameters on the access
side are consistent with those on the macro base station side.
1. Select a service solution. In the native IP access scenario, set Service Solution to HVPN
Solution.
2. Select an aggregation-side network solution based on the actual plan of the macro base
station on the live network.
3. Select an access-side network solution based on the actual plan of the macro base station
on the live network.
4. Select BGP route strategy based on the actual plan of the macro base station on the live
network.
5. Set NE Role to CSG.
6. Click Apply.
The basic configuration template for managing the ATN 905 going online can be established
using 2 methods.
NOTE
Templates established using the 2 methods are consistent. The following uses method 1 as an example.
l Method 1: Click Create to create a template. Then save the template.
l Method 2: Execute [HVPN-CSG]Basic Configuration Template Sample that is generated
after the Customizing Basic Configuration Solutions step is complete. The template name
contains the time when the template was generated. Click Modify, modify the template based
on the ATN 905 requirements, and save the template as an ATN 905 template.
2. Configure common parameters by referring to the NE Login Parameters step and click
Next.
3. On the Configuration Template tab, enter the template name and click Show Details.
4. On the Configuration Template tab, enter configuration information and the template for
managing the ATN 905 going online is completed. Ensure that Configure clock time
zone, NE Basic Configuration, AAA and User-interface, IGP Configuration,
LoopBack Interface Configuration, Network Interface Configuration are selected and
others are deselected.
l In Configure clock time zone, enter a time zone name. Ensure that the time zone is
different from the Coordinated Universal Time (UTC).
The procedure of customizing the template for managing the ATN 905 going online is
complete.
----End
NOTE
Procedure
Step 1 Click Template Management > Template Management.
Step 2 Choose Templates > Common Configuration Template > [Micro]Native-IP Basic
Configuration Template Sample.
Step 3 On the Template Configuration window on the right, enter configuration information.
l When services do not need to be isolated, ensure that Private IGP Configuration, Configure
a static route, Network Interface Configuration, and Clock configuration are selected
and other items are deselected.
l When services need to be isolated, select VRF Configuration.
1. Select VRF configurations in the scenario where services need to be isolated.
5. Click Save.
6. In the dialog box that is displayed, click OK. The procedure of customizing the basic service
configuration template is complete.
----End
Sample and save the template as Native-IP CSG Extend Configuration Template Sample -
upe.
NOTE
Procedure
Step 1 Click Template Management > Template Management.
Step 2 Choose Templates > Common Configuration Template > [Micro]Native-IP CSG Extend
Configuration Template Sample.
Step 3 On the Template Configuration window on the right, enter configuration information and save
the template.
1. In BGP Configuration, enter the BGP AS number and VPN instance name for the upper-
layer IP RAN service and deselect Import OSPF Route. Other items are selected by
default.
2. In IGP Configuration, enter the name of the VPN instance on the upper-layer IP RAN for
Binding the ISIS process to a VPN instance. Other items are selected by default.
3. In Service Configuration, enter the name of the VPN instance on the upper-layer IP RAN
for Binding the interface to a VPN instance. Other items are selected by default.
NOTE
If services need to be isolated for the ATN device at a macro base station, select VRF
Configuration. Otherwise, retain the default configuration (deselected).
Procedure
Step 1 Click Deployment Configuration > Deployment Overview > Basic NE Configurations >
Extend Configuration Template.
Step 2 Click Select Extend Configuration Template. Select Project Tempalte in the Search
Location, select configuration template for ATN 905 and the ATN device at a macro base station,
----End
?.2. Issuing Extension Configurations to the ATN Device at a Macro Base Station
This section describes how to issue extension configurations to the ATN device at a macro base
station using the Native-IP CSG Extension Configuration Template Sample.
Prerequisites
The U2000 client has been started.
The ATN device at the macro base station has gone online.
Procedure
Step 1 On the Online NE Commissioning interface, click
Step 2 Set the ATN device at the macro base station to the gateway NE (GNE). Specifically, click
or right-click Gateway NE Tree from the Navigation Tree on the left and choose Set Gate
NE from the shortcut menu.
Step 3 Right-click in the blank area and choose Synchronize from the shortcut menu. The to-go online
ATN 905 appears in the topology diagram.
Step 4 Choose the ATN device at the macro base station, right-click, and click Apply Basic
Configuration > Plan and Apply Additional Data.
Step 5 Select the Native-IP CSG Extend Configuration Template Sample - upe, click Next.
ISIS process description Enter the description based on the site plan.
Step 7 Click OK. In the dialog box that is displayed, click Apply Configuration.
----End
Prerequisites
The U2000 client has been started.
The ATN device at the macro base station has gone online.
Procedure
Step 1 On the DCN Management for Routers interface, choose the ATN 905 and click Apply Basic
Configuration > Basic Configuration Planned And Apply.
Step 2 Enable the ATN 905 to go online without a planning tool. Specifically, choose the ring where
the ATN 905 resides and click Next.
Step 3 Choose all ATN 905 devices, modify the basic configuration templates in batches, and choose
the template for managing the ATN 905 going online.
private network configuration template, which has been created when you customize the NE
management channel.
Step 4 Choose all ATN 905 devices, click Extend Configuration Template, add the Native IP service
configuration template for the ATN 905, and configure related parameters.
1. Configure IGP parameters.
Binding the ISIS process to a VPN instance Enter the name of the VRF instance bound
to services at the small-cell base station.
ISIS process description Enter the description based on the site plan.
2. Configure parameters for the static route from the ATN 905 to the service IP address of the
wireless small-cell base station.
Binding the static route to a VPN instance Enter the name of the VRF instance bound
to services at the small-cell base station.
the mask length of the destination IP Enter the service IP address mask of the
address small-cell base station.
the next-hop address Enter the IP address of the link from the
small-cell base station to the ATN 905.
Each ATN 905 supports 3 types of service links and a type needs to be defined for each
link.
Binding the interface to a VPN instance Enter the name of the VRF instance bound
to services at the small-cell base station.
Interface ISIS process ID Enter the number of the IS-IS process for
services at the small-cell base station.
Configure clock system priority Enter the priority value in the row of the
ATN 905 interface where the clock source
is introduced.
Step 5 Click OK. In the dialog box that is displayed, click Apply Configuration.
----End
Application Scenarios
1. Small-cell base station bearer scenario
Mobile networks are transforming from dominant macro base stations to co-existing macro
and small-cell base stations. In addition, small-cell base stations, with characteristics such
as low cost, wide coverage, and easy installation, will play a more and more important role
in future network construction.
In Huawei's mobile bearer solution, ATN 905 devices are used as small-cell base station
bearer NEs and connected to the access device (the CSG in the figure) at the macro base
station in chain networking mode. As an extension of the IPRAN mobile bearer solution
based on the macro base station, Huawei's mobile bearer solution integrates mobile bearer
clock and maintenance solutions in an end-to-end manner, and features low cost, easy
deployment, and easy O&M. Figure 1 shows the networking diagram of the solution using
the ATN 905 as the bearer device at the small-cell base station.
Figure 4-14 Networking diagram of the small-cell base station bearer solution
Small-cell Base IPRAN
Station Access
BSC
RNC
NOTE
The mobile bearer device at the macro base station may be a third-party device. In this topic, Huawei's
IPRAN solution (ATN + CX networking) on the macro base station side is used as an example to illustrate
the deployment configuration.
EDD Scenario
ASG RSG
CSG
EDD
RNC
ATN 905
As shown in Figure 3, an enterprise rents a 100M private line from a provider. However,
the enterprise user considers the bandwidth as lower than 100 M. In the case of a fault on
the enterprise user network, the enterprise user tends to call the provider and complain.
How can the provider divide the maintenance responsibilities? The provider can deploy an
EDD near the CPE and test the throughput using RFC 2544 before the deployment so as
to prove that the bandwidth meets the requirements. After services are provisioned, the
EDD monitors service packets in real time using IP FPM, obtains information such as the
throughput, packet loss rate, latency, and jitter, and periodically provides an SLA to the
enterprise user so as to prove the provider's network quality.
CPE PE PE CPE
EDD PE PE
ATN 905
B
A
NOTE
For easy description, the upstream network of the EDD is called aggregation network.
Networking Models
In both solutions, the ATN 905 is connected to the nearby network of the operator. If the
operator's network is regarded as an abstract "cloud", only the deployment and configuration of
the part (marked by the dotted rectangle on the left) on the access network need to be considered.
For the marked part of the access network, the configuration roadmaps and procedures in both
solutions are basically the same. Therefore, this topic only provides detailed configuration
description from the angle of the access technology. That is, scenarios are not differentiated
while only solutions are differentiated. The following typical networking models are provided
for the configuration example.
l Native IP scenario: Layer 3 IP packets are forwarded between the ATN 905 and CSG.
Micro/Pico
Macro Cell
RNC/SGW
Micro/Pico
Native IP
Traffic flow
l Native Ethernet scenario: Layer 2 Ethernet packets are forwarded between the ATN 905
and CSG.
Micro/Pico
Macro Cell
RNC/SGW
Micro/Pico
Native Eth
Traffic flow
Configuration Overview
Figure 4-19 Relationship between the iManager U2000 IP LCT interface and ATN 905
configuration
l Small-cell Base Station Bearer Scenario: If a Layer 3 access solution (such as Native IP solution
HVPN) is used on the macro base station side, you are advised to deploy the
native IP solution between the ATN 905 and cell site gateway (CSG) to forward
services.
l EDD Scenario: If a Layer 3 access solution (such as MPLS/IP) is used on the
aggregation network, you are advised to deploy the native IP solution between
the ATN 905 and PE to forward services.
This solution facilitates end-to-end IP-based continuity check (CC) and
performance monitoring.
l Small-cell Base Station Bearer Scenario: If a Layer 2 or Layer 2 + Layer 3 Native Ethernet solution
access solution (such as mixed VPN) is used on the macro base station side, you
are advised to deploy the native Ethernet solution between the ATN 905 and
CSG to transparently transmit packets from the small-cell base station.
l EDD Scenario: If a Layer 2 access solution (such as metro Ethernet) is used on
the aggregation network, you are advised to deploy the native Ethernet solution
between the ATN 905 and PE to forward services.
In this solution, the VLAN information of the small-cell base station or enterprise
private line user is not modified. Instead, packets of the small-cell base station or
enterprise private line user are transparently transmitted.
2. Going online protocol selection: On the iManager U2000 IP LCT interface, click
Apply without the need of focusing on DCN or DHCP selection.
3. NE management channel selection: Click Apply without the need of focusing on public
or private network selection.
4. Basic configuration selection: Select and customize the management plane configuration
template and service configuration template based on the native IP or native Ethernet
solution.
Template The following two templates are required: The following two templates are required:
l A template for managing the ATN 905 going l A template for managing the ATN 905
online: Choose Basic NE Configurations > going online: Choose Basic NE
Checking Basic Configuration Template. Configurations > Checking Basic
On the Checking Basic Configuration Configuration Template. On the
Template tab page, click Create to customize Checking Basic Configuration Template
the basic configuration template, which is used tab page, click Create to customize the basic
to configure the management plane. The configuration template, which is used to
procedure for creating the basic configuration configure the management plane. The
template is similar to that on the ATN device procedure for creating the basic
at a macro base station. For details, see configuration template is similar to that on
Customizing a Template for Managing the the ATN device at a macro base station. For
ATN 905 Going Online. details, see Customizing a Template for
Managing the ATN 905 Going Online.
5. Link planning: Allocate IP resources, add the templates to the link planning table, and
export the link planning table. Fill configuration parameters and import the link planning
table to generate configuration scripts.
6. Configuration issuing: Process the generated scripts, which can be used as a standard
template for reference. Log in to the ATN 905 to issue script configurations.
NOTE
This document describes the process of issuing ATN 905 configurations. The process of issuing the
configurations of the upstream CSG at the macro base station is similar to that of issuing the configurations
of the ATN 905. For configuration details, see Configuration Reference for the ATN Device at the
Upstream Macro Base Station.
NOTE
To log in to http://support.huawei.com and download the software package, you must apply for an account.
The name of the folder can contain only letters, digits, and underscores (_) to ensure that all functions
can work properly.
2. Double-click the lct_start.vbs file in the folder.
4. When Open Home Page becomes available, click to start the IP LCT client.
5. On the login interface, enter the user name, password, and verification code. The default
user name and password are admin and Changeme_123, respectively.
6. Click Login.
NOTE
When you log in for the first time, change the password as prompted.
Scenario Overview
This section describes the networking.
When the live network is a Huawei IPRAN and the macro base station bearer solution uses a
Layer 3 access solution (for example, the HVPN solution), the ATN 905 accesses a carrier
network through Layer 3 IP packet forwarding. This scenario is called a native IP access scenario.
In the native IP access scenario, select the native IP basic configuration template on the IP LCT
to customize configurations. Different from the native Ethernet access scenario, the native IP
access scenario involves service-plane IGP configurations and VRF configurations for service
isolation (optional).
Configuration Roadmap
According to the operation procedures on the left of the IP LCT interface, customize
configuration templates and export scripts. Then log in to the ATN 905, copy the script
configurations, and issue them to the ATN 905.
Configuration Procedure
This section describes how to use the IP LCT to customize configurations for the ATN 905.
After the configuration scripts are generated, the configurations can be issued using commands.
Data Preparation
Specify basic management parameters for the ATN 905 and ensure that management parameters
on all ATN 905 devices are consistent.
Management Plane Link IP address pool, management IP address pool, IGP, and IGP
Parameters process number
Service Plane Service link IP address plan, service IGP, service IGP process
Parameters number, VRF name, and clock tracing relationship
Procedure
Step 1 Configure the NE going online protocol.
----End
Customizing Templates
This topic describes how to customize templates for managing the ATN 905 going online and
issuing service configurations to the ATN 905.
?.1. Customizing a Template for Managing the ATN 905 Going Online
The template applies in native IP scenarios and its contents are ATN 905 management-plane
configurations.
NOTE
Procedure
Step 1 Choose Basic NE Configurations, click the Customizing Basic Configuration Solutions tab,
and enter the service plan on the macro base station side. Ensure that parameters on the access
side are consistent with those on the macro base station side.
1. Select a service solution. In the native IP access scenario, set Service Solution to HVPN
Solution.
2. Select an aggregation-side network solution based on the actual plan of the macro base
station on the live network. For the macro base station, if IGP Solution is set to ISIS,
choose ISIS; if MPLS Solution is set to MPLS TE, choose MPLS TE.
3. Match the network solution on the access side with that on the aggregation side.
Specifically, set IGP Solution to ISIS Multi-Process and MPLS Solution to MPLS
TE. Then set Access-side IGP Assignment Rule to Unique on the network.
4. Select a BGP routing policy at the macro base station as required.
5. Set NE Role to CSG.
6. Click Apply.
The basic configuration template for managing the ATN 905 going online can be established
using 2 methods.
NOTE
Templates established using the 2 methods are consistent. The following uses method 1 as an example.
l Method 1: Click Create to create a template. Then save the template.
l Method 2: Execute [HVPN-CSG]Basic Configuration Template Sample that is generated
after the Customizing Basic Configuration Solutions step is complete. The template name
contains the time when the template was generated. Click Modify, modify the template based
on the ATN 905 requirements, and save the template as an ATN 905 template.
4. On the Configuration Template tab, enter configuration information and the template for
managing the ATN 905 going online is completed. Ensure that Configure clock time
zone, NE Basic Configuration, AAA and User-interface, IGP Configuration,
LoopBack Interface Configuration, Network Interface Configuration, FTP, SFTP
and NTP Configuration, and SNMP Configuration are selected and others are
deselected.
l In Configure clock time zone, enter a time zone name. Ensure that the time zone is
different from the Coordinated Universal Time (UTC).
l In NE Basic Configuration, retain the default configurations.
NOTE
This network entity must be unique for each device. The area address is designed based on user
demands. To change the area address, click Set Expression. The default value is 49.0001.
l Retain the default selection configuration for LoopBack Interface Configuration and
Network Interface Configuration.
l In FTP, SFTP and NTP Configuration, deselect NTP Service Source Interface and
NTP Service Unicast Service IP.
5. After the preceding configurations are complete, click Finish. The procedure of
customizing the template for managing the ATN 905 going online is complete.
----End
NOTE
Procedure
Step 1 Click Template Management > Template Management.
Step 2 Choose Templates > Common Configuration Template > [Micro]Native-IP Basic
Configuration Template Sample.
Step 3 On the Template Configuration window on the right, enter configuration information.
l When services do not need to be isolated, ensure that Private IGP Configuration, Configure
a static route, Network Interface Configuration, and Clock configuration are selected
and other items are deselected.
l When services need to be isolated, select VRF Configuration.
1. Select VRF configurations in scenarios where services need to be isolated.
3. In Private IGP Configuration, set Network Entity. Set Expression indicates that a
network entity name is calculated using the formula by default. Deselect ISIS Name and
set-overload on-startup.
NOTE
This network entity must be unique for each device. The format of the value is area address (1 to 13
bytes).system ID (6 bytes).SEL(00). The area address is designed based on user demands. To change
the area address, click Set Expression. The default value is 49.0001.
4. Choose Save As from the main menu to save the template. In the dialog box that is
displayed, click OK.
l Select a path for saving the template. The default path is Project Template.
l Set Template name.
l Set NE type and NE version.
l Click OK.
5. Optional: When services need to be isolated, configure VRFs as many as VPNs that carry
services. You can add VRFs in the template by copying.
Click VRF Configuration, Copy, and Paste in sequence to copy a VRF.
Click Save.
6. In the dialog box that is displayed, click OK. The procedure of customizing the basic service
configuration template is complete.
----End
Issuing Configurations
Plan an IP address pool, and fill parameters in the link planning table. After the link planning
table is imported, IP addresses are automatically assigned from the address pool. Scripts are
generated in IP LCT script management, and then configurations are issued to the ATN 905
based on the scripts.
Link Planning
In the link planning phase, complete the following tasks:
1. Plan address pool resources so that LSR IDs and link IP addresses can be automatically
allocated after the link planning table is imported.
2. Use the service configuration template as the extension template and export the link
planning table.
3. Enter basic information of the ATN 905 and link information of the upstream NE.
Procedure
Step 1 Plan an address pool.
1. Click Deployment Configuration > Deployment Overview and choose Link Plan.
2. On the Address Pool Planning tab, click Create. In the dialog box that is displayed, click
OK. To create an address pool for the management plane LSR IDs, set IP Pool Name, set
IP Pool Type to LSR ID Address Pool, set Start IP and End IP, and set Mask Length
to 32.
3. Click Create and a dialog box is displayed. To create an address pool for link IP addresses,
set IP Pool Name, set IP Pool Type to Link IP Address Pool, set Start IP and End IP,
and set Mask Length to 30.
.
2. In the Export Link Planning Table Template dialog box that is displayed, click Choose
Extend Template. In the Choose Extend Template dialog box that is displayed, set
Search Location to Project Template (the path for saving the customized service
3. Click Export Link Planning Table Template. In the dialog box that is displayed, click
OK to save the link planning table to a local path. To differentiate this table from others,
name it as "xxx Site xxx Planning Table".
2. Plan the link connection relationship. Specifically, choose the NetworkLayout tab and
enter the ATN 905 information in the columns with a green header and the upstream NE
information in the columns with a yellow header. Address pools have been planned, so
LSR ID and Interface IP Address/mask can be left unspecified. When devices goes
online, addresses are automatically allocated for them from the address pools.
3. On the Aggregate_NE_INFO tab, enter the information about the ring where the ATN
905 resides. Set Ring Name to RING1, a new ring established based on the ATN 905.
4. On the Other Configuration tab, enter service configuration information, including the
IGP protocol, service link information, and clock tracing relationship of each ATN 905,
and the static route from the ATN 905 to the service IP address of the wireless small-cell
base station.
NOTE
If the small-cell base station uses the IP address of the interface directly connecting to the ATN 905
as the service IP address, no static route needs to be configured.
Binding the ISIS process to a VPN instance Enter the name of the VRF instance bound
to services at the small-cell base station.
ISIS process description Enter the description based on the site plan.
Table 4-22 Parameters for the static route from the ATN 905 to the service IP address of
the wireless small-cell base station
Binding the static route to a VPN instance Enter the name of the VRF instance bound
to services at the small-cell base station.
the mask length of the destination IP Enter the service IP address mask of the
address small-cell base station.
the next-hop address Enter the IP address of the link from the
small-cell base station to the ATN 905.
Binding the interface to a VPN instance Enter the name of the VRF instance bound
to services at the small-cell base station.
Interface ISIS process ID Enter the number of the IS-IS process for
services at the small-cell base station.
NOTE
Each ATN 905 supports 3 types of service links and a type needs to be defined for each link.
l Link leading upstream to the ATN device
l Link leading to the wireless small-cell base station
l Link leading downstream to the ATN 905
Configure clock system priority Enter the priority value in the row of the
ATN 905 interface where the clock source
is introduced.
5. After entering the link connection relationship, ring information, and service configuration
information, save the link planning table.
----End
Procedure
Step 1 Click Link Plan. On the Interconnection Relationship Planning tab, click
Step 2 In the dialog box that is displayed, choose the link planning table and click Next.
Step 3 In the Import Parameter Set dialog box that is displayed, modify Configuration Rules for
Link Planning, select Automatic configuration, and click Configuration to perform advanced
configuration.
1. In the Advanced Configuration dialog box that is displayed, select Assign LSR ID
automatically, click Select IP Address Pool on the right, and choose the planned LSR ID
address pool.
2. Select Configure IP Address, click Select IP Address Pool on the right, choose the
planned link IP address pool, and click OK.
3. Click Next. In the dialog box that is displayed, check whether the entered data is correct
and click OK to import the data.
2. In the Select Template dialog box that is displayed, choose the created template for
managing the ATN 905 going online, and click OK. The default template for managing
the ATN 905 going online is the newly-created one.
----End
Procedure
Step 1 Click Script Management > Script Management > NE List.
1. Choose NE Name from the Attribute drop-down list, enter a filter criterion in the
Match text box, and click Query. Then choose the desired NE in the list below.
2. Modify the basic NE information, including the NE type and version.
3. Click Apply.
Step 3 In the Navigation Tree, choose an NE under the NE List node to generate configuration scripts.
Step 4 Click Basic configuration scripts. In the Script Configuration field, click Verify Script. Then
query the verification result based on Error Number and click Previous Error or Next
Error to locate errors.
You are advised to check whether the following parameter settings meet project requirements:
l AS number
l AAA parameters
l U2000 server IP address
NOTE
The verification can detect syntax errors but cannot detect semantic errors. Generally, command errors
occur when parameters are set incorrectly or the current version does not support some commands.
----End
Procedure
Step 1 Select the generated scripts, and click Export Script. Each ATN 905 has two scripts: basic
configuration script of the management plane and service configuration script of the service
plane.
Step 2 Choose to save the file, and click OK. The scripts are automatically saved to the local path.
Step 3 Open the TXT file for the basic configuration script, and change the ciphertext passwords for
AAA and SNMP to desired simple passwords to ensure that the script can be successfully issued
when you log in to the ATN 905 through a serial interface.
1. Change the AAA password to a simple password.
Step 4 Add Y or N for an interactive command in the script so that the script configuration can be
directly copied to the ATN 905 for issuing.
Y indicates the subsequent action of the command. N indicates that the command is canceled.
For example, the save command is an interactive command.
Step 5 Log in to the ATN 905 through the serial interface, and copy commands from the TXT script
file to the ATN 905 for configuration issuing.
----End
Appendix
Configuration Reference for the ATN Device at the Upstream Macro Base Station
When the ATN 905 goes online, the ATN device at the upstream macro base station must also
issue some configurations for service interworking.
Procedure
Step 1 Configure a template, and add it to a link planning table. Then complete the link planning table
to generate the configurations for the ATN device at the upstream macro base station.
NOTE
If packet loss and delay statistics do not need to be configured, the native Ethernet CSG extension
configuration template may not be used. This does not affect ATN 905 going online.
1. Select [Micro]Native-IP CSG Extend Configuration Template Sample and [Micro]
Native Ethernet CSG Extend Configuration Template Sample for native IP and native
Ethernet scenarios, respectively.
2. The CSG extension template is added to a link planning table as an additional template.
Export the link planning table, and set service configuration information for the ATN device
at the macro base station on the Other Configuration tab page.
Table 4-25 Configuration parameters for the ATN device at the macro base station
ISIS process description Enter the description based on the site plan.
3. Save the link planning table. After the link planning table is imported, the configuration
script for the ATN device at the macro base station is generated, and then configurations
are issued to the ATN device at the macro base station based on the script.
----End
Scenario Overview
This section describes the networking.
This solution is recommended when the live network is large-scale and formed with Huawei's
IP RAN products, the macro base station bearer solution is a Layer 2 or Layer 2 + Layer 3
solution, and macro base stations use the public network management plane.
Configuration Roadmap
According to the operation procedures on the left of the IP LCT interface, customize
configuration templates and export scripts. Then log in to the ATN 905, copy the script
configurations, and issue them to the ATN 905.
1. Select the mode in which the ATN 905 goes online. When the IP LCT is used, select DCN
or DHCP, which does not affect configuration customization.
2. Set NE login parameters and enter related parameters to establish connection to the U2000
and achieve authentication and network management.
3. Select the management channel. When the IP LCT is used, select the public or private
network solution. The public network solution is selected in this document.
4. Customize the basic configuration template. In the native Ethernet access scenario, select
the Layer 2+Layer 3 solution and create the basic configuration template for ATN 905
going online management.
5. On the template management interface, customize the ATN 905 service template based on
the [Micro]Native-Ethernet Service Configuration Template Sample.
6. Import the service template to the link planning table as an extension template, export the
link planning table, and enter the link relationship and service planning data. Then import
the link planning table.
7. Check whether the generated scripts are correct.
8. Export the scripts. Log in to the ATN 905 and issue configurations to the ATN 905.
Configuration Procedure
This section describes how to use the IP LCT to customize configurations for the ATN 905.
After the configuration scripts are generated, the configurations can be issued using commands.
Data Preparation
Specify basic management parameters for the ATN 905 and ensure that management parameters
on all ATN 905 devices are consistent.
Management Plane Link IP address pool, management IP address pool, IGP, and IGP
Parameters process number
Service Plane Service link IP address plan, service IGP, service VLAN, VRF name,
Parameters and clock tracing relationship
Procedure
Step 1 Configure the NE going online protocol.
----End
Customizing Templates
This topic describes how to customize templates for managing the ATN 905 going online and
issuing service configurations to the ATN 905.
?.1. Customizing a Template for Managing the ATN 905 Going Online
The template applies in native Ethernet scenarios and its contents are ATN 905 management-
plane configurations.
NOTE
Procedure
Step 1 Choose Basic NE Configurations, click the Customizing Basic Configuration Solutions tab,
and enter the service plan on the macro base station side. Ensure that parameters on the access
side are consistent with those on the macro base station side.
1. Select the service plan. In the native Ethernet access scenario, select L2+L3 Solution.
2. Select an aggregation-side network solution based on the actual plan of the macro base
station on the live network. For the macro base station, if IGP Solution is set to ISIS,
choose ISIS; if MPLS Solution is set to MPLS TE, choose MPLS TE.
3. Match the network solution on the access side with that on the aggregation side.
Specifically, set IGP Solution to ISIS Multi-Process and MPLS Solution to MPLS
TE. Then set Access-side IGP Assignment Rule to Unique on the network.
4. Select a BGP routing policy at the macro base station as required.
5. set NE Role to CSG.
6. Click Apply.
The basic configuration template for managing the ATN 905 going online can be established
using 2 methods.
NOTE
Templates established using the 2 methods are consistent. The following uses method 1 as an example.
l Method 1: Click Create to create a template. Then save the template.
l Method 2: Execute [L2+L3-CSG]Basic Configuration Template Sample that is generated
after the Customizing Basic Configuration Solutions step is complete. The template name
contains the time when the template was generated. Click Modify, modify the template based
on the ATN 905 requirements, and save the template as an ATN 905 template.
4. On the Configuration Template tab, enter configuration information. Then the template
for managing the ATN 905 going online is completed.
On the default template, deselect MPLS Configuration and ensure that Configure clock
time zone, NE Basic Configuration, AAA and User-interface, IGP Configuration,
LoopBack Interface Configuration, Network Interface Configuration, FTP, SFTP
and NTP Configuration, and SNMP Configuration are selected.
l In Configure clock time zone, enter a time zone name. Ensure that the time zone is
different from the Coordinated Universal Time (UTC).
l In NE Basic Configuration, retain the default configurations.
l Retain the default selection configuration for LoopBack Interface Configuration and
Network Interface Configuration.
l In FTP, SFTP and NTP Configuration, deselect NTP Service Source Interface and
NTP Service Unicast Service IP.
5. After the preceding configurations are complete, click Finish. The procedure of
customizing the template for managing the ATN 905 going online is complete.
----End
NOTE
Procedure
Step 1 Click Template Management > Template Management.
Step 2 Choose Templates > Common Configuration Template > [Micro]Native-Ethernet Service
Configuration Template Sample.
Step 3 On the Template Configuration window on the right, enter configuration information.
1. Ensure that VLANs configuration, Network Interface Configuration, and Clock
configuration are selected and other items are deselected.
Step 4 Choose Save As from the main menu to save the template. In the dialog box that is displayed,
click OK.
l Select a path for saving the template. The default path is Project Template.
l Set Template name.
Step 5 The system automatically redirects to the configuration template saved in the project template.
The procedure of customizing the basic service configuration template is complete.
----End
Issuing Configurations
Plan an IP address pool, and fill parameters in the link planning table. After the link planning
table is imported, IP addresses are automatically assigned from the address pool. Scripts are
generated in IP LCT script management, and then configurations are issued to the ATN 905
based on the scripts.
Link Planning
In the link planning phase, complete the following tasks:
l Plan address pool resources so that LSR IDs and link IP addresses can be automatically
allocated after the link planning table is imported.
l Use the service configuration template as the extension template and export the link
planning table.
l Enter basic information of the ATN 905 and link information of the upstream NE to
complete the link planning table.
Procedure
Step 1 Plan an address pool.
1. Click Deployment Configuration > Deployment Overview and choose Link Plan.
2. On the Address Pool Planning tab, click Create. In the dialog box that is displayed, click
OK. To create an address pool for the management plane LSR IDs, set IP Pool Name, set
IP Pool Type to LSR ID Address Pool, set Start IP and End IP, and set Mask Length
to 32.
3. Click Create and a dialog box is displayed. To create an address pool for link IP addresses,
set IP Pool Name, set IP Pool Type to Link IP Address Pool, set Start IP and End IP,
and set Mask Length to 30.
4. Planning of the LSR ID address pool and link IP address pool is complete.
.
2. In the Export Link Planning Table Template dialog box that is displayed, click Choose
Extend Template. In the Choose Extend Template dialog box that is displayed, set
Search Location to Project Template (the path for saving the customized service
3. Click Export Link Planning Table Template. In the dialog box that is displayed, click
OK to save the link planning table to a local path. To differentiate this table from others,
name it as "xxx Site xxx Planning Table".
1. Open the saved link planning table, enter the link connection information, ring information,
and service configuration information on the NetworkLayout, Aggregate_NE_INFO,
and Other Configuration tabs respectively.
2. Plan the link connection relationship. Specifically, choose the NetworkLayout tab and
enter the ATN 905 information in the columns with a green header and the upstream NE
information in the columns with a yellow header. Address pools have been planned, so
LSR ID and Interface IP Address/mask can be left unspecified. When devices goes
online, addresses are automatically allocated for them from the address pools.
3. On the Aggregate_NE_INFO tab, enter the information about the ring where the ATN
905 resides. Set Ring Name to RING1, a new ring established based on the ATN 905.
4. On the Other Configuration tab, enter service configuration information, including the
VLAN list, service interface information, and clock tracing relationship of each ATN 905.
VLANs The VLAN list must cover the VLAN range of user packets and the
management VLAN (set in the "Plan the link connection relationship"
step).
Eth Interface Enter the name of the service interface in use on the ATN 905.
Name
Service Enter the description based on site regulations. You are advised to enter
interface the name of the peer NE.
description
Allow Pass Enter the service VLAN segment (excluding the management VLAN)
VLAN ID that the service interface allows to pass.
The default (Optional) Enter the default VLAN ID of the service interface.
VLAN of the
interface is
configured
Interface Enable clock synchronization for all main service interfaces and enter
Name the names of main service interfaces (one for each row).
Configure Enter the priority value in the row of the ATN 905 interface where the
clock system clock source is introduced.
priority
5. After entering the link connection relationship, ring information, and service configuration
information, save the link planning table.
----End
Procedure
Step 1 Click Link Plan. On the Interconnection Relationship Planning tab, click
Step 2 In the dialog box that is displayed, choose the link planning table and click Next.
Step 3 In the Import Parameter Set dialog box that is displayed, modify Configuration Rules for
Link Planning, select Automatic configuration, and click Configuration to perform advanced
configuration. The operation steps are marked with numbers in the following figure.
1. In the Advanced Configuration dialog box that is displayed, select Assign LSR ID
automatically, click Select IP Address Pool on the right, and choose the planned LSR ID
address pool.
2. Select Configure IP Address, click Select IP Address Pool on the right, choose the
planned link IP address pool, and click OK.
3. Click Next. In the dialog box that is displayed, check whether the entered data is correct
and click OK to import the data.
2. In the Select Template dialog box that is displayed, choose the created template for
managing the ATN 905 going online, and click OK. The default template for managing
the ATN 905 going online is the newly-created one.
----End
Procedure
Step 1 Click Script Management > Script Management > NE List.
1. Choose NE Name from the Attribute drop-down list, enter a filter criterion in the
Match text box, and click Query. Then choose the desired NE in the list below.
2. Modify the basic NE information, including the NE type and version.
3. Click Apply.
Step 3 In the Navigation Tree, choose an NE under the NE List node to generate configuration scripts.
Step 4 Click Basic configuration scripts. In the Script Configuration field, click Verify Script. Then
query the verification result based on Error Number and click Previous Error or Next
Error to locate errors.
NOTE
No. Item
2 Whether the public network IP address of the management link for the upstream and
downstream devices is correctly allocated
7 Whether service interface configurations are normally generated, whether the service
interface is correctly configured as a Layer 2 interface, and whether a VLAN segment
is correctly configured for the service interface
9 Whether the clock priority is correctly configured for the interface where the clock is
introduced
NOTE
The verification can detect syntax errors but cannot detect semantic errors. Generally, command errors
occur when parameters are set incorrectly or the current version does not support some commands.
----End
Procedure
Step 1 Select the generated scripts, and click Export Script. Each ATN 905 has two scripts: basic
configuration script of the management plane and service configuration script of the service
plane.
Step 2 Choose to save the file, and click OK. The scripts are automatically saved to the local path.
Step 3 Open the TXT file for the basic configuration script, and change the ciphertext passwords for
AAA and SNMP to desired simple passwords to ensure that the script can be successfully issued
when you log in to the ATN 905 through a serial interface.
1. Change the AAA password to a simple password.
Step 4 Add Y or N for an interactive command in the script so that the script configuration can be
directly copied to the ATN 905 for issuing.
Y indicates the subsequent action of the command. N indicates that the command is canceled.
For example, the save command is an interactive command.
Step 5 Log in to the ATN 905 through the serial interface, and copy commands from the TXT script
file to the ATN 905 for configuration issuing.
----End