I Manager Huawei

iManager U2000 Unified Network Management System V100R002C01
Operation Guide for UA5000-IPMB NE Management

Issue Date 03 2010-11-19
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2010. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com [email protected]
Website: Email:
Issue 03 (2010-11-19)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System Operation Guide for UA5000-IPMB NE Management
About This Document
About This Document

Related Version
The following table lists the product version related to this document. Product Name iManager U2000 Version V100R002C01
Intended Audience
This document describes the functions and services provided by the UA5000(IPMB). After you read this document, you should be able to know how to operate the UA5000(IPMB) and configure services through the U2000. This document is intended for: l l Data Configuration Engineer Network Monitoring Engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows. Symbol Description
DANGER
Indicates a hazard with a high level of risk, which if not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk, which if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation, which if not avoided, could result in equipment damage, data loss, performance degradation, or unexpected results.
iii
WARNING
CAUTION
Issue 03 (2010-11-19)
About This Document
Symbol
TIP
Description Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text.
NOTE
Command Conventions
The command conventions that may be found in this document are defined as follows. Convention Boldface Italic [] { x | y | ... } [ x | y | ... ] { x | y | ... }* Description The keywords of a command line are in boldface. Command arguments are in italics. Items (keywords or arguments) in brackets [ ] are optional. Optional items are grouped in braces and separated by vertical bars. One item is selected. Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected. Optional items are grouped in braces and separated by vertical bars. A minimum of one item or a maximum of all items can be selected. Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.
[ x | y | ... ]*
GUI Conventions
The GUI conventions that may be found in this document are defined as follows. Convention Boldface > Description Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK. Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder.
iv
Issue 03 (2010-11-19)
About This Document
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains all updates made in previous issues.
Changes in Issue 03 (2010-11-19) Based on Product Version V100R002C01

The third commercial release has the following updates: The following changes: 1.1.5 Configuring the xFTP File in the NAT Networking Mode.

The second commercial release has the following updates: The parameter names and graphs are changed according to latest GUIs.

Initial release for V100R002C01 version.
Issue 03 (2010-11-19)
Contents
Contents
About This Document...................................................................................................................iii 1 Managing Devices......................................................................................................................1-1
1.1 Configuring the xFTP Service.........................................................................................................................1-3 1.1.1 Configuring the FTP, SFTP, or TFTP Service (Windows)....................................................................1-3 1.1.2 Configuring the FTP, SFTP, or TFTP Service (Solaris)........................................................................1-6 1.1.3 Configuring the FTP, SFTP, or TFTP Service (Linux)..........................................................................1-9 1.1.4 Configuring the xFTP Watcher............................................................................................................1-11 1.1.5 Configuring the xFTP File in the NAT Networking Mode..................................................................1-12 1.2 Setting the Communication Parameters........................................................................................................1-14 1.2.1 Setting the SNMP Parameters..............................................................................................................1-14 1.2.2 Setting the NE Handshake Parameters.................................................................................................1-16 1.3 Adding an OLT to the U2000.......................................................................................................................1-17 1.4 Bulk Adding NEs to the U2000....................................................................................................................1-18 1.5 Adding a Shelf...............................................................................................................................................1-19 1.6 Adding an Inter-shelf Link............................................................................................................................1-20 1.7 Configuring the Information About Physical Resources..............................................................................1-21 1.8 Collecting Statistics on Physical Resources..................................................................................................1-23 1.9 Configuration Example of Outband Network Management (Based on the SNMPv1 or SNMPv2c Protocol) .............................................................................................................................................................................1-24 1.10 Configuration Example of Outband Network Management (Based on the SNMPv3 Protocol).................1-30 1.11 Configuration Example of Inband Network Management (Based on the SNMPv1 or SNMPv2c Protocol) .............................................................................................................................................................................1-37 1.12 Configuration Example of Inband Network Management (Based on the SNMPv3 Protocol)...................1-43
2 Pre-configuring Parameters for Service Provisioning........................................................2-1

2.1 Adding a VLAN..............................................................................................................................................2-3 2.2 Configuring the Upstream Port of a VLAN....................................................................................................2-5 2.3 Configuring a VLAN L3 Interface..................................................................................................................2-6 2.4 Configuring the QoS Policy............................................................................................................................2-7 2.5 Configuring a Global Traffic Profile.............................................................................................................2-10 2.5.1 Configuring an ATM Traffic Profile....................................................................................................2-10 2.5.2 Configuring an IP Traffic Profile.........................................................................................................2-11 2.6 Configuring the xDSL-Related Profiles........................................................................................................2-12 2.6.1 Configuring an ADSL Line Profile......................................................................................................2-13 Issue 03 (2010-11-19) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vii
Contents
iManager U2000 Unified Network Management System Operation Guide for UA5000-IPMB NE Management 2.6.2 Configuring an ADSL Alarm Profile...................................................................................................2-15 2.6.3 Configuring a VDSL2 Line Profile......................................................................................................2-16 2.6.4 Configuring a VDSL2 Alarm Profile...................................................................................................2-19 2.6.5 Configuring a G.SHDSL Line Profile..................................................................................................2-21 2.6.6 Configuring a G.SHDSL Alarm Profile...............................................................................................2-23
2.7 Configuring an IGMP Profile........................................................................................................................2-24 2.7.1 Configuring a Program Profile.............................................................................................................2-25 2.7.2 Configuring a Rights Profile................................................................................................................2-26 2.8 Configuring the System Parameters..............................................................................................................2-27 2.8.1 Configuring the DHCP Relay Mode....................................................................................................2-28 2.8.2 Configuring the RSTP Global Parameters...........................................................................................2-29 2.8.3 Enabling the PPPoA Conversion to PPPoE Function..........................................................................2-29 2.8.4 Configuring the IPoA Parameters........................................................................................................2-30 2.8.5 Configuring the Multicast Parameters..................................................................................................2-31 2.8.6 Setting BFD Parameters.......................................................................................................................2-31 2.8.7 Adding the System Parameter Profile to a Device...............................................................................2-32
3 Setting the System Clock..........................................................................................................3-1

3.1 Introduction to the Clock System....................................................................................................................3-2 3.2 Adding a Clock Source...................................................................................................................................3-2 3.3 Setting the Time Zone and the Daylight Saving Time....................................................................................3-3
4 Configuring the System Security Policy................................................................................4-1

4.1 Querying the Blacklist.....................................................................................................................................4-2
5 Configuring the User Security Policy....................................................................................5-1

5.1 Setting PITP Management Parameters............................................................................................................5-2 5.2 Configuring the Security Enabling or Disabling.............................................................................................5-3 5.3 Configuring DHCP Option 82.........................................................................................................................5-3
6 Configuring the DHCP Relay..................................................................................................6-1

6.1 Introduction to the DHCP Relay.....................................................................................................................6-3 6.2 Configuring the DHCP Standard Mode..........................................................................................................6-4 6.2.1 Adding a DHCP Server Group...............................................................................................................6-5 6.2.2 Configuring a VLAN L3 Interface.........................................................................................................6-6 6.2.3 Binding an L3 Interface to a DHCP Server Group................................................................................6-7 6.3 Configuring the DHCP Option60 Mode.........................................................................................................6-7 6.3.1 Adding a DHCP Server Group...............................................................................................................6-8 6.3.2 Adding a DHCP Domain........................................................................................................................6-8 6.3.3 Configuring a VLAN L3 Interface.........................................................................................................6-9 6.3.4 Configuring the Gateway IP Address of the Domain Under an Interface............................................6-10 6.4 Configuring the DHCP MAC Address Segment Mode................................................................................6-11 6.4.1 Adding a DHCP Server Group.............................................................................................................6-11 6.4.2 Adding a MAC Address Segment........................................................................................................6-12 6.4.3 Configuring a VLAN L3 Interface.......................................................................................................6-13 viii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-11-19)
Contents
6.4.4 Configuring the Gateway IP Address Corresponding to the MAC Address Segment Under an Interface .......................................................................................................................................................................6-14
7 Configuring the xDSL Access..................................................................................................7-1

7.1 Introduction to the xDSL Access....................................................................................................................7-2 7.2 Configuring the xDSL Access Services..........................................................................................................7-4 7.2.1 Configuring the IPoA Service................................................................................................................7-4 7.2.2 Configuring the PPPoA Service...........................................................................................................7-11 7.2.3 Configuring the IPoE Service..............................................................................................................7-17 7.2.4 Configuring the PPPoE Service...........................................................................................................7-21 7.3 Configuration Example of the ADSL IPoA Access Service.........................................................................7-26 7.4 Configuration Example of the VDSL2 PPPoE Service................................................................................7-33
8 Configuring Multicast Services...............................................................................................8-1

8.1 Introduction to the Multicast Service..............................................................................................................8-4 8.2 Configuring the Multicast Upstream Port.......................................................................................................8-4 8.3 Applying a Program Profile to a Device.........................................................................................................8-5 8.4 Applying a Rights Profile to a Device............................................................................................................ 8-6 8.5 Configuring a Multicast User..........................................................................................................................8-6
9 Configuring the Multicast Services of Subtending Devices.............................................9-1

9.1 Introduction to the Multicast Services of Subtend Devices............................................................................9-5 9.2 Configuration Example of the Multicast Services of Subtend Devices..........................................................9-5
10 Configuring the Triple Play Service...................................................................................10-1

10.1 Introduction to the Triple Play Service.......................................................................................................10-4 10.2 Configuration Example of the Triple Play Service - xDSL Access............................................................10-5
11 Configuring VLAN Stacking Wholesale Services...........................................................11-1

11.1 Introduction to VLAN Stacking Wholesale Services..................................................................................11-3 11.2 Configuring the VLAN Stacking Attribute.................................................................................................11-4 11.3 Configuring the Inner VLAN Tag...............................................................................................................11-5
12 Configuring the QinQ VLAN Private Line Service........................................................12-1

12.1 Introduction to the QinQ VLAN Private Line Service................................................................................12-3 12.2 Configuring the VLAN QinQ Attribute......................................................................................................12-4
13 Configuring the CESoP TDM Private Line Service........................................................13-1

13.1 Introduction to the CESoP TDM Private Line Service...............................................................................13-3 13.2 Configuring the CES E1 Port......................................................................................................................13-3 13.3 Configuring the CESoP Connection...........................................................................................................13-4 13.4 Configuration Example of the CESoP TDM Private Line Service.............................................................13-5
14 Configuring the Active/Standby Switchover for the Upstream Service.....................14-1

14.1 Configuring the Active/Standby Switchover for the IPM Upstream..........................................................14-2 14.1.1 Configuring the Active/Standby Switchover for the IPM Upstream.................................................14-2 14.1.2 Configuring Upstream Link Detection...............................................................................................14-3 14.2 Configuration Example of the Active/Standby Switchover for the IPM Dual Upstream...........................14-3 Issue 03 (2010-11-19) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ix
Contents
14.3 Configuring the Active/Standby Switchover for the AIU Upstream..........................................................14-5
15 Configuring the Ethernet OAM Diagnosis.......................................................................15-1

15.1 Introduction to the Ethernet OAM..............................................................................................................15-4 15.2 Configuring an MD.....................................................................................................................................15-6 15.3 Configuring an MA.....................................................................................................................................15-7 15.4 Configuring a Source MEP.........................................................................................................................15-8 15.5 Enabling the Global CFM Function..........................................................................................................15-10 15.6 Configuration Example of the Ethernet OAM Diagnosis.........................................................................15-11
16 Configuring the BFD Network Monitoring......................................................................16-1

16.1 Introduction to BFD....................................................................................................................................16-2 16.2 Setting the BFD Session Parameters...........................................................................................................16-2
17 Detecting the Network..........................................................................................................17-1

17.1 Telnet...........................................................................................................................................................17-2 17.2 Ping..............................................................................................................................................................17-2 17.3 Tracert.........................................................................................................................................................17-2 17.4 SSH..............................................................................................................................................................17-3
18 Saving the Data.......................................................................................................................18-1

18.1 Setting the Parameters for Saving the Data.................................................................................................18-2 18.2 Immediately Enabling Data Saving Function.............................................................................................18-2
19 Synchronization......................................................................................................................19-1
19.1 Synchronizing the NE Data.........................................................................................................................19-2 19.2 Synchronizing the NE Time........................................................................................................................19-2 19.3 Synchronizing NE Alarms..........................................................................................................................19-2 19.4 Synchronizing the System Parameter Profile..............................................................................................19-3
20 File Operations.......................................................................................................................20-1
20.1 Saving Records as a File.............................................................................................................................20-2 20.2 Previewing the File Printing Effect.............................................................................................................20-2 20.3 Printing........................................................................................................................................................20-3
21 Remote Maintenance Guide................................................................................................21-1

21.1 Monitoring Critical and Major Alarms of NEs...........................................................................................21-3 21.2 Measuring the CPU Usage of a Board........................................................................................................21-5 21.3 Measuring the Performance of an Upstream Ethernet Port.........................................................................21-8 21.4 Measuring the Usage of NE Resources.....................................................................................................21-10 21.5 Checking the NE User Level.....................................................................................................................21-11 21.6 Changing the Password of an NE User.....................................................................................................21-12 21.7 Saving, Backing Up, and Restoring NE Data...........................................................................................21-14 21.7.1 Saving and Backing Up the NE Data Periodically...........................................................................21-14 21.7.2 Saving and Backing Up NE Data Immediately................................................................................21-20 21.7.3 Checking the Backup of the NE Configuration Data.......................................................................21-23 21.7.4 Restoring the NE Data Immediately................................................................................................21-25 x Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-11-19)
Contents
A Acronyms and Abbreviations................................................................................................A-1
Issue 03 (2010-11-19)
xi
Figures
Figures
Figure 1-1 Example network of outband network management........................................................................1-25 Figure 1-2 Example network of outband network management........................................................................1-31 Figure 1-3 Example network of inband network management..........................................................................1-38 Figure 1-4 Example network of inband network management..........................................................................1-44 Figure 6-1 Flowchart for configuring the DHCP relay function..........................................................................6-2 Figure 7-1 Example network of the ADSL access service...................................................................................7-3 Figure 7-2 Flowchart for configuring the IPoA access service............................................................................7-6 Figure 7-3 Flowchart for configuring the PPPoA access service.......................................................................7-13 Figure 7-4 Flowchart for configuring the IPoE access service..........................................................................7-18 Figure 7-5 Flowchart for configuring the PPPoE access service.......................................................................7-23 Figure 7-6 Example network of the ADSL IPoA access service.......................................................................7-27 Figure 7-7 Example Network of the VDSL2 PPPoE Service............................................................................7-33 Figure 8-1 Flowchart for configuring multicast services.....................................................................................8-2 Figure 9-1 Flowchart for configuring the multicast service of the subtending device (Device A)......................9-2 Figure 9-2 Flowchart for configuring the multicast service of the subtending device (Device B)......................9-3 Figure 9-3 Example network of the multicast service of subtend device.............................................................9-6 Figure 10-1 Flowchart for configuring the triple play service-ADSL access....................................................10-2 Figure 10-2 Example network of the triple play service....................................................................................10-6 Figure 11-1 Flowchart for configuring the wholesale service............................................................................11-2 Figure 11-2 Example network of the wholesale service ...................................................................................11-4 Figure 12-1 Flowchart for configuring the private line service.........................................................................12-2 Figure 12-2 Example network for private line service configuration ...............................................................12-3 Figure 13-1 Flowchart for configuring the CESoP TDM private line service ..................................................13-2 Figure 13-2 Example network of the CESoP TDM private line service ...........................................................13-6 Figure 15-1 Flowchart for configuring the Ethernet OAM diagnosis................................................................15-2 Figure 15-2 Example network of the Ethernet OAM.........................................................................................15-5 Figure 15-3 Example network of the Ethernet OAM.......................................................................................15-11
Issue 03 (2010-11-19)
xiii
Tables
Tables
Table 1-1 Data plan for outband network management in a U2000 single-server system.................................1-26 Table 1-2 Data plan for outband network management in a U2000 HA system................................................1-26 Table 1-3 Data plan for outband network management in a U2000 single-server system.................................1-31 Table 1-4 Data plan for outband network management in a U2000 HA system................................................1-32 Table 1-5 Data plan for inband network management in a U2000 single-server system...................................1-38 Table 1-6 Data plan for inband network management in a U2000 HA system..................................................1-39 Table 1-7 Data plan for inband network management in a U2000 single-server system...................................1-45 Table 1-8 Data plan for inband network management in a U2000 HA system..................................................1-45 Table 2-1 VLAN types and their applications......................................................................................................2-3 Table 2-2 VLAN attributes...................................................................................................................................2-4 Table 2-3 ACL classification................................................................................................................................2-8 Table 6-1 L3 forwarding mode.............................................................................................................................6-3 Table 7-1 Data plan for the ADSL service in IPoA mode..................................................................................7-27 Table 7-2 Data plan for the VDSL2 PPPoE service...........................................................................................7-34 Table 9-1 Data plan for the multicast service in subtend mode ..........................................................................9-6 Table 10-1 Triple play implementation - xDSL access......................................................................................10-4 Table 10-2 Data plan for the triple play service.................................................................................................10-7 Table 13-1 Data plan for the CESoP TDM private line service.........................................................................13-6 Table 14-1 Data plan for the active/standby switchover for the IPM dual upstream.........................................14-4 Table 15-1 Data plan for the Ethernet OAM....................................................................................................15-12
Issue 03 (2010-11-19)
xv
1 Managing Devices
1
About This Chapter
Context
Managing Devices
The U2000 provides the graphical management function for devices. After the NEs are added to the topology view, the U2000 can display the physical status of the devices in the NE Pane for device maintenance and management.
When an NE is managed by several U2000s, the NE will fail to be added and the NE data synchronization will also fail. l l When you synchronize the data of an NE that is managed by the U2000 of different versions, an error message will be displayed indicating that NE data synchronization fails. When an NE is added to several U2000s, an error message will be displayed indicating that the NE fails to be added.
1.1 Configuring the xFTP Service This topic describes how to configure the FTP, SFTP, or TFTP service on Windows, Solaris, or Linux OS and how to check the xFTP service on the U2000. 1.2 Setting the Communication Parameters This topic describes how to set the device handshake parameters and SNMP trap port number to set up the communication between the device and U2000. The device automatically sends the trap packet to the U2000 periodically to report the exception event and error alarm to the U2000. The U2000 determines whether the device is running in the normal state and manages the device. 1.3 Adding an OLT to the U2000 This topic describes how to add an OLT to the U2000. You can manage devices in a centralized manner on the U2000. 1.4 Bulk Adding NEs to the U2000 This topic describes how to bulk add NEs to the U2000 to manage the NEs in a centralized manner. 1.5 Adding a Shelf To increase the access capacity of the UA5000(IPMB) and reduce costs, you need to add a local slave shelf on the U2000 and the device. After you add the slave shelf successfully, the control
Issue 03 (2010-11-19) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-1
1 Managing Devices
card in the slave shelf works in the normal state. The service cards in the slave shelf, however, work in the normal state only after you confirm them. 1.6 Adding an Inter-shelf Link When the master shelf needs to communicate with the slave shelf to manage the cards in the slave shelf in a unified manner, you need to perform this operation. After the inter-shelf link is added successfully, if the physical lines connecting the inter-shelf link and the slave shelf are correct, the slave shelf changes to the normal state and the cards in the slave shelf can be managed by the master shelf in a unified manner. 1.7 Configuring the Information About Physical Resources This topic describes how to configure the information about physical resources that cannot be obtained from devices. This facilitates resource management and search. 1.8 Collecting Statistics on Physical Resources Physical resources include telecommunications rooms, racks, NEs, shelves, cards, subcards, ports, and ONUs. The U2000 can collect statistics on network-wide physical resources and save the statistics in files of different types, thereby making it convenient for users to view the statistics. 1.9 Configuration Example of Outband Network Management (Based on the SNMPv1 or SNMPv2c Protocol) This topic describes how to manage and maintain the UA5000(IPMB) in the outband network management mode on the U2000. In the outband network management mode, non-service channels provided by managed devices are used to transmit management information, that is, the management channels and the service channels are separated. Therefore, compared with inband network management, outband network management provides more reliable device management channels. 1.10 Configuration Example of Outband Network Management (Based on the SNMPv3 Protocol) This topic describes how to manage and maintain the UA5000(IPMB) in the outband network management mode on the U2000. In the outband network management mode, non-service channels provided by managed devices are used to transmit management information, that is, the management channels and the service channels are separated. Therefore, compared with inband network management, outband network management provides more reliable device management channels. 1.11 Configuration Example of Inband Network Management (Based on the SNMPv1 or SNMPv2c Protocol) This topic describers how to manage and maintain the UA5000(IPMB) in the inband network management mode on the U2000. In the inband network management mode, the service channels provided by managed devices are used to transmit management information. Therefore, compared with outband network management, inband network management provides a more flexible networking mode without extra devices and is cost-effective. Nevertheless, network maintenance is difficult. 1.12 Configuration Example of Inband Network Management (Based on the SNMPv3 Protocol) This topic describers how to manage and maintain the UA5000(IPMB) in the inband network management mode on the U2000. In the inband network management mode, the service channels provided by managed devices are used to transmit management information. Therefore, compared with outband network management, inband network management provides a more flexible networking mode without extra devices and is cost-effective. Nevertheless, network maintenance is difficult.
1-2
Issue 03 (2010-11-19)
1 Managing Devices
1.1 Configuring the xFTP Service

This topic describes how to configure the FTP, SFTP, or TFTP service on Windows, Solaris, or Linux OS and how to check the xFTP service on the U2000. 1.1.1 Configuring the FTP, SFTP, or TFTP Service (Windows) This topic describes how to configure and start the FTP, SFTP, or TFTP service on Windows OS. NE software communicates with the client or NEs through the FTP, SFTP, or TFTP protocol for NE upgrade, data backup, and patch installation. 1.1.2 Configuring the FTP, SFTP, or TFTP Service (Solaris) This topic describes how to configure and start the FTP, SFTP, or TFTP service on Solaris OS. The DC communicates with clients or NEs by using the FTP, SFTP, or TFTP protocol to upgrade NEs, back up data, and install patches. 1.1.3 Configuring the FTP, SFTP, or TFTP Service (Linux) This topic describes how to configure and start the FTP, SFTP, or TFTP service on Linux OS. The DC communicates with clients or NEs by using the FTP, SFTP, or TFTP protocol to upgrade NEs, back up data, and install patches. 1.1.4 Configuring the xFTP Watcher When NE data is synchronized to the U2000 server in FTP or SFTP mode, you need to configure the xFTP watcher. If you configure the xFTP watcher correctly, the NE data is successfully synchronized to the U2000 server and the U2000 successfully manages the NEs whose data is synchronized in xFTP mode. 1.1.5 Configuring the xFTP File in the NAT Networking Mode In the NAT networking mode, the xFTP must be configured to ensure that the device data can be synchronized to the U2000 server automatically.
1.1.1 Configuring the FTP, SFTP, or TFTP Service (Windows)

This topic describes how to configure and start the FTP, SFTP, or TFTP service on Windows OS. NE software communicates with the client or NEs through the FTP, SFTP, or TFTP protocol for NE upgrade, data backup, and patch installation.
Context
l l The third-party tool must be started after the FTP, SFTP, or TFTP server is configured. The file transfer parameters set on the U2000 must be the same as the parameters set on the FTP, SFTP, or TFTP server.
Procedure
l Configuring the FTP server by using the third-party tool wftpd32.exe 1. 2. Copy the wftpd32.exe file to the U2000 server and double-click the file. In the dialog box that is displayed, choose Security > Users/rights and create a user; choose Security > Host/net and enter the IP address of the FTP server.
Issue 03 (2010-11-19)
1-3
1 Managing Devices
Configuring the SFTP server by using the third-party tool msftpsrvr.exe 1. 2. Copy the msftpsrvr.exe file to the U2000 server and double-click the file. In the dialog box that is displayed, create a user.
Configuring the TFTP server by using the third-party tool tftpd32.exe 1. 2. Copy the tftpd32.exe file to the U2000 server and double-click the file. In the dialog box that is displayed, set the root directory and the IP address of the TFTP server.
Testing the communication between the FTP, SFTP, or TFTP service and the NE software
1-4
Issue 03 (2010-11-19)
1 Managing Devices
1. 2.
Choose Administration > NE Software Management > FTP Settings from the main menu. In the dialog box that is displayed, click the File Transfer Service Setting tab to configure the parameters of the file transfer service.
NOTE
l File Transfer Service Root Directory configured on the U2000 must be the same as the root directory configured on the FTP, SFTP, or TFTP server. In addition, the FTP, SFTP, or TFTP server must be started. l If the FTP protocol is used, ensure that the user name and password set in the last step are the same as the user name and password set when the FTP server is configured. l If the SFTP protocol is used, ensure that the user name, password, and port number set in the last step are the same as the user name, password, and port number set when the SFTP server is configured. l Click Test FTP, Test SFTP, or Test TFTP to check the configuration of the file transfer service.
3.
Click the Transfer Protocol tab. Select a proper protocol from the Protocol dropdown list for file transfer between NEs and the U2000 server.
Issue 03 (2010-11-19)
1-5
1 Managing Devices
4. ----End
Click OK.
1.1.2 Configuring the FTP, SFTP, or TFTP Service (Solaris)

This topic describes how to configure and start the FTP, SFTP, or TFTP service on Solaris OS. The DC communicates with clients or NEs by using the FTP, SFTP, or TFTP protocol to upgrade NEs, back up data, and install patches.
Prerequisite
You must be logged in to the Solaris OS as user root.
Context
l l In the case of the Solaris- or Linux-based U2000, the FTP, SFTP, or TFTP function provided by the Solaris or Linux OS is used. On Solaris OS, the FTP, SFTP, or TFTP server can be configured in the command line interface (CLI). The configuration method varies with OS versions. The following section describes the configuration processes on the Solaris 8 and Solaris 10 OSs in details. The root directory, user name, and password of the FTP, SFTP, or TFTP service must be the same as those that are set on the U2000 client.
Procedure
l Configure the FTP server. 1. To start the FTP service, run the following commands: Solaris 8: # cd /etc/init.d
1-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-11-19)
1 Managing Devices
# ./inetsvc start Solaris 10: # inetconv -i /etc/inet/inetd.conf 1>/dev/null 2>&1 # svcadm enable svc:/network/ftp 2. To check whether the FTP service is started, run the # netstat -a | grep ftp command.
NOTE
If the following message is displayed, it indicates that the FTP service is started.
*.tftp *.tftp Idle *.ftp LISTEN *.ftp 0 0 49152 0 LISTEN Idle *.* *.* 0 0 49152 0
3.
To create an FTP user and set its user name and password, run the following commands:
# useradd -d /tftpboot -s /bin/bash ftpuser # passwd ftpuser New Password: ftp123 Re-enter new Password: ftp123
Configure the SFTP server. 1. If the ssh service is not started, perform the following steps to start it: (1) In the /etc/ssh/sshd_config file, change PasswordAuthentication no to PasswordAuthentication yes and PermitRootLogin no to PermitRootLogin yes. (2) Run the svcadm refresh svc:/network/ssh:default command. 2. To check whether the ssh service is started on Solaris OS, run the svcs -a |grep ssh command.
NOTE
If the following message is displayed, it indicates that the ssh service is started on Solaris OS.
online *.tftp May_04 svc:/network/ssh:default
3.
To create an SFTP user and set its user name and password, run the following commands:
# useradd -d /tftpboot sftpuser # passwd sftpuser
Configure the TFTP server. 1. 2. 3. On the Common Desktop Environment (CDE) desktop, right-click and choose File > File Manager from the shortcut menu. Locate the inetd.conf file in the etc directory and double-click the file to open the file. Search for the tftp dgram udp6 wait root /usr/sbin/in.tftpd in.tftpd -s /tftpboot command.
NOTE
If the command does not exist, add it to the file. If the command exists but is commented out by the pound sign (#), delete the pound sign and save the file.
4.
Issue 03 (2010-11-19)
Start the TFTP service.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-7
1 Managing Devices
Solaris 8: Run the ./inetsvc start command in the /etc/init.d path to start the TFTP service. After the service is started, the default TFTP file path is /tftpboot. Solaris 10: Run the inetconv -i /etc/inet/inetd.conf 1>/dev/null 2>&1 command, and then run the svcadm enable svc:/network/tftp/udp6:default command to start the TFTP service. After the service is started, the default TFTP file path is / tftpboot.
NOTE
If the /etc/inet/inetd.conf configuration file is modified, you need to stop the TFTP service and then restart it. To stop the TFTP service, do as follows: l Solaris 8: Run the ./inetsvc stop command in the /etc/init.d path. l Solaris 10: Run the svcadm disable svc:/network/tftp/udp6:default command.
5. l
Run the #svcs |grep tftp command to check whether the TFTP service is started on Solaris OS.
Testing the communication between the FTP, SFTP, or TFTP service and the NE software 1. 2. Choose Administration > NE Software Management > FTP Settings from the main menu. In the dialog box that is displayed, click the File Transfer Service Setting tab to configure the parameters of the file transfer service.
1-8
Issue 03 (2010-11-19)
NOTE
1 Managing Devices
l File Transfer Service Root Directory configured on the U2000 must be the same as the root directory configured on the FTP, SFTP, or TFTP server. In addition, the FTP, SFTP, or TFTP server must be started. l If the FTP protocol is used, ensure that the user name and password set in the last step are the same as the user name and password set when the FTP server is configured. l If the SFTP protocol is used, ensure that the user name, password, and port number set in the last step are the same as the user name, password, and port number set when the SFTP server is configured. l Click Test FTP, Test SFTP, or Test TFTP to check the configuration of the file transfer service.
3.
Click the Transfer Protocol tab. Select a proper protocol from the Protocol dropdown list for file transfer between NEs and the U2000 server.
4. ----End
Click OK.
1.1.3 Configuring the FTP, SFTP, or TFTP Service (Linux)

This topic describes how to configure and start the FTP, SFTP, or TFTP service on Linux OS. The DC communicates with clients or NEs by using the FTP, SFTP, or TFTP protocol to upgrade NEs, back up data, and install patches.
Prerequisite
You must be logged in to the Linux OS as user root.
Issue 03 (2010-11-19)
1-9
1 Managing Devices
Context
l l l In the case of the Solaris- or Linux-based U2000, the FTP, SFTP, or TFTP function provided by the Solaris or Linux OS is used. The root directory, user name, and password of the FTP, SFTP, or TFTP service must be the same as those that are set on the U2000 client. In a distributed system, you need to configure the FTP or SFTP service on the master server and the slave server that is deployed with the access NE management instance by following the same procedure.
Procedure
l Configure the FTP server. 1. To create an FTP user and set its user name and password, run the following commands:
# useradd -d /tftpboot -s /bin/bash ftpuser # passwd ftpuser New Password: ftp123 Re-enter new Password: ftp123
2.
Restart the FTP service. To stop the FTP service, run the following commands: # cd /etc/init.d # /xinetd stop To start the FTP service, run the following commands: # cd /etc/init.d # ./xinetd start
Configure the SFTP server. 1. In the terminal window, run the useradd -d /ftpboot -m -s /bin/bash ftpuser command to create an SFTP user. ftpuser in the command indicates the SFTP user name. Restart the OS. After the OS is restarted, run the passwd ftpuser command to change the password of the SFTP user to ftpuser. In the /etc/ssh/sshd_config file, change PasswordAuthentication no to PasswordAuthentication yes to allow the SFTP user to log in to the Linux OS after entering the password. After the configuration file is modified, run the /etc/init.d/sshd stop command to stop the SFTP service. Run the /etc/init.d/sshd start command to start the SFTP service. Run the sftp servername@localhost command to connect to the server.
2. 3. 4.
5. 6. 7. l
Configure the TFTP server. 1. To configure the TFTP server by using the YaST, do as follows: (1) Click YaST. The administrator setting panel is displayed. (2) Choose Network Services > TFTP Server. The TFTP Server Configuration window is displayed, as shown in the following figure.
1-10
Issue 03 (2010-11-19)
1 Managing Devices
2.
To configure the TFTP server by using the Konsole, do as follows: (1) In the terminal window, run the cd /etc/xinetd.d command to navigate to the / etc/xinetd.d directory. Then, run the vi tftp command to open the tftp file. (2) Set disable to no (that is, disable = no) to start the TFTP server.
NOTE
To stop the TFTP service, set disable to yes (that is, disable = yes) in the tftp file. To restart the TFTP service, run the /etc/init.d/xinetd restart command.
----End
1.1.4 Configuring the xFTP Watcher

When NE data is synchronized to the U2000 server in FTP or SFTP mode, you need to configure the xFTP watcher. If you configure the xFTP watcher correctly, the NE data is successfully synchronized to the U2000 server and the U2000 successfully manages the NEs whose data is synchronized in xFTP mode.
Prerequisite
The third-party software must be available for configuring the FTP server if more than 5,000 NEs are managed. The FTP or SFTP server must be configured and the xFTP service must be enabled. For details, see 1.1.1 Configuring the FTP, SFTP, or TFTP Service (Windows), 1.1.2 Configuring the FTP, SFTP, or TFTP Service (Solaris), and 1.1.3 Configuring the FTP, SFTP, or TFTP Service (Linux).
Context
Data synchronization in xFTP mode is implemented based on the FTP or SFTP protocol. To improve the efficiency of synchronizing NE data, NEs upload their data in the form of files to the U2000 by using the FTP or SFTP protocol. The UA5000IPMB V100R019C00 supports data synchronization in xFTP mode.
1 Managing Devices
NOTE
l In the case of the NE whose data is synchronized in SNMP mode, you do not need to configure the xFTP watcher. l The U2000 synchronizes data in FTP or SFTP mode, not in TFTP mode. l After the U2000 that is newly installed is started successfully, it automatically configures the xFTP watcher. Therefore, you do not need to modify the default configuration unless it is necessary.
Procedure
1 Choose Administration > Settings > xFtpWatcher from the main menu. 2 In the xFtpWatcher dialog box, click Add. 3 In the dialog box that is displayed, set the parameters.
NOTE
l The default values of Username, Password, and Root path of the U2000 FTP service are ftpuser, u2000ftpuser, d: (Windows-based server) or /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 FTP 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 FTP 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 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.
----End
1.1.5 Configuring the xFTP File in the NAT Networking Mode

In the NAT networking mode, the xFTP must be configured to ensure that the device data can be synchronized to the U2000 server automatically.
1 Managing Devices
Prerequisite
The xFTP watcher of the U2000 must be configured, the FTP server must be configured successfully, and the FTP service must be enabled. For details, see 1.1.4 Configuring the xFTP Watcher.
Context
l If the NAT networking mode is adopted or the U2000 manages NEs in multiple separated network segments, you need to create the iptable_ne2nms.cfg file manually and configure it to ensure that the device data is synchronized to the U2000 server automatically. In the distributed NAT networking mode, the iptable_ne2nms.cfg file must be configured on the master server.
Procedure
1 Open the iptable_ne2nms.cfg file in the installation directory $IMAPROOT/server/etc/ conf/ of the U2000 server. 2 Configure the iptable_ne2nms.cfg file. Each line added to the configuration file indicates a mapping configuration. The format of the mapping configurations is as follows: NE start IP address NE end IP address U2000 IP address [the IP address of the U2000 after NAT translation] The parameters are separated with white spaces or tab spaces. l NE start IP address and NE end IP address: Specify the IP address range of NEs. l U2000 IP address: Indicates the external IP address that the U2000 at a site uses to communicate with NEs. The IP address ranges of the NEs at different sites can overlap. l The IP address of the U2000 after NAT translation: If the NAT networking mode is adopted between the U2000 and NEs, this parameter must be specified. Otherwise, this parameter does not need to be specified. For example, if the NAT networking mode is not adopted, the mapping configuration is 10.71.226.1 10.71.226.255 10.71.221.153. If the NAT networking mode is adopted, the mapping configuration is 10.71.227.1 10.71.227.255 10.71.221.152 10.10.10.10. ----End
Example
In the NAT networking mode, the IP address of the U2000 server is 136.12.36.2 and the IP address changes to 198.168.23.25 after the mapping on the firewall. The IP addresses of certain devices are in the 198.0.0.0 network and these devices can communicate with the U2000 through the mapping address of the U2000 server. The IP addresses of other devices are in the 136.0.0.0 network and these devices can communicate with the U2000 server. In this case, configure the iptable_ne2nms.cfg file as follows: 136.0.0.1 136.0.0.255 136.12.36.2 198.0.0.1 198.0.0.255 136.12.36.2 198.168.23.25
1 Managing Devices
1.2 Setting the Communication Parameters

This topic describes how to set the device handshake parameters and SNMP trap port number to set up the communication between the device and U2000. The device automatically sends the trap packet to the U2000 periodically to report the exception event and error alarm to the U2000. The U2000 determines whether the device is running in the normal state and manages the device. 1.2.1 Setting the SNMP Parameters This topic describes how to set the SNMP parameters. The set SNMP parameters need to be consistent with the parameters on the device. You can directly use the set SNMP parameter profile when adding a device. 1.2.2 Setting the NE Handshake Parameters By setting the device handshake parameters, you can learn the communication status between the device and the U2000. The device initiates the handshake request actively, and sends the handshake packets on a timed basis. If the U2000 receives the handshake packets on a timed basis, the system considers that the current communication is in the normal state.
1.2.1 Setting the SNMP Parameters

This topic describes how to set the SNMP parameters. The set SNMP parameters need to be consistent with the parameters on the device. You can directly use the set SNMP parameter profile when adding a device.
Context
Currently, the SNMP protocol is most widely applied in computer networks. The SNMP protocol ensures that the management information is transmitted between any two nodes. This facilitates the operations of the network administrator in terms of retrieving information, modifying information, locating faults, diagnosing faults, planning capacities, and generating reports on any node in the network. The SNMP protocol uses the polling mechanism and provides the most basic function set to implement the User Datagram Protocol (UDP) that runs on the transmission layer and is based on the connectionless mode. Hence, the SNMP protocol can implement obstacle-free connections with multiple products.
NOTE
l The profile name must be unique. l Currently, the default name of the get community is public and the default name of the set community is private. l To ensure the device security, sometimes you need to change the get community name and set community name. Then, when adding a device, you need to set Device Access Protocol Parameters to choose the corresponding the get community name and set community name. Otherwise, the adding may fail. l After setting the SNMP parameters, you can test whether the SNMP parameters on the U2000 are consistent with the SNMP parameters on the device by performing Step 6 to Step 7.
Procedure
1 Choose Administration > NE Communicate Parameter > NE Access Protocol Parameters from the main menu.
1 Managing Devices
2 On the tab page that is displayed, click Reset. In the dialog box that is displayed, click the corresponding tab, and then click Add. 3 In the dialog box that is displayed, set the Template Name, Get Community, and Set Community parameters.
Issue 03 (2010-11-19)
1-15
1 Managing Devices
NOTE
When clicking the SNMPv3 Parameters tab, you can configure the related parameters.
4 Click OK. 5 Select the added SNMP parameters. Click OK. 6 In the dialog box that is displayed, click Yes to test the set SNMP parameters. 7 The U2000 displays the Loading dialog box. After the testing is complete, click OK. ----End
1.2.2 Setting the NE Handshake Parameters

By setting the device handshake parameters, you can learn the communication status between the device and the U2000. The device initiates the handshake request actively, and sends the handshake packets on a timed basis. If the U2000 receives the handshake packets on a timed basis, the system considers that the current communication is in the normal state.
Context
The handshake duration between the device and the U2000 determines the handshake frequency. If the duration is too short, the U2000 may face a heavy burden when managing too many devices and processing too many handshake packets. If the duration is too long, the U2000 cannot immediately detect the disconnection between the device and U2000. You can set proper handshake duration according to the requirements.
1-16
Issue 03 (2010-11-19)
1 Managing Devices
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose NE Properties > Configure NE Handshake Parameter from the navigation tree on the tab page that is displayed. 3 Select the Device Handshake Switch check box in the view on the right side, and set the device handshake duration. 4 Click Apply. ----End
1.3 Adding an OLT to the U2000

This topic describes how to add an OLT to the U2000. You can manage devices in a centralized manner on the U2000.
Prerequisite
The FTP server must be configured correctly and the FTP service must be enabled. For details, see 1.1 Configuring the xFTP Service.
Context
When an NE is managed by several U2000s, the NE will fail to be added and the NE data synchronization will also fail. l l l When you synchronize the data of an NE that is managed by the U2000 of different versions, an error message will be displayed indicating that NE data synchronization fails. When an NE is added to several U2000s, an error message will be displayed indicating that the NE fails to be added. The SNMP parameters on the U2000 must be the same as the SNMP parameters on the device. These parameters include the protocol version, read community name, and write community name. When adding multi-service access nodes (MSANs), you can add the UA5000(IPMB) and UA5000(PVM) at the same time. Make sure that the SNMP parameters of the two devices are the same and that the SNMP parameters on the U2000 are the same as the SNMP parameters on the two devices. The UA5000(IPMB) and UA5000(PVM) can be discovered automatically by the U2000. If a device fails to be added, check whether the settings of the SNMP parameters on the U2000 are the same as the SNMP parameters on the device and the SNMP parameters are activated. For details, see 1.2.1 Setting the SNMP Parameters.
NOTE
A mini-EMS supports up to 25 OLTs. To add more OLTs, you must delete certain OLTs first.
Procedure
l
Issue 03 (2010-11-19)
Add an OLT to the U2000.

1 Managing Devices
1. 2.
In the Main Topology, right-click in the Physical Root navigation tree and choose New > NE from the shortcut menu. In the dialog box that is displayed, set the parameters.
3.
Click OK.
NOTE
In the dialog box that is displayed, the system displays a message indicating that it takes several seconds or dozens of minutes to load the device data. After the device data is loaded and read successfully, the system automatically refreshes the device icon.
----End
Result
If the icon of the NE is gray or has a sign like a gear in the upper left corner in the Main Topology, you need to right-click the NE and choose Synchronize NE Data from the shortcut menu.
1.4 Bulk Adding NEs to the U2000

This topic describes how to bulk add NEs to the U2000 to manage the NEs in a centralized manner.
Prerequisite
l l The FTP server must be configured correctly and the FTP service must be enabled. For details, see 1.1.4 Configuring the xFTP Watcher. The SNMP parameters on the U2000 must be the same as the SNMP parameters on the NEs. These parameters include the protocol version, get community name, and set community name. For details, see 1.2.1 Setting the SNMP Parameters.
Context
When an NE is managed by several U2000s, the NE will fail to be added and the NE data synchronization will also fail.
1 Managing Devices
l l
When you synchronize the data of an NE that is managed by the U2000 of different versions, an error message will be displayed indicating that NE data synchronization fails. When an NE is added to several U2000s, an error message will be displayed indicating that the NE fails to be added.
Procedure
1 Choose File > Discovery > NE from the main menu. 2 In the dialog box that is displayed, click the SNMP/ICMP NE Search tab and set the parameters.
NOTE
l In the NE Type field, select the required device type. By default, the value is All Device Types. l Click Default SNMP Parameter to set the SNMP parameters on the U2000 for successful communications between the U2000 and NEs. l Click Add to configure the range of IP addresses of automatically discovered NEs in the IP address Range area.
3 Click Next. The U2000 starts searching for NEs and reading the data of the NEs in real time. ----End
1.5 Adding a Shelf

To increase the access capacity of the UA5000(IPMB) and reduce costs, you need to add a local slave shelf on the U2000 and the device. After you add the slave shelf successfully, the control card in the slave shelf works in the normal state. The service cards in the slave shelf, however, work in the normal state only after you confirm them.
1 Managing Devices
Context
l l l l When adding a shelf, you must enter the correct shelf type. Otherwise, the cards in the shelf cannot work in the normal state. After adding a slave shelf, you must connect the master shelf with the slave shelf correctly by using a data cable. Otherwise, the slave shelf cannot work in the normal state. The common types of master shelves are HABD, HABA, and HABL. The common types of slave shelves are HABE and HABB. When adding a slave shelf for a master shelf, ensure that the slave shelf is compatible with the master shelf. Otherwise, the slave shelf fails to be added. Pay attention to the following when adding a slave shelf for a master shelf: The shelves of the H601/H602 and H612 types cannot be used as the master shelf and the slave shelf at the same time. The H601HABL master shelves do not support any slave shelf. If the slave shelf works as the master shelf, you cannot add a slave shelf any more.
Procedure
1 In the Physical Root navigation tree, right-click the required device and choose Add Frame from the shortcut menu. 2 In the dialog box that is displayed, set the parameters such as Name, Number, and Type.
3 Click OK. ----End
1.6 Adding an Inter-shelf Link

When the master shelf needs to communicate with the slave shelf to manage the cards in the slave shelf in a unified manner, you need to perform this operation. After the inter-shelf link is added successfully, if the physical lines connecting the inter-shelf link and the slave shelf are correct, the slave shelf changes to the normal state and the cards in the slave shelf can be managed by the master shelf in a unified manner.
1-20
Issue 03 (2010-11-19)
1 Managing Devices
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose Inter-frame Link Management from the navigation tree on the tab page that is displayed. 3 Right-click, and then choose Add. 4 In the dialog box that is displayed, set the Frame, Slot, Port, and Link direction parameters.
5 Click OK. ----End
1.7 Configuring the Information About Physical Resources

This topic describes how to configure the information about physical resources that cannot be obtained from devices. This facilitates resource management and search.
Procedure
l Configure the information about the rack. 1. 2. Choose Inventory > Physical Inventory > Rack from the main menu. Click the Rack List tab. (1) To create a rack, right-click in the information list and choose New from the shortcut menu. In the dialog box that is displayed, configure the information about the rack.
Issue 03 (2010-11-19)
1-21
1 Managing Devices
(2) To add a shelf to the rack, click the Shelf Information tab, right-click, and then choose Install Shelf from the shortcut menu. In the dialog box that is displayed, select the shelf that will be added to the rack.
Configure the information about the telecommunications room. 1. 2. Choose Inventory > Physical Inventory > Telecommunications Room from the main menu. Click the Telecommunications Room List tab. (1) To create a telecommunications room, right-click in the information list and choose New from the shortcut menu. In the dialog box that is displayed, configure the information about the telecommunications room. (2) To add the rack to the telecommunications room and configure the related U2000, right-click a record in the information list and choose Install Racks/NMSs from the shortcut menu. In the dialog box that is displayed, select the rack that will be added to the telecommunications room and the related U2000.
----End
Result
After configuring the information about the physical resources, you can easily query the information about the telecommunications room, rack, shelf, and card.
1-22
Issue 03 (2010-11-19)
1 Managing Devices
1.8 Collecting Statistics on Physical Resources

Physical resources include telecommunications rooms, racks, NEs, shelves, cards, subcards, ports, and ONUs. The U2000 can collect statistics on network-wide physical resources and save the statistics in files of different types, thereby making it convenient for users to view the statistics.
Context
The navigation tree on the Physical Inventory tab page provides the types of all physical inventories whose statistics can be collected. This topic considers NEs and ports as examples to describe how to collect statistics on NEs and ports.
Procedure
l To collect statistics on NEs, do as follows: 1. 2. Choose Inventory > Physical Inventory > NE from the main menu. In the window that is displayed, click the NE Statistics tab. Then, select the statistics type and statistics collection scope to query the number of NEs of different types. You can query the number of NEs of a specific type by selecting the statistics scope.
You can also customize statistics types to meet different requirements.
Issue 03 (2010-11-19)
1-23
1 Managing Devices
3.
Click the buttons in the lower right corner to implement different functions. Click Count to display the data in the server database on the client in real time. Click Save As to save data to a .xls, .txt, .html. or .csv file and save the file in the report folder in the client directory. Click Print and set Start Row and End Row to print the required contents.
To collect statistics on ports, do as follows: 1. 2. Choose Inventory > Physical Inventory > Port from the main menu. In the window that is displayed, click the Port Statistics tab. Then, select the required NE to collect the statistics on types and numbers of ports on NEs of different types.
3.
Click the buttons in the lower right corner to implement different functions. Click Count to display the data in the server database on the client in real time. Click Save As to save data to a .xls, .txt, .html. or .csv file and save the file in the report folder in the client directory. Click Print and set Start Row and End Row to print the required contents.
----End
1.9 Configuration Example of Outband Network Management (Based on the SNMPv1 or SNMPv2c Protocol)
This topic describes how to manage and maintain the UA5000(IPMB) in the outband network management mode on the U2000. In the outband network management mode, non-service channels provided by managed devices are used to transmit management information, that is, the management channels and the service channels are separated. Therefore, compared with inband network management, outband network management provides more reliable device management channels.
1 Managing Devices
Example Network
Figure 1-1 shows an example network of outband network management. The U2000 manages and maintains the UA5000(IPMB) through the maintenance network port in the outband network management mode. Therefore, you need to add a static route to the U2000 and set the related SNMP parameters on the UA5000(IPMB).
NOTE
The procedure for configuring SNMPv1-based outband network management is similar to the SNMPv2cbased outband network management. This topic considers the SNMPv1-based outband network management as an example.
Figure 1-1 Example network of outband network management
U2000 Router UA5000

GE 0/2/0
COM ETH IPMB
Data Plan
Configuring Outband Network Management in a U2000 Single-Server System The IP address of the outband network management port of the UA5000(IPMB) must be in the same network segment as the IP address of the gateway. When the IP address of the outband network management port is not in the same network segment as the IP address of the U2000, you need to configure a route to forward IP packets. The IP address of the destination host of traps is the IP address of the U2000. The U2000 parses only the traps that are reported by means of the SNMPv1 or SNMPv3 protocol. When configuring traps on the device, you need to check the version of the SNMP protocol that the device supports and configure the trap protocol to SNMPv1 or SNMPv3 accordingly. Table 1-1 provides the data plan for outband network management in a U2000 single-server system.
1 Managing Devices
Table 1-1 Data plan for outband network management in a U2000 single-server system Item IP address of the outband network management port of the UA5000(IPMB) IP address of the gateway of the UA5000 (IPMB) connected to a router Network segment of the U2000 Read community name Write community name SNMP version Data 10.10.21.2/24 10.10.20.254/24 10.10.21.1/24 public private V1
Configuring Outband Network Management in a U2000 HA System l If floating IP addresses are allocated, the active and standby servers in the U2000 HA system use a floating IP address to communicate with the device. Thus, the IP address of the destination host of traps is the floating IP address. The IP address of the outband network management port of the UA5000(IPMB) must be in the same network segment as the IP address of the gateway. When the IP address of the outband network management port is not in the same network segment as the floating IP address, you need to configure a route to forward IP packets. If floating IP addresses are not allocated, the active and standby servers in the U2000 HA system use different IP addresses to communicate with the device. The IP address of the outband network management port of the UA5000(IPMB) must be in the same network segment as the IP address of the gateway. When the IP address of the outband network management port is not in the same network segment as the IP addresses of the active and standby servers, you need to configure a route to forward IP packets.
Table 1-2 provides the data plan for outband network management in a U2000 HA system. Table 1-2 Data plan for outband network management in a U2000 HA system Item IP address of the outband network management port of the UA5000(IPMB) IP address of the U2000 (floating IP addresses are allocated) IP address of the U2000 (floating IP addresses are not allocated) Data 10.10.20.2/24 Floating IP address: 10.10.21.1/24 IP address of the active server: 10.10.21.1/24 IP address of the standby server: 10.10.21.2/24 10.10.20.254/24 public
Issue 03 (2010-11-19)
IP address of the gateway of the UA5000 (IPMB) connected to a router Read community name
1-26
1 Managing Devices
Item Write community name SNMP version
Data private V1
Procedure
1 Configure outband network management on the device. In the case of the U2000 single-server system, the procedure is as follows: 1. Configure the IP address of the maintenance network port.
NOTE
By default, the IP address of the maintenance network port is 10.11.104.2, and the subnet mask is 255.255.255.0.
huawei(config)#interface meth 0 huawei(config-if-meth0)#ip address 10.10.20.2 255.255.255.0 huawei(config-if-meth0)#quit 2. 3. Add a route for outband network management. huawei(config)#ip route-static 10.10.21.0 24 10.10.20.254 Set the SNMP parameters. l Set the community names and access rights. huawei(config)#snmp-agent community read public huawei(config)#snmp-agent community write private l (Optional) Set the administrator identifier and the way to contact the administrator. huawei(config)#snmp-agent sys-info contact HW-075528780808 l (Optional) Set the location information about the device. huawei(config)#snmp-agent sys-info location Shenzhen_China l Set the SNMP version.
NOTE
The SNMP version must be the same as the SNMP version set on the U2000. Assume that the SNMP version on the U2000 is V1.
huawei(config)#snmp-agent sys-info version v1 4. 5. Enable the reporting of traps. huawei(config)#snmp-agent trap enable standard Configure the IP address of the destination host of the traps. huawei(config)#snmp-agent target-host trap-hostname huawei address 10.10.21.1 trap-paramsname ABC huawei(config)#snmp-agent target-host trap-paramsname ABC v1 securityname private 6. 7.
Issue 03 (2010-11-19)
Set the IP address of the maintenance network port as the source IP address of the traps. huawei(config)#snmp-agent trap source meth 0 Save the data.
1 Managing Devices
huawei(config)#save In the case of the U2000 HA system, the procedure for configuring outband network management on the device varies with the IP address allocation scheme. l When floating IP addresses are allocated, the procedure for configuring outband network management on the device in the U2000 HA system is the same as that in the U2000 singleserver system. l When floating IP addresses are not allocated, the procedure for configuring outband network management on the device is as follows: 1. Configure the IP address of the maintenance network port. huawei(config)#interface meth 0 huawei(config-if-MEth0)#ip address 10.10.20.2 255.255.255.0 2. 3. Add a route for outband network management. huawei(config)#ip route-static 10.10.21.0 24 10.10.20.254 Set the SNMP parameters. l Set the community names and access rights. huawei(config)#snmp-agent community read public huawei(config)#snmp-agent community write private l (Optional) Set the administrator identifier and the way to contact the administrator. huawei(config)#snmp-agent sys-info contact HW-075528780808 l (Optional) Set the location information about the device. huawei(config)#snmp-agent sys-info location Shenzhen_China l Set the SNMP version.
NOTE
huawei(config)#snmp-agent sys-info version v1 4. 5. Enable the reporting of traps. huawei(config)#snmp-agent trap enable standard Configure the IP address of the destination host of the traps. huawei(config)#snmp-agent target-host trap-hostname huawei address 10.10.21.1 trap-paramsname ABC1 huawei(config)#snmp-agent target-host trap-paramsname ABC1 v1 securityname private huawei(config)#snmp-agent target-host trap-hostname huawei address 10.10.21.2 trap-paramsname ABC2 huawei(config)#snmp-agent target-host trap-paramsname ABC2 v1 securityname private 6. 7. Set the IP address of the maintenance network port as the source IP address of the traps. huawei(config)#snmp-agent trap source meth 0 Save the data. huawei(config)#save 2 Configure outband network management on the U2000.
1 Managing Devices
1.
Configure the route connecting the U2000 server and the network management port.
NOTE
If the IP address of the network management port and the IP address of the U2000 are in the same network segment, you do not need to configure the route.
l Solaris OS: To add a route, run the route add 10.10.21.1 10.10.20.1 command. To query the information about the current routing table, run the netstat -r command. l Windows OS: To add a route, run the route add 10.10.21.1 mask 255.255.255.0 10.10.20.1 command To query the information about the current routing table, run the route print command. 2. Set the SNMP parameters. a. b. c. Choose Administration > NE Communicate Parameter > NE Access Protocol Parameters from the main menu. On the tab page that is displayed, click Reset. In the dialog box that is displayed, click the SNMPv1 Parameters tab and click Add. In the dialog box that is displayed, set the name and SNMP parameters as follows:
d. e. f. g. 3.
Click OK. Select the new SNMP parameters and click OK. In the dialog box that is displayed, click Yes. The SNMP parameters are tested automatically. The Loading dialog box is displayed. After the test is complete and a message is displayed indicating that the test is successful, click OK. In the Main Topology, right-click in the Physical Root navigation tree and choose New > NE from the shortcut menu.
Add the device to the U2000. a.
Issue 03 (2010-11-19)
1 Managing Devices
b.
In the dialog box that is displayed, set the parameters.
c.
Click OK.
NOTE
----End
Result
After the parameters are set successfully on the U2000, the U2000 manages and maintains the UA5000(IPMB) successfully.
1.10 Configuration Example of Outband Network Management (Based on the SNMPv3 Protocol)
This topic describes how to manage and maintain the UA5000(IPMB) in the outband network management mode on the U2000. In the outband network management mode, non-service channels provided by managed devices are used to transmit management information, that is, the management channels and the service channels are separated. Therefore, compared with inband network management, outband network management provides more reliable device management channels.
Example Network
Figure 1-2 shows an example network of outband network management. The U2000 manages and maintains the UA5000(IPMB) through the maintenance network port in the outband network management mode. Therefore, you need to add a static route to the U2000 and set the related SNMP parameters on the UA5000(IPMB).
1-30
Issue 03 (2010-11-19)
1 Managing Devices
Figure 1-2 Example network of outband network management
U2000 Router UA5000

GE 0/2/0
COM ETH IPMB
Data Plan
Configuring Outband Network Management in a U2000 Single-Server System The IP address of the outband network management port of the UA5000(IPMB) must be in the same network segment as the IP address of the gateway. When the IP address of the outband network management port is not in the same network segment as the IP address of the U2000, you need to configure a route to forward IP packets. The IP address of the destination host of traps is the IP address of the U2000. The U2000 parses only the traps that are reported by means of the SNMPv1 or SNMPv3 protocol. When configuring traps on the device, you need to check the version of the SNMP protocol that the device supports and configure the trap protocol to SNMPv1 or SNMPv3 accordingly. Table 1-3 provides the data plan for outband network management in a U2000 single-server system. Table 1-3 Data plan for outband network management in a U2000 single-server system Item IP address of the outband network management port of the UA5000(IPMB) IP address of the gateway of the UA5000 (IPMB) connected to a router Network segment of the U2000 SNMP
Issue 03 (2010-11-19)
Data 10.10.21.2/24 10.10.20.254/24 10.10.21.1/24 User name: user1

1 Managing Devices
Item
Data Group name: group1 View name: hardy Authentication mode: MD5 Authentication password: auth12345678 Encryption mode: DES Encryption password: pri12345678 Version: V3
Configuring Outband Network Management in a U2000 HA System l If floating IP addresses are allocated, the active and standby servers in the U2000 HA system use a floating IP address to communicate with the device. Thus, the IP address of the destination host of traps is the floating IP address. The IP address of the outband network management port of the UA5000(IPMB) must be in the same network segment as the IP address of the gateway. When the IP address of the outband network management port is not in the same network segment as the floating IP address, you need to configure a route to forward IP packets. If floating IP addresses are not allocated, the active and standby servers in the U2000 HA system use different IP addresses to communicate with the device. The IP address of the outband network management port of the UA5000(IPMB) must be in the same network segment as the IP address of the gateway. When the IP address of the outband network management port is not in the same network segment as the IP addresses of the active and standby servers, you need to configure a route to forward IP packets.
Table 1-4 provides the data plan for outband network management in a U2000 HA system. Table 1-4 Data plan for outband network management in a U2000 HA system Item IP address of the outband network management port of the UA5000(IPMB) IP address of the U2000 (floating IP addresses are allocated) IP address of the U2000 (floating IP addresses are not allocated) Data 10.10.20.2/24 Floating IP address: 10.10.21.1/24 IP address of the active server: 10.10.21.1/24 IP address of the standby server: 10.10.21.2/24 10.10.20.254/24 User name: user1 Group name: group1
IP address of the gateway of the UA5000 (IPMB) connected to a router SNMP
1 Managing Devices
Item
Data View name: hardy Authentication mode: MD5 Authentication password: auth12345678 Encryption mode: DES Encryption password: pri12345678 Version: V3
Procedure
1 Configure outband network management on the device. In the case of the U2000 single-server system, the procedure is as follows: 1. Configure the IP address of the maintenance network port.
NOTE
By default, the IP address of the maintenance network port is 10.11.104.2, and the subnet mask is 255.255.255.0.
huawei(config)#interface meth 0 huawei(config-if-meth0)#ip address 10.10.20.2 255.255.255.0 huawei(config-if-meth0)#quit 2. 3. Add a route for outband network management. huawei(config)#ip route-static 10.10.21.0 24 10.10.20.254 Set the SNMP parameters. l Set the SNMP user, group, and view. huawei(config)#snmp-agent usm-user v3 user1 group1 authentication-mode md5 auth12345678 privacy-mode des56 pri12345678 huawei(config)#snmp-agent group v3 group1 authentication read-view hardy write-view hardy huawei(config)#snmp-agent mib-view hardy include ip l (Optional) Set the administrator identifier and the way to contact the administrator. huawei(config)#snmp-agent sys-info contact HW-075528780808 l (Optional) Set the location information about the device. huawei(config)#snmp-agent sys-info location Shenzhen_China l (Optional) Set the engine ID of the SNMP entity.
NOTE
The engine ID of the SNMP entity must be the same as that set on the U2000.
huawei(config)#huawei(config)#snmp-agent local-engineid 0123456789 l Set the SNMP version.

NOTE
Issue 03 (2010-11-19)
1-33
1 Managing Devices
huawei(config)#snmp-agent sys-info version v3 4. 5. Enable the reporting of traps. huawei(config)#snmp-agent trap enable standard Configure the IP address of the destination host of the traps. huawei(config)#snmp-agent target-host trap-hostname huawei address 10.10.21.1 trap-paramsname ABC huawei(config)#snmp-agent target-host trap-paramsname ABC v3 securityname user1 privacy 6. 7. Set the IP address of the maintenance network port as the source IP address of the traps. huawei(config)#snmp-agent trap source meth 0 Save the data. huawei(config)#save In the case of the U2000 HA system, the procedure for configuring outband network management on the device varies with the IP address allocation scheme. l When floating IP addresses are allocated, the procedure in the U2000 HA system is the same as that in the U2000 single-server system. l When floating IP addresses are not allocated, the procedure is as follows: 1. Configure the IP address of the maintenance network port. huawei(config)#interface meth 0 huawei(config-if-MEth0)#ip address 10.10.20.2 255.255.255.0 2. 3. Add a route for outband network management. huawei(config)#ip route-static 10.10.21.0 24 10.10.20.254 Set the SNMP parameters. l Set the SNMP user, group, and view. huawei(config)#snmp-agent usm-user v3 user1 group1 authentication-mode md5 auth12345678 privacy-mode des56 pri12345678 huawei(config)#snmp-agent group v3 group1 authentication read-view hardy write-view hardy huawei(config)#snmp-agent mib-view hardy include ip l (Optional) Set the administrator identifier and the way to contact the administrator. huawei(config)#snmp-agent sys-info contact HW-075528780808 l (Optional) Set the location information about the device. huawei(config)#snmp-agent sys-info location Shenzhen_China l (Optional) Set the engine ID of the SNMP entity.
NOTE
huawei(config)#snmp-agent local-engineid 0123456789 l Set the SNMP version.

NOTE
huawei(config)#snmp-agent sys-info version v3

1 Managing Devices
4. 5.
Enable the reporting of traps. huawei(config)#snmp-agent trap enable standard Configure the IP address of the destination host of the traps. huawei(config)#snmp-agent target-host trap-hostname huawei address 10.10.21.1 trap-paramsname ABC1 huawei(config)#snmp-agent target-host trap-paramsname ABC1 v3 securityname user1 privacy huawei(config)#snmp-agent target-host trap-hostname huawei address 10.10.21.2 trap-paramsname ABC2 huawei(config)#snmp-agent target-host trap-paramsname ABC2 v3 securityname user1 privacy
6. 7.
Set the IP address of the maintenance network port as the source IP address of the traps. huawei(config)#snmp-agent trap source meth 0 Save the data. huawei(config)#save
2 Configure outband network management on the U2000. 1. Configure the route connecting the U2000 server and the network management port.
NOTE
l Solaris OS: To add a route, run the route add 10.10.21.1 10.10.20.1 command. To query the information about the current routing table, run the netstat -r command. l Windows OS: To add a route, run the route add 10.10.21.1 mask 255.255.255.0 10.10.20.1 command. To query the information about the current routing table, run the route print command. 2. Set the SNMP parameters. a. b. c. Choose Administration > NE Communicate Parameter > NE Access Protocol Parameters from the main menu. On the tab page that is displayed, click Reset. In the dialog box that is displayed, click the SNMPv1 Parameters tab and click Add. In the dialog box that is displayed, set the name and SNMP parameters as follows:
Issue 03 (2010-11-19)
1-35
1 Managing Devices
NOTE
The SNMPv3 protocol supports three security levels: authentication, noauth, and privacy. The U2000 communicates with the device successfully by means of the SNMPv3 protocol only when the authentication and encryption modes of the SNMP user and SNMP group on the device and the SNMP parameters on the U2000 are the same.
d. e. f. g. 3.
Click OK. Select the new SNMP parameters and click OK. In the dialog box that is displayed, click Yes. The SNMP parameters are tested automatically. The Loading dialog box is displayed. After the test is complete and a message is displayed indicating that the test is successful, click OK. In the Main Topology, right-click in the Physical Root navigation tree and choose New > NE from the shortcut menu. In the dialog box that is displayed, set the parameters.
Add the device to the U2000. a. b.
1-36
Issue 03 (2010-11-19)
1 Managing Devices
c.
Click OK.
NOTE
----End
Result
1.11 Configuration Example of Inband Network Management (Based on the SNMPv1 or SNMPv2c Protocol)
This topic describers how to manage and maintain the UA5000(IPMB) in the inband network management mode on the U2000. In the inband network management mode, the service channels provided by managed devices are used to transmit management information. Therefore, compared with outband network management, inband network management provides a more flexible networking mode without extra devices and is cost-effective. Nevertheless, network maintenance is difficult.
Example Network
Figure 1-3 shows an example network of inband network management. The U2000 manages and maintains the UA5000(IPMB) through an upstream port in the inband network management mode. Therefore, you need to add a static route to the U2000 and set the related SNMP parameters on the UA5000(IPMB).
NOTE
The procedure for configuring SNMPv1-based inband network management is similar to the SNMPv2cbased inband network management. This topic considers the SNMPv1-based inband network management as an example.
Issue 03 (2010-11-19)
1-37
1 Managing Devices
Figure 1-3 Example network of inband network management
U2000
Router UA5000
GE 0/2/0
COM ETH IPMB
Data Plan
Configuring Inband Network Management in a U2000 Single-Server System The IP address of the inband network management port of the UA5000(IPMB) must be in the same network segment as the IP address of the gateway. When the IP address of the inband network management port is not in the same network segment as the IP address of the U2000, you need to configure a route to forward IP packets. The IP address of the destination host of traps is the IP address of the U2000. The U2000 parses only the traps that are reported by means of the SNMPv1 or SNMPv3 protocol. When configuring traps on the device, you need to check the version of the SNMP protocol that the device supports and configure the trap protocol to SNMPv1 or SNMPv3 accordingly. Table 1-5 provides the data plan for inband network management in a U2000 single-server system. Table 1-5 Data plan for inband network management in a U2000 single-server system Item IP address of the inband network management port of the UA5000(IPMB) IP address of the gateway of the UA5000 (IPMB) connected to a router Network segment of the U2000 Read community name
1-38
Data 10.10.21.2/24 10.10.20.254/24 IP address: 10.10.21.1/24 public

Issue 03 (2010-11-19)
1 Managing Devices
Item Write community name SNMP version
Data private V1
Configuring Inband Network Management in a U2000 HA System l If floating IP addresses are allocated, the active and standby servers in the U2000 HA system use a floating IP address to communicate with the device. Thus, the IP address of the destination host of traps is the floating IP address. The IP address of the inband network management port of the UA5000(IPMB) must be in the same network segment as the IP address of the gateway. When the IP address of the inband network management port is not in the same network segment as the floating IP address, you need to configure a route to forward IP packets. If floating IP addresses are not allocated, the active and standby servers in the U2000 HA system use different IP addresses to communicate with the device. The IP address of the inband network management port of the UA5000(IPMB) must be in the same network segment as the IP address of the gateway. When the IP address of the inband network management port is not in the same network segment as the IP addresses of the active and standby servers, you need to configure a route to forward IP packets.
Table 1-6 provides the data plan for inband network management in a U2000 HA system. Table 1-6 Data plan for inband network management in a U2000 HA system Item IP address of the inband network management port of the UA5000(IPMB) IP address of the U2000 (floating IP addresses are allocated) IP address of the U2000 (floating IP addresses are not allocated) Data 10.10.20.2/24 Floating IP address: 10.10.21.1/24 IP address of the active server: 10.10.21.1/24 IP address of the standby server: 10.10.21.2/24 IP address: 10.10.20.254/24 public private V1
IP address of the gateway of the UA5000 (IPMB) connected to a router Read community name Write community name SNMP version
Procedure
1 Configure inband network management on the device. In the case of the U2000 single-server system, the procedure is as follows:
1 Managing Devices
1.
Configure the IP address of the inband network management port.

NOTE
If the packets transmitted to the upstream Ethernet port do not carry VLAN tags (that is, they are untagged), run the native-vlan command to set the default VLAN of the upstream port to the VLAN that the upstream port belongs to.
a. b. c. d.
Create a network management VLAN. huawei(config)#vlan 1000 standard Add an upstream port. huawei(config)#port vlan 1000 0/2 0 Enter the interface configuration mode of the network management VLAN. huawei(config)#interface vlanif 1000 Configure the IP address of the interface of the network management VLAN. huawei(config-if-vlanif1000)#ip address 10.10.20.2 255.255.255.0 huawei(config-if-vlanif1000)#quit
2. 3.
Add a route for inband network management. huawei(config)#ip route-static 10.10.21.0 24 10.10.20.254 Set the SNMP parameters. The SNMP parameters must be the same as the SNMP parameters on the U2000. l Set the community names and access rights. huawei(config)#snmp-agent community read public huawei(config)#snmp-agent community write private l (Optional) Set the administrator identifier and the way to contact the administrator. huawei(config)#snmp-agent sys-info contact HW-075528780808 l (Optional) Set the location information about the device. huawei(config)#snmp-agent sys-info location Shenzhen_China l Set the SNMP version.
NOTE
huawei(config)#snmp-agent sys-info version v1 4. 5. Enable the reporting of traps. huawei(config)#snmp-agent trap enable standard Configure the IP address of the destination host of the traps. huawei(config)#snmp-agent target-host trap-hostname huawei address 10.10.21.1 trap-paramsname ABC huawei(config)#snmp-agent target-host trap-paramsname ABC v1 securityname private 6. 7. Set the IP address of the VLANIF interface as the source IP address of the traps. huawei(config)#snmp-agent trap source vlanif 1000 Save the data. huawei(config)#save In the case of the U2000 HA system, the procedure for configuring inband network management on the device varies with the IP address allocation scheme.
1 Managing Devices
l When floating IP addresses are allocated, the procedure is the same as that in the U2000 single-server system. l When floating IP addresses are not allocated, the procedure is as follows: 1. Configure the IP address of the inband network management port.
NOTE
If the packets transmitted to the upstream Ethernet port do not carry VLAN tags (that is, they are untagged), run the native-vlan command to configure the default VLAN of the upstream port to the VLAN that the upstream port belongs to.
a. b. c. d.
2. 3.
Add a route for inband network management. huawei(config)#ip route-static 10.10.21.0 24 10.10.20.254 Set the SNMP parameters. l Set the community names and access rights. huawei(config)#snmp-agent community read public huawei(config)#snmp-agent community write private l (Optional) Set the administrator identifier and the way to contact the administrator. huawei(config)#snmp-agent sys-info contact HW-075528780808 l (Optional) Set the location information about the device. huawei(config)#snmp-agent sys-info location Shenzhen_China l Set the SNMP version.
NOTE
huawei(config)#snmp-agent sys-info version v1 4. 5. Enable the reporting of traps. huawei(config)#snmp-agent trap enable standard Configure the IP address of the destination host of the traps. huawei(config)#snmp-agent target-host trap-hostname huawei address 10.10.21.1 trap-paramsname ABC1 huawei(config)#snmp-agent target-host trap-paramsname ABC1 v1 securityname private huawei(config)#snmp-agent target-host trap-hostname huawei address 10.10.21.2 trap-paramsname ABC2
1 Managing Devices
huawei(config)#snmp-agent target-host trap-paramsname ABC2 v1 securityname private 6. 7. Set the IP address of the VLANIF interface as the source IP address of the traps. huawei(config)#snmp-agent trap source vlanif 1000 Save the data. huawei(config)#save 2 Configure inband network management on the U2000. 1. Configure the route connecting the U2000 server and the network management port.
NOTE
l Solaris OS: To add a route, run the route add 10.10.21.1 10.10.20.1 command. To query the information about the current routing table, run the netstat -r command. l Windows OS: To add a route, run the route add 10.10.21.1 mask 255.255.255.0 10.10.20.1 command To query the information about the current routing table, run the route print command. 2. Set the SNMP parameters. a. b. c. Choose Administration > NE Communicate Parameter > NE Access Protocol Parameters from the main menu. On the tab page that is displayed, click Reset. In the dialog box that is displayed, click the SNMPv1 Parameters tab and click Add. In the dialog box that is displayed, set the name and SNMP parameters as follows:
d.
1-42
Click OK.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-11-19)
1 Managing Devices
e. f. g. 3.
Select the new SNMP parameters and click OK. In the dialog box that is displayed, click Yes. The SNMP parameters are tested automatically. The Loading dialog box is displayed. After the test is complete and a message is displayed indicating that the test is successful, click OK.
Add the device to the U2000. a. b. In the Main Topology, right-click in the Physical Root navigation tree and choose New > NE from the shortcut menu. In the dialog box that is displayed, set the parameters.
c.
Click OK.
NOTE
----End
Result
1.12 Configuration Example of Inband Network Management (Based on the SNMPv3 Protocol)
This topic describers how to manage and maintain the UA5000(IPMB) in the inband network management mode on the U2000. In the inband network management mode, the service channels provided by managed devices are used to transmit management information. Therefore, compared with outband network management, inband network management provides a more flexible networking mode without extra devices and is cost-effective. Nevertheless, network maintenance is difficult.
1 Managing Devices
Example Network
Figure 1-4 shows an example network of inband network management. The U2000 manages and maintains the UA5000(IPMB) through an upstream port in the inband network management mode. Therefore, you need to add a static route to the U2000 and set the related SNMP parameters on the UA5000(IPMB). Figure 1-4 Example network of inband network management
U2000
Router UA5000
GE 0/2/0
COM ETH IPMB
Data Plan
Configuring Inband Network Management in a U2000 Single-Server System The IP address of the inband network management port of the UA5000(IPMB) must be in the same network segment as the IP address of the gateway. When the IP address of the inband network management port is not in the same network segment as the IP address of the U2000, you need to configure a route to forward IP packets. The IP address of the destination host of traps is the IP address of the U2000. The U2000 parses only the traps that are reported by means of the SNMPv1 or SNMPv3 protocol. When configuring traps on the device, you need to check the version of the SNMP protocol that the device supports and configure the trap protocol to SNMPv1 or SNMPv3 accordingly. Table 1-7 provides the data plan for inband network management in a U2000 single-server system.
1-44
Issue 03 (2010-11-19)
1 Managing Devices
Table 1-7 Data plan for inband network management in a U2000 single-server system Item IP address of the inband network management port of the UA5000(IPMB) IP address of the gateway of the UA5000 (IPMB) connected to a router Network segment of the U2000 SNMP Data 10.10.21.2/24 10.10.20.254/24 10.10.21.1/24 User name: user1 Group name: group1 View name: hardy Authentication mode: MD5 Authentication password: auth12345678 Encryption mode: DES Encryption password: pri12345678 Version: V3
Configuring Inband Network Management in a U2000 HA System l If floating IP addresses are allocated, the active and standby servers in the U2000 HA system use a floating IP address to communicate with the device. Thus, the IP address of the destination host of traps is the floating IP address. The IP address of the inband network management port of the UA5000(IPMB) must be in the same network segment as the IP address of the gateway. When the IP address of the inband network management port is not in the same network segment as the floating IP address, you need to configure a route to forward IP packets. If floating IP addresses are not allocated, the active and standby servers in the U2000 HA system use different IP addresses to communicate with the device. The IP address of the inband network management port of the UA5000(IPMB) must be in the same network segment as the IP address of the gateway. When the IP address of the inband network management port is not in the same network segment as the IP addresses of the active and standby servers, you need to configure a route to forward IP packets.
Table 1-8 provides the data plan for inband network management in a U2000 HA system. Table 1-8 Data plan for inband network management in a U2000 HA system Item IP address of the inband network management port of the UA5000(IPMB) IP address of the U2000 (floating IP addresses are allocated) Data 10.10.20.2/24 Floating IP address: 10.10.21.1/24
Issue 03 (2010-11-19)
1-45
1 Managing Devices
Item IP address of the U2000 (floating IP addresses are not allocated)
Data IP address of the active server: 10.10.21.1/24 IP address of the standby server: 10.10.21.2/24 10.10.20.254/24 User name: user1 Group name: group1 View name: hardy Authentication mode: MD5 Authentication password: auth12345678 Encryption mode: DES Encryption password: pri12345678 Version: V3
IP address of the gateway of the UA5000 (IPMB) connected to a router SNMP
Procedure
1 Configure inband network management on the device. In the case of the U2000 single-server system, the procedure is as follows: 1. Configure the IP address of the inband network management port.
NOTE
If the packets transmitted to the upstream Ethernet port do not carry VLAN tags (that is, they are untagged), run the native-vlan command to set the default VLAN of the upstream port to the VLAN that the upstream port belongs to.
a. b. c. d.
2. 3.
Add a route for inband network management. huawei(config)#ip route-static 10.10.21.0 24 10.10.20.254 Set the SNMP parameters. The SNMP parameters must be the same as the SNMP parameters on the U2000.
1-46
1 Managing Devices
l Set the SNMP user, group, and view. huawei(config)#snmp-agent usm-user v3 user1 group1 authentication-mode md5 auth12345678 privacy-mode des56 pri12345678 huawei(config)#snmp-agent group v3 group1 authentication read-view hardy write-view hardy huawei(config)#snmp-agent mib-view hardy include ip l (Optional) Set the administrator identifier and the way to contact the administrator. huawei(config)#snmp-agent sys-info contact HW-075528780808 l (Optional) Set the location information about the device. huawei(config)#snmp-agent sys-info location Shenzhen_China l (Optional) Set the engine ID of the SNMP entity.
NOTE

NOTE
huawei(config)#snmp-agent sys-info version v3 4. 5. Enable the reporting of traps. huawei(config)#snmp-agent trap enable standard Configure the IP address of the destination host of the traps. huawei(config)#snmp-agent target-host trap-hostname huawei address 10.10.21.1 trap-paramsname ABC huawei(config)#snmp-agent target-host trap-paramsname ABC v3 securityname user1 privacy 6. 7. Set the source IP address of the traps. huawei(config)#snmp-agent trap source vlanif 1000 Save the data. huawei(config)#save In the case of the U2000 HA system, the procedure for configuring inband network management on the device varies with the IP address allocation scheme. l When floating IP addresses are allocated, the procedure is the same as that in the U2000 single-server system. l When floating IP addresses are not allocated, the procedure is as follows: 1. Configure the IP address of the inband network management port.
NOTE
If the packets transmitted to the upstream Ethernet port do not carry VLAN tags (that is, they are untagged), run the native-vlan command to configure the default VLAN of the upstream port to the VLAN that the upstream port belongs to.
a.
Create a network management VLAN. huawei(config)#vlan 1000 standard
Issue 03 (2010-11-19)
1-47
1 Managing Devices
b. c. d.
Add an upstream port. huawei(config)#port vlan 1000 0/2 0 Enter the interface configuration mode of the network management VLAN. huawei(config)#interface vlanif 1000 Configure the IP address of the interface of the network management VLAN. huawei(config-if-vlanif1000)#ip address 10.10.20.2 255.255.255.0 huawei(config-if-vlanif1000)#quit
2. 3.
Add a route for inband network management. huawei(config)#ip route-static 10.10.21.0 24 10.10.20.254 Set the SNMP parameters. l Set the SNMP user, group, and view. huawei(config)#snmp-agent usm-user v3 user1 group1 authentication-mode md5 auth12345678 privacy-mode des56 pri12345678 huawei(config)#snmp-agent group v3 group1 authentication read-view hardy write-view hardy huawei(config)#snmp-agent mib-view hardy include ip l (Optional) Set the administrator identifier and the way to contact the administrator. huawei(config)#snmp-agent sys-info contact HW-075528780808 l (Optional) Set the location information about the device. huawei(config)#snmp-agent sys-info location Shenzhen_China l (Optional) Set the engine ID of the SNMP entity.
NOTE

NOTE
huawei(config)#snmp-agent sys-info version v3 4. 5. Enable the reporting of traps. huawei(config)#snmp-agent trap enable standard Configure the IP address of the destination host of the traps. huawei(config)#snmp-agent target-host trap-hostname huawei address 10.10.21.1 trap-paramsname ABC1 huawei(config)#snmp-agent target-host trap-paramsname ABC1 v3 securityname user1 privacy huawei(config)#snmp-agent target-host trap-hostname huawei address 10.10.21.2 trap-paramsname ABC2 huawei(config)#snmp-agent target-host trap-paramsname ABC2 v3 securityname user1 privacy 6. Set the IP address of the VLANIF interface as the source IP address of the traps. huawei(config)#snmp-agent trap source vlanif 1000
1 Managing Devices
7.
Save the data. huawei(config)#save
2 Configure inband network management on the U2000. 1. Configure the route connecting the U2000 server and the network management port.
NOTE
l Solaris OS: To add a route, run the route add 10.10.21.1 10.10.20.1 command. To query the information about the current routing table, run the netstat -r command. l Windows OS: To add a route, run the route add 10.10.21.1 mask 255.255.255.0 10.10.20.1 command. To query the information about the current routing table, run the route print command. 2. Set the SNMP parameters. a. b. c. Choose Administration > NE Communicate Parameter > NE Access Protocol Parameters from the main menu. On the tab page that is displayed, click Reset. In the dialog box that is displayed, click the SNMPv1 Parameters tab and click Add. In the dialog box that is displayed, set the name and SNMP parameters as follows:
NOTE
The SNMPv3 protocol supports three security levels: authentication, noauth, and privacy. The U2000 communicates with the device successfully by means of the SNMPv3 protocol only when the authentication and encryption modes of the SNMP user and SNMP group on the device and the SNMP parameters on the U2000 are the same.
d.
Issue 03 (2010-11-19)
Click OK.
1 Managing Devices
e. f. g. 3.
Select the new SNMP parameters and click OK. In the dialog box that is displayed, click Yes. The SNMP parameters are tested automatically. The Loading dialog box is displayed. After the test is complete and a message is displayed indicating that the test is successful, click OK. In the Main Topology, right-click in the Physical Root navigation tree and choose New > NE from the shortcut menu. In the dialog box that is displayed, set the parameters.
Add the device to the U2000. a. b.
c.
Click OK.
NOTE
----End
Result
1-50
Issue 03 (2010-11-19)
2 Pre-configuring Parameters for Service Provisioning
Pre-configuring Parameters for Service Provisioning
About This Chapter

According to the actual operation and maintenance scenarios, the service configuration and management of the U2000 can be classified into the parameter pre-configuration for service provisioning, network element management, and service provisioning. Parameter preconfiguration for service provisioning refers to setting the service-related global parameters, such as the system parameter profile, traffic profile, IGMP program profile, and VLAN according to the global data plan before provisioning services for the network element. 2.1 Adding a VLAN Before you provision services for network elements, you can add a VLAN or add VLANs in batches according to the global data plan. When VLANs with continuous IDs and the VLAN type is consistent with the VLAN attribute, these VLANs can be added in batches. In addition, the names of the VLANs that are added in batches are generated automatically. 2.2 Configuring the Upstream Port of a VLAN To enable the user packets with a VLAN tag to be forwarded through an upstream port, perform this operation to add the upstream port to the VLAN. After the upstream port is successfully added, the user packets with this VLAN tag can be forwarded through the corresponding port. 2.3 Configuring a VLAN L3 Interface The functions of a L3 interface that is based on the VLAN are similar to a L3 switch. Through L3 forwarding, the L3 interface forwards data between different VLANs. 2.4 Configuring the QoS Policy The quality of service (QoS) provides the user services with the end-to-end quality assurance by setting different measurement indicators, such as the service availability, throughput, delay, jitter, and loss rate. The UA5000(IPMB) provides the high QoS assurance by supporting the traffic classification, traffic statistics, and schedule policy of the traffic rules. 2.5 Configuring a Global Traffic Profile The traffic profile defines a series of traffic parameters. It can be referenced by the device and the port to monitor and control traffic streams. 2.6 Configuring the xDSL-Related Profiles Before you provision services for network elements, you can configure the xDSL-related profiles according to the global data plan. The xDSL-related profiles can improve the service quality by
limiting the port rate and noise margin, and can monitor the performance of the port by configuring the related thresholds. 2.7 Configuring an IGMP Profile The Internet Group Management Protocol (IGMP) profile contains the parameters required for configuring the multicast service. 2.8 Configuring the System Parameters The system parameter profile integrates the parameters required for configuring the NE or the service. Bound to the specified device, the profile is used for configuring the global parameters of the device. The system parameters are the static configuration parameters at the device level. For a carrier, the devices of the same type in the entire network need to have the same configurations. For this purpose, the carrier can use the system parameter profile to configure the device system parameters in a unified manner.
2-2
Issue 03 (2010-11-19)
2.1 Adding a VLAN

Before you provision services for network elements, you can add a VLAN or add VLANs in batches according to the global data plan. When VLANs with continuous IDs and the VLAN type is consistent with the VLAN attribute, these VLANs can be added in batches. In addition, the names of the VLANs that are added in batches are generated automatically.
Context
Virtual local area network (VLAN) is a technology used to form virtual workgroups by grouping the devices of a LAN logically. The UA5000(IPMB) supports a maximum of 4000 VLANs, and supports the standard VLAN, MUX VLAN, smart VLAN, and super VLAN. Table 2-1 describes VLAN types and their applications. Table 2-1 VLAN types and their applications VLAN Type Standard VLAN Description Ethernet ports in a standard VLAN are interconnected with each other. Ethernet ports in different standard VLANs are isolated from each other. A smart VLAN contains multiple service virtual ports. In addition, traffic streams on these ports are isolated from each other and traffic streams on different VLANs are isolated from each other. A smart VLAN provides access for multiple users, saving the VLAN resources. A MUX VLAN contains only one service virtual port. In addition, traffic streams on different VLANs are isolated from each other. One-to-one mapping can be set up between a MUX VLAN and an access user. In this case, a MUX VLAN can uniquely identify an access user. The super VLAN is a L3-based VLAN. It consists of multiple sub VLANs. Through ARP proxy, a super VLAN realizes L3 interconnection for these sub VLANs. A sub VLAN can be a standard VLAN, smart VLAN, or a MUX VLAN. Application Only available for Ethernet ports. Applied to network management and subtending. Applied to the access service, such as the residential community access.
Smart VLAN
MUX VLAN
Applied to the access service, such as scenarios where users are distinguished based on VLANs.
Super VLAN
Applied to save IP address resources so that the utilization of the IP address is improved.
The VLAN supports the common, QinQ, and stacking attributes. Table 2-2 describes the VLAN attributes.
Table 2-2 VLAN attributes VLAN Attribute Common QinQ Application A VLAN with the common attribute can be used as a L2 VLAN or to create a L3 interface. A QinQ VLAN packet contains two layers of VLAN tags: inner VLAN tag from the private network and outer VLAN tag from the UA5000 (IPMB). Through the outer VLAN, a L2 VPN tunnel can be set up to transparently transmit the service between private networks. A stacking VLAN packet contains two layers of VLAN tags: inner VLAN tag and outer VLAN tag from the UA5000(IPMB). With this attribute, the upper layer BRAS device authenticates users based on the two VLAN tags, thus increasing the number of access users. In an upper network in the L2 working mode, you can forward packets according to the "VLAN + MAC", thus providing the wholesale service provisioning function for ISPs.
Stacking
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose VLAN from the navigation tree. 3 On the VLAN tab page, set the filter criteria or click 4 Right-click the list, and then choose Add or Batch Add. 5 In the dialog box that is displayed, set the parameters. l When you add a VLAN, and then set the parameters as follows: VLAN ID Name Alias Type to display the VLANs.
2-4
Issue 03 (2010-11-19)
l When you add VLANs in batches, and then set the parameters as follows: Start ID End ID Type
6 Click Done. ----End
2.2 Configuring the Upstream Port of a VLAN

To enable the user packets with a VLAN tag to be forwarded through an upstream port, perform this operation to add the upstream port to the VLAN. After the upstream port is successfully added, the user packets with this VLAN tag can be forwarded through the corresponding port.
Issue 03 (2010-11-19)
2-5
Prerequisite
The corresponding VLAN must exist. For details about adding a VLAN, see 2.1 Adding a VLAN.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose VLAN from the navigation tree. 3 On the VLAN tab page, set the filter criteria or click to display the VLANs.
4 Select the VLAN to be configured, right-click, and then choose Configure. 5 In the dialog box that is displayed, click Configure VLAN, click the Sub Port tab, and then set the upstream port of the VLAN. 6 Click Done. ----End
2.3 Configuring a VLAN L3 Interface

The functions of a L3 interface that is based on the VLAN are similar to a L3 switch. Through L3 forwarding, the L3 interface forwards data between different VLANs.
Context
You can configure the L3 interfaces of only common VLANs.
Procedure
4 Select a VLAN record, right-click, and then choose Configure. 5 In the dialog box that is displayed, click the L3 Interface tab, select Configure L3 Interface, and then set the IP address and the subnet mask of the L3 interface as follows.
2-6
Issue 03 (2010-11-19)
2.4 Configuring the QoS Policy

The quality of service (QoS) provides the user services with the end-to-end quality assurance by setting different measurement indicators, such as the service availability, throughput, delay, jitter, and loss rate. The UA5000(IPMB) provides the high QoS assurance by supporting the traffic classification, traffic statistics, and schedule policy of the traffic rules.
Context
l The access control list (ACL) is used to filter the specific data packets by setting the filter criteria. In this way, the required objects can be displayed. After the required objects are displayed, network devices can permit or refuse the matching data packets to pass with the matching rules. The QoS processes the packets filtered by the ACL according to the user requirement, which is the vital function of the ACL. In the UA5000(IPMB), the ACL can be classified into the standard ACL, extended ACL, L2 ACL, and customized ACL. Table 2-3 lists the ACL classification.
l l
Issue 03 (2010-11-19)
2-7
Table 2-3 ACL classification Item Standard ACL Extended ACL Range 2000-2999 Feature Defines ACL rules according to only the L3 source IP address, and analyzes and processes the data packets. Defines ACL rules according to the source IP address and destination IP address of the data packets, protocol type carried by the IP network, features of the protocol (such as the source port and destination port of the TCP, ICMP type, and code). With the extended ACL, rules more exact, rich, and flexible can be defined. Defines ACL rules according to the information about the link layer, such as the source MAC address, source VLAN ID, L2 protocol type, and destination MAC address, and analyzes and processes the data. Performs matching according to the 32 bytes of the former 80 bytes of the L2 data frames at random, and processes the data packets.
3000-3999
L2 ACL
4000-4999
Customized ACL
5000-5999
Procedure
1 Add the time range. 1. In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. Choose QoS > QoS&ACL from the navigation tree. Click the Time Segment Management tab, right-click the list, and then choose Add. In the dialog box that is displayed, set the name of the time range. Click OK. Select the added time record, click the One-off Time tab or the Periodic Time tab in the lower pane. In the information list, right-click and choose Add from the shortcut menu. In the dialog box that is displayed, set the parameters. l In the Add One-off Time dialog box, set Start Time and End Time of the time range. l In the Add Periodic Time dialog box, set the period, Start Time, and End Time of the time range. 8. Click OK.
2. 3. 4. 5. 6. 7.
2 Add an ACL group. The following uses the standard ACL group as an example. 1. 2. Click the ACL Management tab, set the filter criteria to display the records, right-click the list, and then choose Add. In the dialog box that is displayed, set Type, Step and ACL group index of the ACL group, as follows.
2-8
3. 4. 5.
Click OK. Select the added ACL, and then click the Standard Sub Item tab in the lower pane. In the information list, right-click and choose Add from the shortcut menu. In the dialog box that is displayed, set the Sub Item Index, Action, Source IP Address, Source IP Address Wildcard, Matching Fragmented Packets, and Time Segment Name parameters.
6.
Click OK.
3 Add the QoS rule. The following uses adding rules in batches as an example. 1. 2. Click the QoS Management tab, set the filter criteria to display the records, right-click the list, and then choose Batch Add > Packet Filtering. In the dialog box that is displayed, set the parameters. There are three steps for adding packets filtering, that is, select the port, select the ACL rule, and fill in the packets filtering parameter. The specific operations are as follows: l Select the port to be bound, and then click Next. l Select the referenced ACL rule, and then click Next. l Select the packets filtering parameter, that is, the direction for packets filtering.
Issue 03 (2010-11-19)
2-9
3.
Click Finish.
----End
2.5 Configuring a Global Traffic Profile

The traffic profile defines a series of traffic parameters. It can be referenced by the device and the port to monitor and control traffic streams.
Context
The traffic profile includes the ATM traffic profile and IP traffic profile. The ATM traffic profile provides the traffic control function for different ATM services so that the QoS assurance is provided. The IP traffic profile is referenced when the service virtual port is configured to manage the traffic of the service virtual port. 2.5.1 Configuring an ATM Traffic Profile The ATM traffic profile defines the ATM service type, the ATM traffic type, and their corresponding parameter values. It is used to control the traffic of the PVC. The device provides an appropriate QoS based on the traffic parameters. 2.5.2 Configuring an IP Traffic Profile The IP traffic profile defines a series of traffic parameters. It can be referenced by the device and the port to monitor and control traffic streams. After an IP traffic profile is created, you can directly reference it when creating a traffic stream and configuring the port rate limitation.
2.5.1 Configuring an ATM Traffic Profile

The ATM traffic profile defines the ATM service type, the ATM traffic type, and their corresponding parameter values. It is used to control the traffic of the PVC. The device provides an appropriate QoS based on the traffic parameters.
Context
The global ATM traffic profile added through the U2000 exists only in the database of the U2000, but is not added to the device. The device can provide a proper QoS based on the traffic parameters only when the global ATM traffic profile is added to the device.
Procedure
1 Choose Configuration > Access Profile Management > Traffic Profile from the main menu. 2 Click the ATM Traffic Profile tab, and select UA5000(IPMB) from the Device Type dropdown list. 3 Right-click and choose Add Global Profile from the shortcut menu. 4 In the dialog box that is displayed, set Name, Service Category, and Describe Type for the traffic profile. 5 Click Next. In the dialog box that is displayed, set the parameters.
NOTE
The parameter values are determined by the service level and traffic description.
6 Click Finish. ----End
2.5.2 Configuring an IP Traffic Profile

The IP traffic profile defines a series of traffic parameters. It can be referenced by the device and the port to monitor and control traffic streams. After an IP traffic profile is created, you can directly reference it when creating a traffic stream and configuring the port rate limitation.
Context
When an IP traffic profile is added through the U2000, the IP traffic profile is added to only the database of the U2000, but is not applied to the device. This IP traffic profile is created on a device only when the device references the IP traffic profile to create a service port or the IP traffic profile is manually applied to the device.
Procedure
1 Choose Configuration > Access Profile Management > Traffic Profile from the main menu. 2 Click the IP Traffic Profile tab, and select UA5000(IPMB) from the Device Type drop-down list. 3 Right-click and choose Add Global Profile from the shortcut menu. 4 In the dialog box that is displayed, set the parameters.
Issue 03 (2010-11-19)
2-11
5 Click OK. ----End
2.6 Configuring the xDSL-Related Profiles

Before you provision services for network elements, you can configure the xDSL-related profiles according to the global data plan. The xDSL-related profiles can improve the service quality by limiting the port rate and noise margin, and can monitor the performance of the port by configuring the related thresholds.
Context
l The asymmetric digital subscriber line (ADSL) adopts the asymmetric transmission mode. It provides asymmetric upstream and downstream rates over an existing POTS line. ADSL profiles include ADSL line profiles, ADSL alarm profiles, and ADSL extended profiles. The ADSL line profile is used to limit the port rate and noise margin to improve the service quality. The ADSL alarm profile is used to monitor the performance of the ADSL port. The ADSL extended profile is used to improve the reliability of the line, that is, the profile disables certain sub-channels that are affected by much interference. The very high speed digital subscriber line (VDSL2) is a transmission technology that is used to provide high-speed leased line access over the twisted pairs in the asymmetrical or symmetrical mode. VDSL2 is an extension of VDSL. The VDSL2 profiles include the VDSL2 line configuration profile and VDSL2 alarm configuration profile. The VDSL2 line profile limits the port rate and noise margin to improve the service quality by referencing the VDSL2 line configuration profile and VDSL2 channel configuration profile. The VDSL2 alarm profile monitors the performance of the VDSL2 port by referencing the VDSL2 line alarm configuration profile and VDSL2 channel alarm configuration profile. The G.SHDSL line profile provides parameters that are required for activating the ATM G.SHDSL port. After the G.SHDSL line profile is configured successfully, when you configure the attributes of the ATM G.SHDSL port, you can directly reference the G.SHDSL line profile to limit the port rate and noise margin to improve the service quality. The G.SHDSL alarm profile defines a series of alarm parameters for measuring the G.SHDSL port performance. You can monitor the performance of the G.SHDSL line by setting thresholds for these alarm parameters.
2.6.1 Configuring an ADSL Line Profile An ADSL line profile provides parameters that are required for activating an ADSL port. After the ADSL line profile is configured successfully, when you configure the attributes of the ADSL port, you can directly reference the ADSL line profile to limit the port rate and noise margin to improve the service quality. 2.6.2 Configuring an ADSL Alarm Profile When the ADSL port is activated, it directly references the ADSL alarm profile to monitor the performance of the port. When the actual parameter value of the port exceeds the threshold, the system generates an alarm. 2.6.3 Configuring a VDSL2 Line Profile The VDSL2 line profile binds the specified VDSL2 line configuration profile to the VDSL2 channel configuration profile. After a VDSL2 line profile is bound to a VDSL2 port, when the VDSL2 port is activated, it directly references the VDSL2 line profile to limit the port rate and noise margin to improve the service quality.
2.6.4 Configuring a VDSL2 Alarm Profile A VDSL2 alarm profile binds a specified line alarm configuration profile and a channel alarm configuration profile. After the binding is successful, when a VDSL2 port is activated, it directly references an alarm profile to monitor the performance of the VDSL2 port. When the parameter value of the port exceeds the threshold, the system generates an alarm. 2.6.5 Configuring a G.SHDSL Line Profile A G.SHDSL line profile provides parameters that are required for activating an ATM G.SHDSL port. After the G.SHDSL line profile is configured successfully, when you configure the attributes of the ATM G.SHDSL port, you can directly reference the G.SHDSL line profile to limit the port rate and noise margin to improve the service quality. 2.6.6 Configuring a G.SHDSL Alarm Profile A G.SHDSL alarm profile defines a series of alarm parameters for measuring the performance of a G.SHDSL port. You can monitor the performance of the G.SHDSL circuit by setting thresholds for these alarm parameters. When the ATM G.SHDSL port is activated, it directly references the G.SHDSL alarm profile to monitor the performance of the port. When the parameter value of the port exceeds the preset threshold, the system generates an alarm.
2.6.1 Configuring an ADSL Line Profile

An ADSL line profile provides parameters that are required for activating an ADSL port. After the ADSL line profile is configured successfully, when you configure the attributes of the ADSL port, you can directly reference the ADSL line profile to limit the port rate and noise margin to improve the service quality.
Context
l l A profile name uniquely identifies a profile. Therefore, the profile name must be specified and it must be unique. Otherwise, the profile cannot be added. You can add profiles that have the same parameters but different names.
Procedure
1 Choose Configuration > Access Profile Management > ADSL Profile from the main menu. 2 Click the ADSL Line Profile tab, and select UA5000(IPMB) from the Device Type drop-down list. 3 Right-click and choose Add Global Profile from the shortcut menu. 4 In the dialog box that is displayed, set the parameters.
Issue 03 (2010-11-19)
2-13
5 Click Next. 6 In the dialog box that is displayed, set the parameters.
2-14
Issue 03 (2010-11-19)
2.6.2 Configuring an ADSL Alarm Profile

When the ADSL port is activated, it directly references the ADSL alarm profile to monitor the performance of the port. When the actual parameter value of the port exceeds the threshold, the system generates an alarm.
Context
Procedure
1 Choose Configuration > Access Profile Management > ADSL Profile from the main menu. 2 Click the ADSL Alarm Profile tab, and select UA5000(IPMB) from the Device Type dropdown list. 3 Right-click and choose Add Global Profile from the shortcut menu. 4 In the dialog box that is displayed, set the parameters.
5 Click OK. ----End
2.6.3 Configuring a VDSL2 Line Profile

The VDSL2 line profile binds the specified VDSL2 line configuration profile to the VDSL2 channel configuration profile. After a VDSL2 line profile is bound to a VDSL2 port, when the VDSL2 port is activated, it directly references the VDSL2 line profile to limit the port rate and noise margin to improve the service quality.
Procedure
l Configure a VDSL2 line spectrum configuration profile. One VDSL2 line can be configured with multiple transmission modes. You can set some frequency parameters mapping a transmission mode in the line spectrum configuration profile. When the line is activated, the central office and the CPE negotiate to determine the transmission mode, and then the line spectrum configuration profile mapping the transmission mode is used. As an NMS type profile, the VDSL2 line spectrum configuration profile, after being created, can be referenced by different line configuration profiles. 1. 2. 3. 4. Choose Configuration > Access Profile Management > VDSL2 Profile from the main menu. Click the Line Spectrum Configuration Profile tab, and select UA5000(IPMB) from the Device Type drop-down list. Right-click and choose Add Global Profile from the shortcut menu. In the dialog box that is displayed, set the parameters related to the line spectrum.
2-16
Issue 03 (2010-11-19)
NOTE
Click next to PSD Mask Value Downstream Parameter and PSD Mask Value Upstream Parameter, and then add a VDSL2 PSD profile in the dialog box that is displayed.
5. l
Click OK.
Configure a VDSL2 line configuration profile. The VDSL2 line configuration profile is bound to the VDSL2 channel configuration profile to form the VDSL2 line profile. The line profile is directly referenced when the VDSL2 port is activated. When the VDSL2 port is activated, the central office and the CPE negotiate based on the specified line configuration profile to determine whether the line can work in the normal state. When you set the SNR margin of the upstream and downstream channels, make sure that: minimum SNR margin target SNR margin maximum SNR margin. 1. 2. 3. Click the Line Configuration Profile tab, and select UA5000(IPMB) from the Device Type drop-down list. Right-click and choose Add Global Profile from the shortcut menu. In the dialog box that is displayed, set the parameters of the line configuration profile. The configuration procedure is as follows: (1) In the dialog box, set the basic parameters of the line configuration profile. (2) Click Next, and then set the downstream power backoff parameters in the dialog box. (3) Click Next, and then set the upstream power backoff parameters in the dialog box.
Issue 03 (2010-11-19)
2-17
(4) Click Next, and then set the advanced parameters in the dialog box. (5) Click Next, and then set the transmission mode in the dialog box. (6) Click Next, and then set the line spectrum configuration profile that is bound to the line configuration profile in the dialog box. 4. l Click Finish. Configure a VDSL2 channel configuration profile. A VDSL2 channel configuration profile is a collection of most parameters for a VDSL2 channel, and the profile is referenced by a VDSL2 line profile. When the VDSL2 port is activated, the central office and the CPE negotiate based on the specified channel configuration profile to determine whether the line can work in the normal state. 1. 2. 3. Click the Channel Configuration Profile tab, and select UA5000(IPMB) from the Device Type drop-down list. Right-click and choose Add Global Profile from the shortcut menu. In the dialog box that is displayed, set the parameters related to the channel.
4. l 1. 2. 3.
Click OK. Click the Line Template tab, and select UA5000(IPMB) from the Device Type dropdown list. Right-click and choose Add Global Profile from the shortcut menu. In the dialog box that is displayed, set Line Profile, Channel Configuration Profile and related parameters that are referenced by the line configuration profile as follows.
Configure a VDSL2 line template.
2-18
Issue 03 (2010-11-19)
4. ----End
Click OK.
2.6.4 Configuring a VDSL2 Alarm Profile

A VDSL2 alarm profile binds a specified line alarm configuration profile and a channel alarm configuration profile. After the binding is successful, when a VDSL2 port is activated, it directly references an alarm profile to monitor the performance of the VDSL2 port. When the parameter value of the port exceeds the threshold, the system generates an alarm.
Procedure
l VDSL2 line alarm configuration profile A VDSL2 line alarm configuration profile defines a series of alarm thresholds that are used to monitor the performance of an activated VDSL2 line. When a certain measurement entry reaches the alarm threshold, the device is notified and an alarm is reported to the log host and the U2000. After being configured successfully, a VDSL2 line alarm configuration profile is bound to a VDSL2 channel alarm configuration profile to form a VDSL2 alarm profile, which can be bound to a VDSL2 port to take effect. 1. 2. 3. 4. 5. Choose Configuration > Access Profile Management > VDSL2 Profile from the main menu. Click the VDSL2 Alarm Profile tab. Click the Line Alarm Configuration Profile tab. Right-click and choose Add Global Profile from the shortcut menu. In the dialog box that is displayed, set the alarm thresholds related to the line.
Issue 03 (2010-11-19)
2-19
6. l
Click OK.
VDSL2 channel alarm configuration profile A VDSL2 channel alarm configuration profile defines a series of alarm thresholds that are used to monitor the performance of an activated VDSL2 channel. When a certain measurement entry reaches the alarm threshold, the device is notified and an alarm is reported to the log host and the U2000. After being configured successfully, a VDSL2 channel alarm configuration profile is bound to a VDSL2 line alarm configuration profile to form a VDSL2 alarm profile, which can be bound to a VDSL2 port to take effect. A VDSL2 channel alarm configuration profile defines a 15-minute threshold. When the measurement entry within 15 minutes reaches the threshold that is defined in the profile, an alarm is generated. If the threshold is set to 0, it means that no measurement is performed and no alarm is generated. 1. 2. 3. Click the Channel Alarm Configuration Profile tab. Right-click and choose Add Global Profile from the shortcut menu. In the dialog box that is displayed, set the alarm thresholds related to the channel.
2-20
Issue 03 (2010-11-19)
4. l 1. 2. 3.
Click OK. Click the Alarm Template tab. Right-click and choose Add Global Profile from the shortcut menu. In the dialog box that is displayed, set Line Alarm Configuration Profile and Channel Alarm Configuration Profile that are referenced by the alarm profile.
Configure a VDSL2 alarm profile.
4. ----End
Click OK.
2.6.5 Configuring a G.SHDSL Line Profile

A G.SHDSL line profile provides parameters that are required for activating an ATM G.SHDSL port. After the G.SHDSL line profile is configured successfully, when you configure the attributes of the ATM G.SHDSL port, you can directly reference the G.SHDSL line profile to limit the port rate and noise margin to improve the service quality.
Context
Issue 03 (2010-11-19)
2-21
Procedure
1 Choose Configuration > Access Profile Management > G.SHDSL Profile from the main menu. 2 Click the G.SHDSL Line Profile tab, and select UA5000(IPMB) from the Device Type dropdown list. 3 Right-click and choose Add Global Profile from the shortcut menu. 4 In the dialog box that is displayed, set the parameters.
5 Click Next. 6 In the dialog box that is displayed, set the parameters of the line profile.
2-22
Issue 03 (2010-11-19)
2.6.6 Configuring a G.SHDSL Alarm Profile

A G.SHDSL alarm profile defines a series of alarm parameters for measuring the performance of a G.SHDSL port. You can monitor the performance of the G.SHDSL circuit by setting thresholds for these alarm parameters. When the ATM G.SHDSL port is activated, it directly references the G.SHDSL alarm profile to monitor the performance of the port. When the parameter value of the port exceeds the preset threshold, the system generates an alarm.
Context
Issue 03 (2010-11-19)
2-23
Procedure
1 Choose Configuration > Access Profile Management > G.SHDSL Profile from the main menu. 2 Click the G.SHDSL Alarm Profile tab, and select UA5000(IPMB) from the Device Type dropdown list. 3 Right-click and choose Add Global Profile from the shortcut menu. 4 In the dialog box that is displayed, set the parameters.
5 Click OK. ----End
2.7 Configuring an IGMP Profile

The Internet Group Management Protocol (IGMP) profile contains the parameters required for configuring the multicast service.
Context
The IGMP profiles of the UA5000(IPMB) consist of the program profile, the rights profile . l The program profile is used for adding static multicast programs to a multicast VLAN. Before watching a multicast program, you need to add the program to the multicast program library. The rights profile is used for managing the permission to a series of programs.
l
2-24
NOTE
l You can add the confirmed profiles only to the confirmed profile list. l Profiles with different names but the same parameters can be added.
2.7.1 Configuring a Program Profile The program profile is used for adding static multicast programs to a multicast VLAN. Before watching a multicast program, you need to add the program to the multicast program library. If a program profile is referenced by a multicast VLAN, the multicast VLAN is automatically configured with the parameter values of the attributes contained in the program profile. 2.7.2 Configuring a Rights Profile The rights profile is used for managing the permission to a series of programs. Program rights are classified into three types: watch, preview, and forbid. In a rights profile, set the permission to different programs, and then bind the rights profile to the users that require authentication. In this way, the permission of the users to the programs is limited. The users that do not require authentication can watch all the programs on the device.
2.7.1 Configuring a Program Profile

The program profile is used for adding static multicast programs to a multicast VLAN. Before watching a multicast program, you need to add the program to the multicast program library. If a program profile is referenced by a multicast VLAN, the multicast VLAN is automatically configured with the parameter values of the attributes contained in the program profile.
Procedure
1 Choose Configuration > Access Profile Management > IGMP Profile from the main menu. 2 Click the Program Profile tab, and select UA5000(IPMB) from the Device Type drop-down list. 3 Right-click and choose Add Global Profile from the shortcut menu. 4 In the dialog box that is displayed, set the parameters.
Issue 03 (2010-11-19)
2-25
5 Click OK. ----End
2.7.2 Configuring a Rights Profile

The rights profile is used for managing the permission to a series of programs. Program rights are classified into three types: watch, preview, and forbid. In a rights profile, set the permission to different programs, and then bind the rights profile to the users that require authentication. In this way, the permission of the users to the programs is limited. The users that do not require authentication can watch all the programs on the device.
Procedure
1 Choose Configuration > Access Profile Management > IGMP Profile from the main menu. 2 Click the Right Profile tab, and select UA5000(IPMB) from the Device Type drop-down list. 3 Right-click and choose Add Global Profile from the shortcut menu. 4 In the dialog box that is displayed, enter the name of the rights profile. In the Selected Program Profile list, right-click, and choose Select Profile. In the dialog box that is displayed, select the program profile required for configuring the rights profile. Click OK.
NOTE
In the Selected Program Profile list, select a program profile, and then set the Right parameter.
5 Click OK. ----End
2.8 Configuring the System Parameters

The system parameter profile integrates the parameters required for configuring the NE or the service. Bound to the specified device, the profile is used for configuring the global parameters of the device. The system parameters are the static configuration parameters at the device level. For a carrier, the devices of the same type in the entire network need to have the same configurations. For this purpose, the carrier can use the system parameter profile to configure the device system parameters in a unified manner.
Issue 03 (2010-11-19)
2-27
Context
The main advantages of the system parameter profile are: l l l It is configured based on the network, managed in centralized manner, and supports configuration in batches. It can be configured regularly through task scheduling mode. The configuration results can be queried. It is top-down and is actively managed. The NEs that have the same configurations can share data.
2.8.1 Configuring the DHCP Relay Mode The DHCP Relay serves as a bridge between a DHCP client and a server that are located on different subnets. With this function, the DHCP packets can be relayed to the destination DHCP server (or client) across different subnets. As a result, the DHCP clients on different subnets can share the same DHCP server. In this way, it saves cost and realizes uniform management. 2.8.2 Configuring the RSTP Global Parameters The Rapid Spanning Tree Protocol (RSTP) is improved based on the STP protocol. Therefore, it supports all the functions of the STP protocol, shortens the delay required for spanning network topology, and ensures the network connectivity. 2.8.3 Enabling the PPPoA Conversion to PPPoE Function After the PPPoA conversion to PPPoE function is enabled, and the service is configured correctly, the service in ATM mode is transmitted upstream to the IP network through the uplink port. 2.8.4 Configuring the IPoA Parameters IP over ATM (IPoA) is a technology by which the payloads of the ATM packets are converted into the Ethernet frames which are transmitted to the upstream, and the IPoE packets are converted into the IPoA packets which are forwarded to the user. IPoA is used for the private line access. It meets the carriers' requirements for the transition from the ATM network to the IP network. 2.8.5 Configuring the Multicast Parameters Before you provision services for multicast, you can configure the multicast parameters according to the global data plan. The parameters consist of the Internet Group Management Protocol parameters and NTV mode. 2.8.6 Setting BFD Parameters The device can handle the BFD protocols and you can configure the BFD functions only after the global BFD function is enabled. 2.8.7 Adding the System Parameter Profile to a Device The system parameter profile is used to apply the system parameters that are pre-configured in the U2000 to the device. After this operation is performed successfully, the system parameters that are pre-configured in the U2000 take effect on the device immediately.
2.8.1 Configuring the DHCP Relay Mode

The DHCP Relay serves as a bridge between a DHCP client and a server that are located on different subnets. With this function, the DHCP packets can be relayed to the destination DHCP server (or client) across different subnets. As a result, the DHCP clients on different subnets can share the same DHCP server. In this way, it saves cost and realizes uniform management.
2-28
Issue 03 (2010-11-19)
Procedure
1 Choose Configuration > Access Profile Management > System Parameter Profile from the main menu. 2 On the System Parameter Profile tab page, select UA5000(IPMB) from the Device Type dropdown list. 3 Right-click and choose Add Global Profile from the shortcut menu. 4 In the dialog box that is displayed, enter the name of the system parameter profile. Choose all to add the parameters from the Parameters for Selection navigation tree, click parameters to the Selected Parameters navigation tree, and then click Next. 5 Select Protocol > DHCP Relay forward mode on the System Parameter Settings navigation tree. 6 In the right pane, select DHCP Relay forward mode and DHCP server selection mode. 7 Click Finish. ----End
2.8.2 Configuring the RSTP Global Parameters

The Rapid Spanning Tree Protocol (RSTP) is improved based on the STP protocol. Therefore, it supports all the functions of the STP protocol, shortens the delay required for spanning network topology, and ensures the network connectivity.
Procedure
1 Choose Configuration > Access Profile Management > System Parameter Profile from the main menu. 2 On the System Parameter Profile tab page, select UA5000(IPMB) from the Device Type dropdown list. 3 Right-click and choose Add Global Profile from the shortcut menu. 4 In the dialog box that is displayed, enter the name of the system parameter profile. Choose all to add the parameters from the Parameters for Selection navigation tree, click parameters to the Selected Parameters navigation tree, and then click Next. 5 Select Protocol > RSTP on the System Parameter Settings navigation tree. 6 In the right pane, set RSTP device switch to Open, and then set other related parameters according to the plan. 7 Click Finish. ----End
2.8.3 Enabling the PPPoA Conversion to PPPoE Function

After the PPPoA conversion to PPPoE function is enabled, and the service is configured correctly, the service in ATM mode is transmitted upstream to the IP network through the uplink port.
Procedure
1 Choose Configuration > Access Profile Management > System Parameter Profile from the main menu. 2 On the System Parameter Profile tab page, select UA5000(IPMB) from the Device Type dropdown list. 3 Right-click and choose Add Global Profile from the shortcut menu. 4 In the dialog box that is displayed, enter the name of the system parameter profile. Choose all parameters from the Parameters for Selection navigation tree, click to add the parameters to the Selected Parameters navigation tree, and then click Next. 5 Select Encapsulation Management > PPPoA on the System Parameter Settings navigation tree. 6 In the right pane, set PPPoA to PPPoE switch to Open, and then set other related parameters according to the plan. 7 Click Finish. ----End
2.8.4 Configuring the IPoA Parameters

IP over ATM (IPoA) is a technology by which the payloads of the ATM packets are converted into the Ethernet frames which are transmitted to the upstream, and the IPoE packets are converted into the IPoA packets which are forwarded to the user. IPoA is used for the private line access. It meets the carriers' requirements for the transition from the ATM network to the IP network.
Procedure
1 Choose Configuration > Access Profile Management > System Parameter Profile from the main menu. 2 On the System Parameter Profile tab page, select UA5000(IPMB) from the Device Type dropdown list. 3 Right-click and choose Add Global Profile from the shortcut menu. 4 In the dialog box that is displayed, enter the name of the system parameter profile. Choose all to add the parameters from the Parameters for Selection navigation tree, click parameters to the Selected Parameters navigation tree, and then click Next. 5 Select Encapsulation Management > IPoA on the System Parameter Settings navigation tree. 6 In the right pane, set IPoA Enable state to Open, and then set other related parameters according to the plan. 7 Click Finish. ----End
2.8.5 Configuring the Multicast Parameters

Before you provision services for multicast, you can configure the multicast parameters according to the global data plan. The parameters consist of the Internet Group Management Protocol parameters and NTV mode.
Procedure
l Configure the IGMP parameters. The Internet Group Management Protocol (IGMP) defines the mechanism used to set up and maintain the relationship of multicast group members between the host and the router. By setting the IGMP parameters, you can effectively control the IGMP parameters of the multicast packets, including the related parameters defined by the IGMP. 1. 2. 3. 4. Choose Configuration > Access Profile Management > System Parameter Profile from the main menu. On the System Parameter Profile tab page, select UA5000(IPMB) from the Device Type drop-down list. Right-click and choose Add Global Profile from the shortcut menu. In the dialog box that is displayed, enter the name of the system parameter profile. Choose all parameters from the Parameters for Selection navigation tree, click to add the parameters to the Selected Parameters navigation tree, and then click Next. 5. 6. 7. l Select Protocol > IGMP on the System Parameter Settings navigation tree. In the right pane, set the related parameters according to the plan. Click Finish.
Configure the NTV parameters. Configure the multicast video service mode. 1. 2. Choose Configuration > Access Profile Management > System Parameter Profile from the main menu. On the System Parameter Profile tab page, select UA5000(IPMB) from the Device Type drop-down list. Right-click and choose Add Global Profile from the shortcut menu. In the dialog box that is displayed, enter the name of the system parameter profile. Choose all parameters from the Parameters for Selection navigation tree, click to add the parameters to the Selected Parameters navigation tree, and then click Next. 4. 5. 6. Select NTV on the System Parameter Settings navigation tree. In the right pane, set the related parameters according to the plan. Click Finish.
3.
----End
2.8.6 Setting BFD Parameters

The device can handle the BFD protocols and you can configure the BFD functions only after the global BFD function is enabled.
Procedure
1 Choose Configuration > Access Profile Management > System Parameter Profile from the main menu. 2 On the System Parameter Profile tab page, select UA5000(IPMB) from the Device Type dropdown list. 3 Right-click and choose Add Global Profile from the shortcut menu. 4 In the dialog box that is displayed, enter the name of the system parameter profile. Choose all to add the parameters from the Parameters for Selection navigation tree, click parameters to the Selected Parameters navigation tree, and then click Next. 5 In the dialog box that is displayed, set the name of the system parameter profile and choose Protocol > BFD from the System Parameter Settings navigation tree. 6 In the right pane, set Global BFD enabling to Open. 7 Click Finish. ----End
2.8.7 Adding the System Parameter Profile to a Device

The system parameter profile is used to apply the system parameters that are pre-configured in the U2000 to the device. After this operation is performed successfully, the system parameters that are pre-configured in the U2000 take effect on the device immediately.
Procedure
1 Choose Configuration > Access Profile Management > System Parameter Profile from the main menu. 2 On the System Parameter Profile interface, select UA5000(IPMB) from the Device Type drop-down list. Then, query the required record of the system parameter profile, right-click, and then choose Download to NE. 3 In the dialog box that is displayed, select a device to which the profile is to be applied, and then click OK. ----End
2-32
Issue 03 (2010-11-19)
3 Setting the System Clock
3
About This Chapter
1.
Setting the System Clock
This topic describes how to specify the clock signals of a port as the system clock source so that the entire system uses a same clock reference. The clock source may be an external BITS clock or a line clock of the upper-level node. The clock module automatically checks the types (BITS, TDM, or SDH) of the specified clock sources, and then locks the clock source with the highest priority as the system clock source. 3.2 Adding a Clock Source This topic describes how to specify the clock signals of a specified port as the system clock source. UA5000(IPMB) supports a maximum of 10 clock sources. 3.3 Setting the Time Zone and the Daylight Saving Time This topic describes how to set the time zone of the device location as the time zone of the system, and how to set the start time, the end time, and the offset of the daylight saving time (DST).
2.
Issue 03 (2010-11-19)
3-1
3.1 Introduction to the Clock System

When configuring the system clock, restrict the clock frequency and the phase of each node in a network within the predefined tolerance scope. This prevents transmission performance degradation caused by poor timings at both Tx and Rx ends.
Context
In the digital network that is composed of the UA5000(IPMB) and other devices, clock synchronization is a fundamental requirement. Clock synchronization aims to restrict the clock frequency and the phase of each node in a network within the predefined tolerance scope. This prevents transmission performance degradation caused by poor timings at both Tx and Rx ends. The methods for clock synchronization on the digital network are as follows: pseudo synchronization and master/slave synchronization. l Pseudo synchronization: The digital switch offices of a digital switch network have clocks that are independent of one another. These clocks, usually cesium atomic clocks, have high accuracy and stability. Although these clocks are not synchronous (in frequency and phase), the time difference between them is small, that is, they are almost synchronous. Therefore, these clocks are in pseudo synchronization. Pseudo synchronization is mainly used in international digital networks, that is, between the digital networks of different countries. Master/slave synchronization: The digital switch network has a master clock configured with a clock of high accuracy. The digital switch offices of the digital switch network are under the control of the master clock. That is, these offices trace the master clock, and use the clock as the clock source. A lower layer office, including the end terminal office, uses the clock of its upper layer office as the clock source.
Generally, the UA5000(IPMB) uses master/slave clock synchronization. Clock synchronization is implemented in the following way: 1. The UA5000(IPMB) obtains the clock signals of the upper layer device from the line as the system clock sources, and uses the system clock source with the highest priority as the system clock. The UA5000(IPMB) sends the system clock signals to the service cards through the backplane. The service cards send the clock signals further to the lower layer network elements (NEs).
2. 3.
3.2 Adding a Clock Source

This topic describes how to specify the clock signals of a specified port as the system clock source. UA5000(IPMB) supports a maximum of 10 clock sources.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 On the tab page that is displayed, choose NE Properties > Clock Management > Clock Source from the navigation tree.
3 In the right pane, click the Frequency Clock Source(8k) tab. 4 In the information list, right-click, and then choose Add Clock Source. 5 In the dialog box that is displayed, set the parameters. 6 Click OK. ----End
3.3 Setting the Time Zone and the Daylight Saving Time
This topic describes how to set the time zone of the device location as the time zone of the system, and how to set the start time, the end time, and the offset of the daylight saving time (DST).
Context
l If the preset time zone of the system is incorrect, the backup operation timed at 04:00 am (the time when the traffic on the network is small) may be performed in the daytime (the time when the traffic on the network is heavy). As a result, the CPU is overloaded, and it is also difficult to locate problems. Therefore, we need to use the time zone of the device location as the time zone of the system. The daylight saving time (DST) is ahead of or behind the standard time. If the country or the region of the carrier uses the DST, synchronize the system time with the DST, and adjust, based on the DST, the time-sensitive services to ensure that time information of the accounting, the billing, the alarm, and the log records is correct.
Procedure
1 In the navigation tree, choose a device container under the device node, right-click, and then choose Object Attributes. 2 In the dialog box that is displayed, click the Time Zone and DST tab, and set Time Zone and DST.
Issue 03 (2010-11-19)
3-3
3 Click OK. ----End
3-4
Issue 03 (2010-11-19)
4 Configuring the System Security Policy
4
Context
Configuring the System Security Policy
About This Chapter

System security configuration aims to prevent devices from being attacked by unauthorized packets that are transmitted from the network side or the user side. System security configuration ensures that the devices on the network run in the normal state.
System security features tighten the network security and protect the UA5000(IPMB), and prevent users' attacks on the system to the utmost extent. In this case, the security of the UA5000 (IPMB) is guaranteed. 4.1 Querying the Blacklist The system can filter out all of the service packets whose source IP addresses are included in a firewall blacklist. In this case, the system security and the network security are guaranteed. The purpose of setting the firewall blacklist is to prevent system attacks by malicious users. The user packets are discarded if their source IP addresses are included in the firewall blacklist.
Issue 03 (2010-11-19)
4-1
4 Configuring the System Security Policy
4.1 Querying the Blacklist

The system can filter out all of the service packets whose source IP addresses are included in a firewall blacklist. In this case, the system security and the network security are guaranteed. The purpose of setting the firewall blacklist is to prevent system attacks by malicious users. The user packets are discarded if their source IP addresses are included in the firewall blacklist.
Prerequisite
l l Before querying the system blacklist, enable the firewall blacklist function and add the entries to the blacklist. Before querying the blacklist records on the U2000, set Anti DOS attack function to Enabled in the system parameter profile.
Context
l l Currently, the devices support the functions of enabling the firewall blacklist and adding blacklist entries, while the U2000 supports only the blacklist query. By taking the anti-denial of service (DoS) attack measures, the system receives the control packets sent from users in a restrictive manner. The DoS attack means that malicious users send a large number of control packets to attack the system, which makes the system unable to process normal service requests, that is, the normal services are denied. The system the malicious users who initiate DoS attacks to the blacklist. Then, the control packets sent by these users will not be sent to the control module. For the users listed in the blacklist, the system administrator can force them to go offline.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 On the tab page that is displayed, choose Security > Query Blacklist from the navigation tree. 3 On the Blacklist Query interface, view Attack Port Index, Message Type, Attack Type, and Attack Time. ----End
4-2
Issue 03 (2010-11-19)
5 Configuring the User Security Policy
5
Context
Configuring the User Security Policy
About This Chapter

This topic introduces the user security function and describes how to configure it in the UA5000 (IPMB).
The UA5000(IPMB) supports a series of the user security authentication functions that comply with the security standards. With these functions, the UA5000(IPMB) performs the binding authentication between the user account and the access port to prevent theft and roaming of the user account. 5.1 Setting PITP Management Parameters By setting PITP management parameters, you can implement the PITP user authentication function. In this case, the device provides the upper layer BRAS with the location information of the access user. After the BRAS obtains the information about the service port, it performs the binding authentication between the user account and the access port to avoid theft and roaming of the user account. 5.2 Configuring the Security Enabling or Disabling You can configure the security enabling or disabling in the system parameter profile to guarantee the security of the operators and access users. 5.3 Configuring DHCP Option 82 Dynamic Host Configuration Protocol (DHCP) option 82 is a type of user security mechanism. A user initiates a DHCP request packet, and the device adds the location information of the access user to the option 82 field of the DHCP request packet. This helps the upper layer authentication server authenticate the user.
Issue 03 (2010-11-19)
5-1
5.1 Setting PITP Management Parameters

By setting PITP management parameters, you can implement the PITP user authentication function. In this case, the device provides the upper layer BRAS with the location information of the access user. After the BRAS obtains the information about the service port, it performs the binding authentication between the user account and the access port to avoid theft and roaming of the user account.
Prerequisite
l In PITP V mode, the protocol type to be set cannot conflict with the existing protocol type. The existing protocol types are as follows: The IP protocol type is 2048 (0x0800). The ARP protocol type is 2054 (0x0806). The RARP protocol type is 32821 (0x8035). The 802.1Q protocol is 33024 (0x8100). The PPPoE protocol types are 34915 (0x8863) and 34916 (0x8864). l In the PITP V mode, the Vmode Ethernet protocol type parameter cannot be set.
Context
There are two PITP modes: PPPoE+ mode (P mode), and virtual broadband access server (V mode). In terms of implementation principles, these two modes have the similar functions, that is, binding the user account with the information about the physical port. The differences of these two modes are as follows. l In PITP P mode, the UA5000(IPMB) sends the service port information actively, and adds tags to the PPPoE packets. The UA5000(IPMB) identifies the user based on the service port information carried in the PPPoE authentication request packet, and transmits the service port information to the BRAS. In PITP V mode, the BRAS initiates the request for querying the service port actively. The UA5000(IPMB) is required to report the information about the physical port of the access user. UA5000(IPMB) sends the port information to the BRAS through a response packet.
Procedure
1 Configure global PITP parameters. 1. In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. On the tab page that is displayed, choose NE Properties > Protocol > PITP mode from the navigation tree. Set the parameters such as PITP Administrative status, Vmode Ethernet protocol type, PITP mode of RAIO, PITP Sub Option81, PITP Sub Option82, and PITP Sub Option90. Click Apply.
2. 3.
4.
----End
5.2 Configuring the Security Enabling or Disabling

You can configure the security enabling or disabling in the system parameter profile to guarantee the security of the operators and access users.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 On the tab page that is displayed, choose NE Properties > Security > Security from the navigation tree. 3 Configure Anti ICMP attack function, Anti IP attack function, Anti IP spoofing function, Anti MAC spoofing function, Anti DOS attack function, CLI User Auto Unlocked Time, Lawful Declaration Displayed on User Logging in and MAC mode of PPPoA. 4 Click Apply. ----End
5.3 Configuring DHCP Option 82

Dynamic Host Configuration Protocol (DHCP) option 82 is a type of user security mechanism. A user initiates a DHCP request packet, and the device adds the location information of the access user to the option 82 field of the DHCP request packet. This helps the upper layer authentication server authenticate the user.
Prerequisite
l l Before enabling the DHCP option 82 function, make sure that the upper layer authentication device has completed the authentication configuration. After the DHCP option 82 function is enabled, you can set the maximum length of the DHCP packet. If the length of a DHCP packet that is added with the option 82 field exceeds the maximum length of the DHCP packet, or exceeds the maximum transmission unit (MTU) of the VLAN L3 interface, the system transparently transmits the packet directly, without adding the option 82 field to the DHCP packet. If you do not set the maximum length of the DHCP packet, the system uses the MTU of the VLAN L3 interface as the maximum length of the DHCP packet.
Context
l Currently, the widely used DHCP function has no authentication and security mechanism, especially for the independent DHCP server. In the actual network applications, compared with the Point-to-Point Protocol (PPP), DHCP has some security problems, such as too much DHCP broadcast, DHCP IP address use-up attack, IP address spoofing, MAC address spoofing, and user ID spoofing. In addition, DHCP clients cannot be managed in a centralized manner. To enhance the security when the user obtains IP address through DHCP and enhance the user access security, the UA5000(IPMB) adds a reliable option that is used to identify the user ports and terminal information to the DHCP packets. The DHCP server uses this option
Issue 03 (2010-11-19)
as a valid basis and reference when allocating the IP address and setting the other parameters. This option is called DHCP Relay Agent Information Option. Because its serial number is 82, it is shortened as DHCP option 82. l The DHCP option 82 field includes the CID (circuit ID), RID (remote ID), and optional sub-option90 fields, which provide the user's shelf ID, slot ID, port ID, VPI, and VCI. The formats and contents of CID and RID vary with the RAIO working modes. The suboption90 field contains the line encapsulation information. You can determine whether to add this field by enabling or disabling setting. The UA5000(IPMB) adds the option 82 field to or removes the option 82 field from the DHCP packet only when the DHCP option 82 function is enabled.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 On the tab page that is displayed, choose NE Properties > Protocol > DHCP Option82 from the navigation tree. 3 Set the parameters such as DHCP Option82 and Max length of the DHCP packet after being attached with the Option82 option. 4 Click Apply. ----End
5-4
Issue 03 (2010-11-19)
6 Configuring the DHCP Relay
6
About This Chapter
Context
Configuring the DHCP Relay
The DHCP relay enables the UA5000(IPMB) to function as a bridge between the DHCP clients and servers that are located in different subnets. With this function, the DHCP packets can be relayed to the destination DHCP server (or client) across different subnets. As a result, the DHCP clients in different networks can share the same DHCP server. In this case, it saves the cost and realizes the uniform management.
Figure 6-1 shows the flowchart for configuring the DHCP relay function.
Issue 03 (2010-11-19)
6-1
Figure 6-1 Flowchart for configuring the DHCP relay function

Start
Configure the system parameter profile (DHCP relay mode) Binding a System Parameter Profile
Add a VLAN
Configure L3 Interface of the VLAN
Add a DHCP Server Group
Standard Mode Binding a L3 Interface to a DHCP Server Group
Option60 Mode Add a DHCP domain
MAC Address Segment Mode Add a MAC address segment
Configuring gateway of the domain under the interface
Save the data
End
6.1 Introduction to the DHCP Relay This topic describes the technical principles and service specifications of the dynamic host configuration protocol (DHCP) relay. 6.2 Configuring the DHCP Standard Mode In the DHCP standard mode, the UA5000(IPMB) selects a DHCP server according to the DHCP server group that is bound to the VLAN L3 interface where the DHCP packets of the client are received. 6.3 Configuring the DHCP Option60 Mode In the DHCP option60 mode, the UA5000(IPMB) differentiates the service types according to terminal types, thus forwarding DHCP packets to different DHCP server groups. 6.4 Configuring the DHCP MAC Address Segment Mode In the DHCP MAC address segment mode, the UA5000(IPMB) forwards the DHCP packets matching a certain MAC address segment to the DHCP server group to which the MAC address segment is bound.
6-2
Issue 03 (2010-11-19)
6.1 Introduction to the DHCP Relay

This topic describes the technical principles and service specifications of the dynamic host configuration protocol (DHCP) relay.
Context
DHCP is a solution for dynamic IP address allocation based on the TCP/IP protocol suite. DHCP is only applicable to the case that the DHCP client and the DHCP server are in the same subnet, and the client and the server cannot work across the subnet. In this case, each subnet needs to be set with a DHCP server, which wastes resources. The DHCP relay functions as a bridge between the DHCP clients and servers that are located in different subnets. With this function, the DHCP packets can be relayed to the destination DHCP server (or client) across different subnets. As a result, the DHCP clients on different networks can share the same DHCP server. In this way, it saves cost and realizes uniform management. The UA5000(IPMB) supports L2 and L3 forwarding. L3 forwarding includes the standard mode, Option60 (DHCP domain) mode, and MAC address segment mode. l l In the L2 mode, the UA5000(IPMB) only transparently transmits packets and does not process the packets. When the UA5000(IPMB) is in the L3 forwarding mode, the DHCP packets are forwarded by the DHCP client according to the forwarding mode (standard, Option60, or MAC address segment) that is selected by the DHCP relay module. Table 6-1 describes the features of DHCP relay modes. Table 6-1 L3 forwarding mode Parameter MAC address segment mode Description Selects a DHCP server group based on the source MAC address segment of DHCP packets. The UA5000(IPMB) forwards the DHCP packets that match a certain MAC address segment to the DHCP server group that is bound to the MAC address segment. A MAC address segment can be bound to only one DHCP server group. The device finds the MAC address segment according to the source MAC address of a user, and forwards DHCP packets based on the DHCP server bound to the MAC address segment. The system supports up to 128 MAC address segments.
Issue 03 (2010-11-19)
6-3
Parameter DHCP standard mode
Description Selects a DHCP server based on the IP address of the VLAN L3 interface to forward DHCP packets. The UA5000(IPMB) selects a DHCP server based on the DHCP server group that is bound to the VLAN L3 interface for receiving DHCP packets from the client. A VLAN L3 interface can be bound to only one DHCP server group. Therefore, all the DHCP packets to be sent upstream through the VLAN L3 interface are forwarded to the DHCP server group bound to the VLAN L3 interface.
Option60 (DHCP domain) mode
Selects a DHCP server based on the DHCP Option60 domain. The UA5000(IPMB) differentiates service types according to terminal types, thus forwarding DHCP packets to different DHCP server groups. Option60 is an option in the DHCP packet. It identifies the terminal type. You can select the gateway connected to the interface for the DHCP domain according to different terminal types.
The DHCP relay of the UA5000(IPMB) can be configured as only one forwarding mode in the same period. For details about how to set the forwarding mode, see 2.8.1 Configuring the DHCP Relay Mode. The UA5000(IPMB) enhances the security of the DHCP function through the DHCP option 82 feature. The actual applications over the network may encounter various security problems, because the DHCP function is without the authentication and security mechanism. The UA5000(IPMB) can solve these problems by using the DHCP option 82 option. When the DHCP option 82 function is enabled, the BRAS can authenticate the user. When the DHCP option 82 feature is enabled, the BRAS can authenticate the user. When the DHCP option 82 feature is disabled, the device only transparently transmits the DHCP packets and does not process the packets. For details about how to configure the DHCP option 82 feature, see Setting DHCP Option 82 Parameters.
6.2 Configuring the DHCP Standard Mode

In the DHCP standard mode, the UA5000(IPMB) selects a DHCP server according to the DHCP server group that is bound to the VLAN L3 interface where the DHCP packets of the client are received.
Prerequisite
l The DHCP relay mode must be set in the system parameter profile and must be applied to the device. For details about the operations, see 2.8.1 Configuring the DHCP Relay Mode and 2.8.7 Adding the System Parameter Profile to a Device. The corresponding VLAN must be added. For details about the operations, see 2.1 Adding a VLAN.
6.2.1 Adding a DHCP Server Group

To add a DHCP server group to provide the DHCP services for the DHCP clients in the local network, perform this operation. 6.2.2 Configuring a VLAN L3 Interface The functions of a L3 interface that is based on the VLAN are similar to a L3 switch. Through L3 forwarding, the L3 interface forwards data between different VLANs. 6.2.3 Binding an L3 Interface to a DHCP Server Group To bind a VLAN L3 interface to a DHCP server group, perform this operation. When the DHCP relay function uses the standard mode to forward DHCP packets, you need to configure the VLAN L3 interface of the DHCP server group. After the configuration is successful, all packets received on the VLAN L3 interface are forwarded to the corresponding DHCP server group.

To add a DHCP server group to provide the DHCP services for the DHCP clients in the local network, perform this operation.
Context
l l The system supports up to 20 server groups. The IP addresses of the active and standby servers in each server group must be unique. A server group must contain at least the IP address of an active server.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose Protocol > DHCP from the navigation tree. 3 Select DHCP Server Group tab. 4 In the information list, right-click and choose Add from the shortcut menu. 5 In the dialog box that is displayed, enter the proper parameters.
6 Click OK. ----End
Issue 03 (2010-11-19)
6-5
6.2.2 Configuring a VLAN L3 Interface

Context
Procedure
4 Select a VLAN record, right-click, and then choose Configure. 5 In the dialog box that is displayed, choose Configure VLAN from the navigation tree, click the L3 Interface tab, select Configure L3 Interface, and then set the IP address and the subnet mask of the L3 interface as follows.

6.2.3 Binding an L3 Interface to a DHCP Server Group

To bind a VLAN L3 interface to a DHCP server group, perform this operation. When the DHCP relay function uses the standard mode to forward DHCP packets, you need to configure the VLAN L3 interface of the DHCP server group. After the configuration is successful, all packets received on the VLAN L3 interface are forwarded to the corresponding DHCP server group.
Context
If the VLAN L3 interface is already bound to a DHCP server group, the new value overwrites the original value.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose Protocol > DHCP from the navigation tree. 3 On the Standard Mode tab page, set the querying criteria to display the required records. 4 Right-click a record and choose Modify from the shortcut menu. 5 In the dialog box that is displayed, select DHCP Server Group No.. 6 Click OK. ----End
6.3 Configuring the DHCP Option60 Mode

In the DHCP option60 mode, the UA5000(IPMB) differentiates the service types according to terminal types, thus forwarding DHCP packets to different DHCP server groups.
Prerequisite
l The DHCP relay mode must be set in the system parameter profile and must be applied to the device. For details about the operations, see 2.8.1 Configuring the DHCP Relay Mode and 2.8.7 Adding the System Parameter Profile to a Device. The corresponding VLAN must be added. For details about the operations, see 2.1 Adding a VLAN.
6.3.1 Adding a DHCP Server Group To add a DHCP server group to provide the DHCP services for the DHCP clients in the local network, perform this operation. 6.3.2 Adding a DHCP Domain To create a DHCP domain when the UA5000(IPMB) enables the DHCP relay function and the forwarding mode is the Option60 (DHCP domain) mode, perform this operation. 6.3.3 Configuring a VLAN L3 Interface The functions of a L3 interface that is based on the VLAN are similar to a L3 switch. Through L3 forwarding, the L3 interface forwards data between different VLANs. 6.3.4 Configuring the Gateway IP Address of the Domain Under an Interface
When the DHCP relay working mode is the DHCP domain forwarding mode, you need to configure the gateway IP address corresponding to the DHCP domain. After the gateway IP address is configured successfully, the UA5000(IPMB) can forward packets to the corresponding server through the gateway IP address.

Context
l l The system supports up to 20 server groups. The IP addresses of the active and standby servers in each server group must be unique. A server group must contain at least the IP address of an active server.
Procedure
6 Click OK. ----End
6.3.2 Adding a DHCP Domain

To create a DHCP domain when the UA5000(IPMB) enables the DHCP relay function and the forwarding mode is the Option60 (DHCP domain) mode, perform this operation.
Context
After receiving the DHCP packets containing the Option60 information from a service port, the UA5000(IPMB) checks whether the information matches the domain names by the packets. The matching rule is from long to short, and from start to end. If the DHCP packet does not contain
the Option60 information or does not match a proper domain name after the matching process ends, the device matches the default domain for the DHCP relay.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose Protocol > DHCP from the navigation tree. 3 Click the DHCP Domain tab, right-click, and then choose Add. 4 In the dialog box that is displayed, set the parameters. 5 Click OK. ----End

Context
Procedure
Issue 03 (2010-11-19)
6-9
6.3.4 Configuring the Gateway IP Address of the Domain Under an Interface

When the DHCP relay working mode is the DHCP domain forwarding mode, you need to configure the gateway IP address corresponding to the DHCP domain. After the gateway IP address is configured successfully, the UA5000(IPMB) can forward packets to the corresponding server through the gateway IP address.
Context
On a VLAN interface, a DHCP domain can be configured with only one gateway IP address, and this gateway IP address must be the IP address already configured on the VLAN interface.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose Protocol > DHCP from the navigation tree. 3 Click the DHCP Domain tab, and set the filter criteria to display the required DHCP domains.
6-10
Issue 03 (2010-11-19)
4 Select a record from the DHCP domain list, right-click, and then click the Gateway of the Domain under the Interface tab in the lower pane. 5 Right-click a record and choose Modify from the shortcut menu. 6 In the dialog box that is displayed, set the parameters. 7 Click OK. ----End
6.4 Configuring the DHCP MAC Address Segment Mode

In the DHCP MAC address segment mode, the UA5000(IPMB) forwards the DHCP packets matching a certain MAC address segment to the DHCP server group to which the MAC address segment is bound.
Prerequisite
l The DHCP relay mode must be set in the system parameter profile and the system parameter profile must be applied to the device. For details about the operations, see 2.8.1 Configuring the DHCP Relay Mode and 2.8.7 Adding the System Parameter Profile to a Device. The corresponding VLAN must be added. For details about the operations, see 2.1 Adding a VLAN.
6.4.1 Adding a DHCP Server Group To add a DHCP server group to provide the DHCP services for the DHCP clients in the local network, perform this operation. 6.4.2 Adding a MAC Address Segment To add a DHCP MAC address segment when the UA5000(IPMB) enables the DHCP relay function and the forwarding mode is the MAC address segment mode, perform this operation. 6.4.3 Configuring a VLAN L3 Interface The functions of a L3 interface that is based on the VLAN are similar to a L3 switch. Through L3 forwarding, the L3 interface forwards data between different VLANs. 6.4.4 Configuring the Gateway IP Address Corresponding to the MAC Address Segment Under an Interface To configure the gateway IP address corresponding to the MAC address segment under a VLAN interface, perform this operation. When the DHCP relay mode is the MAC address segment forwarding mode, you need to configure the gateway IP address corresponding to the MAC address segment. After the gateway IP address is configured successfully, the UA5000 (IPMB) can forward packets to the corresponding server through the gateway IP address.

Context
l The system supports up to 20 server groups. The IP addresses of the active and standby servers in each server group must be unique.
Issue 03 (2010-11-19)
A server group must contain at least the IP address of an active server.
Procedure
6 Click OK. ----End
6.4.2 Adding a MAC Address Segment

To add a DHCP MAC address segment when the UA5000(IPMB) enables the DHCP relay function and the forwarding mode is the MAC address segment mode, perform this operation.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose Protocol > DHCP from the navigation tree. 3 Click the MAC Address Segment tab, right-click, and then choose Add. 4 In the dialog box that is displayed, set the parameters.
6-12
Issue 03 (2010-11-19)
5 Click OK. ----End

Context
Procedure
Issue 03 (2010-11-19)
6-13
6.4.4 Configuring the Gateway IP Address Corresponding to the MAC Address Segment Under an Interface
To configure the gateway IP address corresponding to the MAC address segment under a VLAN interface, perform this operation. When the DHCP relay mode is the MAC address segment forwarding mode, you need to configure the gateway IP address corresponding to the MAC address segment. After the gateway IP address is configured successfully, the UA5000 (IPMB) can forward packets to the corresponding server through the gateway IP address.
Context
On a VLAN interface, a MAC address segment can be configured with only one gateway IP address, and this gateway IP address must be the IP address already configured on the VLAN interface.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose Protocol > DHCP from the navigation tree. 3 Click the MAC Address Segment tab, and set the filter criteria to display the required MAC address segments. 4 Select a MAC address segment, and then click the Gateway of the MAC Address Segment Under the Interface tab in the lower pane. 5 Right-click a record and choose Modify from the shortcut menu. 6 In the dialog box that is displayed, select Gateway IP of the MAC Address Segment Under the Interface. 7 Click OK. ----End
6-14
Issue 03 (2010-11-19)
7 Configuring the xDSL Access
7
About This Chapter
Configuring the xDSL Access
This topic describes the ADSL, G.SHDSL, and VDSL2 in the xDSL technology and how to configure the IPoA, PPPoA, IPoE, and PPPoE access services on the UA5000(IPMB). 7.1 Introduction to the xDSL Access Using the existing twisted pair and high frequency (higher than 4 kHz) data compress method, the xDSL technology is a modulation technology providing users with a high rate and high frequency Internet service. Because the xDSL have a higher frequency spectrum than common communication signal, the twisted pair can transmit the voice signal when providing the Internet service with the xDSL technology. 7.2 Configuring the xDSL Access Services This topic describes how to configure the IPoA, PPPoA, IPoE, and PPPoE access services based on the xDSL technology on the UA5000(IPMB). 7.3 Configuration Example of the ADSL IPoA Access Service This topic describes how to configure the ADSL IPoA access service based on the example network. After the configuration, the user can log in to the Internet through the ADSL line in the IPoA mode. 7.4 Configuration Example of the VDSL2 PPPoE Service Based on the example network, this topic describes how to configure the VDSL2 PPPoE service and how to access the Internet in the PPPoE mode through the VDSL2 line after the configuration.
Issue 03 (2010-11-19)
7-1
7.1 Introduction to the xDSL Access

Using the existing twisted pair and high frequency (higher than 4 kHz) data compress method, the xDSL technology is a modulation technology providing users with a high rate and high frequency Internet service. Because the xDSL have a higher frequency spectrum than common communication signal, the twisted pair can transmit the voice signal when providing the Internet service with the xDSL technology.
Context
l ADSL stands for asymmetric digital subscriber line. The ADSL technology uses the asymmetric transmission mode. It provides asymmetric upstream and downstream rates over the existing twisted pair. Users can access the Internet over the ADSL line. The ADSL technology has three standards, namely, ADSL standard, ADSL2 standard, and ADSL2+ standard. The ADSL technology has the following features: The asymmetric digital subscriber line uses the existing twisted pair to transmit data information with high bandwidth for enterprises and family users. Different from the current dialing telephone service, the service provided by the ADSL technology is continuous and always online. The ADSL technology is asymmetric, that is, the ADSL technology uses most of the service channel in the downstream transmission and little service channel to receive information from the users. The ADSL technology can store the analog (voice) and data signals on the same line at the same time. The ADSL technology has the following specifications: The ADSL technology supports the maximum downstream rate 8 Mbit/s, the maximum upstream rate 896 kbit/s, and the maximum transmission distance 5 km. The ADSL2+ technology supports the maximum downstream rate 24 Mbit/s, the maximum upstream rate 1.2 Mbit/s, and the maximum transmission distance 6.5 km. The ADSL2+ is the development of the ADSL technology and the device that supports the ADSL2+ access can support the ADSL and ADSL2 access. l G.SHDSL stands for G.single-pair high-speed digital subscriber line. As a high-speed symmetric transmission technology, it uses the existing unused high frequency in the twisted pair to transmit the data at a high speed with different modulation methods. The G.SHDSL technology has the following features: The transmission rate of the G.SHDSL technology is related to the transmission distance and line quality. Generally, the longer the transmission distance, the poorer is the line quality and the lower is the transmission rate; the shorter the transmission distance, the better is the line quality and the higher is the transmission rate. A G.SHDSL connection can automatically adjust its rate to a proper value according to the line status, such as distance and noise. The G.SHDSL technology has the following specifications: The G.SHDSL supports the transmission distance 3-6 km. The two-wire G.SHDSL line supports the rate 192-5696 kbit/s and the four-wire G.SHDSL line supports the rate 384-4608 kbit/s.
The very high speed digital subscriber line 2 (VDSL2) is the development of the VDSL. It uses the existing twisted pair to provide the asymmetric or symmetric high-speed access service for the users. The VDSL2 technology has the following feature: The VDSL technology supports spectrum profiles of various types and in various encapsulation modes. Hence, the VDSL2 technology provides short-distance and high-rate solutions to the next generation FTTx access scenarios. The VDSL2 technology has the following specifications: The VDSL2 technology supports the maximum symmetric rates 100 Mbit/s, and the maximum transmission distance 3.5 km. When ADSL or ADSL2+ terminal units are connected to VDSL2 lines, the VDSL2 lines can work in the ADSL or ADSL2+ mode. The VDSL2 access service supports two encapsulation modes, that is, ATM and PTM. ATM mode: Transmits the ATM cell on the channel PTM mode: Transmits the IP packet on the channel
Figure 7-1 shows an example network of the ADSL access service on the UA5000(IPMB). Figure 7-1 Example network of the ADSL access service
BRAS
0/2/0 C S R B UA5000 0/11 Modem
I P M B
Modem
PC
PC
Issue 03 (2010-11-19)
7-3

NOTE
l The PC is connected to the service port of the UA5000(IPMB) through the ADSL modem. The user packets are sent to the modem, and sent to the UA5000(IPMB) in different modes (such as IPoA, PPPoA, IPoE, or PPPoE), and then sent upstream to the upper layer network through the upstream port. l The example networks of the G.SHDS access service and of the VDSL2 access service are the same as the example network of the ADSL access service. The difference lies only in the access service cards. This document uses the example network of the ADSL access service as an example.
7.2 Configuring the xDSL Access Services

This topic describes how to configure the IPoA, PPPoA, IPoE, and PPPoE access services based on the xDSL technology on the UA5000(IPMB). 7.2.1 Configuring the IPoA Service This topic describes how to log in to the Internet through the ADSL line in the IPoA mode. The following uses the IPoA access mode of the ADSL technology as an example. The IPoA access modes of the G.SHDSL and VDSL2 technologies are the same as the IPoA access mode of the ADSL technology. The difference lies only in the port types. 7.2.2 Configuring the PPPoA Service This topic describes how to log in to the Internet through the G.SHDSL line in the PPPoA mode. The following uses the PPPoA access mode of the G.SHDSL technology as an example. The PPPoA access modes of the ADSL and VDSL2 technologies are the same as the PPPoA access mode of the G.SHDSL technology. The difference lies only in the port types. 7.2.3 Configuring the IPoE Service This topic describes how to log in to the Internet through the ADSL line in the IPoE mode. The following uses the IPoE access mode of the ADSL technology as an example. The IPoE access modes of the G.SHDSL and VDSL2 technologies are the same as the IPoE access mode of the ADSL technology. The difference lies only in the port types. 7.2.4 Configuring the PPPoE Service This topic describes how to log in to the Internet through the VDSL2 line in the PPPoE mode. The following uses the PPPoE access mode of the VDSL2 technology as an example. The PPPoE access modes of the ADSL and G.SHDSL technologies are the same as the PPPoE access mode of the VDSL2 technology. The difference lies only in the port types.
7.2.1 Configuring the IPoA Service

This topic describes how to log in to the Internet through the ADSL line in the IPoA mode. The following uses the IPoA access mode of the ADSL technology as an example. The IPoA access modes of the G.SHDSL and VDSL2 technologies are the same as the IPoA access mode of the ADSL technology. The difference lies only in the port types.
Prerequisite
l The VLAN must be added and the upstream port of the VLAN must be configured and be downloaded to the device. For details, see 2.1 Adding a VLAN and 2.2 Configuring the Upstream Port of a VLAN. The traffic profile of the MEF IP must be configured and be downloaded to the device. For details, see Configuring an MEF IP Traffic Profile.
7-4
Issue 03 (2010-11-19)
The line profile and alarm profile of the ADSL are configured and be downloaded to the device. For details, see 2.6.1 Configuring an ADSL Line Profile and 2.6.2 Configuring an ADSL Alarm Profile. For enabling the protocol conversion function and configuring the IPoA with the default gateway, see 2.8.4 Configuring the IPoA Parameters.
Context
l IPoA stands for Internet protocol over ATM. The IPoA technology transmits the IP data packet on the ATM-LAN. It stipulates the connection setup among ATM terminals in the ATM network, especially the requirements of the IP data communication through the switched virtual circuit (SVC). With the development of the IP network, the IP access mode in the DSLAM devices becomes a mainstream access mode. To adapt to the user modem that is accessed in the ATM mode, the UA5000(IPMB) supports the conversion from the IPoA/PPPoA protocol to the IPoE/PPPoE protocol, and transparently accesses the IPoA/PPPoA users to the upperlayer IP network. Currently, the actual application services of the IPoA/PPPoA users are common Internet access services. In the IPoA access, for the packet, the user can use a dynamic IP address (not to specify the source IP address of the packet) or a static IP address (to specify the source IP address of the packet). When the user IP address switches from the IPoA dynamic to the IPoA static, however, the IP address has to switch to the LLC-Bridge encapsulation type, and then it can switch to the IPoA static encapsulation type. The UA5000(IPMB) restricts the access rate of a user through either a traffic profile or an ADSL line profile. When both are applied, the smaller value works.
l l
Figure 7-2 shows the flowchart for configuring the IPoA access service on the UA5000 (IPMB).
Issue 03 (2010-11-19)
7-5
Figure 7-2 Flowchart for configuring the IPoA access service
Start Add a VLAN and configure the upstream port for the VLAN Is a proper traffic profile available ? Yes Is a proper line profile available ? Yes No
No
Configure a traffic Profile
Configure a line Profile
Is a proper alarm profile available ? Yes Enable the protocol conversation Configure an alarm Profile
Enable the default IPoA gateway
Configure the service virtual port
Configure the attributes of the xDSL port Activate the xDSL port Configure the MAC address pool Configure the IPoA service encapsulation type of the xDSL port Save the data
End
7-6
Issue 03 (2010-11-19)
Configuring a Service Port

After being configured successfully, the xDSL service port can carry service streams of various types.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose DSL > ADSL from the navigation tree. 3 On the ADSL tab page, set the filter criteria or click to display the ADSL ports.
4 In the information list, select an ADSL port record. On the Service Port tab page in the lower pane, right-click, and then choose Add. 5 In the dialog box that is displayed, set Upstream Traffic Name, Downstream Traffic Name, VLAN Choice, Vlan ID, VPI, VCI, and Service Type.
Issue 03 (2010-11-19)
7-7

NOTE
l The configuration of VLAN ID must be the same as that in 2.2 Configuring the Upstream Port of a VLAN. l Select only the MEF IP Traffic Profile that exists on the device. Otherwise, the system reports an error.
6 Click OK. ----End
Configuring the Attributes of an ADSL Port

This topic describes how to configure a line profile, an alarm profile, extended profile (optional) of an ADSL port. These attributes can be used after the ADSL port is activated.
Context
You can modify the attributes of a port when the port is in the activated, activating, or deactivated state. If the port is in the deactivated state, modify the port attributes directly. If the port is in the activated or activating state, deactivate it before modifying the port attributes.
Procedure
4 In the information list, select an ADSL port record, right-click, and then choose Configure Attributes. 5 In the dialog box that is displayed, bind the ADSL port to the corresponding profile.
6 Click OK. ----End

Result
Click the tabs to view the information about the ADSL port, such as the line quality.
Activating an ADSL Port

The ADSL port can transmit the service in the normal state only when it is activated successfully.
Context
l l l The ADSL port must be activated and then it can transmit the service. Before configuring new parameters to an activated port, you need to deactivate the port, configure the port with a profile with the new parameters, and then activate the port. When you activate a port: If the ATU-R is online (powered on), the activating process is complete after the training is successful. If the ATU-R is offline (powered off), the connection set up during the activating process is interrupted, and the ATU-C is in the detection state. When the ATU-R is powered on again, the training automatically initiates. If the training is successful, the port is activated.
Procedure
4 In the information list, select an ADSL port to be activated, right-click, and then choose Activate. ----End
Configuring a MAC Address Pool

In case of IPoA or PPPoA access, the UA5000(IPMB) needs to convert the IPoA/PPPoA packets to the IPoE/PPPoE packets. In this case, the MAC address pool allocates a MAC address to the user and adds a MAC address (source MAC address) to the ATM cell, thus converting the ATM cell to the Ethernet packet.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose NE Properties > MAC Address Pool from the navigation tree on the tab page that is displayed. 3 In the information list, right-click and choose Add from the shortcut menu. 4 In the dialog box that is displayed, set Start MAC Address, Address Range and Type. 5 Click OK. ----End
Configuring the IPoA Encapsulation Type of an ADSL Port

This topic describes how to configure a specified encapsulation type of the service port. After the encapsulation type is configured successfully, the specified PVC packets are sent upstream or downstream in the configured encapsulation type.
Procedure
4 Click the Service Port Info tab in the lower pane. Select a record from the service port list, right-click, and then choose Configure Extended Properties. 5 In the dialog box that is displayed, set the Protocol Type to llc_ip and then set the Source IP Address and Destination IP Address parameters.
7-10
Issue 03 (2010-11-19)
6 Click OK. ----End
7.2.2 Configuring the PPPoA Service

This topic describes how to log in to the Internet through the G.SHDSL line in the PPPoA mode. The following uses the PPPoA access mode of the G.SHDSL technology as an example. The PPPoA access modes of the ADSL and VDSL2 technologies are the same as the PPPoA access mode of the G.SHDSL technology. The difference lies only in the port types.
Prerequisite
l l l The VLAN must be added and the upstream port of the VLAN must be configured. For details, see 2.1 Adding a VLAN and 2.2 Configuring the Upstream Port of a VLAN. The traffic profile of the MEF IP must be configured. For details, see Configuring an MEF IP Traffic Profile. The line profile and alarm profile of the G.SHDSL are configured. For details, see 2.6.5 Configuring a G.SHDSL Line Profile and 2.6.6 Configuring a G.SHDSL Alarm Profile. For configuring the function of converting PPPoA to PPPoE, see 2.8.3 Enabling the PPPoA Conversion to PPPoE Function.
Context
l PPPoA stands for point to point protocol over ATM. It is used to manage and verify the user information and it is applied in the asynchronous transmission mode as the PPP network protocol. With the development of the IP network, the IP access mode in the DSLAM devices becomes a mainstream access mode. To adapt to the user modem that is accessed in the ATM mode, the UA5000(IPMB) supports the conversion from the IPoA/PPPoA protocol
Issue 03 (2010-11-19)
to the IPoE/PPPoE protocol, and transparently accesses the IPoA/PPPoA users to the upperlayer IP network. l l Currently, the actual application services of the IPoA/PPPoA users are common Internet access services. The UA5000(IPMB) restricts the access rate of a user through either a traffic profile or a G.SHDSL line profile. When both are applied, the smaller value works.
Figure 7-3 shows the flowchart for configuring the PPPoA access service on the UA5000 (IPMB).
7-12
Issue 03 (2010-11-19)
Figure 7-3 Flowchart for configuring the PPPoA access service

Start
Add a VLAN and configure the upstream port for the VLAN
Is a proper traffic profile available? Yes Is a proper line profile available? Yes Is a proper alarm profile available? Yes Configure the PPPoA-to-PPPoE conversion
No Configure a traffic profile No Configure a line profile No Configure an alarm profile
Is the port activated? No Configure the attributes of the G.SHDSL port
Yes Deactivate the G.SHDSL port
Activate the G.SHDSL port
Configure the MAC address pool Configure the PPPoA service encapsulation type of the G.SHDSL port
Save the data
End
Issue 03 (2010-11-19)
7-13

After being configured successfully, the G.SHDSL service port can carry service streams of various types.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose DSL > ATM G.SHDSL Port from the navigation tree. 3 On the ATM G.SHDSL Port tab page, set the filter criteria or click ports. to display the G.SHDSL
4 In the information list, select a G.SHDSL port record. On the Service Port Info tab page in the lower pane, right-click and choose Add from shortcut menu. 5 In the dialog box that is displayed, set Upstream Traffic Name, Downstream Traffic Name, VLAN Choice, Vlan ID, VPI, VCI, and Service Type.
7-14
Issue 03 (2010-11-19)
NOTE
l The preset VLAN ID must be the same as the value preset in 2.2 Configuring the Upstream Port of a VLAN. l Select only the MEF IP Traffic Profile that exists on the device. Otherwise, the system reports an error.
6 Click OK. ----End
Configuring the Attributes of a G.SHDSL Port

This topic describes how to configure a line profile and an alarm profile of a G.SHDSL port. These attributes can be used after the G.SHDSL port is activated.
Context
Procedure
4 In the G.SHDSL port list, right-click a record and choose Configure Attributes from the shortcut menu. 5 In the dialog box that is displayed, bind the G.SHDSL port with the corresponding profile.
6 Click OK. ----End

Activating a G.SHDSL Port

The port can transmit the service in the normal state only when it is activated.
Context
l l l The G.SHDSL port must be activated and then it can transmit the service. Before configuring new parameters for an activated port, you need to deactivate the port, configure the port with a profile with the new parameters, and then activate the port. When you activate a port: If the ATU-R is online (powered on), the activating process is complete after the training is successful. If the ATU-R is offline (powered off), the connection set up during the activating process is interrupted, and the ATU-C is in the detection state. When the ATU-R is powered on again, the training automatically initiates. If the training is successful, the port is activated.
Procedure
4 Select a record from the G.SHDS list, right-click, and then choose Activate. ----End
Configuring a MAC Address Pool

In case of IPoA or PPPoA access, the UA5000(IPMB) needs to convert the IPoA/PPPoA packets to the IPoE/PPPoE packets. In this case, the MAC address pool allocates a MAC address to the user and adds a MAC address (source MAC address) to the ATM cell, thus converting the ATM cell to the Ethernet packet.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose NE Properties > MAC Address Pool from the navigation tree on the tab page that is displayed. 3 In the information list, right-click and choose Add from the shortcut menu. 4 In the dialog box that is displayed, set Start MAC Address, Address Range and Type. 5 Click OK. ----End
Configuring the PPPoA Encapsulation Type of a G.SHDSL Port

To configure the PPPoA encapsulation type of a G.SHDSL Port to llc_ppp, perform this operation.
Procedure
4 Click the Service Port Info tab in the lower pane. Select a record from the service port list, right-click, and then choose Configure Extended Properties. 5 In the dialog box that is displayed, set Protocol Type to llc_ppp. 6 Click OK. ----End
7.2.3 Configuring the IPoE Service

This topic describes how to log in to the Internet through the ADSL line in the IPoE mode. The following uses the IPoE access mode of the ADSL technology as an example. The IPoE access modes of the G.SHDSL and VDSL2 technologies are the same as the IPoE access mode of the ADSL technology. The difference lies only in the port types.
Prerequisite
l l l The VLAN must be added and the upstream port of the VLAN must be configured. For details, see 2.1 Adding a VLAN and 2.2 Configuring the Upstream Port of a VLAN. The traffic profile of the MEF IP must be configured. For details, see Configuring an MEF IP Traffic Profile. The line profile and alarm profile of the ADSL are configured. For details, see 2.6.1 Configuring an ADSL Line Profile and 2.6.2 Configuring an ADSL Alarm Profile.
Context
l IPoE stands for IP over Ethernet. For the IPoE access, after being encapsulated by the Ethernet card on the user PC, the IP packet is directly transmitted to the UA5000(IPMB) without any other encapsulation and change. The UA5000(IPMB) restricts the access rate of a user through either a traffic profile or an ADSL line profile. When both are applied, the smaller value works.
Figure 7-4 shows the flowchart for configuring the IPoE access service on the UA5000 (IPMB).
Issue 03 (2010-11-19)
7-17
Figure 7-4 Flowchart for configuring the IPoE access service

Start
Add a VLAN and configure the upstream port for the VLAN
Is a proper traffic profile available? Yes Is a proper line profile available? Yes Is a proper alarm profile available? Yes Configure the service virtual port
No Configure a traffic profile No Configure a line profile No
Configure an alarm profile
Configure the attributes of the ADSL port
Activate the ADSL port
Save the data
End

After being configured successfully, the xDSL service port can carry service streams of various types.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose DSL > ADSL from the navigation tree.
3 On the ADSL tab page, set the filter criteria or click
to display the ADSL ports.
4 In the information list, select an ADSL port record. On the Service Port tab page in the lower pane, right-click, and then choose Add. 5 In the dialog box that is displayed, set Upstream Traffic Name, Downstream Traffic Name, VLAN Choice, Vlan ID, VPI, VCI, and Service Type.
NOTE
l The configuration of VLAN ID must be the same as that in 2.2 Configuring the Upstream Port of a VLAN. l Select only the MEF IP Traffic Profile that exists on the device. Otherwise, the system reports an error.
6 Click OK. ----End
Configuring the Attributes of an ADSL Port

This topic describes how to configure a line profile, an alarm profile, extended profile (optional) of an ADSL port. These attributes can be used after the ADSL port is activated.
Issue 03 (2010-11-19)
7-19
Context
Procedure
4 In the information list, select an ADSL port record, right-click, and then choose Configure Attributes. 5 In the dialog box that is displayed, bind the ADSL port to the corresponding profile.
6 Click OK. ----End
Result
Click the tabs to view the information about the ADSL port, such as the line quality.
7-20
Issue 03 (2010-11-19)
Activating an ADSL Port

The ADSL port can transmit the service in the normal state only when it is activated successfully.
Context
l l l The ADSL port must be activated and then it can transmit the service. Before configuring new parameters to an activated port, you need to deactivate the port, configure the port with a profile with the new parameters, and then activate the port. When you activate a port: If the ATU-R is online (powered on), the activating process is complete after the training is successful. If the ATU-R is offline (powered off), the connection set up during the activating process is interrupted, and the ATU-C is in the detection state. When the ATU-R is powered on again, the training automatically initiates. If the training is successful, the port is activated.
Procedure
4 In the information list, select an ADSL port to be activated, right-click, and then choose Activate. ----End
7.2.4 Configuring the PPPoE Service

This topic describes how to log in to the Internet through the VDSL2 line in the PPPoE mode. The following uses the PPPoE access mode of the VDSL2 technology as an example. The PPPoE
access modes of the ADSL and G.SHDSL technologies are the same as the PPPoE access mode of the VDSL2 technology. The difference lies only in the port types.
Prerequisite
l l l The VLAN must be added and the upstream port of the VLAN must be configured. For details, see 2.1 Adding a VLAN and 2.2 Configuring the Upstream Port of a VLAN. The traffic profile of the MEF IP must be configured. For details, see Configuring an MEF IP Traffic Profile. The link profile and alarm profile of the VDSL2 are configured. For details, see 2.6.3 Configuring a VDSL2 Line Profile and 2.6.4 Configuring a VDSL2 Alarm Profile.
Context
l PPPoE stands for point-to-point protocol over Ethernet. As the network protocol, it is used to encapsulate the PPP frame in the Ethernet frame. Generally, it is used with the DSL services to provide standard PPP features, such as authorization, encryption, and compression. For the PPPoE access, after being encapsulated by the Ethernet card on the user PC, the IP packet is directly transmitted to the UA5000(IPMB) without any other encapsulation and change. The UA5000(IPMB) restricts the access rate of a user through either a traffic profile or a VDSL2 line profile. When both are applied, the smaller value works.
Figure 7-5 shows the flowchart for configuring the PPPoE access service on the UA5000 (IPMB).
7-22
Issue 03 (2010-11-19)
Figure 7-5 Flowchart for configuring the PPPoE access service

Start Add a VLAN and configure the upstream port for the VLAN
Is a proper traffic profile available? Yes Is a proper line profile available? Yes Is a proper alarm profile available? Yes Configure the service virtual port
No Configure a traffic profile No Configure a line profile No
Configure an alarm profile
Configure the attributes of the VDSL2 port
Activate the VDSL2 port
Save the data
End

After being configured successfully, the VDSL2 port can carry service streams of various types.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose DSL > VDSL2 from the navigation tree. 3 On the VDSL2 tab page, set the filter criteria or click
Issue 03 (2010-11-19)
to display the VDSL2 ports.

7-23
4 In the information list, select a VDSL2 port record. On the Service Port Info tab page in the lower pane, right-click, and then choose Add. 5 In the dialog box that is displayed, set Upstream Traffic Name, Downstream Traffic Name, VLAN Choice, Vlan ID, VPI, VCI, and Service Type.
NOTE
l The preset VLAN ID must be consistent with the value preset in 2.2 Configuring the Upstream Port of a VLAN. l Select only the MEF IP Traffic Profile that exists on the device. Otherwise, the system reports an error.
6 Click OK. ----End
Configuring the Attributes of a VDSL2 Port

This topic describes how to configure a line profile and an alarm profile of a VDSL2 port. These attributes can be used after the VDSL2 port is activated.
Context
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose DSL > VDSL2 from the navigation tree. 3 On the VDSL2 tab page, set the filter criteria or click to display the VDSL2 ports.
4 In the VDSL2 port list, right-click a record and choose Configure Attributes from the shortcut menu. 5 In the dialog box that is displayed, bind the VDSL2 port to the corresponding profile.
6 Click OK. ----End
Activating a VDSL2 Port

A VDSL2 port transmits services in the normal state only after it is activated.
Context
l l l A VDSL2 port must be activated and then it can transmit services. Before setting new parameters for an activated port, you need to deactivate the port, configure the port with a profile with the new parameters, and then activate the port. When you activate a port: If the ATU-R is online (powered on), the activating process is complete after the training is successful. If the ATU-R is offline (powered off), the connection set up during the activating process is interrupted, and the ATU-C is in the detection state. When the ATU-R is powered on
again, the training automatically initiates. If the training is successful, the port is activated.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose DSL > VDSL2 from the navigation tree. 3 On the VDSL2 tab page, set the filter criteria or click to display the VDSL2 ports.
4 In the VDSL2 list, right-click a record and choose Activate from the shortcut menu. ----End
7.3 Configuration Example of the ADSL IPoA Access Service

This topic describes how to configure the ADSL IPoA access service based on the example network. After the configuration, the user can log in to the Internet through the ADSL line in the IPoA mode.
Prerequisite
l l l The example network as shown in Figure 7-6 must be complete. The network devices and lines must be in the normal state. The ADSL service cards are in the normal state.
Example Network
Figure 7-6 shows an example network of the ADSL IPoA service. The PC is connected to the ADSL service port of the UA5000(IPMB) through the ADSL modem. After transmitted through the modem, the user packets are transmitted to the UA5000(IPMB) in the IPoA mode and then transmitted upstream to the upper layer network.
7-26
Issue 03 (2010-11-19)
Figure 7-6 Example network of the ADSL IPoA access service
BRAS
0/2/0 C S R B UA5000 0/11 Modem
I P M B
Modem
PC
PC
NOTE
The UA5000(IPMB) restricts the access rate of a user through either a traffic profile or an ADSL line profile. When both are applied, the smaller value works.
Data Plan
Table 7-1 Data plan for the ADSL service in IPoA mode Item Service card Data ADSL Port: 0/11/0-0/11/31 VPI: 0 VCI: 35 Service Type: Single VLAN ID: 20-51 VLAN Type: MUX VLAN VLAN Attribute: Common The VLAN must be consistent with the VLAN configured on the upper layer device. Remarks -
Issue 03 (2010-11-19)
7-27
Item Upstream port
Data 0/2/0
Remarks The upstream port is also the subport of VLANs 20-51. The Tx service port and the Rx service port use the parameters in the traffic profile for rate restriction. -
IP Traffic Profile
l Name: ip_profile l CAR: 2048 kbit/s l Accept the default values for the other parameters.
Line Profile
Name: adsl_lineprofile ADSL Operating Mode: g.dmt Line Type: Interleaved Adapt Mode in Downstream: Adaptation at Runtime Rate parameters: l ATU-C(Downstream) Interleaved Min.Tx Rate: 32 kbit/s l ATU-R(Upstream) Interleaved Min.Tx Rate: 32 kbit/s l ATU-C(Downstream) Interleaved Max.Tx Rate: 2048 kbit/s l ATU-R(Upstream) Interleaved Max.Tx Rate: 512 kbit/s Accept the default values for the other parameters.
Alarm Profile
Name: adsl_alarmprofile l ATU-C(Downstream) 15-min Loss Thresh: 60s l ATU-C(Upstream) 15-min Loss Thresh: 60s l ATU-C(Downstream) 15-min ESs Thresh: 60s l ATU-C(Upstream) 15-min ESs Thresh: 60s Accept the default values for the other parameters.
MAC Address Pool
Start MAC Address: 00-00-00-00-00-10 Address Range: 256
7-28
Issue 03 (2010-11-19)
Item IPoA encapsulation type
Data llc_ip
Remarks Before configuring the encapsulation type of the service port as IPoA, you must enable the IPoA function. It indicates the IP address of the upper layer router. The destination IP address (Dst IP) in the extended attribute of the service port must be the same as this IP address.
IPoA default gateway
IP Address: 10.1.1.1
Modem
Working mode: IPoA IP Address: 10.1.1.10-10.1.1.41
The source IP address (Src IP) in the extended attribute of the service port must be the same as this IP address.
Procedure
1 Add a VLAN and configure an upstream port to the VLAN. 1. In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. Choose VLAN from the navigation tree. On the VLAN tab page, set the filter criteria or click 3. 4. to display the VLANs. Right-click the list, and then choose Batch Add. In the dialog box that is displayed, click the Base Info tab, and then set the parameters as follows: l Start ID and End ID: 20 and 51 respectively l Type: MUX VLAN l Attribute: Common 5. 6. 7. Click Next. Click the Sub Port tab, configure the upstream port in the VLAN, and then set Sub Port to 0/2/0. Click Done.
2.
2 Configure the IP traffic profile.

1. 2. 3. 4. 5. 6.
Choose Configuration > Access Profile Management > Traffic Profile from the main menu. Click the IP Traffic Profile tab, and select UA5000(IPMB) from the Device Type dropdown list. Right-click and choose Add Global Profile from the shortcut menu. In the dialog box that is displayed, set the IP traffic profile parameters Name to ip_profile and CAR to 2048kbit/s. Click OK. Select the IP traffic profile, right-click, and then choose Download to NE. In the dialog box that is displayed, select the required UA5000(IPMB), and then click OK.
3 Configure the ADSL line profile. 1. 2. 3. 4. Choose Configuration > Access Profile Management > ADSL Profile from the main menu. Click the ADSL Line Profile tab, and select UA5000(IPMB) from the Device Type dropdown list. Right-click and choose Add Global Profile from the shortcut menu. In the dialog box that is displayed, set the ADSL line profile parameters as follows: l Name: adsl_lineprofile l ADSL Operating Mode: G.dmt l Line Type: Interleaved l Adapt Mode in Downstream: Adaptation at Runtime l ATU-C(Downstream)/ATU-R(Upstream) Interleaved Min.Tx Rate: 32kbit/s l ATU-C(Downstream) Interleaved Max.Tx Rate: 2048kbit/s l ATU-R(Upstream) Interleaved Max.Tx Rate: 512kbit/s 5. 6. 7. Click Next to set the ADSL line profile advanced parameters and extended parameters, click Finish. Select the line profile, right-click, and then choose Download to NE. In the dialog box that is displayed, select the required UA5000(IPMB), and then click OK.
4 Configure the ADSL alarm profile. 1. 2. 3. 4. Choose Configuration > Access Profile Management > ADSL Profile from the main menu. Click the ADSL Alarm Profile tab, and select UA5000(IPMB) from the Device Type drop-down list. Right-click and choose Add Global Profile from the shortcut menu. In the dialog box that is displayed, set the parameters of the ADSL alarm profile as follows: l Name: adsl_alarmprofile l ATU-C(Downstream) 15-min Loss Thresh: 60s l ATU-C(Upstream) 15-min Loss Thresh: 60s l ATU-C(Downstream) 15-min ESs Thresh: 60s l ATU-C(Upstream) 15-min ESs Thresh: 60s 5.
7-30
Click OK.
6. 7.
Select the alarm profile, right-click, and then choose Download to NE. In the dialog box that is displayed, select the required UA5000(IPMB), and then click OK.
5 Enable the protocol conversion function and configure the IPoA default gateway. 1. In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. On the tab page that is displayed, choose NE Properties > Encapsulation Management > IPoA from the navigation tree. In the right pane of the interface, set IPoA Enable state as Open and set IP address of the default gateway to 10.1.1.1.
2. 3.
6 Configure a service port. 1. In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. Choose DSL > ADSL from the navigation tree. On the ADSL tab page, set the filter criteria or click to display the ADSL ports.
2. 3. 4. 5.
In the information list, select an ADSL port record. On the Service Port Info tab page in the lower pane, right-click, and then choose Add. In the dialog box that is displayed, set the parameters of the ADSL service port as follows: l In the Traffic Profile Info area, select Keep the upstream and downstream settings the same, and then set the Upstream Traffic Name and Downstream Traffic Name both to ip_profile. l In the User Side area, set the Interface Selection to 0/11/0-0/11/31. l In the Network Side area, set the VLAN parameter as follows and make them consistent with the parameters when you add the VLAN. VLAN Choice: MUX VLAN VLAN ID Start and VLAN ID End: 20 and 51 respectively l In the VPI/VCI Info area, set the VPI/VCI parameters as follows: VPI: 0 VCI: 35 l In the Attributes area, set the Service Type parameter to Single.
6.
Click OK.
7 Configure the attributes of an ADSL port. 1. In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. Choose DSL > ADSL from the navigation tree. On the ADSL tab page, set the filter criteria or click to display the ADSL ports.
2. 3. 4.
Select a record from the ADSL port list, right-click, and then choose Configure Attributes.
Issue 03 (2010-11-19)
5.
In the dialog box that is displayed, bind the ADSL port with the corresponding profile, and then set the Line Profile parameter to adsl_lineprofile and the Alarm Profile parameter to adsl_alarmprofile. Click OK.
6.
8 Activate an ADSL port. 1. In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. Choose DSL > ADSL from the navigation tree. On the ADSL tab page, set the filter criteria or click to display the ADSL ports. Select a record from the port list 0/11/0-0/11/31 to be configured, right-click, and then choose Activate.
2. 3. 4.
9 Configure the MAC address pool. 1. In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. Choose NE Properties > MAC Address Pool from the navigation tree on the tab page that is displayed. In the information list, right-click and choose Add from the shortcut menu. In the dialog box that is displayed, set the Start MAC Address parameter to 00-00-00-00-00-10, the Address Range parameter to 256 and the Type parameter to xpoa. Click OK.
2. 3. 4.
5.
10 Configure the IPoA encapsulation type of the ADSL port. 1. In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. Choose Connection > Service Port from the navigation tree. On the Service Port tab page, set the filter criteria to display the required service virtual ports. Select a record that you need from the service port list, right-click, and then choose Configure Extended Properties. In the dialog box that is displayed, set the Protocol Type parameter to llc_ip and the Source IP Address parameter to 10.1.1.10 and the Destination IP Address parameter to 10.1.1.1. Click Apply, and then configure the IPoA encapsulation type of port 0/11/1-0/11/31 according to the preceding operation: The Source IP Address parameter is 10.1.1.11-10.1.1.41 and the Destination IP Address parameter is 10.1.1.1. Click OK.
2. 3. 4. 5.
6.
7.
11 Save the data. 1. 2. In the Main Topology, select UA5000(IPMB) in the Physical Root navigation tree, rightclick, and then choose Save Data Immediately. Click OK.
----End
Result
After the configuration is complete, the user PC can pass the authentication and log in to the Internet in the IPoA mode.
7.4 Configuration Example of the VDSL2 PPPoE Service

Based on the example network, this topic describes how to configure the VDSL2 PPPoE service and how to access the Internet in the PPPoE mode through the VDSL2 line after the configuration.
Prerequisite
l l l The example network as shown in Figure 7-7 must be complete. Network devices and lines must be in the normal state. The VDSL2 service card must be in the normal state.
Example Network
Figure 7-7 shows an example network of the VDSL2 PPPoE service. The PC is connected to the VDSL2 service port of the UA5000(IPMB) through the VDSL2 modem. After being sent to the modem, the user packets are sent to the UA5000(IPMB) in the PPPoE mode, and then sent upstream to the upper layer network through the upstream port of the control card. Figure 7-7 Example Network of the VDSL2 PPPoE Service
BRAS
0/2/0 V D M B UA5000 0/11 Modem
I P M B
Modem
PC
Issue 03 (2010-11-19)
PC
7-33
NOTE
The UA5000(IPMB) can restrict the access rate of a user through either a traffic profile or a preset VDSL2 line profile by different means. When both profiles are applied, the smaller value works as the user bandwidth. The following example uses the traffic profile as an example to restrict the access rate of the user.
Data Plan
Table 7-2 Data plan for the VDSL2 PPPoE service Item Service card Data VDSL2 port: 0/11/0-0/11/23 VDSL2 port: 0/1/0-0/1/23 VPI: 0 VCI: 35 Service type: Single VLAN ID: 20-43 VLAN selection: MUX VLAN VLAN attribute: Common This VLAN must be the same as the VLAN configured on the upper layer device. The upstream port is also the subport of VLANs 20-43. The Tx service port and the Rx service port use the parameters in the traffic profile for rate limitation. Remarks -
Upstream port
0/2/0
IP Traffic Profile
l Name: ip_profile l CAR: 2048 kbit/s l Use the default values for other parameters.
Line Spectrum Configuration Profile Line Configuration Profile Channel1 Configuration Profile VDSL2 Line Profile
Name: vdsl_linespectrumcfgprofile Accept the default values for the parameters. Name: vdsl_linecfgprofile Accept the default values for the parameters. Name: vdsl_channelcfgprofile Accept the default values for the parameters. Name: vdsl_lineprofile Accept the default values for the parameters.
7-34
Issue 03 (2010-11-19)
Item Line Alarm Configuration Profile Channel1 Alarm Configuration Profile VDSL2 Alarm Profile
Data Name: vdsl_linealarmprofile Accept the default values for the parameters. Name: vdsl_channelalarmprofile Accept the default values for the parameters. Name: vdsl_alarmprofile Accept the default values for the parameters.
Remarks -
Modem
Working mode: PPPoE Obtain the IP address automatically.
Procedure
1 Add a VLAN and configure the upstream port of the VLAN. 1. In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. Choose VLAN from the navigation tree. On the VLAN tab page, set the filter criteria or click 3. 4. to display the VLANs. Right-click the list, and then choose Batch Add. In the dialog box that is displayed, click the Base Info tab to configure the VLAN parameters. Set the values of the parameters as follows: l Set Start ID and End ID to 20 and 43 respectively. l Set Type to MUX VLAN. l Set Attribute to Common. 5. 6. Click the Sub Port tab to configure the upstream port of the VLAN. Set Subport to 0/2/0. Click OK.
2.
2 Configure the IP traffic profile. 1. 2. 3. 4. 5. 6. Choose Configuration > Access Profile Management > Traffic Profile from the main menu. Click the IP Traffic Profile tab, and select UA5000(IPMB) from the Device Type dropdown list. Right-click and choose Add Global Profile from the shortcut menu. In the dialog box that is displayed, set the IP traffic profile parameters Name to ip_profile and CAR to 2048kbit/s. Click OK. Select the IP traffic profile, right-click, and then choose Download to NE. In the dialog box that is displayed, select the required UA5000(IPMB), and then click OK.
3 Configure the VDSL2 line profile.

1. 2. 3. 4.
Choose Configuration > Access Profile Management > VDSL2 Profile from the main menu. Click the Line Spectrum Configuration Profile tab, and select UA5000(IPMB) from the Device Type drop-down list. Right-click and choose Add Global Profile from the shortcut menu. In the dialog box that is displayed, set the parameters of the VDSL2 line spectrum configuration profile as follows: l Name: vdsl_linespectrumcfgprofile l Accept the default values for the other parameters.
5. 6. 7. 8.
Click OK. Click the Channel Configuration Profile tab, and select UA5000(IPMB) from the Device Type drop-down list. Right-click and choose Add Global Profile from the shortcut menu. In the dialog box that is displayed, set the parameters of the VDSL2 channel configuration profile as follows: l Name: vdsl_channelcfgprofile l Accept the default values for the other parameters.
9.
Click OK.
10. Select the VDSL2 channel configuration profile, right-click, and then choose Download to NE. 11. In the dialog box that is displayed, select the required UA5000(IPMB), and then click OK. 12. Click the Line Configuration Profile tab, and select UA5000(IPMB) from the Device Type drop-down list. 13. Right-click and choose Add Global Profile from the shortcut menu. 14. In the dialog box that is displayed, set the parameters of the VDSL2 line configuration profile as follows: l Name: vdsl_linecfgprofile l Accept the default values for the other parameters. 15. Click OK. 16. Select the VDSL2 line configuration profile, right-click, and then choose Download to NE. 17. In the dialog box that is displayed, select the required UA5000(IPMB), and then click OK. 18. Click the Line Template tab. 19. Right-click and choose Add Global Profile from the shortcut menu. 20. In the dialog box that is displayed, set the parameters of the VDSL2 line profile as follows: l Name: vdsl_lineprofile l Line Configuration Profile: vdsl_linecfgprofile l Channel1 Configuration Profile: vdsl_channelcfgprofile l Accept the default values for the other parameters. 21. Click OK. 22. Select the line profile, right-click, and then choose Download to NE.
23. In the dialog box that is displayed, select the required UA5000(IPMB), and then click OK. 4 Configure the VDSL2 alarm profile. 1. 2. 3. 4. 5. Choose Configuration > Access Profile Management > VDSL2 Profile from the main menu. Click the VDSL2 Alarm Profile. Click the Line Alarm Configuration Profile tab. Right-click and choose Add Global Profile from the shortcut menu. In the dialog box that is displayed, set the parameters of the VDSL2 line alarm configuration profile as follows: l Name: vdsl_linealarmprofile l Accept the default values for the other parameters. 6. 7. 8. 9. Click OK. Select the VDSL2 line alarm configuration profile, right-click, and then choose Download to NE. In the dialog box that is displayed, select the required UA5000(IPMB), and then click OK. Click the Channel Alarm Configuration Profile tab.
10. Right-click and choose Add Global Profile from the shortcut menu. 11. In the dialog box that is displayed, set the parameters of the VDSL2 channel alarm configuration profile as follows: l Name: vdsl_channelalarmprofile l Accept the default values for the other parameters. 12. Click OK. 13. Select the VDSL2 channel alarm configuration profile, right-click, and then choose Download to NE. 14. In the dialog box that is displayed, select the required UA5000(IPMB), and then click OK. 15. Click the Alarm Template tab. 16. Right-click and choose Add Global Profile from the shortcut menu. 17. In the dialog box that is displayed, set the parameters of the VDSL2 alarm profile as follows: l Name: vdsl_alarmprofile l Line Alarm Configuration Profile: vdsl_linealarmprofile l Channel1 Alarm Configuration Profile: vdsl_channelalarmprofile l Accept the default values for the other parameters. 18. Click OK. 19. Select the VDSL2 alarm profile, right-click, and then choose Download to NE. 20. In the dialog box that is displayed, select the required UA5000(IPMB), and then click OK. 5 Configure the service port.
1.
In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. Choose DSL > VDSL2 from the navigation tree. On the VDSL2 tab page, set the filter criteria or click to display the VDSL2 ports. In the information list, select a VDSL2 port record. On the Service Port Info tab page in the lower pane, right-click, and then choose Add. Set the parameters of the VDSL2 port in the dialog box that is displayed. Set the values of the parameters as follows: l In Attributes, set Connection Type to LAN-VDSL2. l In the Traffic Profile Info area, select Keep the upstream and downstream settings the same, and then set the Upstream Traffic Name and Downstream Traffic Name both to ip_profile. l In User Side, set Interface Selection to 0/11/0-0/11/23. l In Network Side, set the VLAN parameters. The parameters must be the same as the parameters that are set in step 1. Set VLAN Choice to MUX VLAN. Set VLAN ID Start and VLAN ID End to 20 and 43 respectively. l In VPI/VCI Info, set the parameters of the VPI/VCI. Set the values of the parameters as follows: Set VPI to 0. Set VCI to 35. l In Attributes, set Service Type to Single.
2. 3. 4. 5.
6.
Click OK.
6 Configure the attributes of the VDSL2 port. 1. In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. Choose DSL > VDSL2 from the navigation tree. On the VDSL2 tab page, set the filter criteria or click to display the VDSL2 ports. Select a VDSL2 port from the list, right-click, and then choose Configure Attributes. In the dialog box that is displayed, bind the VDSL2 port to the corresponding profile, and set Line Template to vdsl2_lineprofile and Alarm Template to vdsl_alarmprofile. Click OK.
2. 3. 4. 5. 6.
7 Activate the VDSL2 port. 1. In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. Choose DSL > VDSL2 from the navigation tree. On the VDSL2 tab page, set the filter criteria or click to display the VDSL2 ports. In the list, choose ports 0/11/0-0/11/23 to be activated. Right-click, and then choose Activate.
2. 3. 4.
7-38
8 Save the data. 1. 2. In the Main Topology, select UA5000(IPMB) in the Physical Root navigation tree, rightclick, and then choose Save Data Immediately. Click OK.
----End
Result
After the configuration is complete, the PC of the user can pass the authentication and can access the Internet in the PPPoE mode.
Issue 03 (2010-11-19)
7-39
8 Configuring Multicast Services
8
About This Chapter
Prerequisite
l l l l
Configuring Multicast Services
Multicast is a point-to-multipoint communication mode in which the source transmits messages to a subset of nodes on the network. The UA5000(IPMB) uses the multicast technology to provide IPTV services for carriers. The controlled multicast technology allows carriers to manage and control multicast users on the network equipment, and to provision broadband video services according to the requirements. In this case, multicast services are operable and manageable.
The required VLAN must be added. For details, see 2.1 Adding a VLAN. The VLAN must be configured with an upstream port. For details, see 2.2 Configuring the Upstream Port of a VLAN. The system parameter profile must be configured with multicast system parameters. For details, see 2.8.5 Configuring the Multicast Parameters. The xDSL access mode must be configured. For details, see 7.2 Configuring the xDSL Access Services.
Context
The principles and configurations of multicast services in different xDSL access modes are similar, except for the access mode and parameter settings. Figure 8-1 shows the flowchart for configuring multicast services.
Issue 03 (2010-11-19)
8-1
Figure 8-1 Flowchart for configuring multicast services
Start Add a VLAN and configure the Uplink Port
Configure Multicast Uplink Port
Configure xDSL Access Configure IGMP system Parameters Configure Preview Profile (optional) Deliever the Preview Profile to the device (optional)
Configure Programe Profile
Deliever the Programe Profile to the device Configure Right Profile
Deliever the Right Profile to the device
Configure Multicast User
Save the data
End
8-2
Issue 03 (2010-11-19)
1.
8.2 Configuring the Multicast Upstream Port To provide demand services when the upstream port is not working in the MSTP mode, you need to configure a multicast upstream port to transmit and receive the multicast packets (including the protocol packets and data packets). After the multicast upstream port is added, the multicast packets are transmitted and received through this port. 8.3 Applying a Program Profile to a Device This topic describes how to apply a configured program profile to a device and make the program profile take effect on the device. 8.4 Applying a Rights Profile to a Device This topic describes how to apply a configured rights profile to a device and make the rights profile take effect on the device. 8.5 Configuring a Multicast User This topic describes how to add a multicast user. Only multicast users can watch multicast programs.
2.
3.
4.
Issue 03 (2010-11-19)
8-3
8.1 Introduction to the Multicast Service

As the streaming media such as multimedia videos and data warehouses are emerging in the IP network, the multicast applications become more and more popular. The multicast technology is used in the point-to-multipoint data transmission applications, such as the streaming media, distance learning, video conferencing, video multicasting (such as Web TV), online games, and Internet data center (IDC).
Context
The UA5000(IPMB) provides the operable and manageable multicast service. It supports the IGMP V2/V3, IGMP proxy, and IGMP snooping. l l l l l It supports up to 1024 multicast programs. A multicast user can join up to eight multicast programs at the same time. It supports the program preview function. Users can preview a program for a specific period. The preview times, preview duration, and preview interval are configurable. It supports the audience statistics function. It provides the controlled multicast function to control the multicast programs that multicast users can join in. It supports the rights profile mode. The rights are classified into three types: watchable, previewable, and forbidden. The rights profile mode satisfies the carriers' different requirements for multicast services.
8.2 Configuring the Multicast Upstream Port

To provide demand services when the upstream port is not working in the MSTP mode, you need to configure a multicast upstream port to transmit and receive the multicast packets (including the protocol packets and data packets). After the multicast upstream port is added, the multicast packets are transmitted and received through this port.
Prerequisite
The Uplink port mode parameter cannot be configured with RSTP. For details, see Setting IGMP Parameters.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose Multicast > Uplink Port from the navigation tree. 3 Click Find to display the required multicast upstream port records according to the filter criteria that you specify. 4 In the information list, right-click and choose Add from the shortcut menu. 5 In the dialog box that is displayed, configure the shelf, slot, and port of the upstream port, and then click Assigned Bandwidth.
6 Click OK. ----End
8.3 Applying a Program Profile to a Device

This topic describes how to apply a configured program profile to a device and make the program profile take effect on the device.
Prerequisite
The multicast program profile must be configured. For details, see 2.7.1 Configuring a Program Profile. The VLAN must be configured. For details, see 2.1 Adding a VLAN.
Procedure
1 Choose Configuration > Access Profile Management > IGMP Profile from the main menu. 2 Click the Program Profile tab, and select UA5000(IPMB) from the Device Type drop-down list. 3 Click Filter to display the required program profiles according to the filter criteria that you specify. 4 Select the required profile, right-click, and then choose Download to NE. 5 In the Delivering Program Profile dialog box, select the required devices in the left pane, set the task attributes in the right pane, and then click Next. 6 In the dialog box that is displayed, set the Up Port and VLAN ID, and then click Finish. ----End
8.4 Applying a Rights Profile to a Device

This topic describes how to apply a configured rights profile to a device and make the rights profile take effect on the device.
Prerequisite
The multicast rights profile must be configured. For details, see 2.7.2 Configuring a Rights Profile. The VLAN must be configured. For details, see 2.1 Adding a VLAN.
Procedure
1 Choose Configuration > Access Profile Management > IGMP Profile from the main menu. 2 Click the Right Profile tab, and select UA5000(IPMB) from the Device Type drop-down list. 3 Click Filter to display the required rights profiles according to the filter criteria that you specify. 4 Select the required profile, right-click, and then choose Download to NE. 5 In the Delivering Right Profile dialog box, select the required devices in the left pane, set the task attributes in the right pane, and then click Next. 6 In the dialog box that is displayed, set the Up Port and VLAN ID, and then click Finish.
NOTE
If the selected program profile has been applied to an NE, you need not select an upstream port and enter a VLAN ID.
----End
8.5 Configuring a Multicast User

This topic describes how to add a multicast user. Only multicast users can watch multicast programs.
Prerequisite
The corresponding service virtual port must exist. For details on how to configure the service virtual port in the xDSL access mode, see Configuring a Service Port.
Context
l l When adding a multicast user, you must specify a service virtual port. An authentication user must be bound to a rights profile to obtain relevant rights. A nonauthentication user can watch all the programs configured on the device. You need not configure the rights for a non-authentication user.
8-6
Issue 03 (2010-11-19)
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose Multicast > Multicast User from the navigation tree. 3 On the Multicast User tab page, set the filter criteria to display the required multicast users. 4 On the Multicast User interface, right-click, and then choose Add. 5 In the dialog box that is displayed, set the parameters.
NOTE
After selecting Enable Authorization, click Next. In the dialog box that is displayed, configure the rights profile that is applied to the multicast user.
Issue 03 (2010-11-19)
8-7
9 Configuring the Multicast Services of Subtending Devices
9
Prerequisite
l l
Configuring the Multicast Services of Subtending Devices
About This Chapter

The UA5000(IPMB) provides various types of Ethernet ports, which can be used to subtend devices. This topic describes how to configure multicast services when the UA5000(IPMB) is in a subtending network.
The multicast source must exist in the network. The service card must be in the normal state.
Context
Figure 9-1 shows the flowchart for configuring the multicast service of the upper-layer subtending device (Device A).
Issue 03 (2010-11-19)
9-1
Figure 9-1 Flowchart for configuring the multicast service of the subtending device (Device A)
Start
Add a Standard VLAN
Configure Uplink Port of the VLAN
Configure Multicast Cascade Port
Save the data
End
Figure 9-2 shows the flowchart for configuring the multicast service of the lower-layer subtending device (Device B).
9-2
Issue 03 (2010-11-19)
Figure 9-2 Flowchart for configuring the multicast service of the subtending device (Device B)
Start Add a VLAN and configure the Uplink Port
Configure Multicast Uplink Port
Configure xDSL Access Configure IGMP system Parameters Configure Preview Profile (optional) Deliever the Preview Profile to the device (optional)
Configure Programe Profile
Deliever the Programe Profile to the device Configure Right Profile
Deliever the Right Profile to the device
Configure Multicast User
Save the data
End
Issue 03 (2010-11-19)
9-3
9.1 Introduction to the Multicast Services of Subtend Devices The UA5000(IPMB) provides various types of Ethernet ports. These ports are used to subtend other devices and implement multicast service access. 9.2 Configuration Example of the Multicast Services of Subtend Devices This topic provides an example for configuring the multicast services of subtend devices.
9-4
Issue 03 (2010-11-19)
9.1 Introduction to the Multicast Services of Subtend Devices

The UA5000(IPMB) provides various types of Ethernet ports. These ports are used to subtend other devices and implement multicast service access.
Context
In a subtend network, the access devices are directly interconnected to each other through the FE or GE ports. Subtend networks can extend the network coverage and support a large number of users. Subtend networks make networking more flexible by using the UA5000(IPMB) products. The subtend networking saves the upstream link resources of the access points, reduces the number of local convergence devices, and simplifies the complex networking.
9.2 Configuration Example of the Multicast Services of Subtend Devices

This topic provides an example for configuring the multicast services of subtend devices.
Prerequisite
l l The networking as shown in Figure 9-3 must be completed. The devices on the network must work in the normal state. The multicast source must exist in the network.
The principles and configurations of the multicast services of subtend devices in the different xDSL access modes are similar, except for the access mode and parameter configuration. This topic considers the ADSL access mode as an example.
Example Network
Figure 9-3 shows the example network in which the multicast service of the subtend UA5000 (IPMB) is configured.
Issue 03 (2010-11-19)
9-5
Figure 9-3 Example network of the multicast service of subtend device
Router Multicast Source
0/2/0 I P M B 0/2/1 0/2/0 I P M B C S R I 0/11 Modem C S R I
Device A
Device B
Modem
STB
STB
Data Plan
Table 9-1 provides the data plan. Table 9-1 Data plan for the multicast service in subtend mode Data Device A Remarks
9-6
Issue 03 (2010-11-19)
Data IP address of the upper layer multicast router VLAN 10.0.0.254
Remarks -
VLAN ID: 30 VLAN type: Standard VLAN
Upstream port
Upstream port: 0/2/0 and 0/2/1
The upstream ports are also the subports of the standard VLAN 30. -
Subtend port Program profile
0/2/1 The multicast server provides three programs. Three programs use the default preview profile of the system. l Name of the program profiles: BTV-1, BTV-2, and BTV-3 l Range of multicast addresses: 224.0.1.2-224.0.1.4 l Source IP address of the programs: 10.10.10.10 l Accept the default values for other parameters.
Device B ADSL access mode IP traffic profile Service port: 0/11/0 and 0/11/1 l Name: ip_profile l Priority: 0 l Priority policy: PVC-Setting l CAR: 8 (access rate = 8 x 64 = 512 kbit/ s) VLAN VLAN ID: 30 VLAN type: Standard VLAN Multicast upstream port IGMP global parameter Upstream port: 0/2/0 The VLAN ID is the same as the VLAN ID of device A. The upstream ports are also the subports of the Standard VLAN 30. These are the traffic profiles of the transmit and receive ends of the service virtual port.
l Default video VPI/VCI: 0/35 l Upstream port mode: Default l NTV mode: IGMP_proxy l Rights profile mode: Profile l Accept the default values for other parameters.
Issue 03 (2010-11-19)
9-7
Data Program profile The multicast server provides three programs. Three programs use the default preview profile of the system. l Name of the program profiles: BTV-1, BTV-2, and BTV-3 l Range of multicast addresses: 224.0.1.2-224.0.1.4 l Source IP address of the programs: 10.10.10.10 l Accept the default values for other parameters. Rights profile Name: profile1 Available programs: BTV-1 and BTV-2 Multicast user Use A: l Port: 0/11/0 l The use who requires no authentication. l Maximum number of available programs: 6 Use B: l Port: 0/11/1 l The user who requires authentication. The rights profile is profile1. l Maximum number of available programs: 2
Remarks -
Procedure
l To configure the multicast service of the subtend device A, do as follows. 1. Add a VLAN and configure the upstream port of the VLAN. (1) In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. (2) Choose VLAN from the navigation tree. (3) In the information list, right-click and choose Add from the shortcut menu. (4) In the dialog box that is displayed, set the parameters. VLAN ID: 30 Type: Standard VLAN Attribute: Common (5) Click Next. (6) In the Sub Port tab, select 0/2/0 and 0/2/1 as the upstream port(s).
(7) Click Done. 2. Configure the multicast upstream port. (1) Choose Multicast > Uplink Port from the navigation tree. (2) In the information list, right-click and choose Add from the shortcut menu. (3) In the dialog box that is displayed, select the device name. Set the upstream port to 0/2/0 and percentage of allocated bandwidth to 100%. (4) Click OK. 3. Configure the multicast program profile. Set the parameters as follows: Name of the program profiles: BTV-1, BTV-2, and BTV-3 Range of multicast addresses: 224.0.1.2-224.0.1.4 Source IP address of the programs: 10.10.10.10 Accept the default values for other parameters. 4. Apply a program profile to a device. Set the parameters as follows: Up Port: 0/2/0 VLAN ID: 30 5. Configure the multicast subtend ports. (1) Choose Multicast > Cascading Port from the navigation tree. (2) In the information list, right-click and choose Add from the shortcut menu. (3) In the dialog box that is displayed, set the subtend port to 0/2/1. (4) Click OK. l To configure the multicast service of the subtend device B, do as follows. 1. Add a VLAN and configure the upstream port of the VLAN. (1) In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. (2) Choose VLAN from the navigation tree. (3) In the information list, right-click and choose Add from the shortcut menu. (4) In the dialog box that is displayed, set the parameters. VLAN ID: 30 Type: Standard VLAN Attribute: Common (5) Click Next. (6) In the Sub Port tab, select 0/2/0 and 0/2/1 as the upstream port(s). (7) Click Done. 2. Configure the multicast upstream port. (1) Choose Multicast > Uplink Port from the navigation tree. (2) In the information list, right-click and choose Add from the shortcut menu. (3) In the dialog box that is displayed, select the device name. Set the upstream port to 0/2/0 and percentage of allocated bandwidth to 100%. (4) Click OK.
3.
Add a traffic profile. (1) Choose Configuration > Access Profile Management > Traffic Profile from the main menu. (2) Click the IP Traffic Profile tab, and select UA5000(IPMB) from the Device Type drop-down list. (3) Right-click and choose Add Global Profile from the shortcut menu. (4) In the dialog box that is displayed, set the parameters as follows: Traffic profile name: ip_profile Priority: 0 Priority policy: PVC-Setting CAR: 512 Kbps Accept the default values for other parameters. (5) Click OK.
4.
Configure the service virtual port. (1) Choose Connection > Service Port from the navigation tree. (2) Right-click the list, and then choose Add. (3) In the dialog box that is displayed, set the parameters of the service virtual port as follows: Connection Type: ADSL Traffic profile of the transmit/receive end: ip_profile VLAN information: VLAN Choice: Standard VLAN VLAN ID: 30 Port information: 0/11/0 and 0/11/1 VPI/VCI: 0/35
5.
2.8.5 Configuring the Multicast Parameters and 2.8.7 Adding the System Parameter Profile to a Device. Set the parameters as follows: Default VPI for VOD: 0 Default VCI for VOD: 35 NTV mode: IGMP_proxy Uplink port mode: Default Right profile mode: Profile based mode Accept the default values for other parameters.
6.
Configure the multicast program profile. Set the parameters as follows: Name of the program profiles: BTV-1, BTV-2, and BTV-3 Range of multicast addresses: 224.0.1.2-224.0.1.4 Source IP address of the programs: 10.10.10.10 Accept the default values for other parameters.
7.
Apply a program profile to a device. Set the parameters as follows: Up Port: 0/2/0 VLAN ID: 30
9-10
Issue 03 (2010-11-19)
8.
Configure the rights profile. Set the parameters as follows: Name: profile1 Available programs: BTV-1 and BTV-2
9.
Apply a rights profile to a device. Set the parameters as follows: Up Port: 0/2/0 VLAN ID: 30
10. Configure multicast users. Set the parameters as follows: Use A: Port: 0/11/0 The use who requires no authentication. Maximum number of available programs: 6 User B: Port: 0/11/1 The user who requires authentication. The rights profile is profile1. Maximum number of available programs: 2 l Save the data. ----End
Result
User A of device B is a non-authentication user who can watch all programs. User B is an authentication user who can only watch programs BTV-1 and BTV-2.
Issue 03 (2010-11-19)
9-11
10 Configuring the Triple Play Service
10
Context
Configuring the Triple Play Service
About This Chapter

By the powerful service processing capability, the UA5000(IPMB) provides users with the voice service, data service, and video service at the same time, that is, the triple play service. In addition, the quality of service (QoS) is guaranteed.
Figure 10-1 shows the flowchart for configuring the triple play service.
Issue 03 (2010-11-19)
10-1
Figure 10-1 Flowchart for configuring the triple play service-ADSL access
Start
Configure the traffic profile
Configure the VLAN
Configure the program profile
Configure the rights profile
Configure the ADSL line profile Configure the ADSL alarm profile Configure the system parameter profile Configure the xDSL access
VoIP service Configure the service virtual port
IPTV service Configure the service virtual port
Internet service Configure the service virtual port
Configure the multicast upstream port
Deliver the program profile to the device
Deliver the rights profile to the device
Configure the multicast user
Save the data
End
10-2
Issue 03 (2010-11-19)
10.1 Introduction to the Triple Play Service The triple play service provides subscribers with various service access methods concurrently over one subscriber line. Currently, the high-speed Internet access service, VoIP service, and IPTV service are supported. 10.2 Configuration Example of the Triple Play Service - xDSL Access This topic provides an example for configuring the triple play service. On the user side, the VoIP, IPTV, and Internet services are accessed through different service virtual ports. At least three service virtual ports must be configured for each xDSL port. On the network side, the upstream port must be configured so that the three types of services are transmitted upstream through different VLANs.
Issue 03 (2010-11-19)
10-3
10.1 Introduction to the Triple Play Service

The triple play service provides subscribers with various service access methods concurrently over one subscriber line. Currently, the high-speed Internet access service, VoIP service, and IPTV service are supported.
Context
The major concerns of the triple play service are how to process various services on one service port based on the priorities, and how to lessen the interaction among the services to the utmost extent. l VoIP service: The VoIP service uses low bandwidth and has high requirements on the delay. If the delay is long, the problems such as echo may exist, thus affecting the voice quality. Therefore, the VoIP service has the highest priority among the three types of services. l IPTV service: The IPTV service uses high bandwidth and has high requirements on the bit error rate and the packet loss ratio. If the bit error rate or the packet loss ratio is too high, the video frames are lost, which results in the mosaic of the picture or even the screen mess. Therefore, among the three types of services, the priority of the IPTV service is lower than that of the VoIP service, but higher than that of the high-speed Internet service. l Internet service: Most users of the high-speed Internet service often browse the websites, so the service has low requirements on the real-time feature. In addition, the requirement on the packet loss ratio is not as high as that of the IPTV service, because the system supports the retransmission mechanism to ensure the transmission reliability. Therefore, among the three types of services, the high-speed Internet service has the lowest priority. For convenient management of the three types of services on one port, three VLANs are used on the upstream port of the UA5000(IPMB). Each service has one VLAN.
NOTE
If the services are differentiated by the Ethernet type (IPoE/PPPoE), only two VLANs are needed for upstream transmission.
For the xDSL access, two methods can be used to implement the triple play service, as shown in Table 10-1. The following considers the multi-PVC multi-service mode as an example. Table 10-1 Triple play implementation - xDSL access Implementation Mode Multi-PVC multiservice mode Difference Multiple PVCs are set up between the UA5000(IPMB) and each xDSL terminal to bear various services. Different PVCs are used to differentiate the service flow.
10-4
Issue 03 (2010-11-19)
Implementation Mode Single-PVC multiservice mode
Difference Only one PVC is set up between the UA5000(IPMB) and each xDSL terminal to bear various services. l The Ethernet type (IPoE/PPPoE) is used to differentiate the services. l The VLAN ID from the xDSL terminal is used to differentiate the services. l The 802.1p value from the xDSL terminal is used to differentiate the services. l The combination of the 802.1p value (Ethernet packet) with the VLAN ID is used to differentiate the services. l The combination of the Ethernet type (IPoE/PPPoE) with the VLAN ID is used to differentiate the services.
10.2 Configuration Example of the Triple Play Service xDSL Access

This topic provides an example for configuring the triple play service. On the user side, the VoIP, IPTV, and Internet services are accessed through different service virtual ports. At least three service virtual ports must be configured for each xDSL port. On the network side, the upstream port must be configured so that the three types of services are transmitted upstream through different VLANs.
Context
Figure 10-2 shows an example network of the triple play service.
Issue 03 (2010-11-19)
10-5
Figure 10-2 Example network of the triple play service
Multicast source
OSS & RADIUS Server/RADIUS Proxy NMS
IPTV DHCP Server TG BRAS LSW Router VoIP DHCP Server
I P M B
I P M B
C S R I
UA5000 Modem Home gateway 1 DHCP PPPoE DHCP STB DHCP Modem Home gateway 2 PPPoE DHCP STB
Ephone
PC
TV
Ephone
PC
TV
10-6
Issue 03 (2010-11-19)
NOTE
In the triple play network, one user terminal provides various service access modes at the same time. l l The UA5000(IPMB) transmits the VoIP service to the next generation network (NGN) or to the public switched telephone network (PSTN) through the TG. The IPTV service provides users with video services, that is, program sources. l The IGMP proxy control packets are transmitted upstream to the video server through the UA5000(IPMB). In this way, the management of the multicast users and programs is implemented. l The video service stream is sent from the multicast server. Then, the UA5000(IPMB) transparently transmits the video service stream to the user terminal. l On the user side, the set top box (STB) terminates the video signals, converts the media, and controls program switching. l The UA5000(IPMB) accesses the Internet service. The service data is transmitted upstream to the IP network after processed by the BRAS.
Table 10-2 provides the data plan for the triple play service. Table 10-2 Data plan for the triple play service Item Upstream port Service card Data 0/2/0 l Port: 0/11/0 l VoIP service: VPI/VCI = 0/35 l IPTV service: VPI/VCI = 0/36 l Internet service: VPI/VCI = 0/37 ADSL profiles Line profile l Name: adsl_lineprofile l Accept the default values for the other parameters. Alarm profile l Name: alarm_profile l Accept the default values for the other parameters.
Issue 03 (2010-11-19)
10-7
Item IP traffic profile
Data VoIP service l Name: profile_voip l CAR: 2048 kbit/s l Priority: 6 l Accept the default values for the other parameters. IPTV service l Name: profile_iptv l CAR: 2048 kbit/s l Priority: 5 l Accept the default values for the other parameters. Internet service l Name: profile_internet l CAR: 2048 kbit/s l Priority: 1 l Accept the default values for the other parameters.
VLAN
VoIP service l VLAN type: Smart VLAN l VLAN ID: 11 IPTV service l VLAN type: Smart VLAN l VLAN ID: 12 Internet service l VLAN type: Smart VLAN l VLAN ID: 13
System parameter profile Program profile
l Name: systemprofile l The profile is already bound to the device. l Name: BTV-1 l IP address: 224.1.1.1 l Source IP address of the program: IP address of the ISP1 (10.10.10.10)
Rights profile
l Name: profile1 l The user with the rights can watch BTV-1 in the program library.
Multicast user
l Port: 0/11/0 l Name: IGMPUserA l Accept the default values for the other parameters.
10-8
Issue 03 (2010-11-19)
Procedure
l Pre-configure the parameters for service provisioning. 1. Set IP traffic profile. (1) Choose Configuration > Access Profile Management > Traffic Profile from the main menu. (2) Click the IP Traffic Profile tab, and select UA5000(IPMB) from the Device Type drop-down list. Right-click and choose Add Global Profile from the shortcut menu. (3) In the dialog box that is displayed, set the parameters. VoIP service Name: profile_voip CAR: 2048 kbit/s Priority: 6 IPTV service Name: profile_iptv CAR: 2048 kbit/s Priority: 5 Internet service Name: profile_internet CAR: 2048 kbit/s Priority: 1 (4) Click OK. (5) Select the traffic profile, right-click, and then choose Download to NE. (6) Click OK. 2. Add a program profile. (1) Choose Configuration > Access Profile Management > IGMP Profile from the main menu. (2) Click the Program Profile tab, and select UA5000(IPMB) from the Device Type drop-down list. (3) Right-click and choose Add Global Profile from the shortcut menu. In the dialog box that is displayed, set the parameters. Name: BTV-1 Begin IP Address: 224.1.1.1 End IP Address: 224.1.1.1 Source IP Address: 10.10.10.10 (4) Click OK. 3. Add a rights profile. (1) Click the Right Profile tab, and select UA5000(IPMB) from the Device Type drop-down list. (2) Right-click and choose Add Global Profile from the shortcut menu. In the dialog box that is displayed, set the parameters.
Name: profile1 Program list: BTV-1 Accept the default values for the other parameters. (3) Click OK. 4. Configure an ADSL line profile. (1) Choose Configuration > Access Profile Management > ADSL Profile from the main menu. (2) Click the ADSL Line Profile tab, and select UA5000(IPMB) from the Device Type drop-down list. (3) Right-click and choose Add Global Profile from the shortcut menu. (4) In the dialog box that is displayed, set the parameters. Name: adsl_lineprofile Accept the default values for the other parameters. (5) Click Finish. (6) Select the line profile, right-click, and then choose Download to NE. (7) In the dialog box that is displayed, select the required device, and then click OK. 5. Configure an ADSL alarm profile. (1) Choose Configuration > Access Profile Management > ADSL Profile from the main menu. (2) Click the ADSL Alarm Profile tab, and select UA5000(IPMB) from the Device Type drop-down list. (3) Right-click and choose Add Global Profile from the shortcut menu. (4) In the dialog box that is displayed, set the parameters. Name: alarm_profile Accept the default values for the other parameters. (5) Click OK. (6) Select the alarm profile, right-click, and then choose Download to NE. (7) In the dialog box that is displayed, select the required device, and then click OK. 6. Configure a system parameter profile. (1) Choose Configuration > Access Profile Management > System Parameter Profile from the main menu. (2) On the System Parameter Profile tab page, select UA5000(IPMB) from the Device Type drop-down list. (3) Right-click and choose Add Global Profile from the shortcut menu. (4) In the dialog box that is displayed, enter the name of the system parameter profile. Choose all parameters from the Parameters for Selection navigation tree, click to add the parameters to the Selected Parameters navigation tree, and then click Next.
NOTE
Set the name of the system parameter profile to systemprofile.
10-10
Issue 03 (2010-11-19)
(5) Click Finish. (6) Select the system parameter profile whose name is systemprofile, right-click, and then choose Download to NE. (7) In the dialog box that is displayed, select a device name.
NOTE
In the dialog box that is displayed, select the Show window of task manager after finished check box, and click OK to display the scheduling center interface.
(8) Click OK. 7. Configure a VLAN. (1) In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. (2) Choose VLAN from the navigation tree. (3) On the VLAN tab page, right-click, and then choose Add. (4) In the dialog box that is displayed, set the parameters. On the Base Info interface, set the parameters as follows. VLAN ID: 11 (Add VLAN IDs 12 and 13 in turn.) Type: Smart VLAN On the Sub Port tab page of the Configure VLAN interface, add 0/2/0 as the upstream port of the VLAN. (5) Click Finish. l Configure the ADSL access. 1. Bind an ADSL port with the related profile. (1) In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. (2) Choose DSL > ADSL from the navigation tree. (3) On the ADSL tag page, select ADSL port 0/11/0, right-click, and then choose Configure. (4) In the dialog box that is displayed, set the parameters. Line Profile: adsl_lineprofile Alarm Profile: alarm_profile (5) Click OK. 2. Activate an ADSL port. On the ADSL tag page, select ADSL port 0/11/0, right-click, and then choose Activate. l Configure the VoIP service. 1. Configure a service virtual port. (1) Choose Connection > Service Port from the navigation tree. (2) On the Service Port tab page, right-click, and then choose Add. (3) In the dialog box that is displayed, set the parameters. Traffic profile name: profile_voip
VLAN ID: 11 VPI/VCI: 0/35 Interface Selection: 0/11/0 (4) Click OK. l Configure the IPTV service. 1. Configure a service virtual port. For details, see the steps of configuring a service virtual port when configuring the VoIP service. Traffic profile name: profile_iptv VLAN ID: 12 VPI/VCI: 0/36 Interface Selection: 0/11/0 2. Configure a multicast upstream port. (1) In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. (2) Choose Multicast > Uplink Port from the navigation tree. (3) On the Uplink Port tab page, right-click, and then choose Add. (4) In the dialog box that is displayed, set Uplink Port Info to 0/2/0. (5) Click OK. 3. Apply a program profile to the device. (1) Choose Configuration > Access Profile Management > IGMP Profile from the main menu. (2) Click the Program Profile tab, and select UA5000(IPMB) from the Device Type drop-down list. (3) Select the program profile whose IP Address is 224.1.1.1 from the list, rightclick, and then choose Download to NE. (4) In the dialog box that is displayed, select the required device, set the task attributes in the right pane, and then click Next. In the dialog box that is displayed, set VLAN ID to 12. (5) Click OK. 4. Apply a rights profile to a device. (1) Choose Configuration > Access Profile Management > IGMP Profile from the main menu. (2) Click the Right Profile tab, and select UA5000(IPMB) from the Device Type drop-down list. (3) Select the rights profile whose Name is profile1 from the list, right-click, and then choose Download to NE. (4) In the dialog box that is displayed, select the required device, set the task attributes in the right pane, and then click Next. In the dialog box that is displayed, set VLAN ID to 12. (5) Click OK. 5.
10-12
Configure a multicast user.

(1) In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. (2) Choose Multicast > Multicast User from the navigation tree. (3) On the Multicast User tab page, right-click, and then choose Add. (4) In the dialog box that is displayed, set the parameters. Alias: IGMPUserA Select Enable Authorization. Select the configured service virtual port. Rights profile: profile1 (5) Click Finish. l Configure the Internet service. Configure a service virtual port. For details, see the steps of configuring a service virtual port when configuring the VoIP service. Traffic profile name: profile_internet VLAN ID: 13 VPI/VCI: 0/37 Interface Selection: 0/11/0 l Save the data. 1. 2. ----End In the Main Topology, select UA5000(IPMB) in the navigation tree, right-click, and then choose Save Data Immediately. Click OK.
Result
l l l The VoIP user can make calls successfully. The multicast user whose service port is 0/11/0 can watch the program whose IP address is 224.1.1.1. The Internet user can access the Internet in PPPoE dialing mode.
Issue 03 (2010-11-19)
10-13
11 Configuring VLAN Stacking Wholesale Services
11
Prerequisite
Configuring VLAN Stacking Wholesale Services
About This Chapter

VLAN stacking allows batches of users to access the services provided by their respective ISPs according to certain rules.
l l l l
The IP traffic profile must be configured. For details, see and 2.5.2 Configuring an IP Traffic Profile. The required VLAN must be added. For details, see 2.1 Adding a VLAN. The VLAN must be configured with an upstream port. For details, see 2.2 Configuring the Upstream Port of a VLAN. The corresponding access services must be configured. For details, see 7.2 Configuring the xDSL Access Services.
Context
When there are multiple ISPs in the layer 2 metropolitan area network (MAN), the wholesale service allows batches of user to access the services provided by their ISPs according to certain rules. A stacking VLAN packet has inner and outer VLAN tags that are allocated by the UA5000 (IPMB). The upper layer BRAS device authenticates the packet based on the two VLAN tags. Two VLAN tags increases the number of access users. Figure 11-1 shows the flowchart for configuring the wholesale service.
Issue 03 (2010-11-19)
11-1
Figure 11-1 Flowchart for configuring the wholesale service
Start
Configure the VLAN
Configure an upstream port for the VLAN
Set the VLAN attribute
Set the inner VLAN tag
Save the data
End
1.
11.2 Configuring the VLAN Stacking Attribute Stacking is an attribute of the VLAN. VLAN stacking is mainly used in the wholesale service. 11.3 Configuring the Inner VLAN Tag The packet of a VLAN with the stacking attribute has an inner VLAN tag and an outer VLAN tag. The inner VLAN tag is used to identify the user.
2.
11-2
Issue 03 (2010-11-19)
11.1 Introduction to VLAN Stacking Wholesale Services

VLAN stacking refers to the stack of the 802.1q tags. It allows the device to add two 802.1q VLAN tags to an untagged user packet or change a tagged user packet into a packet with two 802.1q VLAN tags. The packet with two VLAN tags can be transmitted over the backbone network of the service provider. When the packet reaches the BRAS, the BRAS authenticates the packet based on the two VLAN tags, or removes the outer VLAN tag and identifies the user by the inner VLAN tag.
Background
The VLAN stacking feature allows the UA5000(IPMB) to add an inner 802.1q VLAN tag and an outer 802.1q VLAN tag to an access user packet. The packet with two VLAN tags is transmitted to the layer 2 switching network, and forwarded to the ISP network according to the outer VLAN tag. Wholesale service: In a layer 2 MAN, there may be multiple Internet service providers (ISPs). The services of these ISPs need to be provisioned to their users quickly. Therefore, the outer VALN tag is used to identify the ISP and the inner VLAN tag is used to identify the user. In this manner, different user groups with different outer VLAN tags can gain access to the specified ISP networks and obtain the services provided by the ISPs. Figure 11-2 shows the example network of the wholesale service. Users 1, 2, 3, and 4 are configured in the same way. The broadband service of users 1 and 2 and the broadband service of users 3 and 4 are provided by different ISPs. The VLAN stacking feature allows the UA5000(IPMB) to add two VLAN tags to a user packet and forward the user packet to the layer 2 network. The outer VLAN tag is used to identify the ISP and the inner VLAN tag is used to identify the user. The layer 2 switch forwards the user packet to the specified ISP BRAS according to the outer VLAN tag. The ISP BRAS removes the outer VLAN tag and identifies the user by the inner VLAN tag. After being authenticated by the ISP BRAS, the user can access the services provided by the ISP.
Issue 03 (2010-11-19)
11-3
Figure 11-2 Example network of the wholesale service
ISP1
BRAS
VLAN ID:20
VLAN ID:21 BRAS
ISP2
I P M B
C S R I
C S R I
0/2/0
Modem
UA5000
PC1
PC2
PC3
PC4
11.2 Configuring the VLAN Stacking Attribute

Stacking is an attribute of the VLAN. VLAN stacking is mainly used in the wholesale service.
Prerequisite
To set the stacking attribute for the VLAN, make sure that the VLAN must be added. For details, see 2.1 Adding a VLAN.
Context
The UA5000(IPMB) supports up to 4000 stacking VLANs. The following VLANs cannot be configured with the stacking attribute:
l l l l l l l
Super VLAN Sub VLAN Standard VLAN VLAN with a layer-3 interface VLAN with a service virtual port Default VLAN Reserved VLAN
Procedure
4 Select the VLAN to be configured, right-click, and then choose Configure. 5 In the dialog box that is displayed, set Attribute to Stacking. 6 Click Done. ----End
11.3 Configuring the Inner VLAN Tag

The packet of a VLAN with the stacking attribute has an inner VLAN tag and an outer VLAN tag. The inner VLAN tag is used to identify the user.
Prerequisite
Service virtual ports must be configured for the VLAN with the stacking attribute.
Procedure
4 Select the stacking VLAN to be configured, and click the Service Port tab in the lower pane. 5 Select a record from the service virtual port list, right-click, and then choose Configure Extended Properties. 6 In the dialog box that is displayed, set Inner VLAN ID as follows.
Issue 03 (2010-11-19)
11-5
7 Click OK. ----End
11-6
Issue 03 (2010-11-19)
12 Configuring the QinQ VLAN Private Line Service
12
Prerequisite
l l l l
Configuring the QinQ VLAN Private Line Service
About This Chapter

QinQ VLAN is used in the private line services of enterprise private networks to provide safe channels for the data transmission between the enterprise private networks.
The IP traffic profile must be configured. For details, see 2.5.2 Configuring an IP Traffic Profile. The corresponding VLAN must exist. For details, see 2.1 Adding a VLAN. The VLAN must be configured with an upstream port. For details, see 2.2 Configuring the Upstream Port of a VLAN. The corresponding access services must be configured. For details, see 7.2 Configuring the xDSL Access Services.
Context
The private line service allows the private network services to be transparently transmitted to the peer end, for example, on an Intranet. To communicate with each other, users that are on the same private network but at different locations are connected to the public network through the UA5000(IPMB). On the UA5000 (IPMB), configure the upstream VLAN for user packets from the private network to have the QinQ attribute. In this way, the packet has two VLAN tags: an inner VLAN tag from the private network and an outer VLAN tag from the public network. Through the outer VLAN tag, the packet is transparently transmitted to the peer private network user. In this way, private network users can communicate with each other. Figure 12-1 shows the flowchart for configuring the private line service.
Issue 03 (2010-11-19)
12-1
Figure 12-1 Flowchart for configuring the private line service
Start
Configure the VLAN
Configure an upstream port for the VLAN
Set the VLAN attribute
Save the data
End
1.
12.2 Configuring the VLAN QinQ Attribute QinQ is an attribute of the VLAN. QinQ VLAN is mainly used in the private line service.
12-2
Issue 03 (2010-11-19)
12.1 Introduction to the QinQ VLAN Private Line Service

QinQ VLAN is a tunnel protocol based on the 802.1Q encapsulation. QinQ VLAN adds an 802.1Q tag to a VLAN packet that already has an 802.1Q tag from the private network so that this VLAN packet can be transparently transmitted from the private network to the layer-2 VPN through the public network.
Background
The UA5000(IPMB) receives a packet with a private VLAN tag and uses the QinQ (802.1Q in 802.1Q) feature to add a public VLAN tag (that is, the QinQ VLAN tag) to the packet. The packet with the private VLAN tag is forwarded to the peer UA5000(IPMB) over the public network according to its outer public VLAN tag. The peer UA5000(IPMB) removes the outer VLAN tag and transmits the packet to the peer private network. Figure 12-2 shows the example network of the private line service. Figure 12-2 Example network for private line service configuration
L2/L3 I P M B C S R I
L2/L3 I P M B C S R I
0/2/0
UA5000_A Modem
0/2/0
UA5000_B Modem
LAN Switch
LAN Switch
corporateA
corporateA
Issue 03 (2010-11-19)
12-3

NOTE
l Two offices of the enterprise are connected to the metropolitan area network (MAN) through device_A and device_B respectively. After the QinQ VLAN private line service is configured on the UA5000 (IPMB), the services can be transparently transmitted between the two offices within the enterprise private network over the public network. l Device_A and device_B are configured in the same way.
12.2 Configuring the VLAN QinQ Attribute

QinQ is an attribute of the VLAN. QinQ VLAN is mainly used in the private line service.
Prerequisite
To set the QinQ attribute for one VLAN, make sure that the VLAN must be added. For details, see 2.1 Adding a VLAN.
Context
The UA5000(IPMB) supports up to 4000 QinQ VLANs. When adding VLANs in batches, set the QinQ attribute for the VLANs directly. The following VLANs cannot be configured with the QinQ attribute: l l l l l l Super VLAN Sub VLAN VLAN with a layer-3 interface VLAN with a service virtual port Default VLAN Reserved VLAN
Procedure
4 Select the VLAN to be configured, right-click, and then choose Configure 5 In the dialog box that is displayed, set Attribute to QinQ. 6 Click Finish. ----End
12-4
Issue 03 (2010-11-19)
13 Configuring the CESoP TDM Private Line Service
13
Prerequisite
l
Configuring the CESoP TDM Private Line Service
About This Chapter

Circuit emulation services over packet (CESoP) refers to the service in which circuit emulation services are implemented on the packet switched network. By using the circuit emulation services based on packet switching, carriers support the seamless TDM services over the packet switched network.
The IP address of the COPA card must be configured properly.
Context
Figure 13-1 shows the flowchart for configuring the CESoP TDM private line service.
Issue 03 (2010-11-19)
13-1
Figure 13-1 Flowchart for configuring the CESoP TDM private line service
Start
Configure a smart VLAN Configure the IP address of the board Configure a CES E1 port
Add a CESoP connection
Save the data
End
1.
13.2 Configuring the CES E1 Port This topic describes how to modify the line encoding mode, the working mode, and the clock mode of the CES E1 port. You must set the working mode of the E1 port before configuring services on the E1 port. After the working mode of the E1 port is changed, the port switches from the idle state to a working state. 13.3 Configuring the CESoP Connection The card must be configured with CESoP connections before it can bear the CESoP service. After a CESoP connection and its service stream are added successfully, the communication on the CESoP E1 line becomes normal. 13.4 Configuration Example of the CESoP TDM Private Line Service This topic provides an example for configuring the CESoP TDM private line service.
2.
3.
13-2
Issue 03 (2010-11-19)
13.1 Introduction to the CESoP TDM Private Line Service

The UA5000(IPMB) transmits the CESoP TDM private line service data to the upstream by the CES E1 port. The circuit switched network is evolving to the packet switched network. During the deployment of the IP network, the method of providing traditional circuit switched service over the IP network must be taken into consideration. CESoP is a solution to carrying the TDM service over the packet switched network.
Background
The UA5000(IPMB) provides TDM service solutions through the COPA card. The COPA card converts the TDM frames into the CESoP frames, and provides 16 E1 interfaces to forward the E1 service to the upper layer TDM network. The basic idea of the CESoP is to establish a "channel" on a packet switched network to transmit the services based on the TDM links (such as T1 and E1 services). In this way, the TDM devices on either end of the network do not need to know whether they are connected to a TDM network. The packet switched network is used to emulate TDM circuit services. This is the meaning of circuit emulation.
13.2 Configuring the CES E1 Port

This topic describes how to modify the line encoding mode, the working mode, and the clock mode of the CES E1 port. You must set the working mode of the E1 port before configuring services on the E1 port. After the working mode of the E1 port is changed, the port switches from the idle state to a working state.
Context
NOTE
Modifying the line encoding mode may affect the services. Exercise caution when performing this operation.
The CES E1 port supports the following two types of line encoding modes: AMI and HDB3. l AMI encoding: The binary code zero is converted into the baseband signal whose amplitude is 0. The binary code one is converted into the return-to-zero code whose value is +1 and -1 alternatively. The defect of this encoding mode is that when multiple 0s occur consecutively, it is difficult to extract the timing signal. Therefore, in this encoding mode, the number of 0s is restricted. HDB3 encoding: When there are less than four consecutive 0s, the AMI encoding mode is used. When there are four consecutive 0s, the first and the forth 0s are converted to 0 or 1 according to the value of 1 before the four 0s. At the receiving end, if two 1s of the same polarity are received consecutively and there are three consecutive 0s before the two 1s, the second one is converted into zero. If there are two consecutive 0s before the consecutive 1s of the same polarity, the two 1s are converted into 0s. In this way, the original data signal is reconstructed. System: system clock. This is the clock of the OLT system. Line: line clock. This is the clock on the E1 line.
The clock mode of the CES E1 port is of three types: l l

Issue 03 (2010-11-19)
ACM: Adapt clock state. The adaptive restoration clock refers to the clock that is restored and output from the received service packet stream through the adaptive algorithm.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose E1/T1 > CES E1/T1 Port from the navigation tree. 3 On the CES E1 Port tab page, set the filter criteria to display the required CES E1 ports. 4 Right-click a record and choose Modify from the shortcut menu. 5 In the dialog box that is displayed, set the parameters.
6 Click OK. ----End
13.3 Configuring the CESoP Connection

The card must be configured with CESoP connections before it can bear the CESoP service. After a CESoP connection and its service stream are added successfully, the communication on the CESoP E1 line becomes normal.
Context
The local UDP port number maps the E1 port. On a COPA card, the same local UDP port cannot be configured for two CESoP connections.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose E1/T1 > CES E1/T1 Port from the navigation tree. 3 On the CES E1 Port tab page, set the filter criteria to display the required CES E1 ports. 4 Select a record from the CES E1 port list, and then click the CESoP Info tab in the lower pane.
NOTE
The selected port is the upstream port for the CESoP service.
5 Right-click the list, and then choose Add CESoP Connection. 6 In the dialog box that is displayed, set the parameters.
7 Click OK. ----End
13.4 Configuration Example of the CESoP TDM Private Line Service

This topic provides an example for configuring the CESoP TDM private line service.
Context
l The circuit switched network is evolving to the packet switched network. During the deployment of the packet switched network, the method of providing traditional circuit switched service over the packet switched network must be taken into consideration. During the deployment of the IP network, the method of providing traditional circuit switched service over the IP network must be taken into consideration. CESoP is a solution to carrying the TDM service on the packet switched network. The UA5000 supports the structure-agnostic TDM over PSN (SAToPSN CESoP) service. The tunnel carrying the CESoP service uses the IP+UDP mode and the encapsulation format complies with RFC4553.
Issue 03 (2010-11-19)
Example Network
Figure 13-2 shows an example network of the CESoP TDM private line service. The COPA card of UA5000(IPMB) converts TDM signals into CESoP Ethernet packets and transmits the CESoP Ethernet packets to the OLT. In this way, you can provide CESoP TDM private line service to your client. Figure 13-2 Example network of the CESoP TDM private line service
IP: 10.10.10.11 VLAN: 60 Uplink Port: 0/6/0 UDP port ID: 50048 MAC: 0000-1111-2222
E1 GE
Community
E1
UA5000
GE
IP: 10.10.10.12 VLAN: 60 UDP port ID: 50048 E1 SDH

Ethernet
Enterprise
E1
UA5000
GE
OLT
Enterprise
UA5000
CESoP
Data Plan
Table 13-1 provides the data plan for the CESoP TDM private line service. Table 13-1 Data plan for the CESoP TDM private line service Item VLAN Data l VLAN ID: 60 l Type: Smart VLAN IP address of the COPA card Upstream port The attributes of CES E1 port 10.10.10.11 Port: 0/6/0 l Working Mode: UDT l Line Coding: HDB3 l Clock Type: System
13-6
Issue 03 (2010-11-19)
Item CESoP connection
Data l Remote MAC address: 00-00-11-11-33-33 l Remote IP address: 10.10.10.12/24 l Remote UDP label: 50048 l Local UDP label: 50048 l Jitter Buffer: 1000 l RTP Frame Head: Enable l VLAN: 60
Procedure
1 Configure the VLAN. 1. In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. Choose VLAN from the navigation tree. to display the VLANs. In the On the VLAN tab page, set the filter criteria or click information list, right-click and choose Add from the shortcut menu. In the dialog box that is displayed, set the parameters. l VLAN ID: 60 l Type: Smart VLAN 5. 6. 7. Click Next. Click the Sub Port tab, configure the upstream port in the VLAN, and then set Sub Port to 0/6/0. Click Done.
2. 3. 4.
2 Configure theCOPA card. 1. 2. 3. Choose NE Panel from the navigation tree. Right-click the required shelf in the view in the right pane and choose Frame View from the shortcut menu. Select the card , right-click, and then choose Config Board Property. In the dialog box that is displayed, set the parameters. IP address: 10.10.10.11 4. Click OK.
3 Add a CESoP connection. 1. 2. 3. 4. Choose E1/T1 > CES E1/T1 Port from the navigation tree. On the CES E1 Port tab page, set the filter criteria to display the required CES E1 ports. Select port 0/6/0 from the list, and then click the CESoP Info tab in the lower pane. Right-click the list, and then choose Add CESoP Connection. In the dialog box that is displayed, set the parameters. l Remote MAC address: 00-00-11-11-33-33
l Remote IP address: 10.10.10.12/24 l Remote UDP label: 50048 l Local UDP label: 50048 l Jitter Buffer: 1000 l RTP Frame Head: Enable l VLAN: 60 4 Save the data. 1. In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. On the tab page that is displayed, click Save Data Immediately. Click OK. above the navigation tree, and then choose
2. 3.
----End
Result
After successful configuration of the CESoP TDM private line service, the user can access the upper layer TDM network.
13-8
Issue 03 (2010-11-19)
14 Configuring the Active/Standby Switchover for the Upstream Service
14
Configuring the Active/Standby
Switchover for the Upstream Service
About This Chapter

This topic describes how to configure the card with the active/standby switchover for the upstream service so that the stability of the service is guaranteed. 14.1 Configuring the Active/Standby Switchover for the IPM Upstream The UA5000 adopts the active/standby switchover mechanism to ensure the stability of the service. In addition, the UA5000 is designed with the service protection mechanism for the upstream port. When the UA5000 is disconnected from the upper layer device physically and thus causes service interruption, the UA5000 automatically uses the standby line to carry the Internet access service of users. 14.2 Configuration Example of the Active/Standby Switchover for the IPM Dual Upstream This topic describes how to configure the active/standby switchover for the IPM dual upstream. 14.3 Configuring the Active/Standby Switchover for the AIU Upstream This topic describes how to configure the active/standby switchover for the AIU upstream to ensure continual services.
Issue 03 (2010-11-19)
14-1
14.1 Configuring the Active/Standby Switchover for the IPM Upstream

The UA5000 adopts the active/standby switchover mechanism to ensure the stability of the service. In addition, the UA5000 is designed with the service protection mechanism for the upstream port. When the UA5000 is disconnected from the upper layer device physically and thus causes service interruption, the UA5000 automatically uses the standby line to carry the Internet access service of users.
Prerequisite
l l The active and standby IPM control cards must have been configured and must work in the normal state. The ports of the active IPM control card must correspond to the ports of the standby IPM control card correctly.
Context
The UA5000 provides three checking modes of the active/standby switchover to protect the service of the upstream port. l Port status checking mode: In this mode, the two ports in a protection group or the Tx ports on the two control cards are enabled. The UA5000 checks the port status to determine whether to perform the active/standby switchover. Delay checking mode: In this mode, only one Tx port in the protection group is enabled, and the other port is disabled. If the status of the enabled Tx port is DOWN, the UA5000 disables the Tx port and enables the other Tx port. If the status of the other Tx port is UP, the UA5000 performs the switchover. Otherwise, the UA5000 continues checking. Link Aggregation Control Protocol (LACP) checking mode: In this mode, the UA5000 runs the LACP protocol to implement port protection. When the ports of the active and standby control cards are configured with the link aggregation group (LAG) and work in the active and standby mode, if the LACP status of the standby port of the standby control card is normal and the LACP status of the active port of the active control card is abnormal, the active/standby switchover is performed. 14.1.1 Configuring the Active/Standby Switchover for the IPM Upstream The protection group of an upstream port contains an active port and a standby port. In normal conditions, the active port carries the service. When the link of the active port is faulty, the system automatically switches the service of the active port over to the standby port to ensure normal service transmission and to provide protection for the upstream link. 14.1.2 Configuring Upstream Link Detection This topic describes how to configure upstream link detection.
1.
2.
14.1.1 Configuring the Active/Standby Switchover for the IPM Upstream

The protection group of an upstream port contains an active port and a standby port. In normal conditions, the active port carries the service. When the link of the active port is faulty, the system automatically switches the service of the active port over to the standby port to ensure normal service transmission and to provide protection for the upstream link.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose NE Panel from the navigation tree. Right-click the required shelf in the view in the right pane and choose Frame View from the shortcut menu. 3 Right-click a card in the list and choose IPM Protect Group from the shortcut menu. 4 In the dialog box that is displayed, click Add. 5 In the dialog box that is displayed, configure the parameters. 6 Click OK to return to the previous dialog box. 7 Click Close. ----End
14.1.2 Configuring Upstream Link Detection

This topic describes how to configure upstream link detection.
Context
l l Upstream link detection can be performed on only the active IPMB control card. The active and standby IPMB control cards must have been configured and must work in the normal state.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose NE Panel from the navigation tree. Right-click the required shelf in the view in the right pane and choose Frame View from the shortcut menu. 3 Right-click an active IPMB control card in the list and choose Detect Uplink from the shortcut menu. 4 In the dialog box that is displayed, configure the link switchover mode and click OK. ----End
14.2 Configuration Example of the Active/Standby Switchover for the IPM Dual Upstream
This topic describes how to configure the active/standby switchover for the IPM dual upstream.
Issue 03 (2010-11-19)
14-3
Context
Table 14-1 Data plan for the active/standby switchover for the IPM dual upstream Item Configure the active/standby switchover for the IPM upstream Data Protect type: l Protect type: Port protect group l Work mode: Port status Work: l Frame: 0 l Slot: 2 l Port: 0 Protect: l Frame: 0 l Slot: 3 l Port: 0
Procedure
1 Configure the active/standby switchover for the IPM upstream. 1. In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. Choose NE Panel from the navigation tree. Right-click the required shelf in the view in the right pane and choose Frame View from the shortcut menu. Right-click a card in the list and choose IPM Protect Group from the shortcut menu. In the dialog box that is displayed, click Add. In the Add Port Protect Group dialog box that is displayed, set the parameters as follows: l Protect type: Port protect group l Work mode: Port status l Frame: 0 l Slot: 2 l Port: 0 l Frame: 0 l Slot: 3 l Port: 0 6. 7. Click OK. Click Close.
2. 3. 4. 5.
2 Configure the upstream link detection.

1.
In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. Choose NE Panel from the navigation tree. Right-click the required shelf in the view in the right pane and choose Frame View from the shortcut menu. Right-click an active IPMB control card in the list and choose Detect Uplink from the shortcut menu. In the dialog box that is displayed, configure the link switchover mode and click OK.
2. 3. 4.
----End
14.3 Configuring the Active/Standby Switchover for the AIU Upstream

This topic describes how to configure the active/standby switchover for the AIU upstream to ensure continual services.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose NE Panel from the navigation tree. Right-click the required shelf in the view in the right pane and choose Frame View from the shortcut menu. 3 Right-click an AIU card in the list and choose AIU Protect Group from the shortcut menu. 4 In the dialog box that is displayed, click Add. 5 In the dialog box that is displayed, set related parameters. 6 Click OK. ----End
Issue 03 (2010-11-19)
14-5
15 Configuring the Ethernet OAM Diagnosis
15
About This Chapter
Prerequisite
l l
Configuring the Ethernet OAM Diagnosis
This topic describes the principles, configuration procedure, and configuration example of the Ethernet OAM diagnosis.
The corresponding VLAN must exist. For details, see 2.1 Adding a VLAN. The VLAN must be configured with an upstream port. For details, see 2.2 Configuring the Upstream Port of a VLAN.
Context
With the extension of the Ethernet technology from the carrier network to MAN and WAN, carriers are more concerned about the maintainability of devices. Therefore, the maintenance of Ethernet devices becomes more and more important. The operations, administration and maintenance (OAM) issue of the transmission network is pressing. The 802.1ag connectivity fault management (CFM) provides an end-to-end method for detecting faults. The Ethernet OAM mechanism supported by the 802.1ag CFM covers connectivity check (CC), loopback (LB), link trace (LT), and forward AIS alarms. Figure 15-1 shows the flowchart for configuring the Ethernet OAM diagnosis on the UA5000 (IPMB).
Issue 03 (2010-11-19)
15-1
Figure 15-1 Flowchart for configuring the Ethernet OAM diagnosis
Start
Add a Smart VLAN
Configure Uplink Port of the VLAN
Configure an MD
Configure an MA
Configure an MEP
Configure a remote MEP
Configure the CC sending interval of an MA Enable the CFM gloabl switch
End
15.1 Introduction to the Ethernet OAM This topic describes the basic concepts and principles of the Ethernet connectivity fault management (CFM) and the example network of the Ethernet OAM. The Ethernet OAM mechanism supported by the 802.1ag covers the connectivity check (CC), link trace (LT), and loopback (LB). 15.2 Configuring an MD This topic describes how to configure an MD. Different MDs are maintained by different management entities. 15.3 Configuring an MA
15-2
Issue 03 (2010-11-19)
This topic describes how to add an MA, add devices to the MA, configure the interval for sending CCM packets and the function of checking remote MEPs, check the remote MEPs configured in the MA, and report alarms of detected faults. 15.4 Configuring a Source MEP This topic describes how to create a source MEP to detect the connectivity of a channel in an MA, and how to configure the administrative status, CCM and LTM priority, and CCM sending status for the MEP. 15.5 Enabling the Global CFM Function This topic describes how to set the Ethernet OAM global parameters on the U2000 and apply the parameters to the specified devices. You can configure the Ethernet OAM global parameters in the System Parameter Profile of the U2000. Devices can detect and locate Ethernet faults through the bound System Parameter Profile. 15.6 Configuration Example of the Ethernet OAM Diagnosis This topic provides an example for configuring the Ethernet OAM on the UA5000(IPMB).
Issue 03 (2010-11-19)
15-3
15.1 Introduction to the Ethernet OAM

This topic describes the basic concepts and principles of the Ethernet connectivity fault management (CFM) and the example network of the Ethernet OAM. The Ethernet OAM mechanism supported by the 802.1ag covers the connectivity check (CC), link trace (LT), and loopback (LB).
Context
The basic concepts and principles of the Ethernet CFM are described as follows: 1. Basic concepts: l Maintenance domain (MD): The Ethernet CFM divides a network into a maximum of eight layers. A bridge can have different layers to manage different MDs. A CFM MD consists of bridges, and is a combination of bridges and maintenance levels. MDs come under three layers: user domain (levels 7-5), service provider domain (levels 4-3), and carrier domain (levels 2-0). Different MDs are maintained by different management entities. l Maintenance association (MA): An MD can be divided into multiple MAs. Each MA maps with a service instance (SI) identified by a VLAN in the MD. That is, the MA can be understood as a combination of an MD and a VLAN. (According to the standard, multiple VLANs can map with one SI, and one SI maps with one MA.) l Maintenance point (MP): An MA consists of maintenance points (MPs) that are defined on the ports of bridges. That is, an MP is a combination of a bridge port, a VLAN, and a maintenance level. MPs are classified into two types: maintenance association end point (MEP) and maintenance association intermediate point (MIP). An MEP initiates and responds to CFM messages. An MIP does not initiate CFM messages. It only transparently transmits or responds to CFM messages. 2. Principles of fault detection: l Continuity check messages (CCMs) are used to detect Ethernet faults. Each MEP actively sends CCM packets at regular intervals. The CCM packets are copied to the multicast addresses. All the MIPs and MEPs in the MD can receive the CCM packets but need not respond. When an MEP receives CCM packets from other MEPs, it sets up and maintains an MEP CCM database. The database records the MEP IDs, MAC addresses of the MEPs, and the mappings between the MEPs and the receiving ports. The database also records the information about other MEPs in the MA. If the MEP does not receive CCM packets from another MEP for three successive times, the MEP reports a fault. l Loss of CCM packets may be caused by a link fault, a switched network fault, or wrong configurations between two MEPs. The NMS can use other methods, such as loss of physical layer signals, instead of CCM packets, to detect the link faults. But in this case, the NMS cannot detect the non-link faults, such as switched network faults or wrong configurations. After a fault is discovered through CCM packets, you can use LB or LT to locate the fault (for example, in the switched network). l CCM packets can detect not only the link faults and switched network faults, but also the service configuration errors (such as unmatched MA names), repeated MEP configurations (such as repeated MEP names), undesired MEPs, loopback (repeated serial numbers), data loss, and data corruption (such as wrong checksum). 3.
15-4
Alarm mechanism: There are four types of alarms.

l Cross-connection alarm: After an MEP on a bridge receives a CCM packet, the MEP checks whether certain configuration (including the type and length of the MD name; the MD name; the type and length of the MA name; and the MA name) of the peer MEP as carried by the CCM packet is completely the same as the local configuration. If the configurations are different, the MEP reports a cross-connection alarm. l Loss-of-CCM alarm: If an MEP on a bridge does not receive a CCM packet from a remote MEP in a specific period (3.5 times the sending interval), the MEP reports a loss-of-CCM alarm. l Error alarm: After an MEP on a bridge receives a CCM packet, the MEP compares the MEP information in the received CCM packet with the configuration information about the remote MEP, including the interval for sending CCM packets. If the information does not match, the MEP reports an error alarm. l RDI alarm: If a local MEP does not receive CCM packets from its remote MEP, the local MEP sends a CCM packet with an RDI bit. When another MEP receives the CCM packet with the RDI bit, the MEP reports an RDI alarm. 4. LT principle: l The LT helps to check the MIP path between two MEPs. A link trace message (LTM) contains a known multicast address, but is not multicasted. The LTM contains additional information indicating the MAC address of the destination MEP. When the LTM is forwarded by MIPs to the destination MEP in unicast mode, each MIP sends a link trace reply (LTR) to the source MEP. In this way, the source MEP learns the MIPs along the path to the destination MEP and records their MAC addresses. 5. LB principle: l LB helps an MEP to locate faults in an MA. LB uses the unicast MAC address of an MEP or MIP that is discovered by the CC or LT. The source MEP creates a loopback message (LBM) containing the index of the destination MEP, sends the LBM, and starts the timer. After receiving the LBM, the destination MEP sends an LBR to the source MEP. The loopback test succeeds. If the timer of the source MEP expires, the loopback test fails. Figure 15-2 shows the example network of the Ethernet OAM on the UA5000(IPMB). The link between UA5000(IPMB)_A and UA5000(IPMB)_B uses the Ethernet OAM mechanism to detect link faults. Both UA5000(IPMB)_A and UA5000(IPMB)_B are configured with a local MEP and a remote MEP. The local MEP ID of UA5000(IPMB)_B is the same as the remote MEP ID of UA5000(IPMB)_A. The remote MEP ID of UA5000(IPMB)_B is the same as the local MEP ID of UA5000(IPMB)_A. Figure 15-2 Example network of the Ethernet OAM
Issue 03 (2010-11-19)
15-5
15.2 Configuring an MD
This topic describes how to configure an MD. Different MDs are maintained by different management entities.
Prerequisite
l l l The corresponding VLAN must exist. For details, see 2.1 Adding a VLAN. The VLAN must be configured with an upstream port. For details, see 2.2 Configuring the Upstream Port of a VLAN. You can perform this operation only after the CFM function is enabled globally.
Context
l l l l The system supports three MDs. MDs with the same name format and the same name cannot be created on the same device, but can be created on different devices. MDs of the same level cannot be created on the same device, but can be created on different devices. The total length of the names of an MA and the corresponding MD must be less than or equal to 43 characters.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose ETH OAM from the navigation tree. 3 Click the Maintenance Domain tab, and set the filter criteria to display the required MDs. 4 Right-click in the list and choose Add from the shortcut menu. 5 In the dialog box that is displayed, set MD Name Format, MD Name, Level and MHF Creation Rule as follows.
6 Click OK. ----End

15.3 Configuring an MA
This topic describes how to add an MA, add devices to the MA, configure the interval for sending CCM packets and the function of checking remote MEPs, check the remote MEPs configured in the MA, and report alarms of detected faults.
Prerequisite
l l l The corresponding VLAN must exist. For details, see 2.1 Adding a VLAN. The VLAN must be configured with an upstream port. For details, see 2.2 Configuring the Upstream Port of a VLAN. The MD must be configured. For details, see 15.2 Configuring an MD.
Context
l l l l l You can perform this operation only after the CFM function is enabled globally. Each MD can be configured with up to 48 MAs and the system supports up to 48 MAs. That is, if you configure 48 MAs in an MD, no more MAs can be configured in other MDs. The MA must belong to an MD. Do not create an MA that is the same as an existing one. The MAs in the same MD cannot be associated with the same VLAN. The total length of the names of an MA and the corresponding MD must be less than or equal to 43 characters.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose ETH OAM from the navigation tree. 3 Click the Maintenance Association tab, and set the filter criteria to display the required MAs. 4 Right-click in the list and choose Add from the shortcut menu. 5 In the dialog box that is displayed, set MD Name, MA Name Format, MA Name, and CC Interval as follows.
6 Click OK.
7 Right-click MA1 and choose Configure from the shortcut menu. 8 In the dialog box that is displayed, set MHF Creation Rule, Remote MEP Detection Function and Associated VLAN as follows.
9 Click OK. ----End
15.4 Configuring a Source MEP

This topic describes how to create a source MEP to detect the connectivity of a channel in an MA, and how to configure the administrative status, CCM and LTM priority, and CCM sending status for the MEP.
Prerequisite
l l l l The corresponding VLAN must exist. For details, see 2.1 Adding a VLAN. The VLAN must be configured with an upstream port. For details, see 2.2 Configuring the Upstream Port of a VLAN. The MD must be configured. For details, see 15.2 Configuring an MD. The MA must be configured. For details, see 15.3 Configuring an MA.
Context
An MEP is the end point of a maintenance channel. Ethernet OAM depends on the MEPs at both ends of a channel to check the connectivity. Therefore, the MEPs must be created. After creating the MEPs, you can use them to check the connectivity of a channel in an MA. l l l The MEP takes effect only after the administrative function is enabled. The MEP can send CCM packets at regular intervals to check the connectivity of a channel only after the CCM packet sending function is enabled successfully. After the CCM and LTM priority is successfully configured, the system discards the packets with lower priority in case of congestion.
15-8
Issue 03 (2010-11-19)
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose ETH OAM from the navigation tree. 3 Click the Maintenance Association tab, and set the filter criteria to display the required MAs. 4 Select an MA, and click the Source MEP ID Info tab in the lower pane. 5 Right-click in the list and choose Add from the shortcut menu. 6 In the dialog box that is displayed, set MEP ID, Interface Info, Interface Direction, VLAN TAG1, VLAN TAG2 and CCM And LTM Priority as follows.
7 Click OK. 8 Right-click the added source MEP and choose Configure from the shortcut menu. 9 In the dialog box that is displayed, enable the Administrative Status and CC Sending Status of the MEP and set CCM And LTM Priority, Alarm Waiting Time and Alarm Recovery Time as follows.
Issue 03 (2010-11-19)
15-9
10 Click OK. ----End
15.5 Enabling the Global CFM Function

This topic describes how to set the Ethernet OAM global parameters on the U2000 and apply the parameters to the specified devices. You can configure the Ethernet OAM global parameters in the System Parameter Profile of the U2000. Devices can detect and locate Ethernet faults through the bound System Parameter Profile.
Context
When the global CFM function is enabled, the CFM packets are captured, and the functions of CC, LB and LT are enabled. When the global CFM function is disabled, the CFM packets are not captured, and the functions of CC, LB, and LT are disabled. The system parameter profile is a collection of system parameters, such as ETH OAM parameters and other parameters. After a system parameter profile is applied to a device successfully, the parameters in the profile overwrite the original parameters on the device. This may affect the services of the device. Therefore, the system parameter profile must be applied to the device before service provisioning.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 On the tab page that is displayed, choose NE Properties > Protocol > ETH OAM from the navigation tree. 3 In the parameter configuration area in the right pane, set the global parameters of the Ethernet OAM devices, including the multicast MAC base address that is used to send CC/LT packets, and then set Global remote MEP test and Global CFM switch.
15-10
Issue 03 (2010-11-19)
4 Click Apply. ----End
15.6 Configuration Example of the Ethernet OAM Diagnosis

This topic provides an example for configuring the Ethernet OAM on the UA5000(IPMB).
Prerequisite
l l The example network as shown in Figure 15-3 must be complete. The network devices and lines must be in the normal state.
Example Network
Figure 15-3 shows the example network of the Ethernet OAM on the UA5000(IPMB). The link between UA5000(IPMB)_A and UA5000(IPMB)_B uses the Ethernet OAM mechanism to detect link faults. Both UA5000(IPMB)_A and UA5000(IPMB)_B are configured with a local MEP and a remote MEP. The local MEP ID of UA5000(IPMB)_B is the same as the remote MEP ID of UA5000(IPMB)_A. The remote MEP ID of UA5000(IPMB)_B is the same as the local MEP ID of UA5000(IPMB)_A. Figure 15-3 Example network of the Ethernet OAM
Data Plan
Table 15-1 provides the data plan for the Ethernet OAM on the UA5000(IPMB).
Issue 03 (2010-11-19)
15-11
Table 15-1 Data plan for the Ethernet OAM Item UA5000(IPMB)_A Data l Port: 0/2/0 l Smart VLAN: 100 l MD Name Format: character string type l MD Name: MD1 l Level: 3 l MA Name Format: character string type l MA Name: MA1 l Remote MEP check: Enable l Associated VLAN: 100 l MEP ID: 2 l Interface Direction: DOWN l CCM and LTM Priority: 7 l Administrative Status: enable l CC Sending Status: enable l Alarm Waiting Time: 2500 l Alarm Recovery Time: 10000 UA5000(IPMB)_B l Port: 0/2/1 l Smart VLAN: 100 l MD Name Format: character string type l MD Name: MD1 l Level: 3 l MA Name Format: character string type l MA Name: MA1 l Remote MEP check: Enable l Associated VLAN: 100 l MEP ID: 2 l Interface Direction: UP l CCM and LTM Priority: 7 l Administrative Status: enable l CC Sending Status: enable l Alarm Waiting Time: 2500 l Alarm Recovery Time: 10000
15-12
Issue 03 (2010-11-19)
NOTE
l Configure the remote MEP of UA5000(IPMB)_A on UA5000(IPMB)_B in the same way as configuring the MEP of UA5000(IPMB)_A. l This topic considers the configuration on UA5000(IPMB)_A as an example.
Procedure
1 Add a VLAN and configure the upstream port of the VLAN. 1. In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. Choose VLAN from the navigation tree. Right-click in the list and choose Add from the shortcut menu. In the dialog box that is displayed, set the related parameters as follows: l VLAN ID: 100 l Type: Smart VLAN l Attribute: Common 4. Click Next and select port 0/2/0 as the upstream port. Click Done. 2 Configure the MD. 1. 2. 3. 4. Choose ETH OAM from the navigation tree. Click the Maintenance Domain tab, and set the filter criteria to display the required MDs. Right-click in the list and choose Add from the shortcut menu. In the dialog box that is displayed, set the device name and the name format, name, and level of the MD as follows, and then click OK. l MD name format: character string type l MD name: MD1 l Level: 3 3 Configure the MA. 1. 2. 3. Click the Maintenance Association tab, and set the filter criteria to display the required MAs. Right-click in the list and choose Add from the shortcut menu. In the dialog box that is displayed, set the name format, name and associated VLAN of the MA as follows, and then click OK. l MD name: MD1 l MA name format: character string type l MA name: MA1 4. 5. Right-click the added MA1 and choose Configure from the shortcut menu. In the dialog box that is displayed, set the parameters as follows and click OK. l Remote MEP check: Enable l Associated VLAN: 100 4 Configure the MEP ID. 1.
Issue 03 (2010-11-19)
2. 3.
Click the Maintenance Association tab, set the filter criteria to display the records.
2. 3. 1. 2. 3.
Select the added MA1 and click the MEP ID Info tab in the lower pane. Right-click in the list and choose Add from the shortcut menu. In the dialog box that is displayed, set MEP ID to 2. Click the Maintenance End Point tab, and select UA5000(IPMB) from the Device Type drop-down list. Right-click in the list and choose Add from the shortcut menu. In the dialog box that is displayed, set the name of the MA, the name and identifier of the MEP, the port information, and the port direction as follows, and then click OK. l MEP ID: 2 l Interface Info: 0/2/0 l Interface Direction: UP l CCM and LTM Priority: 7
5 Configure the MEP.
4. 5.
Right-click the added MEP1 and choose Configure from the shortcut menu. In the dialog box that is displayed, set the parameters as follows and click OK. l Administrative Status: enable l CCM and LTM Priority: 7 l CC Sending Status: enable l Alarm Waiting Time: 2500 l Alarm Recovery Time: 10000
6 Enable the global CFM function. 1. In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. On the tab page that is displayed, choose NE Properties > Protocol > ETH OAM from the navigation tree. Enable Global remote MEP test and Global CFM switch. Click Apply.
2. 3. 4.
----End
Result
After successful configuration, you can query the statistics of the packets on UA5000(IPMB) _A or UA5000(IPMB)_B. The number of the transmitted CCM packets and the number of the received CCM packets are not zero.
15-14
Issue 03 (2010-11-19)
16 Configuring the BFD Network Monitoring
16
About This Chapter
Configuring the BFD Network Monitoring
The bidirectional forwarding detection (BFD) is used to test the link status between two devices quickly. When the main channel is faulty, the UA5000(IPMB) can switch the service to the standby channel, and thus to increase the reliability of the service and the inband maintenance channel. 16.1 Introduction to BFD The bidirectional forwarding detection (BFD) is used to detect the link status between two devices quickly. When the main channel is faulty, the UA5000(IPMB) switches the service to the standby channel, and thus to increase the reliability of the service and the inband maintenance channel. 16.2 Setting the BFD Session Parameters Before the detection of the link fault, the BFD session between the two ends of the channel need to be set up and the peer IP address need to be bound to the local VLAN.
Issue 03 (2010-11-19)
16-1
16.1 Introduction to BFD

The bidirectional forwarding detection (BFD) is used to detect the link status between two devices quickly. When the main channel is faulty, the UA5000(IPMB) switches the service to the standby channel, and thus to increase the reliability of the service and the inband maintenance channel.
Prerequisite
The global BFD function is enabled. For details, see 2.8.6 Setting BFD Parameters. The VLAN is set up. For details, see 2.1 Adding a VLAN.
Context
l l l Currently, BFD only supports the detection of the static route faults. Up to 32 BFD sessions are supported. When the route is bound to a BFD, select the link according to the status of the BFD and the priority of the route; when the route is not bound to a BFD, select the link only according to the priority of the route. To avoid the route switching to the route with higher priority but not bound to a BFD, if there is another route bound to the BFD going to the same destination, you must reduce the priority of the route that is not bound to the BFD before unbinding the route from the port.
16.2 Setting the BFD Session Parameters

Before the detection of the link fault, the BFD session between the two ends of the channel need to be set up and the peer IP address need to be bound to the local VLAN.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 Choose Protocol > BFD from the navigation tree. 3 In the information list, right-click and choose Add from the shortcut menu. 4 In the dialog box that is displayed, set the BFD session parameters.
16-2
Issue 03 (2010-11-19)
5 Click OK. ----End
Issue 03 (2010-11-19)
16-3
17 Detecting the Network
17
About This Chapter
Detecting the Network
This topic describes how to check the connectivity of a network and whether the host is reachable, and how to check all gateways passed by data packets sent from a source host to the destination host. In addition, this operation helps you to locate network faults and log in to the device through the network remotely to configure and maintain the device. 17.1 Telnet This topic describes how to log in to a device through the network remotely to configure and maintain the device. 17.2 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, perform this operation. 17.3 Tracert This topic descries how to test the route that is passed by data packets sent from a source host to the destination host. To track the route that is passed by data packets and locate the network fault, perform this operation. After running the ping command to test the network and detect a fault, you can run the tracert command to locate the fault on the network. 17.4 SSH The secure shell (SSH) guarantees the security of the network communications by providing authentication, encryption, and authorization. When users telnet the router through an insecure network, SSH offers secure information guarantee and powerful authentication to protect the device against attacks such as IP address spoofing and interception of the plain text password.
Issue 03 (2010-11-19)
17-1
17.1 Telnet
This topic describes how to log in to a device through the network remotely to configure and maintain the device.
Prerequisite
Make sure that port 9811 between the U2000 server and clients is enabled before you telnet a device.
Procedure
1 In the navigation tree or the topology view, select a required device. 2 Right-click and choose Tool > Telnet from the shortcut menu. After you successfully telnet to the remote server or device in the network, you can operate the device in command lines. ----End
17.2 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, perform this operation.
Context
During the ping process, the source host sends the ICMP ECHO-REQUEST packets to the destination host. If the network connection between the source host and the destination host is normal, after receiving the ICMP ECHO-REQUEST packets, the destination host responds to the source host with the ICMP ECHO-REPLY packets.
Procedure
1 In the navigation tree or the topology view, select a required device. 2 Right-click and choose Tool > Ping from the shortcut menu. 3 In the dialog box that is displayed, select Ping or Continual Ping and click Start.
NOTE
l If the operation is successful, it indicates that the destination host is reachable. In the Result area, the system displays the information indicating that the network connectivity is in the normal state. The displayed information includes the number of sent packets, number of received response packets, packet loss ratio, and minimum, maximum, and average values of the response time. l If the operation fails, it indicates that the destination host is not reachable. The system fails to check the network connectivity or line failure. The system displays the message Request time out.
----End
17.3 Tracert
This topic descries how to test the route that is passed by data packets sent from a source host to the destination host. To track the route that is passed by data packets and locate the network
fault, perform this operation. After running the ping command to test the network and detect a fault, you can run the tracert command to locate the fault on the network.
Context
The execution process of the tracert command is as follows: l l l l l The source host sends a packet with TTL 1. 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 with TTL 2. 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 with TTL 3. 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. 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.
Procedure
1 In the navigation tree or the topology view, select a required device. 2 Right-click and choose Tool > Tracert from the shortcut menu. ----End
17.4 SSH
The secure shell (SSH) guarantees the security of the network communications by providing authentication, encryption, and authorization. When users telnet the router through an insecure network, SSH offers secure information guarantee and powerful authentication to protect the device against attacks such as IP address spoofing and interception of the plain text password.
Procedure
1 In the navigation tree or the topology view, select a required device. 2 Right-click and choose Tool > SSH from the shortcut menu. 3 In the dialog box that is displayed, set the parameters. 4 Click OK. ----End
Issue 03 (2010-11-19)
17-3
18 Saving the Data
18
About This Chapter
Saving the Data
After saving the data to the flash memory of a device, you can query the data information to maintain and manage the device. 18.1 Setting the Parameters for Saving the Data You can configure the auto save period of the data through enabling the auto save function of the device. The U2000 automatically saves the data to the flash memory of the device according to the configured period. Through the U2000, you can periodically maintain and manage the device according to the saved data information. 18.2 Immediately Enabling Data Saving Function This topic describes how to immediately enable the auto save function of a device to save the current data of the device in time.
Issue 03 (2010-11-19)
18-1
18 Saving the Data
18.1 Setting the Parameters for Saving the Data

You can configure the auto save period of the data through enabling the auto save function of the device. The U2000 automatically saves the data to the flash memory of the device according to the configured period. Through the U2000, you can periodically maintain and manage the device according to the saved data information.
Context
NOTE
The absolute period and relative period of the device are based on the time of the site where the device is located.
Procedure
1 In the Main Topology, double-click the required UA5000(IPMB) in the Physical Root navigation tree; or right-click the required UA5000(IPMB) and choose NE Explorer from the shortcut menu. 2 On the tab page that is displayed, choose NE Properties > Auto Save Configuration from the navigation tree. 3 In the right pane, select the Enable Automatic Save check box, and then set the Period parameter for saving the data.
NOTE
Period: The data is automatically saved at an interval. For example, if the Period parameter is set to 00d 05h 31m, the data is automatically saved every other 331 minutes.
4 Click Apply. ----End
18.2 Immediately Enabling Data Saving Function

This topic describes how to immediately enable the auto save function of a device to save the current data of the device in time.
Context
CAUTION
l This operation is applicable to only the device that supports the SNMP protocol. l After being enabled immediately, the automatic saving function cannot be manually stopped. Do not power off or reset the device before the data is saved. Otherwise, the data saved to the flash memory is damaged.
18-2
Issue 03 (2010-11-19)
18 Saving the Data
Procedure
1 In the Main Topology, choose the required UA5000(IPMB) from the Physical Root navigation tree, right-click, and then choose Save Data Immediately from the shortcut menu. 2 In the dialog box that is displayed, click OK. ----End
Issue 03 (2010-11-19)
18-3
19 Synchronization
19
About This Chapter
Synchronization
This topic describes how to synchronize the NE data, NE time, NE alarms and system parameter profile so that the data of the NE and the data on the U2000 are the same 19.1 Synchronizing the NE Data This topic describes how to synchronize the device panel data and service data on the U2000 with that of the NE, which facilitates the centralized maintenance and management. 19.2 Synchronizing the NE Time This topic describes how to synchronize the NE time with the U2000 time to ensure that the time when the NE reports the information is correct. 19.3 Synchronizing NE Alarms This topic describes how to synchronize NE alarms. After the communication between the U2000 and the device recovers or the U2000 restarts, the alarms generated on the device are not reported to the U2000 in time. This results in the inconsistency of the alarm status between the U2000 and the device. In this case, you need to synchronize the alarms. You can synchronize the alarms manually, or enable the automatic synchronization. This ensures that the U2000 monitors the actual running status of the device. 19.4 Synchronizing the System Parameter Profile You can perform this operation to synchronize the system parameter profile that is modified at the global side to the device to maintain the consistency of the parameters in the system parameter profile.
Issue 03 (2010-11-19)
19-1
19 Synchronization
19.1 Synchronizing the NE Data

This topic describes how to synchronize the device panel data and service data on the U2000 with that of the NE, which facilitates the centralized maintenance and management.
Prerequisite
The FTP, SFTP, or TFTP server must be configured and the FTP, SFTP, or TFTP service must be enabled.
Context
l l During the operation on the U2000, the data of the NE and the data on the U2000 must be the same. After the data of the NE is configured and the NE works in the normal state, synchronize the data on the U2000 with that of the NE manually. When an error occurs to the NE data, check whether the NE data saved on the U2000 is correct. If it is correct, download the data from the U2000 to the NE. In this case, the data of the NE is restored.
Procedure
l In the Main Topology, choose the required UA5000(IPMB) from the Physical Root navigation tree, right-click, and then choose Synchronize NE Data from the shortcut menu.
----End
19.2 Synchronizing the NE Time

This topic describes how to synchronize the NE time with the U2000 time to ensure that the time when the NE reports the information is correct.
Context
l l The U2000 delivers the system time automatically when a device goes online. After synchronizing the NE time, do not change the system time of the U2000 frequently.
Procedure
l In the Main Topology, select the required UA5000(IPMB) from the Physical Root navigation tree, right-click, and then choose Set NE Time from the shortcut menu.
----End
19.3 Synchronizing NE Alarms

This topic describes how to synchronize NE alarms. After the communication between the U2000 and the device recovers or the U2000 restarts, the alarms generated on the device are not reported to the U2000 in time. This results in the inconsistency of the alarm status between the U2000 and the device. In this case, you need to synchronize the alarms. You can synchronize the alarms manually, or enable the automatic synchronization. This ensures that the U2000 monitors the actual running status of the device.
19 Synchronization
Procedure
l In the Main Topology, choose the required UA5000(IPMB) from the Physical Root navigation tree, right-click, and then choose Synchronize Current Alarms from the shortcut menu. By manual alarm synchronization, all alarms generated by NE are synchronized.
----End
19.4 Synchronizing the System Parameter Profile

You can perform this operation to synchronize the system parameter profile that is modified at the global side to the device to maintain the consistency of the parameters in the system parameter profile.
Context
To synchronize the system parameter profile, perform this operation.
Procedure
l Navigation path: 1. 2. Choose View > Main Topology from the main menu. On the Physical Root navigation tree on the Main Topology tab page, select the required UA5000(IPMB), right-click, and then choose Synchronize System Parameter Profile.
----End
Issue 03 (2010-11-19)
19-3
20 File Operations
20
About This Chapter
File Operations
By means of file operations, you can save the records as a file, preview the file printing effect, and print the file. In this case, you can save and analyze the relevant information of the U2000. 20.1 Saving Records as a File This topic describes how to save records as a CVS file, a text file, an xls file, or an HTM (HTML) file. In this case, you can use the records in different file formats. 20.2 Previewing the File Printing Effect This topic describes how to preview the file printing effect so that you can adjust the page settings before printing. 20.3 Printing You can print out the records in the U2000 information list to keep the related information of the U2000 and analyze it.
Issue 03 (2010-11-19)
20-1
20 File Operations
20.1 Saving Records as a File

This topic describes how to save records as a CVS file, a text file, an xls file, or an HTM (HTML) file. In this case, you can use the records in different file formats.
Context
This topic considers VLAN as an example. For other subjects, the steps are the same but the navigation path is different.
Procedure
4 In the information list, right-click and choose File > Save As from the shortcut menu. 5 In the dialog box that is displayed, set the parameters. l Set Start Row and End Row. l Click next to File Name and set the path for saving the file, the filename, the file type and encoding. 6 Click OK. ----End
20.2 Previewing the File Printing Effect

This topic describes how to preview the file printing effect so that you can adjust the page settings before printing.
Context
Procedure
4 Right-click in the list and choose File > Print Preview from the shortcut menu.
20 File Operations
5 In the dialog box that is displayed, set Start Row and End Row, click OK. 6 In the dialog box that is displayed, preview the file printing effect, or adjust the page settings according to the requirements. Click Close to close the current dialog box, or click Print to print the file. ----End
20.3 Printing
You can print out the records in the U2000 information list to keep the related information of the U2000 and analyze it.
Context
Procedure
4 Right-click in the list and choose File > Print from the shortcut menu. 5 In the dialog box that is displayed, set the parameters. 6 Click OK. ----End
Issue 03 (2010-11-19)
20-3
21 Remote Maintenance Guide
21
About This Chapter
Remote Maintenance Guide
This topic describes the tasks of maintaining the UA5000(IPMB) software through the U2000, and the reference standard, operation guide, exception handling, and command reference of the tasks. 21.1 Monitoring Critical and Major Alarms of NEs It is recommended that you check whether unhandled critical and major alarms persist in the system every day. This operation helps timely detect and solve the problems that may occur when the NEs are running. 21.2 Measuring the CPU Usage of a Board It is recommended that you measure the CPU usage rat of each board once ever week to rectify the fault of the board whose CPU usage is not in the normal range. This helps you to learn the running status of the boards in time, rectify the capacity fault, and prevent the potential security risks (such as the DoS attack) during the running of the boards. 21.3 Measuring the Performance of an Upstream Ethernet Port It is recommended that you measure the performance of the upstream Ethernet port once every week. This operation ensures that the services on the upstream Ethernet port are normal and reliable. 21.4 Measuring the Usage of NE Resources This topic describes how to measure the resource usage of the NE. You can query the NE information, such as the number, software version, type, MAC address, physical location, and running status. 21.5 Checking the NE User Level It is recommended that you check whether the allocation of the level of the user who configures NEs is correct once every month. This operation ensures that the allocated user level can be the same as the user level that is planned and deployed, and that the user level meets the requirement of NE maintenance. 21.6 Changing the Password of an NE User To ensure the security of an account, it is recommended that you change the password of an NE user periodically instead of using the same password for a long period during maintenance. 21.7 Saving, Backing Up, and Restoring NE Data
The topic describes how to save and back up NE data and restore NE data when an NE fails to be upgraded.
21-2
Issue 03 (2010-11-19)
21.1 Monitoring Critical and Major Alarms of NEs

It is recommended that you check whether unhandled critical and major alarms persist in the system every day. This operation helps timely detect and solve the problems that may occur when the NEs are running.
Prerequisite
The hardware for monitoring NE alarms must be configured, such as an environment monitoring unit (EMU) and sensors.
Context
l After setting the default profile, choose Fault > Browse Current Alarm from the main menu to display the required alarm information directly. For information on how to set and change the default profile, see Setting the Default Profile. You can set the policies for defining alarms according to the extent that the alarms are concerned and the actual requirement, including setting alarm names, function classifications, and alarm severity. For details, see Configuring the Policy of Redefining Alarms and Events. A great number of alarms may be generated during the repair, test, and deployment of devices. In this case, you can mask the alarms that are irrelevant. In this manner, the alarms are not displayed or saved on the U2000. For details, see Configuring the Policy of Masking Alarms and Events.
Reference Standard
You can determine the alarm severity according to colors of the alarm legends. Generally, the critical and major alarms should not persist in the system. The following table lists the alarm legends and provides the meanings of the legends. Legend Color Red Orange Yellow Blue Alarm Severity Critical Major Minor Warning
Procedure
1 Choose Fault > Browse Current Alarm from the main menu. Then, the Filter dialog box is displayed.
Issue 03 (2010-11-19)
21-3

NOTE
l If you already set the default template for the current alarms, the alarms that meet the default template criteria are directly displayed, without the displaying of the Filter dialog box. l You can choose Template > New in the lower pane to create an alarm profile and set the device alarm parameters. You can also choose Template > Open to query the device alarms by selecting the new alarm profile.
2 On the Basic Setting tab, set the parameters required for querying alarms, such as the alarm name, severity, status, and type. These parameters are optional.
3 On the Alarm Source tab, set the alarm source information for querying alarms. In the Select Mode area, set the mode for filtering alarms. l l If All objects is selected, it indicates that alarms are not filtered and all alarms of the alarm source are queried. If Custom is selected, click Add to filter the concerned alarm source according to Object below NE and Object Group.
4 Click OK to display the required critical and major alarms. ----End
Exception Handling
l Select a fault alarm that is not recovered. The alarm information is displayed in Alarm Details in the lower pane and the cause of the alarm and handling suggestions are displayed in Handling Suggestion. Handle the alarm according to the suggestions.
21-4
Record the critical alarms that occur frequently at recent time and their recovery information. Handle the alarms according to the cause and handling suggestions, and analyze potential risks that may exist in the system. If the fault persists, contact Huawei technical support engineers. For details, see How to Obtain Technical Support from Huawei.
NOTE
For an alarm that is handled successfully, it is recommended that you record the detailed handling measures, which helps locate and troubleshoot the similar faults that occur. To enter the maintenance experience, select the alarm, right-click, and then choose Experience.
Related Commands
To... Query the alarm history Query the basic information about alarms Query the alarm configuratio n Query the alarm statistics Query the information about the existing alarms in the system Run the Command... display alarm history display alarm list In... User mode User mode
display alarm configuration
User mode
display alarm statistics
User mode
display alarm active
Privilege mode
21.2 Measuring the CPU Usage of a Board

It is recommended that you measure the CPU usage rat of each board once ever week to rectify the fault of the board whose CPU usage is not in the normal range. This helps you to learn the running status of the boards in time, rectify the capacity fault, and prevent the potential security risks (such as the DoS attack) during the running of the boards.
Prerequisite
l l You must have Create a Performance Measurement Task. If the attributes of NE resources change, you need to perform synchronize to keep the data of the NE and performance management module the same and then perform query . Otherwise , the collection of performance data is abnormal. The procedure of synchronizing information is as follows:
Issue 03 (2010-11-19)
1. 2.
On the Main Topology tab, select an NE from the Physical Root navigation tree, right-click, and then choose Synchronize NE Data. Choose Performance > Performance Monitor Management from the main menu. In the Performance Monitoring Management tab, right-click the monitoring instance, and select Synchronization Resource.
Context
Only the control boards and service boards support this operation.
Reference Standard
l l The CPU usage ranges from 0% to 100%. The CPU usage of a board that runs normally does not exceed 70%. The high CPU usage of a board occurs only when the board data is being written to the flash memory of the control board or is being saved. The high CPU usage usually lasts less than 60s.
Procedure
1 Choose Performance > Browse History Performance Data from the main menu. 2 Choose Performance Management > Card > Access NE Card > Board Health from the navigation tree. 3 Click Filter. The dialog is displayed. The resources and the corresponding indicators associated with the selected resources is displayed.
NOTE
If the query profile is created, click Template > Query by Template. In the dialog box that is displayed, select the required profile, and then import the profile to query the performance statistics.
4 In the Show Type drop-down list, select the graph type as Single Resource Graph. 5 In the area, select the NE type. In the Available Resources area in the right pane, select the resource name. 6 Click , to move the resources to the Selected Resources area.
7 Click
in the right side of the window to expand the Option area box.
8 In the buttom of the pane, select the indicators for the selected resources.
NOTE
Maximum 10 indicators can be selected at a time.
9 Select the Option check box and in the Time drop-down list, select the time period. Time period can be set as Recent 1 hour, Recent 12 hours, Recent 1 day, Recent 1 week, Recent 1 month, Recent 1 year, or Custom Define. 1. 2.
21-6
Select Custom Define, and click time period can be 1 year. Click OK.
to select the start and end time period. The maximum
Issue 03 (2010-11-19)
NOTE
Start time period should be earlier than end time period.
10 In the Granularity drop-down list, select the granularity period. Based on the time period, granularity can be one of the following: l Recent 1 hour: 5 minutes, 10 minutes, 15 minutes, and 30 minutes. l Recent 12 hours: 5 minutes, 10 minutes, 15 minutes, and 30 minutes, 1 hour. l Recent 1 day: 5 minutes, 10 minutes, 15 minutes, and 30 minutes, 1 hour. l Recent 1 week: 1 hour, 1 day. l Recent 1 month: 1 day. l Recent 1 year: 1 day. l Custom Define: 5 minutes, 10 minutes, 15 minutes, 30 minutes, 1 hour and 1 day.
NOTE
For custom define, the granularity can be selected based on the time period selected.
11 Optional: Click Advance, and set the filter conditions for the indicators. 1. 2. 3. In the Logic Type drop-down list, select the logic type as AND or OR. Select the Operator and set the Value for the corresponding indicators. Operator can be set as =, <, >, <=, >=, or !=. Click OK.
12 Optional: Click Save as Query Template to save a new or an existing template as a new template. 13 Optional: Click Cancel to cancel the operation. 14 Click OK to get the performance data based on the filter conditions set for one graph one resource. ----End
Exception Handling
l l If the CPU usage of a board is temporarily over-high, there is no need to proceed. If the CPU usage of a board is frequently over-high, check the following items: Whether the data configuration of the device is proper. If the data configuration is improper, it is recommended that you decrease the number of users or increase the capacity of the system. Whether the networking is proper and whether a larger number of broadcast packets are generated due to the existing loop networks. Whether the DoS attack exists, which may lead to the high CPU usage. The solution is to enable the anti-DoS attack function. l If the fault persists, contact Huawei technical support engineers. For details, see How to Obtain Technical Support from Huawei.
Issue 03 (2010-11-19)
21-7
Related Commands
To... Query the CPU usage of a board Run the Command... display cpu In... Privilege mode
21.3 Measuring the Performance of an Upstream Ethernet Port

It is recommended that you measure the performance of the upstream Ethernet port once every week. This operation ensures that the services on the upstream Ethernet port are normal and reliable.
Prerequisite
l l You must have Create a Performance Measurement Task. If the attributes of NE resources change, you need to perform synchronize to keep the data of the NE and performance management module the same and then perform query . Otherwise , the collection of performance data is abnormal. The procedure of synchronizing information is as follows: 1. 2. On the Main Topology tab, select an NE from the Physical Root navigation tree, right-click, and then choose Synchronize NE Data. Choose Performance > Performance Monitor Management from the main menu. In the Performance Monitoring Management tab, right-click the monitoring instance, and select Synchronization Resource.
Reference Standard
In the statistics of the upstream Ethernet port, a small number of frames with cyclical redundancy check (CRC) errors and a few packet loss errors exist and the traffic transmission is stable.
Procedure
1 Choose Performance > Browse History Performance Data from the main menu. 2 Choose Performance Management > Port > Access Ethernet Port > Ethernet Port from the navigation tree. 3 Click Filter. The dialog is displayed. The resources and the corresponding indicators associated with the selected resources is displayed.
NOTE
If the query profile is created, click Template > Query by Template. In the dialog box that is displayed, select the required profile, and then import the profile to query the performance statistics.
4 In the Show Type drop-down list, select the graph type as Single Resource Graph.
21-8
Issue 03 (2010-11-19)
5 Click
in the right side of the window to expand the Available Resources area box.
6 In the area, select the NE type. In the Available Resources area in the right pane, select the resource name. 7 Click , to move the resources to the Selected Resources area.
8 Click
in the right side of the window to expand the Option area box.
9 In the buttom of the pane, select the indicators for the selected resources.
NOTE
Maximum 10 indicators can be selected at a time.
10 Select the Option check box and in the Time drop-down list, select the time period. Time period can be set as Recent 1 hour, Recent 12 hours, Recent 1 day, Recent 1 week, Recent 1 month, Recent 1 year, or Custom Define. 1. 2. Select Custom Define, and click time period can be 1 year. Click OK.
NOTE
to select the start and end time period. The maximum
Start time period should be earlier than end time period.
11 In the Granularity drop-down list, select the granularity period. Based on the time period, granularity can be one of the following: l Recent 1 hour: 5 minutes, 10 minutes, 15 minutes, and 30 minutes. l Recent 12 hours: 5 minutes, 10 minutes, 15 minutes, and 30 minutes, 1 hour. l Recent 1 day: 5 minutes, 10 minutes, 15 minutes, and 30 minutes, 1 hour. l Recent 1 week: 1 hour, 1 day. l Recent 1 month: 1 day. l Recent 1 year: 1 day. l Custom Define: 5 minutes, 10 minutes, 15 minutes, 30 minutes, 1 hour and 1 day.
NOTE
For custom define, the granularity can be selected based on the time period selected.
12 Optional: Click Advance, and set the filter conditions for the indicators. 1. 2. 3. In the Logic Type drop-down list, select the logic type as AND or OR. Select the Operator and set the Value for the corresponding indicators. Operator can be set as =, <, >, <=, >=, or !=. Click OK. 13 Optional: Click Save as Query Template to save a new or an existing template as a new template. 14 Optional: Click Cancel to cancel the operation.
15 Click OK to get the performance data based on the filter conditions set for one graph one resource. ----End
Exception Handling
l If a large number of frames with CRC errors exist or the traffic on an Ethernet port is low in a certain period, check whether the line quality is poor or whether any Ethernet port of the device is faulty. If a large number of packets are lost, check whether the traffic suppression function is enabled. If the fault persists, replace the port to prevent the communication failure caused by the port fault. If the fault persists, contact Huawei technical support engineers. For details, see How to Obtain Technical Support from Huawei.
l l l
Related Commands
To... Query the statistics of an Ethernet port Run the Command... display port statistics In... EPON mode, GPON mode, IPM mode , EAU mode and GAU mode
21.4 Measuring the Usage of NE Resources

This topic describes how to measure the resource usage of the NE. You can query the NE information, such as the number, software version, type, MAC address, physical location, and running status.
Prerequisite
The NE must be added to the U2000 successfully.
Procedure
1 Choose Inventory > Physical Inventory > NE from the main menu. 2 Click the NE Statistics tab. Select NE Type, Software Version, NE Type+Software Version, or Customize from the Statistics Type drop-down list. 1. 2. Select NE Type from the Statistics Type drop-down list and click Count. The number of NEs of different types is displayed in the information list in the lower pane. Select Software Version from the Statistics Type drop-down list, and click Count. The number of NEs of different software versions is displayed in the information list in the lower pane. Select NE Type+Software Version from the Statistics Type drop-down list and click Count. The number of NEs of different software versions corresponding to different NE types is displayed in the information list in the lower pane.
3.
21-10
4.
Select Customize. In the Customize NE Statistics Type dialog box, click New. In the New Customize NE Statistics Type dialog box, enter the name of the measurement item to be customized in the Custom Name text box in the Customize NE Statistics Type area. In the Basic Item area, select the measurement item to be customized, click add the selected measurement item to the Combined Item area. Then, click OK. to
5.
Click OK.
3 Click next to Statistics Scope. In the dialog box that is displayed, select the NE to be measured, and then click OK. 4 Select the required record from the NE list, and then you can perform the following operations: l Choose Save As. In the dialog box that is displayed, set Start Row and End Row, and then next to File Name. In the dialog box that is displayed, set File Name, File click Type and Encoding, and then click Save. Click OK in the Save Options dialog box to save the report to the specified path.
NOTE
The reports can be saved as txt, xls, html and xls files.
Choose Print. In the dialog box that is displayed, set Start Row and End Row, and then click OK to print the report.
----End
Command Reference
To... Query the details of a board (After performing an operation on a board, you can query the details of the board, such as the slot number, name, status, daughter board information, port information and online status.) Run the Command... display board In... User mode
21.5 Checking the NE User Level

It is recommended that you check whether the allocation of the level of the user who configures NEs is correct once every month. This operation ensures that the allocated user level can be the same as the user level that is planned and deployed, and that the user level meets the requirement of NE maintenance.
Context
Users are divided into four levels by rights, that is, the common user, operator, administrator, and superuser. l
Issue 03 (2010-11-19)
A common user can perform basic system operations and simple query operations.
l l l
An operator can perform basic configurations for the device and services. An administrator can perform all configurations. The administrator is responsible for maintaining the device, user account, and rights to manage devices. The superuser is unique in the system. Being the top-level user in the system, the superuser can add an administrator and has all the rights of the administrator.
Reference Standard
The level of the user who configures NEs is the same as the level that is planned and deployed, and can meet the requirement of NE maintenance. The user rights are allocated properly.
Procedure
1 Choose Administration > NE Security Management > LCT User Management from the main menu. 2 In the LCT Management window, click the NE User tab. 3 Select the required device type from the Device Type drop-down list. The information about all the users of the selected device type is displayed in the list. Then, click Filter to display the NE users that meet the filtering criteria. 4 Query the level of the NE user in the Level column in the list. ----End
Exception Handling
l If the allocation of the NE user level is improper, right-click the record to be queried in the list on the NE User tab, and then select Configure to modify the NE user level.
NOTE
Only the user with the administrator or higher-level right can modify the NE user level.
If the fault persists, contact Huawei technical support engineers. For details, see How to Obtain Technical Support from Huawei.
Related Commands
To... Query the NE user level Modify the NE user level Run the Command... display terminal user terminal user level In... User mode Privilege mode
21.6 Changing the Password of an NE User

To ensure the security of an account, it is recommended that you change the password of an NE user periodically instead of using the same password for a long period during maintenance.
Prerequisite
You must be an NMS user with the Security Manager User authority or higher.
Reference Standard
You can log in to an NE by using the new password.
Procedure
1 Choose Administration > NE Security Management > LCT User Management from the main menu. 2 Click the NE User tab, and then select the required device type from the Device Type dropdown list. All the users on this type of devices are displayed in the user list. Click Find to display the required users. 3 Select one or more records from the user list, right-click, and then choose Set Password. 4 In the Set Password dialog box as shown in the following figure, set a new password.
NOTE
The password consists of 1 to 15 characters.
5 Click OK. ----End
Exception Handling
l l If the password fails to be changed, the U2000 displays a message indicating the failure. In this case, check whether the password is correct according to the message. If the problem persists, contact Huawei technical support engineers. For information on how to contact Huawei technical support engineers, see How to Obtain Technical Support from Huawei.
Related Commands
To... Change the password of an NE user Run the Command... terminal user password In... Privilege mode
Issue 03 (2010-11-19)
21-13
21.7 Saving, Backing Up, and Restoring NE Data

The topic describes how to save and back up NE data and restore NE data when an NE fails to be upgraded. 21.7.1 Saving and Backing Up the NE Data Periodically The DC saves and backs up data periodically according to the default policy or user-defined policy and thus helps to restore and load the data in future. 21.7.2 Saving and Backing Up NE Data Immediately The DC can save and back up NE data periodically or immediately to meet the requirements in different scenarios. 21.7.3 Checking the Backup of the NE Configuration Data It is recommended that you check whether the NE configuration data is backed up successfully once every week. This operation helps you to restore the recent system data in time in the case that an expected fault occurs in the system. Thus, the impact on users is minimized. 21.7.4 Restoring the NE Data Immediately The DC can restore the history backup data after a NE is selected. This operation ensures that the NE data can be restored if the system upgrade fails or any problems occur. Thus, the system can be restored to the normal state.
21.7.1 Saving and Backing Up the NE Data Periodically

The DC saves and backs up data periodically according to the default policy or user-defined policy and thus helps to restore and load the data in future.
Saving and Backing Up the NE Data by Using the Default Policy

This topic describes how to save and back up the NE data periodically by using the default policy. Hence, you can save and back up the NE data at a fixed time, which facilitates the restoring and loading of the NE data.
Impact on the System

The backup has certain impact on the running rate of the NE. Therefore, it is recommended that you back up the NE data when the NE carries minimum traffic, for example, at 2:00 a.m.
Prerequisite
l l l The DCServer process runs in the normal state. The communication between the NE and the U2000 must be in the normal state. The TFTP/FTP/SFTP service must be configured and run in the normal state. For details, see 1.1.1 Configuring the FTP, SFTP, or TFTP Service (Windows), 1.1.2 Configuring the FTP, SFTP, or TFTP Service (Solaris) and 1.1.3 Configuring the FTP, SFTP, or TFTP Service (Linux).
Procedure
1 Choose Administration > NE Software Management > Default Policy from the main menu.
2 Click the Backup Policy tab, and then configure the backup policy of the NE, as shown in the following figure.
NOTE
l If Policy Status is set to Running, the DC backs up NEs at the specified time. l If Policy Status is set to Suspended. the DC does not back up NEs even if the policy period reaches the specified time, and the policy is still suspended.
3 Click the Save Policy tab, and then configure the save policy of the NE, as shown in the following figure.
Issue 03 (2010-11-19)
21-15
NOTE
l If Policy Status is set to Running, the DC saves NEs at the specified time. l If Policy Status is set to Suspended, the DC does not save NEs even if the policy period reaches the specified time, and the policy is still suspended.
4 Click OK to complete the configurations of the save and backup policies. 5 In the Operation Result dialog box, click OK. ----End
Related Commands
To... Configure the conditional backup function of the automatic backup Configure the periodical backup function of the automatic backup Run the Command... auto-backup condition In... Global config mode
auto-backup period
Global config mode
21-16
Issue 03 (2010-11-19)
Saving and Backing Up the NE Data by Using the Customized Policy

This topic describes how to save and back up the NE data periodically by using the customized policy. Hence, you can save and back up the required NE data at a fixed time, which facilitates the restoring and loading of the NE data.

The backup has certain impact on the running rate of the NE, therefore, it is recommended that you back up the NE data when the NE carries minimum traffic, for example, at 2:00 a.m.
Prerequisite
l l l The DCServer process runs in the normal state. The communication between the NE and the U2000 must be in the normal state. The TFTP/FTP/SFTP service must be configured and run in the normal state. For details, see 1.1.1 Configuring the FTP, SFTP, or TFTP Service (Windows), 1.1.2 Configuring the FTP, SFTP, or TFTP Service (Solaris) and 1.1.3 Configuring the FTP, SFTP, or TFTP Service (Linux).
Context
You can configure the save and backup policies for a single NE or for multiple NEs simultaneously.
Procedure
1 Choose Administration > NE Software Management > User-Defined Policy from the main menu. The User-Defined Policy dialog box is displayed. 2 Select the NE type and NE version to be configured with the save and backup policies as required. 1. 2. 3. Select the required NE type from the NE Type drop-down list. Optional: Select the required NE version from the NE Version drop-down list. Choose one or multiple NEs to be configured with the save and backup policies from the navigation tree under the NE Version drop-down list.
3 Click Next and the User-Defined Policy dialog box is displayed. 4 Click the Backup Policy tab, and then configure the backup policy of the NE, as shown in the following figure.
Issue 03 (2010-11-19)
21-17
NOTE
l If Policy Status is set to Running, the DC backs up NEs at the specified time. l If Policy Status is set to Suspended, the DC does not back up NEs even if the policy period reaches the specified time, and the policy is still suspended.
5 Click the Save Policy tab, and then configure the save policy of the NE, as shown in the following figure.
21-18
Issue 03 (2010-11-19)
NOTE
l If Policy Status is set to Running, the DC save NEs at the specified time. l If Policy Status is set to Suspended, the DC does not save NEs even if the policy period reaches the specified time, and the policy is still suspended.
6 Click Finish to complete the configurations of the save and backup policies. 7 In the Operation Result dialog box, click OK. ----End
Related Commands
To... Configure the conditional backup function of the automatic backup
Issue 03 (2010-11-19)
Run the Command... auto-backup condition
In... Global config mode
21-19
To... Configure the periodical backup function of the automatic backup
Run the Command... auto-backup period
In... Global config mode
21.7.2 Saving and Backing Up NE Data Immediately

The DC can save and back up NE data periodically or immediately to meet the requirements in different scenarios.
Saving the NE Data Immediately

Through the DC, you can save the related NE data periodically. You can also save the NE data immediately. This meets the requirements of different application scenarios.
Prerequisite
l l The communication between the NE and the U2000 must be in the normal state. The DCServer process runs in the normal state.
Context
NOTE
The manual saving task cannot be interrupted after it is started.
Procedure
1 Choose Administration > NE Software Management > NE Data Backup/Restoration from the main menu. 2 Click l l , and expand the UA5000(IPMB) NE node from the NE navigation tree.
If a certain NE type is selected, all the NEs of this type are displayed in the NE list in the NE View window in the right pane. If a NE version is selected in a certain NE type node, all the NEs of this version are displayed in the NE list in the NE View window in the right pane.
3 Optional: To locate a specific NE, click Find in the NE View window in the right pane. 4 Select one or multiple records from the NE list in the NE View window in the right pane, rightclick, and then choose Save.
NOTE
You can save the NE data for only one or multiple NEs of the same type at a time.
5 In the dialog box that is displayed, select one or multiple records need to be saved, and then click Start to save the NE data. 6 The saving process and the operation results are displayed in the Operation Status of the list. ----End
Related Commands
To... Save the current database file and configuration file of the system Save the current database file of the system Save the current configuration file of the system Run the Command... save In... Privilege mode
save data
Privilege mode
save configuration
Privilege mode
Backing Up the NE Data Immediately

Through the DC, you can back up the NE data periodically. You can also back up the NE data immediately. This meets the requirements of different application scenarios.

The backup has certain impact on the running rate of the NE. Therefore, it is recommended that you back up the NE data when the device carries minimum traffic, for example, at 2:00 a.m.
Prerequisite
l l l The DCServer process runs in the normal state. The communication between the device and the U2000 must be in the normal state. The TFTP/FTP/SFTP service must be configured and run in the normal state. For details, see 1.1.1 Configuring the FTP, SFTP, or TFTP Service (Windows), 1.1.2 Configuring the FTP, SFTP, or TFTP Service (Solaris) and 1.1.3 Configuring the FTP, SFTP, or TFTP Service (Linux). To back up the NE data to the U2000 client, the SFTP server must be configured and the SFTP service must be in the running state.
Context
NOTE
After a manual backup task is started, it cannot be stopped.
Procedure
1 Choose Administration > NE Software Management > NE Data Backup/Restoration from the main menu. 2 Click l , and expand the UA5000(IPMB) NE node from the NE navigation tree.
If a certain NE type is selected, all the NEs of this type are displayed in the NE list in the NE View window in the right pane.
Issue 03 (2010-11-19)
If a NE version is selected in a certain NE type node, all the NEs of this version are displayed in the NE list in the NE View window in the right pane.
3 Optional: To locate a specific NE, click Find in the NE View window in the right pane. 4 Select one or more records from the NE list in the NE View window in the right pane, rightclick, and then choose Backup or click Backup in the lower pane.
NOTE
You can back up the NE data for only one or multiple NEs of the same type at a time.
5 In the dialog box as shown in the following figure, set the parameters related to backing up the NE data immediately.
NOTE
To back up the data for multiple NEs of the same type, click Same as first Content Type in the upper right corner of the Backup dialog box. In this manner, you can configure the backup file with the same content for multiple NEs at a time rather than configure the backup files one by one.
6 Click Start to back up the NE data. 7 The backup process and the operation results are displayed in the Operation Status of the list. If the backup is successful, the information about the backup file is displayed on the Backup Information tab. ----End
Related Commands
To... Back up the database file manually Run the Command... backup data In... Privilege mode
21-22
Issue 03 (2010-11-19)
To... Back up the configuratio n file manually Back up the data to the backup server manually
Run the Command... backup configuration
In... Privilege mode
auto-backup manual
Global config mode
21.7.3 Checking the Backup of the NE Configuration Data

It is recommended that you check whether the NE configuration data is backed up successfully once every week. This operation helps you to restore the recent system data in time in the case that an expected fault occurs in the system. Thus, the impact on users is minimized.
Prerequisite
The parameters for periodically backing up the NE data must be set.
NOTE
After the backup policy is configured successfully, you need not manually back up data every day and need only to check the backup once every week.
Context
l The UA5000(IPMB) supports the saving and backing up of the database file. This ensures that the system can be restored in the case that an expected fault occurs in the system. For information on how to restore the NE data, see Restoring the NE Data Immediately. The U2000 supports the function of transferring the database file of the UA5000(IPMB) in the FTP/TFTP/SFTP mode. To back up the data, you can upload the file saved on the UA5000(IPMB) to a specified file server. To restore the data, you can download the file saved on the specified file server to the UA5000(IPMB).
Reference Standard
No backup failure is recorded in the log, and the backup database file exists in the specified path.
Procedure
1 Choose Administration > NE Software Management > NE Software Log Management from the main menu. 2 In the NE Software Log Management window, click Filter. The Filter Log dialog box is displayed. 3 In the Filter Log dialog box, select Backup from the Operation Type drop-down list, and then set other filtering criteria to display the required log that records backup operations (the filtering criteria items are optional), as shown in the following figure.
4 Click OK. The information about the backup operation logs is displayed in the information list. You can determine whether the database is backed up successfully by viewing the Result column in the information list. If Success is displayed in the Result column, view the directory for saving backup files in the File Path column. ----End
Exception Handling
l If Failure is displayed in the Result column, take measures according to the information displayed in the Details column. If the data is backed up in the FTP/TFTP/SFTP mode, check the following items: Whether you can ping through the IP address of the maintenance network port on the control board or the IP address of a layer 3 interface of a VLAN from the FTP/TFTP/ SFTP server. That is, check whether the communication between the UA5000(IPMB) and the U2000 is normal. Whether the entered IP address of the FTP/TFTP/SFTP server is correct. Whether the FTP/TFTP/SFTP program is running on the backup server. Whether the path in the FTP/TFTP/SFTP program is set correctly. l l If the automatic backup fails, back up the data manually. In addition, locate the cause of the backup failure and modify the settings according to the cause. If the fault persists, contact Huawei technical support engineers. For details, see How to Obtain Technical Support from Huawei.
Related Commands
To... Query user logs Run the Command... display log In... User mode
21-24
Issue 03 (2010-11-19)
To... Query the file server Configure the file server
Run the Command... display file-server file-server
In... Privilege mode Privilege mode
21.7.4 Restoring the NE Data Immediately

The DC can restore the history backup data after a NE is selected. This operation ensures that the NE data can be restored if the system upgrade fails or any problems occur. Thus, the system can be restored to the normal state.
Prerequisite
l l l The DCServer process runs in the normal state. The communication between the NE and the U2000 must be in the normal state, and there must be no packet loss in the network. The TFTP/FTP/SFTP service must be configured and run in the normal state. For details, see 1.1.1 Configuring the FTP, SFTP, or TFTP Service (Windows), 1.1.2 Configuring the FTP, SFTP, or TFTP Service (Solaris) and 1.1.3 Configuring the FTP, SFTP, or TFTP Service (Linux). The NE data must be backed up to the NMS server.
NOTE
To copy the backup files that contain the NE data to another path, copy the directory where the backup files exist. If you copy only a certain backup file, the file is invalid when the NE data is recovered.
To restore the NE data by selecting the history file on the U2000 client, the SFTP server must be configured and the SFTP service must be in the running state.
Context
NOTE
After a manual restoring task is started, it cannot be stopped.
Procedure
1 Choose Administration > NE Software Management > NE Data Backup/Restoration from the main menu. 2 Click l l , and expand the UA5000(IPMB) NE node from the NE navigation tree. If a certain NE type is selected, all the NEs of this type are displayed in the NE list in the NE View window in the right pane. If a NE version is selected in a certain NE type node, all the NEs of this version are displayed in the NE list in the NE View window in the right pane.
3 Optional: To locate a specific NE, click Find in the NE View window in the right pane. 4 Select one or multiple records from the NE list in the NE View window in the right pane, rightclick, and then choose Recover or click Recover in the lower pane.

NOTE
You can restore the NE data for only one or multiple NEs of the same type at a time.
5 In the dialog box that is displayed, set the parameters related to restoring the NE data immediately.
NOTE
l The activation types are No Reboot and With Service Interruption. l No Reboot: Start the recover operation without rebooting the NE. l With Service Interruption: If the operation is successful, the service of the selected NE(s) is interrupted. l To restore the data for multiple NEs of the same type, click Same as first Board or Same as first Activate Type in the upper right corner of the Recover dialog box. In this manner, you can configure multiple NEs with the same board type or activation type at a time rather than restore the NE data one by one.
6 Click Start to restore the history backup data of the selected NE. 7 In the Operation Confirmation dialog box, click Yes. 8 In the Operation Status column of the NE list, the restoring process and result are displayed. ----End
Related Commands
To... Load the configuratio n file Load the database file
21-26
Run the Command... load configuration
In... Privilege mode
load data
Privilege mode
Issue 03 (2010-11-19)
Issue 03 (2010-11-19)
21-27
A Acronyms and Abbreviations
A
A AAA AAL1 AAL5 ABR ADSL ANSI ATM ATU-C ATU-R
Acronyms and Abbreviations
The following table describes the acronyms and abbreviations used in the UA5000(IPMB) Configuration Guide.
Authentication, Authorization and Accounting ATM Adaptation Layer Type 1 ATM Adaptation Layer Type 5 Available Bit Rate Asymmetric Digital Subscriber Line American National Standard Institute Asynchronous Transfer Mode ADSL Transceiver Unit, Central office end ADSL Transceiver Unit, Remote end
B BRAS BRA BRI Broadband Remote Access Server Basic Rate Access Basic Rate Interface
C CAR CAS CBR CES Committed Access Rate Channel Associated Signaling Constant Bit Rate Circuit Emulation Service
Issue 03 (2010-11-19)
A-1
CDVT CLP CLR CS CTC CTD
Cell Delay Variation Tolerance Cell Loss Priority Cell Loss Rate Convergence Sub layer Common Transmit Clock Cell Transfer Delay
D DCE DDN DSLAM DTE Data Communications Equipment Digital Data Network Digital Subscriber Line Access Multiplexer Digital Terminal Equipment
E EMU EPD ESC Environment Monitor Unit Early Packet Discard Environment Supervision Circuit
F FE FEBE FR FTP Far End Far End Bit Error Frame Relay File Transfer Protocol
G GMII Gigabit Media Independent Interface
H HDLC HEC High-Level Data Link Control Header Error Control
A-2
Issue 03 (2010-11-19)
IAD ICMP IMA IPoA ISDN ISP IWF
Integrated Access Device Internet Control Message Protocol Inverse Multiplexing over ATM Internet Protocols Over ATM Integrated Service Digital Network Internet Service Provider Inter Working Function
L LAN LOF LOS Local Area Network Loss of Frame Loss of Signal
M MA MAC MBS MIB MMX MTU Media Service Access Media Access Control Maximum Burst Size Management Information Base Main Multiplexer Card Maximum Transmission Unit
N NE NMS NNI nrt-VBR Network Element Network Management Station Network Node Interface Non-Real-Time Variable Bit Rate
O OAM OC-3 OLT ONU Operations, Administration, and Maintenance Optical Carrier Level 3 Optical Line Terminal Optical Network Unit
Issue 03 (2010-11-19)
A-3
P PBX PCM PCR POTS PPD PPP PPPoE PRA PRI PSTN PVC PVP Private Branch Exchange Pulse Code Modulation Peak Cell Rate Plain Old Telephone Service Partial Packet Discard Point-to-Point Protocol PPP Over Ethernet Primary Rate Access Primary Rate Interface Public Switched Telephone Network Permanent Virtual Connection Permanent Virtual Path
Q QoS Quality of Service
R RADIUS RTU rt-VBR Remote Authentication Dial In User Service Remote Terminal Unit Real-Time Variable Bit Rate
S SAR SCR SDH SNMP SRA STM-1 STM-4 STS-3 Segmentation and Reassembly Sustainable Cell Rate Synchronous Digital Hierarchy Simple Network Management Protocol Seamless Rate Adaptive Synchronous Transport Module-1 Synchronous Transport Module-4 Synchronous Transport Signal Level 3
A-4
Issue 03 (2010-11-19)
T TDM TFTP Time Division Multiplex Trivial File Transfer Protocol
U UBR UDT UNI UPC UTOPIA Unspecified Bit Rate Unstructured Data Transfer User Network Interface Usage Parameter Control Universal Test&Operations PHY Interface for ATM
V VBR VCI VCL VLAN VPDN VPI Variable Bit Rate Virtual Channel Identifier Virtual Channel Link Virtual Local Area Network Virtual Private Data Network Virtual Path Identifier
Issue 03 (2010-11-19)
A-5

I Manager Huawei

Uploaded by

Copyright:

Available Formats

I Manager Huawei

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

I Manager Huawei

Uploaded by

Copyright:

Available Formats

What is the purpose of this document?

What is the purpose of this document?

What types of users is this document intended for?

What types of users is this document intended for?

iManager U2000 Unified Network Management System V100R002C01

Operation Guide for UA5000-IPMB NE Management

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

About This Document

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

Changes in Issue 03 (2010-11-19) Based on Product Version V100R002C01

Changes in Issue 02 (2010-09-24) Based on Product Version V100R002C01

Changes in Issue 01 (2010-08-16) Based on Product Version V100R002C01

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

2 Pre-configuring Parameters for Service Provisioning........................................................2-1

3 Setting the System Clock..........................................................................................................3-1

4 Configuring the System Security Policy................................................................................4-1

5 Configuring the User Security Policy....................................................................................5-1

6 Configuring the DHCP Relay..................................................................................................6-1

7 Configuring the xDSL Access..................................................................................................7-1

8 Configuring Multicast Services...............................................................................................8-1

9 Configuring the Multicast Services of Subtending Devices.............................................9-1

10 Configuring the Triple Play Service...................................................................................10-1

11 Configuring VLAN Stacking Wholesale Services...........................................................11-1

12 Configuring the QinQ VLAN Private Line Service........................................................12-1

13 Configuring the CESoP TDM Private Line Service........................................................13-1

14 Configuring the Active/Standby Switchover for the Upstream Service.....................14-1

14.3 Configuring the Active/Standby Switchover for the AIU Upstream..........................................................14-5

15 Configuring the Ethernet OAM Diagnosis.......................................................................15-1

16 Configuring the BFD Network Monitoring......................................................................16-1

17 Detecting the Network..........................................................................................................17-1

18 Saving the Data.......................................................................................................................18-1

21 Remote Maintenance Guide................................................................................................21-1

A Acronyms and Abbreviations................................................................................................A-1

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

1.1 Configuring the xFTP Service

1.1.1 Configuring the FTP, SFTP, or TFTP Service (Windows)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

1.1.2 Configuring the FTP, SFTP, or TFTP Service (Solaris)

Start the TFTP service.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

1.1.3 Configuring the FTP, SFTP, or TFTP Service (Linux)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

1.1.4 Configuring the xFTP Watcher

1.1.5 Configuring the xFTP File in the NAT Networking Mode

1.2 Setting the Communication Parameters

1.2.1 Setting the SNMP Parameters

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.