M2000 R012 Topology

3 infoX-MMSC M2000 V200R012C00 Topology Management

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.
:32-35pt : R153 G0 B0 : FrutigerNext LT Medium : Arial :30-32pt : R153 G0 B0 : :20-22pt (2-5) :18pt : : FrutigerNext LT Regular : Arial :18-20pt (2-5):18pt : :
13
.
Page*
Objectives
Upon completion of this course, you will be able to:
Construct and manage the topology structure of the entire network.
Learn and monitor the running status of the entire network by browsing the topology view.

13
.
Page*
Contents
13
.
Page*
x-*
Topology management is used to create and manage the topology structure of the entire network and reflect the networking and running status of devices. You can learn and monitor the running status of the entire network in real time by browsing the topology view.
Topology management provides the following functions:
Three types of topology types are provided: physical view, electronic map, and customized view. You can define and organize different topology views as required.
Different icons are used to identify different types of topology objects. A small icon is used to identify the status of a topology object, such as the disconnection state and the synchronization state.
Adding, deleting, modifying, and moving the NE, subnet, and link in the topology view are supported.
The status of each managed object can be displayed, such as whether the object is faulty and whether the object is connected to other NEs.
You can query and browse the alarm information of an NE by using the topology view.
You can customize the start view, filter topology objects by type, order topology objects by legend, and order topology objects by name or type.
Setting the background is supported on the topology view. You can learn the specific location of a device node by viewing the location of the icon in the background.
Topology view supports global zooming and partial zooming to help you view the network topology structure.
The function of finding the global topology objects is provided to help you locate the topology object. The auxiliary tools, such as the overview, print, and filter tools are provided to help you implement the management function.
13
.
Page*
Objects in Topology
Objects in topology indicate the objects in the network. Each element managed by the NMS is an object.
An object can be a subnet, an NE, a group NE, or a link between NEs.

x-*
Subnet: 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. In topology, these smaller networks are called subnets.
A subnet exists in the physical topology and logical topology.
NE: NEs are used to identify concrete entity devices, such as switches and routers. NEs can be grouped into physical NEs and virtual NEs.
Group NE: In a telecommunication network, some NEs are interdependent. A group NE is an NE that has the characteristics of both NE and subnet.
Link: Links refer to the links between NEs that are mapped in the topology, including physical links and virtual links.
Physical link indicates that there is physical connection between two physical NEs. Currently the M2000 supports six types of physical links: M3UA, H248, BICCSCTPLNK, DATALINK, MTP3, and MTP3B.
M3UA, H248 and BICCSCTPLNK links are created by the system automatically.
DATALINK, MTP3 and MTP3B links are created manually. You can delete only physical links that are manually created.
Virtual link refers to the logic link between two NEs (including physical NEs and virtual NEs), and you can set up a virtual link manually.
13
.
Page*
Contents
13
.
Page*
Designing a Physical View
Before deploying NEs in a physical view, you need to design a physical subnet. The physical topology must show the topology structure of the actual telecommunication network and facilitate the routine operation and maintenance of operators.
On the physical topology, topology objects and the hierarchical relationship among objects are shown in the navigation tree on the left; all topology objects on the existing subnet and the location relationship among the objects are shown in the topology view on the right.

x-*
The M2000 provides the following modes for dividing physical subnets to meet various management requirements:
By region: based on regions where NEs are located.
By NE type: based on types of NEs.
By IP Address: based on IP addresses of NEs.
By responsible person: based on responsible persons of NEs.
13
.
Page*
x-*
By properly setting a background and device position, you can know the locations of the devices directly.
Only the image files in the formats of .gif or .jpg can be imported, and the file size cannot exceed 1 MB.
If you need to cancel the background setting, select empty.gif in the Select a background dialog box and click Open.
13
.
Page*
13
.
Page*
Contents
13
.
Page*
Classification of Physical NEs
A physical NE is a communication device that is connected to the M2000 and can be managed by the M2000. The M2000 can manage a communication device only when the corresponding physical NE is created on the M2000.
The M2000 divides the managed mobile network devices into the devices of the GSM, WCDMA, CDMA, WiMAX, and LTE network based on the network that the NE belongs to. IP devices are independent of the preceding networks.

13
.
Page*

x-*
After you successfully create a physical NE in the topology view, the M2000 obtains the configuration data of the NE by synchronizing the NE.
13
.
Page*
Creating Physical Links
A physical link is a physical connection between two physical NEs. You can have a clear understanding of the telecommunication network between NEs and the communication status by setting up a physical link. The MTP3 MTP3B, and DATALINK links must be created manually.
Currently, the M2000 supports the following link types: M3UA, H248, BICCSCTPLNK, DATALINK, MTP3, and MTP3B.
M3UA, H248, and BICCSCTPLNK links are automatically created by the system. MTP3 MTP3B, and DATALINK links must be created manually.
You can delete only physical links that are manually created.

13
.
Page*
Creating Multiple Physical NEs
The M2000 supports the function of creating multiple physical NEs to reduce the maintenance workload. You can create multiple physical NEs at a time on the topology.
Before creating multiple physical NEs in batches, you must copy the information about the physical NEs to be created to an .ini or .csv file. The operation does not support the creation of virtual NEs.

x-*
The template used for creating NEs in batches is divided into the INI and CSV format. The script file in the CSV format does not support the creation of the RNC, RAC, BSC, GT800BSC, BSC6000, CBSC, and IMS group NEs (IMSOMU, CSCF, HSS, ATS, RM, CCF, DOPRA, SBC, MRF, MRFC, MRFP, CSE, OMS2600, MEDIAX, and IPCTRX).
13
.
Page*

13
.
Page*
13
.
Page*
Contents
13
.
Page*
Monitoring an NE
You can choose System > NE Monitor to view the NE status, including the NE name, NE type, alarm status, and connection status.
Common icons in the topology view:
NE disconnected:
13
.
Page*
Setting NE Reconnection Status
When an NE is disconnected from the M2000 server, you can specify whether the M2000 server attempts to reconnect the NE.
There are two reconnection states:
Enable Connection
When an NE is disconnected from the M2000 server, the M2000 server attempts to reconnect the NE. By default, the reconnection status of a newly added NE is Enable Connection.
Disable Connection
When an NE is disconnected from the M2000 server, the M2000 server does not attempt to reconnect the NE.

13
.
Page*
Manually Reconnecting an NE
You can manually reconnect an NE to the M2000 server when the NE is disconnected from the M2000 server.
In the physical topology view, right-click an NE with and choose Reconnect NE from the shortcut menu.
disappears after the reconnection is successful.

13
.
Monitoring Cell Status
You can browse the cell status of a GBTS, NodeB, eNodeB, or MBTS by selecting the GBTS, NodeB, eNodeB, or MBTS. In addition, you can block and unblock, activate and deactivate a cell, and switch to the performance monitoring window of the cell by using the shortcut menu.
Page*
13
.
Page*
Contents
13
.
Page*
Adjusting the Network Topology
After a subnet, NEs, and links are successfully created, you can adjust the network topology as required. The network topology adjustment involves operations such as modification and deletion of the subnet, NEs, and links. The shortcut menu supports the preceding operations.

13
.
Page*
Adjusting the Topology View
You can adjust the topology view as required. The topology view adjustment involves showing or hiding the topology navigation tree, switching the current subnet, displaying the topology view in full screen, zooming the topology view, and customizing the topology prompt information.
Create a link
Zoom
Refresh
13
.
Page*
Setting the Default Topology View
Set the currently selected subnet to the default subnet that is displayed when you enter the topology view.
The configured subnet is directly displayed when you enter the main topology window next time.

Date post:	30-Sep-2015
Category:	Documents
Upload:	manuel
View:	51 times
Download:	5 times

M2000 R012 Topology

Documents