Professional Documents
Culture Documents
Issue
Release Date
Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved.
Non-by this company written permission, no unit or individual may discretionally extract, copy some or all
content in this document and must not be transmitted in any form.
And other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd..
This document All other trademarks or registered trademarks mentioned, all of their respective holders.
Note
The purchased products, services, or features shall be restricted by Huawei commercial contract and the
clauses in the constraints described in this document all or partial products, services and features may not
be within the purchase scope or the usage scope. Unless otherwise specified in the contract, Huawei made
to the contents in this document do not guarantees or representations of any kind, either express or implied.
Due to product upgrades or other reasons. This document will be aperiodically updated. Unless otherwise
stated, this document serves only as a guide on how to use this document, all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Preface
Overview
This document describes HUAWEI GENEX Discovery PS configuration method of the
collector.
This document provides guidance for frontline engineers through HUAWEI GENEX
Discovery PS configuration of the collector.
Intended Audience
This document (guide) is intended for the following engineers:
Technical support engineers
Maintenance engineers
Symbol conventions
In this article may be the following flag, they represent are described as follows.
Symbol Description
Modification Records
Modify the cumulative description of each document update. The latest document issue
contains the content of the update of all earlier document versions.
Directory
Directory
Preface ............................................................................................................................................... ii
1 Adding a collector ......................................................................................................................... 5
1.1 Collector Configuration.................................................................................................................................... 5
1.2 The file to be uploaded ..................................................................................................................................... 7
1.3 Configure synchronization ............................................................................................................................... 7
1.4 Check the configuration. .................................................................................................................................. 8
1 Adding a collector
a) USN CHR documents For the OMU board, SPU board of the UGW CHR documents. The UFDR
xDRs of the SPU board, STE board of the UFDR, and xDR documents. According to 1.4 check. If the
corresponding mode exists, set the to is not connected to the data of this type. Otherwise, according to
the specific circumstances set need to be connected to the data of this type.
b) For EVU boards USN CHR, if there are new NE access needs to be parsed, the set to need to be
connected to the data of this type, and set the NE service IP; If no new NE needs to be parsed, the set not
to access data of that type.
c) For CSGN, if there are new NEs or connected to the peer IP needs to be parsed, the needs to be
configured for access data of this type, and set the corresponding NE service IP; If no new NE needs to
be parsed, the set not to access data of that type.
The server name to the server where the DPU module is located. If you want to select all server where the
DPU module is located.
If the check result is Inconsistent, the synchronize configuration data. Otherwise, the does not synchronize
the configuration.
2. Settings-> Configuration Management-> Routine Maintenance-> configuration data synchronization. If
conditions do not change.
TCP 189.104.30.13:10500 (LISTEN): 1.1 EVU boards in the section corresponding to USN
CHR,TCP protocol 10500 port.
TCP 189.104.30.13:10900 (LISTEN): 1.1 section in CSGN,TCP protocol, 10900 port.
1.1 section corresponding to the UDP 189.104.30.13:mcreport: USN CHR bills of the OMU board,
SPU board of the UGW CHR documents,DTP protocol, 8003 port. If yes, it indicates that data of
this type can access the network.
UDP 189.104.30.13:10700: SPU board in the corresponding 1.1 in UFDR xDRs, STE board of the
UFDR, and xDR documents,UDP protocol, 10700 port. If yes, it indicates that data of this type can
access the network.
UDP 189.104.30.13:8004: 1.1 section corresponding to the SPU board of the UGW CHR
document,UDP protocol, 8004 port. If the table already exists. If yes, it indicates that data of this
type can access the network.