Og For Ua5000-Pvm Ne Management - (v100r002c01 - 03)

iManager U2000 Unified Network Management System V100R002C01
Operation Guide for UA5000-PVM 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-PVM 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(PVM). After you read this document, you should be able to know how to operate the UA5000(PVM) 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-36 1.12 Configuration Example of Inband Network Management (Based on the SNMPv3 Protocol)...................1-42
2 Pre-configuring Parameters for Service Provisioning........................................................2-1

2.1 Configuring the VoIP Media Gateway............................................................................................................2-3 2.1.1 Configuring an IP Interface....................................................................................................................2-3 2.1.2 Adding an MG (H.248/MGCP)..............................................................................................................2-4 2.1.3 Adding an MG (SIP)..............................................................................................................................2-5 2.1.4 Configuring an MGC.............................................................................................................................2-6 2.1.5 Adding the Ringing Mapping of MG.....................................................................................................2-7 2.1.6 Starting Up an MG Interface..................................................................................................................2-8 2.2 Configuring the VoIP Signaling Gateway......................................................................................................2-8 2.2.1 Adding an SG.........................................................................................................................................2-8 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-PVM NE Management 2.2.2 Adding an Association...........................................................................................................................2-9
2.3 Configuring a V5 Interface...........................................................................................................................2-10 2.3.1 Adding a V5 Interface..........................................................................................................................2-11 2.3.2 Adding a 2M Link on a V5 Interface...................................................................................................2-12 2.3.3 Adding a C-Channel.............................................................................................................................2-13 2.3.4 Adding an ISDN C-Channel................................................................................................................2-14 2.3.5 Resetting a V5 Interface.......................................................................................................................2-14 2.4 Configuring an Impedance Profile................................................................................................................2-14 2.5 Configuring an MGC Profile.........................................................................................................................2-15 2.6 Configuring the UAS Profile.........................................................................................................................2-16 2.7 Configuring the System Parameters..............................................................................................................2-17 2.7.1 Configuring the FoIP and MoIP Attributes..........................................................................................2-18 2.7.2 Adding the System Parameter Profile to a Device...............................................................................2-18
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 VoIP PSTN Service......................................................................................4-1

4.1 Configuring Dual Homing..............................................................................................................................4-4 4.2 Setting Standalone Parameters........................................................................................................................4-5 4.3 Setting Authentication Parameters..................................................................................................................4-6 4.4 Setting DMM Parameters................................................................................................................................4-7 4.5 Configuring the TID Profile Reference...........................................................................................................4-8 4.6 Setting the TID Prefix Parameters..................................................................................................................4-9 4.7 Setting Digitmap Parameters.........................................................................................................................4-10 4.8 Setting the MGC Overload Parameters.........................................................................................................4-11 4.9 Configuring DSP Resources..........................................................................................................................4-13 4.10 Configuring Ringing Mapping....................................................................................................................4-14 4.11 Configuring the VoIP PSTN Service..........................................................................................................4-15 4.11.1 Configuring a VoIP PSTN Port..........................................................................................................4-16 4.11.2 Enabling a VoIP PSTN Port...............................................................................................................4-17 4.12 Configuration Example of the VoIP PSTN Service....................................................................................4-18 4.13 Configuration Example of the VoIP PSTN Service (SIP)..........................................................................4-22 4.14 Configuring the VoIP VAG Service...........................................................................................................4-26 4.15 Configuring the MoIP Service....................................................................................................................4-27 4.16 Configuring the FoIP Service......................................................................................................................4-29
5 Configuring the VoIP ISDN Service......................................................................................5-1

5.1 Configuring the VoIP ISDN BRA Service.....................................................................................................5-2 5.1.1 Configuring the Attributes of a VoIP ISDN BRA Port..........................................................................5-2 5.2 Configuring the VoIP ISDN PRA Service......................................................................................................5-4 5.2.1 Configuring the CRC4...........................................................................................................................5-4 viii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-11-19)
Contents
5.2.2 Configuring the Working Mode of the EDTB Card..............................................................................5-5 5.2.3 Configuring the Attributes of a VoIP ISDN PRA Port..........................................................................5-5 5.3 Configuration Example of the VoIP ISDN BRA Service...............................................................................5-6 5.4 Configuration Example of the VoIP ISDN PRA Service.............................................................................5-11
6 Configuring the V5 ISDN Service..........................................................................................6-1

6.1 Introduction to the V5 ISDN Service..............................................................................................................6-2 6.2 Configuring the V5 ISDN BRA Service.........................................................................................................6-3 6.2.1 Configuring the V5 ISDN BRA Service................................................................................................6-3 6.3 Configuring the V5 ISDN PRA Service......................................................................................................... 6-4 6.3.1 Configuring the CRC4........................................................................................................................... 6-4 6.3.2 Configuring the Working Mode of the EDTB Card.............................................................................. 6-5 6.3.3 Configuring a V5 ISDN PRA User........................................................................................................6-5
7 Configuring the V5 PSTN Service..........................................................................................7-1

7.1 Introduction to the V5 PSTN Service ............................................................................................................ 7-3 7.2 Configuring the V5 PSTN User Information..................................................................................................7-3
8 Configuring the Transparent Transmission Service on the U Interface.........................8-1

8.1 Introduction to the Transparent Transmission Service on the U Interface......................................................8-2 8.2 Adding an SPC................................................................................................................................................8-2
9 Configuring the ATI Service....................................................................................................9-1

9.1 Introduction to the ATI Service...................................................................................................................... 9-2 9.2 Configuring 2/4-Wire VF Service and the E&M Trunk Service.................................................................... 9-2 9.2.1 Configuring the ATI Port Attributes......................................................................................................9-2 9.2.2 Adding an SPC.......................................................................................................................................9-3 9.3 Configuring the Hotline Service of the E&M Trunk Interface.......................................................................9-5 9.3.1 Configuring the ATI Port Attributes......................................................................................................9-5 9.3.2 Adding an SPC.......................................................................................................................................9-6
10 Configuring the VFB Service...............................................................................................10-1

10.1 Introduction to the VFB Service.................................................................................................................10-2 10.2 Configuring the VFB Port Attributes..........................................................................................................10-2 10.3 Adding an SPC............................................................................................................................................10-3
11 Configuring the MTA Service.............................................................................................11-1

11.1 Introduction to the MTA Service................................................................................................................11-2 11.2 Configuring the Attributes of an MTA Port................................................................................................11-2 11.3 Adding an SPC............................................................................................................................................11-3
12 Configuring the HSL Service...............................................................................................12-1

12.1 Introduction to the HSL Service..................................................................................................................12-2 12.2 Configuring the V.35 Port Attributes of the HSL Card..............................................................................12-2 12.3 Adding an SPC............................................................................................................................................12-3
13 Configuring the SDL Service...............................................................................................13-1

Issue 03 (2010-11-19) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ix
Contents
13.1 Introduction to the SDL Service..................................................................................................................13-2 13.2 Configuring the TDM G.SHDSL Service...................................................................................................13-2 13.2.1 Configuring the Working Mode of the SDL Card.............................................................................13-3 13.2.2 Configuring the Attributes of a TDM G.SHDSL Port.......................................................................13-3 13.2.3 Adding an SPC...................................................................................................................................13-4 13.3 Configuring the Subtend Service of the TDM G.SHDSL...........................................................................13-5 13.3.1 Configuring the Working Mode of the SDL Card.............................................................................13-6 13.3.2 Configuring the Running Mode of the TDM G.SHDSL Port............................................................13-7 13.3.3 Adding a Remote Subscriber Shelf....................................................................................................13-8 13.3.4 Adding an Inter-Shelf Link................................................................................................................13-9 13.3.5 Configuring Subscriber Data..............................................................................................................13-9 13.3.6 Enabling a Service Port....................................................................................................................13-11
14 Configuring the CDI Service...............................................................................................14-1

14.1 Introduction to the CDI Service..................................................................................................................14-2 14.2 Configuring the Z-Interface Extension Service...........................................................................................14-3 14.2.1 Configuring the Attributes of a CDI Port...........................................................................................14-4 14.2.2 Setting Up an SPC..............................................................................................................................14-5 14.3 Configuring the PBX Bidirectional Connection.........................................................................................14-7 14.3.1 Configuring the Attributes of a CDI Port...........................................................................................14-8 14.3.2 Setting Up an SPC..............................................................................................................................14-9 14.4 Configuring the DDI Service....................................................................................................................14-10 14.4.1 Configuring the Attributes of a CDI Port.........................................................................................14-13 14.4.2 Adding the DDI User Data...............................................................................................................14-14 14.4.3 Starting the DDI Service..................................................................................................................14-15
15 Maintaining the TDM G.SHDSL Terminal......................................................................15-1

15.1 Querying the Information About a TDM G.SHDSL Terminal...................................................................15-2 15.2 Configuring a Remote Loopback for a TDM G.SHDSL Terminal.............................................................15-2
16 Detecting the Network..........................................................................................................16-1

16.1 Telnet...........................................................................................................................................................16-2 16.2 Ping..............................................................................................................................................................16-2 16.3 Tracert.........................................................................................................................................................16-2 16.4 SSH..............................................................................................................................................................16-3
17 Saving the Data.......................................................................................................................17-1

17.1 Setting the Parameters for Saving the Data.................................................................................................17-2 17.2 Immediately Enabling Data Saving Function.............................................................................................17-2
18 Synchronization......................................................................................................................18-1
18.1 Synchronizing the NE Data.........................................................................................................................18-2 18.2 Synchronizing the NE Time........................................................................................................................18-2 18.3 Synchronizing NE Alarms..........................................................................................................................18-2 18.4 Synchronizing the System Parameter Profile..............................................................................................18-3 x Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-11-19)
Contents
19 File Operations.......................................................................................................................19-1
19.1 Saving Records as a File.............................................................................................................................19-2 19.2 Previewing the File Printing Effect.............................................................................................................19-2 19.3 Printing........................................................................................................................................................19-3
20 Remote Maintenance Guide................................................................................................20-1

20.1 Monitoring Critical and Major Alarms of NEs...........................................................................................20-3 20.2 Measuring the CPU Usage of a Board........................................................................................................20-5 20.3 Measuring the Performance of an Upstream Ethernet Port.........................................................................20-8 20.4 Measuring the Usage of NE Resources.....................................................................................................20-10 20.5 Checking the NE User Level.....................................................................................................................20-11 20.6 Changing the Password of an NE User.....................................................................................................20-12 20.7 Saving, Backing Up, and Restoring NE Data...........................................................................................20-13 20.7.1 Saving and Backing Up the NE Data Periodically...........................................................................20-14 20.7.2 Saving and Backing Up NE Data Immediately................................................................................20-20 20.7.3 Checking the Backup of the NE Configuration Data.......................................................................20-23 20.7.4 Restoring the NE Data Immediately................................................................................................20-25
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-37 Figure 1-4 Example network of inband network management..........................................................................1-42 Figure 4-1 Example network of the VoIP PSTN service...................................................................................4-19 Figure 4-2 Example network of the VoIP PSTN service...................................................................................4-23 Figure 5-1 Example network for configuring the VoIP ISDN BRA service ......................................................5-7 Figure 5-2 Example network for configuring the VoIP ISDN PRA service .....................................................5-12 Figure 7-1 Flowchart for configuring the V5 PSTN service................................................................................7-2 Figure 14-1 Example network of the Z-interface extension service..................................................................14-3 Figure 14-2 Flowchart for configuring the Z-interface extension service.........................................................14-4 Figure 14-3 Example network of the PBX bidirectional connection.................................................................14-7 Figure 14-4 Flowchart for configuring the PBX bidirectional connection........................................................14-8 Figure 14-5 Example network of the DDI service...........................................................................................14-11 Figure 14-6 Flowchart for configuring the DDI service..................................................................................14-12
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-37 Table 1-6 Data plan for inband network management in a U2000 HA system..................................................1-38 Table 1-7 Data plan for inband network management in a U2000 single-server system...................................1-43 Table 1-8 Data plan for inband network management in a U2000 HA system..................................................1-44 Table 4-1 Data plan for the VoIP PSTN service................................................................................................4-19 Table 4-2 Data plan for the VoIP PSTN service (SIP).......................................................................................4-24 Table 4-3 Fax modes supported by the UA5000(PVM) (H.248/MGCP)...........................................................4-30 Table 5-1 Data plan for the VoIP ISDN BRA service.........................................................................................5-8 Table 5-2 Data plan for the VoIP ISDN PRA service........................................................................................5-12 Table 6-1 Number of ISDN BRA ports provided by service cards......................................................................6-2 Table 6-2 Number of ISDN PRA ports provided by service cards......................................................................6-3
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(PVM) and reduce costs, you need to add a local slave shelf on the U2000 and the device. When you add the shelf on both the U2000 and the
Issue 03 (2010-11-19) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-1
1 Managing Devices
device, the shelf works in the normal state only after you confirm it on the U2000. After adding the shelf successfully, you can configure and query the shelf. 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(PVM) 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(PVM) 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(PVM) 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(PVM) 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 UA5000PVM 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(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) 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(PVM) and reduce costs, you need to add a local slave shelf on the U2000 and the device. When you add the shelf on both the U2000 and the device, the shelf works in the normal state only after you confirm it on the U2000. After adding the shelf successfully, you can configure and query the shelf.
1 Managing Devices
Context
l The shelf where the control card is located is the master shelf. The master shelf can be connected with a subtended shelf and a slave shelf to expand the service capacity of the device. A slave shelf must be configured by commands and the cards in the slave shelf are numbered from 0. The slave shelf can be connected with a subtended shelf to expand the service capacity. A subtended shelf is a logical expansion of the master shelf or the slave shelf. The subtended shelf does not need to be configured. The cards in the subtended shelf are numbered together with the cards in the master shelf or slave shelf. When adding a shelf, pay attention to the following: After a master shelf is added, the master shelf is in the normal state and the control card in it is also in the normal state. After a slave shelf is added, the slave shelf is in the faulty state and will work in the normal state only after you add the connections between the shelves. When adding a shelf, you must enter the correct shelf type. Otherwise, the cards in the shelf cannot work in the normal state.
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. 4 In the Physical Root navigation tree, right-click the slave shelf to be confirmed and choose Confirm Frame from the shortcut menu. ----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
1 Managing Devices
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.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) 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.
Issue 03 (2010-11-19)
1-21
1 Managing Devices
(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. (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
1-22
Issue 03 (2010-11-19)
1 Managing Devices
Result
After configuring the information about the physical resources, you can easily query the information about the telecommunications room, rack, shelf, and card.
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(PVM) 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(PVM) 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(PVM).
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(PVM) 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(PVM) IP address of the gateway of the UA5000 (PVM) 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(PVM) 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(PVM) 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(PVM) 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 (PVM) 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. 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 2. 3. 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 4. 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
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.
1 Managing Devices
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. In the dialog box that is displayed, set the parameters.
Add the device to the U2000. a. b.
Issue 03 (2010-11-19)
1-29
1 Managing Devices
c.
Click OK.
NOTE
----End
Result
After the parameters are set successfully on the U2000, the U2000 manages and maintains the UA5000(PVM) successfully.
1.10 Configuration Example of Outband Network Management (Based on the SNMPv3 Protocol)
This topic describes how to manage and maintain the UA5000(PVM) 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(PVM) 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(PVM).
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(PVM) 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(PVM) IP address of the gateway of the UA5000 (PVM) 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(PVM) 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(PVM) 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(PVM) 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 (PVM) 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. 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
huawei(config)#snmp-agent sys-info version v3 2. 3. 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
1 Managing Devices
4.
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. 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 2. 3. 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 4. Save the data. huawei(config)#save 2 Configure outband network management on the U2000. 1.
1-34
Configure the route connecting the U2000 server and the network management port.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 03 (2010-11-19)
NOTE
1 Managing Devices
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. e. f. g.
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.
Issue 03 (2010-11-19)
1 Managing Devices
3.
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.11 Configuration Example of Inband Network Management (Based on the SNMPv1 or SNMPv2c Protocol)
This topic describers how to manage and maintain the UA5000(PVM) 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(PVM) 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(PVM).
NOTE
1 Managing Devices
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.
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(PVM) 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(PVM)
Issue 03 (2010-11-19)
Data 10.10.21.2/24
1-37
1 Managing Devices
Item IP address of the gateway of the UA5000 (PVM) connected to a router Network segment of the U2000 Read community name Write community name SNMP version
Data 10.10.20.254/24 IP address: 10.10.21.1/24 public 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(PVM) 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(PVM) 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(PVM) 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 (PVM) connected to a router Read community name Write community name SNMP version
1-38
Issue 03 (2010-11-19)
1 Managing Devices
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.
2.
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 3. 4. 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 5. 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.
2.
Issue 03 (2010-11-19)
Set the SNMP parameters.

1 Managing Devices
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 3. 4. 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 5. 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. 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.
1-40
1 Managing Devices
c.
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.
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.
Issue 03 (2010-11-19)
1-41
1 Managing Devices
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(PVM) 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-4 shows an example network of inband network management. The U2000 manages and maintains the UA5000(PVM) 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(PVM). Figure 1-4 Example network of inband network management
U2000
Router UA5000
GE 0/2/0
COM ETH IPMB
1-42
Issue 03 (2010-11-19)
1 Managing Devices
Data Plan
Configuring Inband Network Management in a U2000 Single-Server System The IP address of the inband network management port of the UA5000(PVM) 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. 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(PVM) IP address of the gateway of the UA5000 (PVM) 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(PVM) 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(PVM) must be in the same network
Issue 03 (2010-11-19)
1 Managing Devices
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(PVM) 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 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 (PVM) 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.
2.
Set the SNMP parameters. The SNMP parameters must be the same as the SNMP parameters on the U2000. l Set the SNMP user, group, and view.
1-44
Issue 03 (2010-11-19)
1 Managing Devices
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 3. 4. 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 5. 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.
2.
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
Issue 03 (2010-11-19)
1-45
1 Managing Devices
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 3. 4. 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 5. 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.
1 Managing Devices
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. 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.
Issue 03 (2010-11-19)
1-47
1 Managing Devices
c.
Click OK.
NOTE
----End
Result
1-48
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 V5 interface, media gateway, MGC profile, and system parameter profile according to the global data plan before provisioning services for the network element. 2.1 Configuring the VoIP Media Gateway In the NGN, the media gateway (MG) and the media gateway controller (MGC) are separated completely. That is, the functions of the user plane are separately from the functions of the control plane. The UA5000(PVM) functions as the MG and completes the message interconnection of the user plane, which performs the communication between the UA5000(PVM) and the upper layer MGC through the MG interface. The MGC completes the message interconnection of the control plane. An MG converts the media format of a type of networks into the media format of another type of networks. Hence, the messages of the user plane can interconnect with each other. In addition, the MG is also called the access gateway (AG). 2.2 Configuring the VoIP Signaling Gateway The signaling gateway (SG) is used to convert and transmit the signaling, and it converts the signaling system number 7 (SS7) of the ISDN network into the signaling protocol corresponding to the IP network. In this case, the signaling can be exchanged between the IP network and the ISDN network. The SG communicates with the softswitch through SCTP. If the upstream transmission is performed, the SG transmits the signaling that is converted through SCTP to the softswitch. If the downstream transmission is performed, the SG first receives the signaling of the IP network from the softswitch, converts the signaling into SS7 signaling, and then transmits the SS7 signaling to the ISDN network through the PSTN signaling interface. 2.3 Configuring a V5 Interface The V5 interface is the standard digital interface between the access network (AN) and the local exchange (LE). The V5 interface supports abundant integrated services access. It supports separation of access and services, thus improving the network structure. 2.4 Configuring an Impedance Profile
The impedance profile integrates the parameters required for the impedance and the voice gain of a PSTN port. The U2000 manages these parameters through the profile. By setting the impedance and the voice gain of a PSTN port, you can adjust the voice signals of the user phones. 2.5 Configuring an MGC Profile The media gateway controller (MGC) integrates multiple logical function entities, provides the call control and connection of integrated services, and implements integrated services. The MGC profile defines the parameters required for an MGC interface. The U2000 manages the parameters through the profile. 2.6 Configuring the UAS Profile The user agent server (UAS) profile is used to set the parameters of the SIP interface. When configuring the SIP interface, bind this profile to the SIP interface to specify the interface that communicates with the call control. After you configure the UAS profile and bind the profile to the SIP interface, the settings of the SIP interface are complete. 2.7 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 Configuring the VoIP Media Gateway

In the NGN, the media gateway (MG) and the media gateway controller (MGC) are separated completely. That is, the functions of the user plane are separately from the functions of the control plane. The UA5000(PVM) functions as the MG and completes the message interconnection of the user plane, which performs the communication between the UA5000(PVM) and the upper layer MGC through the MG interface. The MGC completes the message interconnection of the control plane. An MG converts the media format of a type of networks into the media format of another type of networks. Hence, the messages of the user plane can interconnect with each other. In addition, the MG is also called the access gateway (AG). 1. 2.1.1 Configuring an IP Interface The IP interface is used to forward IP packets at layer 3. The configured IP address is placed into the IP address pool and functions as the signaling IP address of the MG or the media IP address, which is used to communicate with the MGC. 2.1.2 Adding an MG (H.248/MGCP) Before you provision services for network elements, you can add an MG according to the global data plan to provide the MG interface for communication with the upper layer MGC. 2.1.3 Adding an MG (SIP) Before you provision services for network elements, you can add an MG according to the global data plan to provide the MG interface for communication with the upper layer device. 2.1.4 Configuring an MGC The MGC controls the status of calls that are inside the MG and are related to the control of media channel connections. An MGC integrates multiple logical function entities, provides the call control and connection of integrated services, and implements integrated services and interconnection and conversion of various signaling protocols. 2.1.5 Adding the Ringing Mapping of MG Ringing mapping indicates that the MG maps the peer-end parameter (the parameter value of the ringing type) sent by the MGC with a specified ringing mode. After the ringing mapping is added successfully, the MG initiates the ringing based on the ringing mode corresponding to the peer-end parameter sent by the MGC. 2.1.6 Starting Up an MG Interface Cold starting the MG interface so that the MG interface can negotiate with the MGC through the specified MGC protocol. In this case, the MG interface can register with the MGC so that the configured data can take effect.
2.
3.
4.
5.
6.
2.1.1 Configuring an IP Interface

The IP interface is used to forward IP packets at layer 3. The configured IP address is placed into the IP address pool and functions as the signaling IP address of the MG or the media IP address, which is used to communicate with the MGC.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose ETH from the navigation tree.
3 In the Ethernet port list, select a record and click the IP Interface Info. tab in the lower pane. In the IP Interface Info. tab page, right-click and choose Add from the shortcut menu. 4 In the dialog box that is displayed, set the parameters of the IP interface.
NOTE
Right-click a record with a certain packet type and choose Modify from the shortcut menu. In the dialog box that is displayed, modify the QoS information.
5 Click OK. ----End
2.1.2 Adding an MG (H.248/MGCP)

Before you provision services for network elements, you can add an MG according to the global data plan to provide the MG interface for communication with the upper layer MGC.
Prerequisite
The signaling IP address and the media IP address must exist in the corresponding IP address pool.
Context
l l l l l l An MG ID must be unique on a device. Ensure that the MG parameter values are the same as the corresponding parameter values on the MGC. You can configure up to eight MGs on a device. After the MG is added, you must perform the cold starting or recovering operation so that the MG can work in the normal state. After the MG is added successfully, the system adds two MGCs concurrently. This MG can provide services to the user when the MG communicates with only one MGC. The H.248 protocol separates the signaling stream and the media stream and uses different QoS policies for the two types of streams.
NOTE
The procedure for adding an MG supporting the MGCP protocol is the same as the procedure for adding an MG supporting the H.248 protocol. The preset parameters, however, are different. The following procedure uses adding the MG supporting the H.248 protocol as an example.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Voice Gateway > Media Gateway from the navigation tree. 3 On the Media Gateway tab page, set the filter criteria to display the required MGs. 4 In the information list, right-click and choose Add from the shortcut menu. 5 In the dialog box that is displayed, set the parameters as follows.
6 Click OK. ----End
2.1.3 Adding an MG (SIP)

Before you provision services for network elements, you can add an MG according to the global data plan to provide the MG interface for communication with the upper layer device.
Prerequisite
The signaling IP address and the media IP address must exist in the corresponding IP address pool.
Context
l l l An MG ID must be unique on a device. You can configure up to eight MGs on a device. After the MG is added, you must perform the resetting operation so that the MG can work in the normal state.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Voice Gateway > Media Gateway from the navigation tree.
3 On the Media Gateway tab page, set the filter criteria to display the required MGs. 4 In the information list, right-click and choose Add from the shortcut menu. 5 In the dialog box that is displayed, set the parameters as follows.
6 Click OK. ----End
2.1.4 Configuring an MGC

The MGC controls the status of calls that are inside the MG and are related to the control of media channel connections. An MGC integrates multiple logical function entities, provides the call control and connection of integrated services, and implements integrated services and interconnection and conversion of various signaling protocols.
Prerequisite
The corresponding MGC profile must exist. For details about how to add an MGC profile, see 2.5 Configuring an MGC Profile.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Voice Gateway > Media Gateway from the navigation tree. 3 On the Media Gateway tab page, set the filter criteria to display the required MGs. 4 Select a record, click the MGC Information tab. 5 Right-click a record and choose Modify from the shortcut menu.
6 In the dialog box that is displayed, select the MGC profile whose Configured Name is mgcprofile. 7 Click OK. ----End
2.1.5 Adding the Ringing Mapping of MG

Ringing mapping indicates that the MG maps the peer-end parameter (the parameter value of the ringing type) sent by the MGC with a specified ringing mode. After the ringing mapping is added successfully, the MG initiates the ringing based on the ringing mode corresponding to the peer-end parameter sent by the MGC.
Context
l l When the ringing mapping is not configured, the common ringing (NULL) is adopted for all users. You can set the break duration of the ringing mode according to the local standard and up to 16 ringing modes can be set.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Voice Gateway > Media Gateway from the navigation tree. 3 On the Ringing Mapping tab page, set the filter criteria to display the required ringing mapping records. 4 In the information list, right-click and choose Add from the shortcut menu. 5 In the dialog box that is displayed, set MG ID, MGC Ringing, Cadence Ringing Mode and Initial Ringing Mode, as follows.
6 Click OK. ----End
Issue 03 (2010-11-19)
2-7
2.1.6 Starting Up an MG Interface

Cold starting the MG interface so that the MG interface can negotiate with the MGC through the specified MGC protocol. In this case, the MG interface can register with the MGC so that the configured data can take effect.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Voice Gateway > Media Gateway from the navigation tree. 3 On the Media Gateway tab page, set the filter criteria to display the required MGs. 4 Select the MG record to be configured, right-click, and then choose Cold Start (H.248) or Reset (MGCP or SIP). 5 Click Yes. ----End
2.2 Configuring the VoIP Signaling Gateway

The signaling gateway (SG) is used to convert and transmit the signaling, and it converts the signaling system number 7 (SS7) of the ISDN network into the signaling protocol corresponding to the IP network. In this case, the signaling can be exchanged between the IP network and the ISDN network. The SG communicates with the softswitch through SCTP. If the upstream transmission is performed, the SG transmits the signaling that is converted through SCTP to the softswitch. If the downstream transmission is performed, the SG first receives the signaling of the IP network from the softswitch, converts the signaling into SS7 signaling, and then transmits the SS7 signaling to the ISDN network through the PSTN signaling interface. 1. 2.2.1 Adding an SG The SG is used to convert and transmit the signaling, and it converts the signaling system number 7 (SS7) of the ISDN network into the signaling protocol corresponding to the IP network. This topic describes how to add an SG so that the signaling can be exchanged between the IP network and the ISDN network. 2.2.2 Adding an Association An association is a stream control transmission protocol (SCTP) association, which indicates that a logical relationship (channel) for data transmission which is set up by two SCTP endpoints through the four-way startup handshake mechanism of SCTP. An association provides the reliable transmission for the signaling.
2.
2.2.1 Adding an SG
The SG is used to convert and transmit the signaling, and it converts the signaling system number 7 (SS7) of the ISDN network into the signaling protocol corresponding to the IP network. This topic describes how to add an SG so that the signaling can be exchanged between the IP network and the ISDN network.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Voice Gateway > Signaling Gateway from the navigation tree. 3 On the Signaling Gateway tab page, set the filter criteria to display the required SGs. 4 In the information list, right-click and choose Add from the shortcut menu. 5 In the dialog box that is displayed, set the parameters.
6 Click OK. ----End
2.2.2 Adding an Association

An association is a stream control transmission protocol (SCTP) association, which indicates that a logical relationship (channel) for data transmission which is set up by two SCTP endpoints through the four-way startup handshake mechanism of SCTP. An association provides the reliable transmission for the signaling.
Prerequisite
l l l The corresponding SG must exist. For details about how to add an SG, see 2.2.1 Adding an SG. The corresponding MGC profile must exist. For details about how to add an MGC profile, see 2.5 Configuring an MGC Profile. The local IP address used for the association must exist in the IP address pool.
Context
The endpoint of the association can have multiple IP addresses. The SCTP port number of the association endpoint, however, must be unique.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Voice Gateway > Signaling Gateway from the navigation tree. 3 On the Association tab page, set the filter criteria to display the required associations. 4 In the information list, right-click and choose Add from the shortcut menu. 5 In the dialog box that is displayed, set the parameters.
6 Click OK. ----End
2.3 Configuring a V5 Interface

The V5 interface is the standard digital interface between the access network (AN) and the local exchange (LE). The V5 interface supports abundant integrated services access. It supports separation of access and services, thus improving the network structure.
Context
When the UA5000(PVM) uses the PVM card to function as the narrowband control card, the PVM card supports the V5 interface, and provides all the functions of the optical line terminal (OLT) of the narrowband access network. The UA5000(PVM) supports the following two V5 interfaces: l l V5.1 interface manages only one line with 2048 kbit/s, it does not have the line concentration capability and does not support 30B + D mode. V5.2 interface manages 1 to 16 lines with 2048 kbit/s, it has the line concentration capability and supports 30B + D mode.
2-10
1.
2.3.1 Adding a V5 Interface Before you provision services for network elements, you can add the V5 interface according to the global data plan. The V5 interface converts the simulated connection between the switch and the access device into the standardized digital connection. 2.3.2 Adding a 2M Link on a V5 Interface This topic describes how to add a 2M link for a specified V5 interface. After the AN and the LE are connected by an E1 cable, the 2M link with the same ID is enabled. 2.3.3 Adding a C-Channel A communication channel (C-channel) refers to a circuit that is used to transmit the signaling, and the communication channel is used to carry various V5 protocols. 2.3.4 Adding an ISDN C-Channel When the integrated services digital network (ISDN) users in the V5 mode are supported, the ISDN C-channel needs to be added to bear the ISDN D signaling. After this operation is performed successfully, add the corresponding channel on the LE side and keep the parameters consistent on the AN and the LE sides. Then, the ISDN C-channel can be connected physically. 2.3.5 Resetting a V5 Interface This topic describes how to reset a V5 interface to make configuration take effect.
2.
3.
4.
5.
2.3.1 Adding a V5 Interface

Before you provision services for network elements, you can add the V5 interface according to the global data plan. The V5 interface converts the simulated connection between the switch and the access device into the standardized digital connection.
Context
The following parameters of the interconnected AN interface and the LE interface must be consistent. l l l l V5 Interface ID Protocol Version Variable Assignment PSTN C-channel ID
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Voice Gateway > V5 Interface from the navigation tree. 3 On the V5 Interface tab page, set the filter criteria to display the required V5 interfaces. 4 In the information list, right-click and choose Add from the shortcut menu. 5 In the dialog box that is displayed, set the parameters such as Device Name, Name, V5 Interface ID, Interface Type, PSTN C-channel ID, Protocol Version, Variable Assignment, and Timed Start.
Issue 03 (2010-11-19)
2-11
6 Click OK. ----End
2.3.2 Adding a 2M Link on a V5 Interface

This topic describes how to add a 2M link for a specified V5 interface. After the AN and the LE are connected by an E1 cable, the 2M link with the same ID is enabled.
Context
The link parameters on the AN side must be consistent with the link parameters on the LE side. When the links with the same ID on the AN and LE sides are connected by the E1 cable, the link can be used. The link ID must be unique. One V5.1 interface can have only one 2M link, and one V5.2 interface can have up to 16 2M links. In addition, one physical port can have only one 2M link.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Voice Gateway > V5 Interface from the navigation tree. 3 On the V5 Interface tab page, set the filter criteria to display the required V5 interfaces. 4 On the V5 Interface Configuration navigation tree, select a 2M Link node from the V5 interface. In the information list, right-click and choose Add from the shortcut menu.
5 In the dialog box that is displayed, set the physical position and Link ID for the 2M link. 6 Click OK. ----End
2.3.3 Adding a C-Channel

A communication channel (C-channel) refers to a circuit that is used to transmit the signaling, and the communication channel is used to carry various V5 protocols.
Context
The number of C-channels is determined by the number of signaling messages. The sequence of distributing the C-channels is TS16TS15TS31. That is, when TS16s of all links are distributed, if more timeslot is required, TS15 of a certain link is used; if more timeslot is required, TS31 of the same link is used; if more timeslot is required, TS15 of another link is used; if more timeslot is required, TS31 of the same link is used ... In this way, all timeslots are distributed.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Voice Gateway > V5 Interface from the navigation tree. 3 On the V5 Interface tab page, set the filter criteria to display the required V5 interfaces. 4 On the V5 Interface Configuration navigation tree, select the required V5 interface of the device, unfold 2M Link, select the required 2M link, and then choose C-Channel. 5 In the information list, right-click and choose Add from the shortcut menu. 6 In the dialog box that is displayed, set the Time Slot, Protection Group Type, and Logical Cchannel ID parameters as follows.
7 Click OK. ----End

2.3.4 Adding an ISDN C-Channel

When the integrated services digital network (ISDN) users in the V5 mode are supported, the ISDN C-channel needs to be added to bear the ISDN D signaling. After this operation is performed successfully, add the corresponding channel on the LE side and keep the parameters consistent on the AN and the LE sides. Then, the ISDN C-channel can be connected physically.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Voice Gateway > V5 Interface from the navigation tree. 3 On the V5 Interface tab page, set the filter criteria to display the required V5 interfaces. 4 On the V5 Interface Configuration navigation tree, click a V5 interface, and select ISDN Communication Channel. 5 In the information list, right-click and choose Add from the shortcut menu. 6 In the dialog box that is displayed, set Logical C-Channel ID to 0, and D-channel Signaling Type to ISDN D Signaling. 7 Click OK. ----End
2.3.5 Resetting a V5 Interface

This topic describes how to reset a V5 interface to make configuration take effect.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Voice Gateway > V5 Interface from the navigation tree. 3 On the V5 Interface tab page, set the filter criteria to display the required V5 interfaces. 4 In the V5 interface list, right-click a record and choose Maintenance > Reset from the shortcut menu. 5 Click OK. ----End
2.4 Configuring an Impedance Profile

The impedance profile integrates the parameters required for the impedance and the voice gain of a PSTN port. The U2000 manages these parameters through the profile. By setting the impedance and the voice gain of a PSTN port, you can adjust the voice signals of the user phones.
Procedure
1 Choose Configuration > Access Profile Management > Impedance Profile from the main menu. 2 Right-click and choose Add Global Profile from the shortcut menu. 3 In the dialog box that is displayed, set the parameters.
4 Click OK. ----End
2.5 Configuring an MGC Profile

The media gateway controller (MGC) integrates multiple logical function entities, provides the call control and connection of integrated services, and implements integrated services. The MGC profile defines the parameters required for an MGC interface. The U2000 manages the parameters through the profile.
Procedure
1 Choose Configuration > Access Profile Management > MGC Profile from the main menu. 2 Right-click and choose Add Global Profile from the shortcut menu. 3 In the dialog box that is displayed, set the parameters.
Issue 03 (2010-11-19)
2-15
4 Click OK. ----End
2.6 Configuring the UAS Profile

The user agent server (UAS) profile is used to set the parameters of the SIP interface. When configuring the SIP interface, bind this profile to the SIP interface to specify the interface that communicates with the call control. After you configure the UAS profile and bind the profile to the SIP interface, the settings of the SIP interface are complete.
Procedure
1 Choose Configuration > Access Profile Management > UAS Profile from the main menu. 2 Right-click and choose Add Global Profile from the shortcut menu. 3 In the dialog box that is displayed, set the parameters as follows: Set the Name, Alias, IP Address 1, IP Address 2, Proxy Port, Domain Name, and Address Mode parameters.
2-16
Issue 03 (2010-11-19)
4 Click OK. ----End
2.7 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.
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.7.1 Configuring the FoIP and MoIP Attributes Fax over IP (FoIP) or modem over IP (MoIP) is a fax or modem over IP transmission service that is provided between IP networks or between the IP network and the traditional PSTN network. That is, the fax machine or modem is connected to the traditional POTS user terminal to implement the fax or modem service over the IP network. 2.7.2 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.7.1 Configuring the FoIP and MoIP Attributes

Fax over IP (FoIP) or modem over IP (MoIP) is a fax or modem over IP transmission service that is provided between IP networks or between the IP network and the traditional PSTN network. That is, the fax machine or modem is connected to the traditional POTS user terminal to implement the fax or modem service over 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(PVMV1) 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 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 Voice > FoIP/MoIP on the System Parameter Settings navigation tree. 6 In the right pane, set the related parameters according to the plan. 7 Click Finish. ----End
2.7.2 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(PVMV1) 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-18
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(PVM) 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(PVM) 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(PVM) uses master/slave clock synchronization. Clock synchronization is implemented in the following way: 1. The UA5000(PVM) 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(PVM) 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(PVM) supports a maximum of 10 clock sources.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) 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(TDM) 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 VoIP PSTN Service
4
Context
Configuring the VoIP PSTN Service
About This Chapter

This topic describes the principles and features of the VoIP PSTN technology. In addition, this topic describes how to implement the voice service on the UA5000(PVM) and how to configure and manage the PSTN ports.
In the VoIP PSTN service, also called the VoIP service, traditional analog voice signals are specially processed, such as compressed and packetized, and then are transmitted over the IP packet switching network. This reduces the cost of the voice service. 4.1 Configuring Dual Homing When the MGCP protocol is used, one UA5000(PVM) can be configured to belong to three MGCs at the same time. If one MGC is faulty and causes communication loss, the UA5000 (PVM) can switch to next MGC according to the order defined in the standby MGC list. When the H.248 protocol is used, one UA5000(PVM) can be configured to belong to two MGCs at the same time. If one MGC is faulty and causes communication loss, the UA5000(PVM) can switch to another MGC automatically. 4.2 Setting Standalone Parameters When the MG loses communication with the MGC, the standalone function ensures that internal calls are normal under the same MG. 4.3 Setting Authentication Parameters The purpose of authentication is to verify the validity of users and networks. You can use the same authentication algorithm on the MG and MGC sides separately. Then, compare the calculation results on the MG and MGC sides separately. If the calculation results are the same, it indicates that the authentication is successful. If the calculation results are different, it indicates that the authentication fails. 4.4 Setting DMM Parameters A country or region has particular requirements on the duration of various digitmap timers (DMMs). To meet different requirements, you can modify the DMM parameters to set the duration of a DMM. 4.5 Configuring the TID Profile Reference TID stands for the target identifier and is also called terminal ID. The TID is a prefix that a terminal carries when the terminal registers with the MG. The system automatically generates
the TID string according to the TID profile. The MGC can identify the line that a user occupies by using the TID string. 4.6 Setting the TID Prefix Parameters If the TID profile that is bound to the user in an MG interface does not support the layered configuration, you must set the TID field when configuring a user. If the TID profile that is bound to the user in an MG interface supports the layered configuration, you need not set the TID field because the TID field value is automatically generated according to rules. The TID prefix is the prefix of the automatic generation rule. 4.7 Setting Digitmap Parameters A digitmap is a set of digit collection descriptors and it refers to the dialing policies on the MG. The digitmap is used to detect and report dialing events received by terminals. 4.8 Setting the MGC Overload Parameters An MGC needs to handle the calls reported by multiple AGs that the MGC controls. If the call traffic reported by the AGs increases, the MGC may overload. The UA5000(PVM) controls calls in the case of MGC overload and guarantees the priorities of the calls of high-priority users and emergency users. This enhances the reliability and availability of the system. 4.9 Configuring DSP Resources DSP resources refer to the number of DSP channels. The DSP channel is a product of quantifying the processing capability of a DSP chip. That is, use the number of DSP channels to represent the processing capability of a DSP chip. Each DSP channel processes the information carried over a 64K PCM voice channel. 4.10 Configuring Ringing Mapping When the MGC interacts with the UA5000(PVM), they negotiate the ringing mode. The purpose of ringing mapping is to match the peer parameters that the MGC applies to the UA5000 (PVM) to a specified ringing mode. 4.11 Configuring the VoIP PSTN Service This topic describes how to access and configure the VoIP PSTN service. 4.12 Configuration Example of the VoIP PSTN Service This topic provides an example for configuring the VoIP PSTN service in an example network. After the configuration, PSTN users will be able to make calls. 4.13 Configuration Example of the VoIP PSTN Service (SIP) This topic provides an example for configuring the VoIP PSTN service based on SIP protocol in an example network. After the configuration, PSTN users should be able to make calls. 4.14 Configuring the VoIP VAG Service The virtual access gateway (VAG) simulates a physical access gateway (AG) device in the form of multiple virtual AG devices, thus reallocating the AG resources. 4.15 Configuring the MoIP Service The modem over IP (MoIP) is a modem service that is provided between IP networks or between the IP network and the traditional PSTN network. In the NGN network, traditional modems are connected to the voice service ports that the MG provides. Under the control of the MGC, the MG encodes the modem data service that is received, encapsulates the service into packets, and then transmits the packets over the IP network. This implements the modem service. 4.16 Configuring the FoIP Service The fax over IP (MoIP) is a fax service that is provided between IP networks or between the IP network and the traditional PSTN network. In the NGN network, traditional faxes are connected to the voice service ports that the MG provides. Under the control of the MGC, the MG encodes
the fax data service that is received, encapsulates the service into packets, and then transmits the packets over the IP network. This implements the fax service.
Issue 03 (2010-11-19)
4-3
4.1 Configuring Dual Homing

When the MGCP protocol is used, one UA5000(PVM) can be configured to belong to three MGCs at the same time. If one MGC is faulty and causes communication loss, the UA5000 (PVM) can switch to next MGC according to the order defined in the standby MGC list. When the H.248 protocol is used, one UA5000(PVM) can be configured to belong to two MGCs at the same time. If one MGC is faulty and causes communication loss, the UA5000(PVM) can switch to another MGC automatically.
Prerequisite
l l The corresponding MG must exist. To add an MG, see 2.1.2 Adding an MG (H.248/ MGCP). The system uses the MGCP or H.248 protocol.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Voice Gateway > Media Gateway from the navigation tree. 3 On the Media Gateway tab page, set the filter criteria to display the required MGs. 4 Select a record from the MG list, right-click, and then choose Configure MG Software Parameters. 5 If the MGCP protocol is used, in the dialog box that is displayed, set parameters to specify whether the device supports the dual-homing policy. If the dual-homing policy is supported, two options are available, that is, the active MGC automatically switches back and the active MGC does not automatically switch back. If the H.248 protocol is used, in the dialog box that is displayed, set Dual-Homing Policy to Supported without switching back or Supported with switching back.
4-4
Issue 03 (2010-11-19)
6 Click OK. ----End
4.2 Setting Standalone Parameters

When the MG loses communication with the MGC, the standalone function ensures that internal calls are normal under the same MG.
Prerequisite
The corresponding MG must exist. To add an MG, see 2.1.2 Adding an MG (H.248/MGCP).
Context
NOTE
l You can set the standalone parameters only on the devices that support the H.248 protocol. l The standalone function enables the users on the same MG interface to place calls to each other. In other words, the users on different MG interfaces cannot place calls to each other.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Voice Gateway > Media Gateway from the navigation tree. 3 On the Media Gateway tab page, set the filter criteria to display the required MGs.
4 Select a record from the MG list, right-click, and then choose Configure Standalone Parameters. 5 In the dialog box that is displayed, set the parameters such as Dial Tone Duration(s), Ringing Tone Duration(s), and Busy Tone Duration(s).
6 Click OK. ----End
4.3 Setting Authentication Parameters

The purpose of authentication is to verify the validity of users and networks. You can use the same authentication algorithm on the MG and MGC sides separately. Then, compare the calculation results on the MG and MGC sides separately. If the calculation results are the same, it indicates that the authentication is successful. If the calculation results are different, it indicates that the authentication fails.
Prerequisite
The corresponding MG must exist. To add an MG, see 4.3 Setting Authentication Parameters.
Context
NOTE
l l l
The device authentication configuration is optional but it must be the same as the device authentication configured on the MGC. If you use Huawei products such as the SoftX3000 as the MGC, the authentication gateway ID must be a character string that is more than eight digits. If the system uses the H.248 protocol, you can set the authentication parameters of the H.248 protocol. When the system uses the MGCP protocol, you can set the authentication parameters of the MGCP protocol. You need to enable the MG interface in cold mode for it to take effect after the authentication configuration. You need to reset the MG interface for it to take effect after the authentication configuration of the MGCP protocol.
4-6
Issue 03 (2010-11-19)
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Voice Gateway > Media Gateway from the navigation tree. 3 On the Media Gateway tab page, set the filter criteria to display the required MGs. 4 Select a record from the MG list, right-click, and then choose Configure Authentication Parameters. 5 In the dialog box that is displayed, set the related authentication parameters. Set the authentication parameters (H.248), such as Support Authentication, Authentication Initial Key, and Authentication Gateway ID.
6 Click OK. ----End
4.4 Setting DMM Parameters

A country or region has particular requirements on the duration of various digitmap timers (DMMs). To meet different requirements, you can modify the DMM parameters to set the duration of a DMM.
Prerequisite
Issue 03 (2010-11-19)
4-7
Context
NOTE
l l l
The start time of timers varies with the match policy and mode of a specific digitmap. When a user dials a telephone number, the MG starts the long timer if the MG confirms that the telephone number requires at least another digit to match any dialing policy in the digitmap. When a user dials a telephone number, the MG starts the short timer if the telephone number has matched a certain dialing policy in the digitmap but the MG confirms that more digits are required to match the other dialing policies in the digitmap. The start timer is used before any dialed number, that is, the duration from when the user picks up the phone to when the MG receives the first digit. If the start timer is set to 0, it indicates that the MG waits for dialing endlessly.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Voice Gateway > Media Gateway from the navigation tree. 3 On the Media Gateway tab page, set the filter criteria to display the required MGs. 4 Select a record from the MG list, right-click, and then choose Configure DMM Timer. 5 In the dialog box that is displayed, set the related DMM parameters. Set the DMM parameters (H.248) such as Start Timer, Short Timer, Long Timer, and Duration Timer.
6 Click OK. ----End
4.5 Configuring the TID Profile Reference

TID stands for the target identifier and is also called terminal ID. The TID is a prefix that a terminal carries when the terminal registers with the MG. The system automatically generates the TID string according to the TID profile. The MGC can identify the line that a user occupies by using the TID string.
Prerequisite
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Voice Gateway > Media Gateway from the navigation tree. 3 On the Media Gateway tab page, set the filter criteria to display the required MGs. 4 Select a record from the MG list, right-click, and then choose Configure TID Profile References. 5 In the dialog box that is displayed, configure the reference of the TID profiles for terminals. Configuring the reference of the TID profile (H.248)
6 Click OK. ----End
4.6 Setting the TID Prefix Parameters

If the TID profile that is bound to the user in an MG interface does not support the layered configuration, you must set the TID field when configuring a user. If the TID profile that is bound to the user in an MG interface supports the layered configuration, you need not set the TID field because the TID field value is automatically generated according to rules. The TID prefix is the prefix of the automatic generation rule.
Prerequisite
Context
NOTE
The terminal prefix cannot be empty.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Voice Gateway > Media Gateway from the navigation tree. 3 On the Media Gateway tab page, set the filter criteria to display the required MGs. 4 Select a record from the MG list, right-click, and then choose Configure Terminal ID Prefix Parameters. 5 In the dialog box that is displayed, set the parameters of a TID prefix. Setting the parameters of a TID prefix (H.248)
6 Click OK. ----End
4.7 Setting Digitmap Parameters

A digitmap is a set of digit collection descriptors and it refers to the dialing policies on the MG. The digitmap is used to detect and report dialing events received by terminals.
Prerequisite
Context
NOTE
If the MG communicates with the MGC in the normal state, the MGC sends the digitmap. If the MG loses communication with the MGC and the standalone function is enabled on the MG, the MG sends the digitmap.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Voice Gateway > Media Gateway from the navigation tree. 3 On the Media Gateway tab page, set the filter criteria to display the required MGs. 4 Select a record from the MG list, right-click, and then choose Configure Digitmap Parameters. 5 In the dialog box that is displayed, set the digitmap parameters. Setting digitmap parameters (H.248)
6 Click OK. ----End
4.8 Setting the MGC Overload Parameters

An MGC needs to handle the calls reported by multiple AGs that the MGC controls. If the call traffic reported by the AGs increases, the MGC may overload. The UA5000(PVM) controls calls in the case of MGC overload and guarantees the priorities of the calls of high-priority users and emergency users. This enhances the reliability and availability of the system.
Prerequisite
Context
NOTE
l l l
You cannot set the MGC overload parameters if the system uses the MGCP protocol. The default value of Highest Priority Channel Occupancy is 50%. The relationship between the values of three types of channel occupancy is as follows: Highest Priority Channel Occupancy Second Highest Priority Channel Occupancy Normal Priority Channel Occupancy
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Voice Gateway > Media Gateway from the navigation tree. 3 On the Media Gateway tab page, set the filter criteria to display the required MGs. Select a record from the MGC list, right-click, and then choose Configure MGC Overload Parameters. 4 In the dialog box that is displayed, set the parameters.
5 Click OK. ----End

4.9 Configuring DSP Resources

DSP resources refer to the number of DSP channels. The DSP channel is a product of quantifying the processing capability of a DSP chip. That is, use the number of DSP channels to represent the processing capability of a DSP chip. Each DSP channel processes the information carried over a 64K PCM voice channel.
Prerequisite
Context
l l The globally-shared DSP resources refer to the remaining DSP resources of the system with the DSP resources reserved for the MGC excluded. The priorities of user terminals are classified into three types: Cat1: government1 (for Category 1 official users) Cat2: government2 (for Category 2 official users) Cat3: normal (for normal users) l The relationship between the values of three types of channel occupancy is as follows: Highest Priority Channel Occupancy Second Highest Priority Channel Occupancy Normal Priority Channel Occupancy In the descending order, the user priorities are Cat1, Cat2, and Cat3. DSP resources are not reserved for the users with Cat3 priority. The globally-shared DSP resources reserve the DSP channels for official users with Cat1 or Cat2 priority. The remaining globally-shared DSP resources are shared by the users with Cat1, Cat2, or Cat3 priority. You can specify the priority of a user terminal when adding the corresponding user. In addition, you can modify the priority of an existing user. In the case of Category 1 official users, allocate the DSP resources reserved for these users. If the reserved DSP resources are insufficient, allocate the DSP resources reserved for Category 2 official users to Category 1 official users. If more DSP resources are required, allocate the DSP resources of normal users to Category 1 official users. In the case of Category 2 users, allocate the DSP resources reserved for these users. If the reserved DSP resources are insufficient, allocate the DSP resources of normal users to Category 2 official users. The remaining DSP resources are allocated to normal users. If the number of the DSP channels that are configured for an MG interface is 0, it indicates that the DSP resources occupied by the MG interface are deleted. In this case, the MG interface uses the globally-shared DSP resources.
l l
l l
l l
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu.
2 Choose Voice Gateway > Media Gateway from the navigation tree. 3 On the Media Gateway tab page, set the filter criteria to display the required MGs. Select a record from the MG list, right-click, and then choose Configure DSP Resources. 4 In the dialog box that is displayed, set the parameters. Configuring the DSP resources for the MG
Configuring the globally-shared DSP resources
5 Click OK. ----End
4.10 Configuring Ringing Mapping

When the MGC interacts with the UA5000(PVM), they negotiate the ringing mode. The purpose of ringing mapping is to match the peer parameters that the MGC applies to the UA5000 (PVM) to a specified ringing mode.
Prerequisite
Context
NOTE
l l l
In an MG, a peer parameter matches only one ringing mapping record. An MG uses the normal ringing mode if ringing mapping is not configured on the MG. Only 50 ringing mapping records can be configured on a device.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Voice Gateway > Media Gateway from the navigation tree. 3 On the Ringing Mapping tab page, set the filter criteria to display the required ringing mapping records. 4 In the information list, right-click and choose Add from the shortcut menu. 5 In the dialog box that is displayed, set the parameters.
6 Click OK. ----End
4.11 Configuring the VoIP PSTN Service

This topic describes how to access and configure the VoIP PSTN service.
Prerequisite
l l Network devices and lines must be in the normal state. A proper MGC profile must be configured. For details, see "2.5 Configuring an MGC Profile".
Issue 03 (2010-11-19)
l l
The MG interface must be configured. For details, see "2.1.2 Adding an MG (H.248/ MGCP)". The UA5000(PVM) must be able to communicate with the MGC.
Context
The UA5000(PVM) accesses the VoIP PSTN service stream through the voice service card and transmits the service stream upstream to the IP network through the control card, thus implementing the VoIP PSTN service. 4.11.1 Configuring a VoIP PSTN Port This topic describes how to configure the service attributes and the physical attributes of a VoIP PSTN port to provide the required services. 4.11.2 Enabling a VoIP PSTN Port After you configure the attributes of a VoIP PSTN port, you need to enable the port to start services.
4.11.1 Configuring a VoIP PSTN Port

This topic describes how to configure the service attributes and the physical attributes of a VoIP PSTN port to provide the required services.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose ASL > POTS Port from the navigation tree. 3 Click the VoIP PSTN Port tab, and set the filter criteria to display the required VoIP PSTN ports. 4 Select a record from the VoIP PSTN port list, right-click, and then choose Configure Attribute. 5 In the dialog box that is displayed, click the Service Details tab. Configure the attributes of the VoIP PSTN port, including MG ID, Terminal ID, and Tel No..
4-16
Issue 03 (2010-11-19)
6 Click the Physical Details tab. Configure the physical attributes of the VoIP PSTN port, including High Level Width, Low Level Width, Reversed Polarity, and Dial Mode.
7 Click OK. ----End
4.11.2 Enabling a VoIP PSTN Port

After you configure the attributes of a VoIP PSTN port, you need to enable the port to start services.
Issue 03 (2010-11-19)
4-17
Context
NOTE
You can start services only on the VoIP PSTN port whose User Port Configuration is set to VoIP Configured and Authorized.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose ASL > POTS Port from the navigation tree. 3 Click the VoIP PSTN Port tab, and set the filter criteria to display the required VoIP PSTN ports. 4 Select a record from the VoIP PSTN port list, right-click, and then choose Enable Service. 5 Click OK. ----End
4.12 Configuration Example of the VoIP PSTN Service

This topic provides an example for configuring the VoIP PSTN service in an example network. After the configuration, PSTN users will be able to make calls.
Prerequisite
l l l The example network as shown in Figure 4-1 must be complete. Network devices and lines must be in the normal state. The UA5000(PVM) must be able to communicate with the MGC.
Example Network
Phones are connected to the PSTN ports of the UA5000(PVM). The voice service travels upstream to the upper layer network through the upstream ports of the UA5000(PVM).
4-18
Issue 03 (2010-11-19)
Figure 4-1 Example network of the VoIP PSTN service
MGC Router H.248/MGCP
P V M B
P V M B
C S R I
C S R I
UA5000
Phone
Phone Phone
Phone
Data Plan
Table 4-1 provides the data plan for the VoIP PSTN service. Table 4-1 Data plan for the VoIP PSTN service Item MG interface Upstream port Data Subport: 0/4/1 Remarks -
Issue 03 (2010-11-19)
4-19
Item MG interface parameters
Data MG ID: 1 Name: ag1 MG Message MID Type: Signaling IP Address Signaling IP Address: 10.10.10.7 Media IP Address: 10.10.10.7 Signaling Port No.: 2944 Ringing mapping MG ID: 1 Peer Parameter: 1 Cadence Ringing Mode: 2 Initial Ringing Mode: 2
Remarks Configure the MG interface to enable the standalone function. Use default values for the other parameters.
NOTE The MG interface parameters must be the same as the corresponding parameters preset on the MGC.
PSTN user data
Physical location MG ID Terminal ID Tel No.
0/12/0-0/13/31 1 1-64 Phone numbers of users in ports 0/12/0-0/13/31: 5500-5563
Use default values for the other attributes.
Procedure
1 Add an MG interface. 1. In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. Choose Voice Gateway > Media Gateway from the navigation tree. On the Media Gateway tab page, set the filter criteria to display the required MGs. Rightclick the MG list, and then choose Add. In the dialog box that is displayed, set the parameters. l MG ID: 1 l Name: ag1 l MG Message MID Type: Signaling IP Address l Signaling IP Address: 10.10.10.7 l Media IP Address: 10.10.10.7 l Signaling Port No.: 2944 5.
4-20
2. 3. 4.
Click OK.
6.
Select a record from the device list, right-click, and then choose Config MG Software Parameters. Stand Alone Support Flag: All Click OK. On the Ringing Mapping tab page, set the filter criteria to display the required ringing mapping records. Select a record from the device list, right-click, and then choose Add. In the dialog box that is displayed, set the parameters. l MG ID: 1 l Peer Parameter: 1 l Cadence Ringing Mode: 2 l Initial Ringing Mode: 2
7. 8. 9.
10. Click OK. 2 Configure the attributes of the VoIP PSTN port, including the user data and the physical attributes. 1. In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. Choose ASL > POTS Port from the navigation tree. Click the VoIP PSTN Port tab, and set the filter criteria to display the required VoIP PSTN ports. Select ports 0/12/0-0/13/31 in order from the PSTN port list, right-click, and then choose Configure Attribute. In the dialog box that is displayed, click the Service Details tab, and then configure the VoIP PSTN service. l MG ID: 1 l Tel No.: 5500-5563 l Terminal ID: 1-64 6. 7. 1. Click the Physical Details tab. Configure the physical attributes of the VoIP PSTN port. You can use the default values. Click OK. In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. On the tab page that is displayed, click Immediately. Click OK.
NOTE
2. 3. 4. 5.
3 Save the data.
2. 3.
above the navigation tree. Choose Save data
l The U2000 displays the progress of saving the data in the prompt area. l Do not power off or reset the device before the data saving is complete. Otherwise, the data saved in the flash memory is damaged.
4 Verify the configuration of the VoIP PSTN service.

l The caller is able to hear the dialing tone. l When a user calls another user, the callee is able to hear the ringing tone successfully and the caller is able to hear the ring-back tone. l The caller and the callee are able to talk to each other successfully. l The caller is able to hear the busy tone after the callee places the phone on the hook. l If the UA5000(PVM) loses communication with the MGC, the users connected to the UA5000(PVM) are able to call each other. ----End
4.13 Configuration Example of the VoIP PSTN Service (SIP)

This topic provides an example for configuring the VoIP PSTN service based on SIP protocol in an example network. After the configuration, PSTN users should be able to make calls.
Prerequisite
l l l l l The example network as shown in Figure 4-2 must be complete. Network devices and lines must be in the normal state. The UA5000(PVM) must use the SIP protocol. The UA5000(PVM) must be able to communicate with the IMS. The PSTN user data corresponding to the SIP interface must be configured on the IMS.
Example Network
In this example, the device runs in China. The default configurations of system parameters and the overseas feature parameters meet the standard and the application requirements. Therefore, you need not configure these parameters. Phones are connected to the PSTN ports of the UA5000(PVM). The voice service travels upstream to the upper layer network through the upstream ports of the UA5000(PVM).
4-22
Issue 03 (2010-11-19)
Figure 4-2 Example network of the VoIP PSTN service
Data Plan
Table 4-2 provides the data plan for the VoIP PSTN service.
Issue 03 (2010-11-19)
4-23
Table 4-2 Data plan for the VoIP PSTN service (SIP) Item Parameters of the media and the signaling Data The upstream interface of the media stream and the signaling flow: 0/4/0 Media IP address and IP address for the signaling flow: 10.13.4.116 Basic attribute parameters of the SIP interface The SIP interface ID: 0 Name: gw1 Media IP address and signaling IP address: 10.13.4.116 Signaling port ID: 5555 Transmission protocol: UDP Homing domain name: UA5000 (PVM).com UAS Profile Name: uasprofile1 IP address of the main proxy server: 10.13.4.110 IP address of the standby proxy server: 10.13.4.120 Proxy port: 5555 Address Mode: Fix mode Voice service card (ASPB) SIP gateway ID Tel No. Slot of the card: 0/2 Service port: 0/2/0-0/2/63 ID: 0 User phone numbers: 5500-5563 Use default values for the other attributes. Use default values for the other attributes.
NOTE The SIP interface parameters must be the same as the corresponding parameters preset on the IMS.
Remarks -
Procedure
1 Configure the IP interface. l IP Address: 10.13.4.116 l IP Type: Media/Signaling l Gateway: 10.13.4.1 2 Configure the UAS profile. l Name: uasprofile1 l IP Address 1: 10.13.4.110 l IP Address 2: 10.13.4.120 l Proxy Port: 5555
l Address Mode: Fix mode 3 Add a SIP interface. 1. In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. Choose Voice Gateway > Media Gateway from the navigation tree. On the Media Gateway tab page, set the filter criteria to display the required MGs. Rightclick in the list and choose Add from shortcut menu. In the dialog box that is displayed, set the parameters. l MG ID: 0 l Name: gw1 l Media/Signaling IP Address: 10.13.4.116 l Signaling Port No.: 5555 l Transmission Mode: UDP l Homing Domain Name: UA5000(PVM).com l Active NMS UAS Profile: uasprofile1 5. Click OK.
2. 3. 4.
4 Configure the attributes of the VoIP PSTN port (user data and physical attributes of the port). 1. In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. Choose ASL > POTS Port from the navigation tree. Click the VoIP PSTN Port tab, and set the filter criteria to display the required VoIP PSTN ports. Select ports 0/2/0-0/2/63 from the list one by one, right-click, and choose Configure Attribute from shortcut menu. In the dialog box that is displayed, click the Service Details tab, and then configure the VoIP PSTN service. l MG ID: 0 l Tel No.: 5500-5563 6. 7. Click the Physical Details tab and configure the physical attributes of the VoIP PSTN port. In this example, the default values are used. Click OK.
2. 3. 4. 5.
5 Save the data. 1. In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. On the tab page that is displayed, click Immediately. Click OK.
2. 3.
Issue 03 (2010-11-19)
above the navigation tree. Choose Save data

NOTE
l The U2000 displays the progress of saving the data in the prompt area. l Do not power off or reset the device before the data saving is complete. Otherwise, the data saved in the flash memory is damaged.
----End
Result
After the configuration, users of Phone 0-Phone 63 can communicate with each other successfully. l l l l The calling party can hear the dialing tone after picking up the phone. When the calling party dials the phone number of the called party, the phone of the called party can ring normally, and the calling party can hear the ring-back tone. The calling party and the called party can communicate in the normal state. After the called party hooks on, the calling party can hear the busy tone.
4.14 Configuring the VoIP VAG Service

The virtual access gateway (VAG) simulates a physical access gateway (AG) device in the form of multiple virtual AG devices, thus reallocating the AG resources.
Prerequisite
l l l l l Network devices and lines must be in the normal state. The system uses the H.248 or MGCP protocol. A proper MGC profile must be configured. For details, see 2.5 Configuring an MGC Profile. The MG interface must be configured. For details, see 2.1.2 Adding an MG (H.248/ MGCP) or 2.1.3 Adding an MG (SIP). The UA5000(PVM) must be able to communicate with the MGC.
Context
The UA5000(PVM) supports the VAG function as an AG device. One UA5000(PVM) can support up to eight VAGs.
NOTE
l The MG interface parameter must be the same as the related parameters preset on the MGC. l The cadence ringing mode and the initial ringing mode comply with local standards.
Procedure
1 Configure the VoIP PSTN user in VAG1. For details, see 4.12 Configuration Example of the VoIP PSTN Service or 4.13 Configuration Example of the VoIP PSTN Service (SIP).
NOTE
VAG1 does not support the standalone function. The telephone numbers range from 12345000 to 12345031.
2 Configure the VoIP PSTN user in VAG2. For details, see 4.12 Configuration Example of the VoIP PSTN Service or 4.13 Configuration Example of the VoIP PSTN Service (SIP).
NOTE
VAG2 supports the standalone function. The internal telephone digitmap (the standalone switching digitmap) is 12345xxx. The telephone numbers range from 12345032 to 12345063.
3 Verify the configuration of the VoIP VAG service. l Any two users in VAG1 are able to call each other. The caller is able to hear the dialing tone. When a user calls another user, the callee is able to hear the ringing tone and the caller is able to hear the ring-back tone. The caller and the callee are able to talk to each other. The caller is able to hear the busy tone after the callee places the phone on the hook. l Any two users in VAG2 are able to call each other. The caller is able to hear the dialing tone. When a user calls another user, the callee is able to hear the ringing tone successfully and the caller is able to hear the ring-back tone. The caller and the callee are able to talk to each other successfully. The caller is able to hear the busy tone after the callee places the phone on the hook. l Users in VAG1 and VAG2 are able to place calls to each other. The caller is able to hear the dialing tone. When a user calls another user, the callee is able to hear the ringing tone successfully and the caller is able to hear the ring-back tone. The caller and the callee are able to talk to each other successfully. The caller is able to hear the busy tone after the callee places the phone on the hook. l If the MG loses communication with the MGC, the users whose telephone numbers range from 12345000 to 12345031, that is, users in VAG1, cannot place calls to each other. l If the MG loses communication with the MGC, the users whose telephone numbers range from 12345032 to 12345063, that is, users in VAG2, can place calls to each other. ----End
4.15 Configuring the MoIP Service

The modem over IP (MoIP) is a modem service that is provided between IP networks or between the IP network and the traditional PSTN network. In the NGN network, traditional modems are connected to the voice service ports that the MG provides. Under the control of the MGC, the MG encodes the modem data service that is received, encapsulates the service into packets, and then transmits the packets over the IP network. This implements the modem service.
Prerequisite
l l l Network devices and lines must be in the normal state. The MG interface must be configured. For details, see 2.1.2 Adding an MG (H.248/ MGCP) or 2.1.3 Adding an MG (SIP). The VoIP user must be configured. For details, see4.11.1 Configuring a VoIP PSTN Port.
Issue 03 (2010-11-19)
The voice service port for the MoIP service must be in the normal state, and the voice service of this port must be normal.
Procedure
l Configuration flow of MoIP service under the MGCP/H.248: 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(PVMV1) 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. Select Voice > FoIP/MoIP from the System Parameter Settings navigation tree, and then set the parameters, such as Modem transmission mode, Modem event mode, and Switch of Modem capacity startup RFC2198.
6. 7. l 1.
In the information list, right-click the record and choose Download to NE from the shortcut menu. In the dialog box that is displayed, select the required NE(s), and click OK. In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. Choose Voice Gateway > Media Gateway from the navigation tree. On the Media Gateway tab page, set the filter criteria to display the required MGs.
Configuration flow of MoIP service under the SIP:
2. 3.
4-28
Issue 03 (2010-11-19)
4. 5.
Select a record from the MG list, right-click, and then choose Config FoIP/MoIP Parameters. In the dialog box that is displayed, set the parameters.
6. ----End
Click OK.
4.16 Configuring the FoIP Service

The fax over IP (MoIP) is a fax service that is provided between IP networks or between the IP network and the traditional PSTN network. In the NGN network, traditional faxes are connected to the voice service ports that the MG provides. Under the control of the MGC, the MG encodes the fax data service that is received, encapsulates the service into packets, and then transmits the packets over the IP network. This implements the fax service.
Prerequisite
l l l l Network devices and lines must be in the normal state. The MG interface must be configured. For details, see 2.1.2 Adding an MG (H.248/ MGCP) or 2.1.3 Adding an MG (SIP). The VoIP user must be configured. For details, see4.11.1 Configuring a VoIP PSTN Port. The voice service port for the FoIP service must be in the normal state, and the voice service of this port must be normal.
Context
Table 4-3 describes the fax modes that the UA5000(PVM) supports.
Table 4-3 Fax modes supported by the UA5000(PVM) (H.248/MGCP) Fax Mode V2 T38 Description If the fax service is implemented under the same gateway, you can configure the T.38 fax port at random. If the fax service is implemented across gateways, you need to increase the number of the T.38 fax port by two. Ensure that the numbers of the T.38 fax ports in two gateways are the same. That is, you need to increase the numbers of the two T.38 fax ports by two for each or you do not increase the numbers of the two T. 38 fax ports at the same time. When the T.38 mode is used, the training modes must be the same at the two ends of the gateway. That is, configure the remote training mode or the local training mode at the two ends of the gateway. In this case, the fax service in the T.38 mode is successful. It is recommended that you use the remote training mode at the two ends. V3 flow All the fax processes of MGs are controlled by the MGC. The MGC applies the training mode, coding mode, and port number to the MG. All the fax processes of MGs are controlled by the MGC. The MGC applies the training mode, coding mode, and port number to MGs. If the MGC uses the T.38 mode, the fax port number can be negotiated. For example, the fax port number can be voice port number at one end, and the fax port number can be the sum of the voice port number plus two at the other end. Selfswitch thoroughly You need to configure the fax mode only on the MG. The training modes must be the same at the two ends of the gateway. That is, configure the remote training mode or the local training mode at the two ends of the gateway. It is recommended that you use the remote training mode at the two ends. V5 flow All the fax processes of MGs are controlled by the MGC. The MGC applies the training mode, coding mode, and port number to MGs. The V5 flow mode is compatible with the thoroughly mode and the V3 flow mode. For example, the thoroughly or V3 flow mode is configured on the peer end, and the V5 flow mode is configured on the local end. When the fax service is implemented, the two ends can communicate. When the MGC communicates with the MG in the normal state, the MG uses the self-negotiation T.38 mode to implement the FoIP service. When the MGC breaks down, the MG implements the FoIP service in the selfswitch thoroughly mode.
Selfswitch T38
4-30
Issue 03 (2010-11-19)
Fax Mode V2 Thoroughly
Description When the V2 thoroughly mode is used, the MG uses the voice service port as the fax port to access the T30 fax packets, encodes the fax packets in the G.711 mode, bears the fax packets in the G.711 codes, and then transmits the fax packets transparently to the peer end.
Procedure
l Configuration flow of FoIP service under the MGCP/H.248: 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(PVMV1) from the Device Type drop-down list. In the information list, right-click and choose Add 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. Select Voice > FoIP/MoIP from the System Parameter Settings navigation tree, and then set the parameters, such as Fax transmission mode, T38 fax port, Negotiate mode of fax, Negotiate flow of fax, and Packet switch of Fax transparent 10ms.
6. 7. l
Issue 03 (2010-11-19)
In the information list, right-click the record and choose Download to NE from the shortcut menu. In the dialog box that is displayed, select the required NE(s), and click OK.
Configuration flow of FoIP service under the SIP:

1.
In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. Choose Voice Gateway > Media Gateway from the navigation tree. On the Media Gateway tab page, set the filter criteria to display the required MGs. Select a record from the MG list, right-click, and then choose Config FoIP/MoIP Parameters. In the dialog box that is displayed, set the parameters.
2. 3. 4. 5.
6. ----End
Click OK.
4-32
Issue 03 (2010-11-19)
5 Configuring the VoIP ISDN Service
5
Context
Configuring the VoIP ISDN Service
About This Chapter

This topic describes how to configure the VoIP ISDN service and how the voice service is implemented on the UA5000(PVM).
The integrated services digital network (ISDN) is a CCITT standard and is developed from the integrated digital network (IDN). The ISDN network can support the end to end digital connection to implement various telecom services, such as the voice service and non-voice service. The VoIP ISDN service implements the ISDN access function under the control of the H.248 protocol or the MGCP protocol. In this case, the VoIP ISDN service provides the integrated voice, video and the data service for users. 5.1 Configuring the VoIP ISDN BRA Service The VoIP ISDN BRA service indicates that the ISDN BRA user on the MG side uses the ISDN basic rate interface to implement the access under the control of the H.248 protocol or the MGCP protocol. In addition, the ISDN service is transmitted to the next generation network (NGN) to implement the point-to-point (P2P) or point-to-multipoint (P2MP) multimedia communication of the voice, image, and data over the IP networking. 5.2 Configuring the VoIP ISDN PRA Service The VoIP ISDN PRA service indicates that the ISDN PRA user on the MG side uses the ISDN basic rate interface to implement the access under the control of the H.248 protocol or the MGCP protocol. In addition, the ISDN service is transmitted the next generation network (NGN) to implement the multimedia communication of the voice, image, and data over the IP networking. 5.3 Configuration Example of the VoIP ISDN BRA Service This topic provides an example for configuring the VoIP ISDN BRA service in an example network. After the configuration, ISDN BRA users should be able to make calls. 5.4 Configuration Example of the VoIP ISDN PRA Service This topic provides an example for configuring the VoIP ISDN PRA service in an example network. After the configuration, ISDN PRA users should be able to make calls.
Issue 03 (2010-11-19)
5-1
5.1 Configuring the VoIP ISDN BRA Service

The VoIP ISDN BRA service indicates that the ISDN BRA user on the MG side uses the ISDN basic rate interface to implement the access under the control of the H.248 protocol or the MGCP protocol. In addition, the ISDN service is transmitted to the next generation network (NGN) to implement the point-to-point (P2P) or point-to-multipoint (P2MP) multimedia communication of the voice, image, and data over the IP networking.
Prerequisite
l l The corresponding MG must be configured. For details about how to configure the MG, see 2.1 Configuring the VoIP Media Gateway. The corresponding SG must be configured. For details about how to configure the SG, see 2.2 Configuring the VoIP Signaling Gateway.
Context
The basic rate access (BRA) provides two B-channels with the rate of 64 kbit/s and one Dchannel with the rate of 16 kbit/s. The B-channel is mainly used to carry the service, and the Dchannel is mainly used to transmit the call control signaling and the maintenance and management signaling. 5.1.1 Configuring the Attributes of a VoIP ISDN BRA Port To configure the attributes of a VoIP ISDN BRA port and make the port meet the requirements, perform this operation.
5.1.1 Configuring the Attributes of a VoIP ISDN BRA Port

To configure the attributes of a VoIP ISDN BRA port and make the port meet the requirements, perform this operation.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose DSL > ISDN(BRA) Port from the navigation tree. 3 Click the VoIP BRA Port tab, and set the filter criteria to display the required VoIP ISDN BRA ports. Select a record to be configured from the list, right-click, and then choose Configure Attribute. 4 In the dialog box that is displayed, select the device, and then set the attributes of the port as follows.
5-2
Issue 03 (2010-11-19)
NOTE
The BRA works in the P2MP or P2P mode. l In the P2P working mode, one network terminal (NT) can connect to only one terminal, and the L2 link is always in the setup state to ensure that the service can be carried at any time. l In the P2MP working mode, one NT can connect to multiple terminals, two L2 links can be set up concurrently, and a maximum of two users can call concurrently. If no call service is processed, the terminals can be deactivated automatically to save the power.
Issue 03 (2010-11-19)
5-3
5 Click OK. ----End
5.2 Configuring the VoIP ISDN PRA Service

The VoIP ISDN PRA service indicates that the ISDN PRA user on the MG side uses the ISDN basic rate interface to implement the access under the control of the H.248 protocol or the MGCP protocol. In addition, the ISDN service is transmitted the next generation network (NGN) to implement the multimedia communication of the voice, image, and data over the IP networking.
Prerequisite
l l The corresponding MG must be configured. For details about how to configure the MG, see 2.1 Configuring the VoIP Media Gateway. The corresponding SG must be configured. For details about how to configure the SG, see 2.2 Configuring the VoIP Signaling Gateway.
Context
The primary rate access (PRA) provides one D-channel and 23 (T1) or 30 (E1) B-channels. Each channel is with the rate of 64 kbit/s. The B-channel is mainly used to carry the service, and the D-channel is mainly used to transmit the call control signaling and the maintenance and management signaling. 5.2.1 Configuring the CRC4 To configure the CRC4 for the E1 port, perform this operation. The method for CRC4 must be the same with that for the LE. 5.2.2 Configuring the Working Mode of the EDTB Card To configure an EDTB card to work in the independent mode, perform this operation. After the working mode of the card is configured, you can configure services to the card. 5.2.3 Configuring the Attributes of a VoIP ISDN PRA Port To configure the attributes of a VoIP ISDN PRA port and make the port meet the requirements, perform this operation.
5.2.1 Configuring the CRC4

To configure the CRC4 for the E1 port, perform this operation. The method for CRC4 must be the same with that for the LE.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose E1/T1 > TDM E1/T1 Port from the navigation tree. 3 Click the TDM E1 Port tab and enter the filter criteria to display the required TDM E1 ports. 4 In the port list, right-click a record and choose Modify from the shortcut menu.
5 In the dialog box that is displayed, set CRC4 to Enable. 6 Click OK. ----End
5.2.2 Configuring the Working Mode of the EDTB Card

To configure an EDTB card to work in the independent mode, perform this operation. After the working mode of the card is configured, you can configure services to the card.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) 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 the required EDTB card in the shelf view and choose Config Work Mode from the shortcut menu. 4 In the dialog box that is displayed, set Board Work Mode to VOICE or SATOP. 5 Click OK. ----End
5.2.3 Configuring the Attributes of a VoIP ISDN PRA Port

To configure the attributes of a VoIP ISDN PRA port and make the port meet the requirements, perform this operation.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose E1/T1 > TDM E1/T1 Port from the navigation tree. 3 Click the VoIP ISDN PRA Port tab, and set the filter criteria to display the required VoIP ISDN PRA ports. 4 In the port list, right-click a record to be configured and choose Configure Attribute from the shortcut menu. 5 In the dialog box that is displayed, select the device, and then set the attributes of the D-channel and B-channel of the port as follows.
Issue 03 (2010-11-19)
5-5
6 Click OK. ----End
5.3 Configuration Example of the VoIP ISDN BRA Service

This topic provides an example for configuring the VoIP ISDN BRA service in an example network. After the configuration, ISDN BRA users should be able to make calls.
Prerequisite
The UA5000(PVM) must be able to communicate with the MGC. The ISDN digital telephone must support the P2P function.
Context
Example Network Figure 5-1 shows an example network for configuring the VoIP ISDN BRA service.
5-6
Issue 03 (2010-11-19)
Figure 5-1 Example network for configuring the VoIP ISDN BRA service
MGC Router
H.248/MGCP 0/7 UA5000 I P M B I P M B P V M B P V M B D S L
NT1
ISDN phone
ISDN phone
Data Plan Table 5-1 lists the data plan for the VoIP ISDN BRA service.
Issue 03 (2010-11-19)
5-7
Table 5-1 Data plan for the VoIP ISDN BRA service Item MGC profile Data Name: mgcprofile Protocol type: H.248 IP Address 1: 10.10.10.10 Port ID: 2944 MG interface MG ID: 1 Name: ag1 MG Message MID Type: Signaling IP Address Signaling IP Address: 10.10.10.7 Media IP Address 1: 10.10.10.7 Signaling Port Number: 2944 Peer Parameter ID: 6 Cadence Ringing Type: NULL Initial Ringing Type: NULL SG ID: 1 Association ID: 0 MGC profile l Name: xuaprofile l Protocol type: xUA l IP Address: 10.10.10.7 l Port ID: 2944 Local Port: 9900 ISDN BRA ports Physical location Working mode Tel No. 0/7/0-0/7/1 P2P 12345000 and 12345001 Use default values for the other attributes. Use default values for the other attributes. Remarks -
Procedure
1 Configure the MGC profile.
5-8
Issue 03 (2010-11-19)
1. 2.
Choose Configuration > Access Profile Management > MGC Profile from the main menu. Right-click and choose Add Global Profile from the shortcut menu. In the dialog box that is displayed, set the parameters. Set the parameters as follows: l Name: mgcprofile l Protocol type: H.248 l IP Address 1: 10.10.10.10 l Port ID: 2944
NOTE
Repeat this step to add an MGC profile by setting Name to xuaprofile, Protocol type to xUA, and IP Address to 10.10.10.7.
3.
Click OK.
2 Add an MG interface. 1. In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. Choose Voice Gateway > Media Gateway from the navigation tree. On the Media Gateway tab page, set the filter criteria to display the required MGs. Rightclick in the MG list, and choose Add from the shortcut menu. In the dialog box that is displayed, set the parameters. l MG ID: 1 l Name: ag1 l MG Message MID Type: Signaling IP Address l Signaling IP Address: 10.10.10.7 l Media IP Address 1: 10.10.10.7 l Signaling Port No.: 2944 5. Click OK.
2. 3. 4.
3 Configure the MGC. 1. 2. 3. Click MGC Information tab in the lower pane,Right-click a record and choose Modify from the shortcut menu. In the dialog box that is displayed, select the profile whose Name is mgcprofile. Click OK.
4 Add the ringing mapping. 1. Click Ringing Mapping tab in the pane, In the information list, right-click and choose Add from the shortcut menu. In the dialog box that is displayed, set the parameters. Configure the parameters as follows: l MG ID: 1 l Peer Parameter ID: 6 l Cadence Ringing Type: NULL
l Initial Ringing Type: NULL 2. 1. Click OK. On the Media Gateway tab page, set the filter criteria to display the required MGs. Click Filter to display the MG whose MG ID is 1. Right-click a record to be started in the list and choose Cold Start from the shortcut menu. Click OK. On the Signaling Gateway tab page, set the filter criteria to display the required SGs. Click Signal Gateway tab in the pane, In the information list, right-click and choose Add from the shortcut menu. In the dialog box that is displayed, set the parameters. Set the parameters as follows: l SG ID: 1 l Penging Time: 4 l Work mode: Override l MG ID: 1 4. 1. 2. Click OK. Click Association tab in the pane, In the information list, right-click and choose Add from the shortcut menu. In the dialog box that is displayed, set the parameters. Parameter settings: l Association ID: 0 l SG ID: 1 l Local IP: 10.10.10.7 l Local Port: 9900 l Profile Name: xuaprofile 3. 1. 2. Click OK. Choose DSL > ISDN(BRA) Port from the navigation tree. Click the VoIP BRA Port tab, and set the filter criteria to display the required VoIP ISDN BRA ports. Select ports 0/7/0 and 0/7/1 from the list, right-click, and then choose Configure Attribute from the shortcut menu. In the dialog box that is displayed, set the parameters. Set the parameters as follows: l MG ID: 1 l SG ID: 1 l Association ID: 0 l Interface ID: 1 with the step of 1
5 Start the MG interface.
2. 1. 2. 3.
6 Add the SG.
7 Add the association.
8 Configure the attributes of the VoIP ISDN BRA port.
3.
l Tel No.: 12345000 with the step of 1 l Working Mode: P2P 4. 1. 2. Click OK. In the Main Topology, choose UA5000(PVMV1) from the navigation tree, right-click, and then choose Save Data Immediately from the shortcut menu. Click OK.
NOTE
9 Save the data.
l When saving the data, the U2000 displays the progress of saving the data in the prompt area. l Do not power off or reset the device before the data is saved completely. Otherwise, the data saved in the flash memory is lost.
10 Verify the configuration of the VoIP ISDN BRA service. After the configuration, the ISDN BRA user connected to port 0/7/0 and the ISDN BRA user connected to port 0/7/1 should be able to communicate successfully. In addition, these two ports are always in the activated state. ----End
5.4 Configuration Example of the VoIP ISDN PRA Service

This topic provides an example for configuring the VoIP ISDN PRA service in an example network. After the configuration, ISDN PRA users should be able to make calls.
Prerequisite
The UA5000(PVM) must be able to communicate with the MGC.
Context
Example Network Figure 5-2 shows an example network for configuring the VoIP ISDN PRA service.
Issue 03 (2010-11-19)
5-11
Figure 5-2 Example network for configuring the VoIP ISDN PRA service
MGC
Router FE/GE I I P P P P V V M M M M B B B B
Router 0/7 E D T B
UA5000
UA5000
PBX
Phone A
Phone N
Phone N+1
Data Plan Table 5-2 lists the data plan for the VoIP ISDN PRA service. Table 5-2 Data plan for the VoIP ISDN PRA service Item MGC profile Data Name: mgcprofile Protocol type: H.248 IP Address 1: 10.10.10.10 Port number: 2944 Remarks -
5-12
Issue 03 (2010-11-19)
Item MG interface
Data MG ID: 1 Name: ag1 MG Message MID Type: Signaling IP Address Signaling IP Address: 10.10.10.7 Media IP Address 1: 10.10.10.7 Signaling Port Number: 2944 Peer Parameter ID: 6 Cadence Ringing Type: NULL Initial Ringing Type: NULL SG ID: 1 Association ID: 0 MGC profile l Name: xuaprofile l Protocol type: xUA l IP Address: 10.10.10.7 l Port number: 2944 Local Port: 9900
Remarks Use default values for the other attributes.
ISDN PRA ports
Physical location Terminal ID Overload Priority
0/7/0-0/7/1 Terminal ID Auto Selected Cat1
Use default values for the other attributes. -
Procedure
1 Configure the MGC profile. 1. 2. Choose Configuration > Access Profile Management > MGC Profile from the main menu. Right-click and choose Add Global Profile from the shortcut menu. In the dialog box that is displayed, set the parameters. Set the parameters as follows: l Name: mgcprofile l Protocol type: H.248
l IP: 10.10.10.10 l Port number: 2944

NOTE
Repeat this step to add an MGC profile by setting Name to xuaprofile, Protocol type to xUA, and IP Address 1 to 10.10.10.7.
3. 1. 2.
Click OK. Choose Voice Gateway > Media Gateway from the navigation tree. Click Media Gateway tab in the pane, In the information list, right-click and choose Add from the shortcut menu. In the dialog box that is displayed, set the parameters. Set the parameters as follows: l MG ID: 1 l Name: ag1 l MG Message MID Type: Signaling IP Address l Signaling IP Address: 10.10.10.7 l Media IP Address 1: 10.10.10.7 l Signaling Port Number: 2944
2 Add an MG interface.
3. 1. 2. 3. 1.
Click OK. Click MGC Information tab in the lower pane,Right-click a record and choose Modify from the shortcut menu. In the dialog box that is displayed, select the profile whose Name is mgcprofile. Click OK. Click Ringing Mapping tab in the pane, In the information list, right-click and choose Add from the shortcut menu. In the dialog box that is displayed, set the parameters. Set the parameters as follows: l MG ID: 1 l Peer Parameter ID: 6 l Cadence Ringing Type: NULL l Initial Ringing Type: NULL
3 Configure the MGC.
4 Add the ringing mapping.
2. 1.
Click OK. On the Media Gateway tab page, set the filter criteria to display the required MGs. Click Filter to display the MG whose MG ID is 1. Right-click a record to be started and choose Cold Start from the shortcut menu. Click OK. On the Signaling Gateway tab page, set the filter criteria to display the required SGs. Click Signal Gateway tab in the pane, In the information list, right-click and choose Add from the shortcut menu. In the dialog box that is displayed, set the parameters.
5 Start the MG interface.
2. 1. 2.
6 Add the SG.
5-14
Set the parameters as follows: l SG ID: 1 l Penging Time: 4 l Work mode: Override l MG ID: 1 3. Click OK.
7 Add the association. 1. 2. Click Association tab in the pane, In the information list, right-click and choose Add from the shortcut menu. In the dialog box that is displayed, set the parameters. Parameter settings: l Association ID: 0 l SG ID: 1 l Local IP: 10.10.10.7 l Local Port: 9900 l Profile Name: xuaprofile 3. Click OK.
8 Configure the attributes of the VoIP ISDN PRA port. 1. 2. Choose E1/T1 > TDM E1/T1 Port from the navigation tree. Click the VoIP ISDN PRA Port tab, and set the filter criteria to display the required VoIP ISDN PRA ports. Select ports 0/7/0 and 0/7/1 from the list, right-click, and then choose Configure Attribute from the shortcut menu. In the dialog box that is displayed, set the parameters. Set the parameters as follows: l MG ID: 1 l SG ID: 1 l Interface ID: 1 with the step of 1 l Terminal ID: Terminal ID Auto Selected 4. Click OK.
3.
9 Save the data. 1. 2. In Main Topology, choose UA5000(PVMV1) from the navigation tree, right-click, and choose Save Data Immediately from the shortcut menu. Click OK.
NOTE
l When saving the data, the U2000 displays the progress of saving the data in the prompt area. l Do not power off or reset the device before the data is saved completely. Otherwise, the data saved in the flash memory is lost.
10 Verify the configuration of the VoIP ISDN PRA service.

After the configuration, the ISDN PRA user connected to port 0/7/0 and the ISDN PRA user connected to port 0/7/1 should be able to communicate successfully. In addition, these two ports are always in the activated state. ----End
5-16
Issue 03 (2010-11-19)
6 Configuring the V5 ISDN Service
6
Context
Configuring the V5 ISDN Service
About This Chapter

This topic describes how to configure the V5 ISDN service and describes how the voice service can be implemented according to the UA5000(PVM).
The Integrated services digital network (ISDN) is a CCITT standard and is developed from the integrated digital network (IDN). The ISDN network can support the end-to-end digital connection to implement various telecommunications services, such as the voice service and non-voice service. The V5 ISDN service implements the ISDN access function under the control of the LE. In this case, the V5 ISDN service provides the integrated voice, video and data services for users. 6.1 Introduction to the V5 ISDN Service The integrated services digital network (ISDN) accesses voice services and non-voice services by providing the limited, standard, and multipurpose user-network interfaces. 6.2 Configuring the V5 ISDN BRA Service This topic describes how to access the V5 ISDN BRA user through the DSL service card of the UA5000(PVM), and how to configure parameters for users so that the users can communicate with each other. 6.3 Configuring the V5 ISDN PRA Service This topic describes how to access the V5 ISDN PRA user through the PVMB control card or the EDTB service card of the UA5000(PVM), and how to configure parameters for users so that the users can communicate with each other.
Issue 03 (2010-11-19)
6-1
6.1 Introduction to the V5 ISDN Service

The integrated services digital network (ISDN) accesses voice services and non-voice services by providing the limited, standard, and multipurpose user-network interfaces.
Service Description
The International Telegraph and Telephone Consultative Committee (CCITT) define the IDSN as a network evolving from the integrated digital network. It can provide the end-to-end digital connection to support the various telecommunications services, including the voice services and non-voice services. According to the user-network interface model, the ISDN provides two types of user-network interfaces: l The ISDN basic rate interface (BRI) supports an aggregate data rate of 144 kbit/s, including two B-channels used to bear services and one D-channel used to transmit the call control signaling and maintenance management signaling. The rate of the B-channel is 64 kbit/s and the rate of the D-channel is 16 kbit/s. The ISDN primary rate interface (PRI) supports an aggregate data rate of 2048 kbit/s, including 30 B-channels and 2 D-channels. The rates of the B-channel and the D-channel are 64 kbit/s.
In the upstream direction, the UA5000(PVM) supports the networking through the V5 interface so that the ISDN service can access the LE.
Service Specifications
The UA5000(PVM) provides the ISDN BRI interface through the DSL card, the voice and data services for the resident users, and implements the V5 ISDN basic rate access (BRA) service. The UA5000(PVM) provides the ISDN PRI interface through the PVMB, PVMD, or EDTB card, connects to devices such as the private branch exchange (PBX) that is compatible with the E1 interface, provides the voice, video, and data services for the commercial users, and implements the V5 ISDN primary rate access (PRA) service. Table 6-1 lists the number of ISDN BRA ports provided by service cards. Table 6-1 Number of ISDN BRA ports provided by service cards Card DSLD, DSLE DSL Port Quantity 16 ISDN BRA ports 8 ISDN BRA ports
Table 6-2 lists the number of ISDN PRA ports provided by service cards.
6-2
Issue 03 (2010-11-19)
Table 6-2 Number of ISDN PRA ports provided by service cards Card PVMB, PVMD EDTB Port Quantity 4 ISDN PRA ports 16 ISDN PRA ports
6.2 Configuring the V5 ISDN BRA Service

This topic describes how to access the V5 ISDN BRA user through the DSL service card of the UA5000(PVM), and how to configure parameters for users so that the users can communicate with each other.
Prerequisite
l l l The DSL card must be added to the UA5000(PVM) and must work in the normal state. The corresponding V5 interface and the channel must exist in the system. For details about the operations, see 2.3 Configuring a V5 Interface. The configuration on the LE must be correct.
6.2.1 Configuring the V5 ISDN BRA Service This topic describes how to access the V5 ISDN BRA user through the DSL card of the UA5000 (PVMV1), and how to configure parameters for users so that the users can communicate with each other.
6.2.1 Configuring the V5 ISDN BRA Service

This topic describes how to access the V5 ISDN BRA user through the DSL card of the UA5000 (PVMV1), and how to configure parameters for users so that the users can communicate with each other.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose DSL > ISDN(BRA) Port from the navigation tree. 3 Click the V5 BRA Port tab, and set the filter criteria to display the required V5 BRA ports. right-click a port to be configured and choose Configure Attribute from the shortcut menu. 4 In the dialog box that is displayed, set the parameters and determine whether the remote power supply should be adopted or whether the EF address needs to be allocated automatically, as follows.
Issue 03 (2010-11-19)
6-3
5 Click OK. ----End
6.3 Configuring the V5 ISDN PRA Service

This topic describes how to access the V5 ISDN PRA user through the PVMB control card or the EDTB service card of the UA5000(PVM), and how to configure parameters for users so that the users can communicate with each other.
Prerequisite
l l l The DSL card must be added to the UA5000(PVM) and must work in the normal state. The corresponding V5 interface and the channel must exist in the system. For details about the operations, see 2.3 Configuring a V5 Interface. The configuration on the LE must be correct.
6.3.1 Configuring the CRC4 To configure the CRC4 for the E1 port, perform this operation. The method for CRC4 must be the same with that for the LE. 6.3.2 Configuring the Working Mode of the EDTB Card To configure an EDTB card to work in the independent mode, perform this operation. After the working mode of the card is configured, you can configure services for the card. 6.3.3 Configuring a V5 ISDN PRA User To configure the attributes of a V5 ISDN PRA port and make the port meet the requirements, perform this operation.
6.3.1 Configuring the CRC4

To configure the CRC4 for the E1 port, perform this operation. The method for CRC4 must be the same with that for the LE.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose E1/T1 > TDM E1/T1 Port from the navigation tree. 3 Click the TDM E1 Port tab and enter the filter criteria to display the required TDM E1 ports. 4 In the port list, right-click a record and choose Modify from the shortcut menu. 5 In the dialog box that is displayed, set CRC4 to Enable. 6 Click OK. ----End
6.3.2 Configuring the Working Mode of the EDTB Card

To configure an EDTB card to work in the independent mode, perform this operation. After the working mode of the card is configured, you can configure services for the card.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 On the tab page that is displayed, choose NE Panel from the navigation tree. Double-click the shelf in the right pane to display the shelf view. 3 In the shelf view, right-click the required EDTB card and choose Config Work Mode from the shortcut menu. 4 In the dialog box that is displayed, set Work Mode to Independent. 5 Click OK. ----End
6.3.3 Configuring a V5 ISDN PRA User

To configure the attributes of a V5 ISDN PRA port and make the port meet the requirements, perform this operation.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose E1/T1 > TDM E1/T1 Port from the navigation tree. 3 Click the V5 ISDN PRA Port tab and enter the filter criteria to display the required V5 ISDN PRA ports.
4 In the port list, right-click a port to be configured and choose Configure Attribute from the shortcut menu. 5 In the dialog box that is displayed, set the parameters and determine whether the EF address needs to be allocated automatically, as follows.
6 Click OK. ----End
6-6
Issue 03 (2010-11-19)
7 Configuring the V5 PSTN Service
7
Prerequisite
l l l
Configuring the V5 PSTN Service
About This Chapter

This topic describes how to configure the V5 PSTN service. After you configure the V5 interface and V5 voice user data, the voice users can make calls.
The V5 interface must be configured. For details, see 2.3.1 Adding a V5 Interface. The 2M link of the V5 interface must be configured. For details, see 2.3.2 Adding a 2M Link on a V5 Interface. The communication channel must be configured. For details, see 2.3.3 Adding a CChannel.
Context
Figure 7-1 shows the flowchart for configuring the V5 PSTN service.
Issue 03 (2010-11-19)
7-1
Figure 7-1 Flowchart for configuring the V5 PSTN service
Start
Add a V5 interface
Add a 2M link
Configure a C-channel
Reset the V5 interface
Configure the PSTN user data
Save the Data
End
7.1 Introduction to the V5 PSTN Service The UA5000(PVM) supports the V5 interface, and is compatible with the optical line terminal (OLT) of the narrowband access network (AN). After connecting with the PSTN exchange through the V5 interface, the UA5000(PVM) provides the V5 PSTN service. 7.2 Configuring the V5 PSTN User Information This topic describes how to configure the protocol and physical port information about the V5 PSTN port to meet the requirements for the V5 PSTN service.
7-2
Issue 03 (2010-11-19)
7.1 Introduction to the V5 PSTN Service

The UA5000(PVM) supports the V5 interface, and is compatible with the optical line terminal (OLT) of the narrowband access network (AN). After connecting with the PSTN exchange through the V5 interface, the UA5000(PVM) provides the V5 PSTN service.
Context
The V5 interface is specially designed for the development of the AN. The interface is used between the local exchange (LE) and the AN to convert the analog connection between the LE and the AN device into the standard digital interface connection. The standard V5 interface is classified into V5.1 interface and V5.2 interface. The V5.1 interface manages only one 2048 kbit/s link, without the concentration capability. The V5.2 interface manages up to sixteen 2048 kbit/s links, with the concentration capability. l When the V5.1 protocol is used to configure narrowband service users, up to 30 users can be added in batches to the V5.1 interface. When the system allocates the V5.1 timeslots, timeslot 16 and the timeslot configured for the C-channel are skipped. When you add PSTN users in batches, the system searches PSTN ports automatically in the specified range, and adds the users one by one. The values of the L3 address and the telephone number are increased by one (default step). When the V5.2 protocol is used to configure the narrowband service users, the link timeslots are not used. The system allocates the V5.2 timeslots dynamically after the user hooks off.
The ringing mode of a PSTN user is controlled by the LE, but it is achieved by the AN device. In this case, the mapping between the LE and the AN device must be created. The mapping is distinguished based on the V5 interface. The mappings in the same interface are the same. By default, if the configuration table of the ringing modes is not configured, all ports adopt the common ringing mode. If the LE is the C&C08 of Huawei, you need not set the configuration table of the ringing modes. The reason is that the ringing type ID of the C&C08 is the same as the ringing type ID of the AN device. Currently, the system supports the following three types of the ringing ratio configurations: l l l a:b (a: ringing time; b: break time) a:b:c:d (a: ringing time; b: break time; c: ringing time; d: break time) a:b:c:d:e:f (a: ringing time; b: break time; c: ringing time; d: break time; e: ringing time; f: break time)
7.2 Configuring the V5 PSTN User Information

This topic describes how to configure the protocol and physical port information about the V5 PSTN port to meet the requirements for the V5 PSTN service.
Procedure
2 Choose ASL > POTS Port from the navigation tree. 3 Click the V5 PSTN Port tab, and set the filter criteria to display the required V5 PSTN ports. 4 Select one or multiple consecutive records from the V5 PSTN port list, right-click, and then choose Configure Attribute from the shortcut menu.
NOTE
When the Protocol Version parameter of the V5 interface is V5.1, you need to configure V5.1 TS. For details of the V5 interface, see 2.3.1 Adding a V5 Interface.
l When configuring one V5 PSTN port, set V5 Interface ID, L3 Addr., V5.1 TS, and Tel. NO..
l When configuring multiple consecutive V5 PSTN ports, set the values and step for V5 Interface ID, L3 Addr., V5.1 TS, and Tel. NO..
5 Click OK. ----End

8 Configuring the Transparent Transmission Service on the U Interface
Configuring the Transparent Transmission Service on the U Interface
About This Chapter

This topic describes how to configure the transparent transmission service provided by the UA5000(PVM) on the U interface. 8.1 Introduction to the Transparent Transmission Service on the U Interface The transparent transmission service on the U interface is to implement the transparent transmission service of the ISDN BRA (U interface) over the SPC between the DSL cards. With the transparent transmission service on the U interface, the transmission distance of the U interface on the node device can be extended, which resolves the problem about the U interface coverage. 8.2 Adding an SPC This topic describes how to add an SPC between two DSL cards to implement the transparent transmission on the U interface.
Issue 03 (2010-11-19)
8-1
8.1 Introduction to the Transparent Transmission Service on the U Interface

The transparent transmission service on the U interface is to implement the transparent transmission service of the ISDN BRA (U interface) over the SPC between the DSL cards. With the transparent transmission service on the U interface, the transmission distance of the U interface on the node device can be extended, which resolves the problem about the U interface coverage.
Context
When the PVM card is used as the narrowband control card of the UA5000(PVM), the ports on DSL cards of two ends need to work in the MNT and MLT modes respectively for configuring the transparent transmission service on the U interface. Generally, the ports on the DSL card that are used to connect the network-side devices work in the MNT mode, and the ports on the DSL card that are used to connect the user-side devices work in the MLT mode.
8.2 Adding an SPC

This topic describes how to add an SPC between two DSL cards to implement the transparent transmission on the U interface.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Connection > SPC from the navigation tree. 3 On the SPC tab page, set the filter criteria to display the required SPCs. 4 In the information list, right-click and choose Add from the shortcut menu. 5 In the dialog box that is displayed, select the Transparent Transmission check box, and set the parameters as follows: l Total Channel: 2 l MNT subtype Source Port Subtype: MNT subtype l Destination Port Subtype: MLT subtype l Start Channel: 0
8-2
Issue 03 (2010-11-19)
6 Click OK. ----End
Issue 03 (2010-11-19)
8-3
9 Configuring the ATI Service
9
About This Chapter
Configuring the ATI Service
This topic describes how the UA5000(PVM) provides the ATI service by using the ATI card. In addition, this topic describes how to configure and manage the ATI port. 9.1 Introduction to the ATI Service The UA5000(PVM) provides the E&M signaling and 2/4-wire voice frequency (VF) transparent transmission service by using the ATI card. 9.2 Configuring 2/4-Wire VF Service and the E&M Trunk Service This topic describes how to configure the 2/4-wire VF service and the E&M trunk service. 9.3 Configuring the Hotline Service of the E&M Trunk Interface This topic describes how to configure the hotline service of the E&M trunk interface.
Issue 03 (2010-11-19)
9-1
9.1 Introduction to the ATI Service

The UA5000(PVM) provides the E&M signaling and 2/4-wire voice frequency (VF) transparent transmission service by using the ATI card.
Context
l The slots of the ATI card and the service card are compatible. The ATI card can provide six 2/4-wire E&M trunk interfaces. Each port of an ATI card provides a 2/4-wire VF line and a 1E1M signaling line. When the E&M signaling line is not in use, the 2/4-wire VF line can be used separately to transmit VF signals. The signaling channel and voice channel of the E&M trunk interface are separate. Hence, when the E&M trunk interface is supported, a port includes the signaling line (E line and M line) and the VF line. Where, The signaling line can be configured to support the Bell IV or V interfaces through the DIP switch settings. The VF line can be configured to support the 2/4-wire VF interfaces through the DIP switch settings.
9.2 Configuring 2/4-Wire VF Service and the E&M Trunk Service

This topic describes how to configure the 2/4-wire VF service and the E&M trunk service.
Prerequisite
l l Network devices and lines must be in the normal state. The ATI card must be added and must work in the normal state.
Context
l l Currently, the ATI port supports only the 1E1M working mode. After modifying the EM mode and the subscriber line mode, adjust the DIP switch settings on the card.
9.2.1 Configuring the ATI Port Attributes After you configure the attributes of an ATI port, the ATI port can provide the required services. 9.2.2 Adding an SPC This topic describes how to set up a semipermanent connection (SPC) between ports.
9.2.1 Configuring the ATI Port Attributes

After you configure the attributes of an ATI port, the ATI port can provide the required services.
9-2
Issue 03 (2010-11-19)
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose ASL > ATI Port from the navigation tree. 3 Click the ATI Configuration tab. 4 In the ATI port list, right-click a record and choose Modify from the shortcut menu. 5 In the dialog box that is displayed, configure the subscriber line mode, receive gain, and transmit gain of the ATI port.
6 Click OK. ----End
9.2.2 Adding an SPC

This topic describes how to set up a semipermanent connection (SPC) between ports.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Connection > SPC from the navigation tree. 3 Click the SPC tab. 4 Right-click the list, and then choose Add. 5 In the dialog box that is displayed, set the configured service type to common and the connection type to internal SPC.
6 Click OK. ----End
9-4
Issue 03 (2010-11-19)
9.3 Configuring the Hotline Service of the E&M Trunk Interface

This topic describes how to configure the hotline service of the E&M trunk interface.
Prerequisite
l l Network devices and lines must be in the normal state. The ATI card must be added and must work in the normal state.
Context
NOTE
The physical line disconnection of the E&M trunk interface cannot be detected. Only the fault of the leased line that implements services inside the UA5000(PVM) can be detected.
9.3.1 Configuring the ATI Port Attributes After you configure the attributes of an ATI port, the ATI port can provide the required services. 9.3.2 Adding an SPC To implement the hotline service, you can set up a semipermanent connection (SPC) for the hotline service on the E&M trunk interface.
9.3.1 Configuring the ATI Port Attributes

After you configure the attributes of an ATI port, the ATI port can provide the required services.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose ASL > ATI Port from the navigation tree. 3 Click the ATI Configuration tab. 4 In the ATI port list, right-click a record and choose Modify from the shortcut menu. 5 In the dialog box that is displayed, configure the subscriber line mode, receive gain, and transmit gain of the ATI port.
Issue 03 (2010-11-19)
9-5
6 Click OK. ----End
9.3.2 Adding an SPC

To implement the hotline service, you can set up a semipermanent connection (SPC) for the hotline service on the E&M trunk interface.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Connection > SPC from the navigation tree. 3 Click the SPC tab and enter the filter criteria to display the required SPCs. 4 Right-click in the device list and choose Add from the shortcut menu. 5 In the dialog box that is displayed, set the parameters of the SPC.
6 Click OK. ----End
Issue 03 (2010-11-19)
9-7
10 Configuring the VFB Service
10
About This Chapter
Configuring the VFB Service
This topic describes how the UA5000(PVM) transmits the voice or data service through the VF channels on the dedicated network. 10.1 Introduction to the VFB Service The UA5000(PVM) provides the point-to-point (P2P) VF channels. You can connect VF telephones or modems at the two ends of VF channels to implement the dedicated interconnections of the voice or data service. 10.2 Configuring the VFB Port Attributes After you configure the attributes of a VFB port, the VFB port can provide the required services. 10.3 Adding an SPC This topic describes how to set up a semipermanent connection (SPC) between ports.
Issue 03 (2010-11-19)
10-1
10.1 Introduction to the VFB Service

The UA5000(PVM) provides the point-to-point (P2P) VF channels. You can connect VF telephones or modems at the two ends of VF channels to implement the dedicated interconnections of the voice or data service.
Context
l The UA5000(PVM) provides the VF dedicated service through the VFB card (2/4-wire VF dedicated interface card). If the terminal that you use is not fixed, that is, feedback is required sometimes and is not required sometimes, take priority to use the ASL card to implement dedicated interconnections. You can use the VFB card to implement the VF dedicated service only when the terminal in use does not require feedback and the interface impedance is 600 ohms. The VFB card has the following features: Provides the function of adjusting the 2/4-wire port through software. The VFB card provides sixteen 2-wire interfaces and eight 4-wire interfaces. You can configure only two adjacent ports as a 4-wire port. The two adjacent ports must meet the following requirements: 1. 2. The number of the first port must be even, and the number of the second port must be odd. The port with an even number must be always a transmitter, and the port with an odd number must be always a receiver.
The impedance of the 2/4-wire port must be always 600 ohms. Supports the encoding and decoding functions to perform the digital-to-analog conversion and the analog-to-digital conversion. Provides the overvoltage and overcurrent protection.
10.2 Configuring the VFB Port Attributes

After you configure the attributes of a VFB port, the VFB port can provide the required services.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose ASL > VFB Port from the navigation tree. 3 In the port list, right-click a record and choose Modify from the shortcut menu. 4 In the dialog box that is displayed, configure the working mode, receive gain, and transmit gain of the VFB port.
10-2
Issue 03 (2010-11-19)
5 Click OK. ----End
10.3 Adding an SPC

Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Connection > SPC from the navigation tree. 3 Right-click the device list, and then choose Add. 4 In the dialog box that is displayed, set the configured service type to common and the connection type to internal SPC.
5 Click OK. ----End
10-4
Issue 03 (2010-11-19)
11 Configuring the MTA Service
11
About This Chapter
Configuring the MTA Service
This topic describes the MTA service provided by the UA5000(PVM). In addition, this topic describes how to manage and operate the MTA port. 11.1 Introduction to the MTA Service The UA5000(PVM) provides the following external ports by using the multifunctional terminal adapter (MTA): 64/128 kbit/s synchronous port and 2.4/4.8/9.6/19.2 kbit/s subrate synchronous or asynchronous port. In addition, the UA5000(PVM) provides physical channels for the data terminal to communicate with the digital data network (DDN) or other data terminal users. 11.2 Configuring the Attributes of an MTA Port After you configure the attributes of an MTA port, the MTA port can provide the required services. 11.3 Adding an SPC This topic describes how to set up a semipermanent connection (SPC) between ports.
Issue 03 (2010-11-19)
11-1
11.1 Introduction to the MTA Service

The UA5000(PVM) provides the following external ports by using the multifunctional terminal adapter (MTA): 64/128 kbit/s synchronous port and 2.4/4.8/9.6/19.2 kbit/s subrate synchronous or asynchronous port. In addition, the UA5000(PVM) provides physical channels for the data terminal to communicate with the digital data network (DDN) or other data terminal users.
Context
l The MTA is connected to the DSL card through the 2B1Q interface on the device side. On the user side, the MTA provides one V.35/V.24 compatible port and two V.24 ports. The three ports can work only in the DCE mode. V.35/V.24 compatible port (port 0): It is a DB25 socket. The port provides the external V.24 port directly (you can also use the DCE-DTE direct connection cable). In addition, the port supports the 64 kbit/s synchronization and the 19.2 kbit/s, 9.6 kbit/s, 4.8 kbit/ s, and 2.4 kbit/s synchronization or asynchronization. You can use the V.35 transfer cable to provide the V.35 port that supports the rate of 128 or 64 kbit/s. V.24 port (ports 1 and 2): It is an 8-pin RJ45 connector. You can use the RJ45-DB25 transfer cable to provide the V.24 port that supports the 64 kbit/s synchronization and the 19.2 kbit/s, 9.6 kbit/s, 4.8 kbit/s, and 2.4 kbit/s synchronization or asynchronization. It is recommended that you do not use the 19.2 kbit/s synchronization or asynchronization on port 2. l The data devices that are connected to the MTA directly must provide the standard V.24/ RS-232 serial port or the V.35 serial port. The devices include the following: Router Computer Front end processor (FEP) for communication Other data terminal equipment (DTE)
11.2 Configuring the Attributes of an MTA Port

After you configure the attributes of an MTA port, the MTA port can provide the required services.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose DSL > MTA from the navigation tree. 3 In the MTA port list, right-click a record and choose Modify from the shortcut menu. 4 In the dialog box that is displayed, set the working mode, receive gain, and transmit gain of the MTA port.
11-2
Issue 03 (2010-11-19)
5 Click OK. ----End
11.3 Adding an SPC

Procedure
5 Click OK. ----End
11-4
Issue 03 (2010-11-19)
12 Configuring the HSL Service
12
About This Chapter
Configuring the HSL Service
This topic describes the HSL service provided by the UA5000(PVM). In addition, this topic describes how to manage and operate the ports of the HSL card. 12.1 Introduction to the HSL Service The UA5000(PVM) provides two V.35 ports and two FE1 ports by using the HSL card to access the N x 64K (N ranges from 1 to 31) data service. 12.2 Configuring the V.35 Port Attributes of the HSL Card After you configure the attributes of the V.35 port of the HSL card, the V.35 port can provide the required services. 12.3 Adding an SPC This topic describes how to set up a semipermanent connection (SPC) between ports.
Issue 03 (2010-11-19)
12-1
12.1 Introduction to the HSL Service

The UA5000(PVM) provides two V.35 ports and two FE1 ports by using the HSL card to access the N x 64K (N ranges from 1 to 31) data service.
Context
l You need to set up SPCs between the FE1, V.35, or SHDSL port of the HSL card and other service ports to transmit the subscriber service data. The services of the HSL card can be implemented in two modes: intra-card SPC and inter-card SPC. If an SPC is set up between the V.35 or SHDSL port and the FE1 port of the same HSL card, the SPC is called an intra-SPC. In this case, the FE1 port provides an upstream interface for services. That is, the service streams do not occupy the HW resources of the backplane. If an SPC is set up between the ports of one HSL card and the FE1, V.35, or SHDSL port of another HSL card or the E1 port of the PVM card, the SPC is called an inter-card SPC. In this case, the service streams occupy the HW resources of the backplane.
12.2 Configuring the V.35 Port Attributes of the HSL Card

After you configure the attributes of the V.35 port of the HSL card, the V.35 port can provide the required services.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose V.35 > HSL V.35 Port from the navigation tree. 3 Click HSL V35 and enter the filter criteria to display the required HSL V.35 ports. 4 On the HSL V35 tab page, set the filter criteria to display the required HSL V35 ports. 5 In the port list, right-click a record and choose Configure Port from the shortcut menu. 6 In the dialog box that is displayed, set Run Mode to DCE and Clock Mode to Internal.
12-2
Issue 03 (2010-11-19)
7 Click OK. ----End
12.3 Adding an SPC

Procedure
Issue 03 (2010-11-19)
12-3
5 Click OK. ----End
12-4
Issue 03 (2010-11-19)
13 Configuring the SDL Service
13
About This Chapter
Configuring the SDL Service
This topic describes the SDL service provided by the UA5000(PVM). In addition, this topic describes how to manage and operate the ports of the SDL card. 13.1 Introduction to the SDL Service On the UA5000(PVM), the G.SHDSL service is carried on the SDL card. The SDL card accesses the G.SHDSL service of the data dedicated line users in the TDM mode. 13.2 Configuring the TDM G.SHDSL Service This topic describes how to access and configure the TDM G.SHDSL service. 13.3 Configuring the Subtend Service of the TDM G.SHDSL This topic describes how to access and configure the subtend service of the TDM G.SHDSL port.
Issue 03 (2010-11-19)
13-1
13.1 Introduction to the SDL Service

On the UA5000(PVM), the G.SHDSL service is carried on the SDL card. The SDL card accesses the G.SHDSL service of the data dedicated line users in the TDM mode.
Context
l You need to set up SPCs between the FE1 or V.35 port of the SDL card and other service ports to transmit the subscriber service data. The services of the SDL card can be implemented in two modes: intra-card SPC and inter-card SPC. If an SPC is set up between the SHDSL port and the E1 port of the same SDL card, the SPC is called an intra-card SPC. Ensure that the SDL card works in the normal mode. In this case, the E1 port provides an upstream interface for services. That is, the service streams do not occupy the HW resources of the backplane. If an SPC is set up between the ports of one SDL card and the FE1, V.35, or SHDSL port of another SDL card or between two E1 ports of the same SDL card, the SPC is called an inter-card SPC. In this case, the service streams occupy the HW resources of the backplane. According to service modes, setting up SPCs on the SDL card must meet the following requirements: The intra-card SPC of the SDL card supports up to 32 timeslots. The start and end timeslots of an SPC start from the smallest idle timeslot. The inter-card SPC from one SDL card to another SDL card supports up to 28 timeslots. The start and end timeslots of an SPC start from the smallest idle timeslot.
13.2 Configuring the TDM G.SHDSL Service

This topic describes how to access and configure the TDM G.SHDSL service.
Prerequisite
You must set the DIP switches of the card before the service configuration.
Context
G.SHDSL is a member of the xDSL technologies covering the HDSL, ADSL, and VDSL. The G.SHDSL technology uses the 36B+w7D frames and it can bear the TDM, ATM, IP, or combined transmission. The G.SHDSL technology uses the trellis coded pulse amplitude modulation (TC-PAM). Hence, it provides symmetric upstream and downstream rates that reach 2.3 Mbit/s over common twisted pairs. The transmission distance reaches 3 km or more when the symmetric upstream and downstream rates are 2.3 Mbit/s. In addition, the lines have the stronger capability against interference and the lower transmit power. The G.SHDSL is widely used in various applications such as the E1 replacement, access of data services symmetrically at high speed, video conference, remote medical treatment, and VoDSL. The G.SHDSL is based on the TDM or ATM mode. 13.2.1 Configuring the Working Mode of the SDL Card After you set the working mode and clock source of the SDL card, the card can provide the required services.
13.2.2 Configuring the Attributes of a TDM G.SHDSL Port After you configure the attributes of the TDM G.SHDSL port on the SDL card, the port can provide the required services. When you configure the port attributes, ensure that the working mode of the TDM G.SHDSL port maps the router that is connected to the TDM G.SHDSL port. The working modes of the TDM G.SHDSL port and the router are E1 mode. 13.2.3 Adding an SPC This topic describes how to set up a semipermanent connection (SPC) between ports.
13.2.1 Configuring the Working Mode of the SDL Card

After you set the working mode and clock source of the SDL card, the card can provide the required services.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 On the tab page that is displayed, choose NE Panel from the navigation tree. Double-click the shelf in the right pane to display the shelf view. 3 Right-click the required SDL card and choose Configure Board Param from the shortcut menu. 4 In the dialog box that is displayed, set Work Mode to Normal and Clock Source to System Clock.
5 Click OK. ----End
13.2.2 Configuring the Attributes of a TDM G.SHDSL Port

After you configure the attributes of the TDM G.SHDSL port on the SDL card, the port can provide the required services. When you configure the port attributes, ensure that the working mode of the TDM G.SHDSL port maps the router that is connected to the TDM G.SHDSL port. The working modes of the TDM G.SHDSL port and the router are E1 mode.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose DSL > TDM G.SHDSL Port from the navigation tree. 3 On the TDM G.SHDSL Port tab page, set the filter criteria to display the required TDM G.SHDSL ports. 4 In the TDM G.SHDSL port list, right-click a record and choose Configure Port from the shortcut menu. 5 In the dialog box that is displayed, set the parameters as follows: l Run Mode: E1 l Port Rate: 32 l Frame Mode/Synchronization Mode: PCM31
6 Click OK. ----End
13.2.3 Adding an SPC

Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Connection > SPC from the navigation tree.
3 Right-click the device list, and then choose Add. 4 In the dialog box that is displayed, set the configured service type to common and the connection type to internal SPC.
5 Click OK. ----End
13.3 Configuring the Subtend Service of the TDM G.SHDSL

This topic describes how to access and configure the subtend service of the TDM G.SHDSL port.
Prerequisite
l A proper MGC profile must be configured. For details, see 2.5 Configuring an MGC Profile.
Issue 03 (2010-11-19)
l l
The MG interface must be configured. For details, see 2.1.2 Adding an MG (H.248/ MGCP). The UA5000(PVM) must be able to communicate with the MGC.
Context
The applications of the TDM G.SHDSL port are classified into two types: l l Extension of the circuit emulation interfaces such as the CES E1 interface and the CES V. 35 interface Extension of the frame relay interfaces such as the E1 interface and the V.35 interface
The subtend service of the TDM G.SHDSL port is applicable to the actual broadband service expansion where the user is far away from the ATM access device and no fibers are available. Even if fibers are available, the cost is high if you access individual users by using fibers. In this case, you can use the TDM-based G.SHDSL technology to make full use of twisted pairs that are of large quantity, thus accessing users flexibly and easily at low cost. The devices such as the PBX, DDN, router, conference TV, and narrowband optical network unit (ONU) can be accessed. The UA5000(PVM) connects the ONU through the SDL card. Subtending remote ONUs increases the capacity of the UA5000(PVM) to access users. 13.3.1 Configuring the Working Mode of the SDL Card After you set the working mode and the clock source of the SDL card, the card can provide the required services. 13.3.2 Configuring the Running Mode of the TDM G.SHDSL Port After you configure the attributes of the TDM G.SHDSL port of the SDL card, the port can provide the required services. 13.3.3 Adding a Remote Subscriber Shelf This topic describes how to add the remote subscriber shelf RSUG_ONU60A (HUBO). 13.3.4 Adding an Inter-Shelf Link This topic describes how to add an inter-shelf link. 13.3.5 Configuring Subscriber Data This topic describes how to configure the service attributes and physical attributes of a PSTN port to provide the required services. 13.3.6 Enabling a Service Port After you configure the attributes of the VoIP PSTN port, you need to enable the port to start services.
13.3.1 Configuring the Working Mode of the SDL Card

After you set the working mode and the clock source of the SDL card, the card can provide the required services.
Procedure
2 On the tab page that is displayed, choose NE Panel from the navigation tree, double-click the shelf in the right pane to display the shelf view. 3 Right-click the required SDL card and choose Configure Board Param from the shortcut menu. 4 In the dialog box that is displayed, set Work Mode to Normal and Clock Source to System Clock.
5 Click OK. ----End
13.3.2 Configuring the Running Mode of the TDM G.SHDSL Port

After you configure the attributes of the TDM G.SHDSL port of the SDL card, the port can provide the required services.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose DSL > TDM G.SHDSL Port from the navigation tree. 3 On the TDM G.SHDSL Port tab page, set the filter criteria to display the required TDM G.SHDSL ports. 4 In the TDM G.SHDSL port list, right-click a record and choose Configure Port from the shortcut menu. 5 In the dialog box that is displayed, set Run Mode to V.35.
Issue 03 (2010-11-19)
13-7
6 Click OK. ----End
13.3.3 Adding a Remote Subscriber Shelf

This topic describes how to add the remote subscriber shelf RSUG_ONU60A (HUBO).
Procedure
1 In the Main Topology, choose the required UA5000(PVMV1) from the Physical Root navigation tree, right-click, and then choose Add Frame from the shortcut menu. 2 In the dialog box that is displayed, set the parameters such as Frame Name, Frame Alias, and Frame Type.
NOTE
Frame Type must be set to RSUG_ONU60A(HUBO).
3 Click OK.
4 Repeat Steps 4 and 5 to add another remote subscriber shelf. ----End
13.3.4 Adding an Inter-Shelf Link

This topic describes how to add an inter-shelf link.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 On the tab page that is displayed, choose Inter-frame Link Management from the navigation tree. 3 In the device list, right-click and choose Add from the shortcut menu. In the displayed dialog box, set the parameters of the new inter-shelf link in the Left Port and Right Port fields.
4 Click OK. 5 Repeat Steps 4 and 5 to add another inter-shelf link. ----End
13.3.5 Configuring Subscriber Data

This topic describes how to configure the service attributes and physical attributes of a PSTN port to provide the required services.
Procedure
2 Choose ASL > POTS Port from the navigation tree. 3 Click the VoIP PSTN Port tab, and set the filter criteria to display the required VoIP PSTN ports. 4 In the PSTN port list, right-click a record and choose Configure Attribute from the shortcut menu. 5 In the dialog box that is displayed, click the Service Details tab. Configure the attributes such as MG ID, Terminal ID, and Tel No. of the VoIP PSTN subscriber.
6 Click the Physical Details tab. Configure the physical attributes such as High Level Width, Low Level Width, Reversed Polarity, and Dial Mode of the VoIP PSTN port.
7 Click OK. ----End

13.3.6 Enabling a Service Port

After you configure the attributes of the VoIP PSTN port, you need to enable the port to start services.
Context
NOTE
You can start services only on the PSTN port whose User Port Configuration is VoIP Configured and Authorized.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose ASL > POTS Port from the navigation tree. 3 Click the VoIP PSTN Port tab, and set the filter criteria to display the required VoIP PSTN ports. 4 In the PSTN port list, right-click a record and choose Enable Service from the shortcut menu. 5 Click OK. ----End
Issue 03 (2010-11-19)
13-11
14 Configuring the CDI Service
14
About This Chapter
Configuring the CDI Service
This topic describes how to configure the CDI service of the direct-dialing-in subscriber interface card (CDI) on the UA5000(PVM). The CDI card connects the subscriber ports of the local exchange in the actual network through the external analog interface, thus implementing the transparent transmission and direct dialing service of the analog service port. 14.1 Introduction to the CDI Service The UA5000(PVM) subsystem implements the transparent transmission of analog service ports by using the CDI card. The CDI card provides the following services: the Z-interface extension, private branch exchange (PBX) bidirectional connection, and E1-direct dialing in (DDI). 14.2 Configuring the Z-Interface Extension Service The digital-to-analog conversion, transparent transmission, and signaling processing of the host between the CDI and ASL ports implement the transparent extension of the analog service ports (Z-interface) of other external exchanges inside the access network. 14.3 Configuring the PBX Bidirectional Connection To enable the users connected to two PBXs in the access network to communicate with each other, you need to configure the SPC leased line service in the access network. 14.4 Configuring the DDI Service The UA5000(PVM) supports the CDI card to provide the analog trunk interface that is connected to the PBX to implement the DDI function. With the DDI function, the calls from the outside can be established by dialing the access code (PBX pilot number) and the number of the PBX extension number without the second dialing or the help from operators.
Issue 03 (2010-11-19)
14-1
14.1 Introduction to the CDI Service

The UA5000(PVM) subsystem implements the transparent transmission of analog service ports by using the CDI card. The CDI card provides the following services: the Z-interface extension, private branch exchange (PBX) bidirectional connection, and E1-direct dialing in (DDI).
Context
The concepts related to the CDI card are as follows: l The slots of the CDI card and other service cards such as the ASL card and the DSL card are compatible. The CDI card assigns timeslot resources in dynamic mode and detects and reports the electrical features such as the ring current, busy tone, and feed of external lines. The CDI card connects analog lines and the CDI port can be regarded as the analog telephone. The receive gain of the CDI card ranges from -22.5 dB to -3 dB; the transmit gain of the CDI card ranges from -8.5 dB to 0.5 dB; the step for adjusting is 0.5 dB. Z-interface extension service: The digital-to-analog conversion, transparent transmission, and signaling processing of the host between the CDI and ASL ports implement the transparent extension of the analog service ports of other external exchanges inside the access network. The Zinterface refers to the analog telephone interface. In the networking where only a few analog telephones exist, the Z-interface increases the service capacity by using transparent transmission if the V5 interfaces of the exchange are unavailable. Connect the analog telephone of a local exchange to another local exchange through the Z interface extension. In this case, you can reduce the toll charge without changing the charging mode. l PBX bidirectional connection: Configure the SPC leased line service in the access network. In this case, the users connected to two PBXs in the access network can communicate with each other. DDI service: Through an analog trunk interface between the inter-office exchange and the CPE, the user can dial directly to connect to the CPE device through the DDI interface and place a call to the users connected to the CPE device. The UA5000(PVM) supports the CDI card to provide the analog trunk interface that is connected to the PBX to implement the DDI function. With the DDI function, the calls from the outside can be established by dialing the access code (PBX pilot number) and the number of the PBX extension number without the second dialing or the help from operators. The UA5000(PVM) can provide the DDI channel and the emergency channel to the PBX by using the same CDI card. The same port, however, cannot provide the DDI channel and the emergency channel at the same time.
l l
The CDI services are as follows: l
14-2
Issue 03 (2010-11-19)
14.2 Configuring the Z-Interface Extension Service

The digital-to-analog conversion, transparent transmission, and signaling processing of the host between the CDI and ASL ports implement the transparent extension of the analog service ports (Z-interface) of other external exchanges inside the access network.
Prerequisite
The CDI card must be added and work in the normal state.
Context
l The Z-interface extension refers to the extension of the POTS user signals. The Z-interface extension converts analog POTS user signals into digital POTS user signals and transmits the digital signals to the receive end. At the receive end, the digital signals are converted into analog signals. The Z-interface extension service increases the access distance of twisted pairs. The typical Z-interface extension requires a Z-interface, the digital transmission system, and a POTS port. The Z-interface extension service provides the following functions: Connects the users of the dedicated network to the local exchange. In this dedicated network, only a few analog telephone users exist. Extends the analog telephone service of a local exchange to another local exchange with reducing the toll fee and without changing the charging mode. Connects long-distance users. Improves the utility of lines by using dynamic convergence. Figure 14-1 shows an example network of the Z-interface extension service. Figure 14-1 Example network of the Z-interface extension service
l l l
Issue 03 (2010-11-19)
14-3
Figure 14-2 shows the flowchart for configuring the Z-interface extension service Figure 14-2 Flowchart for configuring the Z-interface extension service
Start
Configure the attributes of the CDI port
Configure the SPC
Does the service quality meet the requirements?
No
Modify the attributes of the CDI port
Save the data
End
1.
14.2.1 Configuring the Attributes of a CDI Port To implement the transparent transmission of an analog user port on the CDI card, you need to configure the attributes of the CDI port, including the transmit gain, receive gain, dialing mode, working mode, and Z-interface ringing mode. After the attributes of a CDI port are configured, you can use the SPC configured on the CDI port. 14.2.2 Setting Up an SPC An SPC can connect, release, check, and protect one or more 64K channels between the CDI card and the ASL card. After an SPC is set up successfully, the connection channel is created automatically.
2.
14.2.1 Configuring the Attributes of a CDI Port

To implement the transparent transmission of an analog user port on the CDI card, you need to configure the attributes of the CDI port, including the transmit gain, receive gain, dialing mode, working mode, and Z-interface ringing mode. After the attributes of a CDI port are configured, you can use the SPC configured on the CDI port.
14-4
Issue 03 (2010-11-19)
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose ASL > CDI Port from the navigation tree. 3 Click the CDI tab. 4 Right-click a record in the CDI port list and choose Modify from the shortcut menu. 5 In the dialog box that is displayed, set the parameters such as Rx Plus, Tx Plus, Line Attribute, and Z Interface Ring Mode.
6 Click OK. ----End
14.2.2 Setting Up an SPC

An SPC can connect, release, check, and protect one or more 64K channels between the CDI card and the ASL card. After an SPC is set up successfully, the connection channel is created automatically.
Procedure
2 Choose Connection > SPC from the navigation tree. 3 Click the SPC tab and enter the filter criteria to display the required SPCs. 4 Right-click in the device list and choose Add from the shortcut menu. 5 In the dialog box that is displayed, set Service Type to Z-interface extension, and set Connection Type to Leased Line.
NOTE
The Z-interface extension service supports only the SPC whose Connection Type is Leased Line.
6 Click OK. ----End

14.3 Configuring the PBX Bidirectional Connection

To enable the users connected to two PBXs in the access network to communicate with each other, you need to configure the SPC leased line service in the access network.
Prerequisite
The CDI card must be added and work in the normal state.
Context
Figure 14-3 shows an example network of the PBX bidirectional connection. Figure 14-3 Example network of the PBX bidirectional connection
Figure 14-4 shows the flowchart for configuring the PBX bidirectional connection.
Issue 03 (2010-11-19)
14-7
Figure 14-4 Flowchart for configuring the PBX bidirectional connection
Start
Configure the SPC
Does the service quality meet the requirements?
No
Modify the attributes of the CDI port
Save the data
End
1.
14.3.1 Configuring the Attributes of a CDI Port To configure the port attributes in the PBX bidirectional connection service, you need to configure the port attributes of two CDI cards separately, including the transmit gain, receive gain, dialing mode, working mode, and Z-interface ringing mode. After the attributes of a CDI port are configured, you can use the SPC configured on the CDI port. 14.3.2 Setting Up an SPC An SPC can connect, release, check, and protect one or more 64K channels between the CDI cards. After an SPC is set up successfully, the connection channel is created automatically.
2.

To configure the port attributes in the PBX bidirectional connection service, you need to configure the port attributes of two CDI cards separately, including the transmit gain, receive gain, dialing mode, working mode, and Z-interface ringing mode. After the attributes of a CDI port are configured, you can use the SPC configured on the CDI port.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose ASL > CDI Port from the navigation tree.
3 Click the CDI tab. 4 Select one or more records of the same CID card from the CDI port list, right-click, and then choose Modify from the shortcut menu. 5 In the dialog box that is displayed, set the parameters such as Rx Plus, Tx Plus, Line Attribute, and Z Interface Ring mode.
6 Click OK. 7 Repeat Steps 3-5 to configure the port attributes of the other CDI card. ----End
14.3.2 Setting Up an SPC

An SPC can connect, release, check, and protect one or more 64K channels between the CDI cards. After an SPC is set up successfully, the connection channel is created automatically.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose Connection > SPC from the navigation tree. 3 Click the SPC tab and enter the filter criteria to display the required SPCs. 4 Right-click in the device list and choose Add from the shortcut menu. 5 In the dialog box that is displayed, set Service Type to PBX bidirectional connection and Connection Type to Leased Line.
NOTE
The PBX bidirectional connection supports only the SPC whose Connection Type is Leased Line.
6 Click OK. ----End
14.4 Configuring the DDI Service

The UA5000(PVM) supports the CDI card to provide the analog trunk interface that is connected to the PBX to implement the DDI function. With the DDI function, the calls from the outside can be established by dialing the access code (PBX pilot number) and the number of the PBX extension number without the second dialing or the help from operators.
Prerequisite
l l l l l The MG interface must be added. To add an MG interface, see 2.1.2 Adding an MG (H. 248/MGCP). The required parameters of the MGC must be set. To set the required parameters of the MGC, see 2.1.4 Configuring an MGC. The MG interface must be enabled and work in the normal state. To enable an MG interface, see 2.1.6 Starting Up an MG Interface. The CDI card must be added and work in the normal state. The signaling IP address and the media IP address must be configured successfully.
Context
l l The terminal ID must be the same as the terminal ID preset on the MGC. If the TID profile that is bound to the user in an MG interface does not support layered terminals, the terminal IDs of DDI users must be specified in a unified manner on the MG interface. If the TID profile that is bound to the user in an MG interface is configured to support layered terminals, you need not specify the terminal ID when configuring a DDI user. In this case, the system generates a protocol address automatically.
Figure 14-5 shows an example network of the DDI service. Figure 14-5 Example network of the DDI service
Issue 03 (2010-11-19)
14-11
Figure 14-6 shows the flowchart for configuring the DDI service. Figure 14-6 Flowchart for configuring the DDI service
Start
Configure the IP address
Add an MG interface
Configure the data of the MGC interface
Start the MG interface
Add a CDI board
Add the DDI user data
Start the DDI service
Save the data
End
14-12
Issue 03 (2010-11-19)
1.
14.4.1 Configuring the Attributes of a CDI Port You can configure the DDI channel or emergency channel service on the CDI port. In the case of the CDI card, you can configure certain CDI ports as DDI channels and configure the rest CDI ports as emergency channels. You can configure a CDI port as either a DDI channel or an emergency channel. 14.4.2 Adding the DDI User Data To add a DDI user and configure the user data on the specified CDI port or configure an emergency channel for the DDI user, you need to perform the operation. 14.4.3 Starting the DDI Service To make the DDI service available, you need to start the service of the required DDI or emergency channel.
2.
3.

You can configure the DDI channel or emergency channel service on the CDI port. In the case of the CDI card, you can configure certain CDI ports as DDI channels and configure the rest CDI ports as emergency channels. You can configure a CDI port as either a DDI channel or an emergency channel.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose ASL > CDI Port from the navigation tree. 3 Click the CDI tab. 4 Right-click a record in the CDI port list and choose Modify from the shortcut menu. 5 In the dialog box that is displayed, set the parameters such as MG ID and Terminal ID.
Issue 03 (2010-11-19)
14-13
6 Click OK. ----End
14.4.2 Adding the DDI User Data

To add a DDI user and configure the user data on the specified CDI port or configure an emergency channel for the DDI user, you need to perform the operation.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose ASL > CDI Port from the navigation tree. 3 Click the DDI tab. 4 Right-click in the list and choose Add from the shortcut menu. 5 In the dialog box that is displayed, set parameters such as Emergency Flag, Terminal MG ID, Terminal ID, and Frame/Slot/Port.
14-14
Issue 03 (2010-11-19)
6 Click OK. ----End
14.4.3 Starting the DDI Service

To make the DDI service available, you need to start the service of the required DDI or emergency channel.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose ASL > CDI Port from the navigation tree. 3 Click the DDI tab. 4 Right-click a record in the DDI list and choose Terminal Operation > Start from the shortcut menu. ----End
Issue 03 (2010-11-19)
14-15
15 Maintaining the TDM G.SHDSL Terminal
15
Maintaining the TDM G.SHDSL Terminal
About This Chapter

This topic describes how to query the information about a TDM G.SHDSL terminal and configure a loopback for a TDM G.SHDSL terminal. 15.1 Querying the Information About a TDM G.SHDSL Terminal This topic describes how to query the information about a TDM G.SHDSL terminal on the U2000, such as the basic information, alarm information and LAN port information. 15.2 Configuring a Remote Loopback for a TDM G.SHDSL Terminal This topic describes how to configure a remote loopback for a TDM G.SHDSL terminal. After successful configuration, you can check whether the line is in the normal state by comparing the transmitted and received Ethernet frames.
Issue 03 (2010-11-19)
15-1
15.1 Querying the Information About a TDM G.SHDSL Terminal

This topic describes how to query the information about a TDM G.SHDSL terminal on the U2000, such as the basic information, alarm information and LAN port information.
Prerequisite
l l The TDM G.SHDSL terminal must be managed remotely by the U2000. The TDM G.SHDSL terminal must be activated.
Procedure
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) and choose NE Explorer from the shortcut menu. 2 Choose DSL > TDM G.SHDSL Port from the navigation tree. 3 On the TDM G.SHDSL Port tab page, set the filter criteria to display the required TDM G.SHDSL ports. 4 In the TDM G.SHDSL terminal list, right-click a record and choose Terminal Manage from the shortcut menu. 5 In the dialog box that is displayed, click the Terminal Panel tab. Click the Basic Info tab in the lower pane to view the details of the TDM G.SHDSL terminal. 6 On the Terminal Panel tab page, click the LAN port and the SHDSL port to view the details. ----End
15.2 Configuring a Remote Loopback for a TDM G.SHDSL Terminal

This topic describes how to configure a remote loopback for a TDM G.SHDSL terminal. After successful configuration, you can check whether the line is in the normal state by comparing the transmitted and received Ethernet frames.
Prerequisite
l l The TDM G.SHDSL terminal must support the remote management by the U2000. The TDM G.SHDSL terminal must be activated.
Procedure
2 Choose DSL > TDM G.SHDSL Port from the navigation tree. 3 On the TDM G.SHDSL Port tab page, set the filter criteria to display the required TDM G.SHDSL ports. 4 In the TDM G.SHDSL terminal list, right-click a record and choose Terminal Manage from the shortcut menu. 5 In the Terminal Manage window, right-click the SHDSL port and choose Remote Loopback from the shortcut menu. 6 After the loopback is completed, right-click the SHDSL port in the Terminal Manage window and choose Cancel Loopback from the shortcut menu. ----End
Issue 03 (2010-11-19)
15-3
16 Detecting the Network
16
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. 16.1 Telnet This topic describes how to log in to a device through the network remotely to configure and maintain the device. 16.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. 16.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. 16.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)
16-1
16.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
16.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
16.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
16.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)
16-3
17 Saving the Data
17
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. 17.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. 17.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)
17-1
17 Saving the Data
17.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(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) 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
17.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.
17-2
Issue 03 (2010-11-19)
17 Saving the Data
Procedure
1 In the Main Topology, choose the required UA5000(PVMV1) 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)
17-3
18 Synchronization
18
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 18.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. 18.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. 18.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. 18.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)
18-1
18 Synchronization
18.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(PVMV1) from the Physical Root navigation tree, right-click, and then choose Synchronize NE Data from the shortcut menu.
----End
18.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(PVMV1) from the Physical Root navigation tree, right-click, and then choose Set NE Time from the shortcut menu.
----End
18.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.
18 Synchronization
Procedure
l In the Main Topology, choose the required UA5000(PVMV1) 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
18.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(PVMV1), right-click, and then choose Synchronize System Parameter Profile.
----End
Issue 03 (2010-11-19)
18-3
19 File Operations
19
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. 19.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. 19.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. 19.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)
19-1
19 File Operations
19.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
1 In the Main Topology, double-click the required UA5000(PVMV1) in the Physical Root navigation tree; or right-click the required UA5000(PVMV1) 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 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
19.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.
19 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
19.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)
19-3
20 Remote Maintenance Guide
20
About This Chapter
Remote Maintenance Guide
This topic describes the tasks of maintaining the UA5000(PVM) software through the U2000, and the reference standard, operation guide, exception handling, and command reference of the tasks. 20.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. 20.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. 20.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. 20.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. 20.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. 20.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. 20.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.
20-2
Issue 03 (2010-11-19)
20.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)
20-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.
20-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
20.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.
20-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)
20-7
Related Commands
To... Query the CPU usage of a board Run the Command... display cpu In... Privilege mode
20.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.
20-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 and GPON mode
20.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. 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
3.
4.
20-10
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. 5. Click OK. to
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 click next to File Name. In the dialog box that is displayed, set File Name, File 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
20.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 l l l A common user can perform basic system operations and simple query operations. 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
20.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
20.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. 20.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. 20.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. 20.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.
20.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.
20.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.
20-14
Issue 03 (2010-11-19)
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)
20-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
20-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)
20-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.
20-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
20-19
To... Configure the periodical backup function of the automatic backup
Run the Command... auto-backup period
In... Global config mode
20.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(PVM) 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(PVM) 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
20-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
20.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(PVM) 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(PVM) in the FTP/TFTP/SFTP mode. To back up the data, you can upload the file saved on the UA5000(PVM) to a specified file server. To restore the data, you can download the file saved on the specified file server to the UA5000(PVM).
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(PVM) 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
20-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
20.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(PVM) 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
20-26
Run the Command... load configuration
In... Privilege mode
load data
Privilege mode
Issue 03 (2010-11-19)
Issue 03 (2010-11-19)
20-27
A Acronyms and Abbreviations
A
A ADSL B BRA
Acronyms and Abbreviations
This section describes the acronyms and abbreviations used in the UA5000(PVM) Configuration Guide
Asymmetric Digital Subscriber Line
Basic Rate Access
C CES Circuit Emulation Service
D DCE DDN DMM DSLAM DTE Data Communications Equipment Digital Data Network Distributed Message Manager Digital Subscriber Line Access Multiplexer Digital Terminal Equipment
F FE FoIP FR FSK Far End Fax over IP Frame Relay Frequency Shift Keying
Issue 03 (2010-11-19)
A-1
I IP ISDN Internet Protocol Integrated Service Digital Network
L LAN Local Area Network
M MAC MoIP MG MGC MGCP Media Access Control Media over IP Media Gateway Media Gateway Controller Media Gateway Control Protocol
N NE NMS O OLT ONU Optical Line Terminal Optical Network Unit Network Element Network Management Station
P PBX PCM POTS PRA PRI PSK PSTN Private Branch Exchange Pulse Code Modulation Plain Old Telephone Service Primary Rate Access Primary Rate Interface Phase Shift Keying Public Switched Telephone Network
A-2
Issue 03 (2010-11-19)
QoS
Quality of Service
S SPC SNMP Semi-permanent connection Simple Network Management Protocol
T TDM Time Division Multiplex
U UDP UNI User Datagram Protocol User Network Interface
V VLAN VOD Virtual Local Area Network Video on Demand
Issue 03 (2010-11-19)
A-3

Og For Ua5000-Pvm Ne Management - (v100r002c01 - 03)

Uploaded by

Copyright:

Available Formats

Og For Ua5000-Pvm Ne Management - (v100r002c01 - 03)

Uploaded by

Document Information

Original Description:

Original Title

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

Og For Ua5000-Pvm Ne Management - (v100r002c01 - 03)

Uploaded by

Copyright:

Available Formats

iManager U2000 Unified Network Management System V100R002C01

Operation Guide for UA5000-PVM 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 VoIP PSTN Service......................................................................................4-1

5 Configuring the VoIP ISDN Service......................................................................................5-1

6 Configuring the V5 ISDN Service..........................................................................................6-1

7 Configuring the V5 PSTN Service..........................................................................................7-1

8 Configuring the Transparent Transmission Service on the U Interface.........................8-1

9 Configuring the ATI Service....................................................................................................9-1

10 Configuring the VFB Service...............................................................................................10-1

11 Configuring the MTA Service.............................................................................................11-1

12 Configuring the HSL Service...............................................................................................12-1

13 Configuring the SDL Service...............................................................................................13-1

14 Configuring the CDI Service...............................................................................................14-1

15 Maintaining the TDM G.SHDSL Terminal......................................................................15-1

16 Detecting the Network..........................................................................................................16-1

17 Saving the Data.......................................................................................................................17-1

20 Remote Maintenance Guide................................................................................................20-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.

1.2.2 Setting the NE Handshake Parameters

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

1.3 Adding an OLT to the U2000

Add an OLT to the U2000.