Beruflich Dokumente
Kultur Dokumente
Equipment
V200R003C10
Configuration Guide
Issue
01
Date
2014-01-31
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:
support@huawei.com
Issue 01 (2014-01-31)
If the plaintext mode is used, a password is stored in plaintext in the configuration file. This
results in high security risks. The plaintext mode applies only to scenarios with special
requirements, such as compatibility and interworking requirements.
Related Version
The following table lists the product version related to this document.
Product Name
Version
l ATN 910
V200R003C10
l ATN 910I
l ATN 910B
l ATN 950B
Huawei iManager U2000
V200R001C00
Intended Audience
This document is intended for:
l
Issue 01 (2014-01-31)
Commissioning Engineer
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
ii
Symbol Conventions
Symbol
Description
Indicates an imminently hazardous situation which, if not
avoided, will result in death or serious injury.
Indicates a potentially hazardous situation which, if not
avoided, could result in death or serious injury.
Indicates a potentially hazardous situation which, if not
avoided, may result in minor or moderate injury.
Indicates a potentially hazardous situation which, if not
avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to personal
injury.
Calls attention to important information, best practices and
tips.
NOTE is used to address information not related to personal
injury, equipment damage, and environment deterioration.
Command Conventions
Issue 01 (2014-01-31)
Convention
Description
Boldface
Italic
[]
{ x | y | ... }
[ x | y | ... ]
iii
Convention
Description
{ x | y | ... }*
[ x | y | ... ]*
GUI Conventions
Convention
Description
Boldface
>
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Issue 01 (2014-01-31)
iv
Contents
Contents
About This Document.....................................................................................................................ii
1 Network Deployment...................................................................................................................1
1.1 Overview........................................................................................................................................................................1
1.2 Creating a Topology.......................................................................................................................................................2
1.3 Deploying a Network Using the Plug-and-Play Management.....................................................................................11
1.3.1 IP LCT Overview......................................................................................................................................................11
1.3.2 IP LCT Operation Tasks............................................................................................................................................18
1.3.3 Common Maintenance Operations............................................................................................................................37
1.4 Deploying a Network Using the NE Explorer..............................................................................................................67
1.4.1 Panorama of NE management features......................................................................................................................67
1.4.2 General Instructions for the NE Explorer..................................................................................................................72
1.5 Verifying Basic Configuration.....................................................................................................................................76
Contents
vi
Contents
vii
Contents
Issue 01 (2014-01-31)
viii
1 Network Deployment
Network Deployment
1.1 Overview
This topic describes the deployment task, implementation modes, and applicable scenarios at
the network deployment stage. Network deployment must be complete before service
deployment.
Table 1-1 Deployment task
Issue 01 (2014-01-31)
Configu
ration
Item
Description
Configuri
ng the
managem
ent
channel
Configuri
ng the
interface
Configuri
ng IGP
and BGP
Configuri
ng MPLS
Configuri
ng the
tunnel
policy
Configu
ration
Item
Description
Configuri
ng the
routing
policy
1 Network Deployment
The U2000 provides two modes to implement the preceding deployment task.
Table 1-2 Implementation modes
Implemen
tation
Mode
Applicable Scenario
1.3
Deploying
a Network
Using the
Plug-andPlay
Manageme
nt
1.4
Deploying
a Network
Using the
NE
Explorer
For example, there may be more than one hundred CSGs at each site in the IP
RAN deployment scenario and the Plug-and-Play Management is
recommended to implement batch deployment. The U2000 Plug-and-Play
Management supports plug-and-play (devices must support this function too).
After devices are powered on and connected to fibers, the Plug-and-Play
Management automatically completes the network deployment based on
predefined configurations. The software commissioning engineers do not need
to go to the site and the deployment is of high efficiency.
Issue 01 (2014-01-31)
1 Network Deployment
Context
Network deployment can be implemented using the Plug-and-Play Management or NE Explorer.
If the Plug-and-Play Management is used, the following configurations are optional for NEs that
support automatic NE configuration. In other cases, the following configurations are mandatory.
The topology creation procedure varies according to the usage scenario and habit. If a large
number of NEs need to be created in a scenario such as deployment, the topology creation
procedure shown in Table 1-3 is recommended.
Table 1-3 Recommended topology creation procedure
Operation
Description
Create a subnet.
Create NEs in
batches.
Select an NE layout.
Create links.
Synchronize NE
data.
Prerequisites
l
The U2000 communicates with NEs successfully. That is, correct IP addresses are
configured for NEs and the U2000 and managed NEs can ping each other.
Before automatic ICMP NE searches, disable ICMP packet blocking in the firewall of the
U2000 server, because the ICMP packet blocking interrupts communication between the
U2000 and ICMP NEs.
Interworking between NEs to be managed and the U2000 has been commissioned. Telnet/
STelnet, SNMP, and NetConf parameters have been set.
Issue 01 (2014-01-31)
1 Network Deployment
Procedure
1.
Create a subnet.
a.
Right-click in the Main Topology and choose Create > Subnet from the shortcut
menu.
b.
In the dialog box that is displayed, select Property and set Name for the subnet to be
created.
NOTE
c.
2.
Click OK.
b.
Click ... on the right of the NE Type text box. In the dialog box that is displayed,
specify the desired NE type.
c.
Click Default SNMP Parameter. In the dialog box that is displayed, set SNMP
parameters and ensure that the parameters are consistent with those on the NE side.
a.
Click the tab associated with the desired SNMP version. Then click Add.
b.
NOTE
c.
Issue 01 (2014-01-31)
Click OK.
d.
d.
1 Network Deployment
Click OK.
Optional:
Set Ping Times, Timeout, and Layers as needed.
NOTE
If many NEs need to be searched on the network, setting Ping Times to 3 and Timeout to 5 is
recommended. Otherwise, some NEs may fail to be searched out.
e.
Optional:
(Optional) If an SNMP version is not required, select the desired version in
Version, right-click, and choose Delete from the shortcut menu.
NOTE
Deleting the SNMP version that is not required improves NE search efficiency.
f.
g.
Click Advanced and set Telnet/STelnet or NetConf parameters for NEs. Using
STelnet is recommended because of its higher security than Telnet.
a.
Click ... on the right of Telnet/STelnet Settings. In the dialog box that is
displayed, configure a Telnet/STelnet parameter template with the parameter
values consistent with those on NEs. Telnet/STelnet parameter settings in the
template are automatically applied to created NEs.
1)
Click Create.
2)
In the dialog box that is displayed, set Protocol Name and Template
Name.
3)
Click OK.
4)
Select the newly created template. In the Details area, set the relevant
parameters and click Apply.
NOTE
If the AAA user needs to be used, set Auth. Mode to User Auth. In addition, set
User Name and Password.
Issue 01 (2014-01-31)
b.
1 Network Deployment
Optional: Click the ... button on the right of NetConf Settings. In the dialog box
that is displayed, configure a NetConf parameter template with the parameter
values consistent with those on NEs. NetConf parameter settings in the template
are automatically applied to created NEs.
NOTE
NetConf parameters need to be set only when VRP V8-based routers are to be created.
c.
Issue 01 (2014-01-31)
1)
Click Create.
2)
3)
Click OK.
4)
Select the newly created template. In the Details area, set the relevant
parameters and click Apply.
Click OK.
h.
Check whether xFTP service status is normal: Choose Administration > Settings >
xFtpWatcher from the main menu to check whether configuration items in the list
are marked green. If the xFTP service status is abnormal or not configured, configure
the xFTP service by performing operations described in Configure a xFTP
watcher in the follow-up procedure section.
i.
Click ... on the right of the Physical Path text box. Then select the created IPRAN
subnet.
j.
In the IP Address Range area, click Add. In the dialog box that is displayed, set start
IP address, end IP address and a mask as need and click OK.
1 Network Deployment
k.
Click Next. The U2000 begins to search for NEs. The U2000 automatically creates
NEs after finding NEs that meet the search criteria.
l.
If you still need to create some NEs, repeat the preceding steps.
3.
Issue 01 (2014-01-31)
Select an NE layout.
a.
Double-click in the Main Topology to access the IP RAN. Right-click and choose
Layout from the shortcut menu.
b.
In the Layout dialog box, set the layout type of NEs. Click OK.
4.
1 Network Deployment
Create links.
a.
Choose File > Discovery > Link from the main menu.
b.
c.
Select one or more NEs or subnets from the list on the left and click
d.
In the LLDP Status Management dialog box, perform the following operations:
a.
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.
Issue 01 (2014-01-31)
b.
c.
The dialog box indicating It takes 30s before the enabled LLDP takes effect.
Are you sure to perform search? is displayed. Click OK. A progress bar is
displayed indicating the search progress.
e.
After the search is complete, a dialog box is displayed indicating that the operation is
successful. Click Close. Link search results are displayed.
f.
In the Link Search window, select all the links that have been searched out and click
Create. A progress bar is displayed indicating the link creation progress.
g.
h.
The dialog box indicating Are you sure to import links as fibers/cables is displayed.
Click OK. The Import Link dialog box is displayed.
i.
j.
5.
1 Network Deployment
Synchronize NE data.
Select all NEs in the Main Topology, right-click, and choose Synchronize NE Data from
the shortcut menu.In the dialog box that is displayed, NE data is then automatically
synchronized from the NEs to the U2000.
NOTE
After NEs are created on the U2000, the NE data is automatically synchronized to the U2000. If some
configurations are delivered to NEs using commands or other methods, perform the preceding
operations to synchronize NE data to the U2000.
Follow-up Procedure
Configure a xFTP watcher.
1.
Choose Administration > Settings > xFtpWatcher from the main menu.
2.
3.
Issue 01 (2014-01-31)
1 Network Deployment
NOTE
l The default values of Username, Password, and Root path of the U2000 xFTP service are
ftpuser, Changeme_123, d: (Windows-based server. If the server does not have drive D, set the
drive where the U2000 is installed as the root directory.) or /opt/backup/ftpboot (Linux-based
server or Solaris-based server for single-server system) or /opt/sybase/data (Solaris-based server
for backup system) respectively.
l If the user password and path of the xFTP service are changed, make sure that Password and
Root path in the xFtpWatcher dialog box are also changed.
l IP address cannot be set to 127.0.0.1.
l In the case of a single-server system, IP address is the IP address of the xFTP server that can
communicate with NEs, that is, the IP address of the U2000 server. In the case of a distributed
system, IP address is the IP address that is configured by means of the network address
translation (NAT).
l Port: Please use the default port ID, and ensure that the port is not occupied.
l The value of Root path must be correct. In addition, Root path must be an absolute path and
cannot end with / or \ or contain a space. On Windows OS, the default value of Root path is "d:"
disk, if the "d:" disk does not exist, please set the non-system disk as the root path of the FTP
server manually.
4.
Optional: In the xFtpWatcher dialog box, click FTP Server Setting to set FTP server
parameters such as the password and root path and start or shut down the FTP server.
NOTE
l Click
next to Password and change the password for the FTP server in the dialog box that
is displayed.
l By default, the FTP server of the U2000 is started. If you want to stop it, click Stop.
l By default, the root directory of the FTP server is d: on a PC running Windows. If d: does not
exist, set the root directory of the FTP server in a non-system disk.
Issue 01 (2014-01-31)
10
1 Network Deployment
System Overview
The IP LCT can be used to complete remote commissioning and basic configuration for a large
number of NEs, freeing software commissioning engineers from going to sites and improving
the deployment efficiency.
l
The IP LCT provides system-defined templates and baseline templates. You need to set
only a few parameters for generating basic NE configuration scripts.
The IP LCT supports remote commissioning using the Dynamic Host Configuration
Protocol (DHCP) or through the data communication network (DCN) to rapidly enable
management channels for new NEs. Software commissioning engineers can remotely add
NEs and assign management IP addresses to the NEs, without going to sites. The
configuration scripts are automatically applied to the NEs for site deployment. Currently,
CX600-X1, CX600-X2, CX600-X8-D0, ATN910, ATN950, ATN950B, ATN980, and
ATN990 support automatic NE configuration.
Hardware installation
engineer
Customize a template
Network planning
engineer
Plan data
U2000
plug-and-play
management
Perform remote
commissioning in
DCN mode
Software commissioning
engineer
Issue 01 (2014-01-31)
Perform remote
commissioning in
DHCP mode
Deploy IP services
11
1 Network Deployment
During deployment, the IP LCT is mainly used to perform DCN configurations for new NEs so
that the U2000 can manage the NEs. The IP LCT can be used to apply basic configurations to
NEs in different networking scenarios to complete batch NE deployment.
U2000 operators can use the IP LCT or UniSTAR for network planning. The plug-and-play
function can be implemented after a planning list is imported to the IP LCT.
System Functions
This topic describes the functions of the IP LCT.
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 IP LCT supports two remote commissioning methods:
l
Basic Concepts
This topic describes the basic concepts related to the IP LCT.
DHCP
DHCP is a technology used to dynamically manage and configure users in a centralized manner.
Issue 01 (2014-01-31)
12
1 Network Deployment
DHCP adopts the C/S communication mode, in which the DHCP client sends the configuration
request (requesting for the IP address, subnet mask, or default gateway) to the DHCP server,
and the DHCP server returns the corresponding configuration according to the predefined policy.
DHCP Server
The DHCP server is responsible for assigning IP addresses to DHCP clients. After a DHCP
client sends a configuration-requesting packet (requesting for the IP address, subnet mask, or
default gateway) to the DHCP server, the DHCP server returns a packet carrying the requested
configuration according to the predefined policy. The request and reply packets are both
encapsulated with UDP.
DHCP Relay
DHCP relay is introduced to transmit packets between the DHCP client and DHCP server that
are on different network segments. The DHCP relay agent can transparently transmit DHCP
broadcast packets between the DHCP client and DHCP server that are on different network
segments.
In the actual network environment, the DHCP relay function is generally implemented on a
specific interface of a router. You need to configure an IP relay address on this interface to
specify the DHCP server.
The IP relay address refers to the IP address of the DHCP server specified on the DHCP relay
agent. After the DHCP relay function is configured on an interface, the DHCP broadcast packets
received on this interface are sent to the specified DHCP server.
Upstream NE
NE role relationships should be described in the IP LCT link planning table according to the
order for making NEs online. If an NE at one end of a link is planned to go online earlier than
the other end, this NE can be regarded as the upstream NE.
The preceding figure shows that ASG3 and ASG4 are the NEs that have been made online on
the network. CSG1 and CSG2 are the plug-and-play NEs to go online. All the NEs are planned
Issue 01 (2014-01-31)
13
1 Network Deployment
to go online in the following time order: ASG3 -> CSG1 -> CSG2 -> ASG4. Port configuration
is also implemented in the same order. In this case, CSG1 is the upstream NE for CSG2. If the
NEs go online in the order of ASG4 -> CSG2 -> CSG1 -> ASG3, CSG2 is the upstream NE for
CSG1.
Note that specifying ASGs as upstream NEs is recommended in any cases. In the preceding
order examples, ASG4 is the upstream NE for CSG2 and ASG3 is the upstream NE for CSG1.
NEs deployed at both ends of a link between ASGs, ASGs and RSGs, and RSGs can act as
upstream NEs.
The upstream NE concept indicating the relationship between NEs on the same link is used for
filling the planning table and implementing remote commissioning only. It is not an absolute
concept. The relationship between a pair of NEs can be exchanged by changing the upstream
and downstream NEs' functions during remote commissioning. The upstream NE in this scenario
is irrelevant to the upstream NE for services.
Main Window
This topic describes main window components of the IP LCT as well as the functions of each
component.
Issue 01 (2014-01-31)
14
1 Network Deployment
1.
Main menu: The main menu options for the IP LCT are: Deployment Configuration,
Script Management, Template Management, System Management, and Help.
2.
Global information: The global information includes the networking scenarios and NE
information for sites.
3.
Process: The whole process ranges from network planning to service configuration
deployment.
Shortcut Icons
This topic describes the functions of shortcut icons used for the configuration of scripts or
templates.
Icon
Name
Function
Issue 01 (2014-01-31)
15
Icon
1 Network Deployment
Name
Function
Modify
Save
Find/Replace
Previous Error
Next Error
Deploy
Verify Script
Generate
Template
Query
Issue 01 (2014-01-31)
Copy
Paste
16
Icon
1 Network Deployment
Name
Function
Up
Down
Insert
Delete
Modify
Description
Modify
Command
Mark Parameter
Apply
Save
Save as
Restore Defaults
Restores the commands and parameter values in the systemdefined template to their default status.
NOTE
Only the system-defined template can be restored to its default status.
Expand
Collapse
Search
Name
Description
Abnormal
packets of the
DHCP server
Issue 01 (2014-01-31)
17
Icon
1 Network Deployment
Name
Description
Online
Already online
Basic
configuration
deployment
failure
Offline
To be online
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.
The U2000 IP Plug-and-Play Management window is displayed.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 On the Deployment Overview tab, click Set a Network Scenario.
Step 4 In the Set a Network Scenario dialog box, select a service scenario.
Step 5 Click OK.
Step 6 Optional: Choose System Management > Set Global Options from the main menu. In the
dialog box that is displayed, click the Options for Remote Commissioning tab and set remote
commissioning parameters.
Issue 01 (2014-01-31)
18
1 Network Deployment
Description
If the check box is selected, the IP LCT applies basic accessside configurations to aggregation site gateways (ASGs)
after cell site gateways (CSGs) go online. The check box
needs to be selected when ASGs do not have basic
configurations.
By default, this check box is selected.
DHCP Options
Deploy Script Automatically
Issue 01 (2014-01-31)
19
1 Network Deployment
Parameter
Description
Synchronize Uplink NE
sysname Automatically
Issue 01 (2014-01-31)
20
1 Network Deployment
Parameter
Description
Route Isolation
Step 7 Optional: On the Extend Script Settings tab, set related parameters and click OK.
Table 1-5 Parameter description
Name
Description
Context
A DCN type needs to be set only when NEs get online in DCN mode, but not DHCP 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.
The U2000 IP Plug-and-Play Management window is displayed.
Issue 01 (2014-01-31)
21
1 Network Deployment
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 In the Deployment Overview area, click Set DCN Type.
Step 4 On the DCN Mode Settings dialog box, select a DCN deployment mode.
l DCN Public Mode: The management packets between the U2000 and NEs are forwarded
using the service route.
l DCN Private Mode: The management packets between the U2000 and NEs are forwarded
using an independent private IGP route. The route is logically isolated from the service route.
Local VRF: All NEs are bound to the same VRF to establish private management channels
for packet transmission.
DCN VPN: Private management channels provided at delivery are used to transmit
packets. All NEs must support the DCN management function.
Step 5 Click OK.
----End
Customizing Templates
This topic describes how to use the IP LCT to customize a basic NE configuration template and
a BGP peer configuration template.
Context
l
Available network scenarios are hierarchy virtual private network (HVPN), L2+L3,
Gateway, multiprotocol label switching transport profile (MPLS-TP), and Native IP. One
of the network scenarios is deployed at an IP radio access network (IPRAN) site.
Available NE roles are aggregation site gateway (ASG), cell site gateway (CSG), radio
service gateway (RSG), ACCESS-P and AGG-P. If multiple NE roles need to be deployed
at a site, create multiple site-specific templates. The procedure for creating a basic
configuration template for ASGs is used as an example.
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.
The U2000 IP Plug-and-Play Management window is displayed.
Issue 01 (2014-01-31)
22
1 Network Deployment
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 On the Deployment Overview tab, click Customize a Template.
Step 4 Click Create Basic Configuration Template if it is the first time you use Customize a
Template.
If a site-specific template has been created, click Modify Basic Configuration Template.
A site-specific template can be modified as needed. For example, you can insert commands into
or delete commands from the template, or make extended marks on parameters.
For details about how to modify a template, see Modifying a Template.
Step 5 In the dialog box that is displayed, select a network scenario and an NE role, set an IP address
for the master server of the U2000, and click Next.
NOTE
You can select multiple NE roles in this step and set template parameters in follow-up steps.
l If multiple NE roles have been selected, click associated NE tabs and set template parameters.
l The basic configuration template includes basic NE configurations, such as basic NE information, and
authentication, authorization and accounting (AAA) user, global MPLS, Interior Gateway Protocol
(IGP), loopback interface, ring interface, and Simple Network Management Protocol (SNMP)
configurations.
Issue 01 (2014-01-31)
23
1 Network Deployment
1.
2.
Click to expand the template. Select desired check boxes based on service planning to
choose configurations to be applied to NEs.
To delete unwanted configurations, click .
3.
Set or modify values in the Default Value column. The parameters for which the Default
Value column are marked yellow are mandatory.
4.
Optional: Select the Show Parameter check box. In the template, select the desired
parameter and click
and click OK.
Issue 01 (2014-01-31)
24
1 Network Deployment
You can select an extended parameter predefined in the template or create an extended
parameter as needed.
a.
b.
In the dialog box that is displayed, enter the parameter ID, name, type, and description,
and click OK.
Context
l
The basic configuration template does not contain BGP peer configuration commands.
Therefore, BGP peer configuration templates must be created to deploy BGP peer
configurations.
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.
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 Custom Template Design in the Deployment Overview area.
Step 4 Click Create New Peer Template.
If a peer configuration template has been created, click Modify Peer Template.
Issue 01 (2014-01-31)
25
1 Network Deployment
A peer configuration template can be modified as needed. For example, you can insert commands
into or delete commands from the template, or make extended marks on parameters.
Step 5 In the dialog box that is displayed, select route reflector type and desired peer configuration
template type, enter the local AS number.
NOTE
l The available options of Route Reflector (RR) Type are Independent RR, RSG As RR, and Without
RR.
l If a global AS number is available, enter this AS number. Alternatively, enter AS numbers for each
BGP peer configuration template at the next step.
2.
In the dialog box that is displayed, configure automatic peer generation rules for the access
and aggregation sides.
3.
Click OK.
2.
Click to expand the template. Select desired check boxes based on service planning to
choose configurations to be applied to NEs.
To delete unwanted configurations, click .
3.
Set or modify values in the Default Value column. The parameters for which the Default
Value column are marked yellow are mandatory.
4.
Optional: Select the Show Parameter check box. In the template, select the desired
parameter and click
and click OK.
You can select an extended parameter predefined in the template or create an extended
parameter as needed.
Issue 01 (2014-01-31)
a.
b.
In the dialog box that is displayed, enter the parameter ID, name, type, and description,
and click OK.
26
1 Network Deployment
Planning Data
Plan link data, data communication network (DCN) data, and Border Gateway Protocol (BGP)
peer relationships.
Prerequisites
A project template has been configured.
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.
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 Optional: Plan IP address pools.
Step 4 Export the link planning template.
1.
2.
Click Export the link excel planning template and then design it.
3.
In the dialog box that is displayed, click Export Link Planning Table.
To apply configurations except the basic configuration template, click Choose Extend
Template. To configure a routing policy and a clock priority, select an extended template.
In the dialog box that is displayed, select the extended template to be applied and click
OK.
4.
5.
Click OK.
6.
Select a path for saving the link planning table, enter the planning table name, and click
Save.
Issue 01 (2014-01-31)
27
7.
1 Network Deployment
Open the link planning table and enter link planning information based on Note.
The parameters marked with asterisks (*) on each sheet are mandatory.
Table 1-6 Description of sheets in the link planning table
Sheet
Description
NetworkLayout
Aggregate_NE_
INFO
DCN_Layout
Trunk
Vlanif
Template_List
Other_Configur
ation
8.
Click Save.
2.
3.
In the dialog box that is displayed, click Browse and select the planning table that has been
filled in.
Issue 01 (2014-01-31)
28
4.
Click Open.
5.
Click Next.
1 Network Deployment
If the selected planning table is not exported from the IP LCT or UniSTAR, specify the
mappings for each field in the planning table.
6.
In the Configuration Rules for Link Planning area, select the Automatic
configuration check box and click Configure. In the dialog box that is displayed, set the
label switching router (LSR) ID network segment, IP network segment, and access interface
parameters.
NOTE
If the LSR ID and the IP address of the interconnected interface have been entered in the planning
table, clear the Automatic configuration check box.
7.
In the DCN Mode area, set DCN Mode and IGP Type.
8.
Optional: In the DCN Address Pool Planning area, select the Automatic
configuration check box and click Advanced. In the dialog box that is displayed, plan the
DCN address pool.
Issue 01 (2014-01-31)
29
1 Network Deployment
NOTE
l DCN Address Pool Planning needs to be set only when DCN Mode is set to Private (local
VRF in private DCN mode).
l If DCN Mode is set to Local VRF, Management Channel Name must be set.
9.
Click OK.
10. Click Next. In the dialog box that is displayed, click OK.
11. In the dialog box that is displayed, select a template for each NE and click Next.
12. On the Select Peer Template tab, modify the peer configuration templates mapping to the
NEs based on site conditions, and click Finish.
Step 6 Optional: Plan peer relationships.
If peer relationships are not generated using default rules, manually create peer relationships
based on planning information.
Step 7 View configuration scripts.
1.
2.
3.
Ensure that configurations in each script are the same as those planned.
The scripts are automatically generated based on project templates and planning tables and
cannot be manually modified. To adjust configurations in a script, modify the template or
planning table and re-import the planning table.
----End
Result
1.
2.
After you choose Configuration Data > Link Planning from the navigation tree, you can
find that the information has been imported from the planning table to the IP LCT.
Issue 01 (2014-01-31)
30
1 Network Deployment
Example
Figure 1-2 Network topology example
The examples of filling in link planning tables in four typical interface scenarios are as follows:
l
Issue 01 (2014-01-31)
Scenario in which interfaces are connected, with the link between CSG1 and CSG2 as an
example
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
31
1 Network Deployment
NOTE
Scenario in which subinterfaces are connected, with the link between ASG3 and ASG4 as
an example
Figure 1-5 Example of filling in the NetworkLayout sheet
NOTE
Scenario in which trunk interfaces are connected, with the link between RSG5 and RSG6
as an example
Figure 1-6 Example of filling in the NetworkLayout sheet
Issue 01 (2014-01-31)
32
1 Network Deployment
NOTE
Scenario in which virtual local area network (VLAN) interfaces are connected, with the
link between RSG5 and RSG6 as an example
Figure 1-8 Example of filling in the NetworkLayout sheet
NOTE
Prerequisites
l
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.
The U2000 IP Plug-and-Play Management window is displayed.
Issue 01 (2014-01-31)
33
1 Network Deployment
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 In the Deployment Overview area, click DCN Type.
Step 4 Click Monitor NE Online Process.
Step 5 In the dialog box that is displayed, click OK.
The DCN view is displayed on the U2000 client.
, or right-click the Gateway NE Tree node in the navigation tree, and choose Set Gate
Step 6 Click
NE from the shortcut menu.
Step 7 In the dialog box that is displayed, click Add Gateway NE to select the desired gateway NEs.
Select an NE IP address pool if the private DCN mode is used.
Step 8 Click Telnet Template to set Telnet or STelnet parameters. Click OK.
NOTE
You are advised to use the more secure STelnet mode if this mode is supported.
After the operation succeeds, the added gateway NEs are displayed under the Gateway NE
Tree node. The non-gateway NEs to go online are displayed in the DCN view in the right pane
of the window. In this case, these NEs are dimmed.
Step 9 Power on the non-gateway NEs to go online.
Step 10 Right-click in a blank area in the DCN view and choose Synchronize from the shortcut menu.
. The non-gateway NEs have been online after
The DCN view can be updated by clicking
their colors are changed to blue or Status on the NE tab is displayed as Online.
Step 11 Select the online non-gateway NE, right-click, and choose Apply Basic Configuration from
the shortcut menu.
Step 12 In the dialog box that is displayed, browse the scripts to be applied and click Apply.
View associated logs after the scripts are applied. If some commands are failed to be applied,
use Telnet or STelnet to log in to the NEs and re-apply these commands to the NEs.
NOTE
Views logs, you can search for logs by search forward, circle search, or case matching.
The colors of the non-gateway NEs in the DCN view are changed from blue to green after scripts
are successfully applied to them.
----End
Prerequisites
The upstream NEs have been managed by the U2000.
Issue 01 (2014-01-31)
34
1 Network Deployment
Context
Configurations must be applied to the upstream NEs during remote commissioning. Therefore,
the Telnet or STelnet parameters must be configured for these NEs in advance.
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.
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 In the Deployment Overview area, click DHCP Type.
Step 4 Click Configure Uplink NE TELNET Parameter.
Step 5 In the dialog box that is displayed, set Telnet parameters for every uplink NE, and click Test
Connectivity.
NOTE
If the test succeeds, the routes between the IP LCT and uplink NEs are reachable.
Step 6 Click OK.
----End
Remote Commissioning
After the DHCP service is enabled, the IP LCT automatically sets up a management channel for
newly added NEs and deploys configurations planned in the template to the associated NEs.
Context
After the DHCP service is enabled, the IP LCT starts exchanging DHCP messages with NEs.
After receiving DHCP request messages from the newly added NEs, the IP LCT assigns IP
addresses for the newly added NEs based on the planning information. A management channel
is then set up for the newly added NEs. The IP LCT automatically generates configuration scripts
based on the configured template and planned data and deploys the configuration scripts to the
newly added 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.
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 In the Deployment Overview area, click DHCP Remote Commissioning.
Issue 01 (2014-01-31)
35
1 Network Deployment
or click Refresh.
NOTE
Select each NE and view logs and scripts on the Running Log and Configuration Script tab pages. For
NEs with Eth-Trunk interfaces, the Trunk Interface Message Log tab page is also displayed, on which
you can view Trunk interface packet logs.
Task
Description
Check and
commission newly
added NEs
----End
Issue 01 (2014-01-31)
36
1 Network Deployment
Troubleshooting Procedure
Abnormality case 1: The newly created NE is online, but some planning information needs to
be modified.
1.
2.
Choose Configuration Data > Link Planning from the navigation tree.
3.
Select an error configuration record and click Modify to modify link planning
configurations.
4.
Click OK.
5.
6.
Select an error configuration record, right-click, and choose Reset NE Status from the
shortcut menu.
7.
Abnormality case 2: After relay has been enabled for an uplink NE during remote
commissioning, the newly added NE is in the To be online state.
NOTE
Relay has been enabled for an uplink NE but scripts fail to be deployed, which indicates that the
configurations of the newly added NE are not empty. Clear up the empty configurations.
1.
Select the problem NE, right-click, and choose Send DHCP Packets from the shortcut
menu.
2.
Follow-up Procedure
After remote commissioning is complete, you are recommended to delete confidential password
information such as the user password from the project template.
1.
2.
Select a template that contains password information and delete the default password
information.
3.
Click Save.
Maintaining NEs
This topic describes how to maintain NEs.
37
1 Network Deployment
Context
You are advised to plan the address pools if a great number of NEs need to be deployed. If you
do not plan the address pools, you can fill out the planning table with the IP address pool
information.
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.
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 In the Deployment Overview area, click Plan Data.
Step 4 Click Plan IP Address Pool.
Step 5 In the dialog box that is displayed, click Create.
Step 6 In the dialog box that is displayed, set parameters for the IP address pools. Click OK.
Three types of IP address pools can be created, including the LSR ID address pool, management
IP address pool, and link IP address pool.
Step 7 In the Address Pool Management dialog box, click Close.
----End
Context
The BGP peer relationships between NEs can be created independently or in batches. You can
select Full MESH or HUB/SPOKE for creating the BGP peer relationships in batches.
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.
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 In the Deployment Overview area, click Plan Data.
Step 4 Choose Plan Peer Relation.
Step 5 Optional: Configure RRs in the aggregation ring.
1.
Issue 01 (2014-01-31)
38
2.
3.
4.
Click Save.
1 Network Deployment
2.
3.
Click Next.
4.
Click Add to add the NEs for which the BGP peer relationships are created to the NE
list.
5.
Click Finish.
2.
In the dialog box that is displayed, set Source NE, Source Peer Template, Source
NE Group, Sink NE, Sink Peer Template, and Sink NE Group.
3.
Click OK.
----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.
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 the Script tab.
Step 4 In the NE List navigation tree or folder, right-click NE List and choose Synchronize NMS and
NESync NE From VSM from the shortcut menu.
Step 5 In the Synchronize NMS and NESync NE From VSM dialog box, set query conditions and
click Query.
Step 6 Select the NE to be imported and click OK.
The imported NE is displayed in the NE List navigation tree and NE List.
----End
Issue 01 (2014-01-31)
39
1 Network Deployment
Follow-up Procedure
To check whether the NE communicates with the IP LCT properly, perform the following
operations:
1.
2.
3.
4.
Prerequisites
Routers or switches are available in the U2000 Main Topology.
Context
An .xlsx file exported by the IP LCT 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.
Step 2 Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu.
The U2000 IP Plug-and-Play Management window is displayed.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Choose Deployment Configuration > Export NMS Data from the main menu.
Step 4 In the dialog box that is displayed, click Save File and OK.
Step 5 Select a save path and click Save.
----End
Prerequisites
The IP LCT and new NEs are directly connected through network cables.
Issue 01 (2014-01-31)
40
1 Network Deployment
Context
After the DHCP service is enabled, DHCP packets are exchanged between the IP LCT and NEs.
After receiving a DHCP request packet from a new NE, the IP LCT assigns an IP address to the
NE's interface directly connected to the IP LCT to enable the device management channel.
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.
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 Deployment Configuration > 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.
Prerequisites
NEs must be added to the IP LCT and the connectivity check must be performed successfully.
For details about how to add NEs, see Synchronizing NE Configurations to the U2000.
Context
l
Issue 01 (2014-01-31)
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 IP LCT and you do
not need to click Obtain Command Set.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
41
1 Network Deployment
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.
Step 2 Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu.
The U2000 IP Plug-and-Play Management window is displayed.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Click the Script tab.
Step 4 In the NE List navigation tree, select the NE whose command set needs to be obtained, rightclick, and then choose Obtain Command Set from the shortcut menu.
Alternatively, choose Script Management > NE > Obtain Command Set from the main
menu.
A progress bar is displayed indicating the progress of obtaining the command set.
Step 5 Optional: Click Run in Background.
Step 6 After obtaining the command set successfully, click Close.
The values of NE type and NE version for the NE are changed.
----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.
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 the Script tab.
Step 4 Optional: Create a folder.
1.
In the NE List navigation tree, right-click NE List and choose Create Folder from the
shortcut menu.
Alternatively, choose Script Management > Folder > Create Folder from the main
menu.
2.
Issue 01 (2014-01-31)
In the Create folder dialog box, enter the folder name, and then click OK.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
42
1 Network Deployment
Step 5 In the NE List navigation tree, right-click NE List and choose Create NE from the shortcut
menu.
You can also right-click in the NE List area and choose Create NE from the shortcut menu.
Alternatively, choose Script Management > Folder > Create NE from the main menu.
Step 6 In the Create NE dialog box, set NE parameters, and then click OK.
NOTE
l If the NE script needs to be exported or merged in the future, the NE name cannot contain special
characters \ / : * ? < > |.
l If the NE type and NE version currently in use are not available for the NE type and NE version
parameters, obtain the required command set. After the command set is obtained, the NE type and NE
version are automatically added to NE information. For details, see Obtaining Command Sets.
l To create multiple NEs in batches, click Create in the Create NE dialog box. Then, set the NE
parameters.
The created NE is displayed in the NE List navigation tree and on the NE List tab page.
----End
Follow-up Procedure
Check whether the NE and IP LCT are connected properly.
1.
Choose NE List from the navigation tree, and select a new NE in the NE List area on the
right.
2.
Optional: In the General area, you can modify the NE parameters and then click Apply
to complete the modification.
3.
4.
Issue 01 (2014-01-31)
43
1 Network Deployment
l If the message Test succeeded. is displayed, the IP LCT communicates properly with
the new NE.
l If the message Test failed. The target NE cannot be reached. is displayed, the NE IP
address is incorrect.
l If the message Test failed. Check the user name and password. is displayed, the user
name and password for authentication are incorrect.
Prerequisites
Global plug-and-play parameters must have been set. For details, see Setting a Network
Scenario.
DHCP replay must have been enabled for the uplink NE.
The uplink NE for the NE to be created must have been added to the IP Local Craft Terminal
(LCT).
Context
l
Create planning information about the NE to be created, and then start the Dynamic Host
Configuration Protocol (DHCP) service. The NE will be automatically assigned an IP
address and added to the IP LCT.
If you have completed deployment by using automatic NE configuration or will not use
automatic NE configuration, it is recommended that the DHCP server be stopped to save
server resources.
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.
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 the Automatic NE Configuration tab.
Step 4 Choose Data Planning > NE Information from the navigation tree.
Step 5 Click Create.
Step 6 In the Create NE dialog box, set the required parameters.
To add a record, click Add.
Issue 01 (2014-01-31)
44
1 Network Deployment
Step 7 Click OK. The new planning record is displayed in the NE list.
----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.
2.
3.
4.
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.
NOTE
If the Internet Explorer is used, the Save As dialog box is displayed. Select the path for saving the
exported file.
To export information about all NEs into a file, perform the following operations:
1.
2.
3.
4.
5.
6.
In the dialog box that is displayed, click the Save File option button and click OK.
NOTE
If the Internet Explorer is used, the Save As dialog box is displayed. Select the path for saving the
exported file.
----End
Issue 01 (2014-01-31)
45
1 Network Deployment
Prerequisites
NEs must exist in the NE list.
Procedure
Step 1 Click the Automatic NE Configuration tab.
Step 2 Choose Automatic NE Configuration > Remote Commissioning from the navigation tree.
Step 3 In the NE list, select an NE and click Ping.
Step 4 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.
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.
Maintaining Templates
This topic describes how to maintain templates.
Creating a Template
This topic describes how to create a template. A lot of NEs need to be configured during network
configuration. You can create a template for NEs of the same type and apply the template to
these NEs. This improves script generation efficiency.
Use any of the following methods to generate a template:
l
Generating a template using existing scripts: Use sample scripts in the Low Level Design
(LLD) document or existing scripts to generate a template.
Manually creating a template: If neither the LLD document nor existing scripts are
available, manually create a template. This method requires a good grasp of NE
configuration commands.
Issue 01 (2014-01-31)
46
1 Network Deployment
Prerequisites
A template is a predefined and exported .zip file. The template to be imported must exist.
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.
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 the Template tab.
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.
Step 6 Click Import. The imported template is displayed in the navigation tree.
----End
Prerequisites
Inheritable scripts must be obtained.
Context
Existing scripts can be classified into the following types:
l
Issue 01 (2014-01-31)
47
1 Network Deployment
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.
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 the Script tab.
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.
Enter only the keyword of the command to be queried. Do not enter any command parameter.
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 10 Click Generate Template.
Step 11 In the Generate Template dialog box, modify the parameters in commands as required.
Step 12 Click OK.
Issue 01 (2014-01-31)
48
1 Network Deployment
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.
Step 15 Click OK.
----End
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.
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 the Template tab.
Step 4 In the Template List navigation tree, right-click the Template List node and choose Create
Folder from the shortcut menu.
Alternatively, choose Template Management > Folder > Create Folder.
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 the Template List node 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, selectCommon Template.
Step 8 Select a path for saving the template, set NE type and NE version related to the template, and
enter basic template information. Then, click OK.
Step 9 In the Insert dialog box, select a value from the Select View drop-down list.
Step 10 In the Query Command field, enter the keyword of the command to be queried.
All commands containing this keyword are displayed in the query result area.
Issue 01 (2014-01-31)
49
Step 11 Click
OK.
1 Network Deployment
to add the required commands to the list of selected commands. Then, click
You can also copy a command script to the blank area directly.
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. Modify the command
and insert it into the template again.
The created template is displayed in the navigation tree, and details about the template are
displayed in the Template Configuration area.
Step 12 In the Template Configuration area, modify the created template.
l Double-click a command or parameter to modify the related description.
l Double-click the Parameter Value column to enter or change parameter values.
Issue 01 (2014-01-31)
50
1 Network Deployment
Modifying a Template
This topic describes how to modify commands and parameters in a template.
Context
Custom project templates can be modified, and predefined templates cannot 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.
Step 2 Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu.
The U2000 IP Plug-and-Play Management window is displayed.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Click the Manage Template tab.
NOTE
For details about how to modify a VTL template, refer to the procedure for creating a VTL template.
Step 4 Choose the template to be modified 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
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 a template are the same, the parameters are combined
into one in the exported template.
l If a command contains parameters of the enumerated type and the enumerated parameter values
are incomplete, modify the command to add values. For example, in the authentication-mode
aaa command, aaa indicates that the authentication mode is AAA. The other two authentication
modes are password and none. If you change aaa into ENUM{aaa,none,password} in the
command, any authentication mode can be selected as needed when you set parameters.
Issue 01 (2014-01-31)
Click
2.
Click
. In the dialog box that is displayed, select the desired view and command.
to add the command to the list of selected commands.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
51
1 Network Deployment
3.
You can also copy a command script to the blank area directly.
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.
Modify the command and insert it into the template again.
Enter default parameter values. Double-click the parameter value column to enter or change
parameter values.
The parameters marked yellow in the Default Value column are mandatory.
The rules of assigning values to some parameters 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). That is, the value of ISIS Name is sysname
+igpid. To meet site requirements, the rule can be changed to =sysname, and the value of
ISIS Name is sysname.
Issue 01 (2014-01-31)
Select the command that contains no parameter, and then click Modify Command.
In the dialog box that is displayed, add square brackets for the selected command.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
52
1 Network Deployment
NOTE
2.
Click OK. A check box is displayed to the right of the command. If the check box is
selected, it indicates that the command needs to be executed. If the check box is not
selected, it indicates that the command will not be executed.
Select the commands to be copied or the view in which commands need to be copied,
and then click to copy the commands.
NOTE
2.
Click
If a view or a parameter of the view is copied, the item will be pasted to the last
node related to the view.
If a command or a parameter of the command is copied, the item will be pasted
below the command.
To paste a copied item to a blank template, the root node must also be copied.
l
Click
2.
Click
If you delete a selected view, all the commands related to the view are deleted.
Applying a Template
This topic describes how to quickly generate a script by using a template.
Context
Both customized templates and universal templates can be used to generate scripts.
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.
Issue 01 (2014-01-31)
53
1 Network Deployment
l In a command, the parameters marked with an asterisk (*) or the value of Necessary is Yes must be
set. If such a parameter is not set, the generated scripts do not contain the command.
l If multiple templates are selected, set the parameters of each template respectively.
Step 7 In the confirmation dialog box, click Yes or No to determine whether to deploy the script
immediately.
Click Yes. The script deployment window is displayed.
----End
Follow-up Procedure
1.
2.
Choose the equipment where the template is applied from the NE List navigation tree. You
can find that the created script is displayed under the equipment. The name of the script is
the same as the name of the applied template.
Prerequisites
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.
Issue 01 (2014-01-31)
54
1 Network Deployment
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.
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 the Script tab.
Step 4 Choose NE List from the navigation tree. Right-click NE List and choose Import Planning
Table from the shortcut menu.
Alternatively, choose NE Plan Table > Import from the main 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).
Step 6 Click Import.
The associated scripts are automatically generated under each NE node according to the network
data planning table and template.
----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
2.
Issue 01 (2014-01-31)
55
1 Network Deployment
3.
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.
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.
NOTE
If the Internet Explorer is used, the Save As dialog box is displayed. Select the path for saving the
exported file.
2.
3.
4.
Choose Template List from the navigation tree. All templates are displayed in the
right pane.
5.
6.
In the dialog box that is displayed, click the Save File option button, and then click
OK.
----End
Maintaining Scripts
This topic describes how to maintain 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 create a script in any of the following methods. This topic focuses on the method of
creating a script manually.
l
Issue 01 (2014-01-31)
56
1 Network Deployment
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.
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.
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 the Script tab.
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 \ / : * ? < > |.
The created script is displayed under the NE node.
Step 6 In the Script Configuration area, click
All commands are displayed in colors and view commands are displayed in bold.
NOTE
Step 9 Optional: Incorrect commands are displayed in red. Modify the incorrect commands, and then
click to save the new configurations.
----End
Issue 01 (2014-01-31)
57
1 Network Deployment
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.
Step 2 Choose Configuration > Router/Switch/Security Configuration > Plug-and-Play
Management from the main menu.
The U2000 IP Plug-and-Play Management window is displayed.
Enter a user name and a password for logging in to the U2000 and click Login.
Step 3 Click the Script tab.
Step 4 Choose NE List from the navigation tree. Then, select the script to be modified under an NE
node.
Step 5 Click
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.
Issue 01 (2014-01-31)
58
1 Network Deployment
Procedure
l
2.
3.
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.
NOTE
If the Internet Explorer is used, the Save As dialog box is displayed. Select the path for saving the
exported file.
2.
3.
4.
Choose NE List from the navigation tree. Then, select any of the NEs whose scripts
need to be exported. All scripts of the NE are displayed in the right pane.
5.
Optional: Select All from the Attribute drop-down list. Then, click Query.
6.
7.
In the dialog box that is displayed, click the Save File option button, and then click
OK. Select the required path and click Save.
----End
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
Issue 01 (2014-01-31)
59
1 Network Deployment
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.
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.
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 the Script tab.
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.
Step 7 Click Import. Associated scripts are displayed on each NE node.
----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.
NE version and NE type must be set correctly for the specified NE.
The command set for the NE whose script needs to be verified must exist on the IP LCT
or have been imported into the IP LCT.
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.
Issue 01 (2014-01-31)
60
1 Network Deployment
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.
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 the Script tab. In the NE List navigation tree, select the script to be verified, right-click,
and then choose Verify Script from the shortcut menu.
Alternatively, click
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 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
Enter only the keyword of the command to be queried. Do not enter any command parameter.
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
Combining Scripts
This topic describes how to combine multiple NE scripts into one script.
Prerequisites
l
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
Issue 01 (2014-01-31)
61
1 Network Deployment
1.
2.
3.
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.
l
In the dialog box that is displayed, view the progress of combining scripts. When the
progress bar reaches 100%, click Close.
2.
3.
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.
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
Deploying Scripts
This topic describes how to deploy scripts to configure NEs in batches.
Prerequisites
The scripts that have been successfully verified must exist. For details about how to verify a
script, see Verifying a Script.
Issue 01 (2014-01-31)
62
1 Network Deployment
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.
Scripts for multiple NEs can be selected and deployed in batches.
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.
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 the Script tab.
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.
Step 5 In the Deploy Script dialog box, select a script in the Select Script area. The details about the
script are displayed in the Preview area.
If some command lines or parameters need to be modified, modify them and click Save before
deploying the script.
Step 6 Click Deploy.
The scripts for multiple NEs can be selected for deployment.
Step 7 In the confirmation dialog box, click OK.
Step 8 The progress of deploying the scripts is displayed on the Deployment 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.
Step 10 Click Close.
----End
63
1 Network Deployment
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.
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.
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 the Script tab.
Step 4 Select the NE List node, right-click, and then choose Scheduled Deployment from the shortcut
menu.
Alternatively, choose Script Management > Scheduled Deployment from the main menu.
Step 5 In the dialog box that is displayed, click Add.
Step 6 In the Create Deployment Task dialog box, click
required NE to the list of selected NEs.
or
to add the
The script will be automatically deployed in a scheduled manner. Do not enter any MML command.
Log Subfolder
Vendor
Remarks
Period
64
1 Network Deployment
Follow-up Procedure
After creating scheduled tasks, perform the following operations as required:
l
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.
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.
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
Changing the HSQLDB password during remote NE commissioning or script deployment is not
recommended. It is recommended that you restart the IP LCT process after changing the
HSQLDB password.
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.
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 System Management > Change the HSQLDB password from the main menu.
Step 4 In the dialog box that is displayed, enter the initial HSQLDB password, enter a new password
twice, and click OK.
Issue 01 (2014-01-31)
65
1 Network Deployment
The password must meet the following requirements to safeguard your user account.
1. Consists of 8 to 32 characters.
2. The password must be a combination of letters, digits, and special characters.
l Lower-case letters
l Upper-case letters
l Digits
l Special characters including ~ ! @ # $ % ^ & * ( ) - _ = + \ |[ { } ] ; : ' " , < . > and /
----End
Follow-up Procedure
Restarting the IP LCT process after changing the HSQLDB password is recommended.
1.
2.
3.
4.
After the process is stopped, right-click it and choose Start Process from the shortcut menu.
Context
You must enter the password twice when you log in to the online plug-and-play NE through
Telnet or STelnet.
The default password Changeme_123 is used if it is not changed.
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.
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 System Management > Change Initial NE Login Password from the main menu.
Step 4 In the dialog box that is displayed, enter the initial NE login password, enter a new password
twice, and click OK.
The initial NE login password is Changeme_123.
Issue 01 (2014-01-31)
66
1 Network Deployment
NOTE
The password must meet the following requirements to safeguard your user account.
1. Consists of 8 to 32 characters.
2. The password must be a combination of letters, digits, and special characters.
l Lower-case letters
l Upper-case letters
l Digits
l Special characters including ~ ! @ # $ % ^ & * ( ) - _ = + \ |[ { } ] ; : ' " , < . > and /
----End
Issue 01 (2014-01-31)
Scenario
Feature
Applicable
Device Type
Navigation Path
Fault
diagnosis
IP/MPLS
fault
location
Router
67
Scenario
1 Network Deployment
Feature
Applicable
Device Type
Navigation Path
Router
health
informatio
n
Router
IP NE test
Router
Service
gateway
Service
gateway
Frame-shaped
switch
Box-type
switch
Batch NE
configurati
on
IP QoS
Router
Service
gateway
IP NTP
Router
Service
gateway
IP ACL
Router
Service
gateway
Issue 01 (2014-01-31)
IP
multicast
profile
Router
Router/
Switch/
Security
configurati
on
Router
Reliability
configurati
on
E-Trunk
Router
E-APS
Router
Plug-andplay
deploymen
t
DCN
manageme
nt for
routers
Router
Service
gateway
Service
gateway
68
Scenario
1 Network Deployment
Feature
Applicable
Device Type
Navigation Path
Plug-andPlay
Manageme
nt
Router
Service
gateway
Frame-shaped
switch
Box-type
switch
Cluster
manageme
nt
Router
Frame-shaped
switch
On the cluster subnet page, select a switch, rightclick, and choose Administration from the
shortcut menu.
Box-type
switch
Applicable
Device
Type
Navigation Path
Device Management
Router
Service
Gateway
Frameshaped
switch
Box-type
switch
System
Managem
ent
LLDP
Manageme
nt
Router
Service
Gateway
Frameshaped
switch
Box-type
switch
NE
Channel
Manageme
nt
Issue 01 (2014-01-31)
Router
Service
Gateway
69
Scenario
Applicable
Device
Type
Navigation Path
Frameshaped
switch
Box-type
switch
Clock
Manageme
nt
Router
DCN
Communic
ation
Manageme
nt
Router
Interface Management
1 Network Deployment
Router
Service
Gateway
Frameshaped
switch
Box-type
switch
Ethernet Feature
Management
Router
Frameshaped
switch
Box-type
switch
IP
Applicatio
n Service
Issue 01 (2014-01-31)
ACL
Manageme
nt
Router
ANCP
Manageme
nt
Router
Service
Gateway
70
1 Network Deployment
Scenario
Applicable
Device
Type
Navigation Path
Route Management
Router
Service
Gateway
Frameshaped
switch
Multicast Management
Router
MPLS Management
Router
Service
Gateway
Frameshaped
switch
VPN Management
Router
Service
Gateway
Frameshaped
switch
QoS Management
Router
Service
Gateway
Frameshaped
switch
Reliability
OAM
Manageme
nt
Router
Service
Gateway
Frameshaped
switch
Box-type
switch
Issue 01 (2014-01-31)
71
Scenario
BFD
Manageme
nt
1 Network Deployment
Applicable
Device
Type
Navigation Path
Router
Service
Gateway
Frameshaped
switch
Box-type
switch
VRRP
Manageme
nt
MultiNode Hot
Backup
Manageme
nt
Security Management
Router
Service
Gateway
EPON
Managem
ent
Frameshaped
switch
Router
User
Access
BRAS
Manageme
nt
Router
EPON
Manageme
nt
Frameshaped
switch
Service
Gateway
72
1 Network Deployment
Issue 01 (2014-01-31)
73
1 Network Deployment
Issue 01 (2014-01-31)
74
1 Network Deployment
to NEs. Before you click Apply, all configurations are stored only on the U2000, and the
network and NEs are not affected.
Typical GUI 2: a list that does not support the creation operation
Configurations on such a GUI are usually implemented using shortcut menu options or
buttons.
If a shortcut menu option is used, configurations are deployed NEs after the operation
is confirmed.
If a button is used, a configuration window is usually displayed. The configuration mode
is similar to that on typical GUI 1.
Issue 01 (2014-01-31)
Typical GUI 3: a list that supports the creation operation and provides tab pages for further
configuration
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
75
1 Network Deployment
A logical resource, not a physical resource, is usually created on such a GUI. If the created
logical resource is associated with some features, it can be further configured using tab
pages.
NOTE
If you are not clear about the meaning, system impact, relationship with other parameters, or value setting
rule of a parameter when using the NE Explorer to configure an NE, press F1 to display the associated
help.
Prerequisites
1.
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.
Issue 01 (2014-01-31)
76
1 Network Deployment
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. 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.
Issue 01 (2014-01-31)
77
1 Network Deployment
----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.
Issue 01 (2014-01-31)
78
Prerequisites
The service information does not exist on the U2000 service management module but exists on
NEs.
The desired NE has been added and the relevant NE configurations have been synchronized to
the U2000.
Context
Note that automatically searching for IP services updates IP service data on the U2000. This
operation does not affect NE configurations or services running on NEs.
Issue 01 (2014-01-31)
79
Procedure
Step 1 Choose Service > Search for IP Service from the main menu.
Settings
All
Select NE
Customer
Policy
If this parameter is not set, the automatically discovered services are not
associated with any customer. If this parameter is set, all the discovered
services are associated with this customer.
NOTE
During customer creation, some personal data about users may be used. Therefore,
you are obligated to take considerable measures, in compliance with the laws of the
countries concerned and the user privacy policies of your company, to ensure that the
personal data about users is fully protected.
Naming Policy
Issue 01 (2014-01-31)
80
The following table describes the sub-tab pages on the Discovery Result tab page.
Sub-tab page
Description
Add Service
Modify
Service
Issue 01 (2014-01-31)
81
Sub-tab page
Description
Discrete
Service
----End
Follow-up Procedure
Select one or more records from the list of discovered services and click Jump Service to access
the service management window. In this window, you can perform operations such as viewing
or modifying the service data.
Prerequisites
l
Service data has been synchronized to the U2000 and service data on the U2000 is consistent
with that on NEs.
If service data on NEs has not been added to the U2000, perform the operations described in 2.2.1
Automatically Discovering Single IP Services. Otherwise, qualified composite services on the NE
side cannot be identified and added to the U2000.
Context
Automatic service discovery updates composite service data on the U2000, without affecting IP
service data on the U2000 and NEs or the running of IP services on the network.
The U2000 supports automatic discovery of the following composite services: H-VPLS, PWE3
+L3VPN, VPLS+L3VPN, inter-AS Option A (PWE3, VPLS, and L3VPN), PWE3+EPL, PWE3
+E-Line, SDH+PWE3, and Terminated EPL+L3VPN.
NOTE
Composite services can also be manually created. For details, see 2.7.2 Creating a Composite Service.
Issue 01 (2014-01-31)
82
Procedure
Step 1 Choose Service > Composite Service > Search for Composite Service from the main menu.
Step 2 Configure a service discovery policy.
On the Discovery Policy tab page, specify the NE range, service type, and customer policy for
the services to be discovered.
Major
Parameter
Settings
All
Select NE
Customer
Name
Specify the customer to which the services to be discovered belong. Only the
services belonging to this customer can be discovered.
VSI is Source
Only H-VPLS
services support this
function.
Issue 01 (2014-01-31)
83
Major
Parameter
Settings
PWE3 is
Source
L3VPN is
Source
PWE3 is
Source
Only PWE3+L3VPN
composite services
support this function.
Follow-up Procedure
Select one or more records from the list of discovered services and click Jump Service to access
the service management window. In this window, you can perform operations such as viewing
or modifying the service data.
Issue 01 (2014-01-31)
NE
Static CR
Tunnel
Static
Tunnel
RSVP TE
Tunnel
LDP
Tunnel
IP Tunnel
Router
ATN
84
"" indicates that the device supports the task. "-" indicates that the device does not support the task.
Task
Router
ATN
Navigation Path
Service
discovery
Discover
tunnels.
Discover
tunnel
protection
groups.
Create a
tunnel.
Create
tunnels in
batches.
Create
tunnels by
duplicati
ng
existing
tunnels.
Service
Protection
Create a
Tunnel
Protectio
n Group
Service
reliability
Configure
tunnel
OAM
Configure
MPLS-TP
OAM
Service
creation
Issue 01 (2014-01-31)
85
Service
Scenario
Service
monitoring
Task
Router
ATN
Navigation Path
Configur
e BFD for
TE.
Configur
e BFD for
LSP.
View
discrete
tunnels.
View a
tunnel
topology.
Monitor
Tunnel
alarms
Monitor
Tunnel
performan
ce instance
Issue 01 (2014-01-31)
86
Service
Scenario
Service
diagnosis
Issue 01 (2014-01-31)
Task
Router
ATN
Navigation Path
View
loopback
informatio
n about a
tunnel.
View LDP
sessions.
View
informatio
n about the
VPN on
which
tunnels are
located.
Detect
Tunnel
connectivi
ty
Diagnose
tunnels.
Perform
fast
diagnosis.
Using a
Test Suite
to
diagnose
Tunnel
87
Service
Scenario
Task
Router
ATN
Navigation Path
Service
adjustment
Adjust
tunnel
routes.
Reoptimiz
e tunnel
routes.
Modify a
tunnel.
Undeploy
a tunnel.
Delete
tunnels.
Delete
tunnels
from the
network
side.
Service
maintenanc
e
Issue 01 (2014-01-31)
88
Quick Navigation
The following table lists three tunnel creation methods.
Method
Usage Scenario
Creating a
single tunnel
Creating
tunnels in
batches
Creating
tunnels by
duplicating
existing tunnels
Prerequisites
l
Layer 2 links or IP links must be configured between routers. For details, see the topology
management section.
Procedure
Step 1 Choose Service > Tunnel > Create Tunnel from the main menu.
Issue 01 (2014-01-31)
89
Step 2 Configure basic tunnel information such as the protocol type, signaling type, and protection type.
Major Parameter
Settings
Protocol Type
Signaling Type
l RSVP TE tunnel: You need to specify only the ingress and egress
nodes for an RSVP TE tunnel. The MPLS protocol automatically
calculates a route for the tunnel. In addition, you can specify
constraint nodes to plan a specific route for the tunnel. You can
configure FRR protection and the QoS function for an RSVP TE
tunnel. Therefore, an RSVP tunnel is more flexible and safer than
an LDP tunnel.
l Static CR tunnel: A static CR tunnel is created with certain
constraints. The mechanism for creating and managing those
constraints is CR. Every site that a static CR tunnel passes through
must be manually specified too. Different from a static tunnel that
requires only routing information, creating a CR tunnel has other
configurations, such as the bandwidth, route, and QoS parameters.
l Static tunnel: Every site that a static tunnel passes through must be
manually specified.
NOTE
l Routers do not support LDP tunnels.
Service Direction
A bidirectional tunnel has one path in either direction, and the paths use
the same port and route. A unidirectional tunnel has only one path in a
single direction.
NOTE
l To create bidirectional tunnels, you need to create a single tunnel and select
Create Reverse Tunnel. In this way, two tunnels in opposite directions are
created.
l This parameter is available only when Signaling Type is set to Static CR.
Issue 01 (2014-01-31)
90
Major Parameter
Settings
Protection Type
Backup Type
Issue 01 (2014-01-31)
91
Major Parameter
Settings
Configure BFD
Template
Configure As
Bypass Tunnel
Step 3 Double-click NEs in the physical topology to select the desired source and sink NEs and set the
roles of the NEs in the NE Role column.
You can also use the following methods to select source and sink NEs:
l Method 1: Select the desired NE in the physical topology, right-click, and choose Add from
the shortcut menu.
l Method 2:
1.
Click Add and choose NE. In the Select NE dialog box, select the desired NEs.
2.
Click OK.
To specify the explicit or excluded NEs or interfaces for the tunnel to be created base on planned data,
configure route constraints for the tunnel. Otherwise. select only the source and sink NEs for the tunnel.
Issue 01 (2014-01-31)
92
NOTE
Route constraints for static CR or static tunnels are configured for route calculation.
l For RSVP TE tunnels, select the Synchronize Reverse route constraints check box in
Route Constraint. Then right-click the NE in the Main Topology and choose Set Forward
Primary Path Explicit Route > NE/Interface from the shortcut menu. Configured route
constraints are displayed on the Route Constraint tab page.
l For RSVP TE tunnels, click Add on the right of Route Constraint, and set Interface IP
Address and Restriction Type.
NOTE
l In consideration of tunnel scalability (adding nodes to tunnels), setting Restriction Type to Loosely
include is recommended.
l If creating an explicit path fails, modify the path information as prompted and create the path again.
l After source, sink, and route constraint NEs are configured for an RSVP TE tunnel, click Review
Route. NEs that the tunnel may pass through are highlighted in the physical topology.
Parameter
Description
Loosely include
Strictly include
Step 5 Optional: Click Details and configure tunnel details, and QoS. For details about the parameters
in Details, see the GUI reference.
Step 6 Click OK.
----End
Follow-up Procedure
In the dialog box displayed after the tunnel is successfully created, click Browse Trail. In the
Manage Tunnel dialog box, you can view the created tunnel. You can perform the following
operations:
NOTE
The following operations are applicable only to the tunnels for which Protocol Type is set to MPLS.
Issue 01 (2014-01-31)
93
Choose Service > Tunnel > Manage Tunnel from the main menu.
2.
In the Set Filter Criteria dialog box, set the search criteria and click Filter. The
qualified tunnels are displayed.
3.
Right-click a tunnel in the tunnel list and choose Test and Check from the shortcut
menu.
4.
5.
After the check is complete, click the ... button in Details. If the values of Sent
Packets and Received Packets are the same, the tunnel is functioning properly.
Choose Service > Tunnel > Manage Tunnel from the main menu.
2.
In the Set Filter Criteria dialog box, set the search criteria and click Filter. The
qualified tunnels are displayed.
3.
Select a tunnel, right-click the tunnel, and choose View LSP Topology from the
shortcut menu. The View LSP Topology progress bar is displayed.
4.
After the progress bar is closed, the main topology is automatically displayed, showing
the LSP topology. The solid line stands for an active LSP and the dashed line stands
for a backup LSP.
Prerequisites
l
Procedure
Step 1 Choose Service > Tunnel > Batch Create Tunnel from the main menu.
Step 2 Set basic parameters such as Network Type, Protocol Type, and Signaling Type.
Issue 01 (2014-01-31)
94
Major Parameter
Settings
Network Type
MPLS: If all NEs that a tunnel passes through support MPLS, set
Protocol Type to MPLS.
NOTE
Protocol Type can be set to MPLS only.
Signaling Type
l RSVP TE tunnel: You need to specify only the ingress and egress
nodes for an RSVP TE tunnel. The MPLS protocol automatically
calculates a route for the tunnel. In addition, you can specify
constraint nodes to plan a specific route for the tunnel. You can
configure FRR protection and the QoS function for an RSVP TE
tunnel. Therefore, an RSVP tunnel is more flexible and safer than
an LDP tunnel.
l LDP virtual tunnel: LDP virtual tunnels can be managed but not
created. The NE automatically reports LDP virtual tunnels to the
Manage Tunnel tab page after LDP is enabled in the NE Explorer.
LDP virtual tunnels can be viewed and managed on the Manage
Tunnel tab page.
Backup Type
Issue 01 (2014-01-31)
95
Major Parameter
Settings
Configure BFD
Template
Step 3 Configure the tunnel list and NE list. Double-click NEs in the physical topology to select the
desired source and sink NEs and set the roles of the NEs in the NE Role column.
You can also use the following methods to select source and sink NEs:
l Method 1: Select the desired NE in the physical topology, right-click, and choose Add from
the shortcut menu.
l Method 2:
1.
Click Add and choose NE. In the Select NE dialog box, select the desired NEs.
2.
Click OK.
NOTE
When you set Network Type to Ring, you can click Up or Down to adjust the position of the NE in the
equipment list.
To specify the explicit or excluded NEs or interfaces for the tunnels to be created in batches base on planned
data, configure route constraints for the tunnels. Otherwise. select only the source and sink NEs for the
tunnels.
l Click Add on the right of Route Constraint. Then, select the displayed entry and click
Configure to set Interface IP Address and Restriction Type.
Issue 01 (2014-01-31)
96
l If Network Type is set to Hub-Spoke, the following method can be used: Right-click the
NE in the Main Topology and choose Set Explicit Restriction > NE/Interface from the
shortcut menu. Configured route constraints are displayed on the Route Constraint tab page.
NOTE
l In consideration of tunnel scalability (adding nodes to tunnels), setting Restriction Type to Loosely
include is recommended.
l If creating an explicit path fails, modify the path information as prompted and create the path again.
Parameter
Description
Loosely include
Strictly include
Exclude
Follow-up Procedure
l
Prerequisites
l
Issue 01 (2014-01-31)
97
Context
l
If the tunnel to be duplicated does not belong to a protection group, the U2000 automatically
generates two unidirectional tunnels or a bidirectional tunnel, whose direction is reverse
and share the same source and sink nodes with the tunnel to be duplicated. Perform Step
3 to duplicate the tunnel.
If the Copy Protection Group check box is cleared, a tunnel is duplicated. In this case, you can set
Tunnel Number of Copying and other relevant parameters.
Procedure
Step 1 Choose Service > Tunnel > Manage Tunnel from the main menu.
Step 2 Right-click a tunnel to be duplicated and choose Copy from the shortcut menu. The Copy
Tunnel window is displayed.
Step 3 Optional: Duplicate a tunnel.
Major Parameter
Description
1.
Issue 01 (2014-01-31)
Set Tunnel Number of Copying and click Refresh. The U2000 automatically generates
the specified number of tunnels that shares the same source and sink nodes.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
98
2.
Select Create Reverse Tunnel as required. By default, Create Reverse Tunnel is selected.
3.
4.
Optional: In the case of a static CR tunnel, configure the route calculation for the U2000
as follows:
NOTE
To use the U2000 to automatically calculate the tunnel ID, label, and interfaces, perform this step
when creating a static CR tunnel. Otherwise, manually configure routes for the tunnel and ensure the
configuration correctness.
a.
Optional: Select Auto-Calculate route. Then the U2000 automatically calculates the
routes for a tunnel after you finish Steps 2 and 3.
b.
c.
Specify route constraint nodes. Specifically, you can click Route Restriction and
specify route constraint nodes in the dialog box that is displayed. Alternatively, you
can specify the explicit and excluded nodes using shortcut menu options in the physical
topology.
d.
A Layer 2 link must be configured before route calculation. For details about how to configure a
Layer 2 link, see the topology management section.
By default, the shortest route is selected from the routes that are calculated according to Restriction
Bandwidth and route constraints.
5.
Select a tunnel and click Details to set the detailed parameters of the tunnel.
1.
Copy Protection Group is selected by default. For details about how to duplicate a tunnel
when Copy Protection Group is not selected, see Step 3.
2.
By referring to Step 3.3 and Step 3.4, adjust the source and sink nodes and configure the
automatic route calculation.
NOTE
After you change the source or sink node of a forward tunnel, the source or sink node of the reverse
tunnel changes automatically.
Issue 01 (2014-01-31)
99
3.
Click Details. In the right-hand pane, click Hops Information and Protection Group
Information to configure details about the tunnels and parameters relevant to the protection
group.
Follow-up Procedure
l
Quick Navigation
Item
Basic principle
Protection
capability
Issue 01 (2014-01-31)
100
Item
Resource usage
An NE on an MPLS protection
ring is required to use only two
operation, administration and
maintenance (OAM) instances
and one automatic protection
switching (APS) instance. The
quantities of OAM instances and
APS instances are irrelevant to the
number of services.
Configuration
efficiency
Supported tunnels
Prerequisites
l
Before automatic discovery of protection groups, you must ensure that the tunnel protection
groups to be discovered exist on the live network and the parameter settings are correct.
Before creation of a protection group, you must ensure that a working tunnel and a
protection tunnel have been created.
Issue 01 (2014-01-31)
101
Quick Navigation
Operation
Usage Scenario
Automaticall
y Discovering
Tunnel
Protection
Groups
Creating a
Tunnel
Protection
Group
NOTE
Ensure that the desired tunnel protection group exists on the live network and the
protection group parameters are correctly set. If some of the protection group
parameters are set incorrectly, for example, duplicate IP addresses of interfaces that
the tunnel passes through exist, the tunnel protection group fails to be discovered.
NOTE
l The MPLS APS protection and FRR protection cannot both take effect.
l MPLS APS1+1 protection and MPLS ring protection are mutually exclusive and
cannot both take effect.
l The protection tunnel does not support PWE3, VPLS, and L3VPN services. It is
used to protect the working tunnel only.
Choose Service > Tunnel > Search for Protection Group from the main menu.
2.
In the dialog box, click Add, select the desired NE, and click OK.
3.
Click OK. A dialog box is displayed indicating the number of protection groups.
4.
Choose Service > Tunnel > Create Protection Group from the main menu.
2.
Configure basic information, such as Protection Type and Switching Mode, about the
tunnel protection group.
Issue 01 (2014-01-31)
102
NOTE
l For protection groups of the 1+1 protection type, the source end sends and receives services, and
the sink end selectively receives services. If the working tunnel fails, the protection tunnel is used
to receive services to implement service switchover.
l For protection groups of the 1:1 protection type, services are transmitted on the working tunnel.
If the working tunnel fails, the protection tunnel is used to transmit services. The source end
sends services and the sink end receives services.
l Single-ended switching refers to the scenario wherein only the local end is switched but the peer
end is not notified to switch when a fault occurs at one end. Single-ended switching does not
negotiate by using negotiation packets. Therefore, it is fast and reliable.
l Dual-ended switching refers to the scenario wherein the local end is switched and the peer end
is notified to switch when a fault occurs at one end. In the case of dual-ended switching, the
come-and-go path of a service is the same. This facilitates service management.
3.
Click Add. In the dialog box that is displayed, select the working tunnel and the protection
tunnel and click OK. Set Tunnel Type for the tunnels.
4.
(Optional) Select a required tunnel, click Configure OAM, and then configure the OAM
information of the tunnel.
5.
Follow-up Procedure
The tunnel protection group is successfully created. If the working tunnel fails, the protection
group automatically switches traffic to the protection tunnel. To perform a manual switchover,
choose Service > Tunnel > Manage Protection Group from the main menu. On the tab page
that is displayed, select a protection group, right-click, and choose Switch from the shortcut
menu.
"" indicates that the device supports the task. "-" indicates that the device does not support the task.
Issue 01 (2014-01-31)
Service
TaskScen
ario
Task
Router
ATN
Navigation Path
Service
discovery
Discover
L3VPN
services.
103
Service
TaskScen
ario
Task
Router
ATN
Navigation Path
Service
creation
Create a
dynamic
L3VPN
service.
Service
reliability
Configure
BFD for
VRF.
Configure
VRRP.
View VRF
resources.
View an
L3VPN
service
topology.
Create an
L3VPN
service
performan
ce
monitoring
instance.
View
L3VPN
service
performan
ce.
Check
L3VPN
connectivit
y.
Service
monitorin
g
Service
diagnosis
Issue 01 (2014-01-31)
104
Service
TaskScen
ario
Service
adjustment
Service
maintenan
ce
Issue 01 (2014-01-31)
Task
Router
ATN
Navigation Path
Perform
fast
diagnosis.
Add a
node.
Add an
interface.
Modify an
L3VPN
service.
Undeploy
an L3VPN
service.
Delete
L3VPN
services.
Delete
L3VPN
services
from the
network
side
105
Prerequisites
l
If a dynamic tunnel is used to carry the L3VPN service, the IS-IS protocol must be enabled.
The configurations of the relevant NEs have been synchronized to the U2000.
Procedure
Step 1 Choose Service > L3VPN Service > Create L3VPN Service from the main menu.
Step 2 Add an NE for the L3VPN service.
You can select the desired NE in either of the following methods:
l Method 1: Select the desired NE in the physical topology, right-click, and choose Add NPE
Node to Service from the shortcut menu. This method is recommended.
NOTE
When adding a node to a service, you need to choose an option from the shortcut menu based on the
networking situation and the node role.
l Method 2:
Click Add and select an NE role from the drop-down menu. The NE role varies according
to the networking condition.
In the dialog box that is displayed, select the desired NE and click OK.
l Method 3: In Physical Topology, double-click an NE to add it to the service. If Network
Type is set to Hub-Spoke, HVPN, or Customized, you can select a desired value from the
Node Role drop-down list to change the node role.
Step 3 Configure service details such as basic service attributes, service access interfaces, and routing
information. For details about the relevant parameters, see the GUI reference.
Issue 01 (2014-01-31)
106
Major
Parameter
Settings
General
DHCP Relay
If you configure and enable a DHCP relay based on VRFs, you can
recognize and process the DHCP request packets that are transmitted from
client-side ports.
VRF QoS
Set CIR and PIR as required. Deploy QoS configurations by using a QoS
profile.
NOTE
During service deployment, the selected Profile Name is delivered to NEs to
generate Local Profile Name.
You can do as follows to create a QoS profile:
l In the Select VPN QoS Profile dialog box, right-click, and choose Add Global
Profile from the shortcut menu.
l Choose Configuration > IP QoS Profile > HQoS Profile from the main menu.
On the HQoS Profile tab page, right-click, and choose Add Global Profile from
the shortcut menu.
SAI
You can bind multiple interfaces and set the parameters relevant to the
interfaces.
In addition, CE Information and QoS of the interfaces are optional.
You can also click the SAI Configuration tab to add, modify, or delete an
SAI or configure the SAI QoS.
If you configure and enable a DHCP relay based on ports, you can
accurately control the interaction between the equipment connected to each
port and the DHCP server.
Route
Configuration
Set the basic information, such as the BGP peer. In addition, the Route
Aggregation and Route Import parameters are optional.
You can select the routing protocol and set the relevant parameters
according to actual O&M requirements.
Click
on the right of a static route to copy and import static routes in
batches.
NOTE
l The private BGP protocol is configured in this step.
l The ID of the BGP instance here must be different from the ID of the MP BGP
instance.
l You must set Instance ID for RIP.
l You must set Instance ID and Area No for the OSPF.
Issue 01 (2014-01-31)
107
Follow-up Procedure
After the service is created, click Browse Service in the dialog box that is displayed, and view
the service in the Manage L3VPN Service window.
After the service is created and deployed, click Create Monitoring Instance in the dialog box
that id displayed to rapidly create a performance monitoring instance for the service.
Verify the configuration:
1.
Choose Service > L3VPN Service > Manage L3VPN Service from the main menu.
2.
Select a configured Layer 3 virtual private network (L3VPN) service and click the Service
Link tab in the lower part.
3.
Right-click the link and choose Fast Diagnosis from the shortcut menu.
4.
"" indicates that the device supports the task. "-" indicates that the device does not support the task.
Issue 01 (2014-01-31)
Service
Scenario
Task
Router
ATN
Navigation Path
Service
discovery
Discover
VPLS
services.
Service
creation
Create a
VPLS
service.
Service
reliability
Configure
BFD for
VSI.
108
Service
Scenario
Service
monitoring
Task
Router
ATN
Navigation Path
Configure
VRRP.
Configure
Ethernet
OAM.
View a
VPLS
service
topology.
Monitor
VPLS
service
alarms
Service
diagnosis
Issue 01 (2014-01-31)
Monitor
VPLS
service
performan
ce instance
Detect
VPLS
service
connectivi
ty
Service
Scenario
Service
maintenanc
e
Task
Router
ATN
Navigation Path
Diagnose
VPLS
services.
Perform
fast
diagnosis.
Using a
Test Suite
to
diagnose
PWE3
service
Modify a
VPLS
service.
Undeploy
VPLS
services.
Delete
VPLS
services.
NOTE
A VPLS service can be deleted only
after it is in the undeployed state.
Issue 01 (2014-01-31)
110
Service
Scenario
Task
Router
ATN
Navigation Path
Delete
VPLS
services
from the
network
side.
Prerequisites
l
The DCN function of a port carrying services must be disabled if the port needs to be
exclusively used.
Procedure
Step 1 Choose Service > VPLS Service > Create VPLS Service from the main menu.
Issue 01 (2014-01-31)
111
ATN NEs do not support the ability to use BGP to implement control plane functions.
Enter the name of the service to be created in the Service Name field.
2.
3.
Select a service template. The Service Template check box helps to quickly and
conveniently create a service. Here, only the general service creation procedure that
does not require any templates is described.
NOTE
A service template can be created based on service deployment requirements. For example,
you can select only the concerned parameters in the template and set default values for some
of the parameters. Then you can use the template to quickly create a service. The parameter
list contains only the selected parameters and their values.
4.
Issue 01 (2014-01-31)
112
Hub-Spoke: The UPE and NPE are connected using a multi-hop PW.
NOTE
Customized: When you use customized networking, the NMS does not create PWs
between NEs. You need to establish PWs between NEs.
5.
6.
7.
Enter the brief VSI description in the VSI Description text box.
8.
Select the name of the customer related to the service from the Customer Name dropdown list. If no related customer is available in the drop-down list, click the ... button
next to the Search text box. In the dialog box that is displayed, select the desired
customer. If the desired customer is still unavailable, click New to create a customer.
NOTE
During customer creation, some personal data about users may be used. Therefore, you are
obligated to take considerable measures, in compliance with the laws of the countries concerned
and the user privacy policies of your company, to ensure that the personal data about users is
fully protected.
9.
l
Issue 01 (2014-01-31)
1.
Enter the name of the service to be created in the Service Name field.
2.
3.
Enter the VSI name, VSI RD, and VSI RT, which are used to set common VSI
parameters of equipment. This helps to prevent setting parameters repeatedly.
4.
Enter the brief VSI description in the VSI Description text box.
5.
Select the name of the customer related to the service from the Customer Name dropdown list. If no related customer is available in the drop-down list, click the ... button
next to the Search text box. In the dialog box that is displayed, select the desired
customer. If the desired customer is still unavailable, click New to create a customer.
113
NOTE
During customer creation, some personal data about users may be used. Therefore, you are
obligated to take considerable measures, in compliance with the laws of the countries concerned
and the user privacy policies of your company, to ensure that the personal data about users is
fully protected.
6.
Step 3 Double-clicking NEs in the physical topology to select the desired source and sink NEs and set
the roles of the NEs in the NE Role column. You also can select the desired device from the
device list.
The selected device is displayed in the right-hand topology view.
l If a predefined typical scenario is selected, click Add to select the PE type that meets the
scenario requirements.
l If a user-defined scenario is selected, click Add to directly select the desired PE type. PEs
are not classified for this type of scenario.
NOTE
l Deploy: Select the Deploy check box. The created VPLS service is deployed to the NE.
l Enable: After the Deploy check box is selected, you can select the Enable check box. In this case, the
created service is deployed to the NE and at the same time enabled.
Select one or more sets of NE in the NE list and then click the VSI Configuration tab
to set the related VSI parameters.All equipment in the equipment list needs to be
configured.
Major
Parameter
Settings
VSI Type
Service VSI
Encapsulation
Type
Tunnel Policy
Indicates a tunnel policy for the tunnel that carries the VPLS service.
The tunnel policy determines the tunnel preferred for forwarding
traffic between PEs and whether to perform load balancing. You
can create the tunnel policy when selecting the VPLS service or use
the NE Explorer to create one.
Before the tunnel policy is created, the tunnel selection sequence
must be specified. If no tunnel policy is created, the LSP tunnel is
used by default and load balancing is not performed.
Issue 01 (2014-01-31)
114
Major
Parameter
Settings
Bound to
mVSI
NOTE
ATN NEs do
not support
this function.
2.
Select an NE in the NE list and then click the PW Configuration tab to set the related
PW parameters.
NOTE
Major
Parameter
Settings
PW Type
PW ID
Signaling
Type
Uplink PW
Split Horizon
Downlink PW
Split Horizon
In Tunnel
Binding Type
NOTE
ATN NEs do not support this function.
Out Tunnel
Binding Type
Issue 01 (2014-01-31)
115
Major
Parameter
Settings
In tunnel
You can specify a tunnel interface for carrying services, the priority
of the tunnel carrying services, and the number of tunnels that
participate in load balancing.
Out Tunnel
3.
Select an NE in the NE list and then click the SAI Configuration tab to set the related
SAI parameters.
M
aj
or
Pa
ra
m
ete
r
Settings
Click Create.
Click OK.
l Configure PTN, Hybrid MSTP, and OTN NEs under the following procedure.
Issue 01 (2014-01-31)
116
Step
Operation
In NE List, select an NE and click Details. On the VSI Configuration tab page,
set the relevant VSI parameters.
NOTE
l You need to set parameters for all the NEs in NE List.
l It is recommended that you set Split Horizon Group parameters to prevent multicast
storms. Specifically, add the PWs of NEs to split horizon groups.
Configure an SAI.
1. In NE List, select an NE and click the SAI Configuration tab.
2. Click Create. In the dialog box that is displayed, set the relevant information
for the SAI and click OK.
3. Click the SAI QoS tab, select an SAI, click Configure, and choose Global
QoS Policy Template or QoS Car Template. In the dialog box that is
displayed, set the relevant information for the SAI QoS.
Follow-up Procedure
verify the Configuration:
1.
Choose Service > VPLS Service > Manage VPLS Service from the main menu.
2.
Select a configured Layer 3 virtual private network (VPLS) service and click the VSI tab
in the lower part.
3.
Right-click the link and choose Fast Diagnosis from the shortcut menu.
4.
Issue 01 (2014-01-31)
117
"" indicates that the device supports the task. "-" indicates that the device does not support the task.
Issue 01 (2014-01-31)
Service
Scenari
o
Task
Router
ATN
Navigation Path
Service
discovery
Discover
PWE3
services
Service
creation
Create a
CES
service
Create
an E-line
service
Create
an ATM
service
Create
an ATM
IWF
service
Create a
heteroge
neous
interwor
king
ATM
service
Create a
manage
ment PW
118
Service
Scenari
o
Task
Router
ATN
Navigation Path
Service
reliability
Configur
e BFD
Configure
MPLSTP OAM
Service
monitori
ng
Issue 01 (2014-01-31)
Configure
Ethernet
OAM
Configur
e VRRP
View a
discrete
PWE3
service
119
Service
Scenari
o
Service
diagnosis
Task
Router
ATN
Navigation Path
View
topology
of a
PWE3
service
Monitor
PWE3
service
alarms
Monitor
PWE3
service
performa
nce
instance
Detect
PWE3
service
connectiv
ity
Perform
fast
diagnosis
Issue 01 (2014-01-31)
120
Service
Scenari
o
Task
Router
ATN
Navigation Path
Service
adjustme
nt
Adjust
PWE3
discrete
services
Modify a
PWE3
service
Service
maintena
nce
Undeploy
a PWE3
service
Delete
PWE3
services
Issue 01 (2014-01-31)
121
Service
Scenari
o
Task
Router
ATN
Navigation Path
Delete
PWE3
services
from the
network
side
Prerequisites
l
DCN is disabled on the port that carries the CES service. For details, see the relevant
descriptions of the NE Explorer.
CES service (E1 level): A CES service interface is configured, the interface mode is set to
Layer 1, and the frame format and frame mode of the interface are configured.
30: In the E1 frame format, timeslots 1 to 15 and 17 to 31 are used to transmit service data.
31: In the E1 frame format, timeslots 1 to 31 are used to transmit service data.
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
Issue 01 (2014-01-31)
122
Settings
Service template
Service Type
CES.
Protection Type
l If Protection Type is set to ProtectionFree, you must configure source node and
sink node.
Step 3 Select the source and sink NEs. The number of timeslots of the selected interfaces on the source
and sink NEs must be the same. Otherwise, the deployment may fail.
The methods of configuring the source and sink NEs are the same. Therefore, the following
describes only the method of configuring the source NE.
1.
Right-click an NE in the Physical Topology and choose Select Source from the shortcut
menu.
NOTE
According to the protection types, NEs can be configured as different roles through the shortcut
menu. Set As Switching Node indicates that the NE is configured as a hop of the multi-hop PW. For
services without protection, Set As Switching Node can be set to Working only. For services with
protection, Set As Switching Node can be set to Working or Protection.
2.
Configure interface.
l In the dialog box that is displayed, set the filter criteria and click Search. Then, the
interfaces that meet the filter criteria are displayed.
Issue 01 (2014-01-31)
123
If no interface meets the filter criteria, you can create an interface or modify the attributes
of an existing interface.
3.
Select an interface.
4.
On the SAI Configuration tab page, set the SAI attributes of the service interface.
5.
Click OK. Configure the sink NE or protection node by using the same method according
to the protection type. The configured roles are displayed in the node list.
6.
Click Configure Source And Sink, select Unterminated on the left, specify the LSR ID
of an unterminated node, and click Add Node. In the lower portion of the window, the
unterminated source and sink NEs are displayed. Click OK.
NOTE
On a network, if NEs only at one end of a service can be managed by the U2000, select
Unterminated and set the LSR ID for the peer end of the service.
If Protection Type is set to PW backup protection or PW APS protection, no unterminated node
can be set.
7.
Use the same method to configure the sink, protection, and transit NEs based on the
protection type.
Step 4 Optional: Click Configure PW Switch Node to add working and protection transit NEs
between the source and sink NEs.
NOTE
The protection type defines that protection switching nodes cannot be configured on services that are not
protected.
Step 5 Optional: Double-click parameters in Node and SAI Parameter to modify the settings of the
source and sink NEs displayed in Node List. To view the topology of a configured service, click
the Service Topology tab in the upper right area.
Step 6 Optional: Set basic PW attributes in the PW pane.
Issue 01 (2014-01-31)
Major Parameter
Settings
PW ID
Signaling Type
124
Major Parameter
Settings
Step 7 Click Detail and check the configuration information in the pane that is displayed in the lower
right area.
Step 8 Select the Deploy check box and click OK.
NOTE
l If the Deploy check box is not selected, the configuration data is stored only on the U2000. If the
Deploy check box is selected, the configuration data is stored on the U2000 and applied to NEs. By
default, the Deploy check box is selected.
l If the Deploy and Enable check boxes are selected, services on NEs are available only when the services
are enabled.
----End
Follow-up Procedure
verify the Configuration:
1.
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2.
Select a configured PWE3 service, right-click the link and choose Test And Check from
the shortcut menu.
3.
Prerequisites
l
Issue 01 (2014-01-31)
125
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
Settings
Service template
You can select a template from the Service template text box and
use the template to configure a service.
Service Type
ETH.
Protection Type
If VLAN ID conflict occurs during source or sink NE configuration, information (for example, service
name) about services to which conflict VLAN ID belong is displayed during the conflict check process.
The methods of configuring the source and sink NEs are the same. Therefore, the following
describes only the method of configuring the source NE.
1.
Issue 01 (2014-01-31)
Right-click an NE in the Physical Topology and choose Select Source from the shortcut
menu.
126
NOTE
According to the protection types, NEs can be configured as different roles through the shortcut
menu. Set As Switching Node indicates that the NE is configured as a hop of the multi-hop PW. For
services without protection, Set As Switching Node can be set to Working only. For services with
protection, Set As Switching Node can be set to Working or Protection.
2.
Configure interface.
l In the dialog box that is displayed, set the filter criteria and click Search. Then, the
interfaces that meet the filter criteria are displayed.
If no interface meets the filter criteria, you can create an interface or modify the attributes
of an existing interface.
3.
Select an interface.
4.
On the SAI Configuration tab page, set the SAI attributes of the service interface.
5.
Click OK. Configure the sink NE or protection node by using the same method according
to the protection type. The configured roles are displayed in the node list.
6.
Click Configure Source And Sink, select Unterminated on the left, specify the LSR ID
of an unterminated node, and click Add Node. In the lower portion of the window, the
unterminated source and sink NEs are displayed. Click OK.
NOTE
On a network, if NEs only at one end of a service can be managed by the U2000, select
Unterminated and set the LSR ID for the peer end of the service.
If Protection Type is set to PW backup protection or PW APS protection, no unterminated node
can be set.
7.
Use the same method to configure the sink, protection, and transit NEs based on the
protection type.
Step 4 Optional: Double-click parameters in Node and SAI Parameter to modify the settings of the
source and sink NEs displayed in Node List. To view the topology of a configured service, click
the Service Topology tab in the upper right area.
Step 5 Optional: Set basic PW attributes in the PW pane.
Issue 01 (2014-01-31)
Major Parameter
Settings
PW ID
Signaling Type
127
Major Parameter
Settings
Step 6 Click Detail and check the configuration information in the pane that is displayed in the lower
right area.
Step 7 Optional: Click the Service Parameter tab to set service parameters. If you set BPDU Private
Service to Yes, MTU and VLAN ID cannot be set for the Router Series NE. If multiple source
and sink nodes are configured for the service, configuring different service tags on the source
and sink nodes is supported.
Step 8 Optional: Click the PW QoS tab to configure the global template for a PW. Alternatively, click
Global Template and select a global QoS template from the drop-down list. Then set parameters.
Step 9 Optional: Click the Advanced PW Attribute tab to set advanced PW parameters. TPID and
Request VLAN are available only when PW Type is set to Ethernet Tagged Mode.
Click Configure MPLS-TP OAM. In the dialog box, set MPLS-TP OAM parameters.
NOTE
l If the Deploy check box is not selected, the configuration data is stored only on the U2000. If the
Deploy check box is selected, the configuration data is stored on the U2000 and applied to NEs. By
default, the Deploy check box is selected.
l If the Deploy and Enable check boxes are selected, services on NEs are available only when the services
are enabled.
----End
Follow-up Procedure
verify the Configuration:
1.
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2.
Select a configured PWE3 service, right-click the link and choose Test And Check from
the shortcut menu.
Issue 01 (2014-01-31)
128
3.
Prerequisites
l
When creating a dynamic PW to carry the service, you must set IGP-ISIS and MPLS-LDP
protocol parameters.
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
Issue 01 (2014-01-31)
Major Parameter
Settings
Service template
Service Type
ATM.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
129
Major Parameter
Settings
Service Name
NOTE
Right-click an NE in the Physical Topology and choose Select Source from the shortcut
menu.
NOTE
According to the protection types, NEs can be configured as different roles through the shortcut
menu. Set As Switching Node indicates that the NE is configured as a hop of the multi-hop PW. For
services without protection, Set As Switching Node can be set to Working only. For services with
protection, Set As Switching Node can be set to Working or Protection.
2.
Configure interface.
l In the dialog box that is displayed, set the filter criteria and click Search. Then, the
interfaces that meet the filter criteria are displayed.
If no interface meets the filter criteria, you can create an interface or modify the attributes
of an existing interface.
3.
Select an interface.
4.
On the SAI Configuration tab page, set the SAI attributes of the service interface.
5.
Click OK. Configure the sink NE or protection node by using the same method according
to the protection type. The configured roles are displayed in the node list.
6.
Click Configure Source And Sink, select Unterminated on the left, specify the LSR ID
of an unterminated node, and click Add Node. In the lower portion of the window, the
unterminated source and sink NEs are displayed. Click OK.
NOTE
On a network, if NEs only at one end of a service can be managed by the U2000, select
Unterminated and set the LSR ID for the peer end of the service.
If Protection Type is set to PW backup protection or PW APS protection, no unterminated node
can be set.
7.
Use the same method to configure the sink, protection, and transit NEs based on the
protection type.
Step 4 Optional: Double-click parameters in Node and SAI Parameter to modify the settings of the
source and sink NEs displayed in Node List. To view the topology of a configured service, click
the Service Topology tab in the upper right area.
Step 5 Optional: Set basic PW attributes in the PW pane.
Issue 01 (2014-01-31)
130
Major Parameter
Settings
PW ID
Signaling Type
Step 6 Click ATM Link. In the dialog box, add multiple ATM connections and set the relevant
parameters.
NOTE
An ATM connection requires a source SAI and a sink SAI. The SAIs can be selected from the related dropdown list.
If a configured VPI/VCI has been used for another service, the related message is displayed.
Step 7 Click Detail and check the configuration information in the pane that is displayed in the lower
right area.
Step 8 Optional: Click the PW QoS tab to configure a global PW template. Alternatively, select one
of the configured templates in the Global Template text box and set the relevant parameters.
Step 9 Optional: Click the Advanced PW Attribute tab to set PW parameters.
Click Configure MPLS-TP OAM. In the dialog box that is displayed, set MPLS-TP OAM
parameters.
The PW control word can be changed online. In other words, Control Word can be changed
online after an ATM service is created.
Step 10 Select the Deploy check box and click OK.
Issue 01 (2014-01-31)
131
NOTE
l If the Deploy check box is not selected, the configuration data is stored only on the U2000. If the
Deploy check box is selected, the configuration data is stored on the U2000 and applied to NEs. By
default, the Deploy check box is selected.
l If the Deploy and Enable check boxes are selected, services on NEs are available only when the services
are enabled.
----End
Follow-up Procedure
verify the Configuration:
1.
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2.
Select a configured PWE3 service, right-click the link and choose Test And Check from
the shortcut menu.
3.
Prerequisites
Data synchronization must be performed for the related NE.
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
Issue 01 (2014-01-31)
132
Right-click an NE in the Physical Topology and choose Select Source from the shortcut
menu.
NOTE
According to the protection types, NEs can be configured as different roles through the shortcut
menu. Set As Switching Node indicates that the NE is configured as a hop of the multi-hop PW. For
services without protection, Set As Switching Node can be set to Working only. For services with
protection, Set As Switching Node can be set to Working or Protection.
2.
Configure interface.
l In the dialog box that is displayed, set the filter criteria and click Search. Then, the
interfaces that meet the filter criteria are displayed.
If no interface meets the filter criteria, you can create an interface or modify the attributes
of an existing interface.
3.
Select an interface.
4.
On the SAI Configuration tab page, set the SAI attributes of the service interface.
5.
Click OK. Configure the sink NE or protection node by using the same method according
to the protection type. The configured roles are displayed in the node list.
6.
Click Configure Source And Sink, select Unterminated on the left, specify the LSR ID
of an unterminated node, and click Add Node. In the lower portion of the window, the
unterminated source and sink NEs are displayed. Click OK.
Issue 01 (2014-01-31)
133
NOTE
On a network, if NEs only at one end of a service can be managed by the U2000, select
Unterminated and set the LSR ID for the peer end of the service.
If Protection Type is set to PW backup protection or PW APS protection, no unterminated node
can be set.
7.
Use the same method to configure the sink, protection, and transit NEs based on the
protection type.
Settings
PW ID
Signaling Type
2.
3.
Click OK.
2.
Click the SAI QoS tab and set the QoS policy of the SAI. You can select an existing policy
from QoS Policy.
3.
Click PW QoS and set the QoS template of the PW. You can select an existing template
from QoS Template and set the related parameters.
4.
Click Advanced PW Attribute and set the parameters related to the advanced attributes
of the PW.
Issue 01 (2014-01-31)
134
NOTE
l Click the ... button on the Management PW tab page. In the dialog box that is displayed, select
a management PW to bind it to service PWs.
l Click Configure MPLS-TP OAM. In the dialog box that is displayed, set MPLS-TP OAM
parameters.
Follow-up Procedure
verify the Configuration:
1.
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2.
Select a configured PWE3 service, right-click the link and choose Test And Check from
the shortcut menu.
3.
Prerequisites
Data synchronization must be performed for the related NE.
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
Issue 01 (2014-01-31)
135
Right-click an NE in the Physical Topology and choose Select Source from the shortcut
menu.
NOTE
According to the protection types, NEs can be configured as different roles through the shortcut
menu. Set As Switching Node indicates that the NE is configured as a hop of the multi-hop PW. For
services without protection, Set As Switching Node can be set to Working only. For services with
protection, Set As Switching Node can be set to Working or Protection.
2.
Configure interface.
In the dialog box that is displayed, set the filter criteria and click Search. Then, the
interfaces that meet the filter criteria are displayed.
If no interface meets the filter criteria, you can create an interface or modify the attributes
of an existing interface.
3.
Select an interface.
4.
On the SAI Configuration tab page, set the SAI attributes of the service interface.
5.
Click OK. Configure the sink NE or protection node by using the same method according
to the protection type. The configured roles are displayed in the node list.
6.
Click Configure Source And Sink, select Unterminated on the left, specify the LSR ID
of an unterminated node, and click Add Node. In the lower portion of the window, the
unterminated source and sink NEs are displayed. Click OK.
Issue 01 (2014-01-31)
136
NOTE
On a network, if NEs only at one end of a service can be managed by the U2000, select
Unterminated and set the LSR ID for the peer end of the service.
Currently, PTN NEs in the same management domain can be used to configure unterminated trails.
If Protection Type is set to PW backup protection or PW APS protection, no unterminated node
can be set.
7.
Use the same method to configure the sink, protection, and transit NEs based on the
protection type.
Settings
PW ID
Signaling Type
2.
Click the SAI QoS tab and set the QoS policy of the SAI. You can select an existing policy
from QoS Policy.
3.
Click PW QoS and set the QoS template of the PW. You can select an existing template
from QoS Template and set the related parameters.
4.
Click Advanced PW Attribute and set the parameters related to the advanced attributes
of the PW.
NOTE
l Click the ... button on the Management PW tab page. In the dialog box that is displayed, select
a management PW to bind it to service PWs.
l Click Configure MPLS-TP OAM. In the dialog box that is displayed, set MPLS-TP OAM
parameters.
Issue 01 (2014-01-31)
137
Follow-up Procedure
verify the Configuration:
1.
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2.
Select a configured PWE3 service, right-click the link and choose Test And Check from
the shortcut menu.
3.
Creating a Management PW
This topic describes how to create a management PW. The management PW is used to transmit
packets and helps to perform active/standby switchover as well as link detection through BFD.
Prerequisites
Data synchronization must be performed for the related NE.
Context
Management PWs are created on loopback interfaces. When a large number of service PWs
exist, you can bind the service PWs to a management PW and configure BFD so that the status
of the management PW can be associated with the status of the service PWs. This helps to reduce
the quantities of BFD sessions and BFD packets and save system resources and public link
bandwidths.
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
Issue 01 (2014-01-31)
138
Right-click an NE in the Physical Topology and choose Select Source from the shortcut
menu.
2.
Configure interface.
In the dialog box that is displayed, set the filter criteria and click Search. Then, the
interfaces that meet the filter criteria are displayed.
If no interface meets the filter criteria, you can create an interface or modify the attributes
of an existing interface.
3.
Select an interface.
4.
On the SAI Configuration tab page, set the SAI attributes of the service interface.
5.
Click OK. Configure the sink NE or protection node by using the same method according
to the protection type. The configured roles are displayed in the node list.
6.
Click Configure Source And Sink, select Unterminated on the left, specify the LSR ID
of an unterminated node, and click Add Node. In the lower portion of the window, the
unterminated source and sink NEs are displayed. Click OK.
Issue 01 (2014-01-31)
139
NOTE
On a network, if NEs only at one end of a service can be managed by the U2000, select
Unterminated and set the LSR ID for the peer end of the service.
Currently, PTN NEs in the same management domain can be used to configure unterminated trails.
If Protection Type is set to PW backup protection or PW APS protection, no unterminated node
can be set.
7.
Use the same method to configure the sink, protection, and transit NEs based on the
protection type.
Settings
PW ID
Signaling Type
Dynamic
Step 5 If you select Deploy, services are delivered to the NEs. If you do not select Deploy, services are
saved only on the NMS without being delivered to the NEs.
NOTE
Step 6 Optional: Click Detail, and set the parameters related to the advanced attributes of the PW.
NOTE
On the Advanced PW Attribute tab page, click Configure MPLS-TP OAM. In the dialog box that is
displayed, set MPLS-TP OAM parameters.
Follow-up Procedure
verify the Configuration:
1.
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2.
Select a configured PWE3 service, right-click the link and choose Test And Check from
the shortcut menu.
3.
Issue 01 (2014-01-31)
140
"" indicates that the device supports the task. "-" indicates that the device does not support the task.
Task
Router
ATN
Navigation Path
Service
discovery
Discover
composite
services.
Service
creation
Create an HVPLS
composite
service.
Create a
customized
composite
service.
Configure
BFD for PW.
Configure
Ethernet OAM.
Service
reliability
Issue 01 (2014-01-31)
141
Issue 01 (2014-01-31)
Service
Scenario
Task
Router
ATN
Navigation Path
Service
monitoring
View a
composite
service
topology.
View
composite
service alarms.
View
composite
service
performance.
Service
diagnosis
Perform fast
diagnosis.
Service
maintenance
Modify a
composite
service.
142
Service
Scenario
Task
Router
ATN
Navigation Path
Undeploy a
composite
service.
Deletes
composite
services.
Delete services
in cascading
mode.
In H-VPLS mode, service components and connection points can be automatically created
by configuring basic attributes and adding service nodes. This mode simplifies the creation
process, but is applicable only to H-VPLS composite services.
Composite services are classified based on the service types of the service components that form
these services, as shown in Table 2-7. Different composite services are applicable to different
NEs and impose different requirements on service components and connection points,.
Issue 01 (2014-01-31)
143
Requirements for
Service
Components
Requirem
ents for
Connecti
on Points
Reference
Chapter
H-VPLS
(PWE3
+VPLS)
Routers, ATN
Connection
points must
be PWs
that are
associated
with each
other and
belong to
the PWE3
and VPLS
service
component
s.
Creating
an HVPLS
Composite
Service
Prerequisites
ATN NEs do not support this function.
Context
Typical H-VPLS scenarios are as follows: One VPLS node accesses two PWE3 nodes. Two
VPLS nodes access one PWE3 node.
Procedure
Step 1 Choose Service > Composite Service > Create Composite Service from the main menu.
Issue 01 (2014-01-31)
144
Step 2 In the General area, set basic attributes for the composite service.
1.
2.
Configure BFD.
BFD for PW rapidly checks PW connectivity to detect PW faults in real time. Real-time
PW fault detection helps trigger PW switching timely to achieve carrier-class network
reliability. The procedure for enabling BFD for PW is as follows:
l Select a value from the drop-down list to enable BFD for PW.
l Click to the right of Configure BFD to set BFD parameters.
By default, only the working PW is selected on the U2000. BFD attributes are not
associated based on PWE3 service protection types.
NOTE
Generally, BFD is configured only for the working PW to ensure network reliability under most
conditions and save bandwidth and device resources.
Issue 01 (2014-01-31)
145
Major Parameter
Settings
Click Add VPLS Node. In the dialog box that is displayed, select
VPLS service nodes. The selection methods are as follows:
l Selecting existing service nodes: Use existing NEs as service
nodes to form an H-VPLS composite service. Existing services
can be managed by the composite service in a unified manner. To
adjust or expand existing services, use this method.
On the Add Service tab page, click Filter Criteria and set filter
criteria. Then select one or more VPLS services.
l Adding new service nodes: If the existing services do not meet
requirements, use this method to configure new services on the
device and add them to an H-VPLS composite service.
Click the Add Device tab. Select one or more NEs from the
physical topology tree and click
. Click OK.
Click Add PWE3 Node. In the dialog box that is displayed, select a
PWE3 service node. The selection methods are the same for Add
VPLS Node-SAI.
Repeat this operation to add more PWE3 service nodes.
Click Add Switch Node. In the dialog box, select the required NE
and click
to configure this NE as a PW switching point.
A PW switching point is one hop on a multi-hop PW.
Issue 01 (2014-01-31)
146
NOTE
Step 4 After selecting service nodes, you can change their attributes as needed.
Major Parameter
Settings
VSI
In the service topology or service node list, select the VPLS service
node. On the VSI Configuration tab page, modify VSI attributes as
required.
NOTE
Generally, the default value provided by U2000 is used. If the default value
is different from the value planned for the live network, change the value as
required.
Issue 01 (2014-01-31)
147
Major Parameter
Settings
PW
Issue 01 (2014-01-31)
SAI
On the SAI Configuration tab page, you can modify, add, and delete
an SAI, and set QoS attributes of the SAI.
PWE3 Service
Parameter
On the PWE3 Service Parameter tab page, you can set Service
Tag for a PWE3 service.
PWE3 Protection
Parameter
148
Major Parameter
Settings
E-Trunk
In the service topology, select two service nodes of the same type
(such as two VPLS nodes), right-click, and choose E-Trunk from
the shortcut menu. In the dialog box, set E-Trunk parameters and
click OK.
E-Trunk is an extension to the Link Aggregation Control Protocol
(LACP). It controls and implements inter-device link aggregation.
E-Trunk protects PEs and links between a CE and the PEs when the
CE is dual-homed to a VPLS or PWE3 network.
NOTE
The local IP address of one node must be the peer IP address of the other
node, and Layer 3 routes must be reachable. Loopback interface addresses
are recommended.
Network Protocol
LDP Peer
149
Follow-up Procedure
The status and configurations of composite services are displayed on the Composite Service
Management tab page. You can use different navigation paths on this tab page to perform endto-end service management.
Procedure
Step 1 Choose Service > Composite Service > Create Composite Service from the main menu.
Step 2 In the General area, set basic attributes for the composite service.
NOTE
Step 3 In the Service Component area, click Select to select the related type of service. In the window
that is displayed, select one or more services and click OK. The selected services are displayed
in both the service component list and the service topology.
NOTE
l The changes of Deployment Status, Enabling Status, and Running Status of services added to the
Service Component list area are not monitored on the Create Composite Service tab page. Therefore,
the service status displayed in the list area is not refreshed in real-time according to actual service
changes.
l If no qualified services are displayed, click Create to create a service.
Issue 01 (2014-01-31)
150
Step 4 In the Connection Point area, configure the connection point for the composite service. The
configured connection point is displayed in both the connection point list area and the service
topology.
l
For a PWE3+L3VPN composite service, click Interface. The U2000 automatically checks
whether the L3VPN service has an SAI for interconnecting to the PWE3 service.
1.
If such an SAI exists, a connection point between the PWE3 and L3VPN services is
generated and displayed in the Connection Point list.
2.
If such an SAI does not exist, the U2000 keeps checking whether the NE has an L3VE
interface for interconnecting to the PWE3 service.
a.
If such a L3VE interface exists, an interconnection SAI for the L3VPN service
is automatically generated based on the PWE3 SAI information.
b.
If such a L3VE interface does not exist, connection point information is generated
but the L3VPN service has no connection point generated. You need to configure
a connection point for the L3VPN service.
2.
In the dialog box that is displayed for creating the connection point, set Name or select
the Auto-Name check box.
3.
4.
NOTE
l Interface connection point: Select service access interfaces associated with the involved
service components. For example, if the VPLS and L3VPN service components are used
to create a composite service, select an L2VE interface associated with the VPLS service
component and an L3VE interface associated with the L3VPN service component.
l PW connection point: Select the PWs connected to the PWE3 and VPLS service
components.
5.
Click OK.
151
Follow-up Procedure
The status and configurations of composite services are displayed on the Composite Service
Management tab page. You can use different navigation paths on this tab page to perform endto-end service management.
Prerequisites
The composite service to be modified exists.
Procedure
Step 1 Choose Service > Composite Service > Manage Composite Service from the main menu.
Step 2 In the Set Filter Criteria dialog box, set the filter criteria and click Filter. All the qualified
composite services are displayed in the query result area.
Step 3 Select the desired composite service and click Modify.
Step 4 Modify the following parameters of the composite service as required:
The windows for modifying and creating a composite service are similar. The only difference
is that only part of the parameters can be set in the window for modifying the composite service.
l
Except for Creation Type, other parameters can be modified for a customized composite
service. For details, see the part Creating a Customized Composite Service.
Result
Information about the modified composite service is displayed in the list area in the Composite
Service Management window. You can click the Topology, Service Component, and
Connection Point tabs to view details about the composite service.
152
network and the network bandwidth dramatically increases. If the network is interrupted for a
short period, a lot of services running on the network are affected, resulting in serious service
loss. Demands for network infrastructure reliability are increasing.
Prerequisites
Deployment Status of the service for which BFD needs to be configured is Undeployed.
Context
Table 2-8 Common BFD Scenarios
Service
Usage
Scenario
Description
Tunnel
BFD for TE
Issue 01 (2014-01-31)
153
Service
Usage
Scenario
Description
L3VPN
PWE3 + HVPLS
BFD for PW
VPLS
NOTE
BFD for VRRP: In VRRP-based reliability networking, BFD provides rapid detection mechanism
for links between the primary and secondary routers. If a link fault occurs, the VRRP module is
notified of the fault to achieve rapid switchover between the primary and secondary routers.
Procedure
Step 1 Choose Service > L3VPN Service > Manage L3VPN Service from the main menu.
Here, L3VPN services are used as an example. The procedures for configuring BFD for tunnels,
VPLS services, and PWE3 services are similar to that for L3VPN services.
Step 2 Filter services.
In the Set Filter Criteria dialog box, set filter criteria and click Filter. All the qualified services
are displayed in the query result area.
Issue 01 (2014-01-31)
154
Select the desired L3VPN service from the service list, right-click, and choose Configure
BFD from the shortcut menu.
2.
In the Batch Configure BFD Session dialog box, select a detection path.
The detection path is between NEs for the L3VPN service. Generally, a detection path can
be formed between any two of such NEs. You can click + to create multiple detection paths
for the L3VPN service based on site requirements.
2.
The parameter settings for the detection object vary according to the type of the bound
service. The parameters except those described in the following table can use the default
values provided by the U2000 or be manually adjusted according to the planning.
Issue 01 (2014-01-31)
155
NOTE
The monitoring objects supported by the tunnel, VPLS, PWE3, or L3VPN service are different and
the configuration requirements vary too. The following table describes the monitoring objects and
configuration requirements.
Service
Type of Bound
Service
Setting Requirements
L3VPN
Issue 01 (2014-01-31)
PWE3
VPLS
Tunnel
BFD for TE
156
Service
Type of Bound
Service
Setting Requirements
Bind LSP Type: In general, BFD is configured to
detect the primary LSP. If a fault occurs, traffic
is switched to the backup LSP. If services have
high requirements for fault detection, BFD can
be configured for both the primary and bypass
LSPs to speed up fault detection and switchover.
IP link
IP Bind Type:
l Specified IP Address: If you attempt to check
the connectivity of a single-hop or multi-hop
link, select this value.
l Default Multicast Address: If you attempt to
check the connectivity of a link between
Layer 2 or 3 interfaces without IP addresses,
select this value. After this value is selected,
the BFD session sends BFD control packets
to this multicast address to check the physical
status of the link.
Remote IP Address: IP address of the sink NE to
be detected
Out Interface: If this parameter is not set, a multihop route can be detected. If this parameter is set,
a single-hop route, that is, a route that uses this
interface as the outbound interface and the peer
IP address as the next hop is detected.
Local IP Address:
l If this parameter is not set, the U2000 searches
the local routing table for an outbound
interface matching the peer IP address and
uses the IP address of this interface as the
source IP address from which BFD packets
are sent.
l When both BFD and URPF are enabled, you
need to set the source IP address of BFD
packets because URPF checks the source IP
address of every received packet. The system
checks only whether the source IP address is
valid (for example, the source IP address
cannot be a multicast or broadcast address),
without carrying out any correctness check.
Therefore, you need to ensure the correctness
of the source IP address.
157
Click OK to deploy the configurations to the NE. The newly configured BFD session is displayed
in the list of the BFD Session Configuration Management window.
----End
Follow-up Procedure
l
After the preceding configurations are implemented, you can learn about BFD running
conditions by checking the BFD session status. Before checking the BFD session status,
perform synchronization in the NE Explorer.
Double-click the NE in the Main Topology to open the NE Explorer. In the NE Explorer,
choose BFD Management > Service Detection Configuration > VRF Detection
Configuration from the navigation tree. On the VRF Detection Configuration tab page,
right-click in the blank area and choose Synchronize from the shortcut menu.
As described earlier, the measure taken based on the BFD session status is determined by
the upper-layer application, which is usually VRRP. For details, see 2.8.2 Configuring
VRRP.
Prerequisites
Deployment Status of the service for which VRRP needs to be configured is Undeployed.
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
Here, PWE3 services are used as an example. The procedures for configuring VRRP for tunnels,
VPLS services, and L3VPN services are similar to that for PWE3 services.
Step 2 Filter services.
In the Set Filter Criteria dialog box, set filter criteria and click Filter. All the qualified services
are displayed in the query result area.
Step 3 Open the VRRP creation window.
1.
Select the desired PWE3 service from the service list, right-click, and choose Configure
VRRP from the shortcut menu.
2.
In the Set Filter Criteria dialog box, set filter criteria and click OK. All the VRRPs meeting
the filter criteria are displayed in the query result area.
3.
158
1.
Type of Bound
Service
Setting Requirements
VR IP
Issue 01 (2014-01-31)
159
Type of Bound
Service
Setting Requirements
Flowdown
2.
Issue 01 (2014-01-31)
a.
Using the drop-down list, select the remote working device, local working
interface, remote protection device, and local protection interface for the link BFD
to be tracked.
b.
Click Advanced. Set Remote BFD ID and Detection Object. Use the default
values for other parameters, or set these parameters as required. Click OK.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
160
On the Metro Ethernet, VRRP runs between NPEs. BFD between NPEs is called peer BFD, and BFD
between the NPE and UPE is called link BFD. Peer BFD and link BFD are used to detect the link and
NE faults between NPEs and between the NPE and UPE respectively. Peer BFD and link BFD directly
affect the status of a backup group without modifying the priority of the backup group. As a result, in
non-preemption mode, the priority of a backup router may be higher than that of a master router after
peer BFD and link BFD are configured.
Result
View the following information in the VRRP-Based Detection Configuration Management
window:
l
Working NE, Working State, Protection NE, and Protection State in the list to learn
about all VRRP backup groups configured for the PWE3 service and the master and backup
states of NEs in a VRRP backup group.
Service Component Associated with VR tab page on which service components for
tracking VRs are displayed. These service components determine their own active/standby
states by tracking the VR status.
VR Tracking Object tab page on which all objects (usually interfaces, BFD sessions, and
OAM) monitored by the VRRP backup group and priority adjustment values (for example,
10) are displayed. The VRRP backup group adjusts priorities based on the status of
monitored objects and determines whether to perform a master/backup switchover based
on the adjusted priorities.
ARP two-node hot backup can be configured for L3VPN services and back up ARP information
between two NEs running VRRP to ensure ARP information synchronization between the master
and backup NEs. After a VRRP active/standby switchover is complete, Downstream traffic is
transmitted properly without learning of MAC addresses in ARP entries after a master/backup
VRRP switchover is performed. This effectively resolves the packet loss problem that occurs
because ARP information is not obtained in time after a switchover is complete.
1.
Choose Service > L3VPN Service > Manage L3VPN Service from the main menu.
2.
3.
Click Create.
4.
Select the desired NE and L3VE subinterface from the physical topology tree, and click
the ... button on the right of Remote Backup Policy.
A remote backup policy can be created only using the NE Explorer.
5.
Click OK.
6.
Issue 01 (2014-01-31)
161
Procedure
Step 1 Choose Administration > NE Communicate Parameter > NE Telnet/STelnet Template
Management from the main menu.
Step 2 In the dialog box that is displayed, click Create.
NOTE
In the scenario where only part of the parameters of a default template or created template need to be modified,
select the desired template, and then modify associated parameters in the Details area.
Step 3 In the dialog box that is displayed, select the desired protocol type, set Template Name, and
then click OK. The following figure shows how to create a STelnet template.
Add a template record in the Telnet/STelnet Template Information area.
Issue 01 (2014-01-31)
162
Step 4 Select the created template. Then, set associated parameters in the Details area.
Prerequisites
l
The related parameters, such as the user name and password, must be set on equipment.
NOTE
The device login header cannot contain special characters "#", "]", ">". Otherwise, the U2000 fails
to verify Telnet/STelnet parameters.
Context
Security authentication modes are not adopted for the Telnet mode. Packets are transmitted
through TCP in plain text, which brings security risks. The U2000 adopts STelnet to reduce
security risks, using SSH features to ensure security and effective authentication.
Procedure
Step 1 In the Main Topology, select the equipment whose Telnet or STelnet parameters need to be set.
Step 2 Choose Administration > NE Communicate Parameter > Set NE Telnet/STelnet
Parameter from the main menu.
Issue 01 (2014-01-31)
163
NOTE
You can also right-click the selected equipment and then choose Set NE Telnet/STelnet Parameter from
the shortcut menu.
Context
In the U2000, you can configure one Telnet parameter template and one STelnet parameter
template. If required, you can manually modify the configured templates to set the Telnet/
STelnet parameters for equipment.
NOTE
The device login header cannot contain special characters "#", "]", ">". Otherwise, the U2000 fails to verify
Telnet/STelnet parameters.
Procedure
Step 1 In the Main Topology, select the equipment whose Telnet/STelnet parameters need to be
modified.
Step 2 Choose Administration > NE Communicate Parameter > Set NE Telnet/STelnet
Parameter from the main menu.
NOTE
l You can also right-click the selected equipment and then choose Set NE Telnet/STelnet Parameter
from the shortcut menu.
l In the NE Explorer, you can click
on the toolbar.
Step 3 In the Details group box of the Device Telnet/STelnet Parameter Management dialog box,
modify Telnet/STelnet parameters manually.
l
Issue 01 (2014-01-31)
164
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, choose Device Management > System Information.
Step 3 On the System Information tab page, set or view system information.
NOTE
Step 4 Optional: Click Synchronize to refresh system information displayed on the U2000.
----End
Issue 01 (2014-01-31)
165
Context
Ensure that the NE IP address set on the NMS is the same as the actual IP address of the NE.
Otherwise, the communication fails.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Device Management > NE IP Address Management from the service tree.
Step 3 On the NE IP Address Management tab page, the original IP address of the NE is displayed.
You can change the NE IP address stored on the NMS through New IP Address to restore the
communication.
Step 4 Click Apply. In the Confirm dialog box, click OK.
The IP address that you set is displayed in Current IP Address.
----End
Issue 01 (2014-01-31)
166
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
The NE Panel tab page is displayed by default.
Step 2 Optional: If you are currently visiting other tab pages on the NE Explorer tab page, you can
choose Device Management > NE Panel from the service tree to access the NE Panel tab page.
NOTE
l The colors of the board indicate the running status of the board.
l The alarm indicator color is determined by the highest alarm severity of the board and its ports.
l The color of a port indicates the status of the port. For the colors of specific ports, see the legend on
the right of the panel.
l When the administrative status of a port is Down, the following situations occur:
l If no alarm is generated on the port, the color of the port is gray.
l If there is an alarm on the port, the color of the port depends on the severity level of the alarm.
l When the administrative status of a port is Up, the following situations occur:
l If no alarm is generated on the port, the color of the port is green.
l If there is an alarm on the port, the color of the port depends on the severity level of the alarm.
l When the administrative status of a port is Up, the running status of the port is Down, and no alarm
is generated on the port, the port color is the same as the color for critical alarms.
l When a board is inserted into a slot, the slot blinks in blue. After being successfully registered, the
board is displayed on the NE panel.
l If no flexible plug-in board is inserted, the board is displayed as blank. On the NE panel, no subboard
can be selected.
Step 3 When you select components on the panel, you can view the detailed information about the
components through the related tabs on the lower part of the panel.
l When you select the board, the Board Information tab page displays the detailed
information about the board. If the board has subboards or ports, you can view the detailed
information about the subboards or ports through the Subboard Information tab or the Port
Information tab. If you double-click the board, the Port Information tab page is displayed.
Issue 01 (2014-01-31)
167
l When you select a port, the port record is displayed on the Port Information tab page. Rightclick the port record. The shortcut menu options are the same as those displayed when you
right-click a port on the panel.
Step 4 Optional: On the Board Information, Subboard Information, and Port Information tab
page, you can right-click in the table heading in the query result area to select which parameters
are displayed.
l
Method one: Right-click in the table heading and select parameters to be displayed. You
can select only one parameter each time; therefore, this method is applicable for minor
adjustment.
Method two: Right-click in the table heading and choose Customize from the shortcut
menu. In the dialog box that is displayed, select parameters to be displayed. This method
is applicable for selecting parameters to be displayed at a time.
----End
Resetting a Board
This topic describes how to reset a board. When the software of a board needs to be updated or
a fault occurs on a board, you can reset the board.
Prerequisites
Telnet or STelnet parameters must be set on the equipment and the equipment information must
be synchronized to the NMS.
Context
NOTICE
l In most cases, do not reset a board, because the network related to the device will be Down
for a while.
l Back up the key data before resetting the board.
l When you reset a board, do not perform hot swap for the board.
l When the active control board is reset, the equipment restarts without powering off the CPU
of the board. If the equipment has the standby control board, the equipment performs the
active/standby switchover after the board is reset.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
The NE Panel tab page is displayed by default.
Step 2 Optional: If you are currently visiting other tab pages on the NE Explorer tab page, you can
choose Device Management > NE Panel from the service tree to access the NE Panel tab page.
Step 3 Select the board to be reset on the NE panel, right-click it, and then select Reset Board.
Issue 01 (2014-01-31)
168
----End
Follow-up Procedure
If the status of the board is still offline after the board is reset for 10 minutes, click
Synchronize in the lower part of the NE panel to manually synchronize the status of the NE
panel. The status of the board cannot be refreshed when the configurations of other modules are
being synchronized.
Resetting a Subboard
This topic describes how to reset a subboard. When an abnormality occurs during the running
of a subboard, it is recommended that you reset the subboard.
Prerequisites
Telnet or STelnet parameters must be set on the NMS for accessing the device and device
configurations are synchronized to the NMS.
Context
NOTICE
l In normal cases, do not reset a subboard, because this operation may cause the network related
to the device to go Down for a while.
l Back up the key data before resetting the subboard.
l When you reset a subboard, do not hot swap the subboard.
Issue 01 (2014-01-31)
169
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
The NE Panel tab page is displayed by default.
Step 2 Optional: If you are currently visiting other tab pages on the NE Explorer tab page, you can
choose Device Management > NE Panel from the service tree to access the NE Panel tab page.
Step 3 Right-click the board of the subboard on the NE panel and choose Reset Subboard from the
shortcut menu.
Step 4 Click OK.
----End
Follow-up Procedure
If the subboard still cannot be operated 10 minutes after it is reset, that is, no subboard is displayed
on the NE panel, click Synchronize in the lower part of the NE panel to manually refresh the
status of the NE panel. The status of the subboard cannot be refreshed when the configurations
of other modules are being synchronized.
Prerequisites
l
Telnet or STelnet parameters must be set on the equipment and the equipment information
must be synchronized to the NMS.
Issue 01 (2014-01-31)
170
Context
NOTICE
To ensure the normal forwarding of data and reduce the impact on services during the active/
standby switchover on the equipment, enable GR of various routing protocols on the equipment
and its neighboring equipment, set the active/standby switchover parameters such as the default
slot ID of the standby control board on the equipment, enable the forcible active/standby
switchover function on the equipment, and configure the active control board and the standby
control board to automatically synchronize information. For details, see the GR configuration
in the Configuration Guide-Reliability.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
The NE Panel tab page is displayed by default.
Step 2 Optional: If you are currently visiting other tab pages on the NE Explorer tab page, you can
choose Device Management > NE Panel from the service tree to access the NE Panel tab page.
Step 3 Right-click the desired standby control board in the NE panel and choose Switch Active/
Standby Card from the shortcut menu.
Step 4 Click OK.
----End
171
Prerequisites
The equipment must be configured with Telnet or STelnet parameters, and equipment
information must be synchronized to the U2000.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Device Management > NE Panel from the service tree.
Step 3 On the NE Panel, select the port to be viewed, right-click, and then choose Object Attribute
from the shortcut menu.
NOTE
You can also click the Port Information tab. On the tab page, select the port to be viewed, right-click, and
then choose Object Attribute from the shortcut menu.
Step 4 In the Object Attribute dialog box, view basic port information and other associated
information.
Issue 01 (2014-01-31)
172
----End
Context
l
When an interface is idle or not connected to any cable, you need to disable the interface
to avoid the interface abnormality caused by interference.
When an interface has subinterfaces, the interval between enabling and disabling the
interface must at least be 15 seconds.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
The NE Panel tab page is displayed by default.
Step 2 If you are currently visiting other tab pages on the NE Explorer tab page, you can choose Device
Management > NE Panel from the service tree to access the NE Panel tab page.
Step 3 Right-click an interface on the NE panel, and then perform either of the following operations:
l Choose Up from the shortcut menu to enable the interface.
l Choose Down from the shortcut menu, and then click OK in the dialog box that is displayed
to disable the interface.
Issue 01 (2014-01-31)
173
----End
Monitoring NE Status
This topic describes how to monitor NE status. You can monitor the status of an NE by viewing
the system resource usage of the NE, storage space of the NE, and alarms of the NE. The
following takes the operation of viewing the version of an NE as an example to describe how to
monitor NE status.
Issue 01 (2014-01-31)
Function
Description
View Alarm
174
Function
Description
Tool
View NE Version
View NE Clock
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
The NE Panel tab page is displayed by default.
Step 2 If you are currently visiting other tab pages on the NE Explorer tab page, you can choose Device
Management > NE Panel from the service tree to access the NE Panel tab page.
Step 3 Right-click a shelf on the NE panel and choose View NE Version from the shortcut menu.
NOTE
Issue 01 (2014-01-31)
175
Step 4 Optional: In the View NE Version dialog box, click Save As to save the queried NE version
information to a local NE.
----End
Issue 01 (2014-01-31)
176
Function
Description
Reset Board
Reset Subboard
Issue 01 (2014-01-31)
View Alarms
177
Function
Description
NOTE
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
The NE Panel tab page is displayed by default.
Step 2 If you are currently visiting other tab pages on the NE Explorer tab page, you can choose Device
Management > NE Panel from the service tree to access the NE Panel tab page.
Step 3 Right-click a board in the NE panel and choose View Card Information from the shortcut
menu.
Step 4 Optional: In the View Board Information dialog box, click Refresh to refresh board
information.
Step 5 Optional: In the View Board Information dialog box, click Save As to save the queried board
information to a local device.
Issue 01 (2014-01-31)
178
----End
Issue 01 (2014-01-31)
Function
Description
Object Attribute
View Alarms
179
Function
Description
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
The NE Panel tab page is displayed by default.
Step 2 If you are currently visiting other tab pages on the NE Explorer tab page, you can choose Device
Management > NE Panel from the service tree to access the NE Panel tab page.
Step 3 Right-click a port in the NE panel and choose View Port Information from the shortcut menu.
Step 4 Optional: In the View Port Information dialog box, click Refresh to refresh port information.
Step 5 Optional: In the View Port Information dialog box, click Save As to save the queried port
information to a local device.
----End
Issue 01 (2014-01-31)
180
Procedure
Step 1 Right-click the cluster equipment in the Main Topology and choose NE Explorer from the
shortcut menu.
Step 2 Choose Device Management > NE Panel from the service tree.
Step 3 On the Subrack Information tab page, view the following parameters: Name, Subrack No.,
Software Version, Serial No., and Status.
Subrack information cannot be saved. Instead, you can refresh shelf information for query.
----End
Prerequisites
l
Telnet or STelnet parameters must have been set for the NE, and NE information must have
been synchronized to the U2000.
The user termination mode cannot be configured for Ethernet and Eth-Trunk interfaces. If
this mode is configured for an Ethernet or Eth-Trunk interface, the global performance
statistics function for subinterfaces does not take effect for relevant subinterfaces.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Device Management > Global System Configuration from the service tree.
Step 3 In the dialog box that is displayed, view the progress of global NE configuration synchronization.
NOTE
If a message indicating a synchronization failure is displayed, click Details. The failure causes of
configuration items are displayed. In the query result area, no values are displayed for the parameters
mapping the configuration items failed in synchronization.
181
----End
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Device Management > Historical Resources from the service tree.
NOTE
Alternatively, select a system control board on the NE Panel, right-click, and then choose View Historical
Resources from the shortcut menu to access the Historical Resources tab page.
Filter criteria for historical resources include Name, Resource Type, Type Description, Serial
Number, BOM ID, Shelf No., Slot No., Subslot No., Description, Inserted at, and Removed at.
Resource Type can be set to Board, Subboard, or All.
Inserted at and Removed at can be set according to the DST.
182
----End
Context
After historical resources are exported, the associated data is not deleted from the database. You
can query the data on the client.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Device Management > Historical Resources from the service tree.
NOTE
Alternatively, select a system control board on the NE Panel, right-click, and then choose View Historical
Resources from the shortcut menu to access the Historical Resources tab page.
Step 3 On the Historical Resources tab page, set filter criteria and click Query.
Step 4 Click Save As.
Step 5 In the Save dialog box, set the path, name, and format of the file to be saved.
Step 6 Click Save.
Step 7 Click OK.
Issue 01 (2014-01-31)
183
----End
Prerequisites
The features of related interface modules must be synchronized to the NMS.
Context
l
If a physical interface is idle and not connecting to any cable, disable this interface to prevent
interface malfunctions caused by interference.
Issue 01 (2014-01-31)
184
Exercise caution when you enable or disable an interface. In some situations, interface
parameters such as the working mode take effect only after the interface is enabled or
disabled.
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand Interface Management, and then click Interface Information.
Step 3 Optional: Click Condition. In the Filter Criteria dialog box, set query conditions, and then
click OK.
NOTE
When querying all records, you can click Query without setting any filtering rule.
Prerequisites
The features of related interface modules must be synchronized to the NMS.
Context
l
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand Interface Management, and then click Interface Information.
Step 3 Optional: Click Condition. In the Filter Criteria dialog box, set query conditions, and then
click OK.
Issue 01 (2014-01-31)
185
NOTE
When querying all records, you can click Query without setting any filtering rule.
If the peers of virtual connections are on different network segments, using only one master IP address
for the local interface cannot meet the communication requirements. Click Add to set a secondary IPv4
address to solve this problem.
NOTE
If the interface is a Layer 2 interface, the IP address of the interface cannot be set.
Prerequisites
l
Before monitoring real-time performance or querying performance data, ensure that the
Simple Network Management Protocol (SNMP) version is SNMPv2c or higher when you
create NEs. Otherwise, the U2000 cannot properly collect performance data.
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 To monitor the real-time performance of Ethernet interfaces, Ethernet subinterfaces, loopback
interfaces, tunnel interfaces, and VLAN interfaces, perform the following steps:
Choose Interface Management > Interface Information from the service tree to monitor the
real-time performance of all the interfaces that support this function.
Step 3 In the query result area, right-click the interface to be monitored and choose Monitor RealTime Performance from the shortcut menu.
In the dialog box that is displayed, view the graph of real-time board performance.
----End
Issue 01 (2014-01-31)
186
Configuring an E1 Interface
This topic describes how to configure an E1 interface. E1 interfaces are used to implement
multiple-channel communication in a system where a single physical channel consists of
multiple logical channels. If an interface is required to communicate with the peer NE, an E1
interface must be configured.
Prerequisites
l
The NE must support E1 interfaces and the E1 interface to be configured must exist on the
NE.
Context
To enable the U2000 to correctly display information about operation errors, perform the
following operations:
1.
2.
Run the snmp extend error-code enable command to enable the U2000 to correctly
display error codes.
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 Click Condition. In the Filter Criteria dialog box, set query conditions, and then click OK.
NOTE
When querying all records, you can click Query without setting any filtering rule.
Click the Physical Feature tab. Then, set Basic, Monitor Alarm Threshold and Timeslot
Configuration.
187
Prerequisites
l
The NE must support Ethernet interfaces and the Ethernet interface to be configured must
exist on the NE.
When you configure an Ethernet interface, all interface parameters except the interface IP
address have default values. If you need to change the values, ensure that the new values
are consistent with those on the peer NE.
Context
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 Optional: Click Condition. In the Filter Criteria dialog box, set query conditions, and then
click OK.
NOTE
When querying all records, you can click Query without setting any filtering rule.
Click the Physical Feature tab. Then set Working Mode, Negotiation Rate, Medium
Mode, Auto-Negotiation, Delay Time, Up Hold, Down Hold, Byte Overhead, Monitor
Alarm Threshold, and Transfer Mode.
Click the Ethernet Feature tab. Then set User Termination Mode, VLAN Swap, and
interface layer.
Click the IPv4 Address tab. Then set parameters such as the IPv4 address.
Click the Local CE tab. Then set the IP address, MAC address, and broadcast function of
the PE's Ethernet interface connected to the CE.
NOTE
If the Ethernet interface is a Layer 2 interface, no IP address can be set for the interface.
If the Ethernet interface is a Layer 3 interface, IPv4 addresses can be set for the interface.
Issue 01 (2014-01-31)
188
Prerequisites
l
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 On the Interface Information tab page, click Create and select Create Subinterface >
Ethernet Subinterface.
NOTE
After creation, you can also select the subinterface to be configured in the query result area and click
Configure to configure the created subinterface.
Step 4 In the Create Ethernet Subinterface dialog box, set the related parameters as required.
l
Click the General tab. Then, set Main Interface Name, Subinterface No., and
Description.
NOTE
l By default, the main interface name is the name of the currently selected main interface. You can
click the ... button to re-select the main interface.
l To enable the performance measurement function on the subinterface, select Statistic, and choose
to set Statistic Interval Time as required.
Click the Subinterface Feature tab. Then, do as follows to set Access Mode of the
subinterface:
If User Termination Mode is not set for the main interface, you can set Access
Mode to either of the following values for the subinterface:
VLAN Encapsulation (Subinterface is set to VLAN encapsulation.)
Flexible Access
If User Termination Mode is set for the main interface, you can set Access Mode to
either of the following values for the subinterface:
VLAN Termination (Stacking or Dot1q Termination can be choosed.)
Flexible Access
l
Issue 01 (2014-01-31)
Click the IPv4 Address tab. Then, set the IPv4 address of the subinterface.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
189
Click the Local CE tab. Then, set IPv4 and MAC addresses for the PE's interface connecting
to the CE, and enable the broadcast function.
Prerequisites
l
Before you create an Eth-Trunk interface, link-layer parameters must have been set for all
member interfaces and links must function properly.
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 On the Interface Information tab page, click the Create drop-down button and choose Create
Main Interface > Eth-Trunk Interface.
Step 4 In the Create Eth-Trunk Interface dialog box, set parameters as needed.
l
Click the General tab. Then, set Interface No. and Description.
Click the Physical Feature tab. Then, set User Termination Mode, VLAN Swap,
interface layer, Working Mode, Load Balancing Mode, Minimum Up Links, Maximum
Links Affecting Bandwidth, and LACP Feature.
Click the IPv4 Address tab. Then, set parameters such as the Internet Protocol Version 4
(IPv4) address.
190
Prerequisites
l
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 On the Interface Information tab page, click Create, and then select Create Subinterface >
Eth-Trunk Subinterface from the drop-down list.
NOTE
After creation, you can also select the subinterface to be configured in the query result area and click
Configure to configure the created subinterface.
Step 4 In the Create Eth-Trunk Subinterface dialog box, set parameters as required.
l
Click the General tab. Then, set Main Interface Name, Subinterface No. , and
Description.
NOTE
l By default, the main interface name is the name of the currently selected main interface. You can
click the ... button to re-select the main interface.
l To enable the performance measurement function on the subinterface, select Statistic, and choose
to set Statistic Interval Time as required.
Click the Subinterface Feature tab. Then, do as follows to set Access Mode of the
subinterface:
If User Termination Mode is not set for the main interface, you can set Access
Mode to either of the following values for the subinterface:
VLAN Encapsulation
Flexible Access
If User Termination Mode is set for the main interface, you can set Access Mode to
either of the following values for the subinterface:
VLAN Termination
Flexible Access
Click the IPv4 Address tab. Then, set parameters such as the IPv4 address.
Click the Local CE tab. Then, set IPv4 and MAC addresses for the PE's interface connecting
to the CE, and enable the broadcast function.
Issue 01 (2014-01-31)
191
Prerequisites
l
Context
An IMA group is a logical link consisting of one or more links. It is used to provide a higher
bandwidth that is approximately equal to the sum of all the member links' bandwidths.
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 On the Interface Information tab page, click the Create drop-down button and choose Create
Main Interface > IMA Interface.
NOTE
After creation, you can also select the interface to be configured in the query result area and click
Configure to configure the created interface.
Step 4 In the Create IMA Interface dialog box, set the related parameters.
l Click the General tab. Then, set Interface No. and Description.
l Click the Physical Feature tab. Then, set Transmission Clock Mode, Differential Delay,
Frame Length, Min. Active Links, and ATM Interface Type.
l Click the Member Interface tab. Then, add member interfaces.
Step 5 Optional: Click Apply. The interface is added.
Information about the new interface is displayed in the query result area.
You can add more interfaces by repeating the preceding steps.
Step 6 Click OK.
Issue 01 (2014-01-31)
192
Prerequisites
l
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 On the Interface Information tab page, click the Create drop-down button and choose Create
Subinterface > IMA Subinterface.
NOTE
After creation, you can also select the subinterface to be configured in the query result area and click
Configure to configure the created subinterface.
Step 4 In the Create IMA Subinterface dialog box, set the related parameters.
l Click the General tab. Then, set Main Interface Name, Subinterface Type, Subinterface
No., and Description.
l Click the PVC/PVP tab. Then, set the related PVC/PVP parameters for the IMA subinterface.
Step 5 Optional: Click Apply. The subinterface is added.
You can add more subinterfaces by repeating the preceding steps.
Information about the new subinterface is displayed in the query result area.
Step 6 Click OK.
Close the dialog box.
----End
Prerequisites
l
Issue 01 (2014-01-31)
193
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 On the Interface Information tab page, click the Create drop-down button and choose Create
Main Interface > Loopback Interface.
NOTE
After creation, you can also select the interface to be configured in the query result area and click
Configure to configure the created interface.
Step 4 In the Create Loopback Interface dialog box, set parameters as needed.
l
Click the General tab. Then, set Interface No. and Description.
Click the IPv4 Address tab. Then, set parameters such as IPv4 Address.
Prerequisites
l
The NE must support serial interfaces and the serial interface to be configured must exist
on the NE.
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 Optional: Click Condition. In the Filter Criteria dialog box, set query conditions, and then
click OK.
NOTE
When querying all records, you can click Query without setting any filtering rule.
Issue 01 (2014-01-31)
194
Click the Serial Feature tab. Then, set Link Layer Protocol, CRC Length, Negotiated
Packet Interval, and ATM Interface Type.
Prerequisites
A serial subinterface encapsulated in ATM can be created only when Link Layer Protocol is
set to ATM.
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 On the Interface Information tab page, click the Create drop-down button and choose Create
Subinterface > Serial Subinterface.
NOTE
After creation, you can also select the subinterface to be configured in the query result area and click
Configure to configure the created subinterface.
Step 4 In the Create Serial Subinterface dialog box, set the related parameters.
l Click the General tab. Then, set Main Interface Name, Subinterface Type, Subinterface
No., and Description.
l Click the PVC/PVP tab. Then, set the related PVC/PVP parameters for the subinterface.
Step 5 Optional: Click Apply. The subinterface is added.
You can add more subinterfaces by repeating the preceding steps.
Information about the new subinterface is displayed in the query result area.
Step 6 Click OK.
Issue 01 (2014-01-31)
195
Prerequisites
l
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 On the Interface Information tab page, click the Create drop-down button and choose Create
Main Interface > Tunnel Interface.
NOTE
After creation, you can also select the interface to be configured in the query result area and click
Configure to configure the created interface.
Step 4 In the Create Tunnel Interface dialog box, set parameters as needed.
l
Click the General tab. Then, set Interface No. and Description.
NOTE
To enable the performance measurement function on the interface, select Statistic, and choose to set
Statistic Interval Time as required.
Click the IPv4 Address tab. Then, set parameters such as IPv4 Address and Negotiated
IPv4 Address.
196
Prerequisites
l
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 On the Interface Information tab page, click the Create drop-down button and choose Create
Main Interface > Vlan Interface.
NOTE
After creation, you can also select the interface to be configured in the query result area and click
Configure to configure the created interface.
Step 4 In the Create Vlan Interface dialog box, set parameters as needed.
l
Click the General tab. Then, set Interface No. and Description.
Click the IPv4 Address tab. Then, set parameters such as IPv4 Address.
Creating an MP Interface
This topic describes how to create an MP interface. Multiple bound PPP links can be bound as
an MP interface to increase bandwidth. MP can be applied to PPP-capable interfaces such as
serial interfaces and low-speed POS interfaces. MP supports packet fragmentation. Fragmented
packets are sent to the same destination through multiple PPP links of an MP interface.
Prerequisites
l
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 On the Interface Information tab page, click the Create drop-down button and choose Create
Main Interface > MP Interface.
Issue 01 (2014-01-31)
197
NOTE
After creation, you can also select the interface to be configured in the query result area and click
Configure to configure the created interface.
Click the General tab, and then set Interface No. and Description.
Click the IPv4 Address tab, and then set parameters such as the interface IPv4 address.
Prerequisites
l
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 On the Interface Information tab page, click Create, and then select Create Main Interface
> Atm-Bundle Interface from the related drop-down list.
NOTE
After creation, you can also select the interface to be configured in the query result area and click
Configure to configure the created interface.
Step 4 In the Create Atm-Bundle Interface dialog box, set the related parameters as required.
l
Click the General tab. Then, set Interface No. and Description.
198
Creating a VE Interface
This topic describes how to create a Virtual Ethernet (VE) interface. If Point-to-Point Protocol
over Ethernet (PPPoE) or Internet Protocol over Ethernet (IPoE) packets need to be transmitted
over an Asynchronous Transfer Mode (ATM) network, VE interfaces must be configured to
implement interworking between PPPoE and ATM or between IPoE and ATM. VE interfaces
can also be used to access a Layer 2 Virtual Private Network (L2VPN), Virtual Private LAN
Segment (VPLS), and Layer 3 Virtual Private Network (L3VPN), or to perform Layer 3 packet
forwarding.
Prerequisites
l
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 On the Interface Information tab page, click the Create drop-down button and choose Create
Main Interface > VE Interface.
NOTE
After creation, you can also select the interface to be configured in the query result area and click
Configure to configure the created interface.
Step 4 In the Create VE Interface dialog box, set the related parameters.
l
Click the General tab. Then set Interface No. and Description.
Click the IPv4 Address tab. Then, set parameters such as IPv4 Address.
Creating a VE Subinterface
This topic describes how to create a VE subinterface. A VE interface supports multiple logical
subinterfaces. These logical subinterfaces use physical layer and link layer configuration
parameters of the VE interface, and have their own network layer configuration parameters.
Issue 01 (2014-01-31)
199
Prerequisites
l
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 On the Interface Information tab page, click Create, and then select Create Subinterface >
VE Subinterface from the related drop-down list.
NOTE
After creation, you can also select the subinterface to be configured in the query result area and click
Configure to configure the created subinterface.
Step 4 In the Create VE Subinterface dialog box, set the related parameters as required.
l
Click the General tab. Then, set Subinterface No. and Description.
NOTE
To enable the performance measurement function on the subinterface, select Statistic, and choose
to set Statistic Interval Time as required.
Click the Subinterface Feature tab. Then, set the encapsulate mode or termination mode
for the subinterface.
Click the IPv4 Address tab. Then, set parameters such as the subinterface IPv4 address.
Prerequisites
l
Issue 01 (2014-01-31)
200
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 On the Interface Information tab page, click the Create drop-down button and choose Create
Main Interface > DSLGroup Interface.
NOTE
After creation, you can also select the interface to be configured in the query result area and click
Configure to configure the created interface.
Step 4 In the Create DslGroup Interface dialog box, set the related parameters.
l
Click the General tab. Then set Interface No. and Description.
Click the Physical Feature tab. Then set Basic Information and IMA Group Feature.
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 On the Interface Information tab page, click the Create drop-down button and choose Create
Main Interface > Global-MP Interface.
NOTE
After creation, you can also select the interface to be configured in the query result area and click
Configure to configure the created interface.
Step 4 In the Create Global-MP Interface dialog box, set parameters as required.
l
Click the General tab, and then set Interface No. and Description.
Issue 01 (2014-01-31)
201
Click the IPv4 Address tab, and then set parameters such as the interface IPv4 address.
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 On the Interface Information tab page, click the Create drop-down button and choose Create
Main Interface > Cpos-Trunk Interface.
NOTE
After creation, you can also select the interface to be configured in the query result area and click
Configure to configure the created interface.
Step 4 In the Create Cpos-Trunk Interface dialog box, set parameters as required.
l
Click the General tab, and then set Interface No. and Description.
202
clearly displayed. This enhances the relationship between the interface and the service feature
and improves the U2000 usability.
Prerequisites
The features of related interface modules must be synchronized to the NMS.
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 Optional: Click Condition. In the Filter Criteria dialog box, set query conditions, and then
click OK.
NOTE
When querying all records, you can click Query without setting any filtering rule.
Prerequisites
The features of related interface modules must be synchronized to the NMS.
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Issue 01 (2014-01-31)
203
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 Optional: Click Condition. In the Filter Criteria dialog box, set query conditions, and then
click OK.
NOTE
When querying all records, you can click Query without setting any filtering rule.
On the Configure Bandwidth tab page, configure bandwidth restriction for a selected EthTrunk interface and click Apply.
2.
On the GTS tab page, set the related parameters. For details about how to set the parameters,
see Configuring the GTS for Interface QoS.
3.
On the Applying Policy tab page, click Deploy. In the dialog box that is displayed, set the
related parameters. For details about how to set the parameters, see Deploying Applying
Policies for Interface QoS.
4.
On the DiffServ Mode tab page, set the related parameters. For details about how to set
the parameters, see Configuring the DiffServ for Interface QoS.
5.
On the Other tab page, set the related parameters and click Apply.
----End
Result
Information about the configured QoS is displayed in the result area on the related tab page.
Prerequisites
The features of related interface modules must be synchronized to the NMS.
Procedure
Step 1 Right-click an NE in the topology view and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 Optional: Click Condition. In the Filter Criteria dialog box, set query conditions, and then
click OK.
NOTE
When querying all records, you can click Query without setting any filtering rule.
204
Generally, ICMP redirection packets and ICMP host unreachable packets are sent properly. If network
traffic is heavy, NEs may send may ICMP packets, which increases network traffic. Especially, if a
malicious attack is launched, network congestion is increased. Therefore, it is recommended that the
preceding two check boxes be cleared to reduce network traffic and prevent malicious attacks.
Prerequisites
Telnet or STelnet parameters must be set on the equipment and the equipment information must
be synchronized to the U2000.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose System Management > NE Channel Management > VTY Service from the service
tree.
Step 3 On the VTY Service tab page, set Max. Available VTYs with up and down arrows. Click
Apply.
Step 4 Select a VTY record in the VTY service view. Set VTY parameters.
Step 5 Click Apply.
----End
205
Prerequisites
Telnet or STelnet parameters must be set on the equipment and the equipment information must
be synchronized to the U2000.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose System Management > NE Channel Management > FTP Service from the service
tree.
Step 3 On the FTP Service tab page, determine whether to enable FTP Server, set FTP Server
Timeout and VRF Name. If FTP Server is disabled, you cannot set FTP Server Timeout.
NOTE
If the U2000 manages NEs in inband VPN networking mode, the VRF name must be specified.
----End
Prerequisites
The features of local user must be synchronized to the NMS.
Context
A maximum of 1000 local user accounts can be configured on each managed U2000.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose System Management > NE Channel Management > Local User from the service tree.
Step 3 On the Local User tab page, set Number of Password Retries.
Step 4 Right-click on the Local User tab page and choose Create from the shortcut menu.
Step 5 In the Create Local User dialog box, set the related parameters.
Step 6 Click OK or Apply.
----End
Issue 01 (2014-01-31)
206
Prerequisites
l
The selected equipment must support the log service function on the U2000.
Telnet or STelnet parameters must be set on the equipment and the equipment information
must be synchronized to the U2000.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose System Management > NE Channel Management > Syslog Service from the service
tree.
Step 3 On the Syslog Service tab page, click Synchronize.
Step 4 Click Enable or Disable to change the service status of the Syslog source interface.
NOTE
If the Syslog source of the host is in use, you cannot select the Syslog source interface from the drop-down
list box. The displayed status button is Disable. Click Disable to disable the log source. Then, you can
select the Syslog source interface from the drop-down list box. The status button that is displayed changes
to Enable.
Step 5 When the Syslog source is disabled, select the source interface for sending Syslog files from the
drop-down list box, and then click Enable.
----End
Prerequisites
The IP address of the log host must be known.
Context
To view NE Syslog using the U2000, set Log Host IP Address to U2000 Server IP Address
to configure the U2000 server as the NE Syslog receiver.
Issue 01 (2014-01-31)
207
NOTE
The system supports the configuration of a maximum of eight log hosts to realize backup among log hosts.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose System Management > NE Channel Management > Syslog Service from the service
tree.
Step 3 Right-click on the Syslog Service tab page and choose Create from the shortcut menu.
NOTE
If the U2000 manages NEs in inband VPN networking mode, the VRF name must be specified.
Step 4 In the Create Log Host dialog box, set the related parameters.
Step 5 Click OK.
If more than one log host is created, the Create Log Host progress bar is displayed. After all
the log hosts are created, click OK.
----End
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose System Management > NE Channel Management > Syslog Service from the service
tree.
Step 3 On the Syslog Service tab page, click Advanced.
Step 4 In the Advanced Configuration dialog box, set the parameters in the Log buffer and Log
File areas.
Step 5 Click OK.
----End
Issue 01 (2014-01-31)
208
Prerequisites
The trap source interface and its IP address must be known.
Context
An SNMP trap, no matter which interface it comes from, carries a trap address, also called the
address of the trap source interface. When you want to trace a certain event through the trap
address, you can configure the trap source interface.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose System Management > NE Channel Management > Trap Service from the service
tree.
Step 3 On the Trap Service tab page, click Synchronize.
Step 4 Click Enable or Disable to change the service status of the trap source interface.
NOTE
If the trap source of the host is in use, you cannot select the trap source interface from the drop-down list
box. The status button that is displayed is Disable. Click Disable to disable the trap source. Then, you can
select the trap source interface from the drop-down list box. The status button that is displayed changes to
Enable.
Step 5 When the trap source is disabled, select the source interface for sending traps from the dropdown list box, and then click Enable.
----End
Prerequisites
The IP address of the trap receiving host must be known.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose System Management > NE Channel Management > Trap Service from the service
tree.
Issue 01 (2014-01-31)
209
Step 3 Right-click on the Trap Service tab page and choose Create from the shortcut menu.
Step 4 In the Create Receiving Host dialog box, set the related parameters.
NOTE
If the U2000 manages NEs in inband VPN networking mode, the VRF name must be specified.
If more than one receiving host is created, the Create Receiving Host progress bar is displayed. After the
receiving hosts are created, click OK.
----End
Prerequisites
l
The selected equipment must support the configuration of the trap service on the U2000.
Telnet or STelnet parameters must be set on the equipment, and configurations on the
equipment must be synchronized to the U2000.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose System Management > NE Channel Management > Trap Service from the service
tree.
Step 3 On the Trap Service tab page, click Send.
Step 4 In the Configure Sending Module dialog box, do as follows:
l Select the Global Configuration option button. Then, you can configure alarm control on
all modules of the equipment, including Enable Function of All Non-excessive Alarms,
Disable Function of All Non-excessive Alarms, Disable Function of All Excessive
Alarms, and Disable All Alarms.
l Select the Feature Configuration option button. Then, you can configure alarm control on
certain feature modules of the equipment. To configure alarm control, you need to select a
module node and then select the corresponding option button on the right. If you need to
enable a certain excessive alarm, expand the feature module of the alarm and select the check
box corresponding to this module.
Issue 01 (2014-01-31)
210
Prerequisites
l
The selected equipment must support the configuration of the trap service on the U2000.
Telnet or STelnet parameters must be set on the equipment, and configurations on the
equipment must be synchronized to the U2000.
Issue 01 (2014-01-31)
211
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose System Management > NE Channel Management > Trap Service from the service
tree.
Step 3 On the Trap Service tab page, click Advanced.
Step 4 In the Advanced Configuration dialog box, set the related parameters.
Step 5 Click OK.
----End
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose System Management > NE Channel Management > SSH Service > SSH Global
Configuration from the service tree.
NOTE
If no global SSH data is available, click Synchronize. In the Confirm dialog box, click Yes.
Step 3 Set the parameters on the SSH Global Configuration tab page.
Issue 01 (2014-01-31)
212
Before the configuration, you can click Synchronize to synchronize the SSH global parameter settings on
the equipment to the U2000 if you need to view them.
----End
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose System Management > NE Channel Management > SSH Service > SSH Session
Status from the service tree.
Step 3 Right-click on the SSH Session Status tab page and choose Synchronize from the shortcut
menu.
----End
Prerequisites
l
Issue 01 (2014-01-31)
The selected equipment must support the configuration of the SSH service on the U2000.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
213
SNMP parameters on the U2000 must be consistent with those on the equipment.
Context
When the authentication types of the SSH user include password authentication, you need to
create a local SSH user with exactly the same name in the local user service and set a password
for the user.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose System Management > NE Channel Management > SSH Service > SSH User from
the service tree.
Step 3 On the SSH tab page, click Create.
Step 4 Set the parameters in the Create SSH User dialog box.
Issue 01 (2014-01-31)
214
Start
End
A specified website can be accessed only during the working hours (from 8:00 to 18:00)
from Monday to Friday.
User activities are logged for the users who access a specified website during non-working
hours (from 18:00 to 8:00 on the next day).
Prerequisites
Telnet or STelnet parameters must be set on the U2000 for accessing equipment and equipment
configurations must be synchronized to the U2000.
Context
l
When creating a time range, you must configure at least one periodic or absolute time range.
Creating null time ranges is not allowed.
You can configure multiple periodic or absolute time ranges for a time range.
Issue 01 (2014-01-31)
215
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose ACL Management > Time Range from the service tree.
Step 3 On the Time Range tab page, click Create.
NOTE
You can also right-click in the query result area and choose Create from the shortcut menu.
Step 4 In the Create Time Range dialog box, set Time Range Name.
Step 5 Right-click in the Absolute Time Range area and choose Create from the shortcut menu.
Step 6 In the Create Absolute Time Range dialog box, set the related parameters and click OK.
Step 7 Right-click in the Periodic Time Range area and choose Create from the shortcut menu.
Step 8 In the Create Periodic Time Range dialog box, set the related parameters and click OK.
216
Prerequisites
Telnet or STelnet parameters must be set on the U2000 for accessing equipment and equipment
configurations must be synchronized to the U2000.
Context
l
You can enable a time range to take effect during the specific period by creating an absolute
time range in the time range.
You can create an absolute time range when creating a time range. For details, see Creating
a Time Range.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose ACL Management > Time Range from the service tree.
Step 3 On the Time Range tab page, click Query.
Step 4 In the query result area, select a time range record.
Step 5 On the Detail Information tab page, right-click in the Absolute Time Range area and choose
Create from the shortcut menu.
Step 6 In the Create Absolute Time Range dialog box, set the related parameters and click OK.
Step 7 Click Apply.
----End
Prerequisites
Telnet or STelnet parameters must be set on the U2000 for accessing equipment and equipment
configurations must be synchronized to the U2000.
Context
l
You can enable a time range to take effect at a specific time by creating a periodic time
range in the time range.
You can create a periodic time range when creating a time range. For details, see Creating
a Time Range.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Issue 01 (2014-01-31)
217
Step 2 Choose ACL Management > Time Range from the service tree.
Step 3 On the Time Range tab page, click Query.
Step 4 In the query result area, select a time range record.
Step 5 On the Detail Information tab page, right-click in the Periodic Time Range area and choose
Create from the shortcut menu.
Step 6 In the Create Periodic Time Range dialog box, set the related parameters and click OK.
Step 7 Click Apply.
----End
Prerequisites
Telnet or STelnet parameters must be set on the U2000 for accessing equipment and equipment
configurations must be synchronized to the U2000.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose ACL Management > ACL Group from the service tree.
Step 3 On the ACL Group tab page, click Create.
NOTE
You can also right-click in the query result area and choose Create from the shortcut menu.
Step 4 In the Create ACL Group dialog box, set the related parameters.
218
An ACL consists of a series of rules. ACL rules have the following features:
l
Only source IP addresses can be used as the elements for defining basic ACL rules.
Advanced ACL rules can be defined by elements including the source IP address and
destination IP address of packets, the protocol type on the IP bearer network, and protocol
features. Advanced ACL rules are more accurate, diversified, and flexible than basic ACL
rules.
Different from other ACL rules, interface ACL rules are defined according to the interfaces
that receive packets.
Simple ACL rules can be defined according to information such as the source IP address,
destination IP address, user group, protocol type on the IP bearer network, and protocol
feature. With simple ACL rules, you can define authority group rules for a user to access
the network or communicate with other users.
Layer 2 ACL rules are applied to the second layer. You can use the Layer 2 ACL rules
when configuring the features including QoS, NAT, policy-based routing, and packet
filtering.
Ethernet frame ACL rules are defined according to the MAC address and protocol type.
Prerequisites
l
Telnet or STelnet parameters must be set on the U2000 for accessing equipment and
equipment configurations must be synchronized to the U2000.
A basic ACL group must be configured and ACL group configurations on equipment must
be synchronized to the U2000.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose ACL Management > ACL Rules > Basic Rule from the service tree.
Step 3 On the Basic Rule tab page, click Create.
NOTE
You can also right-click in the query result area and choose Create from the shortcut menu.
Step 4 In the Create Basic Rule dialog box, set the related parameters.
Issue 01 (2014-01-31)
219
Prerequisites
l
Telnet or STelnet parameters must be set on the U2000 for accessing equipment and
equipment configurations must be synchronized to the U2000.
An interface ACL group must be configured and ACL group configurations on equipment
must be synchronized to the U2000.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose ACL Management > ACL Rules > Interface Rule from the service tree.
Step 3 On the Interface Rule tab page, click Create.
NOTE
You can also right-click in the query result area and choose Create from the shortcut menu.
Step 4 In the Create Interface Rule dialog box, set the related parameters.
Issue 01 (2014-01-31)
220
Prerequisites
l
Telnet or STelnet parameters must be set on the U2000 for accessing equipment and
equipment configurations must be synchronized to the U2000.
An advanced ACL group must be configured and ACL group configurations on equipment
must be synchronized to the U2000.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose ACL Management > ACL Rules > Advanced Rule from the service tree.
Step 3 On the Advanced Rule tab page, click Create.
NOTE
You can also right-click in the query result area and choose Create from the shortcut menu.
Step 4 In the Create Advanced Rule dialog box, set the related parameters.
Issue 01 (2014-01-31)
221
Creating a VLAN
This topic describes how to create a VLAN on an NE.
Prerequisites
l
Issue 01 (2014-01-31)
222
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Ethernet Feature Management > VLAN Management > Global VLAN
Management from the service tree.
Step 3 On the Global VLAN Management tab page, click Create.
NOTE
You can also right-click in the query result area and choose Create from the shortcut menu.
Step 4 In the Create VLAN dialog box, set the related parameters.
Step 5 Click OK or Apply.
----End
Prerequisites
l
Context
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Ethernet Feature Management > VLAN Management > Global VLAN
Management from the service tree.
Step 3 On the Global VLAN Management tab page, set the filter criteria and click Query.
Step 4 In the query result area, select a equipment record.
Step 5 On the VLAN Member Port tab page, click Add.
Step 6 In the Add Member Port dialog box, set the relate parameters.
Issue 01 (2014-01-31)
223
Click the
list.
Click the
Port list.
button. All the selected member ports are added to the Selected
Click the
list.
Click the
Port list.
button. All the selected member ports are added to the Selected
Issue 01 (2014-01-31)
224
Prerequisites
l
Context
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Ethernet Feature Management > VLAN Management > Global VLAN
Management from the service tree.
Step 3 On the Global VLAN Management tab page, set the filter criteria and click Query.
Step 4 In the query result area, select a equipment record.
Step 5 On the VLAN Interface tab page, choose whether to configure a VLAN interface.
l
If you click the Not Configure VLAN Interface option button, the configured VLAN
interface information is deleted after you click Apply.
If you click the Configure VLAN Interface option button, set the related parameters.
Issue 01 (2014-01-31)
225
Prerequisites
The configurations of MAC address forwarding management must be synchronized to the
U2000.
Context
You can bind only a unicast MAC address to an interface. You cannot bind a multicast MAC
address or a special MAC address to an interface. The special MAC address is reserved for other
usages, for example, the MAC address of a special packet.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Ethernet Feature Management > MAC Address Forwarding Management > Static
MAC Address Forwarding Table from the service tree.
Step 3 On the Static MAC Address Forwarding Table tab page, click Create.
NOTE
You can also right-click in the query result area and choose Create from the shortcut menu.
Step 4 In the Create Static MAC Address Forwarding Entry dialog box, set the related parameters.
Issue 01 (2014-01-31)
226
Prerequisites
The configurations of MAC address learning restriction rules must be synchronized to the
U2000.
Context
l
The supported MAC address learning restriction rules vary according to the equipment
being used.
Three types of Layer 2 interfaces, that is, FE, GE, and Eth-Trunk interfaces, support MAC
address learning restriction rules. Other physical interfaces, logical interfaces, or subinterfaces do not support MAC address learning restriction rules.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Ethernet Feature Management > MAC Address Forwarding Management > MAC
Address Learning Restriction from the service tree.
Step 3 On the MAC Address Learning Restriction tab page, select the type of a learning address
restriction rule from the Function drop-down list.
NOTE
The displayed tab varies according to the selected type of the MAC address learning restriction rule.
Step 4 Click Create, or right-click in the query result area and choose Create from the shortcut menu.
Step 5 In the Create MAC Address Learning Restriction dialog box, set the related parameters.
l
227
Context
l
The aging time is applicable to only dynamic entries in the MAC address forwarding table
because non-dynamic entries do not age.
If the aging time is set to 0, no entry of the MAC address forwarding table ages.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Ethernet Feature Management > MAC Address Forwarding Management > MAC
Address Aging Time from the service tree.
Step 3 On the MAC Address Aging Time tab page, click Synchronize.
You can check whether the MAC address aging time of the NE meets the requirements.
Step 4 In the MAC Address Aging Time text box, enter the aging time.
NOTE
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Ethernet Feature Management > MAC Address Forwarding Table > MAC
Address Table Information from the service tree.
Step 3 Select the information to be queried from the MAC Address Table Type drop-down list.
Step 4 Optional: In the Condition area, set filter criteria.
If MAC Address Table Type is set to MAC address dynamic table, more filter criteria can
be set.
Step 5 Click Display. The required information is displayed in the Result area.
Issue 01 (2014-01-31)
228
NOTE
Issue 01 (2014-01-31)
229
Is CFM enabled?
No
Yes
Create an MD
Create an MA
Is the
interface MIP policy
modified?
No
Yes
Configure the interface MIP creation
policy
No
Do the local
MEP and remote MEP
or MIP exist?
Yes
Create a OAM measure task
Mandatory
Optional
End
Issue 01 (2014-01-31)
230
Is EFM enabled?
No
Yes
Set port EFM parameters
Is the status
of the OAM session
Detected?
No
Yes
Set loopback test parameters
End
Context
OAM functions are unavailable if the following functions are disabled:
l
Issue 01 (2014-01-31)
231
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand Reliablity > OAM Management > Ethernet OAM
Management, and then click Ethernet OAM Global Configuration.
Step 3 Configure Ethernet OAM globally.
NOTE
If data synchronization is not performed for the NE, perform data synchronization first.
Creating an MD
This topic describes how to create a Maintenance Domain (MD). An MD is a network or a part
of a network is a network or a part of a network for which Connectivity Fault Management
(CFM) is performed. Different MDs can be set to restrict the areas that packets in different
Operation, Administration, and Maintenance (OAM) areas can arrive or transverse.
Issue 01 (2014-01-31)
232
Prerequisites
CFM must be enabled on the Ethernet OAM Global Configuration tab page.
Context
A maximum of 16 MDs can be configured for an NE.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand Reliablity > OAM Management > Ethernet OAM Management
> Ethernet Service OAM, and then click MD Management.
Step 3 On the MD Management tab page, Click Create, or right-click in the query result area and
select Create on the shortcut menu.
Step 4 In the Create MD dialog box, set MD parameters.
Method 1:
Click Select and select the MD information created for another NE.
NOTE
l Some parameters may fail to be copied to the destination NE because of NE version differences.
l The MD information copied from another NE can be modified as needed.
Method 2:
Select the Create Default MD check box and set the related parameters.
Issue 01 (2014-01-31)
233
NOTE
This check box is available only when CFM Version is set to Standard on the Ethernet OAM
Global Configuration tab page.
Method 3:
Set MD Name and other parameters.
Creating an MA
This topic describes how to create a Maintenance Association (MA). An MA is a part of a
Maintenance Domain (MD). An MD can be divided into one or more MAs. Ethernet
Connectivity Fault Management (CFM) performs connectivity fault detection for each MA.
Prerequisites
l
CFM must be enabled on the Ethernet OAM Global Configuration tab page.
An MD must exist.
Context
A maximum of 512 MAs can be configured for an NE.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand Reliablity > OAM Management > Ethernet OAM Management
> Ethernet Service OAM, and then click MA Management.
Step 3 On the MA Management tab page, Click Create, or right-click in the query result area and
select Create on the shortcut menu.
Step 4 In the Create MA dialog box, set general MA parameters.
Issue 01 (2014-01-31)
234
To copy the MA information created for another NE, perform the following operations:
Click Select and select the MA information created for another NE.
NOTE
l Some parameters may fail to be copied to the destination NE because of NE version differences.
l The MA information copied from another NE can be modified as needed.
Step 5 Optional: On the Parameter of Alarm tab page, set Operation, Administration, and
Maintenance (OAM) alarm parameters.
Step 6 Optional: On the Parameter of Alarm tab page, set Alarm indicate function.
Issue 01 (2014-01-31)
235
Issue 01 (2014-01-31)
236
1.
2.
Click Select.
3.
In the Select Interface dialog box, select one or more interfaces for which alarms need to
be monitored.
NOTE
The alarm status of only physical interfaces and Eth-Trunk interfaces can be monitored.
4.
Click OK.
Issue 01 (2014-01-31)
237
Prerequisites
l
Connectivity Fault Management (CFM) must be enabled on the Ethernet OAM Global
Configuration tab page.
An MA must exist.
A local MEP can be created on a Gigabit Ethernet (GE) interface, a common Fast Ethernet
(FE) interface, or a trunk interface.
If an MA is not associated with any service, the local MEP direction in the MA cannot be
set to Inward.
Context
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand Reliablity > OAM Management > Ethernet OAM Management
> Ethernet Service OAM, and then click Local MEP Management.
Step 3 On the Local MEP Management tab page, Click Create, or right-click in the query result area
and select Create on the shortcut menu.
Step 4 In the Create Local MEP dialog box, set the general parameters.
Issue 01 (2014-01-31)
238
To copy the local MEP information created for another NE, perform the following operations:
1.
Click the ... button on the right of the MD Name text box. Then, select an MD and an MA.
2.
Click Select and select the MEP information created for another NE.
The MEP information copied from another NE can be modified as needed.
NOTE
Some parameters may fail to be copied to the destination NE because of NE version differences.
Step 5 Optional: On the AIS VLAN Configuration tab page, set alarm indication signal parameters.
Step 6 Click OK or Apply.
Issue 01 (2014-01-31)
239
Prerequisites
l
Connectivity Fault Management (CFM) must be enabled on the Ethernet OAM Global
Configuration tab page.
An MA must exist.
Context
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand Reliablity > OAM Management > Ethernet OAM Management
> Ethernet Service OAM, and then click Remote MEP Management.
Step 3 On the Remote MEP Management tab page, Click Create, or right-click in the query result
area and select Create on the shortcut menu.
Step 4 In the Create Remote MEP dialog box, set the related parameters.
Issue 01 (2014-01-31)
240
To copy the local MEP information created for another NE, perform the following operations:
1.
Click the ... button on the right of the MD Name text box. Then, select an MD and an MA.
2.
Click Select and select the local MEP information created for another NE.
The local MEP information copied from another NE can be modified as needed.
NOTE
Some parameters may fail to be copied to the destination NE because of NE version differences.
Prerequisites
l
Connectivity Fault Management (CFM) must be enabled on the Ethernet OAM Global
Configuration tab page.
Context
If the MIP creation policy is set to Default or Explicit on the U2000, the NE automatically
creates MIPs based on the policy.
The rules for generating MIPs on interfaces are as follows:
l
If no MIP creation policy has been configured for the specified interface or the created MIP creation policy
has been deleted from the interface, the interface inherits the global MIP creation policy.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Issue 01 (2014-01-31)
241
Step 2 In the service tree, expand Reliablity > OAM Management > Ethernet OAM Management
> Ethernet Service OAM, and then click MIP Policy Management.
Step 3 On the MIP Policy Management tab page, click Query. The NE automatically generates MIP
information based on certain rules and displays the information in the query result area.
Step 4 Select the MIP information to be modified and click the Configure Creation Policy drop-down
button. Alternatively, right-click the information and choose Configure Creation Policy from
the shortcut menu. Use any of the preceding methods to modify the MIP creation policy for the
interface.
----End
Creating a MIP
This topic describes how to create a Maintenance Association Intermediate Point (MIP) on an
NE. A MIP is a node inside an MA. MEPs periodically send multicast CCMs. A MIP needs to
be used to locate faults.
Prerequisites
1.
2.
3.
Context
When all devices in the MD are enabled with the CCM sending function, MEPs send multicast
CCMs periodically. If a MEP does not receive any CCMs from an RMEP within three
consecutive sending intervals, this means that a connectivity fault between the MEP and RMEP
occurs. A MIP needs to be used to locate the fault.
Figure 3-4 Diagram of the MIP function
LTM
MEP1
MEP2
MIP1
MIP2
LTR
MEP
MIP
LTM data flow
LTR data flow
As shown in Figure 3-4, the 802.1ag MAC trace operation is performed from MEP1 to MEP2.
MEP1 sends a Linktrace message (LTM) to MEP2. After receiving the LTM, MIP1 replies
MEP1 with an LTR packet and forwards the LTM. Because a fault occurs on the link between
Issue 01 (2014-01-31)
242
MIP1 and MIP2, MIP2 fails to receive the LTM and does not send the LTR packet. This means
that the MEP2 is faulty. In this way, the faulty device is located.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Reliablity > OAM Management > Ethernet OAM Management > Ethernet Service
OAM > MIP Information from service tree.
Step 3 On the MIP Information tab page, click Create. Alternatively, right-click in the query result
area and choose Create from the shortcut menu.
Step 4 In the Create MIP Information dialog box, set the related parameters.
Prerequisites
l
Connectivity Fault Management (CFM) must be enabled on the Ethernet OAM Global
Configuration tab page.
Bidirectional Forwarding Detection (BFD) must be configured and a BFD session must
exist.
Context
CFM-BFD binding is applicable to the following scenario:
As shown in Figure 3-5, CEs are dual homed to PEs that belong to a Multiprotocol Label
Switching (MPLS) network. BFD is configured for the MPLS Label Switched Path (LSP)
between PEs, and Ethernet Operation, Administration, and Maintenance (OAM) is configured
between the CEs and PEs. The configuration helps to implement end-to-end link fault detection.
Issue 01 (2014-01-31)
243
If the BFD module on the core network detects a fault, the related PE notifies the Ethernet OAM
module of the fault. Then, the related CE is switched to the backup path.
Figure 3-5 Application scenario of CFM-BFD binding
PE1
802.3ah
PE2
802.3ah
CE2
CE1
PE3
PE4
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand Reliablity > OAM Management > Ethernet OAM Management
> Ethernet Service OAM > CFM-BFD Binding.
Step 3 On the CFM-BFD Binding tab page, click Create.
Step 4 In the Create CFM-BFD Binding dialog box, set the related parameters.
1.
Click the ... button on the right of the MD Name text box. In the dialog box that is displayed,
select the MD and MA to be bound.
2.
Click the ... button on the right of the BFD Session ID text box. In the dialog box that is
displayed, select the BFD session to be bound.
3.
4.
Click OK or Apply.
----End
244
Prerequisites
1.
2.
3.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Reliablity > OAM Management > Ethernet OAM Management > Ethernet Service
OAM > CFM-CFM Binding from the service tree.
Step 3 On the CFM-CFM Binding tab page, click Create.
Step 4 In the Create CFM-CFM Binding dialog box, set binding parameters.
1.
Click the ... button on the right of the Ingress MD Name text box. In the dialog box that
is displayed, select the uplink MD and MA to be bound.
2.
Click the ... button on the right of the Egress MD Name text box. In the dialog box that is
displayed, select the downlink MD and MA to be bound.
3.
4.
Click OK or Apply.
----End
Prerequisites
EFM is enabled in Ethernet OAM Global Configuration.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand Reliablity > OAM Management > Ethernet OAM Management
> Ethernet Link OAM > Ethernet Link OAM.
Step 3 On the Ethernet Link OAM tab, click Query. Information about the available ports on the
device is displayed.
Step 4 Select the port, and then click Set, or right-click it and select Set on the shortcut menu.
Step 5 In the Configure Port dialog box, click the General and Advanced tabs to set the related
parameters.
Issue 01 (2014-01-31)
245
NOTE
The U2000 provides default values for parameters on the Advanced tab. It is recommended to adopt the
default values rather than modify those parameters.
Issue 01 (2014-01-31)
246
Prerequisites
Ethernet in the First Mile (EFM) must be enabled on the Ethernet OAM Global
Configuration tab page.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand Reliablity > OAM Management > Ethernet OAM Management
> Ethernet Link OAM > Ethernet Link OAM.
Step 3 On the Ethernet Link OAM tab page, click Query. Information about the available ports on
the NE is displayed.
Step 4 Select a port and click the OAM Session tab. Then, click Synchronize.
Step 5 After the synchronization, view the OAM session status in the EFM Protocol Enabling
Status column.
----End
Prerequisites
Two ports must be connected directly by a link and the following requirements must be met to
ensure the link connectivity:
l
Ethernet in the First Mile (EFM) must be enabled on the Ethernet OAM Global
Configuration tab page.
Context
Performing a loopback test on a port interrupts all services running on the port.
Issue 01 (2014-01-31)
247
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand Reliablity > OAM Management > Ethernet OAM Management
> Ethernet Link OAM > Ethernet Link OAM.
Step 3 On the Ethernet Link OAM tab page, click Query. Information about the available interfaces
is displayed in the query result area.
Step 4 Select a port and click Loopback Test. Alternatively, right-click the port and choose Loopback
Test from the shortcut menu.
Step 5 Optional: In the Loopback Test dialog box, click Set.
1.
2.
Prerequisites
1.
2.
3.
4.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Issue 01 (2014-01-31)
248
Step 2 Choose Reliablity > OAM Management > Ethernet OAM Management > Ethernet Link
OAM > EFM-BFD Binding from the service tree.
Step 3 On the EFM-BFD Binding tab page, click Create.
Step 4 In the Create EFM-BFD Binding dialog box, set binding parameters.
1.
Click the ... button on the right of the Interface Name text box. In the dialog box that is
displayed, select the EFM interface to be bound.
2.
Click the ... button on the right of the BFD Session ID text box. In the dialog box that is
displayed, select the BFD session to be bound.
3.
4.
Click OK or Apply.
----End
Prerequisites
1.
2.
An MD must exist.
3.
An MA must exist.
Context
EFM-CFM binding is applicable to the following scenario:
IEEE 802.3ah is designed for the last mile of the Ethernet to detect the direct link between a CE
and a PE. IEEE 802.1ag is designed for a group of services or some specific network devices to
detect faults on the network. It functions between the following devices:
l
CE and CE
PE and PE
CE and PE
As shown in Figure 3-6, EFM OAM or Ethernet CFM runs between CE1 and PE1, and between
CE2 and PE2; Ethernet CFM runs between PE1 and PE2. Configure the association between
Ethernet OAMs. When a fault occurs on the link between CE1 and PE1, Ethernet CFM sends
alarms of the fault to CE2.
Figure 3-6 Diagram of associating Ethernet OAM with Ethernet OAM
CE1
Issue 01 (2014-01-31)
PE1
PE2
CE2
249
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Reliablity > OAM Management > Ethernet OAM Management > Ethernet Link
OAM > EFM-CFM Binding from the service tree.
Step 3 On the EFM-CFM Binding tab page, click Create.
Step 4 In the Create EFM-CFM Binding dialog box, set binding parameters.
1.
Click the ... button on the right of the Interface Name text box. In the dialog box that is
displayed, select the EFM interface to be bound.
2.
Click the ... button on the right of the MD Name text box. In the dialog box that is displayed,
select the MD and MA to be bound.
3.
4.
Click OK or Apply.
----End
Prerequisites
l
A local Maintenance Association End Point (MEP) must be configured for the current MA.
If an outgoing interface needs to be specified, the interface must meet the following
requirements:
No inward MEP has been configured for it.
Issue 01 (2014-01-31)
250
It has been added to the VLAN that is associated with the current MA.
l
No MD, MA, or MEP has been configured for the intermediate NEs on the link to be tested.
Context
A maximum of 4096 802.1ag-based test diagnosis tasks can be created for an NE.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand Reliablity > OAM Management > Ethernet OAM
Management, and then click Test Diagnosis.
Step 3 On the Test Diagnosis tab page, click the Task Type drop-down button and select Test
Diagnosis Task.
Step 4 Click Create, or right-click in the query result area and select Create on the shortcut menu.
Step 5 Set test diagnosis parameters in the Create Test Diagnosis Task dialog box.
Step 6 Optional: Click Set on the right of Diagnosis Parameter to set test diagnosis parameters.
Alternatively, use the default parameter values.
NOTE
The U2000 provides default values for test diagnosis parameters. Using the default values is recommended.
251
The U2000 creates a test diagnosis task and runs the task based on the set parameters.
In the Running Result area, view the result of diagnosis. After the operation is complete, click
Close to close the dialog box.
----End
Prerequisites
A Maintenance Domain (MD), Maintenance Association (MA), and local MEP must exist.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand Reliablity > OAM Management > Ethernet OAM
Management, and then click Test Diagnosis.
Step 3 On the Test Diagnosis tab page, click the Task Type drop-down button and select Multicast
Test Diagnosis Task.
Step 4 Click Create, or right-click in the query result area and select Create on the shortcut menu.
Step 5 Set test diagnosis parameters in the Multicast General Test Diagnosis Task dialog box.
Step 6 Optional: Click Set on the right of Diagnosis Parameter to set test diagnosis parameters.
Alternatively, use the default parameter values.
Step 7 Click OK.
Step 8 If the Immediate Run check box is selected, the Confirm dialog box is displayed. Click OK.
The U2000 creates a test diagnosis task and runs the task based on the set parameters.
In the Running Result area, view the result of diagnosis. After the operation is complete, click
Close to close the dialog box.
----End
Issue 01 (2014-01-31)
252
Prerequisites
l
The MA binding type must be Map VSI, Map L2VC or Map VLAN.
Context
It is applicable to only 802.1ag-based OAM statistics.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand Reliablity > OAM Management > Ethernet OAM Management
> OAM Measure.
Step 3 Click Create, or right-click in the query result area and select Create on the shortcut menu.
Step 4 Set basic information about OAM statistics.
1.
2.
Click Apply.
Step 5 Optional: If Measure Type is set to Packet loss ratio, set Single Ended Configuration and
Dual Ended Configuration related parameters.
Step 6 Optional: If Measure Type is set to Delay, set One Way Configuration and Two Way
Configuration related parameters.
Step 7 After setting the parameters, click OK or Apply.
----End
Follow-up Procedure
Run OAM measure.
1.
Select a measure job in the query result area, click Run or right-click in the query result
area and select Run on the shortcut menu.
2.
3.
4.
Click Close.
Issue 01 (2014-01-31)
253
Prerequisites
Telnet or STelnet parameters must have been set on the device, and configurations on the device
must have been synchronized to the U2000.
Static LSP or static PW must have been set on the device.
Context
NOTE
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Reliability > OAM Management > MPLS-TP OAM Management > MEG
Management from the service tree.
Step 3 On the MEG Management tab page, click Create, or right-click in the query result area and
choose Create from the shortcut menu.
Step 4 In the Create MEG Management dialog box, set MEG Name.
Step 5 Click OK.
Step 6 On the MEG Management tab page, select the created MEG.
Step 7 In the details area, click the ME Configuration tab and click Create.
Step 8 In the Create ME dialog box, set the related parameters.
Step 9 Click OK.
Step 10 On the MEG Management tab page, select the created ME.
Step 11 On the MEG Management tab page, click Configure, or right-click in the query result area
and choose Configure from the shortcut menu.
Step 12 In the Configure MEG Management dialog box, set the related parameters.
Issue 01 (2014-01-31)
254
Follow-up Procedure
View the delay and packet loss ratio related to the created MEG.
On the MEG Management tab page, select the MEG for which complete information has been
configured and perform one of the following steps:
l
Right-click and choose One Way Delay from the shortcut menu to set the related
parameters and view the one-way delay.
Right-click and choose Single Ended Lost from the shortcut menu to set the related
parameters and view the single-end packet loss ratio.
Right-click and choose Two Way Delay from the shortcut menu to set the related
parameters and view the two-way delay.
Right-click and choose Dual Ended Lost from the shortcut menu to set the related
parameters and view the dual-end packet loss ratio.
Right-click and choose LB Test from the shortcut menu to perform a loopback test.
Issue 01 (2014-01-31)
255
Start
End
For details about the configuration tasks shown in Figure 3-7, see Table 3-1.
Table 3-1 Configuration tasks of the PTP function
Issue 01 (2014-01-31)
Operation
Remarks
256
Start
End
For details about the configuration tasks shown in Figure 3-8, see Table 3-2.
Table 3-2 Configuration tasks of the local PTP clock source
Operation
Remarks
Issue 01 (2014-01-31)
257
Start
End
For details about the configuration tasks shown in Figure 3-9, see Table 3-3.
Table 3-3 Configuration tasks of the BITS clock source
Operation
Remarks
Issue 01 (2014-01-31)
258
Start
End
For details about the configuration tasks shown in Figure 3-10, see Table 3-4.
Table 3-4 Configuration tasks of the physical clock
Operation
Remarks
Issue 01 (2014-01-31)
259
The Apply button is applicable to all the tabs in the PTP clock management window. After the parameters
on all the tab pages of PTP clock management are set, you can click Apply to deploy all PTP parameters
simultaneously.
Prerequisites
l
Configure the static route or IGP to make the routes between NEs reachable.
The PTP clock signal can be normally transmitted on the entire clock synchronization
network only after all NEs on the clock synchronization network are configured with PTP
globally.
All the NEs that are configured with clock synchronization through PTP packets must be
on the same PTP clock domain.
Context
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Clock Management > PTP Clock Management from the service tree.
Step 3 Click General tab.
Step 4 Select the Enable PTP check box. Then, configure the general information about the PTP clock.
Issue 01 (2014-01-31)
260
Prerequisites
l
Configure the static route or IGP protocol to make the IP route between NEs reachable.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Clock Management > PTP Clock Management from the service tree.
Step 3 Click Clock Source tab.
Step 4 Click Local Clock Source tab.
Step 5 Set Clock Source ID and BMC Parameter.
Result
After the local clock source is successfully configured, you can view the configurations of the
PTP function and the BMC running status of equipment on the Local Clock Source tab.
261
Prerequisites
You must complete the following tasks before setting the BITS clock source attributes:
l
Configure the static route or IGP protocol to make the IP route between nodes reachable.
Context
You can apply the following roadmap to configure the BITS clock as the PTP clock source:
l
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Clock Management > PTP Clock Management from the service tree.
Step 3 Click Clock Source tab.
Step 4 Click BITS Clock Source tab.
Step 5 Select the BITS clock to be connected to the device in the BITS clock source list.
Step 6 On the General tab page in the lower part, set Signal Type and Direction.
l If Signal Type is set to 2Mbits/s or 2Mhz, Direction cannot be set.
l If Signal Type is set to 1pps, Direction can be set to in or out.
Step 7 Set Switch to On.
Step 8 In the BMC Parameter area, set the attributes of the BITS signal.
262
Prerequisites
l
Context
You can apply the following roadmap to configure the PTP attributes on an interface:
l
Select an interface.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Clock Management > PTP Clock Management from the service tree.
Step 3 Click Clock Source tab.
Step 4 Click Port Clock Source tab.
Step 5 Click Add. In the dialog box that is displayed, select an interface and then click OK.
Step 6 On the Basic Information tab page in the lower part, set the PTP attributes of the interface.
Step 7 Optional: Set Packet Encapsulation Mode, Interval for Receiving and Sending Packets,
Asymmetry Delay Correction, and TCOC Static Clock Source as required.
NOTE
The TCOC static clock source can be configured only when the clock type is P2PTCOC or E2ETCOC.
Issue 01 (2014-01-31)
263
Prerequisites
l
Configure the static route or IGP to make the routes between NEs reachable.
On the PTP Clock Management tab page, select the Enable PTP Adaptive check box
on the General tab page to configure the adaptive clock.
After the Enable PTP Adaptive check box is selected, you cannot set parameters on the
General and Clock Source tab pages.
All the NEs that are configured with clock synchronization by means of PTP packets must
be on the same PTP clock domain.
On the PTP Clock Management tab page, after the Enable PTP Adaptive check box on
the General tab page is selected and configurations are deployed, the NEs are globally
enabled with PTP automatically.
Context
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Clock Management > PTP Clock Management from the service tree.
Step 3 Click General tab.
Issue 01 (2014-01-31)
264
The Apply button is applicable to all the tabs in the physical clock management window. After the
parameters on all the tab pages of physical clock management are set, you can click Apply to deploy all
parameters simultaneously.
Prerequisites
l
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Clock Management > Physical Clock Management from the service tree.
Issue 01 (2014-01-31)
265
Prerequisites
l
Context
The clock source of a physical clock can be a port clock source or other clock source.
l
Port clock sources are clock source configured on devices. To configure a port clock source,
you need to manually select the desired port and set the mandatory parameters, such as
enabling the clock function and setting the SSM level.
Other clock sources are other clock sources of devices, such as the BITS clock source, PTP
clock source. Such clock sources cannot be created on the NMS. Only the related attributes
can be queried or modified.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Issue 01 (2014-01-31)
266
Step 2 Choose Clock Management > Physical Clock Management from the service tree.
Step 3 Click Clock Source tab.
Step 4 Optional: (If the required port already exists, you do not need to perform this step.) On the Port
Clock Source tab page, click Add. In the dialog box that is displayed, select the required port.
Step 5 Select the required port and set port clock source-related parameters.
Step 6 On the Other Clock Source tab page, click Query to query the attributes of other clock sources.
Step 7 Optional: Select a clock source record. On the General tab page, you can modify the attributes
of the clock source.
Step 8 Click Apply.
----End
Prerequisites
The clock management data must be synchronized to the U2000.
Context
l
In the clock view, the local clock source, external clock source, and clock link can be
displayed according certain filter criteria. Different status icons are used for different types
of local clock source or external clock source use.
Clock link indicates the clock tracking relationship between clock NEs. The clock link
between NE A and NE B refers to the clock signal that NE B tracks from NE A.
When the clock tracking relationship changes, the NMS automatically updates the tracking
relationship in the clock view.
Issue 01 (2014-01-31)
267
Procedure
Step 1 On Workbench, double-click Main Topology.
Step 2 Select Clock View from the Current View drop-down list.
Step 3 Select the NE to be queried or configured from the Object Tree. In the blank area of the clock
view, right-click and choose Search Clock Link from the shortcut menu.
Step 4 In the dialog box that is displayed, select NEs for search and click OK. The clock tracking
relationship of each NE is displayed.
Issue 01 (2014-01-31)
268
----End
Prerequisites
The data of the clock management module must be synchronized to the U2000.
Context
When the clock source switches on the equipment, the U2000 receives the trap messages reported
by NEs and the trap messages are displayed as events on the U2000 alarm panel. In addition,
the clock topology status displayed on the U2000 changes accordingly.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Clock Management > > View Clock Source Switching Records from the service
tree.
Issue 01 (2014-01-31)
269
Step 3 Click Condition. In the Set Filter Condition dialog box, set query conditions, and then click
OK.
NOTE
When querying all records, you can click Query without setting any filtering rule.
Navigation Path
Choose Clock Management > PTP Clock Management from the service tree.Click General
tab.
Button Description
Issue 01 (2014-01-31)
Button
Description
View
Refresh
Query
Apply
270
Button
Description
Synchronize
Parameter Description
Table 3-5 Description of the parameters on the General tab page
Issue 01 (2014-01-31)
Parameter
Description
Settings
Enable PTP
Definition:
Setting method:
Enable adaptive
PTP
Definition:
Setting method:
Clock Domain
Definition:
Setting method:
271
Parameter
Description
Settings
Clock Type
Definition:
Setting method:
Issue 01 (2014-01-31)
272
Parameter
Description
Settings
Enable forcible
port status
configuration
Definition:
Setting method:
Definition:
Setting method:
Clock
Synchronize
Status
Definition:
Delay for
Receiving
BITS1pps Signals
Definition:
Setting method:
Definition:
Setting method:
Table 3-6 Description of the parameters on the View-Current Master Clock tab page
Parameter
Description
Clock Source ID
Definition:
Indicates the ID of the clock source.
Definition:
Indicates the port name of the currently accessed clock
source.
Steps
Definition:
Indicates the number of hops between the current
equipment and the current GrandMaster equipment.
Issue 01 (2014-01-31)
273
Parameter
Description
Definition:
Indicates the type of the clock source. Range:
l Atomic Clock
l GPS
l Terrestrial Radio
l PTP
l NTP
l Handset
l Other
l Internal Oscillator
Clock Accuracy
Definition:
Indicates the accuracy of a clock.
Clock Class
Definition:
Indicates the class of a clock.Defines the TAI tracing
capability of the clock.
Priority 1
Definition:
Indicates that priority of the clock source. The smaller
priority value indicates the higher priority of the clock
source.
Priority 2
Definition:
Indicates that priority of the clock source. The smaller
priority value indicates the higher priority of the clock
source.
Navigation Path
Choose Clock Management > PTP Clock Management from the service tree.Click Clock
Source tab.
Quick Navigation
Issue 01 (2014-01-31)
Tab Page
274
Tab Page
Button Description
Button
Description
Add
Delete
Query
Apply
Synchronize
Parameter Description
Table 3-7 Description of the parameters on the BITS Clock Source tab page
Parameter
Description
Port Name
Definition:
Indicates the port name of the currently accessed BITS clock source.
Status
Definition:
Indicates the available status of the BITS clock source.
Table 3-8 Description of the parameters on the BITS Clock Source-General tab page
Issue 01 (2014-01-31)
Parameter
Description
Settings
Signal Type
Definition:
Setting method:
275
Parameter
Description
Settings
Switch
Definition:
Setting method:
Definition:
Setting method:
Clock Source
Type
l Atomic Clock
l GPS
l Terrestrial Radio
l PTP
l NTP
l Handset
l Other
l Internal Oscillator
Clock Accuracy
Clock Class
Priority 1
Priority 2
Issue 01 (2014-01-31)
Definition:
Setting method:
Definition:
Setting method:
Definition:
Setting method:
Definition:
Setting method:
276
Table 3-9 Description of the parameters on the Port Clock Source tab page
Parameter
Description
Port Name
Definition:
Indicates the port name of the currently accessed clock source.
Port ID
Definition:
Indicates the port number of the currently accessed clock source.
Port Status
Definition:
Indicates the status of a port.
Upstream Clock ID
Definition:
Indicates the ID of the upper layer clock connected to the port.
Upstream Device
Name
Definition:
Upstream Port ID
Definition:
Indicates the name of the upper layer equipment connected to the port.
Definition:
Indicates the port name of the upper layer equipment connected to the
port.
Table 3-10 Description of the parameters on the Port Clock Source-Basic Information tab page
Parameter
Description
Settings
Enable PTP
Definition:
Setting method:
Issue 01 (2014-01-31)
277
Parameter
Description
Settings
Drop Announce
packets
Definition:
Setting method:
Definition:
Definition:
Setting method:
Issue 01 (2014-01-31)
278
Parameter
Description
Settings
Delay Mechanism
Definition:
Setting method:
Port Clock
Configuration
Status
Definition:
Setting method:
Issue 01 (2014-01-31)
279
Parameter
Description
Settings
Clock Step
Definition:
Setting method:
Table 3-11 Description of the parameters on the Port Clock Source-Packet Encapsulation
Mode tab page
Parameter
Description
Settings
Packet
Encapsulation
Mode
Definition:
Setting method:
Issue 01 (2014-01-31)
280
Parameter
Description
Settings
Source IP
Definition:
Setting method:
Enter a value.
Definition:
Setting method:
Enter a value.
Definition:
Setting method:
Priority
Definition:
Setting method:
Definition:
Setting method:
Issue 01 (2014-01-31)
281
Parameter
Description
Settings
Destination MAC
Definition:
Setting method:
Enter a value.
Table 3-12 Description of the parameters on the Port Clock Source-Interval for Receiving and
Sending Packets tab page
Parameter
Description
Settings
Announce
Interval
Definition:
Setting method:
Announce
Receipt Timeout
Period
Definition:
Setting method:
Sync Interval
Definition:
Setting method:
Definition:
Setting method:
Min. PdelayReq
Interval
Issue 01 (2014-01-31)
Specifies the timeout duration for Select a value from the drop-down
receiving Announce packets. If no list.
packet is received in the set
duration, the system considers that
the port cannot receive Announce
packets.
282
Parameter
Description
Settings
Min. DelayReq
Interval
Definition:
Setting method:
Table 3-13 Description of the parameters on the Port Clock Source-Asymmetric Delay
Correction tab page
Parameter
Description
Settings
Asymmetry
Correction Type
Definition:
Setting method:
Asymmetry
Negative Delay
Correction/
Asymmetry
Positive Delay
Correction
Definition:
Setting method:
NOTE
During the calculation of the path
delay and time through the 1588v2
protocol, the delay values of the
paths for receiving and sending
packets are the same and delay is
corrected on this basis. If the delay
values of the paths for receiving and
sending packets are different, you
need to configure the asymmetric
delay correction. In this manner, the
system automatically adds the
asymmetric delay correction to the
path delay calculation.
Table 3-14 Port Clock Source-TCOC Static Clock Source tab page
Issue 01 (2014-01-31)
Parameter
Description
Settings
TCOC Static
Device Name
Definition:
Setting method:
TCOC Static
Clock ID
Definition:
TCOC Static
Clock Port Name
283
Parameter
Description
Settings
TCOC Static
Clock Port
Number
Table 3-15 Description of the parameters on the Port Clock Source-Local Clock Source tab page
Parameter
Description
Settings
Clock Source ID
Definition:
Setting method:
Enter a value.
Definition:
Setting method:
Clock Source
Type
l Atomic Clock
l GPS
l Terrestrial Radio
l PTP
l NTP
l Handset
l Other
l Internal Oscillator
Clock Accuracy
Clock Class
Priority 1
Issue 01 (2014-01-31)
Definition:
Setting method:
Definition:
Setting method:
Definition:
Setting method:
284
Parameter
Description
Settings
Priority 2
Definition:
Setting method:
Navigation Path
Choose Clock Management > PTP Clock Management from the service tree.On the PTP
Clock Management tab page, select the Enable PTP Adaptative check box on the General
tab page, and click the Adaptive Clock tab.
Button Description
Button
Description
Query
Apply
Synchronize
Parameter Description
Table 3-16 Description of parameters on the Adaptive Clock tab page
Parameter
Description
Settings
Definition:
Setting method:
Basic Information
Working Mode
Issue 01 (2014-01-31)
285
Parameter
Description
Settings
Sync Mode
Definition:
Setting method:
Definition:
Setting method:
Clock Domain
Local IP Address
Issue 01 (2014-01-31)
Definition:
Setting method:
Definition:
Setting method:
Enter a value.
286
Parameter
Description
Settings
Working State
Definition:
Issue 01 (2014-01-31)
Announce
Interval
Definition:
Setting method:
Announce
Duration
Definition:
Setting method:
Announce
Receipt Timeout
Definition:
Setting method:
287
Parameter
Description
Settings
Sync Interval
Definition:
Setting method:
Definition:
Setting method:
Sync Duration
Navigation Path
Choose Clock Management > Physical Clock Management from the service tree.Click
General tab.
Button Description
Issue 01 (2014-01-31)
Button
Description
Configure
Query
Apply
Synchronize
288
Parameter Description
Table 3-17 Description of the parameters on the General tab page
Issue 01 (2014-01-31)
Parameter
Description
Settings
Enable Ethernet
Synchronization
Definition:
Setting method:
System Clock
Running Mode
Definition:
Definition:
System Trace
Source Status
Definition:
SSM Control
Definition:
Definition:
Specifies whether
Synchronization Status Message
(SSM) takes part in source
selection. By default, SSM does
not take part in source selection.
Enable Frequency
Check
Definition:
Setting method:
Clock Recovery
Mode
Definition:
Setting method:
Clock Waiting
Recovery Time
Definition:
Setting method:
Map Unk to
Special SSM
Definition:
Setting method:
289
Parameter
Description
Settings
Clock Output
Threshold
Definition:
Setting method:
Max. System
Clock Output
SSM
Definition:
Setting method:
Definition:
Setting method:
Clock Source
Selecting Type
Definition:
Clock Source
Selecting Mode
Definition:
Setting method:
Clock Source
Name
Definition:
Traced Clock
Source
Definition:
Navigation Path
Choose Clock Management > Physical Clock Management from the service tree.Click Clock
Source tab.
Quick Navigation
Issue 01 (2014-01-31)
Tab Page
Port Clock-General
290
Button Description
Button
Description
Add
Delete
Query
Apply
Synchronize
Parameter Description
Table 3-18 Description of the parameters on the Port Clock Source tab page
Parameter
Description
Definition:
Indicates the port name of the clock source.
Definition:
Indicates the status of the clock source.
Table 3-19 Description of the parameters on the Port Clock-General tab page
Parameter
Description
Settings
Enable Clock
Definition:
Setting method:
Definition:
Setting method:
Definition:
Setting method:
Definition:
Setting method:
System Priority
2M-1 Priority
SSM Class
Issue 01 (2014-01-31)
291
Parameter
Description
Settings
SSM Source
Select Mode
Definition:
Setting method:
Table 3-20 Description of parameters on the Other Clock Source tab page
Parameter
Description
Definition:
Indicates the name of the clock source.
Definition:
Indicates the status of the clock source.
Table 3-21 Description of the parameters on the Other Clock Source-General tab page
Parameter
Description
Settings
Enable Clock
Definition:
Setting method:
Definition:
Setting method:
System Priority
Issue 01 (2014-01-31)
Definition:
Setting method:
292
Parameter
Description
Settings
SSM Source
Select Mode
Definition:
Setting method:
Timeslot
Definition:
Setting method:
Definition:
Setting method:
Definition:
Setting method:
Definition:
Setting method:
Clock Type
Direction
TOD Format
Navigation Path
Choose Clock Management > > View Clock Source Switching Records from the service
tree.
Button Description
Issue 01 (2014-01-31)
Button
Description
Condition
Sets the filtering condition so that only the information meeting the
condition can be queried.
Query
Delete
Save As
Saves the query results as files in xls, txt, html, or csv format to a local
disk.
293
Parameter Description
Parameter
Description
Clock Source ID
Definition:
Indicates the ID of the current clock source.
Definition:
Indicates the type of the current clock source. The available options
are PTP Clock and Physical Clock.
Switching Time
Definition:
Indicates the time when switching is performed.
Original Clock
Source ID
Definition:
Indicates the ID of the original clock source.
Prerequisites
Route management data must have been synchronized to the U2000.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Route Management > Global Routing Configuration from the service tree.
Step 3 On the Global Routing Configuration tab page,click View to display the related view windows.
The required global route parameters information is displayed in the related view windows.
Issue 01 (2014-01-31)
294
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Route Management > Routing Information from the service tree.
Step 3 Select the routing information to be queried from the View Routing Information drop-down
list.
NOTE
If viewing the private routing information at the PE end, it need that choose VPN in the Condition area
and input the VPN name.
Prerequisites
Route management data must have been synchronized to the U2000.
Issue 01 (2014-01-31)
295
Context
A static route with both the destination IP address and subnet mask as 0.0.0.0 is a default one.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Route Management > Static Route from the service tree.
Step 3 Click Create. In the dialog box that is displayed, set the related parameters.
In the query result area, Deployment Status indicates whether configurations on the U2000 have been
deployed to NEs. If these configurations have been deployed to NEs, the value of Deployment Status is
Deployed; if these configurations have not been deployed to NEs, the value of Deployment Status is
Undeployed.
----End
296
Prerequisites
Route management data must have been synchronized to the U2000.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Route Management > BGP Instance from the service tree.
Step 3 Click Create, the Create BGP Instance dialog box is displayed.
Step 4 On the General, Router Property, and Address Family tab page, set the related parameters.
Issue 01 (2014-01-31)
297
Issue 01 (2014-01-31)
298
Prerequisites
l
Before configuring basic BGP functions, check that the network-layer IP addresses of
adjacent nodes are reachable.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Route Management > BGP Instance from the service tree.
Step 3 Click Configure, the Configure BGP Instance dialog box is displayed.
Step 4 On the Address Family page tab, click Create, the Create Address Family dialog box is
displayed.
Issue 01 (2014-01-31)
299
Step 7 On the Router, Control Route Information and Advanced page tab, set the related parameters.
NOTE
Route import and route distribution can be configured on the Control Route Information page tab. Load
balance can be configured on the Advanced page tab.
Prerequisites
l
Issue 01 (2014-01-31)
300
Before configuring basic BGP functions, check that the network-layer IP addresses of
adjacent nodes are reachable.
A peer group AS number must be specified only when you create an External BGP (EBGP)
peer group.
Peer groups are classified into three types: internal BGP (IBGP) peer group, pure EBGP
peer group, and hybrid EBGP peer group.
Context
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Route Management > BGP Route > Public Network Route > Peer Group from the
service tree.
Step 3 Click Create.
1.
Click the General tab and set the related parameters on this tab page.
2.
Click the Routing Policy tab and set the related parameters on this tab page.
Issue 01 (2014-01-31)
301
3.
Click the Password Verification tab. Then, set Password Type and enter values in the
New Password and Confirm Password text boxes.
4.
Click the Member tab. Then, click Select. In the Select Peer list box, select the peers to
be added.
5.
Click OK.
In the query result area, Deployment Status indicates whether configurations on the U2000 have been
deployed to NEs. If these configurations have been deployed to NEs, the value of Deployment Status is
Deployed; if these configurations have not been deployed to NEs, the value of Deployment Status is
Undeployed.
----End
Prerequisites
l
Before creating a BGP peer, check that the network-layer IP addresses of adjacent nodes
are reachable.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Route Management > BGP Route > Public Network Route > Peer from the service
tree.
Step 3 Click Create.
1.
Issue 01 (2014-01-31)
Click the General tab and set the related parameters on this tab page.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
302
2.
Click the Routing Policy tab and set the related parameters on this tab page.
3.
Click the Password Verification tab. Then, set Password Type and enter values in the
New Password and Confirm Password text boxes.
In the query result area, Deployment Status indicates whether configurations on the U2000 have been
deployed to NEs. If these configurations have been deployed to NEs, the value of Deployment Status is
Deployed; if these configurations have not been deployed to NEs, the value of Deployment Status is
Undeployed.
----End
Issue 01 (2014-01-31)
303
Prerequisites
l
BGP and an Interior Gateway Protocol (IGP) must have been configured for the selected
NE and be running properly.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Route Management > BGP Route > Public Network Route > Import Route from
the service tree.
Step 3 Click Create. In the dialog box that is displayed, set Protocol, Process ID, MED Value, and
Routing Policy.
Step 4 Click OK to return to the Import Route tab page.
Information about the imported route is displayed in the query result area.
----End
Advertising a Route
This topic describes how to advertise a route, that is, how to statically add a route in the local
routing table to the Border Gateway Protocol (BGP) routing table and advertise it to a peer.
Prerequisites
l
BGP must have been configured for the selected NE and be running properly.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Route Management > BGP Route > Public Network Route > Route Distribution
from the service tree.
Step 3 Click Create. In the dialog box that is displayed, set IP Address, Mask, and Routing Policy.
Step 4 Click OK to return to the Route Distribution tab page.
Information about the advertised route is displayed in the query result area.
----End
Issue 01 (2014-01-31)
304
Prerequisites
l
The Border Gateway Protocol (BGP) and VPN instances must have been configured for
the selected NE and be running properly.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Route Management > VPN Instance Address Family from the service tree.
Step 3 Click Create, the Create VPN Instance Address Family dialog box is displayed.
Step 4 On the General, Router Property, Peer(Group), Control Route Information, and
Advanced tab page, set the related parameters.
NOTE
Route import and route distribution can be configured on the Control Route Information page tab. Load
balance can be configured on the Advanced page tab.
305
Prerequisites
l
The Border Gateway Protocol (BGP) and VPN instances must have been configured for
the selected NE and be running properly.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Route Management > VPN Ipv4 Address Family from the service tree.
Step 3 Click Create, the Create VPN Ipv4 Address Family dialog box is displayed.
Step 4 On the General and Peer(Group) tab page, set the related parameters.
Issue 01 (2014-01-31)
306
Prerequisites
l
Bidirectional Forwarding Detection (BFD) must be enabled globally. If BFD is not enabled
globally and only BFD parameters are set during OSPF process creation, creating BFD
sessions fails. For details about how to enable BFD globally, see BFD ManagementConfiguring Global BFD Attributes.
Context
BFD configured for an OSPF interface has a higher priority than BFD configured for a process.
If interface BFD configurations are different from process BFD configurations, BFD sessions
are created based on parameter settings on the interface.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Route Management > OSPF Route > OSPF Process from the service tree.
Step 3 Click Create. In the dialog box that is displayed, set the related parameters.
1.
On the General tab page, set general parameters for creating an OSPF process.
2.
On the Area tab page, click Create. In the dialog box that is displayed, set the related area
parameters.
Issue 01 (2014-01-31)
307
3.
On the Import Route tab page, click Create and Advanced. In the dialog boxes that are
displayed, set parameters for the route to be imported.
4.
On the Advanced tab page, set parameters such as route filtering, route optimization, and
route aggregation.
5.
In the query result area, Deployment Status indicates whether configurations on the U2000 have been
deployed to NEs. If these configurations have been deployed to NEs, the value of Deployment Status is
Deployed; if these configurations have not been deployed to NEs, the value of Deployment Status is
Undeployed.
----End
308
Prerequisites
l
Bidirectional Forwarding Detection (BFD) must be enabled globally. If BFD is not enabled
globally and only BFD parameters are set during OSPF process creation, creating BFD
sessions fails. For details about how to enable BFD globally, see BFD ManagementConfiguring Global BFD Attributes.
Context
BFD configured for an OSPF interface has a higher priority than BFD configured for a process.
If interface BFD configurations are different from process BFD configurations, BFD sessions
are created based on parameter settings on the interface.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Route Management > OSPF Route > OSPF Interface from the service tree.
Step 3 Click Create. In the dialog box that is displayed, set the related parameters.
1.
On the General tab page, set general parameters for creating an OSPF interface.
2.
309
NOTE
In the query result area, Deployment Status indicates whether configurations on the U2000 have been
deployed to NEs. If these configurations have been deployed to NEs, the value of Deployment Status is
Deployed; if these configurations have not been deployed to NEs, the value of Deployment Status is
Undeployed.
----End
Prerequisites
Route management data must have been synchronized to the U2000.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Route Management > IS-IS Route > IS-IS Process from the service tree.
Step 3 Click Create. In the dialog box that is displayed, set the related parameters.
1.
On the General tab page, set general parameters for creating an IS-IS process.
2.
Optional: On the Import Route tab page, set route import parameters.
Issue 01 (2014-01-31)
310
3.
Issue 01 (2014-01-31)
311
NOTE
In the query result area, Deployment Status indicates whether configurations on the U2000 have been
deployed to NEs. If these configurations have been deployed to NEs, the value of Deployment Status is
Deployed; if these configurations have not been deployed to NEs, the value of Deployment Status is
Undeployed.
----End
Prerequisites
Route management data must have been synchronized to the U2000.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Route Management > IS-IS Route > IS-IS Interface from the service tree.
Step 3 Click Create. In the dialog box that is displayed, set the related parameters.
312
NOTE
In the query result area, Deployment Status indicates whether configurations on the U2000 have been
deployed to NEs. If these configurations have been deployed to NEs, the value of Deployment Status is
Deployed; if these configurations have not been deployed to NEs, the value of Deployment Status is
Undeployed.
----End
Prerequisites
Route management data must have been synchronized to the U2000.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Route Management > IP Prefix from the service tree.
Step 3 Click Create. In the dialog box that is displayed, set the related parameters.
1.
2.
In the IP Prefix Filter Rules area, click Create and set filter rule-related parameters.
Prerequisites
Route management data must have been synchronized to the U2000.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Issue 01 (2014-01-31)
313
Step 2 Choose Route Management > Policy Management from the service tree.
Step 3 Click Create. In the dialog box that is displayed, set the related parameters.
1.
2.
In the Node Information area, click Create and set the matching mode to permit or deny.
Prerequisites
Route management data must have been synchronized to the U2000.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Route Management > BGP Route > Public Network Route > Peer or Route
Management > BGP Route > Private Network Route > VPN Instance Address Family from
the service tree.
Step 3 Choose Route Management > BGP Route > BGP Instance or Route Management > BGP
Route > Address Family any address family node from the service tree.
Step 4 Click Query. All the peer records or VPN instance records are displayed in the query result area.
Step 5 Click Query. Choose one record in the query result area.
Step 6 Right-click a record and choose View Running Information > BGP Peer Group
Information from the shortcut menu.
Step 7 In the Peer Group area on the Peer(Group) tab page, select a peer record, right-click, and
choose View Running Information > BGP Peer Group Information from the shortcut menu.
Step 8 In the BGP Peer Group Information dialog box, set VPN and click Display.
Information about the BGP peer group is displayed in the query result area.
----End
Issue 01 (2014-01-31)
314
Follow-up Procedure
The displayed running information about the BGP peer group can be saved, copied, or searched
as follows:
: saves the information displayed in the query result area to a local disk as a TXT file.
: copies the information selected from the query result area to the clipboard.
: searches for the required information by keyword in the running information displayed in
the query result area.
Prerequisites
Route management data must have been synchronized to the U2000.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Route Management > BGP Route > Public Network Route > Peer or Route
Management > BGP Route > Private Network Route > VPN Instance Address Family from
the service tree.
NOTE
On the VPN Instance Address Family tab page, running information about only BGP peers is displayed.
The reason is that each record in the Virtual Private Network (VPN) instance address family represents a
VPN instance, but the BGP peer log information and BGP peer statistics are based on a single peer.
Step 3 Choose Route Management > BGP Route > BGP Instance or Route Management > BGP
Route > Address Family any address family node from the service tree.
NOTE
On the VPN Instance Address Family tab page, running information about only BGP peers is displayed.
The reason is that each record in the Virtual Private Network (VPN) instance address family represents a
VPN instance, but the BGP peer log information and BGP peer statistics are based on a single peer.
Step 4 Click Query. All the peer records or VPN instance records are displayed in the query result area.
Step 5 Click Query. Choose one record in the query result area.
Step 6 To view information about a BGP peer, right-click a record in the query result area and choose
View Running Information > BGP Peer Information from the shortcut menu.
Step 7 In the Peer area on the Peer(Group) tab page, select a peer record, right-click, and choose View
Running Information > BGP Peer Information, View Running Information > BGP Peer
Log Information, or View Running Information > BGP Peer Statistic Information from the
shortcut menu.
Issue 01 (2014-01-31)
315
Step 8 In the BGP Peer Information dialog box, set VPN and click Display.
Information about the BGP peer is displayed in the query result area.
Step 9 To view log information about a BGP peer, right-click a record in the query result area and
choose View Running Information > BGP Peer Log Information from the shortcut menu.
Step 10 In the BGP Peer Log Information dialog box, click Display.
Log information about the BGP peer is displayed in the query result area.
----End
Follow-up Procedure
The displayed running information about the BGP peer can be saved, copied, or searched as
follows:
: saves the information displayed in the query result area to a local disk as a TXT file.
: copies the information selected from the query result area to the clipboard.
: searches for the required information by keyword in the running information displayed in
the query result area.
Statistics about the BGP peer cannot be saved, copied, or searched.
Prerequisites
Route management data must have been synchronized to the U2000.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Route Management > OSPF Route > OSPF Process from the service tree.
Step 3 To view OSPF summary information, right-click a record in the query result area and choose
View Running Information > OSPF Summary Information from the shortcut menu.
Step 4 In the OSPF Summary Information dialog box, click Display.
OSPF summary information is displayed in the query result area.
NOTE
To view the OSPF summary of a specified process, enter a value in the Process ID text box.
Step 5 To view OSPF LSDB information, right-click a record in the query result area and choose View
Running Information > OSPF LSDB Information from the shortcut menu.
Issue 01 (2014-01-31)
316
Step 6 In the OSPF LSDB Information dialog box, set Link Type and click Display.
OSPF LSDB information is displayed in the query result area.
NOTE
To view the OSPF LSDB information about a specified process, enter a value in the Process ID text box.
Step 7 To view information about a virtual link, right-click a record in the query result area and choose
View Running Information > OSPF Virtual Link Information from the shortcut menu.
Step 8 In the OSPF Virtual Link Information dialog box, click Display.
Information about the virtual link is displayed in the query result area.
NOTE
To view virtual link information about a specified process, enter a value in the Process ID text box.
Step 9 To view error information, right-click a record in the query result area and choose View Running
Information > OSPF Error Information from the shortcut menu.
Step 10 In the OSPF Error Information dialog box, set Error Type and click Display.
OSPF error information is displayed in the query result area.
NOTE
To view error information about a specified process, enter a value in the Process ID text box.
----End
Follow-up Procedure
The displayed OSPF running information can be saved, copied, or searched as follows:
: saves the information displayed in the query result area to a local disk as a TXT file.
: copies the information selected from the query result area to the clipboard.
: searches for the required information by keyword in the running information displayed in
the query result area.
Prerequisites
Route management data must have been synchronized to the U2000.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Route Management > IS-IS Route > IS-IS Process from the service tree.
Issue 01 (2014-01-31)
317
Step 3 To view IS-IS summary information, right-click a record in the query result area and choose
View Running Information > IS-IS Summary Information from the shortcut menu.
Step 4 In the IS-IS Summary Information dialog box, click Display.
IS-IS summary information is displayed in the query result area.
NOTE
To view IS-IS summary information about a specified process, enter a value in the Process ID text box.
Step 5 To view IS-IS summary information, right-click a record in the query result area and choose
View Running Information > IS-IS LSDB Information from the shortcut menu.
Step 6 In the IS-IS LSDB Information dialog box, click Display.
IS-IS LSDB information is displayed in the query result area.
NOTE
To view IS-IS LSDB information about a specified process, enter a value in the Process ID text box and
set Route Level.
----End
Follow-up Procedure
The displayed IS-IS running information can be saved, copied, or searched as follows:
: saves the information displayed in the query result area to a local disk as a TXT file.
: copies the information selected from the query result area to the clipboard.
: searches for the required information by keyword in the running information displayed in
the query result area.
Prerequisites
l
Issue 01 (2014-01-31)
318
Disabling MPLS will delete all existing MPLS configurations from the NE. The MPLS
configurations include global configurations and configurations on interfaces. Exercise
caution with this operation.
If you disable LDP on an NE, all LDP sessions associated with the NE's interfaces are
interrupted and all the LSPs based on these sessions are deleted.
Context
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose MPLS Management > MPLS Configuration > Global MPLS Configuration from
the service tree.
Step 3 Click Synchronize.
In the Confirm dialog box, click OK.
Step 4 In the MPLS area, set the related parameters.
l Setting LSR ID is the prerequisite for setting Enable MPLS.
l The value of LSR ID must be the IP address of a loopback interface on an NE.
l Setting Enable MPLS is the prerequisite for setting other MPLS parameters.
Step 5 In the LDP area, set the related parameters.See Setting LDP Parameters.
Step 6 In the MPLS L2VPN area, set the related parameters.
Setting Enable MPLS L2VPN is the prerequisite for setting Enable OAM Detection for PSN
tunnels or Set the signaling mode of dynamic VCs to Martini.
Follow-up Procedure
To change an LSR ID, do as follows:
Issue 01 (2014-01-31)
319
NOTICE
Disabling MPLS is involved in this operation. Disabling MPLS will delete all existing MPLS
configurations from the NE. The MPLS configurations include global configurations and
configurations on interfaces. Exercise caution with this operation.
1.
Clear the selection of the Enable MPLS check box and click Apply.
2.
Change the value of LSR ID to the required one and click Apply.
Prerequisites
l
MPLS and MPLS LDP must have been enabled for NEs.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose MPLS Management > MPLS Configuration > Global MPLS Configuration from
the service tree. Then, click the LDP tab.
Step 3 Click Synchronize.
Step 4 On the General Information tab page, perform the following steps:
l In the LDP Dynamic Announcement area, set the related parameters.
l In the IGP LSP Trigger Policy area, set the related parameters.
l In the Enable Auto FRR area, set the related parameters.
l In the Backoff area, set the related parameters.
l In the Enable LDP MTU Signal area, set the related parameters.
l In the Enable Graceful Restart area, set the related parameters.
l In the LDP LSP Router Longest Match area, set the related parameters.
Issue 01 (2014-01-31)
320
Step 5 Click the Peer Information tab and perform the following steps:
l In the LDP Remote Peer area, set the related parameters.
1.
2.
3.
4.
In the dialog box that is displayed, set basic parameters and key communications
parameters for the remote peer.
5.
To modify existing parameters of a remote peer, select the remote peer and click Configure.
Issue 01 (2014-01-31)
321
2.
In the dialog box that is displayed, configure peer policies for all peers.
2.
In the dialog box that is displayed, set basic peer parameters and other peer-related
parameters.
3.
To modify existing parameters of a peer, select the peer and click Configure.
2.
In the dialog box that is displayed, set basic peer group parameters and other peer
group-related parameters.
3.
To modify existing parameters of a peer group, select the peer group and click Configure.
Issue 01 (2014-01-31)
322
Prerequisites
l
The MPLS data of the NE must have been synchronized to the U2000.
The MPLS, LDP, and MPLS TE capabilities must have been enabled for the NE.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose MPLS Management > MPLS Configuration > Global MPLS Configuration from
the service tree. Then, click the MPLS TE tab.
Step 3 Click Synchronize.
Step 4 In the RSVP-TE area, set the related parameters.
Enable RSVP-TE before setting RSVP-TE parameters.
Step 5 Optional: In the RSVP-TE Hello area, set the related parameters.
Parameters in this area are extended RSVP-TE parameters. Setting these parameters helps to
detect reachability of RSVP neighboring nodes rapidly and support high-availability switchover
of RSVP-TE tunnels. If basic RSVP-TE configurations meet requirements, this step is optional.
1.
Select the Enable RSVP-TE Hello check box, and set Hello Loss Times and Hello
Refresh Interval.
2.
Issue 01 (2014-01-31)
323
After selecting the RSVP-TE GR check box, you can set GR Basic Time as required.
3.
In the Hello Session area, click Create. In the dialog box that is displayed, set LSR ID and
click OK.
2.
3.
Issue 01 (2014-01-31)
324
Select the Reservation Confirmation check box to enable the reservation confirmation
mechanism.
2.
3.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Issue 01 (2014-01-31)
325
Step 2 Choose MPLS Management > MPLS Configuration > MPLS Interface from the service tree.
Step 3 Right-click in the blank area and choose Enable MPLS from the shortcut menu.
Step 4 In the dialog box that is displayed, select required interfaces.
NOTE
In this dialog box, you can also perform the following operations:
l Create some logical interfaces.
l Create some subinterfaces.
l Set interface details.
l Synchronize the data of the interface module.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose MPLS Management > MPLS Configuration > MPLS Interface from the service tree.
Step 3 Select an MPLS interface and click Configure.
NOTE
If the interface list is empty or the desired interface is not displayed in the list, enable MPLS for related
interfaces by referring to Enabling MPLS on Interfaces.
Issue 01 (2014-01-31)
326
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose MPLS Management > MPLS Configuration > MPLS Interface from the service tree.
Step 3 Select an MPLS interface and click Configure.
NOTE
If the interface list is empty or the desired interface is not displayed in the list, enable MPLS for related
interfaces by referring to Enabling MPLS on Interfaces.
Issue 01 (2014-01-31)
327
In the Hello Packet Hold Time text box, enter a desired value.
2.
In the Hello Packet Sending Time text box, enter a desired value.
3.
In the Keepalive Packet Hold Time text box, enter a desired value.
4.
In the Keepalive Packet Sending Time text box, enter a desired value.
5.
Select a desired value from the LDP Transport Address drop-down list.
If Specific is selected, click the ... button and select an interface.
2.
Issue 01 (2014-01-31)
Select the Enable LDP Synchronization check box to enable LDP and IS-IS
synchronization.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
328
b.
c.
Select a desired value from the Maximum Hold Cost drop-down list.
If Specific is selected, enter the maximum hold cost in the text box.
3.
Select the Enable LDP Synchronization check box to enable LDP and IS-IS
synchronization.
b.
c.
Select a desired value from the Maximum Hold Cost drop-down list.
If Specific is selected, enter the maximum hold cost in the text box.
Click Create. In the dialog box that is displayed, perform the following steps:
a.
In the Next Hop text box, enter the IP address of the next hop.
b.
c.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose MPLS Management > MPLS Configuration > MPLS Interface from the service tree.
Step 3 Select an MPLS interface and click Configure.
NOTE
If the interface list is empty or the desired interface is not displayed in the list, enable MPLS for related
interfaces by referring to Enabling MPLS on Interfaces.
Issue 01 (2014-01-31)
329
2.
The ATN equipment only support set the Link Bandwidth BC0.
3.
4.
Optional: In the Flooding Threshold area, set Up Threshold of Flooding and Lower
Threshold of Flooding.
Setting the flooding thresholds helps to prevent frequent flooding from causing bandwidth
waste. If the flooding thresholds are not set or the set flooding thresholds do not meet service
requirements, set parameters in the Flooding Threshold area.
5.
Select an Auto FRR type from the Auto FRR drop-down list.
The parameters in the Enable RSVP-TE area are available only after MPLS TE is enabled.
1.
Issue 01 (2014-01-31)
a.
Select the Enable RSVP-TE Hello check box to enable the extended RSVP Hello
mechanism on interfaces.
b.
Select the Enable Summary Refreshing check box to enable the summary refreshing
function on interfaces.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
330
c.
2.
Select a key type from the RSVP-TE Authentication Key Type drop-down list.
b.
Prerequisites
l
MPLS TE and MPLS RSVP-TE must be enabled on the related NE and interface.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose MPLS Management > Tunnel Configuration from the service tree.
Step 3 On the Tunnel Configuration tab page, click Query to display all tunnels.
Step 4 Right-click in the query result area and choose Create from the shortcut menu.
Step 5 In the Create Tunnel dialog box, click the General Information tab and then set the general
parameters of the tunnel service.
NOTE
l The parameters on the General Information tab page are mandatory, whereas the parameters on other
tab pages are optional.
l If the selected NE does not support a certain feature, the parameters about this feature become
unavailable.
Issue 01 (2014-01-31)
331
NOTE
If Signaling Type is set to Static CR, you can click Configure Static LSP to configure static tunnels. For
details, see 3.11.4 Creating a Static LSP Segment.
332
Prerequisites
l
Context
Static LSP segments are classified into two types: static LSP segments and static CR-LSP
segments.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose MPLS Management > Static LSP Segment from the service tree.
Step 3 In the query condition area, click Query to display all static LSP segments.
Step 4 Right-click in the query result area and choose Add from the shortcut menu.
Step 5 In the dialog box that is displayed, set basic parameters for the static LSP segment.
Step 6 Click the Forward tab and set parameters for the forward LSP.
Step 7 Optional: Click the Backward tab and set parameters for the backward LSP. To create a
bidirectional static LSP, set parameters on this tab page.
Step 8 Click Apply or OK.
----End
Issue 01 (2014-01-31)
333
Prerequisites
l
Context
The protection group is used in the following scenarios:
l
When a fault occurs in the working tunnel, the MPLS OAM mechanism or another detection
mechanism switches traffic to the tunnel in the protection group after detecting the fault.
Manually switch traffic from the working tunnel to the tunnel in the protection group.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose MPLS Management > Protection Management from the service tree.
Step 3 Right-click in the query result area and choose Create from the shortcut menu.
You can also click Create on the Protection Management tab page.
Step 4 In the Create Protection Group dialog box, set the related parameters as required.
NOTE
When Protection Type is set to 1:1 and Switching Type is set to Double-Ended, the working and
protection tunnels must be configured as bidirectional tunnels.
Issue 01 (2014-01-31)
334
Prerequisites
l
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose MPLS Management > MPLS Detection > LDP Session from the service tree.
Step 3 On the LDP Session tab page, click Query.
The information about the sessions among the LDP peers is displayed in the query result area.
----End
Prerequisites
The MPLS data of the NE must be synchronized to the U2000.
Context
l
The label FIB can be viewed only when the protocol type is STATIC, STATIC-CR,
LDP, or RSVP-TE.
Label FIB stands for the label forwarding information base. The core LSR uses the label
FIB to forward labeled packets.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Issue 01 (2014-01-31)
335
Step 2 Choose MPLS Management > MPLS Detection > Label FIB from the service tree.
Step 3 Click Query in the query condition area.
Query results are displayed according to set filter criteria.
Step 4 Select the label FIB to be viewed.
On the General tab page of the details area, the details about this label FIB are displayed.
----End
Counting LSPs
This topic describes how to count different types of LSPs on the current equipment.
Prerequisites
The MPLS data of the equipment must be synchronized to the U2000.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose MPLS Management > MPLS Detection > LSP Statistic from the service tree.
Step 3 Click Collect.
Step 4 Select a collection result.
On the General tab page of the details area, the information such as the type and number of
currently collected LSPs is displayed.
----End
Prerequisites
The MPLS data of the NE must be synchronized to the U2000.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose MPLS Management > TE Tunnel Configuration from the service tree.
Step 3 On the TE Tunnel Configuration tab page, click Query to display all tunnels.
Issue 01 (2014-01-31)
336
Step 4 Select the tunnel to be tested, right-click, and then choose LSP Ping or LSP Trace from the
shortcut menu.
Step 5 In the dialog box that is displayed, set related parameters.
Issue 01 (2014-01-31)
337
Issue 01 (2014-01-31)
338
----End
Prerequisites
The MPLS data of the NE must be synchronized to the U2000.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose MPLS Management > TE Tunnel Configuration from the service tree.
Step 3 On the TE Tunnel Configuration tab page, click Query to display all tunnels.
Step 4 Right-click the tunnel to be reset and choose Reset from the shortcut menu.
Step 5 In the Confirm dialog box, click OK.
If the resetting is successful, the status bar prompts that the MPLS TE tunnel is successfully
reset.
----End
339
tunnel in advance and bandwidth is assigned to the protection tunnel. The working tunnel and
the protection tunnel form a protection group. If the working tunnel fails, data traffic is rapidly
switched to the protection tunnel.
Prerequisites
The MPLS data of the NE must be synchronized to the U2000.
Context
You can switch a protection group in either of the following modes:
l
Clear: It is used to cancel the request of manually configuring switchover for the protection
group.
Switch: It is used to manually switch traffic from the working tunnel to the protection tunnel,
or conversely, from the protection tunnel to the working tunnel.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose MPLS Management > Protection Management from the service tree.
Step 3 On the Protection Management tab page, click Query.
Step 4 Right-click the protection group to be switched and choose Switch > Manually Switch from
the shortcut menu. Select the switching mode as required.
If the OAM protection group is successfully switched, the current operation is displayed in the
Switch Status column of the list, and the switching result is displayed in the Switch Result
column. If the switching of the OAM protection group fails, the system prompts failure causes.
----End
340
2.
3.
4.
Run the following command to set the name of the read community:
snmp-agent community read community-name [ [ mib-view view-name ] | [ acl aclnumber ] ]*
5.
Run the following command to set the name of the write community:
snmp-agent community write community-name [ [ mib-view view-name ] | [ acl aclnumber ] ]*
6.
Run the following command to add the ISO subtree to the view:
snmp-agent mib-view included view-name iso
7.
After the LLDP alarm function is enabled, any of the following situation will trigger the equipment
to send alarm information to the U2000:
l The global LLDP function is disabled.
l The LLDP management address is changed.
l The neighbor information is changed. (No alarm information is generated on the local end if the
neighbor management address is changed.)
2.
3.
4.
5.
Run the following command to add a user to the SNMPv3 user group:
snmp-agent usm-user v3 user-name group-name [ [ authentication-mode { md5 | sha }
password ] [ privacy-mode des56 password ] ] [ acl acl-number ]
6.
Run the following command to add the ISO submap to the MIB view:
snmp-agent mib-view included view-name iso
7.
Issue 01 (2014-01-31)
341
NOTE
After the LLDP alarm function is enabled, any of the following situation will trigger the equipment
to send alarm information to the U2000:
l The global LLDP function is disabled.
l The LLDP management address is changed.
l The neighbor information is changed. (No alarm information is generated on the local end if the
neighbor management address is changed.)
Prerequisites
l
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose System Management > LLDP Management > LLDP Global Configuration from
the service tree.
Step 3 Set parameters such as Management IP Address, Interval for Message Transmission, and
Message Multiple.
NOTE
Unless necessary, keep the default parameter settings unchanged because modifying the settings may
increase the load of the system.
342
Prerequisites
l
By default, the LLDP function on interfaces is enabled after the global LLDP function is enabled.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose System Management > LLDP Management > LLDP Interface Configuration from
the service tree.
Step 3 On the LLDP Interface Configuration tab page, click Query. The interfaces supporting LLDP
after LLDP is globally enabled are displayed in a list.
Step 4 Right-click one or more interfaces that run LLDP and choose Enable or Disable from the
shortcut menu to apply the interface configurations to the equipment.
l If the status of the interfaces is Enabled, you can choose only Disable from the shortcut
menu.
l If the status of the interfaces is Disabled, you can choose only Enable from the shortcut
menu.
l If both Enabled and Disabled interfaces are selected, you can choose either Enable or
Disable from the shortcut menu. Then, the status of all the interfaces becomes the same as
the selected status.
----End
Prerequisites
The related parameters must be set on the equipment.
Procedure
Step 1 Right-click the NE in the Main Topology and choose Synchronize NE Data from the shortcut
menu.The LLDP neighbor information on the equipment is synchronized.
Issue 01 (2014-01-31)
343
----End
Prerequisites
The data of the BFD management must be synchronized to the U2000.
Context
l
If BFD is disabled, all BFD configurations will be deleted. Be cautions to disable BFD.
To dynamically create LDP LSP service detection, you must set global MPLS BFD
parameters.
Issue 01 (2014-01-31)
344
LSPs are unidirectional. On an LSP, after the active party (the source end) creates a
BFD session and then sends an LSP ping packet, the passive party (the sink end) can
automatically create a BFD session only after receiving the LSP ping packet. The
passive party of an LSP is capable of automatically creating BFD sessions only when
the sink end of the LSP is enabled with the function of dynamically creating BFD
sessions. If this function is not enabled, the passive party cannot automatically create
BFD sessions.
A BFD session is not created immediately after this function is enabled. Instead, it is
created after the sink end receives the BFD TLV-carried LSP ping request packet sent
from the source end.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Reliablity > BFD Management > BFD Global from the service tree.
Step 3 On the BFD Global tab page, set the parameters.
NOTE
l If single-hop BFD detection needs to be performed on the Layer 2 interfaces or the Layer 3 physical
interfaces without IP addresses, such as the IP-Trunk member interface and Layer 3 Eth-Trunk member
interface, adopt the default multicast IP address.
l You can set Default multicast address only when Enable BFD is set to Enable.
l If BFD Bind Type is set to Default multicast address, Default multicast address on the BFD
Global tab page cannot be modified.
Issue 01 (2014-01-31)
345
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Reliablity > BFD Management > BFD Global TTL Configuration from the service
tree.
Step 3 Click Create.
NOTE
You can also right-click in the query result area and choose Create from the shortcut menu.
Step 4 In the Create BFD Global TTL Configuration dialog box, set Peer IP, Mask Length, Session
Type, and TTL Value.
Prerequisites
l
Issue 01 (2014-01-31)
346
Context
Service detection supporting this function includes link detection, TE detection, VRF detection,
and PW detection.
The procedures for enabling and disabling the administrative status are similar for all types of
service detection. The following takes link detection as an example to describe the procedure.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Reliablity > BFD Management > Service Detection Configuration > Link Detection
Configuration from the service tree.
Step 3 Click Query.
Step 4 Select one or more BFD configuration records in the query result area.
Step 5 Right-click the selected records and choose Enable Administrative Status or Disable
Administrative Status from the shortcut menu.
NOTE
Batch operation is supported. If you select multiple BFD configuration records, a progress bar is displayed
showing the progress of enabling or disabling the administrative status. Finally, the operation result is
displayed in the Prompt dialog box.
You need to perform this operation only when multiple BFD configuration records are selected for enabling
or disabling the administrative status of service detection.
----End
Prerequisites
l
Optional: The data of the interface information module must be synchronized to the
U2000.
NOTE
If Interface does not need to be bound to a local interface for configuring link detection,
synchronization of interface module information is not required.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Issue 01 (2014-01-31)
347
Step 2 Choose Reliablity > BFD Management > Service Detection Configuration > Link Detection
Configuration from the service tree.
Step 3 Click Create.
NOTE
You can also right-click in the query result area and choose Create from the shortcut menu.
Step 4 In the Create Link Detection Configuration dialog box, set the related parameters.
Prerequisites
l
The data of the VSI management module must be synchronized to the U2000.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Reliablity > BFD Management > Service Detection Configuration > VSI PW
Detection Configuration from the service tree.
Step 3 Click Create.
l
Issue 01 (2014-01-31)
To create BFD detection for management VSIs, select Create Management VSI
Detection Task. In the dialog box that is displayed, set parameters.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
348
To create BFD detection for service VSIs, select Create Service VSI Detection Task. In
the dialog box that is displayed, set parameters.
349
Prerequisites
l
Before you configure BFD to detect an MPLS TE tunnel, the related tunnel interface must
be configured.
BFD can detect only the TE tunnel whose signaling type is CR-Static or RSVP-TE.
If the TE tunnel detected by BFD is in Down state and it can apply the OAM resource, a
BFD session can be established but cannot be Up.
One tunnel may have multiple LSPs. In the case where a tunnel is detected through a BFD
session, the BFD session becomes Down only when all the related LSPs are faulty.
Context
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Reliablity > BFD Management > Service Detection Configuration > MPLS TE
Detection Configuration from the service tree.
Step 3 Click Create.
NOTE
You can also right-click in the query result area and choose Create from the shortcut menu.
Step 4 In the Create MPLS TE Detection Configuration dialog box, set the related parameters.
350
Prerequisites
l
The data of the interface management module must be synchronized to the U2000.
The data of the VRF management module must be synchronized to the U2000.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Reliablity > BFD Management > Service Detection Configuration > VRF Detection
Configuration from the service tree.
Step 3 Click Create.
NOTE
You can also right-click in the query result area and choose Create from the shortcut menu.
Step 4 In the Create VRF Detection Configuration dialog box, set the related parameters.
Configuring PW Detection
This topic describes how to configure PW detection. The setup of BFD sessions based on PWs
helps to detect the link status of PWs between the local and remote PEs, thus reducing the impact
of link faults on services. You need to configure BFD sessions to detect the primary and
secondary PWs respectively.
Issue 01 (2014-01-31)
351
Prerequisites
l
The data of the interface management module must be synchronized to the U2000.
The VC of the PW to be detected must be created through the control word method.
During PW detection, BFD must work in asynchronous mode. ATN only supports the
asynchronous mode. In addition, BFD sessions must be established at the local and peer
ends of the PW by binding the PW.
If the PW can apply the OAM resource, When the PW is in Down state, a BFD session can
be established but cannot be Up.
Context
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Reliablity > BFD Management > Service Detection Configuration > PW Detection
Configuration from the service tree.
Step 3 Click Create.
l
Select Create Static BFD from the drop-down list. In the Create PW Detection
Configuration dialog box, set the related parameters.
Select Create Dynamic BFD from the drop-down list. In the Create PW Detection
Configuration dialog box, set the related parameters.
Issue 01 (2014-01-31)
352
Prerequisites
l
The data of the route management module must be synchronized to the U2000 and IS-IS
processes and IS-IS interfaces must be configured.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Reliablity > BFD Management > Service Detection Configuration > IS-IS Detection
Configuration from the service tree.
Step 3 On the IS-IS Detection Configuration tab page, click the IS-IS Process Configuration tab.
Step 4 Click Create.
Step 5 In the Create IS-IS Process Detection dialog box, set the related parameters.
Issue 01 (2014-01-31)
353
Prerequisites
l
The data of the route management module must be synchronized to the U2000 and IS-IS
processes and IS-IS interfaces must be configured.
Context
You can create IS-IS interface BFD detection in the following cases:
l
BFD needs to be configured on only certain interfaces rather than all the IS-IS processes
of an interface.
IS-IS process BFD detection is configured but certain interfaces must use different BFD
sessions parameters to quickly discover link faults.
Issue 01 (2014-01-31)
354
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Reliablity > BFD Management > Service Detection Configuration > IS-IS Detection
Configuration from the service tree.
Step 3 On the IS-IS Detection Configuration tab page, click the IS-IS Interface Configuration tab.
Step 4 Click Create.
Step 5 In the Create IS-IS Interface BFD Detection dialog box, set the related parameters.
Prerequisites
l
The data of the route management module must be synchronized to the U2000 and BGP
peers or BGP peer groups must be configured.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Reliablity > BFD Management > Service Detection Configuration > BGP Detection
Configuration from the service tree.
Step 3 Click Create.
Step 4 In the Create BGP Detection dialog box, set the related parameters.
NOTE
In the BGP Peer Configuration area, click Create and then set the related parameters to create a peer.
Issue 01 (2014-01-31)
355
Prerequisites
l
The MPLS capability must be enabled and MPLS LDP must be configured on the NE.
The sink end of the LSP must be enabled with the function of dynamically creating BFD
sessions.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Reliablity > BFD Management > Service Detection > LDP LSP Detection
Configuration from the service tree.
Issue 01 (2014-01-31)
356
Prerequisites
l
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Reliablity > BFD Management > Service Detection Configuration > OSPF
Detection Configuration from the service tree.
Step 3 Click Synchronize.
Information about BFD sessions configured on OSPF interfaces is displayed in the details area.
----End
357
Prerequisites
l
Context
If a set of equipment does not exist in the service tree, it indicates that the equipment does not
support this feature.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose QoS Management > Discard Policy from the service tree.
Step 3 Right-click on the Discard Policy tab page and then choose Create from the shortcut menu, or
click Create on the Discard Policy tab page.
Step 4 In the Create Discard Policy dialog box, set the related parameters.
1.
2.
Issue 01 (2014-01-31)
358
3.
You can modify the lower limit, upper limit, and discard probability of the discard policy.
4.
Click OK or Apply.
----End
Prerequisites
l
Context
Each flow queue can be bound to a discard policy. If a flow queue is not bound to any discard
policy, packets are discarded in tail drop mode when the flow queue is full. To bind a flow queue
to a discard policy, create the discard policy before creating the queue profile.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand QoS Management > HQoS, and then click Flow Queue Policy.
Step 3 Right-click on the Flow Queue Policy tab and then select Create on the shortcut menu, or click
Create on the Flow Queue Policy tab.
1.
2.
Click Default to reset all the parameters of the flow queue policy to default values.
Issue 01 (2014-01-31)
359
3.
Step 4 In the Modify Flow Queue Policy Parameter dialog box, Click OK.
Step 5 In the Create Flow Queue Policy dialog box, Click OK or Apply.
----End
Prerequisites
l
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand QoS Management, and then click QoS Profile.
Step 3 Right-click on the QoS Profile tab and then select Create on the shortcut menu, or click
Create on the QoS Profile tab.
Step 4 In the Create QoS Profile dialog box, enter the name of a QoS profile to be created.
Issue 01 (2014-01-31)
360
Step 5 Optional: Select the User Queue check box, and then set the parameter about User Queue.
Step 6 Optional: Or select the User CAR check box, and then set the parameter about User CAR.
Step 7 Click OK or Apply.
----End
Prerequisites
l
Context
If a device does not exist in the service tree, it indicates that the device does not support this
configuration.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand QoS Management, and then click DS Domain Policy.
Step 3 Right-click on the DS Domain Policy tab and then select Create on the shortcut menu, or click
Create on the DS Domain Policy tab.
Step 4 Enter the name of the DS domain policy to be created.
Issue 01 (2014-01-31)
361
Prerequisites
l
Interfaces of devices support the configurations of GTS parameters for the interface QoS.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand QoS Management, and then click Configure Interface QoS.
Step 3 On the Configure Interface QoS tab, click Query to display the attributes of all interfaces.
Step 4 Select an interface QoS record, and then click the GTS tab.
Step 5 Select the GTS check box, and then set the values of PIR.
Step 6 Click Apply.
----End
Prerequisites
l
The related device interface supports the deployment of applying policies for interface QoS.
Issue 01 (2014-01-31)
362
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand QoS Management, and then click Configure Interface QoS.
Step 3 On the Configure Interface QoS tab, click Query to display the attributes of all interfaces.
Step 4 Select an interface QoS record, and then click the Applying Policy tab.
Step 5 Click Deploy.
Set the related parameters.
Prerequisites
l
The related device interface supports configuring the diffServ for interface QoS.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose QoS Management > Configure Interface QoS from the service tree.
Step 3 In the Configure Interface QoS window, click Query, attribute of all the interfaces is displayed.
Step 4 Select an interface QoS record, and then click the DiffServ tab.
Step 5 Select the Enable DiffServ check box and then do as follows:
l Set DiffServ Mode. At present, only Pipe is available.
l Set Service Class for packets sent from this interface.
Step 6 Click Apply.
----End
Issue 01 (2014-01-31)
363
Prerequisites
The configurations of QoS management are synchronized to the U2000.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand QoS Management, and then click Configure Interface QoS.
Step 3 In the Configure Interface QoS window, click Query, attribute of all the interfaces is displayed.
Step 4 Select an interface QoS record and click the Other tab. Then, set the related parameters including
Enable 802.1p, Disable PHB, or IP URPF.
Step 5 Click Apply.
----End
Prerequisites
l
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand QoS Management, and then click Configure Interface QoS.
Step 3 On the Configure Interface QoS tab page, click Query to display the attributes of all interfaces.
Step 4 Right-click an interface record and choose Configure Performance Monitoring from the
shortcut menu.
----End
Prerequisites
l
Issue 01 (2014-01-31)
364
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand QoS Management, and then click Configure Interface QoS.
Step 3 On the Configure Interface QoS tab page, click Query to display the attributes of all interfaces.
Step 4 Right-click an interface record and choose Monitor Real-time Performance from the shortcut
menu.
----End
Prerequisites
l
Context
Generating a DS domain policy profile is taken as an example here.
The QoS features that support generation of QoS profiles are as follows:
l
HQoS
Flow Queue Policy
Discard Policy
QoS Profile
DS Domain Policy
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose QoS Management > DS Domain Policy from the service tree.
Step 3 Select a DS domain policy, right-click, and choose Build Global Profile from the shortcut menu.
The Progress Control dialog box is displayed, indicating whether the operation is successful.
Step 4 Click Detail to view the detailed operation result. Click Close to close the dialog box.
----End
Follow-up Procedure
1.
Issue 01 (2014-01-31)
Choose Configuration > IP QoS Profile > DS Domain Profile from the main menu.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
365
2.
Then, you can view the generated global profile whose name is the same as that in original
QoS configurations.
Context
l
By default, the system provides three authentication schemes, that is, default for LocalRADIUS authentication, default0 for non-authentication, default1 for RADIUS
authentication. They can be modified but cannot be deleted.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand User Access > BRAS Management > AAA Management, and then
click Authentication Scheme.
Step 3 Right-click in the list and select Create on the shortcut menu.
Step 4 Set the parameters in the dialog box that is displayed.
366
Context
l
By default, the system provides two accounting schemes, that is, default0 and default1.
They can be modified but cannot be deleted.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand User Access > BRAS Management > AAA Management, and then
click Accounting Scheme.
Step 3 Right-click in the list and select Create on the shortcut menu.
Step 4 Set the parameters in the dialog box that is displayed.
Context
l
By default, the system provides an authorization scheme named default. You can modify
the default authorization scheme but you cannot delete it.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand User Access > BRAS Management > AAA Management, and then
click Authorization Scheme.
Step 3 Right-click in the list and select Create on the shortcut menu.
Issue 01 (2014-01-31)
367
Context
The ATN equipment manages RADIUS server through RADIUS server groups. A RADIUS
server group is a set of RADIUS servers that have the same attributes (excluding the IP addresses
and port numbers) and working in primary/secondary mode. The ATN equipment supports a
maximum of 16 RADIUS server groups.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand User Access > BRAS Management > AAA Management, and then
click RADIUS Group.
Step 3 Right-click in the list and select Create on the shortcut menu.
Step 4 Set the related parameters.
NOTE
On the Server Information tab page, set the related parameters. Then, click Save. To delete the server
information, click Clear.
Context
The HWTACACS protocol is a security protocol developed on the basis of TACACS (RFC
1492). Compared with RADIUS, HWTACACS features more reliable transmission and
encryption, and is more suitable for security control.
Issue 01 (2014-01-31)
368
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand User Access > BRAS Management > AAA Management, and then
click TACACS Templet.
Step 3 Right-click in the list and select Create on the shortcut menu.
Step 4 Set the parameters in the dialog box that is displayed.
NOTE
On the Server Information tab page, set the related parameters. Then, click Save. To delete the server
information, click Clear.
Context
By default, the system provides one default domain, that is, default_admin. This domain is used
for the users whose management domains cannot be identified. The default domain can be
modified but cannot be deleted.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the service tree, expand User Access > BRAS Management > AAA Management, and then
click User Domain.
Step 3 Right-click in the list and select Create on the shortcut menu.
Step 4 Set the related parameters.
Issue 01 (2014-01-31)
369
Prerequisites
l
Interface configurations must have been synchronized. Tunnel interface and tunnels must
have been configured for NEs and run properly. That is, tunnels can send and receive
packets properly and tunnel interface are in the Up state.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Issue 01 (2014-01-31)
370
Step 2 Choose VPN Management > Tunnel Policy Management from the service tree.
Step 3 Click Create, and set the name and tunnel policy type.
NOTE
The types of tunnel policies are Bind Application to Tunnel and Tunnel Selection Sequence. The two
are mutually exclusive.
Step 4 After completing the settings, click OK to return to the Tunnel Policy Management tab page.
The new tunnel policies will be displayed in the query result area.
----End
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose VPN Management > PW Template Management from the service tree.
Step 3 Click Create and set the related parameters.
371
3.16.3 Creating a PW
This topic describes how to create a management PW, a service PW and an SPW on a per-NE
basis on a PE.
Creating a Service PW
This topic describes how to create a service PW. A PW is a virtual connection between two PEs
and is used to transmit frames between the PEs. You can create a static or dynamic PW, and you
also can creat a static or dynamic PW in the primary/secondary relationship.
Prerequisites
Before configuring a static PW, you must do as follows:
l
Configure IGP for PEs and Ps on the MPLS backbone network to implement IP connectivity
of the backbone network.
Establish the tunnel of a corresponding type between the PEs according to the applied tunnel
policy.
When the CE access type is VLAN, configure subinterfaces on PEs; when the CE access
type is ATM, configure VCs on PEs.
Configure IGP for PEs and Ps on the MPLS backbone network to implement IP connectivity
of the backbone network.
Establish the tunnel of a corresponding type between the PEs according to the applied tunnel
policy.
When the CE access type is VLAN, configure subinterfaces on PEs; when the CE access
type is ATM, configure VCs on PEs.
Configure IGP for PEs and Ps on the MPLS backbone network to implement IP connectivity
of the backbone network.
Establish the tunnel of a corresponding type between the PEs according to the applied tunnel
policy.
Establish tunnels used by the primary and secondary PWs between PEs in the primary and
bypass paths, including the CR-LSP, LSP, and GRE tunnels.
If the tunnel is a GRE or CR-LSP tunnel, configure a tunnel policy. If the tunnel is an LSP
tunnel, configure a tunnel policy.
Issue 01 (2014-01-31)
372
NOTE
l One interface cannot be configured as the AC interface of an L2VPN and as the AC interface of an
L3VPN at the same time. When an interface is bound to an L2VPN, all the Layer 3 features configured
on the interface, such as the IP address and routing protocol, are invalid.
l PWE3 does not support P2MP. When you create an MPLS L2VC on an ATM subinterface, the ATM
subinterface must be the end-to-end type. For the configuration of the transparent transmission of ATM
cells, however, the restriction is not applicable.
l You can configure the primary and secondary static PWs or dynamic PWs. The types of the primary
and secondary PWs must be consistent. That is, the encapsulation types of the primary and secondary
PWs must be consistent.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose VPN Management > PW Management from the service tree.
Step 3 On the PW Management tab page, click Create and select Service PW from the drop-down
list.
1.
Click the Interface Configuration tab, and then set the values of Interface Name and
Signaling Mode.
2.
Issue 01 (2014-01-31)
373
NOTE
The following takes the Dynamic signaling as an example. The parameters to be configured on the
General tab page vary according to the interface types and signaling types on the Interface
Configuration tab page. The parameters unsupported are hidden.
Step 4 After the settings, click OK to return to the PW Management tab page.
The created PWs are displayed in the query result area.
Step 5 Optional: For existing dynamic PWs, you can perform the following configurations:
1.
2.
----End
Creating a PW APS
This topic describes how to create a Pseudo Wire (PW) Automatic Protection Switching (APS).
PW APS is a network protection mechanism. This mechanism is used to switch services to the
secondary PW when the primary PW fails to function properly.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose VPN Management > PWE3 Management > PW APS Management from the service
tree.
Step 3 Click Create and set the related parameters.
Issue 01 (2014-01-31)
374
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose VPN Management > PW APS Management from the service tree.
Step 3 Click Create.
Step 4 In the dialog box that is displayed, set the related parameters.
Result
Information about the created PW APS protection group is displayed in the query result area.
375
Prerequisites
Before configuring the Martini service VSI, complete the following tasks:
l
Configuring LSR IDs and enabling MPLS and MPLS LDP on PE and P equipment
If PEs are not directly connected to each other, that is, if PEs have to communicate with
each other by using Ps, remote LDP sessions must be configured.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose VPN Management > VSI Management from the service tree.
Step 3 Choose Create > Martini Service VSI. The Create Martini Service VSI dialog box is
displayed.
1.
NOTE
The VSI parameters that need to be set vary according to equipment types.
2.
Issue 01 (2014-01-31)
On the Configure VC tab page, click Create and select the VC type as required.
376
NOTE
The commands delivered by and the function of the mesh VC are different from those of the spoke
VC The mesh VC is applicable to the full-mesh scenario, whereas the spoke VC is applicable to the
HVPLS. The essential difference between the mesh VC and the spoke VC is whether to forward
packets received from the PW to another VSI. The spoke VC forwards the packets, whereas the mesh
VC does not.
3.
On the Bind Interface tab page, click Add. In the Select Interface dialog box, select the
access interface associated with the VSI, and then click OK.
NOTE
l You cannot select the interfaces that are bound to other services.
l If no eligible interfaces are displayed, you can click Create to create an interface or subinterface.
4.
On the MAC Address Entry tab page, click Create. In the dialog box that is displayed,
set the related parameters.
Result
On the VSI Management tab page, you can find the newly created Martini service VSI. You
can select the VSI and view details about the VSI in the detailed information area.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose VPN Management > VSI Management from the service tree.
Step 3 Click Query to query all records.
Step 4 Click the VSI List tab. Select one or more VSIs to be operated from the service VSI list. Then
perform either of the following operations:
l Right-click the VSIs and choose Enabled from the shortcut menu.
l Right-click the VSIs and choose Disabled from the shortcut menu.
----End
377
Prerequisites
Before configuring a VRF, you must do as follows:
l
Create routing policies if import or export routing policies need to be applied to the VRF.
Create tunnel policies if MPLS TE tunnels are configured. For configurations about tunnel
policies, see "Creating a Tunnel Policy".
Context
A VRF is also called a VPN instance. One or more VRFs and a public routing table (global
routing table) can be maintained for a PE. VRFs are separate from each other. A VRF can be
regarded as a virtual router, which maintains the independent address space and provides access
interfaces.
To be more specific, every connection between a CE and a PE corresponds to a VPN instance
(not a one-to-one mapping). This mapping is realized on the basis of the configuration that the
VPN instance is associated with (or bound to) the PE interface that directly connects the CE.
The VPN instance realizes the independence of address space through the RD and realizes the
VPN member relationship and routing rules control at the directly connected site and remote
site through the RT attribute.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose VPN Management > VRF Management from the service tree.
Step 3 Click Create.
Step 4 In the Create VRF dialog box, perform the following tasks:
1.
On the VRF Configuration tab page, enter the VRF name, RD, and VRF description.
2.
Click Create. In the Create RT dialog box, set the RT value and type. Click OK.
3.
Optional: Click Advanced. In the Configure Advanced Attribute of VRF dialog box,
set the related parameters. Click OK.
4.
On the Bind Interface tab page, click Add. In the Select Interface dialog box, set the
query conditions and click Query. Select the interface that is bound to the VRF, and then
click OK.
NOTE
Issue 01 (2014-01-31)
378
Result
The created VRF is displayed in the query result area in VRF Management. You can select the
VRF and view details about the VRF in the detailed information area. The details about the VRF
includes the general information and information about the bound interface.
Prerequisites
Before configuring a CCC connection, you must do as follows:
l
Issue 01 (2014-01-31)
379
Procedure
Step 1 Right-click the ATN in the Main Topology and choose ATN Explorer from the shortcut menu.
Step 2 Choose VPN Management > CCC Management from the service tree.
Step 3 On the CCC Management tab page, click Create.
Step 4 Set parameters in the dialog box shown in the following figure.
NOTE
l Incoming Interface indicates the PE's interface that is connected to the first CE.
l Outgoing Interface indicates the PE's interface that is connected to the second CE.
3.17.1 Ping
This topic describes how to send ping packets to a remote host to check whether it is reachable.
To check the network connectivity or the line quality, you can also perform the ping test.
Issue 01 (2014-01-31)
380
Context
During the ping process, the source host sends an ICMP ECHO-REQUEST packet to the
destination host. If the network connection between the source host and the destination host is
normal, after receiving the ICMP ECHO-REQUEST packet, the destination host responds to
the source host with an ICMP ECHO-REPLY packet.
Procedure
Step 1 In the Main Topology, select the NE to be operated.
Step 2 Right-click the NE and choose Tool > Ping from the shortcut menu.
Step 3 In the dialog box that is displayed, select Ping or Continual Ping, and then click Start.
----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.
If the operation fails, it indicates that the destination host is unreachable and the network
connectivity or line failure cannot be detected. The Request time out message is displayed.
3.17.2 Tracert
This topic descries how to test the route that a data packet passes from the source host to the
destination host. The tracert command is used to check whether a network connection is
reachable and to determine the position where a fault occurs. After detecting a fault on the
network by using the ping command, you can use the tracert command to determine the fault
position.
Context
The execution process of the tracert command is as follows:
l
The source host sends a packet whose TTL is 1. The TTL times out. The first hop sends
back an ICMP error message to indicate that this packet cannot be sent.
The source host sends a packet whose TTL is 2. The TTL times out. The second hop sends
back an ICMP error message to indicate that this packet cannot be sent.
The source host sends a packet whose TTL is 3. The TTL times out. The third hop sends
back an ICMP error message to indicate that this packet cannot be sent.
The process continues in this manner until the packet reaches the destination host or a packet
times out whose TTL is 10.
The purpose of performing these operations is to record the source address of each ICMP TTL
time-out message, so as to provide the route that an IP packet passes to reach the destination
host.
Issue 01 (2014-01-31)
381
Procedure
Step 1 In the Main Topology, select the NE to be operated.
Step 2 Right-click the NE and choose Tool > Tracert from the shortcut menu.
NOTE
In the Tracert Result dialog box, the gateways that the test packets pass from the source host to the
destination host and the response time that the three sent test packets reach the gateways are displayed.
----End
3.17.3 Telnet
This topic describes how to remotely log in to an NE by performing the Telnet operation on the
U2000 to configure and maintain the NE.
Prerequisite
Make sure that port 9811 between the U2000 server and clients is enabled before you telnet a
device.
2.
Right-click the NE and choose Tool > Telnet from the shortcut menu.
When you telnet to the remote server or NE successfully, you can operate the NE through
command lines.
The
2.
button on the toolbar is grayed out. It is available only after you access NE Explorer.
3.
Click the
3.17.4 SSH
This topic describes how to guarantee the security of network communications through SSH
that provides authentication, encryption, and authorization. When a user remotely logs in to a
router through an insecure network, SSH offers secure information guarantee and powerful
authentication to protect the NE against attacks such as IP address spoofing and interception of
plain text passwords.
382
2.
Right-click the NE and choose Tool > SSH from the shortcut menu.
3.
In the dialog box that is displayed, set related parameters and click OK.
After logging in to a remote server or host remotely, you can perform operations on the NE
through command lines.
The
2.
button on the toolbar is grayed out. It is available only after you access NE Explorer.
3.
Click the
4.
In the dialog box that is displayed, set related parameters and click OK.
After successfully logging in to the remote device, you can run command lines to operate
the device.
Context
l
Compared with the common ping test, the ICMP ping test supports the setting of test packet
parameters and other advanced parameters, as well as the setting of the source and
destination addresses. Thus, the ICMP ping test can provide more specific test results.
Certain NEs do not support the ICMP ping test. The ICMP Ping option is not contained
in the shortcut menus for these NEs.
Procedure
Step 1 Right-click the source NE to be diagnosed in the Main Topology and choose Tool > ICMP
Ping from the shortcut menu.
Step 2 At the moment, the cursor turns into a cross. Click the destination NE.
Step 3 In the Test dialog box, set the related parameters.
Step 4 Click Run.
Step 5 View the execution result in the Run Test dialog box.
During the test execution, you can click Terminate to stop the test.
----End
Issue 01 (2014-01-31)
383
Context
l
Compared with the common tracert test, the ICMP trace test supports the setting of test
packet parameters and other advanced parameters, as well as the setting of the source and
destination addresses. Thus, the ICMP trace test can provide more specific test results.
Certain NEs do not support the ICMP trace test. The ICMP Trace option is not contained
in the shortcut menus for these NEs.
Procedure
Step 1 Right-click the source NE to be diagnosed in the Main Topology and choose Tool > ICMP
Trace from the shortcut menu.
Step 2 At the moment, the cursor turns into a cross. Click the destination NE.
Step 3 In the Test dialog box, set the related parameters.
Step 4 Click Run.
Step 5 View the execution result in the Run Test dialog box.
During the test execution, you can click Terminate to stop the test.
----End
Issue 01 (2014-01-31)
384
Procedure
l
Basic configurations
All basic configurations are applied to NEs using the IP plug-and-play management
function. Basic configurations include basic device configurations, AAA and user
management, loopback interface configuration, network interface configuration, and
SNMP configurations.
IGP configurations
All IGP configurations are applied to NEs using the IP plug-and-play management function.
IGP configurations include global routing configuration, interface route and IP and routing
policies.
MPLS configurations
LSP Deployment Mode
Issue 01 (2014-01-31)
385
MPLS TE LSP
----End
Configuration Principle
If IGP routes are deployed and the cost value is configured as planned on a network, route
selection can be controlled. In this case, MPLS LDP LSPs of the host on the network can be
triggered based on the routing table.
1.
2.
3.
Issue 01 (2014-01-31)
386
4.
Data Planning
This topic provides the data plan for MPLS LDP configuration.
Table 4-1 MPLS LSR ID planning
NE Role
LSR ID
Remarks
CSG1
1.1.1.1
CSG2
2.2.2.2
ASG3
3.3.3.3
ASG4
4.4.4.4
RSG5
5.5.5.5
RSG6
6.6.6.6
Value
Remarks
Auto-Assign
N/A
50
N/A
50
Configuration Object
Configure BFD for LSP on the primary and secondary ASGs and the primary and secondary
RSGs on a bearer network.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the Service Tree, choose Reliability > BFD Management > Service Detection
Configuration > LDP LSP Detection Configuration from the main menu.
Step 3 Click Configure. The Set Dynamic BFD Detect LDP LSP Detection dialog box is displayed.
Issue 01 (2014-01-31)
387
Step 4 Select Enable Dynamic BFD for LDP LSP Detection and Set Dynamic BFD Detect LDP
LSP Trigger Policy, and set Trigger Type to FEC List.
Step 5 Click ... next to FEC List. The Set FEC List dialog box is displayed. Enter the FEC list name,
click New, enter Peer IP Address, and click Apply. The following table lists the data plan for
NE parameters.
Parameter
Primary/Secondary ASG
Primary/Secondary RSG
FEC List
ASG
RSG
Peer IP Address
5.5.5.5
3.3.3.3
6.6.6.6
4.4.4.4
Issue 01 (2014-01-31)
Parameter
Configuration Requirements
50
50
388
Deploying MPLS TE
This topic describes how to deploy Multi-Protocol Label Switching Traffic Engineer (MPLS
TE) to create TE tunnels for carrying services.
Configuration Principle
This topic describes the principle for configuring layered MPLS TE tunnels.
As shown in Figure 4-1, deploy MPLS TE tunnels to carry MPLS VPN for transport wireless
services.
Issue 01 (2014-01-31)
389
2.
Configure LSR IDs, enable MPLS, MPLS TE, MPLS TE CSPF and BFD for RSVP-TE
globally for nodes on the tunnels, and enable MPLS and MPLS TE for interfaces on the
tunnels.
3.
Issue 01 (2014-01-31)
390
NOTE
In the preceding figure, A to E indicate TE constraint interfaces for TE1 to TE7 respectively.
Constraint Interfaces
Include Mode
TE1
Loose
TE2
Loose
TE3
Loose
TE4
Loose
TE5
Loose
TE6
Loose
TE7
Strict
391
Configure the tunnel re-optimization function. You are advised to set the reoptimization interval to 3600s.
NOTE
If the secondary LSP of a tunnel is not configured with constraint paths, a best-effort path is not
required for the tunnel. Otherwise, a best-effort must be configured for the tunnel.
l Automatic path selection: Properly plan cost values for links and use the TE CSPF
function to automatically select paths. In this mode, tunnel deployment is simple and
network adjustment is easy. On a network with a clear structure, use automatic path
selection. The configuration principle is as follows:
TE automatic path selection is implemented based on IGP routes. Therefore,
configure the cost values according to the network plan when configuring IGP. For
details on IGP cost values, see the related IGP configuration topic.
To ensure that services are transmitted over the best path, configure the tunnel reoptimization function. You are advised to set the re-optimization interval to 3600s.
To maximum protection for the working path of tunnels configured with hotstandby, configure the CR-LSP overlap-path function.
For TE to automatically select proper paths, plan cost values for links. To ensure the
primary TE LSPs select the paths of the rings,the access link between the master and
slave ASGs must have a higher cost value than the maximum metric value of the access
ring. For example, cost values for links a, b, c, and d in the following figure must meet
the following rule: (cost(a) + cost(b) + cost(d)) < cost(c). In addition, set the cost values
for links between the master and slave NPEs based on the following rules: (n - 1) x 10
< cost < n x 10 (for IS-IS); (n - 1) < cost < n (for OSPF); where n is the number of links
on the aggregation ring, excluding the link between RSGs. The figure below shows an
example of cost value plan for this example.
Figure 4-3 IS-IS cost value plan
Issue 01 (2014-01-31)
392
4.
b.
c.
d.
5.
Enable MPLS L2VPN for nodes on the TE tunnels, and enable remote LDP peers for
nodes between tunnels.
b.
c.
Issue 01 (2014-01-31)
393
l Create tunnels TE3 and TE4 as the VPN backup tunnels for the VPN working
tunnel TE1 or TE2.
NOTE
When Ethernet and ATM/TDM services share tunnels, the services can also share tunnel policies as
in this example. If Ethernet and ATM/TDM services do not share tunnels, tunnel policies need to be
configured for the services respectively.
6.
Context
You need to create multiple templates based on different requirements for tunnel settings.
NOTE
Path Constraint in the following table applies to the primary tunnel only.
Tunnel
Path
Constraint
BFD Configuration
Template
Tunnel between
CSG1 and ASG3
Loosely
include
Template 1
Tunnel between
CSG1 and ASG4
Loosely
include
No BFD
Template 3
Tunnel between
ASG3 and RSG5
Loosely
include
Template 1
Tunnel between
ASG3 and RSG6
Loosely
include
Template 1
Tunnel between
ASG4 and RSG5
Loosely
include
Template 1
Tunnel between
ASG4 and RSG6
Loosely
include
Template 1
Tunnel between
RSGs 5 and 6
Strictly
include
Template 2
Procedure
Step 1 Choose Service > Service Template from the main menu.
Step 2 In the Set Filter Criteria dialog box, set Template Type to RSVP-TE Tunnel and click
Filter.
Issue 01 (2014-01-31)
394
Step 3 In the Manage Service Template window, click Create > RSVP-TE Tunnel Template.
Step 4 In the Create RSVP-TE Tunnel Template window, set Template Name as planned. The
following table lists the planned template parameters.
Table 4-4 RSVP-TE tunnel template parameters
Parameter Settings
Default Setting
Unnumbered Interface
N/A
Unnumbered Interface
N/A
N/A
TE Information
Reserve Style
Explicit Sharing
Trail Information
Hop Type
Loosely include
NOTE
The parameter must be set to Strictly include when you
configure template 2.
Hot standby
Reversion Interval(s)
60
Revertive Mode
Revertive
Yes
BFD Information
NOTE
The check box needs to be selected only when you configure the templates for the primary VPN tunnel on
the access ring or all tunnels on the aggregation ring.
BFD Type
Static
MinReceiveSendInterval
50
Issue 01 (2014-01-31)
DetectMultiplier
MinReceiveSendInterval
10
395
Parameter Settings
Default Setting
Advanced>Setup Attribute
Record Route Type
Advanced>Reoptimization
Enable Reoptimization
Yes
Interval(s)
3600
Configuration Object
On the bearer network, configure seven MPLS TE tunnels for service bearer and protection
according to the data plan.
Procedure
Step 1 Create tunnels.
Choose Service > Tunnel > Create Tunnel from the main menu.
Step 2 Set basic tunnel parameters.
Parameter
Configuration Requirements
Tunnel Name
Reverse Tunnel
Name
Issue 01 (2014-01-31)
Template
Protocol Type
Signaling Type
396
Step 3 Add source and sink NEs according to the data plan.
In Physical Topology, right-click source and sink NEs respectively.
Configure the NE where the interface with route constraints resides. For example, if a forward tunnel is
destined from A to B and the next hop is constrained as the network-side interface of B, you need to select
B and configure route constraints for the tunnel.
1.
In the Physical Topology, right-click the sink NE traversed by the primary forward path
and choose Set Explicit Restriction > Interface from the shortcut menu.
2.
In the Set Route Constraint dialog box, click the Primary trail option button, select the
Forward Tunnel and Reverse Tunnel check boxes, and click OK.
NOTE
If requiring the forward and reverse tunnels to constrain different interfaces, you need to configure
constrained interfaces respectively for both tunnels.
3.
Issue 01 (2014-01-31)
In the dialog box that is displayed, select the interface traversed by the primary forward
path and click OK.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
397
NOTE
Click Show all Interface and select an interface from all interfaces on the current NE.
4.
In the Route Constraint area, set Restriction Type on the Forward tunnel primary
trail and Reverse tunnel primary trail tabs. Restriction Type is set to Loosely include
by default. However, you need to set it to Strictly include for tunnels between the primary
and secondary RSGs.
Verifying Configurations
This topic explains how to verify configurations.
Choose Service > Tunnel > Manage Tunnel from the main menu.
2.
In the Set Filter Criteria dialog box, set the search criteria and click Filter. The qualified
tunnels are displayed.
3.
Select a tunnel and click Synchronization. After the synchronization is complete, rightclick the tunnel and choose View LSP Topology from the shortcut menu. The View LSP
Topology progress bar is displayed.
4.
View the LSP topology after the progress bar is automatically closed. The solid line stands
for an active LSP and the dashed line stands for a backup LSP.
5.
1.
Choose Service > Tunnel > Manage Tunnel from the main menu.
2.
In the Set Filter Criteria dialog box, set the search criteria and click Filter. The qualified
tunnels are displayed.
3.
Select a tunnel. In the tunnel topology displayed in the lower area, right-click the tunnel
and choose Fast Diagnose from the shortcut menu.
4.
5.
LSP Ping
Issue 01 (2014-01-31)
398
6.
Repeat the preceding steps to check whether LSP Ping can be successfully performed for
the rest of the tunnels.
Procedure
Step 1 Choose Service > Service Template from the main menu.
Step 2 In the Set Filter Criteria dialog box, set Template Type to L3VPN and click Filter.
Step 3 In the Manage Service Template window, click Create > L3VPN Service Template.
Step 4 In the Create L3VPN Service Template window, set Template Name as planned. The
following table lists the planned template parameters.
Table 4-5 L3VPN template parameters
Parameter Settings
Default Setting
Control
Network Type
HVPN
Issue 01 (2014-01-31)
Yes
399
Parameter Settings
Default Setting
NOTE
This parameter is mandatory when the
MPLS TE tunnel is used.
General
VRF ID
Auto-Assign
VRF Name
N/A
Import RT
N/A
Export RT
N/A
N/A
Per VPN
NOTE
The default route is associated with the VPN loopback
address on the RSG to prevent the generation of black-hole
routes. In this case, Label Distribution Policy needs to be
set to Per VPN.
N/A
N/A
N/A
Network Segment
N/A
Issue 01 (2014-01-31)
N/A
Next VRF
N/A
No
Priority
60
Description
N/A
N/A
BFD Index
N/A
VRRP ID
N/A
Lock
N/A
Metric Priority
N/A
400
Parameter Settings
Default Setting
N/A
Procedure
Step 1 Choose Service > Service Template from the main menu.
Step 2 In the Set Filter Criteria dialog box, set Template Type to PWE3 and click Filter.
Step 3 In the Manage Service Template window, click Create > PWE3 Service Template.
Step 4 In the Create PWE3 Service Template window, set Template Name as planned. The following
table lists the planned template parameters.
Table 4-6 TDM template parameters
Parameter Settings
Default Setting
General
Service Type
CES
Protection Type
Remarks
N/A
Enable
Redundancy Mode
Issue 01 (2014-01-31)
Forward Type
Reverse Type
401
Parameter Settings
Default Setting
Working PW>Advanced
Control Word
Use required
RTP Head
Disable
8000
Encapsulated Frames
Sequence Mode
Standard Mode
Enable
NOTE
The parameter is required only on aggregation site gateways
(ASGs).
Forward Type
Reverse Type
Protection PW>Advanced
Control Word
Use required
RTP Head
Disable
8000
Encapsulated Frames
Sequence Mode
Standard Mode
Enable
NOTE
The parameter is required only on ASGs.
SAI
SAI Description
N/A
BFD Configuration
Issue 01 (2014-01-31)
BFD Type
Static
Detection Multiple
50
402
Parameter Settings
Default Setting
OAM Mapping
OAM Mapping
Enabled
Operation Attribute
Deploy
Deploy
Enable
Enable
Default Setting
General
Service Type
ATM
Protection Type
Remarks
N/A
Enable
Redundancy Mode
Forward Type
Reverse Type
Working PW>Advanced
Issue 01 (2014-01-31)
PW Type
Control Word
Use required
403
Parameter Settings
Default Setting
Forward Type
Reverse Type
Protection PW>Advanced
PW Type
Control Word
Use required
SAI
SAI Description
N/A
BFD Configuration
BFD Type
Static
Detection Multiple
50
OAM Mapping
OAM Mapping
Enable
Operation Attribute
Deploy
Deploy
Enable
Enable
Configuration Object
Set Max.ATM Cells on the cell site gateway (CSG) and on the primary and secondary radio
service gateway (RSGs).
Issue 01 (2014-01-31)
404
Procedure
1.
In the Main Topology, right-click the desired NE and choose NE Explorer from the
shortcut menu.
2.
Choose VPN Management > PWE3 Management > PW Template Management from
the Service Tree.
3.
4.
5.
6.
When ATM subboards do not support cascading, the maximum number of ATM cells should be set to 1.
7.
Click OK.
Configuration Guidelines
This topic describes the guidelines for deploying hierarchical BGP/MPLS VPN and protection
(BGP is short for Border Gateway Protocol, MPLS is short for multiprotocol label switching,
and VPN is short for virtual private network).
l
Figure 4-5 shows the hierarchical GP/MPLS VPN between cell site gateways (CSGs) and
Remote site gateways (RSGs).
Issue 01 (2014-01-31)
405
Deploy MP-IBGP.
l Establish MP-IBGP peer relationships between CSGs and the master ASG, and between
the master ASG and the master RSG.
l To protect the master ASG, establish MP-IBGP peer relationships between CSGs and
the backup ASG, and between the backup ASG and the master RSG.
l To protect the master RSG, establish an MP-IBGP peer relationship between the master
ASG and the backup RSG.
2.
3.
Issue 01 (2014-01-31)
406
This configuration allows the BGP peer relationship to be established between the CSG
and the master ASG after the BGP peer relationship has been established between the
recovered master ASG and the master RSG during LTE X2 service deployment.
l Configure VPN FRR or BFD for BGP.
VPN FRR is recommended. If no VPN instance is created on the deployed devices,
configure BFD for BGP and IP over TE to speed up the master/backup device
switchover.
4.
RSG protection can be implemented using VRRP (recommended) or Active and standby
routes.
l Configure VRRP (recommended).
To protect the links between RSGs and the MBB core, configure VRRP over VLANIF
between the master and backup RSGs.
a.
Configure the interfaces that connect the master and backup RSGs and the
interfaces that connect the master and backup RSGs to the RNC to be Layer 2
switch interfaces, and add these interfaces to a VLAN.
b.
Create a VLANIF interface on the master and backup RSGs and configure VRRP
over VLANIF.
c.
Configure BFD between the master and backup RSGs to check Layer 2 links and
remote private network addresses. This is to speed up the master/backup device
switchover.
d.
Configure VRRP switchback delay on the master RSG. If VRRP switchback delay
is not configured, both NEs may be in the master state during VRRP switchback.
This will result in packet loss.
l Active and standby routes: Configure active and standby static routes to implement RSG
protection. The RNC communicates with the master and backup using logical interfaces.
The logical interfaces connected to the master and backup RSGs can both receive
packets.
Data Plan
Before using the configured BGP/MPLS VPN to carry the Ethernet service, you need to plan
key parameter settings.
Table 4-8 VRF settings (U2000)
Parameter
Value
VRF Name
IPRAN
RD
100:1
Remarks
Issue 01 (2014-01-31)
407
Parameter
Value
Remarks
RT
CSG1: 192.168.100.1/24
RSG5: 192.168.2.2/24
RSG6: 192.168.2.3/24
RSG-side gateway:
192.168.2.100
SAI
Issue 01 (2014-01-31)
VRF Name
LTE-X2
RD
200:1
408
Parameter
Value
Remarks
RT
NOTE
When MPLS LDP LSPs are
used, LTE X2 services may use
the same VPN instance as LTE
S1 services. If you need to
create a new VPN instance for
LTE X2 services, refer to the
data plan in the middle column.
Service IP
CSG2: 192.168.4.1/24
SAI
CSG1/CSG2:
Ethernet0/3/0.100, vlan 100
Configuration Objects
All the main interfaces that connect RSGs or connect the RSGs and the RNC side must be
configured as Layer 2 interfaces.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 Click Query. All the qualified records are displayed.
Step 4 Select the interface to be configured and click Configure. A dialog box is displayed.
Issue 01 (2014-01-31)
409
Step 5 If the interface is an Ethernet port, click the Ethernet Feature tab, select Layer 2, and click
OK.
Step 6 If the interface is an Eth-Trunk port, click the Physical Feature tab, select Layer 2, and click
OK.
Step 7 Configure other interfaces by referring to steps 1-6.
----End
Configuration Object
Configure the CSG, primary and secondary aggregation site gateways (ASGs), and primary and
secondary RSGs to create the L3VPN service.
1.
Choose Service > L3VPN Service > Create L3VPN Service from the main menu.
2.
Configuration Requirements
Service Name
LTE_S1
Service Template
Network Type
HVPN
Route Notify
Policy
Default Route
VRF Name
IPRAN
VRF ID
RD
RT
3.
In the Physical Topology, right-click an NE and choose a node role from the shortcut menu.
After the configuration, the NE is displayed in Node List in the lower-left part.
Table 4-9 NE Role
Issue 01 (2014-01-31)
Node Name
CSG
ASG
RSG
Node Role
UPE
SPE
NPE
410
NOTE
4.
Select all NEs in Node List and click Details in the lower-left part. The VRF
Configuration tab is displayed in the lower-right part.
b.
On the VRF Configuration tab, choose General and modify RD and RT of each NE
according to the data plan.
NOTE
Issue 01 (2014-01-31)
VRF
Configurat
ion
CSG1
ASG3
ASG4
RSG5
RSG6
VRF Name
IPRAN
IPRAN
IPRAN
IPRAN
IPRAN
RD
100:1
100:1
100:1
100:1
100:1
Import RT
200:1
100:1
100:1
100:1
100:1
411
5.
6.
Issue 01 (2014-01-31)
VRF
Configurat
ion
CSG1
ASG3
ASG4
RSG5
RSG6
Export RT
100:1
100:1
200:1
100:1
200:1
100:1
100:1
b.
Double-click in the cell at the intersection of the CSG column and the Interface row,
and click .... In the dialog box that is displayed, select the interface for transmitting
the L3VPN service.
c.
Click the SAI Configuration tab and set the ID and VLAN ID for the subinterface.
d.
Click the IP Address tab and set the IP address and mask for the subinterface.
e.
Configure RNC-side interfaces on the primary and secondary RSGs (with VRRP enabled).
a.
b.
Click the button in the cell at the intersection of the RSG NE column and the Interface
Name row. The Create SAI dialog box is displayed.
c.
Choose Create > VLANIF. Then the Add VLAN Interface dialog box is displayed.
d.
On the General tab, click ... next to Interface No.. Then the Select VLAN ID dialog
box is displayed.
e.
Select an existing VLAN or click Create. In the Create VLAN dialog box, enter the
VLAN ID and click OK to create a VLAN.
412
Issue 01 (2014-01-31)
f.
On the VLAN Member Port tab, click Add. Then the Add Member Port dialog box
is displayed.
g.
h.
In the Selected Port list, set Binding Mode to Passable VLAN for the two ports as
listed in the following table, and click OK.
Port Name
Binding Mode
GigabitEthernet1/0/2
Passable VLAN
Eth-trunk1
Passable VLAN
i.
j.
In the Add VLAN Interface dialog box, click the IPv4 Address tab and set IP address
and mask for the VLANIF interface according to the data plan.
413
k.
l.
In the Create SAI dialog box, select the created VLANIF interface and click OK.
m. (Optional)Set the port link type according to actual conditions. For detailed
operations, see (Optional) Configuring the Port Link Type.
7.
8.
Configure RNC-side interfaces on the primary and secondary RSGs (with active and
standby routing protection enabled).
a.
b.
Click the button in the cell at the intersection of the RSG NE column and the Interface
Name row. The Create SAI dialog box is displayed.
c.
Select a physical interface in use and click Configure. In the Configure Ethernet
Interface dialog box, click the Physical Feature tab, and set Delay Time(ms) to
300000.
d.
e.
If the base station uses a logical IP address, configure a static route destined to this logical IP address on
the CSG and bind the static route to a VPN instance.
a.
Issue 01 (2014-01-31)
On the VRF Configuration tab, choose Route Configuration > Static Route >
Static Route Object.
414
9.
VRF Configuration
CSG
Destination IP Address
Mask
255.255.255.255
On the VRF Configuration tab, choose Route Configuration > BGP > BGP
Instance > Route Import > Route Import Instance.
b.
To import multiple routes, click the icon next to the Route Import node and choose Insert
Instance.
CSG1
ASG3
ASG4
RSG5
RSG6
Route Type
Direct
N/A
N/A
Direct
Direct
Static
Static
Static
Issue 01 (2014-01-31)
415
VRF
Configura
tion
CSG1
ASG3
ASG4
RSG5
RSG6
Network
Segment
N/A
0.0.0.0
0.0.0.0
N/A
N/A
10. (Optional) Configure the VRRP (required only when the VRRP protection is used).
Issue 01 (2014-01-31)
a.
b.
In the topology view, right-click the VALNIF interface extended from the RSG and
choose Expand from the shortcut menu.
c.
Right-click the expanded VLANIF interface and choose Create VRRP from the
shortcut menu. The Configure VRRP dialog box is displayed.
416
d.
e.
Issue 01 (2014-01-31)
VRF Configuration
Secondary RSG
(RSG6)
VR IP
192.168.2.100
192.168.2.100
Delay(s)
180
Notification Interval(s)
30
30
Configured Priority
120
100
Interface
VLANIF100
VLANIF100
Increase Priority By
40
40
Reduce Cost
100
Click the Track BFD option button and Con. The Configure BFD dialog box is
displayed. Set parameters according to the data plan.
VRF Configuration
Secondary RSG
(RSG6)
Local ID
300
300
Min.Receiving Interval
50
50
Min.Sending Interval
50
50
417
f.
After the BFD configuration is complete, click OK in the Configure BFD dialog box.
g.
11. In the Create L3VPN Service window, click Apply to apply the L3VPN service.
12. After the L3VPN service is applied successfully, the Operation Result dialog box is
displayed.
13. Click Browse Trail to view the L3VPN configuration results.
Running Status is Up, Alarm Severity is Normal, Deployment Status is Deployed, and
Enabling Status is Enabled.
NOTE
To view the path carrying the L3VPN service, perform the following operations:
In the Manage L3VPN Service window, select the created L3VPN service, and click Refresh on the
Service Link tab to view the path data or click the Topology tab to view the path in the Service
Topology.
NOTICE
If Running Status is not Up, right-click the L3VPN service, choose Refresh Running
Status from the shortcut menu, and view Running Status.
14. (Optional) Modify the L3VPN service.
Issue 01 (2014-01-31)
a.
Choose Service > L3VPN Service > Manage L3VPN Service from the main menu.
b.
Right-click the L3VPN service and choose Modify from the shortcut menu. The
Modify L3VPN Service window is displayed.
c.
d.
If you have not selected the VPN Auto FRR check box during the L3VPN service
creation, you can perform only the following operations for the VPN Auto FRR
function to take effect:
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
418
a.
On the VRF Configuration tab, choose General > Label Distribution Policy
and set Label Distribution Policy to Per VPN.
b.
On the VRF Configuration tab, choose General > Routing Policy > Routing
Policy Object > Routing Policy.
c.
Double-click in the cell at the intersection of each NE column and the Routing
Policy row, and click .... The Select Routing Policy dialog box is displayed.
d.
e.
f.
Issue 01 (2014-01-31)
Parameter
Configuration Requirements
Policy Type
Route Policy
Policy Name
frr
Configuration Requirements
Node ID
10
Permit
Click Create in the lower pane. In the Create Policy Rule dialog box, set
parameters.
Parameter
Configuration Requirements
Behavior
Apply
Match Type
Auto
419
g.
h.
i.
Configuration Object
Configure the CSG and primary and secondary RSGs to create the L3VPN service.
1.
Choose Service > L3VPN Service > Create L3VPN Service from the main menu.
2.
Issue 01 (2014-01-31)
Parameter
Configuration Requirements
Service Name
LTE_S1
420
Parameter
Configuration Requirements
Service Template
Network Type
HVPN
Route Notify
Policy
Detail Route
VRF Name
IPRAN
VRF ID
RD
RT
3.
In the Physical Topology, right-click an NE and choose a node role from the shortcut menu.
After the configuration, the NE is displayed in Node List in the lower-left part.
Table 4-14 NE Role
Node Name
CSG
RSG
Node Role
UPE
NPE
NOTE
Issue 01 (2014-01-31)
421
4.
Select all NEs in Node List and click Details in the lower-left part. The VRF
Configuration tab is displayed in the lower-right part.
b.
On the VRF Configuration tab, choose General and modify RD and RT of each NE
according to the data plan.
NOTE
5.
Issue 01 (2014-01-31)
VRF
Configuration
CSG1
RSG5
RSG6
VRF Name
IPRAN
IPRAN
IPRAN
RD
100:1
100:1
100:1
Import RT
100:1
100:1
100:1
Export RT
100:1
100:1
100:1
b.
Double-click in the cell at the intersection of the CSG column and the Interface row,
and click .... In the dialog box that is displayed, select the interface for transmitting
the L3VPN service.
c.
Click the SAI Configuration tab and set the ID and VLAN ID for the subinterface.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
422
6.
Issue 01 (2014-01-31)
d.
Click the IP Address tab and set the IP address and mask for the subinterface.
e.
Configure RNC-side interfaces on the primary and secondary RSGs (with VRRP enabled).
a.
b.
Click the button in the cell at the intersection of the RSG NE column and the Interface
Name row. The Create SAI dialog box is displayed.
c.
Choose Create > VLANIF. Then the Add VLAN Interface dialog box is displayed.
d.
On the General tab, click ... next to Interface No.. Then the Select VLAN ID dialog
box is displayed.
e.
Select an existing VLAN or click Create. In the Create VLAN dialog box, enter the
VLAN ID and click OK to create a VLAN.
f.
On the VLAN Member Port tab, click Add. Then the Add Member Port dialog box
is displayed.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
423
g.
h.
In the Selected Port list, set Binding Mode to Passable VLAN for the two ports as
listed in the following table, and click OK.
Port Name
Binding Mode
GigabitEthernet1/0/2
Passable VLAN
Eth-trunk1
Passable VLAN
i.
j.
In the Add VLAN Interface dialog box, click the IPv4 Address tab and set IP address
and mask for the VLANIF interface according to the data plan.
k.
l.
In the Create SAI dialog box, select the created VLANIF interface and click OK.
m. (Optional) Set the port link type according to actual conditions. For detailed
operations, see (Optional) Configuring the Port Link Type.
7.
Issue 01 (2014-01-31)
Configure RNC-side interfaces on the primary and secondary RSGs (with active and
standby routing protection enabled).
a.
b.
Click the button in the cell at the intersection of the RSG NE column and the Interface
Name row. The Create SAI dialog box is displayed.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
424
8.
c.
Select a physical interface in use and click Configure. In the Configure Ethernet
Interface dialog box, click the Physical Feature tab, and set Delay Time(ms) to
300000.
d.
e.
l If the base station uses a logical IP address, configure a static route destined to this logical IP address
on the CSG and bind the static route to a VPN instance.
l If the RNC uses a logical IP address, configure a static route destined to this logical IP address on the
RNC and bind the static route to a VPN instance.
a.
On the VRF Configuration tab, choose Route Configuration > Static Route >
Static Route Object.
Table 4-16 Static route settings
9.
VRF
Configuration
CSG
RSG5
RSG6
Destination IP
Address
120.16.1.2 (logical
IP address of the
base station)
12.12.12.1 (logical
IP address of the
RNC)
12.12.12.1 (logical
IP address of the
RNC)
Mask
255.255.255.255
255.255.255.255
255.255.255.255
Next Hop IP
Address
192.168.1.2 (IP
address of the base
station interface
connecting to the
CSG)
192.168.2.101 (IP
address of the RNC
interface
connecting to the
RSG)
192.168.2.101 (IP
address of the RNC
interface
connecting to the
RSG)
Priority
60
Description
TO NodeB
TO RNC
TO RNC
On the VRF Configuration tab, choose Route Configuration > BGP > BGP
Instance > Route Import > Route Import Instance.
b.
To import multiple routes, click the icon next to the Route Import node and choose Insert
Instance.
Issue 01 (2014-01-31)
VRF
Configuration
CSG1
RSG5
RSG6
Route Type
Direct
Direct
Direct
Static
Static
Static
425
10. (Optional) Configure the VRRP (required only when the VRRP protection is used).
a.
b.
In the topology view, right-click the VALNIF interface extended from the RSG and
choose Expand from the shortcut menu.
c.
Right-click the expanded VLANIF interface and choose Create VRRP from the
shortcut menu. The Configure VRRP dialog box is displayed.
d.
Issue 01 (2014-01-31)
VRF Configuration
Secondary RSG
(RSG6)
VR IP
192.168.2.100
192.168.2.100
Delay(s)
180
Notification Interval(s)
30
30
Configured Priority
120
100
Interface
VLANIF100
VLANIF100
Increase Priority By
40
40
Reduce Cost
100
426
e.
f.
Issue 01 (2014-01-31)
Click the Track BFD option button and Con. The Configure BFD dialog box is
displayed. Set parameters according to the data plan.
VRF Configuration
Secondary RSG
(RSG6)
Local ID
300
300
Min.Receiving Interval
50
50
Min.Sending Interval
50
50
After the BFD configuration is complete, click OK in the Configure BFD dialog box.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
427
g.
11. In the Create L3VPN Service window, click Apply to apply the L3VPN service.
12. After the L3VPN service is applied successfully, the Operation Result dialog box is
displayed.
13. Click Browse Trail to view the L3VPN configuration results.
Running Status is Up, Alarm Severity is Normal, Deployment Status is Deployed, and
Enabling Status is Enabled.
NOTE
To view the path carrying the L3VPN service, perform the following operations:
In the Manage L3VPN Service window, select the created L3VPN service, and click Refresh on the
Service Link tab to view the path data or click the Topology tab to view the path in the Service
Topology.
NOTICE
If Running Status is not Up, right-click the L3VPN service, choose Refresh Running
Status from the shortcut menu, and view Running Status.
14. (Optional) Modify the L3VPN service.
a.
Choose Service > L3VPN Service > Manage L3VPN Service from the main menu.
b.
Right-click the L3VPN service and choose Modify from the shortcut menu. The
Modify L3VPN Service window is displayed.
c.
d.
If you have not selected the VPN Auto FRR check box during the L3VPN service
creation, you can perform only the following operations for the VPN Auto FRR
function to take effect:
a.
On the VRF Configuration tab, choose General > Label Distribution Policy
and set Label Distribution Policy to Per VPN.
b.
On the VRF Configuration tab, choose General > Routing Policy > Routing
Policy Object > Routing Policy.
c.
Double-click in the cell at the intersection of each NE column and the Routing
Policy row, and click .... The Select Routing Policy dialog box is displayed.
d.
e.
Issue 01 (2014-01-31)
Parameter
Configuration Requirements
Policy Type
Route Policy
Policy Name
frr
Configuration Requirements
Node ID
10
428
f.
Issue 01 (2014-01-31)
Parameter
Configuration Requirements
Permit
Click Create in the lower pane. In the Create Policy Rule dialog box, set
parameters.
Parameter
Configuration Requirements
Behavior
Apply
Match Type
Auto
g.
h.
i.
429
Choose Service > L3VPN Service > Create L3VPN Service from the main menu.
2.
Value
Service Name
LTE_X2
Service Template
Network Type
HVPN
Default Route
VRF Name
IPRAN
VRF ID
Auto-Assign
RD
RT
3.
Click Add and choose SPE Node. In the dialog box that is displayed, select the primary
and secondary aggregation site gateways (ASGs) and click OK.
4.
Click Add and choose UPE Node. In the dialog box that is displayed, select the primary
and secondary CSGs and click OK.
5.
Click Details. On the VRF Configuration tab, set basic attributes according to the data
plan.
Table 4-20 Basic parameter settings
Issue 01 (2014-01-31)
VRF
Configuration
CSG1
CSG2
ASG3
ASG4
RSG5
RSG6
General
VRF
Name
IPRAN
IPRAN
IPRAN
IPRAN
IPRAN
IPRAN
RD
200:1
200:1
200:1
200:1
200:1
200:1
Import
RT
200:2
200:2
100:2
100:2
100:2
100:2
Export
RT
100:2
100:2
100:2
200:2
100:2
200:2
100:2
100:2
430
VRF
Configuration
CSG1
CSG2
ASG3
ASG4
RSG5
RSG6
Routing
Policy
frr
frr
frr
frr
frr
frr
Policy
Type
VPN
FRR
VPN
FRR
VPN
FRR
VPN
FRR
VPN
FRR
VPN
FRR
Tunnel
Policy
Name
ipran
ipran
ipran
ipran
ipran
ipran
NOTE
The RT varies according to MPLS LDP LSPs or MPLS TE tunnels. For details about variance, see Data
Plan. This topic uses MPLS TE tunnels as an example.
6.
Double-click in the cell at the intersection of the CSG column and the Interface row,
and click .... In the dialog box that is displayed, select a service access interface
according to the data plan, set its IP address, and click OK.
CSG1
CSG2
ASG3
ASG4
SAI
Interface
Ethernet0/3
/0.100
Ethernet0/3
/0.100
IP Address/
Mask
192.168.3.1
/24
192.168.4.1
/24
Route Type
Direct
Direct
Static
Static
BGP Route
Import
7.
On the VRF Configuration tab, choose Route Configuration > Static Route >
Static Route Object.
Table 4-22 Static route settings
Issue 01 (2014-01-31)
VRF Configuration
ASG3
ASG4
Destination IP Address
0.0.0.0
0.0.0.0
Mask
0.0.0.0
0.0.0.0
431
8.
VRF Configuration
ASG3
ASG4
On the VRF Configuration tab, choose Route Configuration > BGP > BGP
Instance > Network Segment.
Table 4-23 VRF settings
9.
VRF Configuration
ASG3
ASG4
IP Address
0.0.0.0
0.0.0.0
Configuration Object
Configure the primary and secondary RSGs that are located on the bearer network.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Ethernet Feature Management VLAN ManagementPort VLAN Management from
the service tree.
Step 3 Click Query to query VLAN interface information.
Step 4 Select a required interface and click Modify.
Step 5 In the Modify VLAN Attribute of Port dialog box, set Port Link Type to a required value.
Issue 01 (2014-01-31)
432
----End
Configuration Object
The primary and secondary RSGs.
Configuration Procedure
1.
Issue 01 (2014-01-31)
(Optional)Configure BFD for detecting the peer RSG. (This operation is required only if
RSGs have a 10GE link between them.)
a.
Choose Service > L3VPN Service > Manage L3VPN Service from the main menu.
b.
c.
Select the desired service, right-click, and choose Configure BFD from the shortcut
menu.
d.
e.
Set BFD detection path to the link between the primary and secondary RSGs.
f.
g.
h.
BFD-1
BFD-2
BFD Name
link_01
link_02
Local BFD ID
100
101
Remote BFD ID
200
201
433
2.
Parameter
BFD-1
BFD-2
10
10
10
10
i.
Double-click the Detection Object text box, then click Configure that is displayed.
In the dialog box that is displayed, set IP bind type to Default multicast address,
and set the physical interface between RSGs as the outgoing interface according to
data plan.
j.
Click OK.
k.
l.
If the RNC uses a logical address, the static route should destined to the logical address. In addition, the
static route must be referenced by VPN instances.
a.
Choose Service > L3VPN Service > Manage L3VPN Service from the main menu.
b.
c.
d.
On the VRF Configuration tab, expand Route Configuration > Static Route by
clicking it; click the icon behind the node and select Insert Instance. Configure the
static route according the data listed in the following table.
Table 4-24 Static route parameters
Parameter
Destination IP Address
Mask
255.255.255.255
255.255.255.255
Priority
Issue 01 (2014-01-31)
434
Configuration Objects
Active and standby routes need to be configured for the primary and secondary RSGs on the
bearer network
Configuration Roadmap
If the active and standby interfaces have been planned and the RNC supports the dual-receiving
function of these interfaces, you can configure active and standby routes to ensure that the
primary/secondary RSG relationship is consistent with that on the RNC side. This guarantees
millisecond-level fault detection and protection when the primary RSG or the AC link on the
primary RSG is not functioning properly. The RNC uses the IP address of a logical interface as
the target IP address.
Figure 4-6 Configuring active and standby routes
Configure private IGP for subinterfaces between the RSGs to determine the primary/
secondary RSG relationship. IS-IS is used as an example.
Configure static routes from the primary and secondary RSGs to a logical interface on the
RNC, and import the routes to IS-IS.
Unlike VRRP configuration, when you configure active and standby routes, VPN instances use physical
interfaces rather than VLANIF interfaces.
Operation Procedure
Configure private network IS-IS:
Issue 01 (2014-01-31)
435
1.
Choose Service > L3VPN Service > Manage L3VPN Service from the main menu.
2.
3.
Select a service to be configured, and click Modify. The Modify L3VPN Service window
is displayed.
4.
Select primary and secondary RSGs from the node list, and click Details in the lower left
area. Then VRF Configuration is displayed in the lower right area.
5.
On the VRF Configuration tab, expand Route Configuration > ISIS by clicking it; click
the icon behind the ISIS node and select Insert Instance. Then expand the newly-inserted
node and modify its configuration according to the data plan.
Table 4-25 IS-IS process-Basic parameters
6.
Parameter
Primary RSG
Secondary RSG
Instance ID
Network
Entity
Route Level
Level-2
Level-2
Cost Type
Wide
Wide
On the VRF Configuration tab, choose Route Configuration > ISIS > ISIS Instance >
Route Import > External Route Import for the newly-inserted route instance, and modify
related parameters according to the data plan.
NOTE
To import multiple routes, click the icon behind External Route Import and select Insert Instance.
7.
Parameter
Primary RSG
Secondary RSG
Cost Type
External
External
Protocol Type
Static
Static
Route Level
Level-2
Level-2
On the VRF Configuration tab, choose Route Configuration > ISIS > ISIS Instance >
Protocol Interface > Protocol Interface > Interface Name for the newly-inserted route
instance, and modify related parameters according to the data plan.
Table 4-27 IS-IS interface parameters
Issue 01 (2014-01-31)
Parameter
Primary RSG
Secondary RSG
Interface
Name
GigabitEthernet1/0/1.1
GigabitEthernet1/0/1.1
436
On primary and secondary RSGs, configure a static route destined to the RNC.
1.
Choose Service > L3VPN Service > Manage L3VPN Service from the main menu.
2.
3.
Select the service to be configured and click Modify. The Modify L3VPN Service window
is displayed.
4.
5.
Choose Route Configuration > Static Route > Static Route Object from the service tree.
6.
If multiple static routes exist, click the icon next to Static Route and select Insert Instance.
Primary RSG
Secondary RSG
Destination IP
Address
7.7.7.7
7.7.7.7
Mask
255.255.255.252
255.255.255.252
Next Hop IP
Address
192.168.2.2
192.168.2.6
Priority
50
Description
TO RNC
TO RNC
Choose Service > L3VPN Service > Manage L3VPN Service from the main menu.
2.
3.
Select the service to be configured and click Modify. The Modify L3VPN Service window
is displayed.
4.
5.
Choose Route Configuration > BGP > BGP Instance > Route Import > Route Import
Instance from the service tree.
6.
Primary RSG
Secondary RSG
Route Type
Direct
Direct
Issue 01 (2014-01-31)
Parameter
Primary RSG
Secondary RSG
Route Type
Static
Static
MED Value
10
100
437
Primary RSG
Secondary RSG
Route Type
IS-IS
IS-IS
Instance ID
MED Value
10
100
NOTE
Choose Route Management > IS-IS Route > IS-IS Process from Service Tree in the NE
Explorer, and in the dialog box that is displayed, click Query.
2.
Select a process to be configured, click Configure. The Configure IS-IS Process dialog
box is displayed.
3.
Click the Advanced tab, and click Set in the IS-IS Adjustment and Optimization area.
Set parameters and click OK.
Table 4-32 IS-IS process-IS-IS adjustment and optimization parameters
4.
Issue 01 (2014-01-31)
Parameter
Primary RSG
Secondary RSG
SPF Timer
Max Interval: 1
Max Interval: 1
Initial Interval: 50
Initial Interval: 50
Increase Interval: 50
Increase Interval: 50
LSP Refresh
Timer
300
300
350
350
Level-2 Flash
Flood
Level-2 LSP
Timer
Max Interval: 1
Max Interval: 1
Initial Interval: 50
Initial Interval: 50
Increase Interval: 50
Increase Interval: 50
438
Follow-up Procedure
When configuring active and standby routes, configure static routes on the RNC. Ensure that
the routes are destined to the primary and secondary RSGs.
Verify Configurations
This topic describes how to check whether configurations are correct.
VRF Ping
1.
Choose Service > L3VPN Service > Manage L3VPN Service from the main menu.
2.
Select the desired Layer 3 Virtual Private Network (L3VPN) service and click the Service
Link tab.
3.
Right-click on the tab and choose Fast Diagnose from the shortcut menu.
4.
5.
For a peer relationship between ASGs and RSGs, configure it between the primary ASG and primary
RSG, or between the secondary ASG and secondary RSG with a priority. The ping operation will be
performed between each pair of peers. If the test result is successful for the priority peer relationship
but failed for non-priority peer relationship, the test is successful. If a peer relationship is configured
between the primary ASG and secondary RSG, ping packets are transmitted from the primary ASG
to the secondary RSG but returned from the secondary RSG to the secondary ASG, resulting in a
ping failure.
VRF Traceroute
1.
Choose Service > L3VPN Service > Manage L3VPN Service from the main menu.
2.
Right-click a Layer 3 virtual private network (L3VPN) service to be configured and choose
Test and Check from the shortcut menu. The Test and Check window is displayed.
3.
4.
Click OK.
5.
Configuration Process
This topic describes the process of deploying PWE3 services and related protection protocols.
Issue 01 (2014-01-31)
439
Multihop PWE3s are used to carry TDM services between the cell site gateway (CSG) and radio
service gateways (RSGs). Configuration processes are described by allowing for two livenetwork scenarios: building a new network and adding a base station.
NOTE
In the network topology, ASGs 3 and 4 respectively function as primary and secondary ASGs, and RSGs 5 and
6 respectively function as primary and secondary RSGs.
Configure E-APS.
E-APS and PW redundancy together protect services against faults on the primary RSG.
Configure PW redundancy.
PW redundancy protects services against CSG or RSG faults or faults on links between the
CSG and RSGs. You can configure PW redundancy during E2E service configuration.
l
Issue 01 (2014-01-31)
440
Configure BFD for PW on the primary and backup PWs between the CSG and RSGs to
accelerate PW fault detection.
Configure PW redundancy.
PW redundancy protects services against CSG or RSG faults or faults on links between the
CSG and RSGs. You can configure PW redundancy during E2E service configuration.
Data Planning
You must plan data as needed before deploying Pseudo Wire Emulation Edge-to-Edge (PWE3)
services and relevant protection protocols.
Table 4-33 E-APS protection group configured on a Cpos interface
Parameter
Value
Remarks
APS Group ID
10
N/A
Table 4-34 TDM service interface planning for the RNC side
Issue 01 (2014-01-31)
Parameter
Value
Remarks
Cpos-Trunk 0
N/A
Working Mode
Framed
If timeslot compression is
required in order to save
bandwidth resources, set this
parameter to Framed;
otherwise, set this parameter
to Unframed.
Channel ID
No.
N/A
Timeslot Sequence
1-15, 17-31
N/A
441
Table 4-35 TDM service interface planning for the base station side
Parameter
Value
Remarks
Working Mode
Framed
If timeslot compression is
required in order to save
bandwidth resources, set this
parameter to Framed;
otherwise, set this parameter
to Unframed.
This value must be the same
as that set for the RNC side.
No.
Timeslot Sequence
1-15, 17-31
NE Role
Peer NE
Peer LSR ID
CSG1
ASG3
3.3.3.3
ASG4
4.4.4.4
CSG1
1.1.1.1
RSG5
5.5.5.5
CSG1
1.1.1.1
RSG6
6.6.6.6
ASG3
3.3.3.3
RSG6
6.6.6.6
ASG4
4.4.4.4
RSG5
5.5.5.5
Parameter
Value
Remarks
50
N/A
50
N/A
ASG3
ASG4
RSG5
RSG6
Issue 01 (2014-01-31)
442
Configuration Object
Configure management PWs between primary and secondary RSGs.
Data Plan
Parameter
Management
PW ID
PW1: 150
PW1: 150
PW2: 151
PW2: 151
Loopback
interface
PW1: Loopback2
PW1: Loopback2
PW2: Loopback3
PW2: Loopback3
BFD session
name
PW1: RSG5_to_ac
PW1: RSG6_for_aps
PW2: RSG5_for_aps
PW2: RSG6_to_ac
Local BFD ID
PW1: 1500
PW1: 1500
PW2: 2500
PW2: 2500
Remote BFD
ID
BFD
detection
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
Step 2 Set basic attributes. Set Service Type to Management PW and set other parameters as planned.
Issue 01 (2014-01-31)
443
In Physical Topology in the upper-right part, right-click the primary RSG, and choose
Select Source from the shortcut menu.
2.
In the Create SAI dialog box, select an existing loopback interface; or click Create >
Loopback and in the dialog box that is displayed, enter Interface No. and click OK to
create a loopback interface.
NOTE
3.
In Physical Topology in the upper-right part, right-click the secondary RSG, and choose
Select Sink from the shortcut menu.
2.
In the Create SAI dialog box, select an existing loopback interface; or click Create >
Loopback and in the dialog box that is displayed, enter Interface No. and click OK to
create a loopback interface.
NOTE
3.
444
On the Service Topology tab, right-click and select Create LDP Remote Peer to create an LDP
remote peer quickly.
Step 6 Configure the tunnel policy.
In the PW area of the lower left pane, set both Forward Type and Reverse Type to AutoCreate
Order Policy.
2.
In the area that shows the detailed settings, click the Advanced PW Attribute tab and set
Control Word to Use required.
Issue 01 (2014-01-31)
Parameter
Configuration Requirements
BFD Name
Set the BFD name according to the data plan. If you do not set it, the
system automatically allocates one.
Bound Service
Type
445
Parameter
Configuration Requirements
Detection Object
Local BFD ID
The local BFD ID must be consistent with the remote BFD ID of the
peer NE.
Remote BFD ID
The remote BFD ID must be consistent with the local BFD ID of the
peer NE.
Min.Sending
Interval
100
Min.Receiving
Interval
100
Configuring E-APS
When APS protection needs to be between the active and standby CSG->RSG PWs or between
RSG nodes, you can configure E-APS on the service interface of primary and secondary RSGs
to implement APS switching between RSGs in case of emergency. For E-APS between RSG
nodes, you can choose either 1+1 or 1:1 protection.
Configuration Object
l
Issue 01 (2014-01-31)
For APS protection between the active and standby CSG->RSG PWs, configure primary
and secondary RSGs as the left and right nodes of E-APS.
446
E-APS also needs to be configured on the base station controller (BSC) connected to the
RSGs. For details about the E-APS configuration on the BSC, see BSC manuals.
Procedure
Step 1 (Optional) Set the RSG Cpos port connected to the RNC side to the UP state when receiving
optical signals. When the working mode of the protection group is 1+1 unidirectional
switching, set this parameter.
1.
In the NE Explorer, right-click the RSG, choose Service Tree > Interface Management
> Interface Information, and click Query.
2.
Select the Cpos interface, and click Configure. The Configure Cpos Interface dialog box
is displayed.
3.
4.
Click OK.
Step 2 Choose Configure > Node Redundancy > E-APS Management from the main menu.
Step 3 On the E-APS Management tab page, click Create.
Step 4 In the Create E-APS dialog box, set the related parameters.
NOTE
l E-APS 1+1 has four types: single-ended non-revertive, single-ended revertive, dual-ended non-revertive,
and dual-ended revertive. Single-ended non-revertive E-APS 1+1 is recommended.
l E-APS 1:1 has two types: dual-ended non-revertive and dual-ended revertive. Dual-ended revertive E-APS
1:1 is recommended.
Issue 01 (2014-01-31)
447
Parameter
Settings
NE Name
Sets RSG5 (primary RSG) as the left node and RSG6 (secondary RSG)
as the right node.
Interface Name
APS
APS Group ID
Sets this parameter as planned. The IDs for the local and peer NEs must
be the same.
Local IP
Peer IP
The local IP address of the local NE must be the same as the peer IP
address of the peer NE.
Keepalive Timer
Holdtime Timer
Protection Group
Operating Mode
Bound BFD
Session Name
Issue 01 (2014-01-31)
448
Configuration Object
The Cpos interface must be added to the Cpos-Trunk interface because the Cpos interface is
used for configuring E-APS that implements link protection between the RSG and the RNC side.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 On the Interface Information tab page, click Create and choose Create Main Interface >
Cpos-Trunk Interface.
Step 4 In the Create Cpos-Trunk Interface dialog box, set the relevant parameters.
1.
Click the General tab and set Interface No. on this tab page.
2.
Click the Member Interface tab and click Add. In the dialog box that is displayed, select
interfaces to be added from the Available Interface list on the left and click
All selected interfaces are added to the Selected Interface list. Click OK.
NOTICE
l Before configuring the Cpos-Trunk interface, make sure that E-APS has been configured.
l The "DS1 list" and the Cpos-Trunk interface cannot be configured at the same time. It can
only be configured in the Cpos-Trunk interface that already exists.
Step 5 Click OK. The Create Cpos-Trunk Interface dialog box is closed.
Step 6 Configure Cpos-Trunk interfaces on the secondary RSG in the same manner.
----End
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
Step 2 Set basic attributes. Set a PWE3 service profile that already exists on the Creating a PWE3
Template as a service profile.
Issue 01 (2014-01-31)
449
In Physical Topology in the upper-right part, right-click CSG1, and choose Select
Source from the shortcut menu.
2.
In Physical Topology in the upper-right part, right-click the primary RSG, and choose
Select Working-Sink from the shortcut menu.
2.
In Physical Topology in the upper-right part, right-click the secondary RSG, and choose
Select Protection-Sink from the shortcut menu.
2.
450
Select the service to be configured, right-click a blank area on the Topology tab, and select Legend to view
legend descriptions of the physical topology view. Legends help user learn object types and status of each legend
in the physical topology view.
----End
Verifying Configurations
This topic describes how to verify configurations.
VCCV Ping
1.
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2.
In the Set Filter Criteria dialog box, set search criteria and click Filter. All the qualified
services are displayed in the search result area.
3.
Right-click the desired service and choose Test And Check from the shortcut menu.
4.
In the Test And Check dialog box, choose Diagnosis Option > OAM Tool > VCCV
Ping in the Diagnosis Option area.
5.
(Optional)Click the button next to VCCV Ping and set advanced parameters:
Issue 01 (2014-01-31)
451
a.
If there is no direct route between the CSG and RSG, click the button next to VCCV
Ping and change Response Mode to Application Control Channel.
b.
For switch nodes, set VCCV Capability Type to Lable Alart; for other nodes, select
Control Word.
6.
Click Run.
7.
After VCCV test is completed, test results are displayed in the lower Check Result area,
among which Check Result is displayed as Operation Succeeded.
Connectivity Test
NOTE
For ATM services, set the LLID before performing connectivity tests. You can set or query the LLID by choosing
Service Tree > Reliability > OAM Management > ATM OAM Management > Global ATM OAM
Configuration in the NE Explorer.
1.
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2.
In the Set Filter Criteria dialog box, set search criteria and click Filter. All the qualified
services are displayed in the search result area.
3.
Right-click a service to be tested and choose Connectivity Test from the shortcut menu.
4.
In the Connectivity Test dialog box, set the source and sink loopback status, and click
Start.
5.
After the test is complete, the Check Result is displayed as Operation Succeeded.
Configuration Process
This section describes the process of configuring single-homed MS-PW TDM services and
protection.
As shown in the following figure, MS-PWs are established between the cell site gateway (CSG)
and radio service gateway (RSG).
Issue 01 (2014-01-31)
452
The following table shows the process of configuring single-homed MS-PW services.
RNCSupports APS Protection
Verifying Configurations
Verifying Configurations
NOTICE
If the hot backup or APS protection is deployed for tunnels carrying ATM or TDM services,
ensure that the detection period of BFD for PW is longer than the latency of LSP or APS
switchover. This prevents repeated switchover.
Data Plan
To deploy single-homed MS-PW TDM services and protection, plan the following data.
Issue 01 (2014-01-31)
453
Value
Remarks
APS Group ID
10
N/A
Table 4-39 TDM service interface planning for the RNC side
Parameter
Value
Remarks
Cpos-Trunk 0
N/A
Working Mode
Framed
If timeslot compression is
required in order to save
bandwidth resources, set this
parameter to Framed;
otherwise, set this parameter
to Unframed.
Channel ID
No.
N/A
Timeslot Sequence
1-15, 17-31
N/A
Table 4-40 TDM service interface planning for the base station side
Parameter
Value
Remarks
Working Mode
Framed
If timeslot compression is
required in order to save
bandwidth resources, set this
parameter to Framed;
otherwise, set this parameter
to Unframed.
This value must be the same
as that set for the RNC side.
Issue 01 (2014-01-31)
No.
Timeslot Sequence
1-15, 17-31
454
Peer NE
Peer LSR ID
CSG1
ASG3
3.3.3.3
ASG4
4.4.4.4
CSG1
1.1.1.1
RSG5
5.5.5.5
ASG4
CSG1
1.1.1.1
RSG5
ASG3
3.3.3.3
Parameter
Value
Remarks
50
N/A
50
N/A
ASG3
Configuration Object
l
Select the primary RSG as both the left and right NEs for E-APS.
E-APS also needs to be configured on the base station controller (BSC) connected to the
RSGs. For details about the E-APS configuration on the BSC, see BSC manuals.
Procedure
Step 1 Choose Configure > Node Redundancy > E-APS Management from the main menu.
Step 2 On the E-APS Management tab page, click Create.
Step 3 In the Create E-APS dialog box, set the related parameters.
Parameter
Settings
NE Name
Sets RSG5 (primary RSG) as both the left and right nodes.
Interface Name
APS
Issue 01 (2014-01-31)
455
Parameter
Settings
APS Group ID
Sets the APS group ID according to the data plan. The left and right
nodes have the same group ID.
Protection Group
Operating Mode
In the NE Explorer, right-click the RSG, choose Service Tree > Interface Management
> Interface Information, and click Query.
2.
Select the Cpos interface, and click Configure. The Configure Cpos Interface dialog box
is displayed.
3.
Issue 01 (2014-01-31)
456
4.
Click OK.
Step 6 (Optional) Set the RSG ATM port (for the ATM service) connected to the RNC side to the UP
state when receiving optical signals. When the working mode of the protection group is 1+1
unidirectional switching, set this parameter.
1.
In the Main Topology, right-click an RSG and choose Tools > Telnet from the shortcut
menu.
2.
In the dialog box that is displayed, enter the user name and password of the login NE.
3.
4.
Run the interface interface-type interface-number command to enter the ATM interface
view.
5.
6.
----End
Configuration Object
Configure the RSG.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Issue 01 (2014-01-31)
457
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 On the Interface Information tab page, click Create and choose Create Main Interface >
Cpos-Trunk Interface.
Step 4 In the Create Cpos-Trunk Interface dialog box, set the relevant parameters.
1.
Click the General tab and set Interface No. on this tab page.
2.
Click the Member Interface tab and click Add. In the dialog box that is displayed, select
.
interfaces to be added from the Available Interface list on the left and click
All selected interfaces are added to the Selected Interface list. Click OK.
NOTICE
l Before configuring the Cpos-Trunk interface, make sure that E-APS has been configured.
l The "DS1 list" and the Cpos-Trunk interface cannot be configured at the same time. It can
only be configured in the Cpos-Trunk interface that already exists.
Step 5 Click OK. The Create Cpos-Trunk Interface dialog box is closed.
Step 6 Configure Cpos-Trunk interfaces on the secondary RSG in the same manner.
----End
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
Step 2 Set basic attributes. Set a PWE3 service profile that already exists on the Creating a PWE3
Template as a service profile.
In Physical Topology in the upper-right part, right-click CSG1, and choose Select
Source from the shortcut menu.
2.
Issue 01 (2014-01-31)
458
In Physical Topology in the upper-right part, right-click RSG5, and choose Select Sink
from the shortcut menu.
2.
In Physical Topology in the upper-right part, right-click the primary ASG, and choose Set
As Switching Node > Working from the shortcut menu.
2.
In Physical Topology in the upper-right part, right-click the primary ASG, and choose Set
As Switching Node > Protection from the shortcut menu.
Issue 01 (2014-01-31)
459
Step 9 Click Apply or OK to apply PWE3 services to NEs. The Operation Result prompt is displayed.
Click Browse Trail to view PW configurations. Running Status is Up, Alarm Severity is
Normal, Deployment Status is Deployed, and Enabling Status is Enabled.
NOTE
Select the service to be configured, right-click a blank area on the Topology tab, and select Legend to view
legend descriptions of the physical topology view. Legends help user learn object types and status of each legend
in the physical topology view.
----End
Verifying Configurations
This topic describes how to verify configurations.
VCCV Ping
1.
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2.
In the Set Filter Criteria dialog box, set search criteria and click Filter. All the qualified
services are displayed in the search result area.
3.
Right-click the desired service and choose Test And Check from the shortcut menu.
4.
In the Test And Check dialog box, choose Diagnosis Option > OAM Tool > VCCV
Ping in the Diagnosis Option area.
5.
(Optional)Click the button next to VCCV Ping and set advanced parameters:
a.
If there is no direct route between the CSG and RSG, click the button next to VCCV
Ping and change Response Mode to Application Control Channel.
b.
For switch nodes, set VCCV Capability Type to Lable Alart; for other nodes, select
Control Word.
6.
Click Run.
7.
After VCCV test is completed, test results are displayed in the lower Check Result area,
among which Check Result is displayed as Operation Succeeded.
Connectivity Test
NOTE
For ATM services, set the LLID before performing connectivity tests. You can set or query the LLID by choosing
Service Tree > Reliability > OAM Management > ATM OAM Management > Global ATM OAM
Configuration in the NE Explorer.
1.
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2.
In the Set Filter Criteria dialog box, set search criteria and click Filter. All the qualified
services are displayed in the search result area.
Issue 01 (2014-01-31)
460
3.
Right-click a service to be tested and choose Connectivity Test from the shortcut menu.
4.
In the Connectivity Test dialog box, set the source and sink loopback status, and click
Start.
5.
After the test is complete, the Check Result is displayed as Operation Succeeded.
Configuration Process
This topic describes the process of deploying PWE3 services and related protection protocols.
Figure 4-9 Network topology with multihop PWs
In the mixed VPN solution, the multihop PWE3 is used to carry asynchronous transfer mode
(ATM) services between the cell site gateway (CSG) and radio service gateways (RSGs).
Configuration processes are described by allowing for two live-network scenarios: building a
new network and adding a base station.
NOTE
In the network topology, ASGs 3 and 4 respectively function as primary and secondary ASGs, and RSGs 5 and
6 respectively function as primary and secondary RSGs.
Issue 01 (2014-01-31)
461
Configure PW redundancy.
PW redundancy protects services against CSG or RSG faults or faults on links between the
CSG and RSGs. You can configure PW redundancy during E2E service configuration.
Configure E-APS.
E-APS and PW redundancy together protect services against faults on the primary RSG.
Configure PW redundancy.
PW redundancy protects services against CSG or RSG faults or faults on links between the
CSG and RSGs. You can configure PW redundancy during E2E service configuration.
Data Plan
To deploy PWE3 services and related protection protocols, plan the following data.
Issue 01 (2014-01-31)
462
Value
Remarks
APS Group ID
20
N/A
Value
VPI/VCI
Atm-Trunk 1
N/A
Atm-Trunk1.1
10/90
Parameter
Value
Remarks
Work Mode
Framing mode
Channel Set ID
64k Timeslot
1-15, 17-31
Table 4-46 ATM interface planning for the base station side
Parameter
Value
VPI/VCI
Ima-group0/2/1
N/A
Ima-group0/2/1.1
10/90
NE Role
Peer NE
Peer LSR ID
CSG1
ASG3
3.3.3.3
ASG4
4.4.4.4
CSG1
1.1.1.1
RSG5
5.5.5.5
CSG1
1.1.1.1
RSG6
6.6.6.6
ASG3
ASG4
Issue 01 (2014-01-31)
463
NE Role
Peer NE
Peer LSR ID
RSG5
ASG3
3.3.3.3
RSG6
6.6.6.6
ASG4
4.4.4.4
RSG5
5.5.5.5
Parameter
Value
Remarks
50
50
RSG6
Configuration Object
Configure management PWs between primary and secondary RSGs.
Data Plan
Parameter
Management
PW ID
PW1: 150
PW1: 150
PW2: 151
PW2: 151
Loopback
interface
PW1: Loopback2
PW1: Loopback2
PW2: Loopback3
PW2: Loopback3
BFD session
name
PW1: RSG5_to_ac
PW1: RSG6_for_aps
PW2: RSG5_for_aps
PW2: RSG6_to_ac
Local BFD ID
PW1: 1500
PW1: 1500
PW2: 2500
PW2: 2500
Remote BFD
ID
Issue 01 (2014-01-31)
464
Parameter
BFD
detection
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
Step 2 Set basic attributes. Set Service Type to Management PW and set other parameters as planned.
In Physical Topology in the upper-right part, right-click the primary RSG, and choose
Select Source from the shortcut menu.
2.
In the Create SAI dialog box, select an existing loopback interface; or click Create >
Loopback and in the dialog box that is displayed, enter Interface No. and click OK to
create a loopback interface.
NOTE
Issue 01 (2014-01-31)
465
3.
In Physical Topology in the upper-right part, right-click the secondary RSG, and choose
Select Sink from the shortcut menu.
2.
In the Create SAI dialog box, select an existing loopback interface; or click Create >
Loopback and in the dialog box that is displayed, enter Interface No. and click OK to
create a loopback interface.
NOTE
3.
2.
In the area that shows the detailed settings, click the Advanced PW Attribute tab and set
Control Word to Use required.
466
Step 10 Right-click the PWE3 service in the service list, and choose Configure BFD from the shortcut
menu. The BFD Session Configuration Management dialog box is displayed.
Step 11 Click Create. The Batch Configure BFD Session dialog box is displayed.
Step 12 Click Configure. In the dialog box that is displayed, set BFD parameters for each NE and click
OK after parameters are set. Set key parameters according to the following requirements, and
set the other parameters as required or use default values.
Parameter
Configuration Requirements
BFD Name
Set the BFD name according to the data plan. If you do not set it, the
system automatically allocates one.
Bound Service
Type
Detection Object
Local BFD ID
The local BFD ID must be consistent with the remote BFD ID of the
peer NE.
Remote BFD ID
The remote BFD ID must be consistent with the local BFD ID of the
peer NE.
Min.Sending
Interval
100
Min.Receiving
Interval
100
467
Configuring E-APS
When APS protection needs to be between the active and standby CSG->RSG PWs or between
RSG nodes, you can configure E-APS on the service interface of primary and secondary RSGs
to implement APS switching between RSGs in case of emergency. For E-APS between RSG
nodes, you can choose either 1+1 or 1:1 protection.
Configuration Object
l
For APS protection between the active and standby CSG->RSG PWs, configure primary
and secondary RSGs as the left and right nodes of E-APS.
E-APS also needs to be configured on the base station controller (BSC) connected to the
RSGs. For details about the E-APS configuration on the BSC, see BSC manuals.
Procedure
Step 1 Choose Configure > Node Redundancy > E-APS Management from the main menu.
Step 2 On the E-APS Management tab page, click Create.
Step 3 In the Create E-APS dialog box, set the related parameters.
NOTE
l E-APS 1+1 has four types: single-ended non-revertive, single-ended revertive, dual-ended non-revertive,
and dual-ended revertive. Single-ended non-revertive E-APS 1+1 is recommended.
l E-APS 1:1 has two types: dual-ended non-revertive and dual-ended revertive. Dual-ended revertive E-APS
1:1 is recommended.
Parameter
Settings
NE Name
Sets RSG5 (primary RSG) as the left node and RSG6 (secondary RSG)
as the right node.
Interface Name
APS
APS Group ID
Sets this parameter as planned. The IDs for the local and peer NEs must
be the same.
NOTE
APS Group ID for an ATM interface that has been added to the ATM-Trunk
cannot be set or modified. To set or modify APS Group ID, remove the ATM
interface from the ATM-Trunk.
Issue 01 (2014-01-31)
Local IP
Peer IP
The local IP address of the local NE must be the same as the peer IP
address of the peer NE.
Keepalive Timer
Holdtime Timer
468
Parameter
Settings
Protection Group
Operating Mode
Bound BFD
Session Name
In the Main Topology, right-click an RSG and choose Tools > Telnet from the shortcut
menu.
2.
In the dialog box that is displayed, enter the user name and password of the login NE.
3.
4.
Run the interface interface-type interface-number command to enter the ATM interface
view.
5.
6.
----End
Issue 01 (2014-01-31)
469
Configuration Objects
The ATM interfaces that are used for configuring E-APS need to be added to Atm-Trunk
interfaces.
ATM service interfaces need to be configured on the primary and secondary RSGs.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 On the Interface Information tab page, click Create and choose Create Main Interface >
Atm-Trunk Interface.
Step 4 In the Create Atm-Trunk Interface dialog box, set the relevant parameters.
1.
Click the General tab and set Interface No. according to the data plan.
2.
(Optional) Click the ATM Feature tab and select ATM Cell Transfer. To use the ATM
cell transfer mode, select ATM Cell Transfer; to use a non-transfer mode, deselect it. (The
ATM cell transfer mode requires support of ATM subboards.)
3.
Click the Member Interface tab and click Add. In the dialog box that is displayed, select
the desired interface from the Available Interface list on the left and click
selected interface is added to the Selected Interface list. Then click OK.
. The
4.
5.
On the Interface Information tab page, select the configured ATM-Trunk interface, rightclick, and choose Synchronize from the shortcut menu. In the lower part of the window,
the value of Operating Status is Up.
Step 5 Set the working mode of ATM subboards to ATM cell transfer mode.
1.
In the Main Topology, right-click an RSG and choose Tools > Telnet from the shortcut
menu.
2.
In the dialog box that is displayed, enter the user name and password of the login NE.
3.
4.
Run the set service-mode slot slotid cell-concatenation-mode command. slotid is the ID
of the slot where the ATM subboard resides.
5.
----End
470
Configuration Objects
ATM service interfaces need to be configured for all CSGs.
Procedure
Step 1 Configure an E1 interface.
1.
Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
2.
Choose Interface Management > Interface Information from the service tree.
3.
4.
In the Configure E1 Interface dialog box, click the Physical Feature tab.
5.
6.
In the Add Timeslot Binding dialog box, set No. and Timeslot Sequence according to the
planning.
7.
8.
Click OK. The Configure E1 Interface dialog box is displayed. After you click Query,
serial interfaces named in the format of "E1 interface number + sequence number", such
as Serial 0/2/1:1, are displayed on the Interface Information tab page.
9.
Configure other E1 interfaces that need to be bound to an Inverse Multiplexing Over ATM
(IMA) group in the same manner.
2.
In the Configure Serial Interface dialog box, click the Serial Feature tab.
3.
Set Link Layer Protocol to ATM and use the default values for other parameters.
4.
On the Interface Information tab page, click Create and choose Create Main
Interface > IMA Interface.
2.
In the Create IMA Interface dialog box, set Interface No.. The format subrack number/
slot number/IMA group number is recommended.
3.
4.
In the Add Member Interface dialog box, select the desired interface from the Available
Interface list on the left and click
Interface list. Then click OK.
5.
----End
471
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
Step 2 Set basic attributes of PWE3 services. Set a PWE3 service profile that already exists on the
Creating a PWE3 Template as a service profile.
2.
In the Create SAI dialog box, select a configured IMA interface, and set an IMA
subinterface by entering ID on the SAI Configuration tab. Then click OK.
In Physical Topology in the upper-right part, right-click the primary RSG CX600EE-001,
and choose Select Working-Sink from the shortcut menu.
2.
In the Create SAI dialog box, select a configured Atm-Trunk interface, and set an AtmTrunk subinterface by entering ID on the SAI Configuration tab. Then click OK.
In Physical Topology in the upper-right part, right-click the secondary RSG RSG CX600
FF-001, and choose Select Protection-Sink from the shortcut menu.
2.
In the Create SAI dialog box, select a configured Atm-Trunk interface, and set an AtmTrunk subinterface by entering ID on the SAI Configuration tab. Then click OK.
Issue 01 (2014-01-31)
472
2.
In the Configure Link dialog box, click Add Working Link and then Add Protection
Link.
3.
Select the working link and set Source VPI, Source VCI, Sink VPI, and Sink VCI for it
according to the data plan.
4.
Click OK.
Step 11 (Optional) Configure a PW template. This step is required only when the ATM subboard does
not support cascading.
1.
2.
Issue 01 (2014-01-31)
473
3.
Respectively click the cells under Source PW Template and Sink PW Template and click
the "..." button that is displayed. Then, select the PW template that has been created in
Configuring a PW Template for ATM Services in the dialog box that is displayed.
4.
Configure the source and sink templates for other PWs in the same manner.
Step 12 Click Apply or OK to apply PWE3 services to NEs. The Operation Result prompt is displayed.
Click Browse Trail to view PW configurations. Running Status is Up, Alarm Severity is
Normal, Deployment Status is Deployed, and Enabling Status is Enabled.
NOTE
Select the service to be configured, right-click a blank area on the Topology tab, and select Legend to view
legend descriptions of the physical topology view. Legends help user learn object types and status of each legend
in the physical topology view.
----End
Verifying Configurations
This topic describes how to verify configurations.
VCCV Ping
1.
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2.
In the Set Filter Criteria dialog box, set search criteria and click Filter. All the qualified
services are displayed in the search result area.
3.
Right-click the desired service and choose Test And Check from the shortcut menu.
4.
In the Test And Check dialog box, choose Diagnosis Option > OAM Tool > VCCV
Ping in the Diagnosis Option area.
5.
(Optional)Click the button next to VCCV Ping and set advanced parameters:
a.
If there is no direct route between the CSG and RSG, click the button next to VCCV
Ping and change Response Mode to Application Control Channel.
b.
For switch nodes, set VCCV Capability Type to Lable Alart; for other nodes, select
Control Word.
6.
Click Run.
7.
After VCCV test is completed, test results are displayed in the lower Check Result area,
among which Check Result is displayed as Operation Succeeded.
Connectivity Test
NOTE
For ATM services, set the LLID before performing connectivity tests. You can set or query the LLID by choosing
Service Tree > Reliability > OAM Management > ATM OAM Management > Global ATM OAM
Configuration in the NE Explorer.
1.
Issue 01 (2014-01-31)
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
474
2.
In the Set Filter Criteria dialog box, set search criteria and click Filter. All the qualified
services are displayed in the search result area.
3.
Right-click a service to be tested and choose Connectivity Test from the shortcut menu.
4.
In the Connectivity Test dialog box, set the source and sink loopback status, and click
Start.
5.
After the test is complete, the Check Result is displayed as Operation Succeeded.
Configuration Process
This section describes the process of configuring single-homed MS-PW ATM services and
protection.
As shown in the following figure, MS-PWs are established between the cell site gateway (CSG)
and radio service gateway (RSG).
Figure 4-10 Redundancy protection topology for single-homed MS-PWs
2.
3.
Issue 01 (2014-01-31)
475
4.
Configure MS-PW services on the CSG and RSG, and PW exchange on ASGs.
5.
Configure static BFD for PW between the CSG and RSG to accelerate the switchover
between the primary and backup PWs in case of faults.
NOTICE
If the hot backup or APS protection is deployed for tunnels carrying ATM or TDM services,
ensure that the detection period of BFD for PW is longer than the latency of LSP or APS
switchover. This prevents repeated switchover.
Data Plan
To deploy single-homed MS-PW ATM services and protection, plan the following data.
Table 4-49 E-APS protection group configured on an ATM interface
Parameter
Value
Remarks
APS Group ID
20
N/A
Value
VPI/VCI
Atm-Trunk 1
N/A
Atm-Trunk1.1
10/90
Parameter
Value
Remarks
Work Mode
Framing mode
Channel Set ID
64k Timeslot
1-15, 17-31
Table 4-52 ATM interface planning for the base station side
Issue 01 (2014-01-31)
Parameter
Value
VPI/VCI
Ima-group0/2/1
N/A
476
Parameter
Value
VPI/VCI
Ima-group0/2/1.1
10/90
Peer NE
Peer LSR ID
CSG1
ASG3
3.3.3.3
ASG4
4.4.4.4
CSG1
1.1.1.1
RSG5
5.5.5.5
ASG4
CSG1
1.1.1.1
RSG5
ASG3
3.3.3.3
Parameter
Value
Remarks
Min. Receiving
Interval(ms)
50
Min. Sending
Interval(ms)
50
ASG3
Configuration Object
l
Select the primary RSG as both the left and right NEs for E-APS.
E-APS also needs to be configured on the base station controller (BSC) connected to the
RSGs. For details about the E-APS configuration on the BSC, see BSC manuals.
Procedure
Step 1 Choose Configure > Node Redundancy > E-APS Management from the main menu.
Step 2 On the E-APS Management tab page, click Create.
Issue 01 (2014-01-31)
477
Step 3 In the Create E-APS dialog box, set the related parameters.
Parameter
Settings
NE Name
Sets RSG5 (primary RSG) as both the left and right nodes.
Interface Name
APS
APS Group ID
Sets the APS group ID according to the data plan. The left and right
nodes have the same group ID.
Protection Group
Operating Mode
In the NE Explorer, right-click the RSG, choose Service Tree > Interface Management
> Interface Information, and click Query.
2.
Select the Cpos interface, and click Configure. The Configure Cpos Interface dialog box
is displayed.
3.
Issue 01 (2014-01-31)
478
4.
Click OK.
Step 6 (Optional) Set the RSG ATM port (for the ATM service) connected to the RNC side to the UP
state when receiving optical signals. When the working mode of the protection group is 1+1
unidirectional switching, set this parameter.
1.
In the Main Topology, right-click an RSG and choose Tools > Telnet from the shortcut
menu.
2.
In the dialog box that is displayed, enter the user name and password of the login NE.
3.
4.
Run the interface interface-type interface-number command to enter the ATM interface
view.
5.
6.
----End
Configuration Objects
ATM service interfaces need to be configured for all CSGs.
Procedure
Step 1 Configure an E1 interface.
1.
Issue 01 (2014-01-31)
Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
479
2.
Choose Interface Management > Interface Information from the service tree.
3.
4.
In the Configure E1 Interface dialog box, click the Physical Feature tab.
5.
6.
In the Add Timeslot Binding dialog box, set No. and Timeslot Sequence according to the
planning.
7.
8.
Click OK. The Configure E1 Interface dialog box is displayed. After you click Query,
serial interfaces named in the format of "E1 interface number + sequence number", such
as Serial 0/2/1:1, are displayed on the Interface Information tab page.
9.
Configure other E1 interfaces that need to be bound to an Inverse Multiplexing Over ATM
(IMA) group in the same manner.
2.
In the Configure Serial Interface dialog box, click the Serial Feature tab.
3.
Set Link Layer Protocol to ATM and use the default values for other parameters.
4.
On the Interface Information tab page, click Create and choose Create Main
Interface > IMA Interface.
2.
In the Create IMA Interface dialog box, set Interface No.. The format subrack number/
slot number/IMA group number is recommended.
3.
4.
In the Add Member Interface dialog box, select the desired interface from the Available
Interface list on the left and click
Interface list. Then click OK.
5.
----End
Configuration Object
Configure the RSG.
Procedure
l
Issue 01 (2014-01-31)
If the NodeB supports APS protection, you are advised to use the ATM-Trunk interface.
1.
Right-click the NE in the Main Topology and choose NE Explorer from the shortcut
menu.
2.
Choose Interface Management > Interface Information from the service tree.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
480
3.
On the Interface Information tab page, click Create and choose Create Main
Interface > Atm-Trunk Interface.
4.
In the Create Atm-Trunk Interface dialog box, set the relevant parameters.
a.
Click the General tab and set Interface No. according to the planning.
b.
(Optional) Click the ATM Feature tab and select ATM Cell Transfer. To use
the ATM cell transfer mode, select ATM Cell Transfer; to use a non-transfer
mode, deselect it. (The ATM cell transfer mode requires support of ATM
subboards.)
c.
Click the Member Interface tab and click Add. In the dialog box that is
displayed, select the desired interface from the Available Interface list on the
left and click
. The selected interface is added to the Selected
Interface list. Then click OK.
d.
e.
If the base station does not support APS protection, the ATM interface is recommended.
In this situation, the ATM interface does not need to be configured.
Set the working mode of ATM subboards to ATM cell transfer mode.
1.
In the Main Topology, right-click an RSG and choose Tools > Telnet from the shortcut
menu.
2.
In the dialog box that is displayed, enter the user name and password of the login NE.
3.
4.
5.
----End
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
Step 2 Set basic attributes. Set a PWE3 service profile that already exists on the Creating a PWE3
Template as a service profile.
Issue 01 (2014-01-31)
481
In Physical Topology in the upper-right part, right-click CSG1, and choose Select
Source from the shortcut menu.
2.
In the Create SAI dialog box, select a configured IMA primary interface and set ID on the
SAI Configuration tab to set this interface as the IMA subinterface. Then click OK.
In Physical Topology in the upper-right part, right-click CSG5, and choose Select Sink
from the shortcut menu.
2.
In the Create SAI dialog box, select a configured Atm-Trunk or ATM interface, and set
an Atm-Trunk or ATM subinterface by entering ID on the SAI Configuration tab. Then
click OK.
In Physical Topology in the upper-right part, right-click the primary ASG, and choose Set
As Switching Node > Working from the shortcut menu.
2.
In Physical Topology in the upper-right part, right-click the primary ASG, and choose Set
As Switching Node > Protection from the shortcut menu.
2.
In the Configure Link dialog box, click Add Link and set Source VPI, Source VCI, Sink
VPI, and Sink VCI for the link according to the data plan.
3.
Click OK.
Step 9 (Optional) Configure a PW template. This step is required when the ATM subboard does not
cascading.
1.
Issue 01 (2014-01-31)
482
2.
3.
Respectively click the cells under Source PW Template and Sink PW Template and click
the "..." button that is displayed. Then, select the PW template that has been created in
Configuring a PW Template for ATM Services in the dialog box that is displayed.
4.
Configure the source and sink templates for other PWs in the same manner.
Step 10 Click Detail in the lower right part of left pane, and click the Service Parameter tab in the lower
part of right pane. Set Reversion Delay Time to 500.
Step 11 Click Apply or OK to apply PWE3 services to NEs. The Operation Result prompt is displayed.
Click Browse Trail to view PW configurations. Running Status is Up, Alarm Severity is
Normal, Deployment Status is Deployed, and Enabling Status is Enabled.
NOTE
Select the service to be configured, right-click a blank area on the Topology tab, and select Legend to view
legend descriptions of the physical topology view. Legends help user learn object types and status of each legend
in the physical topology view.
----End
Verifying Configurations
This topic describes how to verify configurations.
VCCV Ping
1.
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2.
In the Set Filter Criteria dialog box, set search criteria and click Filter. All the qualified
services are displayed in the search result area.
3.
Right-click the desired service and choose Test And Check from the shortcut menu.
Issue 01 (2014-01-31)
483
4.
In the Test And Check dialog box, choose Diagnosis Option > OAM Tool > VCCV
Ping in the Diagnosis Option area.
5.
(Optional)Click the button next to VCCV Ping and set advanced parameters:
a.
If there is no direct route between the CSG and RSG, click the button next to VCCV
Ping and change Response Mode to Application Control Channel.
b.
For switch nodes, set VCCV Capability Type to Lable Alart; for other nodes, select
Control Word.
6.
Click Run.
7.
After VCCV test is completed, test results are displayed in the lower Check Result area,
among which Check Result is displayed as Operation Succeeded.
Connectivity Test
NOTE
For ATM services, set the LLID before performing connectivity tests. You can set or query the LLID by choosing
Service Tree > Reliability > OAM Management > ATM OAM Management > Global ATM OAM
Configuration in the NE Explorer.
1.
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2.
In the Set Filter Criteria dialog box, set search criteria and click Filter. All the qualified
services are displayed in the search result area.
3.
Right-click a service to be tested and choose Connectivity Test from the shortcut menu.
4.
In the Connectivity Test dialog box, set the source and sink loopback status, and click
Start.
5.
After the test is complete, the Check Result is displayed as Operation Succeeded.
Configuration Process
This topic describes the process for configuring SD bit error detection.
l
Configure the MPLS label distribution mode to non-null using the U2000 IP plug-and-play
management function.
For the MPLS L2VPN service with the PW redundancy protection, configure SD bit error
detection for AC interfaces and intermediate nodes (multi-segment PWs) on the U2000 to
trigger protection switching.
484
Configuration Object
Configure bit error detection thresholds for ports on links to be tested.
NOTE
You can use a template of the U2000 IP plug-and-play management function to bulk configure the thresholds.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 Click Query. All the qualified records are displayed.
Step 4 Select the desired interface and click Configure.
Step 5 In the dialog box that is displayed, click the Monitor Trap Threshold tab, select the CRC
Packet error ratio check box, and set Alarm threshold Coefficient, Resume threshold
Coefficient, Alarm threshold exponent, and Resume threshold exponent according to the
data plan.
Step 6 Select the Trigger LSP check box.
485
Configuration Object
Configure SD bit error detection on the source and sink nodes of primary and backup tunnels
on the bearer network.
Procedure
Step 1 Choose Service > Tunnel > Manage Tunnel from the main menu.
Step 2 In the Set Filter Criteria dialog box, set filter criteria and click Filter. All services meeting the
filter criteria are displayed.
Step 3 In the service list, select the tunnel for which to configure bit error detection. In the lower pane,
click the Bit Error Detection tab.
Step 4 Set Bit Error Detection Mode to Bidirectional.
Step 5 Click Select. In the Select Tunnel dialog box, select the mapping backward tunnel, and click
OK.
Configuration Object
Configure SD bit error detection on primary and backup PWs for low-speed services.
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
Step 2 In the Set Filter Criteria dialog box, set filter criteria and click Filter. All services meeting the
filter criteria are displayed.
Step 3 In the service list, right-click the desired PWE3 service and choose Bit Error Detect >
Enable from the shortcut menu.
----End
Issue 01 (2014-01-31)
486
Configuration Roadmap
Different clock deployment solutions are available for different synchronization requirements.
Multiple technologies can be used to transparently transmit clock signals. The recommended
solution is: using 1588v2 to achieve time synchronization, using synchronous Ethernet to
achieve frequency synchronization, and selecting sources according to Synchronization Status
Message (SSM).
l
To achieve time synchronization using 1588v2, see Selecting the Clock Source,
Configuring Synchronous Ethernet Clock, and Configuring the 1588v2 Clock.
NOTE
In this topology, ASG3 acts as the primary ASG, ASG4 as the secondary ASG, RSG5 as the primary RSG, and
RSG6 as the secondary RSG.
For the output clock interface, do not set a priority but enable clock synchronization. For the input clock interface,
set a priority according to the clock plan and enable clock synchronization.
In this scheme, the synchronous Ethernet clock is used to implement frequency synchronization
and the 1588v2 clock is used to implement time synchronization.
l
1588v2 clock
All the NEs reside in a 1588v2 clock domain and the primary and secondary RSGs have
external clock sources. The clock priorities for the primary and secondary RSGs must be
higher than those for other NEs and the clock priority for the primary RSG must be higher
Issue 01 (2014-01-31)
487
than that for the secondary RSG. The clock tracing relationship in the clock domain is
determined by the Best Master Clock (BMC) algorithm.
Data Planning
Plan different parameter values based on the different requirements of frequency
synchronization and time synchronization.
l
In this document, the RSGs are CX600-X8s and each RSG has three clock ports: bits0,
bits1, and bits2. The three clock ports can be used for both frequency synchronization and
phase synchronization. In this example, port bits2 is used to receive frequency
synchronization signals and port bits0 is used to receive time synchronization signals.
For synchronous Ethernet, source selection control is implemented by enabling SSM and
configuring clock signal priorities in the local priority list.
NOTE
For clock synchronization of synchronous Ethernet, the source selection sequence is: SSM clock quality
> local priority setting > clock source type.
l The priority list of SSM clock qualities is: PRC > SSUA > SSUB > SEC > DNU. Source selection
does not involve the sources not configured with priorities or with the quality of DNU.
l In local settings, the priority value can be set to 1 to 255. Smaller numbers indicate higher priorities.
Source selection does not involve the sources not configured with priorities.
l The priority of a BITS clock source is higher than a clock source connected to a service port.
When the BMC algorithm is used by a 1588v2-enabled device for source selection, priority1 of each
candidate time source is compared first, then the clock-class, clock-accuracy, and priority2. If priority1
of candidate time sources is the same, the clock-class is compared, and so on. The time source with the
highest priority is selected as the master clock. In this example, it is recommended that priority2 be used
for clock source selection. Retain the default settings for priority1, clock-class, and clock-accuracy.
Parameter
Value
Remarks
RS
G5
2mhz
bits0
Local
priority list
bits0
10
GE2/0/1
20
GE1/0/0
RS
G6
Issue 01 (2014-01-31)
2mhz
bits0
488
Obj
ect
Parameter
Local
priority list
Value
Remarks
bits0
20
GE2/0/1
10
GE1/0/0
AS
G
Local
priority list
GE2/1/0
10
GE1/0/0
20
CS
G1
Local
priority list
GE0/2/1
7
10
GE0/2/1
6
20
2mhz
bits0
FE0/2/18
Issue 01 (2014-01-31)
Obj
ect
Parameter
Value
Remarks
RS
G5
Device type
BC
bits0
1pps
ubx
Port delay
measurement
mechanism
Pdelay
Clock step
one-step
Ring-network
asymmetry automeasure function
enable
489
Obj
ect
Parameter
Value
Remarks
Quality
level
Priority
2
Device type
BC
bits0
1pps
ubx
Port delay
measurement
mechanism
Pdelay
Clock step
one-step
Ring-network
asymmetry automeasure function
enable
Priority
Quality
level
Priority
2
Port delay
measurement
mechanism
Pdelay
Device type
BC
Ring-network
asymmetry automeasure function
enable
Port delay
measurement
mechanism
Pdelay
Device type
BC
1pps
ubx
Priority
RS
G6
AS
G
CS
G1
Issue 01 (2014-01-31)
490
Obj
ect
Parameter
Value
Remarks
bits1
FE0/2/18
Ring-network
asymmetry automeasure function
enable
Importing Links
This topic describes how to import links to generate a clock topology before clock deployment.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave Link
Management from the main menu. The Fiber/Cable/Microwave Link Management window
is displayed.
Step 2 Right-click in a blank area and choose Import Link from the shortcut menu. The Import
Link dialog box is displayed.
491
Configuration Object
Perform configurations on the primary and secondary radio service gateways (RSGs) on the
bearer network.
Procedure
1.
Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
2.
Choose System Management > Clock Management > Physical Clock Management
from the navigation tree. Then, click the Other Clock Source subtab on the Clock
Source tab.
3.
Select the bits0 clock source, and set parameters on the General tab as follows:
l Select the Enable Clock check box.
l Set SSM Source Select Mode to Manual.
l Set Input SSM Class to Prc.
l Select the System Priority check box.
l Set System Priority to 10 (10 for the primary RSG and 20 for the secondary RSG)
l Set Clock Type to 2Mhz.
l Retain the default values of other parameters.
NOTE
In this example, external BITS signals are 2 MHz signals. If BITS signals are 2 Mbps signals, you do
not need to set the SSM Source Select Mode and Input SSM Class parameters, but need to set Clock
Type to 2Mbit/s.
Issue 01 (2014-01-31)
492
4.
Select the bits1 clock source, and set parameters on the General tab as follows:
l Set Clock Type to 1pps.
l Set Direction to In.
l Retain the default values of other parameters.
5.
On the Physical Clock Management tab, click the General subtab and set TOD
Format to Ubx.
6.
(Optional) On the Clock Source tab, click the Other Clock Source subtab, select the
ptp clock source, and set parameters in the lower pane as follows:
NOTE
Issue 01 (2014-01-31)
493
7.
Click Apply.
NOTE
Configuration Objects
Synchronous Ethernet clock needs to be configured for all NEs on the bearer network.
Procedure
1.
Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
2.
Choose System Management > Clock Management > Physical Clock Management
from the service tree. Then click the General tab and set relevant clock parameters.
l Select Enable Ethernet Synchronization.
l Select SSM Control.
l Use the default values for other parameters.
Issue 01 (2014-01-31)
494
3.
Click the Clock Source tab and then the Port Clock tab. Click Add. The Select
Interface dialog box is displayed.
4.
Select the interface that connects RSG5 to RSG6 and click OK.
5.
Select this interface, set the relevant parameters on the General tab page, and click Apply
NOTE
For the output clock interface, do not set a priority but enable clock synchronization. For the input
clock interface, set a priority according to the clock plan and enable clock synchronization.
For example, GE interface 1/1/2 is an output clock interface; therefore, enable clock
synchronization for it; GE interface 2/1/0 is an input clock interface and the interface
priority is 1; therefore, set the priority to 1 and enable clock synchronization for it.
Issue 01 (2014-01-31)
495
6.
In the dialog box displayed indicating that the operation is successful, click OK.
7.
Set clock information for the rest of the NEs according to the planning.
Issue 01 (2014-01-31)
496
NOTE
Clock synchronization must be enabled for the interface between the CSG and the base station.
Configuration Objects
The 1588v2 clock needs to be configured for all NEs on the bearer network.
Procedure
1.
In the NE Explorer, choose System Management > Clock Management > PTP
Clock Management from the service tree. The PTP Clock Management tab page is
displayed.
b.
Click the General tab and set the relevant parameters. Then click Apply.
l Select Enable PTP.
l Set Clock Domain according to the planning.
l Set Clock Type according to the planning.
l Select Enable Ring Fiber Asymmetry Measure.
2.
Issue 01 (2014-01-31)
Click the Clock Source tab and then the Port Clock Source tab. Click Add. The
Select Interface dialog box is displayed.
b.
497
c.
On the Port Clock Source tab page, select this interface, set the relevant parameters
on the Basic Information tab page, and click Apply.
l Select Enable PTP.
l Set Delay Mechanism to Pdelay.
l Set Clock Step to One-step.
3.
Issue 01 (2014-01-31)
d.
e.
Configure clock ports on the rest of the NEs according to the planning.
In the NE Explorer, choose System Management > Clock Management > PTP
Clock Management from the service tree. Click the Clock Source tab and then the
Local Clock Source tab.
b.
498
4.
Configure the 1588v2 clock for the rest of the NEs in the same manner.
Verifying Configurations
This topic explains how to verify configurations.
Procedure
Step 1 Select Clock View from the Current View drop-down list in the upper left part of the Main
Topology. Then select an IPRAN subnet from the navigation tree. The clock status of each NE
is displayed.
Step 2 Right-click in the Main Topology and choose Search Clock Link from the shortcut menu. The
Search Clock Link dialog box is displayed. Set the relevant parameters and click OK.
l Select 1588v2 and Synchronous ETH in the Clock Type area.
l Click Search from NE in the Search Mode area.
l Select IPRAN in the NE Search area.
Step 3 In the dialog box that is displayed, click Close. The clock tracing relationships between NEs are
displayed in the clock view. Check whether the relationships are the same as those planned. If
some relationships are different from those planned, check whether the clock parameters are set
according to the planning.
Step 4 Click Legend&Filter&Attribute and select the desired clock type on the Filter tab page.
Step 5 To clear clock configurations of an interface, perform the following operations:
1.
In the clock view, right-click an NE whose clock configurations need to be deleted, and
choose Configure Clock from the shortcut menu. The NE Explorer is displayed.
2.
On the PTP Clock Management tab, select Clock Source > Port Clock Source.
Issue 01 (2014-01-31)
499
3.
Select a clock source and click Delete. In the dialog box that is displayed, click OK.
You can delete all port clock sources of a device by selecting all of them and clicking
Delete.
4.
5.
On the Physical Clock Management tab, select Clock Source > Port Clock Source.
Issue 01 (2014-01-31)
500
6.
Select a clock source and click Delete. In the dialog box that is displayed, click OK.
You can delete all port clock sources of a device by selecting all of them and clicking
Delete.
7.
8.
Click Apply.
Issue 01 (2014-01-31)
501
9.
Click Synchronize.
----End
Configuration Object
This solution uses simple traffic classification to deploy QoS and set CAR parameters for the
network interface of CSGs and RSGs.
l
CAR: CAR parameters are configured in an HQoS profile for CSGs and RSGs and they
are applied to the network interface of CSGs and RSGs.
Configuration roadmap:
l
Create Diffserv profile example used to configure the service interface and network
interface of CSGs, ASGs, and RSGs.
NOTE
If priority mapping rules configured in the default profile are appropriate, use the default profile.
Create an HQoS profile used to configure CAR of the network interface of CSGs and RSGs.
Apply the profile to the interface.
Data Plan
Table 4-57 Data plan for the Diffserv profile
NE
Profile
Name
Direction
Priority
Type
Priority
CoS
Color
CSG1
example
Inbound
direction
DSCP
62
CS6
Green
Outbound
direction
DSCP
62
CS6
Green
ASG3
ASG4
RSG5
RSG6
Issue 01 (2014-01-31)
502
Profile
Name
General
Informatio
n
Queue
Priority
Scheduli
ng Mode
Shaping
Rate (kbit/
s)
CSG1
CSG_UNI
CIR: 4000
CS6
PQ
70
EF
PQ
200
AF1
WFQ
10
AF2
WFQ
10
AF3
WFQ
15
AF4
WFQ
15
BE
WFQ
10
CSG2
PIR: 4000
Outbound
direction
Weight
Profile
Name
General
Informatio
n
Queue
Priority
Scheduli
ng Mode
Shaping
Rate (kbit/
s)
RSG5
RSG_UNI
CIR: 10000
CS6
PQ
500
EF
PQ
2000
AF1
WFQ
10
AF2
WFQ
10
AF3
WFQ
15
AF4
WFQ
15
BE
WFQ
10
RSG6
PIR: 20000
Inbound
direction
Weight
Procedure
Step 1 Configure differentiated services for the outbound direction of the CSG user side.
1.
In the NE Explorer, right-click the CSG, choose Service Tree > VPN Management >
L3VPN Management > VRF Management, and click Query.
2.
Select the VRF and click Configure. The Configure VRF window is displayed.
3.
4.
5.
Click Apply.
503
1.
Choose Configuration > IP QoS Profile > DS Domain Profile from the main menu.
2.
On the DS Domain Profile tab page, right-click in the blank area and choose Add Global
Profile from the shortcut menu.
3.
In the Create DS Domain Profile dialog box, set Name to example. Then configure the
mapping between the Differentiated Services Code Point (DSCP) and Class of Service
(CoS) and set parameters in the Inbound Parameters area. Use the default values for the
parameters in the Outbound Parameters area.
4.
Click OK.
Right-click profile example, and choose Deploy to Interface from the shortcut menu. In
the dialog box that is displayed, select the service interface and network interface of CSGs,
ASG, and RSGs and add them to Selected Interface, and click OK.
Step 4 Disable PHB for the service interface of ASGs and RSGs.
1.
In the NE Explorer, right-click the CSG, choose Service Tree > QoS Management >
Configure Interface QoS, and click Query.
2.
3.
4.
Click Apply.
504
1.
Choose Configuration > IP QoS Profile > HQoS Profile from the main menu.
2.
On the HQoS Profile tab page, right-click in the blank area and choose Add Global
Profile from the shortcut menu.
3.
In the Create HQoS Profile dialog box, set Name to CSG_UNI and click Add.
4.
In the User Queue dialog box, click next to the Flow Queue Policy text box.
5.
In the Select Flow Queue Profile dialog box, right-click in the blank area and choose Add
Global Profile from the shortcut menu.
6.
In the Create Flow Queue Profile dialog box, set Name to CSG_UNI. Then set the
relevant parameters according to the planning. Click OK.
7.
In the Add User Queue dialog box, set CIR to 4000, PIR to 4000, and Direction to
Outbound. Then click OK.
Issue 01 (2014-01-31)
505
8.
9.
Create an HQoS profile by following the preceding procedure, name it RSG_UNI and set
other parameters according to the data plan.
Select the CSG_UNI profile, right-click, and choose Deploy to Interface from the shortcut
menu.
2.
In the Deploy HQoS Profile dialog box, select a UNI on the ATN and add it to the Selected
Interface list. Then click OK.
Select the RSG_UNI profile, right-click, and choose Deploy to Interface from the shortcut
menu.
2.
3.
Click OK.
----End
Configuration Roadmap
Three types of ATM services need to be configured and they are provided by the three user-side
IMA subinterfaces of the CSG and transmitted to the three ATM trunk subinterfaces of the RNC.
On the three IMA subinterfaces of the CSG, three types of ATM services are configured: cbr,
vbrNrt, and vbrRt.
On the three IMA trunk subinterfaces of the RSG, three types of ATM services are configured:
cbr, vbrNrt, and vbrRt.
Data Planning
Table 4-60 ATM QoS parameter planning
Issue 01 (2014-01-31)
Interface
Parameter
Value
Interface
Parameter
Value
Imagroup0/2/
1.1
Service Name/
Service Type
cbr
AtmTrunk0.1
Service Name/
Service Type
cbr
1000
100000
506
Interface
Imagroup0/2/
1.2
Imagroup0/2/
1.3
Parameter
Value
500
Service Name/
Service Type
ntr-vbr
Interface
Parameter
Value
50000
Service Name/
Service Type
ntr-vbr
2000
200000
Sustainable Cell
Rate (kbit/s)
2000
Sustainable Cell
Rate (kbit/s)
200000
Maximum Burst
Size (kpbs)
255
Maximum Burst
Size (kpbs)
255
500
500
Service Name/
Service Type
rt-vbr
Service Name/
Service Type
rt-vbr
2000
200000
Sustainable Cell
Rate (kbit/s)
2000
Sustainable Cell
Rate (kbit/s)
200000
Maximum Burst
Size (kpbs)
255
Maximum Burst
Size (kpbs)
255
500
500
AtmTrunk0.1
AtmTrunk0.1
Procedure
Step 1 Configure an ATM policy profile.
1.
Choose Configuration > IP QoS Profile > ATM Policy Profile from the main menu.
2.
On the ATM Policy Profile window, right-click a blank area and choose Add Global
Profile from the shortcut menu.
3.
In the Create ATM Policy Profile dialog box, set desired parameters according to the data
plan. Click OK.
Issue 01 (2014-01-31)
507
4.
On the ATM Policy Profile window, right-click a profile and choose Download to NE
from the shortcut menu.
5.
In the dialog box that is displayed, select the desired NE and click Next. After download
is complete, click Close.
Step 2 Choose Service > PWE3 Service > Manage PWE3 Service from the shortcut menu.
Step 3 In the Set Filter Criteria dialog box, set filter criteria and click Filter. Then all services that
meet the filter criteria are displayed.
Step 4 Select services to be configured from the service list, click the Topology tab, right-click an ATM
interface, and choose Configuration from the shortcut menu.
Step 5 In the Configure ATM Interface dialog box, click the PVC/PVP tab, select PVC, and click
Configure.
Step 6 In the Configure PVC dialog box, click next to Service Name.
Step 7 In the Select ATM Service dialog box, select the configured ATM policy profile.
Step 8 Click OK to dismiss the Select ATM Service dialog box.
Step 9 Click OK to dismiss the Configure PVC dialog box.
Step 10 Click OK to dismiss the Configure ATM Interface dialog box.
Step 11 Configure the other two IMA subinterfaces and the Atm-Trunk interface of the RSG according
to the data plan.
----End
Issue 01 (2014-01-31)
508
Procedure
l
Basic configurations
All basic configurations are applied to NEs using the IP plug-and-play management
function. Basic configurations include basic device configurations, AAA and user
management, loopback interface configuration, network interface configuration, and
SNMP configurations.
IGP configurations
All IGP configurations are applied to NEs using the IP plug-and-play management function.
IGP configurations include global routing configuration, interface route and IP and routing
policies.
MPLS configurations
LSP Deployment Mode
MPLS TE LSP
Issue 01 (2014-01-31)
509
----End
Configuration Principle
If IGP routes are deployed and the cost value is configured as planned on a network, route
selection can be controlled. In this case, MPLS LDP LSPs of the host on the network can be
triggered based on the routing table.
1.
2.
3.
4.
Data Planning
This topic provides the data plan for MPLS LDP configuration.
Table 4-61 MPLS LSR ID planning
Issue 01 (2014-01-31)
NE Role
LSR ID
Remarks
CSG1
1.1.1.1
CSG2
2.2.2.2
ASG3
3.3.3.3
ASG4
4.4.4.4
RSG5
5.5.5.5
RSG6
6.6.6.6
510
Value
Remarks
Auto-Assign
N/A
50
N/A
50
Configuration Object
Configure BFD for LSP on the primary and secondary ASGs and the primary and secondary
RSGs on a bearer network.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the Service Tree, choose Reliability > BFD Management > Service Detection
Configuration > LDP LSP Detection Configuration from the main menu.
Step 3 Click Configure. The Set Dynamic BFD Detect LDP LSP Detection dialog box is displayed.
Step 4 Select Enable Dynamic BFD for LDP LSP Detection and Set Dynamic BFD Detect LDP
LSP Trigger Policy, and set Trigger Type to FEC List.
Step 5 Click ... next to FEC List. The Set FEC List dialog box is displayed. Enter the FEC list name,
click New, enter Peer IP Address, and click Apply. The following table lists the data plan for
NE parameters.
Issue 01 (2014-01-31)
Parameter
Primary/Secondary ASG
Primary/Secondary RSG
FEC List
ASG
RSG
Peer IP Address
5.5.5.5
3.3.3.3
6.6.6.6
4.4.4.4
511
Issue 01 (2014-01-31)
Parameter
Configuration Requirements
50
50
512
Deploying MPLS TE
This topic describes how to deploy Multi-Protocol Label Switching Traffic Engineer (MPLS
TE) to create TE tunnels for carrying services.
Configuration Principle
This topic describes the principle for configuring layered MPLS TE tunnels.
As shown in Figure 4-12, deploy MPLS TE tunnels to carry MPLS VPN for transport wireless
services.
Figure 4-12 MPLS TE tunnel topology
2.
Configure LSR IDs, enable MPLS, MPLS TE, MPLS TE CSPF and BFD for RSVP-TE
globally for nodes on the tunnels, and enable MPLS and MPLS TE for interfaces on the
tunnels.
3.
Issue 01 (2014-01-31)
513
specify paths for deployment. In this solution, configure explicit paths according to the
following rules.
Figure 4-13 Path constraints
NOTE
In the preceding figure, A to E indicate TE constraint interfaces for TE1 to TE7 respectively.
Constraint Interfaces
Include Mode
TE1
Loose
TE2
Loose
TE3
Loose
TE4
Loose
TE5
Loose
TE6
Loose
TE7
Strict
514
the secondary LSP. For example, use the strict constraint interface E for the primary
LSP of TE7 in the upstream and downstream directions.
Configure the hot-standby CR-LSP overlap-path function to maximize protection
for the primary LSP.
Configure the tunnel re-optimization function. You are advised to set the reoptimization interval to 3600s.
NOTE
If the secondary LSP of a tunnel is not configured with constraint paths, a best-effort path is not
required for the tunnel. Otherwise, a best-effort must be configured for the tunnel.
l Automatic path selection: Properly plan cost values for links and use the TE CSPF
function to automatically select paths. In this mode, tunnel deployment is simple and
network adjustment is easy. On a network with a clear structure, use automatic path
selection. The configuration principle is as follows:
TE automatic path selection is implemented based on IGP routes. Therefore,
configure the cost values according to the network plan when configuring IGP. For
details on IGP cost values, see the related IGP configuration topic.
To ensure that services are transmitted over the best path, configure the tunnel reoptimization function. You are advised to set the re-optimization interval to 3600s.
To maximum protection for the working path of tunnels configured with hotstandby, configure the CR-LSP overlap-path function.
For TE to automatically select proper paths, plan cost values for links. To ensure the
primary TE LSPs select the paths of the rings,the access link between the master and
slave ASGs must have a higher cost value than the maximum metric value of the access
ring. For example, cost values for links a, b, c, and d in the following figure must meet
the following rule: (cost(a) + cost(b) + cost(d)) < cost(c). In addition, set the cost values
for links between the master and slave NPEs based on the following rules: (n - 1) x 10
< cost < n x 10 (for IS-IS); (n - 1) < cost < n (for OSPF); where n is the number of links
on the aggregation ring, excluding the link between RSGs. The figure below shows an
example of cost value plan for this example.
Figure 4-14 IS-IS cost value plan
Issue 01 (2014-01-31)
515
4.
b.
c.
d.
5.
Enable MPLS L2VPN for nodes on the TE tunnels, and enable remote LDP peers for
nodes between tunnels.
b.
c.
Issue 01 (2014-01-31)
516
l Create tunnels TE3 and TE4 as the VPN backup tunnels for the VPN working
tunnel TE1 or TE2.
NOTE
When Ethernet and ATM/TDM services share tunnels, the services can also share tunnel policies as
in this example. If Ethernet and ATM/TDM services do not share tunnels, tunnel policies need to be
configured for the services respectively.
6.
Context
You need to create multiple templates based on different requirements for tunnel settings.
NOTE
Path Constraint in the following table applies to the primary tunnel only.
Tunnel
Path
Constraint
BFD Configuration
Template
Tunnel between
CSG1 and ASG3
Loosely
include
Template 1
Tunnel between
CSG1 and ASG4
Loosely
include
No BFD
Template 3
Tunnel between
ASG3 and RSG5
Loosely
include
Template 1
Tunnel between
ASG3 and RSG6
Loosely
include
Template 1
Tunnel between
ASG4 and RSG5
Loosely
include
Template 1
Tunnel between
ASG4 and RSG6
Loosely
include
Template 1
Tunnel between
RSGs 5 and 6
Strictly
include
Template 2
Procedure
Step 1 Choose Service > Service Template from the main menu.
Step 2 In the Set Filter Criteria dialog box, set Template Type to RSVP-TE Tunnel and click
Filter.
Issue 01 (2014-01-31)
517
Step 3 In the Manage Service Template window, click Create > RSVP-TE Tunnel Template.
Step 4 In the Create RSVP-TE Tunnel Template window, set Template Name as planned. The
following table lists the planned template parameters.
Table 4-64 RSVP-TE tunnel template parameters
Parameter Settings
Default Setting
Unnumbered Interface
N/A
Unnumbered Interface
N/A
N/A
TE Information
Reserve Style
Explicit Sharing
Trail Information
Hop Type
Loosely include
NOTE
The parameter must be set to Strictly include when you
configure template 2.
Hot standby
Reversion Interval(s)
60
Revertive Mode
Revertive
Yes
BFD Information
NOTE
The check box needs to be selected only when you configure the templates for the primary VPN tunnel on
the access ring or all tunnels on the aggregation ring.
BFD Type
Static
MinReceiveSendInterval
50
Issue 01 (2014-01-31)
DetectMultiplier
MinReceiveSendInterval
10
518
Parameter Settings
Default Setting
Advanced>Setup Attribute
Record Route Type
Advanced>Reoptimization
Enable Reoptimization
Yes
Interval(s)
3600
Configuration Object
On the bearer network, configure seven MPLS TE tunnels for service bearer and protection
according to the data plan.
Procedure
Step 1 Create tunnels.
Choose Service > Tunnel > Create Tunnel from the main menu.
Step 2 Set basic tunnel parameters.
Parameter
Configuration Requirements
Tunnel Name
Reverse Tunnel
Name
Issue 01 (2014-01-31)
Template
Protocol Type
Signaling Type
519
Step 3 Add source and sink NEs according to the data plan.
In Physical Topology, right-click source and sink NEs respectively.
Configure the NE where the interface with route constraints resides. For example, if a forward tunnel is
destined from A to B and the next hop is constrained as the network-side interface of B, you need to select
B and configure route constraints for the tunnel.
1.
In the Physical Topology, right-click the sink NE traversed by the primary forward path
and choose Set Explicit Restriction > Interface from the shortcut menu.
2.
In the Set Route Constraint dialog box, click the Primary trail option button, select the
Forward Tunnel and Reverse Tunnel check boxes, and click OK.
NOTE
If requiring the forward and reverse tunnels to constrain different interfaces, you need to configure
constrained interfaces respectively for both tunnels.
3.
Issue 01 (2014-01-31)
In the dialog box that is displayed, select the interface traversed by the primary forward
path and click OK.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
520
NOTE
Click Show all Interface and select an interface from all interfaces on the current NE.
4.
In the Route Constraint area, set Restriction Type on the Forward tunnel primary
trail and Reverse tunnel primary trail tabs. Restriction Type is set to Loosely include
by default. However, you need to set it to Strictly include for tunnels between the primary
and secondary RSGs.
Verifying Configurations
This topic explains how to verify configurations.
Choose Service > Tunnel > Manage Tunnel from the main menu.
2.
In the Set Filter Criteria dialog box, set the search criteria and click Filter. The qualified
tunnels are displayed.
3.
Select a tunnel and click Synchronization. After the synchronization is complete, rightclick the tunnel and choose View LSP Topology from the shortcut menu. The View LSP
Topology progress bar is displayed.
4.
View the LSP topology after the progress bar is automatically closed. The solid line stands
for an active LSP and the dashed line stands for a backup LSP.
5.
1.
Choose Service > Tunnel > Manage Tunnel from the main menu.
2.
In the Set Filter Criteria dialog box, set the search criteria and click Filter. The qualified
tunnels are displayed.
3.
Select a tunnel. In the tunnel topology displayed in the lower area, right-click the tunnel
and choose Fast Diagnose from the shortcut menu.
4.
5.
LSP Ping
Issue 01 (2014-01-31)
521
6.
Repeat the preceding steps to check whether LSP Ping can be successfully performed for
the rest of the tunnels.
Procedure
Step 1 Choose Service > Service Template from the main menu.
Step 2 In the Set Filter Criteria dialog box, set Template Type to L3VPN and click Filter.
Step 3 In the Manage Service Template window, click Create > L3VPN Service Template.
Step 4 In the Create L3VPN Service Template window, set Template Name as planned. The
following table lists the planned template parameters.
Table 4-65 L3VPN template parameters
Parameter Settings
Default Setting
Control
Network Type
Customized
Yes
NOTE
This parameter is mandatory when the
MPLS TE tunnel is used.
General
Issue 01 (2014-01-31)
522
Parameter Settings
Default Setting
VRF ID
Auto-Assign
VRF Name
N/A
Import RT
N/A
Export RT
N/A
VRF Description
N/A
Routing Policy
N/A
Per VPN
N/A
N/A
N/A
Network Segment
N/A
N/A
Next VRF
N/A
No
Priority
60
Description
N/A
N/A
BFD Index
N/A
VRRP ID
N/A
Lock
N/A
Metric Priority
N/A
N/A
Issue 01 (2014-01-31)
523
Procedure
Step 1 Choose Service > Service Template from the main menu.
Step 2 In the Set Filter Criteria dialog box, set Template Type to PWE3 and click Filter.
Step 3 In the Manage Service Template window, click Create > PWE3 Service Template.
Step 4 In the Create PWE3 Service Template window, set Template Name as planned. The following
table lists the planned template parameters.
Table 4-66 TDM template parameters
Parameter Settings
Default Setting
General
Service Type
CES
Protection Type
Remarks
N/A
Enable
Redundancy Mode
Forward Type
Reverse Type
Working PW>Advanced
Issue 01 (2014-01-31)
Control Word
Use required
RTP Head
Disable
8000
Encapsulated Frames
524
Parameter Settings
Default Setting
Sequence Mode
Standard Mode
Enable
NOTE
The parameter is required only on aggregation site gateways
(ASGs).
Forward Type
Reverse Type
Protection PW>Advanced
Control Word
Use required
RTP Head
Disable
8000
Encapsulated Frames
Sequence Mode
Standard Mode
Enable
NOTE
The parameter is required only on ASGs.
SAI
SAI Description
N/A
BFD Configuration
BFD Type
Static
Detection Multiple
50
OAM Mapping
OAM Mapping
Enabled
Operation Attribute
Issue 01 (2014-01-31)
Deploy
Deploy
Enable
Enable
525
Default Setting
General
Service Type
ATM
Protection Type
Remarks
N/A
Enable
Redundancy Mode
Forward Type
Reverse Type
Working PW>Advanced
PW Type
Control Word
Use required
Forward Type
Reverse Type
Protection PW>Advanced
PW Type
Control Word
Use required
SAI
SAI Description
Issue 01 (2014-01-31)
N/A
526
Parameter Settings
Default Setting
BFD Configuration
BFD Type
Static
Detection Multiple
50
OAM Mapping
OAM Mapping
Enable
Operation Attribute
Deploy
Deploy
Enable
Enable
Configuration Object
Set Max.ATM Cells on the cell site gateway (CSG) and on the primary and secondary radio
service gateway (RSGs).
Procedure
1.
In the Main Topology, right-click the desired NE and choose NE Explorer from the
shortcut menu.
2.
Choose VPN Management > PWE3 Management > PW Template Management from
the Service Tree.
3.
4.
5.
6.
When ATM subboards do not support cascading, the maximum number of ATM cells should be set to 1.
7.
Issue 01 (2014-01-31)
Click OK.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
527
Configuration Process
In this solution, the PWE3 is used to transmit Ethernet services on an access ring, and the L3VPN
is used to transmit them on an aggregation ring. Aggregation site gateways (ASGs) terminate
PW services and access Ethernet services over the L3VPN. Primary and backup PWs are
deployed on the access ring and L3VPN IGP convergence and FRR are deployed on the
aggregation ring for service protection.
Figure 4-16 Service bearer and protection
NOTE
In the network topology, ASGs 3 and 4 respectively function as primary and secondary ASGs, and RSGs 5 and
6 respectively function as primary and secondary radio service gateways (RSGs).
On an E2E IPRAN network, configure the Ethernet services and protection as follows:
1.
Establish BGP peer relationships to advertise L3VPN routes on the aggregation network.
l Establish BGP peer relationships between the primary ASG and the primary and
secondary RSGs.
l Establish BGP peer relationships between the secondary ASG and the primary and
secondary RSGs.
2.
3.
4.
You can configure the VRRP or primary and backup routes to implement RSG dual-homing
protection. It is recommended that you configure the VRRP for this purpose.
Issue 01 (2014-01-31)
528
l Configure the VRRP on the VLANIF interfaces of the primary and secondary RSGs.
In this case, the radio network controller (RNC) uses only the primary physical interface
to receive packets from RSGs.
l Configure primary and backup static routes. In this case, the RNC uses both the primary
and secondary logical interfaces to receive packets from RSGs.
On a new access ring, configure the Ethernet services and protection as follows:
1.
2.
Data Plan
To deploy a mixed VPN for Ethernet services, plan the following data.
Table 4-68 CSG UNI data
Parameter
Value
Remarks
Interface
Ethernet0/3/0.2
VLAN ID
14
Parameter
Value
Remarks
Primary
RSG
(RSG5)
VLAN ID
100
Eth-Trunk 1
Eth-Trunk 1 is connected to
the secondary RSG, and
Gigabit Ethernet interface
1/0/2 is connected to the
RNC.
VLANIF IP address
192.168.2.1
Mask
255.255.255.0
VRRP virtual IP
address
192.168.2.100
VLAN ID
100
Secondary
RSG
(RSG6)
Issue 01 (2014-01-31)
GigabitEthernet1/0/2
529
NE Role
Parameter
Value
Remarks
Eth-Trunk 1
Eth-Trunk 1 is connected to
the secondary RSG, and
Gigabit Ethernet interface
1/0/2 is connected to the
RNC.
VLANIF IP address
192.168.2.2
Mask
255.255.255.0
VRRP virtual IP
address
192.168.2.100
GigabitEthernet1/0/2
Paramete
r
Value
Working
Mode
Remarks
Primary
ASG
Layer 2
VE
interface
ID
1/0/0
L2
Termination
Layer 3
VE
interface
ID
1/0/1
L3 Access
VE Group
ID
Seconda
ry ASG
Paramet
er
Val
ue
Subinter
face ID
VLAN
ID
MTU
IP
Address/
Mask
Remarks
Prima
ry
ASG
Layer 2
VE
subinterf
ace ID
1/0/0
.
1000
1000
14
1500
Terminate
s PWE3
services.
Secon
dary
ASG
Issue 01 (2014-01-31)
530
NE
Role
Paramet
er
Val
ue
Subinter
face ID
VLAN
ID
MTU
IP
Address/
Mask
Remarks
Layer 3
VE
subinterf
ace ID
1/0/1
.
1000
1000
14
1500
Primary
ASG:
192.168.1.
1/24
Accesses
the
L3VPN
service.
Secondary
ASG:
192.168.1.
1/24
Value
Remarks
Service Name
l3vpn
VRF Name
ipran
VRF ID
RD
ASG3: 100:3
ASG4: 100:4
RSG5: 100:5
RSG6: 100:6
RT
Issue 01 (2014-01-31)
Local Node
Peer Node
Peer LSR ID
CSG1
ASG3
3.3.3.3
ASG4
4.4.4.4
ASG3
CSG1
1.1.1.1
ASG4
CSG1
1.1.1.1
531
Whether to Preempt
Yes
Yes
Delay
300
Configuration Priority
120
100
Configuring PWs
This topic describes how to configure primary and backup PWs destined to aggregation site
gateways (ASGs) on the cell site gateway (CSG).
Configuration Object
Configure PWs from the CSG to primary and secondary ASGs.
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
Step 2 Set basic attributes. Select the PWE3 service template created in Creating a PWE3
Template.
Click the Physical Topology tab, right-click the CSG and choose Select Source from the
shortcut menu.
2.
Select an interface according to the data plan. Then, click the SAI Configuration tab and
create a subinterface by setting its ID and VLAN ID. For example, you can create Gigabit
Ethernet subinterface 0/1/2.3 by setting ID to 3.
Issue 01 (2014-01-31)
532
3.
(Optional) Click Configure. In the Configure Ethernet Interface window, click the
Physical Feature tab, and set the Working Mode and Negotiation Rate for the service
access interface.
NOTE
The CSG and base station must have the same interface settings.
4.
Click OK.
On the Physical Topology tab, right-click the primary ASG and choose Select WorkingSink from the shortcut menu.
2.
In the Create SAI window, click Create and choose VE. The Create VE Interface dialog
box is displayed.
3.
Click the General tab and set Interface No. according to the data plan.
NOTE
The VE interface needs to be created in the same slot as the ASG interface connecting to the RSG.
4.
Issue 01 (2014-01-31)
On the Ethernet Feature tab, click the Layer 3 option button, select the VE-Group check
box, and set Working Mode to L2 Termination, and VE-Group ID to 1.
533
5.
Click OK.
6.
Select the VE interface. Then, click the SAI Configuration tab and create a VE subinterface
by setting its ID and VLAN ID.
7.
Click OK.
8.
On the Physical Topology tab, right-click the secondary ASG and choose Select
Protection-Sink from the shortcut menu. Then, configure the secondary ASG by referring
to the preceding steps.
Right-click on the Service Topology tab and choose Create LDP Remote Peer from the
shortcut menu to rapidly create an LDP remote peer.
2.
3.
Click OK.
Step 6 Click Detail in the lower right part of left pane, and click the Service Parameter tab in the lower
part of right pane. Set Reversion Delay Time to 500.
534
Running Status is Up, Alarm Severity is Normal, Deployment Status is Deployed, and
Enabling Status is Enabled.
Step 9 (Optional) Modify PWs.
1.
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2.
3.
Select the PWE3 service to be modified. The information about the service is displayed in
the lower part of the page.
4.
----End
Configuration Objects
All the main interfaces that connect RSGs or connect the RSGs and the RNC side must be
configured as Layer 2 interfaces.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 Click Query. All the qualified records are displayed.
Step 4 Select the interface to be configured and click Configure. A dialog box is displayed.
Step 5 If the interface is an Ethernet port, click the Ethernet Feature tab, select Layer 2, and click
OK.
Step 6 If the interface is an Eth-Trunk port, click the Physical Feature tab, select Layer 2, and click
OK.
Step 7 Configure other interfaces by referring to steps 1-6.
----End
Configuration Object
Configure the interface connected to the base station on the cell site gateway (CSG) and
interfaces connected to the RNC on the primary and secondary radio service gateways (RSGs).
Issue 01 (2014-01-31)
535
Procedure
Step 1 In the Main Topology, right-click the desired NE and choose NE Explorer from the shortcut
menu.
Step 2 Choose System Management > DCN Communication Management > DCN Management
from the Service Tree.
Step 3 In the right pane, click the Port Settings tab and click the GE option button.
Step 4 Select the desired port and set Enabling Status to Disabled.
Step 5 Click Apply.
----End
Configuration Object
Configure the L3VPN service on aggregation site gateways (ASGs) and radio service gateways
(RSGs).
Choose Service > L3VPN Service > Create L3VPN Service from the main menu.
2.
Configuration Requirements
Service Name
Service Template
Network Type
Customized
VRF Name
VRF ID
RD
Issue 01 (2014-01-31)
536
Parameter
Configuration Requirements
RT
3.
In the Physical Topology, right-click an ASG and choose Add SPE Node to Service from
the shortcut menu, and right-click an RSG and choose Add NPE Node to Service from
the shortcut menu. After the configuration, the NEs are displayed in Node List in the lowerleft part.
NOTE
4.
Issue 01 (2014-01-31)
Select all NEs in Node List and click Details in the lower-left part. The VRF
Configuration tab is displayed in the lower-right part.
b.
On the VRF Configuration tab, choose General and modify RD and RT of each NE
according to the data plan.
537
5.
Issue 01 (2014-01-31)
VRF
Configuratio
n
ASG3
ASG4
RSG5
RSG6
VRF Name
ipran
ipran
ipran
ipran
RD
100:3
100:4
100:5
100:6
Import RT
100:100
100:100
100:100
100:100
Export RT
100:100
100:100
100:100
100:100
b.
Double-click in the cell at the intersection of the primary ASG column and the
Interface row, and click .... In the dialog box that is displayed, select a Layer 3 VE
interface or subinterface for transmitting the L3VPN service.
c.
If no appropriate interface is available, click Create and choose VE. The Create VE
Interface dialog box is displayed.
d.
Click the General tab and set Interface No. according to the data plan.
e.
Click the Ethernet Feature tab and set Working Mode and VE-Group ID for the
VE-Group according to the data plan.
f.
g.
Click the SAI Configuration tab and set the ID and VLAN ID for the VE subinterface.
h.
Click the IP Address tab and set the IP address and mask for the VE subinterface.
538
6.
7.
8.
Issue 01 (2014-01-31)
i.
j.
Select the Layer 3 VE interface and subinterface for the secondary ASG by referring
to the preceding steps.
Configure the parameters for the Layer 3 VE interface on the primary ASG. Perform this
step when a non-association scheme is used.
a.
b.
Select the Layer 3 VE interface for the primary ASG, and set Direct Route
Configuration to Direct Route Delay, Direct Route Delay to 300, Degrade Cost
to 5000, and Interface Status Track PW Status to Disable.
Configure the parameters for the Layer 3 VE interface on the primary ASG. Perform this
step when an association scheme is used.
a.
b.
Select the Layer 3 VE interface of the primary ASG, set Direct Route
Configuration to Direct Route Track PW Status, Degrade Cost to 500, and
Interface Status Track PW Status to Enable.
Configure RNC-side interfaces on the primary and secondary RSGs (with VRRP enabled).
a.
b.
Click the button in the cell at the intersection of the RSG NE column and the Interface
Name row. The Create SAI dialog box is displayed.
c.
Choose Create > VLANIF. Then the Add VLAN Interface dialog box is displayed.
d.
On the General tab, click ... next to Interface No.. Then the Select VLAN ID dialog
box is displayed.
e.
Select an existing VLAN or click Create. In the Create VLAN dialog box, enter the
VLAN ID and click OK to create a VLAN.
539
Issue 01 (2014-01-31)
f.
On the VLAN Member Port tab, click Add. Then the Add Member Port dialog box
is displayed.
g.
h.
In the Selected Port list, set Binding Mode to Passable VLAN for the two ports as
listed in the following table, and click OK.
Port Name
Binding Mode
GigabitEthernet1/0/2
Passable VLAN
Eth-trunk1
Passable VLAN
i.
j.
In the Add VLAN Interface dialog box, click the IPv4 Address tab and set IP address
and mask for the VLANIF interface according to the data plan.
540
k.
l.
In the Create SAI dialog box, select the created VLANIF interface and click OK.
NOTE
If IP addresses of VLANIF interfaces of primary and secondary RSGs are in the same network
segment, the message The interface network address conflicts with other interface network
address. will be displayed. In this case, click OK to close the dialog box.
m. (Optional)Set the port link type according to actual conditions. For detailed
operations, see (Optional) Configuring the Port Link Type.
9.
Configure RNC-side interfaces on the primary and secondary RSGs (with active and
standby routing protection enabled).
a.
b.
Click the button in the cell at the intersection of the RSG NE column and the Interface
Name row. The Create SAI dialog box is displayed.
c.
Select a physical interface in use and click Configure. In the Configure Ethernet
Interface dialog box, click the Physical Feature tab, and set Delay Time(ms) to
30000.
d.
e.
Issue 01 (2014-01-31)
a.
On the VRF Configuration tab, choose Route Configuration > BGP > BGP
Instance > Route Import > Route Import Instance.
b.
541
NOTE
To import multiple routes, click the icon next to the Route Import node and choose Insert
Instance.
ASG3
ASG4
RSG5
RSG6
Route Type
Direct
Direct
Direct
Direct
Static
Static
Static
Static
11. (Optional) Configure the VRRP (required only when the VRRP protection is used).
a.
b.
In the topology view, right-click the VALNIF interface extended from the RSG and
choose Expand from the shortcut menu.
c.
Right-click the expanded VLANIF interface and choose Create VRRP from the
shortcut menu. The Configure VRRP dialog box is displayed.
d.
Issue 01 (2014-01-31)
VRF Configuration
Secondary RSG
(RSG6)
VR IP
192.168.2.100
192.168.2.100
Delay(s)
300
Notification Interval(s)
30
30
Configured Priority
120
100
542
e.
Issue 01 (2014-01-31)
VRF Configuration
Secondary RSG
(RSG6)
Interface
VLANIF100
VLANIF100
Increase Priority By
40
40
Reduce Cost
100
Click the Track BFD option button and Con. The Configure BFD dialog box is
displayed. Set parameters according to the data plan.
VRF Configuration
Secondary RSG
(RSG6)
Local ID
300
300
Min.Receiving Interval
50
50
Min.Sending Interval
50
50
543
f.
After the BFD configuration is complete, click OK in the Configure BFD dialog box.
g.
12. In the Create L3VPN Service window, click Apply to apply the L3VPN service.
13. After the L3VPN service is applied successfully, the Operation Result dialog box is
displayed.
14. Click Browse Trail to view the L3VPN configuration results.
Running Status is Up, Alarm Severity is Normal, Deployment Status is Deployed, and
Enabling Status is Enabled.
NOTE
To view the path carrying the L3VPN service, perform the following operations:
In the Manage L3VPN Service window, select the created L3VPN service, and click Refresh on the
Service Link tab to view the path data or click the Topology tab to view the path in the Service
Topology.
NOTICE
If Running Status is not Up, right-click the L3VPN service, choose Refresh Running
Status from the shortcut menu, and view Running Status.
15. (Optional) Configure static routes.
NOTE
If the base station uses a logical IP address, configure a static route destined to this logical IP address on
the CSG and bind the static route to a VPN instance.
Issue 01 (2014-01-31)
a.
In the Main Topology, right-click the primary ASG and choose Tools > Telnet from
the shortcut menu.
b.
In the command-line interface (CLI), enter the user name and password to log in to
the ASG.
c.
d.
544
station and 192.168.1.2 indicates the IP address of the base station port connected to
the CSG.
e.
f.
Configure a static route on the secondary ASG by referring to the preceding steps.
Choose Service > L3VPN Service > Manage L3VPN Service from the main menu.
b.
Right-click the L3VPN service and choose Modify from the shortcut menu. The
Modify L3VPN Service window is displayed.
c.
d.
If you have not selected the VPN Auto FRR check box during the L3VPN service
creation, you can perform only the following operations for the VPN Auto FRR
function to take effect:
a.
On the VRF Configuration tab, choose General > Label Distribution Policy
and set Label Distribution Policy to Per VPN.
b.
On the VRF Configuration tab, choose General > Routing Policy > Routing
Policy Object > Routing Policy.
c.
Double-click in the cell at the intersection of each NE column and the Routing
Policy row, and click .... The Select Routing Policy dialog box is displayed.
d.
e.
f.
Issue 01 (2014-01-31)
Parameter
Configuration Requirements
Policy Type
Route Policy
Policy Name
frr
Configuration Requirements
Node ID
10
Permit
Click Create in the lower pane. In the Create Policy Rule dialog box, set
parameters.
Parameter
Configuration Requirements
Behavior
Apply
Match Type
Auto
Selected
545
g.
h.
i.
Configuration Object
Configure the primary and secondary RSGs that are located on the bearer network.
Procedure
Step 1 Right-click an NE on the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Ethernet Feature Management VLAN ManagementPort VLAN Management from
the service tree.
Step 3 Click Query to query VLAN interface information.
Issue 01 (2014-01-31)
546
----End
Configuration Object
The primary and secondary RSGs.
Configuration Procedure
1.
Issue 01 (2014-01-31)
(Optional)Configure BFD for detecting the peer RSG. (This operation is required only if
RSGs have a 10GE link between them.)
a.
Choose Service > L3VPN Service > Manage L3VPN Service from the main menu.
b.
c.
Select the desired service, right-click, and choose Configure BFD from the shortcut
menu.
d.
e.
Set BFD detection path to the link between the primary and secondary RSGs.
f.
g.
h.
BFD-1
BFD-2
BFD Name
link_01
link_02
547
2.
Parameter
BFD-1
BFD-2
Local BFD ID
100
101
Remote BFD ID
200
201
10
10
10
10
i.
Double-click the Detection Object text box, then click Configure that is displayed.
In the dialog box that is displayed, set IP bind type to Default multicast address,
and set the physical interface between RSGs as the outgoing interface according to
data plan.
j.
Click OK.
k.
l.
If the RNC uses a logical address, the static route should destined to the logical address. In addition, the
static route must be referenced by VPN instances.
a.
Choose Service > L3VPN Service > Manage L3VPN Service from the main menu.
b.
c.
d.
On the VRF Configuration tab, expand Route Configuration > Static Route by
clicking it; click the icon behind the node and select Insert Instance. Configure the
static route according the data listed in the following table.
Table 4-78 Static route parameters
Parameter
Destination IP Address
Mask
255.255.255.255
255.255.255.255
Priority
548
interface as the target IP address, and the interfaces connecting the primary and secondary RSGs
operate in active/standby dual-receiving state.
Configuration Objects
Active and standby routes need to be configured for the primary and secondary RSGs on the
bearer network
Configuration Roadmap
If the active and standby interfaces have been planned and the RNC supports the dual-receiving
function of these interfaces, you can configure active and standby routes to ensure that the
primary/secondary RSG relationship is consistent with that on the RNC side. This guarantees
millisecond-level fault detection and protection when the primary RSG or the AC link on the
primary RSG is not functioning properly. The RNC uses the IP address of a logical interface as
the target IP address.
Figure 4-17 Configuring active and standby routes
Configure private IGP for subinterfaces between the RSGs to determine the primary/
secondary RSG relationship. IS-IS is used as an example.
Configure static routes from the primary and secondary RSGs to a logical interface on the
RNC, and import the routes to IS-IS.
Unlike VRRP configuration, when you configure active and standby routes, VPN instances use physical
interfaces rather than VLANIF interfaces.
Issue 01 (2014-01-31)
549
Operation Procedure
Configure private network IS-IS:
1.
Choose Service > L3VPN Service > Manage L3VPN Service from the main menu.
2.
3.
Select a service to be configured, and click Modify. The Modify L3VPN Service window
is displayed.
4.
Select primary and secondary RSGs from the node list, and click Details in the lower left
area. Then VRF Configuration is displayed in the lower right area.
5.
On the VRF Configuration tab, expand Route Configuration > ISIS by clicking it; click
the icon behind the ISIS node and select Insert Instance. Then expand the newly-inserted
node and modify its configuration according to the data plan.
Table 4-79 IS-IS process-Basic parameters
6.
Parameter
Primary RSG
Secondary RSG
Instance ID
Network
Entity
Route Level
Level-2
Level-2
Cost Type
Wide
Wide
On the VRF Configuration tab, choose Route Configuration > ISIS > ISIS Instance >
Route Import > External Route Import for the newly-inserted route instance, and modify
related parameters according to the data plan.
NOTE
To import multiple routes, click the icon behind External Route Import and select Insert Instance.
7.
Issue 01 (2014-01-31)
Parameter
Primary RSG
Secondary RSG
Cost Type
External
External
Protocol Type
Static
Static
Route Level
Level-2
Level-2
On the VRF Configuration tab, choose Route Configuration > ISIS > ISIS Instance >
Protocol Interface > Protocol Interface > Interface Name for the newly-inserted route
instance, and modify related parameters according to the data plan.
550
Primary RSG
Secondary RSG
Interface
Name
GigabitEthernet1/0/1.1
GigabitEthernet1/0/1.1
On primary and secondary RSGs, configure a static route destined to the RNC.
1.
Choose Service > L3VPN Service > Manage L3VPN Service from the main menu.
2.
3.
Select the service to be configured and click Modify. The Modify L3VPN Service window
is displayed.
4.
5.
Choose Route Configuration > Static Route > Static Route Object from the service tree.
6.
If multiple static routes exist, click the icon next to Static Route and select Insert Instance.
Primary RSG
Secondary RSG
Destination IP
Address
7.7.7.7
7.7.7.7
Mask
255.255.255.252
255.255.255.252
Next Hop IP
Address
192.168.2.2
192.168.2.6
Priority
50
Description
TO RNC
TO RNC
Choose Service > L3VPN Service > Manage L3VPN Service from the main menu.
2.
3.
Select the service to be configured and click Modify. The Modify L3VPN Service window
is displayed.
4.
5.
Choose Route Configuration > BGP > BGP Instance > Route Import > Route Import
Instance from the service tree.
6.
Issue 01 (2014-01-31)
Parameter
Primary RSG
Secondary RSG
Route Type
Direct
Direct
551
Primary RSG
Secondary RSG
Route Type
Static
Static
MED Value
10
100
Primary RSG
Secondary RSG
Route Type
IS-IS
IS-IS
Instance ID
MED Value
10
100
NOTE
Choose Route Management > IS-IS Route > IS-IS Process from Service Tree in the NE
Explorer, and in the dialog box that is displayed, click Query.
2.
Select a process to be configured, click Configure. The Configure IS-IS Process dialog
box is displayed.
3.
Click the Advanced tab, and click Set in the IS-IS Adjustment and Optimization area.
Set parameters and click OK.
Table 4-86 IS-IS process-IS-IS adjustment and optimization parameters
Issue 01 (2014-01-31)
Parameter
Primary RSG
Secondary RSG
SPF Timer
Max Interval: 1
Max Interval: 1
Initial Interval: 50
Initial Interval: 50
Increase Interval: 50
Increase Interval: 50
LSP Refresh
Timer
300
300
350
350
Level-2 Flash
Flood
552
4.
Parameter
Primary RSG
Secondary RSG
Level-2 LSP
Timer
Max Interval: 1
Max Interval: 1
Initial Interval: 50
Initial Interval: 50
Increase Interval: 50
Increase Interval: 50
Follow-up Procedure
When configuring active and standby routes, configure static routes on the RNC. Ensure that
the routes are destined to the primary and secondary RSGs.
Verify Configurations
This topic describes how to check whether configurations are correct.
VRF Ping
1.
Choose Service > L3VPN Service > Manage L3VPN Service from the main menu.
2.
Select the desired Layer 3 Virtual Private Network (L3VPN) service and click the Service
Link tab.
3.
Right-click on the tab and choose Fast Diagnose from the shortcut menu.
4.
5.
For a peer relationship between ASGs and RSGs, configure it between the primary ASG and primary
RSG, or between the secondary ASG and secondary RSG with a priority. The ping operation will be
performed between each pair of peers. If the test result is successful for the priority peer relationship
but failed for non-priority peer relationship, the test is successful. If a peer relationship is configured
between the primary ASG and secondary RSG, ping packets are transmitted from the primary ASG
to the secondary RSG but returned from the secondary RSG to the secondary ASG, resulting in a
ping failure.
VRF Traceroute
1.
Choose Service > L3VPN Service > Manage L3VPN Service from the main menu.
2.
Right-click a Layer 3 virtual private network (L3VPN) service to be configured and choose
Test and Check from the shortcut menu. The Test and Check window is displayed.
3.
4.
Click OK.
5.
553
To use the TE tunnel, configure new tunnels between the CSG and the primary and secondary
ASGs before service configuration. For details, see Configuring MPLS TE Tunnels.
Configuring PWs
This topic describes how to configure primary and backup PWs destined to aggregation site
gateways (ASGs) on the cell site gateway (CSG).
Configuration Object
Configure PWs from the CSG to primary and secondary ASGs.
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
Step 2 Set basic attributes. Select the PWE3 service template created in Creating a PWE3
Template.
Click the Physical Topology tab, right-click the CSG and choose Select Source from the
shortcut menu.
2.
Select an interface according to the data plan. Then, click the SAI Configuration tab and
create a subinterface by setting its ID and VLAN ID. For example, you can create Gigabit
Ethernet subinterface 0/1/2.3 by setting ID to 3.
Issue 01 (2014-01-31)
554
3.
(Optional) Click Configure. In the Configure Ethernet Interface window, click the
Physical Feature tab, and set the Working Mode and Negotiation Rate for the service
access interface.
NOTE
The CSG and base station must have the same interface settings.
4.
Click OK.
On the Physical Topology tab, right-click the primary ASG and choose Select WorkingSink from the shortcut menu.
2.
In the Create SAI window, click Create and choose VE. The Create VE Interface dialog
box is displayed.
3.
Click the General tab and set Interface No. according to the data plan.
NOTE
The VE interface needs to be created in the same slot as the ASG interface connecting to the RSG.
4.
Issue 01 (2014-01-31)
On the Ethernet Feature tab, click the Layer 3 option button, select the VE-Group check
box, and set Working Mode to L2 Termination, and VE-Group ID to 1.
555
5.
Click OK.
6.
Select the VE interface. Then, click the SAI Configuration tab and create a VE subinterface
by setting its ID and VLAN ID.
7.
Click OK.
8.
On the Physical Topology tab, right-click the secondary ASG and choose Select
Protection-Sink from the shortcut menu. Then, configure the secondary ASG by referring
to the preceding steps.
Right-click on the Service Topology tab and choose Create LDP Remote Peer from the
shortcut menu to rapidly create an LDP remote peer.
2.
3.
Click OK.
Step 6 Click Detail in the lower right part of left pane, and click the Service Parameter tab in the lower
part of right pane. Set Reversion Delay Time to 500.
556
Running Status is Up, Alarm Severity is Normal, Deployment Status is Deployed, and
Enabling Status is Enabled.
Step 9 (Optional) Modify PWs.
1.
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2.
3.
Select the PWE3 service to be modified. The information about the service is displayed in
the lower part of the page.
4.
----End
Configuration Object
Add L3VPN interfaces on the primary and secondary ASGs.
1.
Choose Service > L3VPN Service > Manage L3VPN Service from the main menu.
2.
3.
Select the desired L3VPN service and click Modify. The Modify L3VPN Service dialog
box is displayed.
4.
Select the primary and secondary ASGs in Node List and click Details in the lower-left
part. The VRF Configuration tab is displayed in the lower-right part.
5.
Issue 01 (2014-01-31)
a.
On the VRF Configuration tab, click the icon next to SAI and choose Insert
Instance.
b.
Double-click in the cell at the intersection of the primary ASG column and the
Interface row, and click .... In the dialog box that is displayed, select a Layer 3 VE
interface or subinterface for transmitting the L3VPN service.
c.
d.
Click the General tab and set Interface No. according to the data plan.
e.
Click the Ethernet Feature tab and set Working Mode and VE-Group ID for the
VE-Group according to the data plan.
557
6.
f.
g.
Click the SAI Configuration tab and set the ID and VLAN ID for the VE subinterface.
h.
Click the IP Address tab and set the IP address and mask for the VE subinterface.
i.
j.
Select the Layer 3 VE interface and subinterface for the secondary ASG by referring
to the preceding steps.
In the Modify L3VPN Service window, click OK to apply the L3VPN service.
Configuration Process
This topic describes the process of deploying PWE3 services and related protection protocols.
Issue 01 (2014-01-31)
558
Multihop PWE3s are used to carry TDM services between the cell site gateway (CSG) and radio
service gateways (RSGs). Configuration processes are described by allowing for two livenetwork scenarios: building a new network and adding a base station.
NOTE
In the network topology, ASGs 3 and 4 respectively function as primary and secondary ASGs, and RSGs 5 and
6 respectively function as primary and secondary RSGs.
Configure E-APS.
E-APS and PW redundancy together protect services against faults on the primary RSG.
Configure PW redundancy.
PW redundancy protects services against CSG or RSG faults or faults on links between the
CSG and RSGs. You can configure PW redundancy during E2E service configuration.
l
Issue 01 (2014-01-31)
559
Configure BFD for PW on the primary and backup PWs between the CSG and RSGs to
accelerate PW fault detection.
Configure PW redundancy.
PW redundancy protects services against CSG or RSG faults or faults on links between the
CSG and RSGs. You can configure PW redundancy during E2E service configuration.
Data Planning
You must plan data as needed before deploying Pseudo Wire Emulation Edge-to-Edge (PWE3)
services and relevant protection protocols.
Table 4-87 E-APS protection group configured on a Cpos interface
Parameter
Value
Remarks
APS Group ID
10
N/A
Table 4-88 TDM service interface planning for the RNC side
Issue 01 (2014-01-31)
Parameter
Value
Remarks
Cpos-Trunk 0
N/A
Working Mode
Framed
If timeslot compression is
required in order to save
bandwidth resources, set this
parameter to Framed;
otherwise, set this parameter
to Unframed.
Channel ID
No.
N/A
Timeslot Sequence
1-15, 17-31
N/A
560
Table 4-89 TDM service interface planning for the base station side
Parameter
Value
Remarks
Working Mode
Framed
If timeslot compression is
required in order to save
bandwidth resources, set this
parameter to Framed;
otherwise, set this parameter
to Unframed.
This value must be the same
as that set for the RNC side.
No.
Timeslot Sequence
1-15, 17-31
NE Role
Peer NE
Peer LSR ID
CSG1
ASG3
3.3.3.3
ASG4
4.4.4.4
CSG1
1.1.1.1
RSG5
5.5.5.5
CSG1
1.1.1.1
RSG6
6.6.6.6
ASG3
3.3.3.3
RSG6
6.6.6.6
ASG4
4.4.4.4
RSG5
5.5.5.5
Parameter
Value
Remarks
50
N/A
50
N/A
ASG3
ASG4
RSG5
RSG6
Issue 01 (2014-01-31)
561
Configuration Object
Configure management PWs between primary and secondary RSGs.
Data Plan
Parameter
Management
PW ID
PW1: 150
PW1: 150
PW2: 151
PW2: 151
Loopback
interface
PW1: Loopback2
PW1: Loopback2
PW2: Loopback3
PW2: Loopback3
BFD session
name
PW1: RSG5_to_ac
PW1: RSG6_for_aps
PW2: RSG5_for_aps
PW2: RSG6_to_ac
Local BFD ID
PW1: 1500
PW1: 1500
PW2: 2500
PW2: 2500
Remote BFD
ID
BFD
detection
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
Step 2 Set basic attributes. Set Service Type to Management PW and set other parameters as planned.
Issue 01 (2014-01-31)
562
In Physical Topology in the upper-right part, right-click the primary RSG, and choose
Select Source from the shortcut menu.
2.
In the Create SAI dialog box, select an existing loopback interface; or click Create >
Loopback and in the dialog box that is displayed, enter Interface No. and click OK to
create a loopback interface.
NOTE
3.
In Physical Topology in the upper-right part, right-click the secondary RSG, and choose
Select Sink from the shortcut menu.
2.
In the Create SAI dialog box, select an existing loopback interface; or click Create >
Loopback and in the dialog box that is displayed, enter Interface No. and click OK to
create a loopback interface.
NOTE
3.
563
On the Service Topology tab, right-click and select Create LDP Remote Peer to create an LDP
remote peer quickly.
Step 6 Configure the tunnel policy.
In the PW area of the lower left pane, set both Forward Type and Reverse Type to AutoCreate
Order Policy.
2.
In the area that shows the detailed settings, click the Advanced PW Attribute tab and set
Control Word to Use required.
Issue 01 (2014-01-31)
Parameter
Configuration Requirements
BFD Name
Set the BFD name according to the data plan. If you do not set it, the
system automatically allocates one.
Bound Service
Type
564
Parameter
Configuration Requirements
Detection Object
Local BFD ID
The local BFD ID must be consistent with the remote BFD ID of the
peer NE.
Remote BFD ID
The remote BFD ID must be consistent with the local BFD ID of the
peer NE.
Min.Sending
Interval
100
Min.Receiving
Interval
100
Configuring E-APS
When APS protection needs to be between the active and standby CSG->RSG PWs or between
RSG nodes, you can configure E-APS on the service interface of primary and secondary RSGs
to implement APS switching between RSGs in case of emergency. For E-APS between RSG
nodes, you can choose either 1+1 or 1:1 protection.
Configuration Object
l
Issue 01 (2014-01-31)
For APS protection between the active and standby CSG->RSG PWs, configure primary
and secondary RSGs as the left and right nodes of E-APS.
565
E-APS also needs to be configured on the base station controller (BSC) connected to the
RSGs. For details about the E-APS configuration on the BSC, see BSC manuals.
Procedure
Step 1 (Optional) Set the RSG Cpos port connected to the RNC side to the UP state when receiving
optical signals. When the working mode of the protection group is 1+1 unidirectional
switching, set this parameter.
1.
In the NE Explorer, right-click the RSG, choose Service Tree > Interface Management
> Interface Information, and click Query.
2.
Select the Cpos interface, and click Configure. The Configure Cpos Interface dialog box
is displayed.
3.
4.
Click OK.
Step 2 Choose Configure > Node Redundancy > E-APS Management from the main menu.
Step 3 On the E-APS Management tab page, click Create.
Step 4 In the Create E-APS dialog box, set the related parameters.
NOTE
l E-APS 1+1 has four types: single-ended non-revertive, single-ended revertive, dual-ended non-revertive,
and dual-ended revertive. Single-ended non-revertive E-APS 1+1 is recommended.
l E-APS 1:1 has two types: dual-ended non-revertive and dual-ended revertive. Dual-ended revertive E-APS
1:1 is recommended.
Issue 01 (2014-01-31)
566
Parameter
Settings
NE Name
Sets RSG5 (primary RSG) as the left node and RSG6 (secondary RSG)
as the right node.
Interface Name
APS
APS Group ID
Sets this parameter as planned. The IDs for the local and peer NEs must
be the same.
Local IP
Peer IP
The local IP address of the local NE must be the same as the peer IP
address of the peer NE.
Keepalive Timer
Holdtime Timer
Protection Group
Operating Mode
Bound BFD
Session Name
Issue 01 (2014-01-31)
567
Configuration Object
The Cpos interface must be added to the Cpos-Trunk interface because the Cpos interface is
used for configuring E-APS that implements link protection between the RSG and the RNC side.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 On the Interface Information tab page, click Create and choose Create Main Interface >
Cpos-Trunk Interface.
Step 4 In the Create Cpos-Trunk Interface dialog box, set the relevant parameters.
1.
Click the General tab and set Interface No. on this tab page.
2.
Click the Member Interface tab and click Add. In the dialog box that is displayed, select
interfaces to be added from the Available Interface list on the left and click
All selected interfaces are added to the Selected Interface list. Click OK.
NOTICE
l Before configuring the Cpos-Trunk interface, make sure that E-APS has been configured.
l The "DS1 list" and the Cpos-Trunk interface cannot be configured at the same time. It can
only be configured in the Cpos-Trunk interface that already exists.
Step 5 Click OK. The Create Cpos-Trunk Interface dialog box is closed.
Step 6 Configure Cpos-Trunk interfaces on the secondary RSG in the same manner.
----End
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
Step 2 Set basic attributes. Set a PWE3 service profile that already exists on the Creating a PWE3
Template as a service profile.
Issue 01 (2014-01-31)
568
In Physical Topology in the upper-right part, right-click CSG1, and choose Select
Source from the shortcut menu.
2.
In Physical Topology in the upper-right part, right-click the primary RSG, and choose
Select Working-Sink from the shortcut menu.
2.
In Physical Topology in the upper-right part, right-click the secondary RSG, and choose
Select Protection-Sink from the shortcut menu.
2.
569
Select the service to be configured, right-click a blank area on the Topology tab, and select Legend to view
legend descriptions of the physical topology view. Legends help user learn object types and status of each legend
in the physical topology view.
----End
Verifying Configurations
This topic describes how to verify configurations.
VCCV Ping
1.
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2.
In the Set Filter Criteria dialog box, set search criteria and click Filter. All the qualified
services are displayed in the search result area.
3.
Right-click the desired service and choose Test And Check from the shortcut menu.
4.
In the Test And Check dialog box, choose Diagnosis Option > OAM Tool > VCCV
Ping in the Diagnosis Option area.
5.
(Optional)Click the button next to VCCV Ping and set advanced parameters:
Issue 01 (2014-01-31)
570
a.
If there is no direct route between the CSG and RSG, click the button next to VCCV
Ping and change Response Mode to Application Control Channel.
b.
For switch nodes, set VCCV Capability Type to Lable Alart; for other nodes, select
Control Word.
6.
Click Run.
7.
After VCCV test is completed, test results are displayed in the lower Check Result area,
among which Check Result is displayed as Operation Succeeded.
Connectivity Test
NOTE
For ATM services, set the LLID before performing connectivity tests. You can set or query the LLID by choosing
Service Tree > Reliability > OAM Management > ATM OAM Management > Global ATM OAM
Configuration in the NE Explorer.
1.
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2.
In the Set Filter Criteria dialog box, set search criteria and click Filter. All the qualified
services are displayed in the search result area.
3.
Right-click a service to be tested and choose Connectivity Test from the shortcut menu.
4.
In the Connectivity Test dialog box, set the source and sink loopback status, and click
Start.
5.
After the test is complete, the Check Result is displayed as Operation Succeeded.
Configuration Process
This section describes the process of configuring single-homed MS-PW TDM services and
protection.
As shown in the following figure, MS-PWs are established between the cell site gateway (CSG)
and radio service gateway (RSG).
Issue 01 (2014-01-31)
571
The following table shows the process of configuring single-homed MS-PW services.
RNCSupports APS Protection
Verifying Configurations
Verifying Configurations
NOTICE
If the hot backup or APS protection is deployed for tunnels carrying ATM or TDM services,
ensure that the detection period of BFD for PW is longer than the latency of LSP or APS
switchover. This prevents repeated switchover.
Data Plan
To deploy single-homed MS-PW TDM services and protection, plan the following data.
Issue 01 (2014-01-31)
572
Value
Remarks
APS Group ID
10
N/A
Table 4-93 TDM service interface planning for the RNC side
Parameter
Value
Remarks
Cpos-Trunk 0
N/A
Working Mode
Framed
If timeslot compression is
required in order to save
bandwidth resources, set this
parameter to Framed;
otherwise, set this parameter
to Unframed.
Channel ID
No.
N/A
Timeslot Sequence
1-15, 17-31
N/A
Table 4-94 TDM service interface planning for the base station side
Parameter
Value
Remarks
Working Mode
Framed
If timeslot compression is
required in order to save
bandwidth resources, set this
parameter to Framed;
otherwise, set this parameter
to Unframed.
This value must be the same
as that set for the RNC side.
Issue 01 (2014-01-31)
No.
Timeslot Sequence
1-15, 17-31
573
Peer NE
Peer LSR ID
CSG1
ASG3
3.3.3.3
ASG4
4.4.4.4
CSG1
1.1.1.1
RSG5
5.5.5.5
ASG4
CSG1
1.1.1.1
RSG5
ASG3
3.3.3.3
Parameter
Value
Remarks
50
N/A
50
N/A
ASG3
Configuration Object
l
Select the primary RSG as both the left and right NEs for E-APS.
E-APS also needs to be configured on the base station controller (BSC) connected to the
RSGs. For details about the E-APS configuration on the BSC, see BSC manuals.
Procedure
Step 1 Choose Configure > Node Redundancy > E-APS Management from the main menu.
Step 2 On the E-APS Management tab page, click Create.
Step 3 In the Create E-APS dialog box, set the related parameters.
Parameter
Settings
NE Name
Sets RSG5 (primary RSG) as both the left and right nodes.
Interface Name
APS
Issue 01 (2014-01-31)
574
Parameter
Settings
APS Group ID
Sets the APS group ID according to the data plan. The left and right
nodes have the same group ID.
Protection Group
Operating Mode
In the NE Explorer, right-click the RSG, choose Service Tree > Interface Management
> Interface Information, and click Query.
2.
Select the Cpos interface, and click Configure. The Configure Cpos Interface dialog box
is displayed.
3.
Issue 01 (2014-01-31)
575
4.
Click OK.
Step 6 (Optional) Set the RSG ATM port (for the ATM service) connected to the RNC side to the UP
state when receiving optical signals. When the working mode of the protection group is 1+1
unidirectional switching, set this parameter.
1.
In the Main Topology, right-click an RSG and choose Tools > Telnet from the shortcut
menu.
2.
In the dialog box that is displayed, enter the user name and password of the login NE.
3.
4.
Run the interface interface-type interface-number command to enter the ATM interface
view.
5.
6.
----End
Configuration Object
Configure the RSG.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Issue 01 (2014-01-31)
576
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 On the Interface Information tab page, click Create and choose Create Main Interface >
Cpos-Trunk Interface.
Step 4 In the Create Cpos-Trunk Interface dialog box, set the relevant parameters.
1.
Click the General tab and set Interface No. on this tab page.
2.
Click the Member Interface tab and click Add. In the dialog box that is displayed, select
.
interfaces to be added from the Available Interface list on the left and click
All selected interfaces are added to the Selected Interface list. Click OK.
NOTICE
l Before configuring the Cpos-Trunk interface, make sure that E-APS has been configured.
l The "DS1 list" and the Cpos-Trunk interface cannot be configured at the same time. It can
only be configured in the Cpos-Trunk interface that already exists.
Step 5 Click OK. The Create Cpos-Trunk Interface dialog box is closed.
Step 6 Configure Cpos-Trunk interfaces on the secondary RSG in the same manner.
----End
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
Step 2 Set basic attributes. Set a PWE3 service profile that already exists on the Creating a PWE3
Template as a service profile.
In Physical Topology in the upper-right part, right-click CSG1, and choose Select
Source from the shortcut menu.
2.
Issue 01 (2014-01-31)
577
In Physical Topology in the upper-right part, right-click RSG5, and choose Select Sink
from the shortcut menu.
2.
In Physical Topology in the upper-right part, right-click the primary ASG, and choose Set
As Switching Node > Working from the shortcut menu.
2.
In Physical Topology in the upper-right part, right-click the primary ASG, and choose Set
As Switching Node > Protection from the shortcut menu.
Issue 01 (2014-01-31)
578
Step 9 Click Apply or OK to apply PWE3 services to NEs. The Operation Result prompt is displayed.
Click Browse Trail to view PW configurations. Running Status is Up, Alarm Severity is
Normal, Deployment Status is Deployed, and Enabling Status is Enabled.
NOTE
Select the service to be configured, right-click a blank area on the Topology tab, and select Legend to view
legend descriptions of the physical topology view. Legends help user learn object types and status of each legend
in the physical topology view.
----End
Verifying Configurations
This topic describes how to verify configurations.
VCCV Ping
1.
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2.
In the Set Filter Criteria dialog box, set search criteria and click Filter. All the qualified
services are displayed in the search result area.
3.
Right-click the desired service and choose Test And Check from the shortcut menu.
4.
In the Test And Check dialog box, choose Diagnosis Option > OAM Tool > VCCV
Ping in the Diagnosis Option area.
5.
(Optional)Click the button next to VCCV Ping and set advanced parameters:
a.
If there is no direct route between the CSG and RSG, click the button next to VCCV
Ping and change Response Mode to Application Control Channel.
b.
For switch nodes, set VCCV Capability Type to Lable Alart; for other nodes, select
Control Word.
6.
Click Run.
7.
After VCCV test is completed, test results are displayed in the lower Check Result area,
among which Check Result is displayed as Operation Succeeded.
Connectivity Test
NOTE
For ATM services, set the LLID before performing connectivity tests. You can set or query the LLID by choosing
Service Tree > Reliability > OAM Management > ATM OAM Management > Global ATM OAM
Configuration in the NE Explorer.
1.
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2.
In the Set Filter Criteria dialog box, set search criteria and click Filter. All the qualified
services are displayed in the search result area.
Issue 01 (2014-01-31)
579
3.
Right-click a service to be tested and choose Connectivity Test from the shortcut menu.
4.
In the Connectivity Test dialog box, set the source and sink loopback status, and click
Start.
5.
After the test is complete, the Check Result is displayed as Operation Succeeded.
Configuration Process
This topic describes the process of deploying PWE3 services and related protection protocols.
Figure 4-20 Network topology with multihop PWs
In the mixed VPN solution, the multihop PWE3 is used to carry asynchronous transfer mode
(ATM) services between the cell site gateway (CSG) and radio service gateways (RSGs).
Configuration processes are described by allowing for two live-network scenarios: building a
new network and adding a base station.
NOTE
In the network topology, ASGs 3 and 4 respectively function as primary and secondary ASGs, and RSGs 5 and
6 respectively function as primary and secondary RSGs.
Issue 01 (2014-01-31)
580
Configure PW redundancy.
PW redundancy protects services against CSG or RSG faults or faults on links between the
CSG and RSGs. You can configure PW redundancy during E2E service configuration.
Configure E-APS.
E-APS and PW redundancy together protect services against faults on the primary RSG.
Configure PW redundancy.
PW redundancy protects services against CSG or RSG faults or faults on links between the
CSG and RSGs. You can configure PW redundancy during E2E service configuration.
Data Plan
To deploy PWE3 services and related protection protocols, plan the following data.
Issue 01 (2014-01-31)
581
Value
Remarks
APS Group ID
20
N/A
Value
VPI/VCI
Atm-Trunk 1
N/A
Atm-Trunk1.1
10/90
Parameter
Value
Remarks
Work Mode
Framing mode
Channel Set ID
64k Timeslot
1-15, 17-31
Table 4-100 ATM interface planning for the base station side
Parameter
Value
VPI/VCI
Ima-group0/2/1
N/A
Ima-group0/2/1.1
10/90
NE Role
Peer NE
Peer LSR ID
CSG1
ASG3
3.3.3.3
ASG4
4.4.4.4
CSG1
1.1.1.1
RSG5
5.5.5.5
CSG1
1.1.1.1
RSG6
6.6.6.6
ASG3
ASG4
Issue 01 (2014-01-31)
582
NE Role
Peer NE
Peer LSR ID
RSG5
ASG3
3.3.3.3
RSG6
6.6.6.6
ASG4
4.4.4.4
RSG5
5.5.5.5
Parameter
Value
Remarks
50
50
RSG6
Configuration Object
Configure management PWs between primary and secondary RSGs.
Data Plan
Parameter
Management
PW ID
PW1: 150
PW1: 150
PW2: 151
PW2: 151
Loopback
interface
PW1: Loopback2
PW1: Loopback2
PW2: Loopback3
PW2: Loopback3
BFD session
name
PW1: RSG5_to_ac
PW1: RSG6_for_aps
PW2: RSG5_for_aps
PW2: RSG6_to_ac
Local BFD ID
PW1: 1500
PW1: 1500
PW2: 2500
PW2: 2500
Remote BFD
ID
Issue 01 (2014-01-31)
583
Parameter
BFD
detection
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
Step 2 Set basic attributes. Set Service Type to Management PW and set other parameters as planned.
In Physical Topology in the upper-right part, right-click the primary RSG, and choose
Select Source from the shortcut menu.
2.
In the Create SAI dialog box, select an existing loopback interface; or click Create >
Loopback and in the dialog box that is displayed, enter Interface No. and click OK to
create a loopback interface.
NOTE
Issue 01 (2014-01-31)
584
3.
In Physical Topology in the upper-right part, right-click the secondary RSG, and choose
Select Sink from the shortcut menu.
2.
In the Create SAI dialog box, select an existing loopback interface; or click Create >
Loopback and in the dialog box that is displayed, enter Interface No. and click OK to
create a loopback interface.
NOTE
3.
2.
In the area that shows the detailed settings, click the Advanced PW Attribute tab and set
Control Word to Use required.
585
Step 10 Right-click the PWE3 service in the service list, and choose Configure BFD from the shortcut
menu. The BFD Session Configuration Management dialog box is displayed.
Step 11 Click Create. The Batch Configure BFD Session dialog box is displayed.
Step 12 Click Configure. In the dialog box that is displayed, set BFD parameters for each NE and click
OK after parameters are set. Set key parameters according to the following requirements, and
set the other parameters as required or use default values.
Parameter
Configuration Requirements
BFD Name
Set the BFD name according to the data plan. If you do not set it, the
system automatically allocates one.
Bound Service
Type
Detection Object
Local BFD ID
The local BFD ID must be consistent with the remote BFD ID of the
peer NE.
Remote BFD ID
The remote BFD ID must be consistent with the local BFD ID of the
peer NE.
Min.Sending
Interval
100
Min.Receiving
Interval
100
586
Configuring E-APS
When APS protection needs to be between the active and standby CSG->RSG PWs or between
RSG nodes, you can configure E-APS on the service interface of primary and secondary RSGs
to implement APS switching between RSGs in case of emergency. For E-APS between RSG
nodes, you can choose either 1+1 or 1:1 protection.
Configuration Object
l
For APS protection between the active and standby CSG->RSG PWs, configure primary
and secondary RSGs as the left and right nodes of E-APS.
E-APS also needs to be configured on the base station controller (BSC) connected to the
RSGs. For details about the E-APS configuration on the BSC, see BSC manuals.
Procedure
Step 1 Choose Configure > Node Redundancy > E-APS Management from the main menu.
Step 2 On the E-APS Management tab page, click Create.
Step 3 In the Create E-APS dialog box, set the related parameters.
NOTE
l E-APS 1+1 has four types: single-ended non-revertive, single-ended revertive, dual-ended non-revertive,
and dual-ended revertive. Single-ended non-revertive E-APS 1+1 is recommended.
l E-APS 1:1 has two types: dual-ended non-revertive and dual-ended revertive. Dual-ended revertive E-APS
1:1 is recommended.
Parameter
Settings
NE Name
Sets RSG5 (primary RSG) as the left node and RSG6 (secondary RSG)
as the right node.
Interface Name
APS
APS Group ID
Sets this parameter as planned. The IDs for the local and peer NEs must
be the same.
NOTE
APS Group ID for an ATM interface that has been added to the ATM-Trunk
cannot be set or modified. To set or modify APS Group ID, remove the ATM
interface from the ATM-Trunk.
Issue 01 (2014-01-31)
Local IP
Peer IP
The local IP address of the local NE must be the same as the peer IP
address of the peer NE.
Keepalive Timer
Holdtime Timer
587
Parameter
Settings
Protection Group
Operating Mode
Bound BFD
Session Name
In the Main Topology, right-click an RSG and choose Tools > Telnet from the shortcut
menu.
2.
In the dialog box that is displayed, enter the user name and password of the login NE.
3.
4.
Run the interface interface-type interface-number command to enter the ATM interface
view.
5.
6.
----End
Issue 01 (2014-01-31)
588
Configuration Objects
The ATM interfaces that are used for configuring E-APS need to be added to Atm-Trunk
interfaces.
ATM service interfaces need to be configured on the primary and secondary RSGs.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 On the Interface Information tab page, click Create and choose Create Main Interface >
Atm-Trunk Interface.
Step 4 In the Create Atm-Trunk Interface dialog box, set the relevant parameters.
1.
Click the General tab and set Interface No. according to the data plan.
2.
(Optional) Click the ATM Feature tab and select ATM Cell Transfer. To use the ATM
cell transfer mode, select ATM Cell Transfer; to use a non-transfer mode, deselect it. (The
ATM cell transfer mode requires support of ATM subboards.)
3.
Click the Member Interface tab and click Add. In the dialog box that is displayed, select
the desired interface from the Available Interface list on the left and click
selected interface is added to the Selected Interface list. Then click OK.
. The
4.
5.
On the Interface Information tab page, select the configured ATM-Trunk interface, rightclick, and choose Synchronize from the shortcut menu. In the lower part of the window,
the value of Operating Status is Up.
Step 5 Set the working mode of ATM subboards to ATM cell transfer mode.
1.
In the Main Topology, right-click an RSG and choose Tools > Telnet from the shortcut
menu.
2.
In the dialog box that is displayed, enter the user name and password of the login NE.
3.
4.
Run the set service-mode slot slotid cell-concatenation-mode command. slotid is the ID
of the slot where the ATM subboard resides.
5.
----End
589
Configuration Objects
ATM service interfaces need to be configured for all CSGs.
Procedure
Step 1 Configure an E1 interface.
1.
Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
2.
Choose Interface Management > Interface Information from the service tree.
3.
4.
In the Configure E1 Interface dialog box, click the Physical Feature tab.
5.
6.
In the Add Timeslot Binding dialog box, set No. and Timeslot Sequence according to the
planning.
7.
8.
Click OK. The Configure E1 Interface dialog box is displayed. After you click Query,
serial interfaces named in the format of "E1 interface number + sequence number", such
as Serial 0/2/1:1, are displayed on the Interface Information tab page.
9.
Configure other E1 interfaces that need to be bound to an Inverse Multiplexing Over ATM
(IMA) group in the same manner.
2.
In the Configure Serial Interface dialog box, click the Serial Feature tab.
3.
Set Link Layer Protocol to ATM and use the default values for other parameters.
4.
On the Interface Information tab page, click Create and choose Create Main
Interface > IMA Interface.
2.
In the Create IMA Interface dialog box, set Interface No.. The format subrack number/
slot number/IMA group number is recommended.
3.
4.
In the Add Member Interface dialog box, select the desired interface from the Available
Interface list on the left and click
Interface list. Then click OK.
5.
----End
590
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
Step 2 Set basic attributes of PWE3 services. Set a PWE3 service profile that already exists on the
Creating a PWE3 Template as a service profile.
2.
In the Create SAI dialog box, select a configured IMA interface, and set an IMA
subinterface by entering ID on the SAI Configuration tab. Then click OK.
In Physical Topology in the upper-right part, right-click the primary RSG CX600EE-001,
and choose Select Working-Sink from the shortcut menu.
2.
In the Create SAI dialog box, select a configured Atm-Trunk interface, and set an AtmTrunk subinterface by entering ID on the SAI Configuration tab. Then click OK.
In Physical Topology in the upper-right part, right-click the secondary RSG RSG CX600
FF-001, and choose Select Protection-Sink from the shortcut menu.
2.
In the Create SAI dialog box, select a configured Atm-Trunk interface, and set an AtmTrunk subinterface by entering ID on the SAI Configuration tab. Then click OK.
Issue 01 (2014-01-31)
591
2.
In the Configure Link dialog box, click Add Working Link and then Add Protection
Link.
3.
Select the working link and set Source VPI, Source VCI, Sink VPI, and Sink VCI for it
according to the data plan.
4.
Click OK.
Step 11 (Optional) Configure a PW template. This step is required only when the ATM subboard does
not support cascading.
1.
2.
Issue 01 (2014-01-31)
592
3.
Respectively click the cells under Source PW Template and Sink PW Template and click
the "..." button that is displayed. Then, select the PW template that has been created in
Configuring a PW Template for ATM Services in the dialog box that is displayed.
4.
Configure the source and sink templates for other PWs in the same manner.
Step 12 Click Apply or OK to apply PWE3 services to NEs. The Operation Result prompt is displayed.
Click Browse Trail to view PW configurations. Running Status is Up, Alarm Severity is
Normal, Deployment Status is Deployed, and Enabling Status is Enabled.
NOTE
Select the service to be configured, right-click a blank area on the Topology tab, and select Legend to view
legend descriptions of the physical topology view. Legends help user learn object types and status of each legend
in the physical topology view.
----End
Verifying Configurations
This topic describes how to verify configurations.
VCCV Ping
1.
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2.
In the Set Filter Criteria dialog box, set search criteria and click Filter. All the qualified
services are displayed in the search result area.
3.
Right-click the desired service and choose Test And Check from the shortcut menu.
4.
In the Test And Check dialog box, choose Diagnosis Option > OAM Tool > VCCV
Ping in the Diagnosis Option area.
5.
(Optional)Click the button next to VCCV Ping and set advanced parameters:
a.
If there is no direct route between the CSG and RSG, click the button next to VCCV
Ping and change Response Mode to Application Control Channel.
b.
For switch nodes, set VCCV Capability Type to Lable Alart; for other nodes, select
Control Word.
6.
Click Run.
7.
After VCCV test is completed, test results are displayed in the lower Check Result area,
among which Check Result is displayed as Operation Succeeded.
Connectivity Test
NOTE
For ATM services, set the LLID before performing connectivity tests. You can set or query the LLID by choosing
Service Tree > Reliability > OAM Management > ATM OAM Management > Global ATM OAM
Configuration in the NE Explorer.
1.
Issue 01 (2014-01-31)
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
593
2.
In the Set Filter Criteria dialog box, set search criteria and click Filter. All the qualified
services are displayed in the search result area.
3.
Right-click a service to be tested and choose Connectivity Test from the shortcut menu.
4.
In the Connectivity Test dialog box, set the source and sink loopback status, and click
Start.
5.
After the test is complete, the Check Result is displayed as Operation Succeeded.
Configuration Process
This section describes the process of configuring single-homed MS-PW ATM services and
protection.
As shown in the following figure, MS-PWs are established between the cell site gateway (CSG)
and radio service gateway (RSG).
Figure 4-21 Redundancy protection topology for single-homed MS-PWs
2.
3.
Issue 01 (2014-01-31)
594
4.
Configure MS-PW services on the CSG and RSG, and PW exchange on ASGs.
5.
Configure static BFD for PW between the CSG and RSG to accelerate the switchover
between the primary and backup PWs in case of faults.
NOTICE
If the hot backup or APS protection is deployed for tunnels carrying ATM or TDM services,
ensure that the detection period of BFD for PW is longer than the latency of LSP or APS
switchover. This prevents repeated switchover.
Data Plan
To deploy single-homed MS-PW ATM services and protection, plan the following data.
Table 4-103 E-APS protection group configured on an ATM interface
Parameter
Value
Remarks
APS Group ID
20
N/A
Value
VPI/VCI
Atm-Trunk 1
N/A
Atm-Trunk1.1
10/90
Parameter
Value
Remarks
Work Mode
Framing mode
Channel Set ID
64k Timeslot
1-15, 17-31
Table 4-106 ATM interface planning for the base station side
Issue 01 (2014-01-31)
Parameter
Value
VPI/VCI
Ima-group0/2/1
N/A
595
Parameter
Value
VPI/VCI
Ima-group0/2/1.1
10/90
Peer NE
Peer LSR ID
CSG1
ASG3
3.3.3.3
ASG4
4.4.4.4
CSG1
1.1.1.1
RSG5
5.5.5.5
ASG4
CSG1
1.1.1.1
RSG5
ASG3
3.3.3.3
Parameter
Value
Remarks
Min. Receiving
Interval(ms)
50
Min. Sending
Interval(ms)
50
ASG3
Configuration Object
l
Select the primary RSG as both the left and right NEs for E-APS.
E-APS also needs to be configured on the base station controller (BSC) connected to the
RSGs. For details about the E-APS configuration on the BSC, see BSC manuals.
Procedure
Step 1 Choose Configure > Node Redundancy > E-APS Management from the main menu.
Step 2 On the E-APS Management tab page, click Create.
Issue 01 (2014-01-31)
596
Step 3 In the Create E-APS dialog box, set the related parameters.
Parameter
Settings
NE Name
Sets RSG5 (primary RSG) as both the left and right nodes.
Interface Name
APS
APS Group ID
Sets the APS group ID according to the data plan. The left and right
nodes have the same group ID.
Protection Group
Operating Mode
In the NE Explorer, right-click the RSG, choose Service Tree > Interface Management
> Interface Information, and click Query.
2.
Select the Cpos interface, and click Configure. The Configure Cpos Interface dialog box
is displayed.
3.
Issue 01 (2014-01-31)
597
4.
Click OK.
Step 6 (Optional) Set the RSG ATM port (for the ATM service) connected to the RNC side to the UP
state when receiving optical signals. When the working mode of the protection group is 1+1
unidirectional switching, set this parameter.
1.
In the Main Topology, right-click an RSG and choose Tools > Telnet from the shortcut
menu.
2.
In the dialog box that is displayed, enter the user name and password of the login NE.
3.
4.
Run the interface interface-type interface-number command to enter the ATM interface
view.
5.
6.
----End
Configuration Objects
ATM service interfaces need to be configured for all CSGs.
Procedure
Step 1 Configure an E1 interface.
1.
Issue 01 (2014-01-31)
Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
598
2.
Choose Interface Management > Interface Information from the service tree.
3.
4.
In the Configure E1 Interface dialog box, click the Physical Feature tab.
5.
6.
In the Add Timeslot Binding dialog box, set No. and Timeslot Sequence according to the
planning.
7.
8.
Click OK. The Configure E1 Interface dialog box is displayed. After you click Query,
serial interfaces named in the format of "E1 interface number + sequence number", such
as Serial 0/2/1:1, are displayed on the Interface Information tab page.
9.
Configure other E1 interfaces that need to be bound to an Inverse Multiplexing Over ATM
(IMA) group in the same manner.
2.
In the Configure Serial Interface dialog box, click the Serial Feature tab.
3.
Set Link Layer Protocol to ATM and use the default values for other parameters.
4.
On the Interface Information tab page, click Create and choose Create Main
Interface > IMA Interface.
2.
In the Create IMA Interface dialog box, set Interface No.. The format subrack number/
slot number/IMA group number is recommended.
3.
4.
In the Add Member Interface dialog box, select the desired interface from the Available
Interface list on the left and click
Interface list. Then click OK.
5.
----End
Configuration Object
Configure the RSG.
Procedure
l
Issue 01 (2014-01-31)
If the NodeB supports APS protection, you are advised to use the ATM-Trunk interface.
1.
Right-click the NE in the Main Topology and choose NE Explorer from the shortcut
menu.
2.
Choose Interface Management > Interface Information from the service tree.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
599
3.
On the Interface Information tab page, click Create and choose Create Main
Interface > Atm-Trunk Interface.
4.
In the Create Atm-Trunk Interface dialog box, set the relevant parameters.
a.
Click the General tab and set Interface No. according to the planning.
b.
(Optional) Click the ATM Feature tab and select ATM Cell Transfer. To use
the ATM cell transfer mode, select ATM Cell Transfer; to use a non-transfer
mode, deselect it. (The ATM cell transfer mode requires support of ATM
subboards.)
c.
Click the Member Interface tab and click Add. In the dialog box that is
displayed, select the desired interface from the Available Interface list on the
left and click
. The selected interface is added to the Selected
Interface list. Then click OK.
d.
e.
If the base station does not support APS protection, the ATM interface is recommended.
In this situation, the ATM interface does not need to be configured.
Set the working mode of ATM subboards to ATM cell transfer mode.
1.
In the Main Topology, right-click an RSG and choose Tools > Telnet from the shortcut
menu.
2.
In the dialog box that is displayed, enter the user name and password of the login NE.
3.
4.
5.
----End
Procedure
Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.
Step 2 Set basic attributes. Set a PWE3 service profile that already exists on the Creating a PWE3
Template as a service profile.
Issue 01 (2014-01-31)
600
In Physical Topology in the upper-right part, right-click CSG1, and choose Select
Source from the shortcut menu.
2.
In the Create SAI dialog box, select a configured IMA primary interface and set ID on the
SAI Configuration tab to set this interface as the IMA subinterface. Then click OK.
In Physical Topology in the upper-right part, right-click CSG5, and choose Select Sink
from the shortcut menu.
2.
In the Create SAI dialog box, select a configured Atm-Trunk or ATM interface, and set
an Atm-Trunk or ATM subinterface by entering ID on the SAI Configuration tab. Then
click OK.
In Physical Topology in the upper-right part, right-click the primary ASG, and choose Set
As Switching Node > Working from the shortcut menu.
2.
In Physical Topology in the upper-right part, right-click the primary ASG, and choose Set
As Switching Node > Protection from the shortcut menu.
2.
In the Configure Link dialog box, click Add Link and set Source VPI, Source VCI, Sink
VPI, and Sink VCI for the link according to the data plan.
3.
Click OK.
Step 9 (Optional) Configure a PW template. This step is required when the ATM subboard does not
cascading.
1.
Issue 01 (2014-01-31)
601
2.
3.
Respectively click the cells under Source PW Template and Sink PW Template and click
the "..." button that is displayed. Then, select the PW template that has been created in
Configuring a PW Template for ATM Services in the dialog box that is displayed.
4.
Configure the source and sink templates for other PWs in the same manner.
Step 10 Click Detail in the lower right part of left pane, and click the Service Parameter tab in the lower
part of right pane. Set Reversion Delay Time to 500.
Step 11 Click Apply or OK to apply PWE3 services to NEs. The Operation Result prompt is displayed.
Click Browse Trail to view PW configurations. Running Status is Up, Alarm Severity is
Normal, Deployment Status is Deployed, and Enabling Status is Enabled.
NOTE
Select the service to be configured, right-click a blank area on the Topology tab, and select Legend to view
legend descriptions of the physical topology view. Legends help user learn object types and status of each legend
in the physical topology view.
----End
Verifying Configurations
This topic describes how to verify configurations.
VCCV Ping
1.
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2.
In the Set Filter Criteria dialog box, set search criteria and click Filter. All the qualified
services are displayed in the search result area.
3.
Right-click the desired service and choose Test And Check from the shortcut menu.
Issue 01 (2014-01-31)
602
4.
In the Test And Check dialog box, choose Diagnosis Option > OAM Tool > VCCV
Ping in the Diagnosis Option area.
5.
(Optional)Click the button next to VCCV Ping and set advanced parameters:
a.
If there is no direct route between the CSG and RSG, click the button next to VCCV
Ping and change Response Mode to Application Control Channel.
b.
For switch nodes, set VCCV Capability Type to Lable Alart; for other nodes, select
Control Word.
6.
Click Run.
7.
After VCCV test is completed, test results are displayed in the lower Check Result area,
among which Check Result is displayed as Operation Succeeded.
Connectivity Test
NOTE
For ATM services, set the LLID before performing connectivity tests. You can set or query the LLID by choosing
Service Tree > Reliability > OAM Management > ATM OAM Management > Global ATM OAM
Configuration in the NE Explorer.
1.
Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
2.
In the Set Filter Criteria dialog box, set search criteria and click Filter. All the qualified
services are displayed in the search result area.
3.
Right-click a service to be tested and choose Connectivity Test from the shortcut menu.
4.
In the Connectivity Test dialog box, set the source and sink loopback status, and click
Start.
5.
After the test is complete, the Check Result is displayed as Operation Succeeded.
Configuration Process
This topic describes the process for configuring SD bit error detection.
l
Configure the MPLS label distribution mode to non-null using the U2000 IP plug-and-play
management function.
For the MPLS L2VPN service with the PW redundancy protection, configure SD bit error
detection for AC interfaces and intermediate nodes (multi-segment PWs) on the U2000 to
trigger protection switching.
603
Configuration Object
Configure bit error detection thresholds for ports on links to be tested.
NOTE
You can use a template of the U2000 IP plug-and-play management function to bulk configure the thresholds.
Procedure
Step 1 Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 Choose Interface Management > Interface Information from the service tree.
Step 3 Click Query. All the qualified records are displayed.
Step 4 Select the desired interface and click Configure.
Step 5 In the dialog box that is displayed, click the Monitor Trap Threshold tab, select the CRC
Packet error ratio check box, and set Alarm threshold Coefficient, Resume threshold
Coefficient, Alarm threshold exponent, and Resume threshold exponent according to the
data plan.
Step 6 Select the Trigger LSP check box.
604
Configuration Object
Configure SD bit error detection on the source and sink nodes of primary and backup tunnels
on the bearer network.
Procedure
Step 1 Choose Service > Tunnel > Manage Tunnel from the main menu.
Step 2 In the Set Filter Criteria dialog box, set filter criteria and click Filter. All services meeting the
filter criteria are displayed.
Step 3 In the service list, select the tunnel for which to configure bit error detection. In the lower pane,
click the Bit Error Detection tab.
Step 4 Set Bit Error Detection Mode to Bidirectional.
Step 5 Click Select. In the Select Tunnel dialog box, select the mapping backward tunnel, and click
OK.
Configuration Object
Configure SD bit error detection on primary and backup PWs for low-speed services.
Procedure
Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.
Step 2 In the Set Filter Criteria dialog box, set filter criteria and click Filter. All services meeting the
filter criteria are displayed.
Step 3 In the service list, right-click the desired PWE3 service and choose Bit Error Detect >
Enable from the shortcut menu.
----End
Issue 01 (2014-01-31)
605
Configuration Roadmap
Different clock deployment solutions are available for different synchronization requirements.
Multiple technologies can be used to transparently transmit clock signals. The recommended
solution is: using 1588v2 to achieve time synchronization, using synchronous Ethernet to
achieve frequency synchronization, and selecting sources according to Synchronization Status
Message (SSM).
l
To achieve time synchronization using 1588v2, see Selecting the Clock Source,
Configuring Synchronous Ethernet Clock, and Configuring the 1588v2 Clock.
NOTE
In this topology, ASG3 acts as the primary ASG, ASG4 as the secondary ASG, RSG5 as the primary RSG, and
RSG6 as the secondary RSG.
For the output clock interface, do not set a priority but enable clock synchronization. For the input clock interface,
set a priority according to the clock plan and enable clock synchronization.
In this scheme, the synchronous Ethernet clock is used to implement frequency synchronization
and the 1588v2 clock is used to implement time synchronization.
l
1588v2 clock
All the NEs reside in a 1588v2 clock domain and the primary and secondary RSGs have
external clock sources. The clock priorities for the primary and secondary RSGs must be
higher than those for other NEs and the clock priority for the primary RSG must be higher
Issue 01 (2014-01-31)
606
than that for the secondary RSG. The clock tracing relationship in the clock domain is
determined by the Best Master Clock (BMC) algorithm.
Data Planning
Plan different parameter values based on the different requirements of frequency
synchronization and time synchronization.
l
In this document, the RSGs are CX600-X8s and each RSG has three clock ports: bits0,
bits1, and bits2. The three clock ports can be used for both frequency synchronization and
phase synchronization. In this example, port bits2 is used to receive frequency
synchronization signals and port bits0 is used to receive time synchronization signals.
For synchronous Ethernet, source selection control is implemented by enabling SSM and
configuring clock signal priorities in the local priority list.
NOTE
For clock synchronization of synchronous Ethernet, the source selection sequence is: SSM clock quality
> local priority setting > clock source type.
l The priority list of SSM clock qualities is: PRC > SSUA > SSUB > SEC > DNU. Source selection
does not involve the sources not configured with priorities or with the quality of DNU.
l In local settings, the priority value can be set to 1 to 255. Smaller numbers indicate higher priorities.
Source selection does not involve the sources not configured with priorities.
l The priority of a BITS clock source is higher than a clock source connected to a service port.
When the BMC algorithm is used by a 1588v2-enabled device for source selection, priority1 of each
candidate time source is compared first, then the clock-class, clock-accuracy, and priority2. If priority1
of candidate time sources is the same, the clock-class is compared, and so on. The time source with the
highest priority is selected as the master clock. In this example, it is recommended that priority2 be used
for clock source selection. Retain the default settings for priority1, clock-class, and clock-accuracy.
Parameter
Value
Remarks
RS
G5
2mhz
bits0
Local
priority list
bits0
10
GE2/0/1
20
GE1/0/0
RS
G6
Issue 01 (2014-01-31)
2mhz
bits0
607
Obj
ect
Parameter
Local
priority list
Value
Remarks
bits0
20
GE2/0/1
10
GE1/0/0
AS
G
Local
priority list
GE2/1/0
10
GE1/0/0
20
CS
G1
Local
priority list
GE0/2/1
7
10
GE0/2/1
6
20
2mhz
bits0
FE0/2/18
Issue 01 (2014-01-31)
Obj
ect
Parameter
Value
Remarks
RS
G5
Device type
BC
bits0
1pps
ubx
Port delay
measurement
mechanism
Pdelay
Clock step
one-step
Ring-network
asymmetry automeasure function
enable
608
Obj
ect
Parameter
Value
Remarks
Quality
level
Priority
2
Device type
BC
bits0
1pps
ubx
Port delay
measurement
mechanism
Pdelay
Clock step
one-step
Ring-network
asymmetry automeasure function
enable
Priority
Quality
level
Priority
2
Port delay
measurement
mechanism
Pdelay
Device type
BC
Ring-network
asymmetry automeasure function
enable
Port delay
measurement
mechanism
Pdelay
Device type
BC
1pps
ubx
Priority
RS
G6
AS
G
CS
G1
Issue 01 (2014-01-31)
609
Obj
ect
Parameter
Value
Remarks
bits1
FE0/2/18
Ring-network
asymmetry automeasure function
enable
Importing Links
This topic describes how to import links to generate a clock topology before clock deployment.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave Link
Management from the main menu. The Fiber/Cable/Microwave Link Management window
is displayed.
Step 2 Right-click in a blank area and choose Import Link from the shortcut menu. The Import
Link dialog box is displayed.
610
Configuration Object
Perform configurations on the primary and secondary radio service gateways (RSGs) on the
bearer network.
Procedure
1.
Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
2.
Choose System Management > Clock Management > Physical Clock Management
from the navigation tree. Then, click the Other Clock Source subtab on the Clock
Source tab.
3.
Select the bits0 clock source, and set parameters on the General tab as follows:
l Select the Enable Clock check box.
l Set SSM Source Select Mode to Manual.
l Set Input SSM Class to Prc.
l Select the System Priority check box.
l Set System Priority to 10 (10 for the primary RSG and 20 for the secondary RSG)
l Set Clock Type to 2Mhz.
l Retain the default values of other parameters.
NOTE
In this example, external BITS signals are 2 MHz signals. If BITS signals are 2 Mbps signals, you do
not need to set the SSM Source Select Mode and Input SSM Class parameters, but need to set Clock
Type to 2Mbit/s.
Issue 01 (2014-01-31)
611
4.
Select the bits1 clock source, and set parameters on the General tab as follows:
l Set Clock Type to 1pps.
l Set Direction to In.
l Retain the default values of other parameters.
5.
On the Physical Clock Management tab, click the General subtab and set TOD
Format to Ubx.
6.
(Optional) On the Clock Source tab, click the Other Clock Source subtab, select the
ptp clock source, and set parameters in the lower pane as follows:
NOTE
Issue 01 (2014-01-31)
612
7.
Click Apply.
NOTE
Configuration Objects
Synchronous Ethernet clock needs to be configured for all NEs on the bearer network.
Procedure
1.
Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
2.
Choose System Management > Clock Management > Physical Clock Management
from the service tree. Then click the General tab and set relevant clock parameters.
l Select Enable Ethernet Synchronization.
l Select SSM Control.
l Use the default values for other parameters.
Issue 01 (2014-01-31)
613
3.
Click the Clock Source tab and then the Port Clock tab. Click Add. The Select
Interface dialog box is displayed.
4.
Select the interface that connects RSG5 to RSG6 and click OK.
5.
Select this interface, set the relevant parameters on the General tab page, and click Apply
NOTE
For the output clock interface, do not set a priority but enable clock synchronization. For the input
clock interface, set a priority according to the clock plan and enable clock synchronization.
For example, GE interface 1/1/2 is an output clock interface; therefore, enable clock
synchronization for it; GE interface 2/1/0 is an input clock interface and the interface
priority is 1; therefore, set the priority to 1 and enable clock synchronization for it.
Issue 01 (2014-01-31)
614
6.
In the dialog box displayed indicating that the operation is successful, click OK.
7.
Set clock information for the rest of the NEs according to the planning.
Issue 01 (2014-01-31)
615
NOTE
Clock synchronization must be enabled for the interface between the CSG and the base station.
Configuration Objects
The 1588v2 clock needs to be configured for all NEs on the bearer network.
Procedure
1.
In the NE Explorer, choose System Management > Clock Management > PTP
Clock Management from the service tree. The PTP Clock Management tab page is
displayed.
b.
Click the General tab and set the relevant parameters. Then click Apply.
l Select Enable PTP.
l Set Clock Domain according to the planning.
l Set Clock Type according to the planning.
l Select Enable Ring Fiber Asymmetry Measure.
2.
Issue 01 (2014-01-31)
Click the Clock Source tab and then the Port Clock Source tab. Click Add. The
Select Interface dialog box is displayed.
b.
616
c.
On the Port Clock Source tab page, select this interface, set the relevant parameters
on the Basic Information tab page, and click Apply.
l Select Enable PTP.
l Set Delay Mechanism to Pdelay.
l Set Clock Step to One-step.
3.
Issue 01 (2014-01-31)
d.
e.
Configure clock ports on the rest of the NEs according to the planning.
In the NE Explorer, choose System Management > Clock Management > PTP
Clock Management from the service tree. Click the Clock Source tab and then the
Local Clock Source tab.
b.
617
4.
Configure the 1588v2 clock for the rest of the NEs in the same manner.
Verifying Configurations
This topic explains how to verify configurations.
Procedure
Step 1 Select Clock View from the Current View drop-down list in the upper left part of the Main
Topology. Then select an IPRAN subnet from the navigation tree. The clock status of each NE
is displayed.
Step 2 Right-click in the Main Topology and choose Search Clock Link from the shortcut menu. The
Search Clock Link dialog box is displayed. Set the relevant parameters and click OK.
l Select 1588v2 and Synchronous ETH in the Clock Type area.
l Click Search from NE in the Search Mode area.
l Select IPRAN in the NE Search area.
Step 3 In the dialog box that is displayed, click Close. The clock tracing relationships between NEs are
displayed in the clock view. Check whether the relationships are the same as those planned. If
some relationships are different from those planned, check whether the clock parameters are set
according to the planning.
Step 4 Click Legend&Filter&Attribute and select the desired clock type on the Filter tab page.
Step 5 To clear clock configurations of an interface, perform the following operations:
1.
In the clock view, right-click an NE whose clock configurations need to be deleted, and
choose Configure Clock from the shortcut menu. The NE Explorer is displayed.
2.
On the PTP Clock Management tab, select Clock Source > Port Clock Source.
Issue 01 (2014-01-31)
618
3.
Select a clock source and click Delete. In the dialog box that is displayed, click OK.
You can delete all port clock sources of a device by selecting all of them and clicking
Delete.
4.
5.
On the Physical Clock Management tab, select Clock Source > Port Clock Source.
Issue 01 (2014-01-31)
619
6.
Select a clock source and click Delete. In the dialog box that is displayed, click OK.
You can delete all port clock sources of a device by selecting all of them and clicking
Delete.
7.
8.
Click Apply.
Issue 01 (2014-01-31)
620
9.
Click Synchronize.
----End
Configuration Object
This solution uses simple traffic classification to deploy QoS and set CAR parameters for the
network interface of CSGs and RSGs.
l
CAR: CAR parameters are configured in an HQoS profile for CSGs and RSGs and they
are applied to the network interface of CSGs and RSGs.
Configuration roadmap:
l
Create Diffserv profile example used to configure the service interface and network
interface of CSGs, ASGs, and RSGs.
NOTE
If priority mapping rules configured in the default profile are appropriate, use the default profile.
Create an HQoS profile used to configure CAR of the network interface of CSGs and RSGs.
Apply the profile to the interface.
Data Plan
Table 4-111 Data plan for the Diffserv profile
NE
Profile
Name
Direction
Priority
Type
Priority
CoS
Color
CSG1
example
Inbound
direction
DSCP
62
CS6
Green
Outbound
direction
DSCP
62
CS6
Green
ASG3
ASG4
RSG5
RSG6
Issue 01 (2014-01-31)
621
Profile
Name
General
Informatio
n
Queue
Priority
Scheduli
ng Mode
Shaping
Rate (kbit/
s)
CSG1
CSG_UNI
CIR: 4000
CS6
PQ
70
EF
PQ
200
AF1
WFQ
10
AF2
WFQ
10
AF3
WFQ
15
AF4
WFQ
15
BE
WFQ
10
CSG2
PIR: 4000
Outbound
direction
Weight
Profile
Name
General
Informatio
n
Queue
Priority
Scheduli
ng Mode
Shaping
Rate (kbit/
s)
RSG5
RSG_UNI
CIR: 10000
CS6
PQ
500
EF
PQ
2000
AF1
WFQ
10
AF2
WFQ
10
AF3
WFQ
15
AF4
WFQ
15
BE
WFQ
10
RSG6
PIR: 20000
Inbound
direction
Weight
Procedure
Step 1 Configure differentiated services for the outbound direction of the CSG user side.
1.
In the NE Explorer, right-click the CSG, choose Service Tree > VPN Management >
L3VPN Management > VRF Management, and click Query.
2.
Select the VRF and click Configure. The Configure VRF window is displayed.
3.
4.
5.
Click Apply.
622
1.
Choose Configuration > IP QoS Profile > DS Domain Profile from the main menu.
2.
On the DS Domain Profile tab page, right-click in the blank area and choose Add Global
Profile from the shortcut menu.
3.
In the Create DS Domain Profile dialog box, set Name to example. Then configure the
mapping between the Differentiated Services Code Point (DSCP) and Class of Service
(CoS) and set parameters in the Inbound Parameters area. Use the default values for the
parameters in the Outbound Parameters area.
4.
Click OK.
Right-click profile example, and choose Deploy to Interface from the shortcut menu. In
the dialog box that is displayed, select the service interface and network interface of CSGs,
ASG, and RSGs and add them to Selected Interface, and click OK.
Step 4 Disable PHB for the service interface of ASGs and RSGs.
1.
In the NE Explorer, right-click the CSG, choose Service Tree > QoS Management >
Configure Interface QoS, and click Query.
2.
3.
4.
Click Apply.
623
1.
Choose Configuration > IP QoS Profile > HQoS Profile from the main menu.
2.
On the HQoS Profile tab page, right-click in the blank area and choose Add Global
Profile from the shortcut menu.
3.
In the Create HQoS Profile dialog box, set Name to CSG_UNI and click Add.
4.
In the User Queue dialog box, click next to the Flow Queue Policy text box.
5.
In the Select Flow Queue Profile dialog box, right-click in the blank area and choose Add
Global Profile from the shortcut menu.
6.
In the Create Flow Queue Profile dialog box, set Name to CSG_UNI. Then set the
relevant parameters according to the planning. Click OK.
7.
In the Add User Queue dialog box, set CIR to 4000, PIR to 4000, and Direction to
Outbound. Then click OK.
Issue 01 (2014-01-31)
624
8.
9.
Create an HQoS profile by following the preceding procedure, name it RSG_UNI and set
other parameters according to the data plan.
Select the CSG_UNI profile, right-click, and choose Deploy to Interface from the shortcut
menu.
2.
In the Deploy HQoS Profile dialog box, select a UNI on the ATN and add it to the Selected
Interface list. Then click OK.
Select the RSG_UNI profile, right-click, and choose Deploy to Interface from the shortcut
menu.
2.
3.
Click OK.
----End
Configuration Roadmap
Three types of ATM services need to be configured and they are provided by the three user-side
IMA subinterfaces of the CSG and transmitted to the three ATM trunk subinterfaces of the RNC.
On the three IMA subinterfaces of the CSG, three types of ATM services are configured: cbr,
vbrNrt, and vbrRt.
On the three IMA trunk subinterfaces of the RSG, three types of ATM services are configured:
cbr, vbrNrt, and vbrRt.
Data Planning
Table 4-114 ATM QoS parameter planning
Issue 01 (2014-01-31)
Interface
Parameter
Value
Interface
Parameter
Value
Imagroup0/2/
1.1
Service Name/
Service Type
cbr
AtmTrunk0.1
Service Name/
Service Type
cbr
1000
100000
625
Interface
Imagroup0/2/
1.2
Imagroup0/2/
1.3
Parameter
Value
500
Service Name/
Service Type
ntr-vbr
Interface
Parameter
Value
50000
Service Name/
Service Type
ntr-vbr
2000
200000
Sustainable Cell
Rate (kbit/s)
2000
Sustainable Cell
Rate (kbit/s)
200000
Maximum Burst
Size (kpbs)
255
Maximum Burst
Size (kpbs)
255
500
500
Service Name/
Service Type
rt-vbr
Service Name/
Service Type
rt-vbr
2000
200000
Sustainable Cell
Rate (kbit/s)
2000
Sustainable Cell
Rate (kbit/s)
200000
Maximum Burst
Size (kpbs)
255
Maximum Burst
Size (kpbs)
255
500
500
AtmTrunk0.1
AtmTrunk0.1
Procedure
Step 1 Configure an ATM policy profile.
1.
Choose Configuration > IP QoS Profile > ATM Policy Profile from the main menu.
2.
On the ATM Policy Profile window, right-click a blank area and choose Add Global
Profile from the shortcut menu.
3.
In the Create ATM Policy Profile dialog box, set desired parameters according to the data
plan. Click OK.
Issue 01 (2014-01-31)
626
4.
On the ATM Policy Profile window, right-click a profile and choose Download to NE
from the shortcut menu.
5.
In the dialog box that is displayed, select the desired NE and click Next. After download
is complete, click Close.
Step 2 Choose Service > PWE3 Service > Manage PWE3 Service from the shortcut menu.
Step 3 In the Set Filter Criteria dialog box, set filter criteria and click Filter. Then all services that
meet the filter criteria are displayed.
Step 4 Select services to be configured from the service list, click the Topology tab, right-click an ATM
interface, and choose Configuration from the shortcut menu.
Step 5 In the Configure ATM Interface dialog box, click the PVC/PVP tab, select PVC, and click
Configure.
Step 6 In the Configure PVC dialog box, click next to Service Name.
Step 7 In the Select ATM Service dialog box, select the configured ATM policy profile.
Step 8 Click OK to dismiss the Select ATM Service dialog box.
Step 9 Click OK to dismiss the Configure PVC dialog box.
Step 10 Click OK to dismiss the Configure ATM Interface dialog box.
Step 11 Configure the other two IMA subinterfaces and the Atm-Trunk interface of the RSG according
to the data plan.
----End
Issue 01 (2014-01-31)
627