1. Network management system description
OMC network management is remote centralized management software. Through this software, it can realize centralized remote management of IMS access equipment, real-time monitoring of equipment operation status, and accurate control of network status. The system provides functional modules such as alarm management, user management, device management, performance management, and log management.
The network management system has the following features:
- Centralized and unified management
Management OMC network management realizes the centralized and unified management of the IMS access equipment, and can easily monitor, operate, configure and maintain the entire network.
- Strong management ability
The software provided by the OMC network management controls the number of NEs managed by the license, but the capability of the management system is mainly determined by the processing capability of the hardware. Different management systems can be configured for different network scales, or a divided management method can be used to configure multiple sets of management systems.
- Great flexibility
A distributed management system can be used to flexibly manage remote devices. The server and Database can be installed on the same server or on different servers. Multiple management terminal PCs can be connected, and management members can be set according to the management scale and authority.
- Safe and reliable
The OMC network management system adopts a safe management mechanism, operates the management system through the client, sends operation instructions to network elements remotely, and sets different user operation rights and network elements that the user can manage on the client according to the situation.
When designing and managing the OMC network management, the security requirements of the management system are fully considered. Based on the enterprise-level database platform design, it has high security in terms of network architecture, user rights management, data backup, and security interfaces.
- Convenient upgrade plan
The OMC network management system software can be changed through patch upgrade and uninstallation, which provides convenience for system maintenance and upgrade, does not affect normal services and ensures system reliability.
- Componentized architecture
Management OMC network management is based on the unified management software platform of Beijing company and adopts multi-process, modular, and object-oriented componentized architecture design. The coupling of each network element management component is small, and it supports different application processes to integrate into the system through registration files, which is a flexible expansion capability. Management OMC network management supports the distribution and hierarchy of database systems, business processing systems, and front-end application systems that support multi-client operations and can adapt to the management needs of complex and large-scale networks.
- Various fault location methods
Management OMC network management supports real-time monitoring of abnormal operating conditions in the network, management OMC network management supports functions such as alarm topology location, alarm remote notification, alarm filtering and statistics, alarm redefinition and alarm maintenance experience database, etc., and provides a complete fault location method.
- Graphical interface
Management OMC network management adopts B/S structure. The management terminal only needs to use the IE browser that comes with Windows to manage the OMC network management without installing other software, which is convenient, concise, and quick to deploy. Fully considering the user’s operating habits, the management OMC network management provides a graphical user interface that is easier for operators to understand and use, and provides templated and batch operation methods to simplify users’ daily operations.
1.2 Network Management System structure
1.2.1 System composition
Management OMC network management adopts B/S working mode, the software is server software, the client only needs to use the IE browser that comes with the client PC, and can configure multiple clients.
Management OMC network management can be used as an equipment monitoring center and data management center. In order to reduce the complexity of the operation, the OMC network management system can adopt a B/S structure, use the client to log in, centrally manage network elements, and can perform remote operation and upgrade. One OMC network management client has multiple network elements, which is convenient for administrators to manage and maintain the equipment.
The OMC network management system includes the user interface, Server, Database, and network elements. The relationship between each part is as follows:
- User interface
The user interface can be called a client, and basically does not maintain dynamic management data. These data are extracted from the database through the Server from time to time when the user uses the network element software. User Interface Log in using the WEB interface.
- Server
The OMC network management server can be called a server manager. The server sends instructions to the corresponding network elements, accepts various notifications from the network elements, and saves all network management data in the database, such as system management, alarm management and other basic data.
- Database
The database mainly completes the information query of the interface and management function modules and stores and processes the information. Such as alarm log, system configuration, etc.
- Network element
The network element is the management target, that is, the IMS access device manages the converged communication product, the corresponding server sends the command, and sends the notification reflecting the daily target behavior to the corresponding server.
1.2.2 Software structure of the network management
The structure of the management OMC network management software is shown in the following figure:
Management OMC network management adopts a mature and widely used B/S structure, adopts multi-process, modularized architecture and object-oriented design, and supports distributed system management. Management OMC network management adopts centralized message forwarding technology and supports information exchange of various business function systems through a unified information management center. Management OMC network management provides component management programs for each device and each function, and you can select corresponding components according to different needs. Management OMC network management has good scalability. Through the component management of equipment, it is convenient to support new types of equipment and new functions.
1.2.3 Hardware requirement for network management
The appearance of the rack server is shown in the following figure:
| Items | OTOMC network management hardware requirements |
| Processor | 2x Intel(R) Quad-Core E Xeon(R) CPU, 2.13GHz, 4M Cache, QPI up to 4.86 GT/s |
| Memory | 4 GB (2×2 GB) 1333 MHz single-rank RDIMM memory |
| Network card | Integrated two POE-enabled Broadcom 5709C dual-port Gigabit Ethernet |
| Storage | 300GB*2 RAID1 10K RPM 6Gbps SAS 2.5-inch hot-swappable hard drive |
| Dimension（W×D×H） | 42.6mm*482.4 mm*772mm |
| AC Input | 220V AC（200V-240V） |
| Power | Hot-swap 717W PSU (high output) |
| Reliability | Hot-plug hard drives, RAID1, hot-plug redundant power supplies, redundant cooling, ECC memory, Single Device Data Correction (SDDC), support for memory requirements, Patrol, and High Availability Failover Clustering |
Chapter 2 System description
2.1 Function lists
| Items | Description |
| Topology management | Provides topology management functions, including topology object management, NE status and main information display, NE management links, topology view management, etc. |
| Alarm management | Provides functions related to alarm management, including alarm query, event management, alarm statistics, alarm analysis, alarm suppression, alarm severity, alarm name, alarm definition, alarm summary, alarm notification, etc. |
| Performance management | Provides performance management functions, including device performance task detection, performance parameter management, performance detection results, performance threshold management, performance statistics, etc. |
| User management | Provide system user management functions, including user management, role management, user group management, etc. |
| Device management | Provides management functions for IMS access devices, including device management, device group management, device type management, and customer management |
| Log management | Provides system log management functions, including operation logs, NE logs, log settings, log cleaning, log backup, etc. |
| Task management | Provide task management, which can operate and manage batch tasks on the managed NEs. |
| Remote operation | Through the remote operation of the management system, it is possible to manage multiple devices to perform a remote reboot of the device, restore the factory settings of the device, restore the preset settings of the device, the number of device parameters, remote tunnel, Ping test, remote version upgrade, etc. |
| Equipment information monitoring | Provides the information status acquisition function of the device, including device online status, device wan information, device CPU memory usage, license number, device version information, signaling tracking, etc. |
| Northbound interface | Provide interface functions such as alarm, performance, business, resource, and test, and support various forms of interface protocols. |
| System configuration | Provide system configuration management, including network configuration, FTP configuration, ACS configuration, TUNNEL configuration, SMTP configuration, login authentication configuration, task timeout configuration, NTP configuration. |
| Database management | Provides database process view, database space alarm, database space alarm definition data backup file list, data backup parameter setting, and database status management for the management database |
| System maintenance | Provide system version information, license management, system upgrade management, system task configuration, and system data recovery. |
2.2 Network Management System protocol
- Southbound interface: manage network elements through SNMP protocol and TR069 protocol
| Interface type | Interface description |
| SNMP southbound interface | Manages the alarm southbound interface between the OMC and NEs. The device reports real-time fault alarms to the OMC. |
| TR069 southbound interface | Manage the service southbound interface between the OMC network management and network element devices, and support service provisioning, service maintenance, resource query, resource provisioning, and resource change notification. |
Northbound interface: the CORBA standard protocol connected to the upper management platform
| Interface type | Description |
| CORBA Northbound interface | Manage the alarms and resource northbound interfaces provided by the OMC network management to the OSS, support alarm query filtering, inventory resource query, and inventory resource change notification. |
| SOAP North interface | Manage the service northbound interface between OMC network management and OSS, and support service provisioning, service maintenance, resource query, resource provisioning, and resource change notification. |
- Other protocols：SMTP，NTP，FTP etc protoc
Chapter 3 network management system Deployment plan
3.1 Hardware configuration
Management OMC network management system consists of a management server, database system, and OMC network management client.
Management server, database server (can use the same one), using Dell R610 rack-mounted server
- The lowest configuration：
Process： Intel x86Xeon quad-core CPU 2.5 or higher
Memory：4G or above
Hard disk space: 320G or more (RAID double hard disk)
Network card：1000M ethernet network card
Optical Drive: Optical drive
Customer side PC
Management News, IMS access device including IPPBX,4G device, etc.
3.2 Software configuration
- Operation system： Linux operation system， Debian Linux 5.0 64bit Or above version.
- Database： MYSQ database，5.0.22 or above version.
- Management OMC network management centralized management system software 1 set
3.3 IP address planning
- OMC network management server: Use 1 intranet IP address and 1 external network address
- IMS access equipment network element: when management and services are not separated, each network element uses one IP address
The IP address is uniformly allocated by the mobile network data center, and the mobile intranet address can be used. It is necessary to ensure network communication between the OMC network management server and the network element. For convenience of use, the OMC network management server address can use the public network IP address, which is convenient for remote WEB login and remote maintenance and upgrade.
3.4 Port Communication Matrix
| （Source device） Source IP | （Destination device) Destination IP: Port number | Type | Application | Module | |
| Network element | OMC network management server | 5078 | TCP | Receive network element reporting signaling | SignalServer |
| 8008 | TCP | Receive JBOSS requests | SNMP server | ||
| 9999 | TCP | NE request monitoring | Tunnel | ||
| 8000 | UDP | Heartbeat monitoring | Acsworker | ||
| 162 | UDP | Receive the alarm reported on the NE | |||
| 8000 | TCP | Access acsserver | |||
| OMC network management server | Network element | 25100 | TCP | Access tr069 client side | Cwmpd |
| 161 | UDP | Performance detect | |||
| OMC network management client-side | OMC network management server | 8000 | TCP | NMSWeb port | |
| 443 | TCP | HTTPS-based web access for NMS | Jboss | ||
| 8100 | TCP | web browser request signaling | SignalServer | ||
| 9998 | TCP | NMS requests to monitor port | Tunnel | ||
| 10000~10100 | TCP | Tunnel reverse connection | Tunnel | ||
| 21 | TCP | FTP server | FTP |
3.5 Network structure
Management OMC network management server can manage a variety of management converged communication products, and can use multiple WEB clients. The management OMC network management is located in the business management layer.
The IPPBX equipment is connected to the mobile metropolitan area network through GPON, realizes the intercommunication with the SBC, and completes the registration to the CM-IMS core network. The management channel of the OMC network management system relies on the network environment of the IMS access device and is mainly carried on the CM-NET metropolitan area network.
The network diagram of the OMC network management using IP management is shown in the following figure:
Since the management protocol is transmitted between the management system and the network element by means of TCP/IP, the only criterion for judging whether the management channel is valid is whether a TCP/IP link can be established between the OMC network management server and the network element, and the PING tool can be used to carry out testing.
The logical networking diagram of the OMC network management is as follows:
The server implements management and interaction functions in the following ways:
- Manage network elements through SNMP and TR069
- WEB client management through HTTP/HTTPS protocol
- Provide alarm function to upper management through NBI northbound interface
The OMC network management network topology using TDM is as follows:
The TDM PBX needs to carry the management data flow through the E1 time slot, as shown in the following figure:
A configuration：
1. In the channel mapping table of Voice Configuration>Basic Settings>PCM settings, change the time slot that needs to be used as the data channel to D.
2. Select the routing mode in Network Configuration>Basic Settings>E1/T1 Settings.
3. Add 1 E1 channel, bind one or more time slots, and the IP address is 10.0.0.2.
B Configuration
1 . In the channel mapping table of Voice Configuration>Basic Settings>PCM settings, change the time slot that needs to be used as the data channel to D.
2.Select bridge mode in network configuration > basic settings > E1/T1 settings, and the IP address is 10.0.0.1.
3. Add 2 E1 channels, each bound with one or more time slots. The number of bound time slots must be the same as A and B. For example, if A is bound to 1 time slot, then the corresponding time slot of THC3800 is also 1.
4. Set the LAN port IP at 192.168.0.1.
5. Add a static route from the E1 bridge interface to 192.168.0.1 in Network Settings > Routing Settings > Static Routes
3.6 Management login
Start the browser on the client PC, and in the address bar of the browser “http://server ip address:port number/otOMC network management/”, (the IP address and port number should be consistent with the actual installation environment, the default port number is 8000 ) and press the Enter key to enter the login interface, as shown in the figure below.
When you log in for the first time, enter the user name “admin”, the default password “admin”, enter the correct verification code, click the <Login> button to enter the system, click the system management to display the version information, and the Web setting page pops up as shown in the following figure:
