1. ONW310600 IManager M2000 V200R013 Topology Management ISS

M2000 V200R013 Topology Management

Confidential Information of Huawei. No Spreading Without Permission


Topology management is a way to present the topology relationships between NEs, subnets,

and links on a network by graphics. The main functions are as follows: importing data from or

exporting data into a file, setting the background, as well as NE layout and monitored NEs.

Topology management provides the following functions:

Displays NEs and links by subnets. Each subnet can be displayed in a different topology

view.

Customizes topology view, displaying or hiding types of NEs and links.

Queries the information about NEs and links between NEs.

Creates, modifies, and deletes subnets, NEs, links.

Zooms out, zooms in, locks, and unlocks a view.

Sets the background (including an empty background) for a view.

Arranges the objects in the current subnet in good order.

Moves, cuts, and pastes the objects in a subnet.

Filters topology objects by object types.

Supports discovering SNMP NEs instantly or as scheduled.

Monitors the statuses of all devices on the main topology view in a centralized manner.

The main topology view displays the device alarms of all severities and devices statuses

with multiple types of icons, and provides alarm information in tips. The user can

customize the display effect of alarms as required.



(1)Topology navigation tree: Displays the hierarchy of the objects on the topology view.

You can precisely locate the objects on the topology view through the topology navigation

tree.

(2)Current view type: You can select views through the list box beside Current View,

including Physical Root, Electronic View, BSC Pool View, RNC Pool View, RNC in Pool View,

Core Network Pool, Core Network MME Pool, Multimode Base Station View, NetEco View,

GBTS Group View, and Signaling Network View.

(3)Topology tool bar: The shortcut icon on the topology tool bar can be used to perform

operations easily and quickly on the physical topology.

(4)Physical topology view: Displays all the networks managed by M2000 in a map.

(5)Extend Apply: You can click on the toolbar to select lists to be displayed, including

Browse Current Alarm, Cell List and Monitor RNC in Pool.


Subnet

On M2000, a large network can be divided into several smaller networks based on a specific rule

(for example, by region), for the convenience of network management. On M2000, these smaller

networks are called subnets. Subnets are located in the physical view and electronic map.

NE

NEs are used to identify concrete entity devices, such as switches and routers. NEs can be grouped

into physical NEs and virtual NEs.

Physical NEs are the Huawei Technologies Co., Ltd. communication devices that exist in the network.

The physical NEs can be managed by M2000.

Virtual NEs are the communication devices that do not truly exist or devices that do not belong to

Huawei Technologies Co., Ltd.. You cannot manage the virtual NEs by M2000, but you can add the

existing virtual NEs to the physical view, and know the entire communication network.

Link

A link is used to identify the physical or logical connection between two topological nodes in the

topology view. It is the general name of connections in the topology view and includes physical links,

optical fibers, and service paths or virtual connections between two nodes. Including physical links

and virtual links.

A physical link indicates that there actually exits physical connection between physical NEs, subnets,

and a physical NE and a subnet. A virtual link refers to the logic link between NEs (including physical

NEs and virtual NEs), subnets, and an NE and a subnet.





Physical subnets reflect the network hierarchy in the topology view. Setting up physical

subnets properly can improve the visibility of the communication network and operability

of M2000. Setting up a physical subnet involves the operations such as designing a

physical view and creating subnets, NEs, and links.


Before deploying NEs in a physical topology view, you need to design the view. The

physical topology view should clearly reflect the actual communication network structure

to facilitate routine maintenance and operations.

The topology management window consists of a navigation tree on the left and a

topology view on the right. The navigation tree displays all the topology objects and their

hierarchical relations in a tree, and the topology view displays all the topology objects and

their positions on the physical topology view.


By setting the background for the specified subnet or container NE, you can view the

positions of the topology objects under the subnet or container NE in a distinguished

manner.

On M2000, only the image files in the formats of .gif or .jpg can be imported, and the file

size cannot exceed 1 MB.

Container NEs refer to multi-subrack devices on a network. NEs in a container NE refer to

boards in subracks of a multi-subrack device. If a subrack of a multi-subrack device has

multiple boards, the subrack is also a container NE. In other words, container NEs can

contain container NEs. Container NEs provide the same functions as subnets and common

NEs do except that: Container NEs do not allows NEs to be moved in or out, but subnets

allow.

Container NEs provide some functions of subnets, but common NEs do not.



You can create a subnet in the physical view or on the electronic map and add NEs to the

subnet to facilitate management.



The recommended number of objects (including NEs and subnets) deployed in the same

subnet is not more than 500; otherwise, the performance may be reduced, especially in

low bandwidth of the network.




M2000 categorizes network devices according to their home networks.

Bearer network

Router series include: AR46, Eudemon1000, Eudemon200, Eudemon500, NE08E,

NE16E, NE40E, NE80E, NE5000E, CX600 and ATN

Switch series include: S2000, S2000B, S3000, S3328, S3500, S5328, S5500,

S8500, and S9300

Security NE series include: Eudemon, SIG, and SVN

Optical network transmission devices. The series include: RTN310, RTN380,

RTN605, RTN610, RTN620, RTN905, RTN910, RTN950, RTN950A, RTN980,

RTN910(NA) and RTN950(NA)

Domain name server DNS

Access network

GSM & UMTS: BSC, PCU, RNC, NodeB, BSC6900 GSM, BSC6900(GSM-R), BSC6900

UMTS, BSC6910 GSM, BSC6910 UMTS, BSC6000(GSM-R), and GSM-R BTS, and

GBTS

CDMA: CBSC and CBTS (3606 and 3612)

RASYS: RAC and RAU

WiMAX: WiMAX BTS (including BTS3701B, BTS3702C, BTS3702E, and DBS3900

WiMAX)




NE Creating

NEs One by

One

Creating NEs in

Batches

(Automatic

Search Mode)

Creating NEs

in Batches

(Template

Mode)

Creation Mode

NodeB, BTS3900 √ √ √ •Creating NEs in batches (automatic

search mode): M2000 creates

NodeBs/BTS3900s managed by the

base station controller by using

automatic detection. After being

created, the NodeBs/BTS3900s can be

operated and maintained on M2000.

GBTS -

√ - No manual intervention is required for

creating physical GBTSs. M2000

automatically searches for them. If

GBTSs exist under a base station

controller, M2000 automatically

creates these GBTSs when it

synchronizes the controller

information.

SNMP device √ √ √ •Creating NEs in batches (automatic

search mode): M2000 can create

SNMP devices in batches by searching

for SNMP devices based on the IP

addresses of the SNMP devices or the

IP network segment that the SNMP

devices are located.


eGBTS must be created under their controller NEs, such as BSC6900 GSM, BSC6900 GU,

BSC6910 GSM and BSC6910 GU, to which eGBTS belongs.

NodeBs must be created under their controller NEs, such as RNC, BSC6900 UMTS, and

BSC6900 GU, to which NodeBs belongs.

After an NE is created, it is displayed in the topology navigation tree and topology view. At

the same time, M2000 automatically synchronizes NE configuration data. If the NE is in an

abnormal status, M2000 displays an NE status icon to the upper-left of the NE icon.

Typical NE status is as follows: :

indicates the NE and M2000 server are disconnected. In this case, you need to

check whether the connection between the NE and M2000 is normal or whether

the IP address of the NE is correctly set.

indicates the NE has not been configured or the NE version does not match the

mediation version installed on M2000 server. In this case, you need to check

whether the NE is correctly configured or whether the matching mediation version

is installed.



M2000 does not support the batch creation of virtual NEs.

If the type of the new NE is NodeB, a virtual or physical RNC must be selected as the

subnet where the new NE is located.



Procedure

Open the Batch Create Topo Objects dialog box.

Choose Topology > Main Topology. The Main Topology window is displayed.

In the topology navigation tree or physical topology view, right-click the subnet of the NE

to be created, and then choose Batch Create Topo Objects from the shortcut menu.

Export the script file template for creating NEs in batches.

Select the NE node under the Batch Create node from the navigation tree of the Batch

Create Topo Objects dialog box.

In the right Export Template pane, select INI File or CSV File, and then click Export.

If INI File is selected, the information about multiple NE types can be exported to a

file all at a time.

If CSV File is selected, the information about an NE type can be exported to a file

all at a time.

Enter the information about NEs to be created in the exported script file template.

Create physical NEs in batches.

In the right pane of the Batch Create Topo Objects dialog box, select a script file.

Click Verify to check the configuration of the script file. If any error occurs on the

configuration, correct the error by referring to Template Verify Information.

You can select Stop Creating in Case of Errors according to the actual requirement.

Click OK to start creating NEs. The Create NE Progress dialog box is displayed, showing

the progress of NE creation and results.

Click Close to close the Create NE Progress dialog box.


This section describes how to enable M2000 to automatically detect and create

NodeBs/BTS3900s. After a specified controller for NodeBs/BTS3900s, such as the RNC,

BSC6900 UMTS, BSC6900 GU, and BSC6900 GSM, has been created in the topology view,

M2000 synchronizes the information about the NodeBs/BTS3900s managed by the

controller by using the automatic detection function, and automatically creates the

NodeBs/BTS3900s. Then, you can perform operation and maintenance on the

NodeBs/BTS3900s on M2000 client.

Prerequisites

The controller managing NodeBs/BTS3900s has been created and communicates

with the M2000 server properly.

The NodeB/BTS3900 mediation software has been installed.

Check whether the relay server of the controller managing NodeBs/BTS3900s has

been configured prope. See Configuration Management course for details.




You need to manually create the MTP3Link, MTP3BLink, DataLink, FiberLink, and

MicroWaveLink, which cannot be automatically created by the system.

Procedure

Choose Topology > Main Topology. The Main Topology window is displayed.

Use either of the following methods to create a physical link in a topology navigation tree

or physical view:

Create a physical link.

Right-click the subnet node in the topology navigation tree or on the

topology view, and then choose New > Link.

Under in the navigation tree, select a specific link type.

Configure link information.

Create physical links in Batches.

Right-click the subnet node in the topology navigation tree or the topology

view, and select Batch Create Topo Objects.

Choose Batch Create > Link in the navigation tree in the left pane.

Click Add in the right pane.



The NE reconnection states are described as follows:

Enable connection: When an NE is disconnected from M2000 server, M2000

attempts to reconnect to the NE. By default, new NEs are set to enable connection.

Disable connection: When an NE is disconnected from M2000 server, M2000 does

not attempt to reconnect to the NE.



NodeBs may be in the disconnected state because they are deleted or reparented.

Therefore, you need to determine the reason why the NodeBs are disconnected before

performing the related operation such as deleting, reconnecting, and waiting for the

NodeBs to be reparented.


You can monitor the status of cells in the topology view only for GSM, UMTS, and LTE

network elements (NEs). The cell display entry is unavailable for NEs of other radio access

technologies (RATs).

Currently, this function applies to GBTSs, MBTSs, NodeBs, and eNodeBs in compatible with

GBSS13.0, WRAN13.0, eRAN2.1, and later versions.



You can select the style for displaying the client: Application style which is new style and

displaying all the applications on the client or Traditional style which is the old one that

you used to see and use in the previous M2000 versions.



You can customize some settings on topology such as the background color, Node icon,

Node Label and etc. here.



1. ONW310600 IManager M2000 V200R013 Topology Management ISS

Documents

Transcript of 1. ONW310600 IManager M2000 V200R013 Topology Management ISS