WO2015196654A1 - 网管的分布式管理方法及装置 - Google Patents
网管的分布式管理方法及装置 Download PDFInfo
- Publication number
- WO2015196654A1 WO2015196654A1 PCT/CN2014/088975 CN2014088975W WO2015196654A1 WO 2015196654 A1 WO2015196654 A1 WO 2015196654A1 CN 2014088975 W CN2014088975 W CN 2014088975W WO 2015196654 A1 WO2015196654 A1 WO 2015196654A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- slave
- server
- network management
- management system
- file
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
Definitions
- the present invention relates to the field of network management technologies, and in particular, to a distributed management method and apparatus for network management.
- network management needs to manage large-scale and large-capacity networks, and the types of devices to be managed are also single responsibilities such as access network management, core network management, and bearer network management.
- the network management system is transformed into a unified and integrated network management system.
- the existing distributed network management system is mostly a hierarchical management system. Through the hierarchical configuration and management domain division of multiple network management stations, the management of large-capacity networks is realized.
- the system generally consists of two parts: the upper network management station and the lower network management station.
- the upper-layer network management station runs the corresponding equipment to complete the configuration and monitoring functions of the lower-level network management station.
- the lower-level network management station uses the Simple Network Management Protocol (SNMP) to collect, report, and monitor the network management data. If you want to expand the management capacity, you need to increase the deployment of the lower-level network management, which is time-consuming and labor-intensive.
- SNMP Simple Network Management Protocol
- Some distributed network management systems use functional distributed management to achieve horizontal expansion of network management functions through the master and slave server architectures.
- the main server controls the message distribution, process allocation, and external network management services of the entire network management system.
- the slave server configures and manages the NEs through SNMP, and can also provide northbound services (that is, services implemented on the northbound interface).
- the distributed management mode cannot meet the technical requirements of the network size expansion, and the embodiment of the present invention provides a distributed management method and device for the network management to solve at least the above technical problem.
- a distributed management method of a network management system including: the main control server starts an update to the local network management system; and the main control server generates a slave machine that updates the network management system of the slave server. Updating a file; the master server synchronizes the slave update file to the slave server.
- the slave update file includes at least one of the following: an upgrade file, a patch file.
- the method includes: the master control server starts installation of the local network management system; and the master control server generates a network management system for installing in the slave network server. a slave installation file of the system; the master server synchronizes the slave installation file to the slave server.
- the method further includes: when the network management system of the master server changes, receiving a synchronization request of the slave server; The master server synchronizes the update file reflecting the change of the network management system to the slave server.
- the synchronizing the slave update file to the slave server by the master server comprises: the master server synchronizing the slave update file to the slave server by using a file transfer protocol FTP.
- a distributed management method of a network management system includes: receiving, by a slave server, a slave update file from a master server; the slave server installing according to the slave update file The network management system of the slave server is updated.
- the slave server before receiving, by the slave server, the slave update file from the master server, the slave server receives a slave installation file from the master server, and the slave installation file is used in the slave A network management system is installed on the server; the slave server installs the network management system on the slave server according to the slave installation file.
- the method further includes: the slave server monitoring the network management system of the master server; When the network management system of the master server changes, the host server is requested to synchronize to update the update file of the network management system.
- a distributed management apparatus for a network management which is applied to a main control server, and includes: a startup module, configured to start an update to a local network management system; and a generation module configured to generate a slave machine
- the slave network management system of the server performs an updated slave update file; the synchronization module is configured to synchronize the slave update file to the slave server.
- the startup module is further configured to initiate installation of the local network management system;
- the generation module is further configured to generate a slave installation file for installing a network management system in the slave server;
- the synchronization module is further configured to synchronize the slave installation file to the slave server.
- a distributed management apparatus for a network management is provided, which is applied to a slave server, including: a receiving module, configured to receive a slave update file from the master server; and an update module, configured to The slave update file updates the network management system installed on the slave server.
- the receiving module is further configured to receive a slave installation file from the master server, where the slave installation file is used to install a network management system on the slave server; the update module is further configured to The network management system is installed on the slave server according to the slave installation file.
- the update file of the network management system of the slave server is generated, and the technical solution of the slave server is synchronized, and the related technology is solved.
- the distributed management mode can not meet the technical requirements of the expansion of the network scale, so that the management of the network management system on the master server can be planned to different machines, which provides strong support for the expansion of the network scale.
- FIG. 1 is a flowchart of a distributed management method of a network management device according to an embodiment of the present invention
- FIG. 2 is a structural block diagram of a distributed management apparatus of a network management device according to an embodiment of the present invention
- FIG. 3 is a flowchart of a distributed management method of another network management device according to an embodiment of the present invention.
- FIG. 4 is a structural block diagram of a distributed management apparatus of another network management device according to an embodiment of the present invention.
- FIG. 5 is a structural block diagram of a network management system according to an embodiment of the present invention.
- the network distributed management solution provided in the related art has technical problems such as the inability to adapt to the expansion of the network scale.
- the embodiment of the present invention is based on a master-slave server architecture, and multiple physical machines are used to form a unified network management system, and each process can be started according to the deployment plan.
- Different physical machines slave servers
- various physical machines services Servers can collaborate with each other and communicate with each other to form a complete network management system.
- the "distributed" in the embodiment of the present invention may be implemented without relying on software such as a magnetic array and a third-party global file system.
- FIG. 1 is a flowchart of a distributed management method of a network management according to an embodiment of the present invention. As shown in Figure 1, the method includes the following processing steps:
- Step S102 the main control server starts an update to the local network management system
- Step S104 The master control server generates a slave update file that updates the network management system of the slave server.
- step S106 the master server synchronizes the above slave update file to the slave server.
- the master server since the master server generates an update file of the slave server and updates it to the slave server when updating or updating the network management system, the master server may be connected to the network management system. Management planning to different machines.
- network management system involved in the above steps may be understood as network management software for implementing network management, but is not limited thereto.
- the foregoing slave update file includes but is not limited to at least one of the following: an upgrade file and a patch file.
- the foregoing principles may be applied to the scenario where the network management system is installed in the slave server.
- the installation of the slave server server system can be implemented in the following manner: the master server starts the local device. The network management system is installed; the master server generates a slave installation file for the network management system installed in the slave server; the master server synchronizes the slave installation file to the slave server to implement the network management system on the slave server. installation.
- the master server In order to realize the real-time management of the slave server by the master server, when the network management system of the master server changes, the synchronization request of the slave server is received; the master server synchronizes the update file reflecting the change of the network management system to the slave server.
- the master server can synchronize the above slave update file to the above slave server via FTP.
- a distributed management device for the network management is further provided, which is applied to the main control server, and is used to implement the foregoing method. As shown in FIG. 2, the device includes:
- the startup module 20 is configured to initiate an update to the local network management system
- the generating module 22 is connected to the startup module 20 and configured to generate a slave update file for updating the network management system of the slave server;
- the synchronization module 24, coupled to the generation module 22, is arranged to synchronize the slave update file to the slave server.
- the startup module 20 is further configured to initiate installation of the local network management system; the generation module 22 is further configured to generate a slave installation file for the network management system installed in the slave server; the synchronization module 24. Also set to synchronize the above slave installation files to the slave server.
- each of the foregoing modules may be implemented by using hardware or software.
- the startup module 20, the generation module 22, and the synchronization module 24 are located in the same processor; or, the startup module 20, The generation module 22 and the synchronization module 24 are located in the first processor, the second processor, and the third processor, but are not limited thereto.
- a distributed management method of the network management is also provided on the slave server side. As shown in FIG. 3, the method includes:
- Step S302 the slave server receives the slave update file from the master server
- Step S304 the slave server updates the network management system installed on the slave server according to the slave update file.
- the slave server may also adopt the foregoing principles when installing the network management system.
- the network management system may be installed on the slave server in the following manner: the slave server receives the slave control.
- the slave installation file of the server, the slave installation file is used to install the network management system on the slave server; the slave server installs the network management system on the slave server according to the above slave installation file.
- the slave server monitors the network management system of the master server; and when the network management system of the master server is changed, the master server is monitored.
- the request synchronizes to reflect the update file of the above network management system change.
- a distributed management device for the network management is also provided, and the device is applied to the slave server for implementing the foregoing method.
- the device includes:
- the receiving module 40 is configured to receive a slave update file from the master server, where the slave update file is used to update the network management system of the slave server;
- the update module 42 is coupled to the receiving module 40 and configured to update the network management system installed on the slave server according to the slave update file.
- the receiving module 40 is further configured to receive a slave installation file from the master server, the slave installation file being used to install the network management system on the slave server; the update module 42 is further configured to The slave installation file installs the above network management system on the slave server.
- each of the foregoing modules may be implemented by using hardware or software.
- the receiving module 42 and the updating module 42 are located in the same processor; or, the receiving module 42 and the updating module 42 respectively It is located in the first processor and the second processor, but is not limited thereto.
- the purpose of this embodiment is to provide a system for deploying, upgrading, and expanding a network management system under a distributed network of a large-capacity network management system, so as to overcome the problem of a single management of the network management system and a bottleneck of the management scale.
- Distributed deployment of services The deployment of the southbound service (that is, the service implemented on the southbound interface) on the physical host increases the management scale. If the existing network is not affected, the new device is added. The network management service provides smooth and stable expansion.
- the upgrade of the master control server is completed, and the upgrade of all the slave servers is completed. The upgrade process is convenient and fast, and the impact on the existing network is small.
- the distributed management of the network management is implemented mainly by the method of file synchronization.
- the distributed management system provided in this embodiment includes:
- the main control server 50 The network management system installs and deploys on the main control server. After installation, an installation package for the slave service is generated.
- the master control server is responsible for the management of the slaves, such as: adding and deleting slaves and managing the switching of the service modules on different slaves; also responsible for the management of slave services, such as receiving the start or stop of the network management service command , the instruction is sent to the slave to control the service on the slave.
- the slave server 52 is configured to receive the command of the master server, and does not need to open the management interface management service on the slave server, and only needs to passively receive the command of the master server to enable and stop the services on the slave. At the same time, there is a synchronization service on the slave, the user monitors the changes on the master server and updates to the machine in time;
- a client can also be set up: the client connects to the network management system through the address of the master server, provides a user system management interface, configures, manages the device, services the device, and monitors the device alarm through the user interface. Information for device maintenance.
- the master server 50 includes:
- Configuration Management Center 500 Sets various parameters of the network management system, including database configuration and public configuration. In the public configuration, you can configure the slave information, increase the address of the slave server, and assign various service modules to the slave. Each slave's service module can add one or more services based on server hardware configuration and performance.
- the main control service module 502 is configured to manage message transmission between the service modules and control the synchronization process of the slave.
- the FTP service module 504 (equivalent to the synchronization module 24) is configured to provide a file transfer service, so that the synchronization module of the slave server synchronizes the data file of the master server to the slave server.
- the FTP server module can be on the master server or on the slave server. If deployed on the primary server, the secondary server synchronizes directly to the FTP service on the primary server.
- the main control module may further include
- the slave server 52 includes:
- the synchronization module 520 (equivalent to the update module 42) is configured to synchronize all the files on the master server, and the file includes a program file, a configuration data file, and a data file during the runtime.
- the synchronization service keeps the slave and host files consistent.
- the service module 522 is classified into a north service module, a south service module, and a database service module according to the type.
- the northbound service module provides services such as Corba, TL1, Syslog, and WebService. These service modules can be distributed across different slaves or hosts.
- Southbound service module Set to manage network devices, such as configuration management, alarm management, and performance management. This service can be divided into access, bearer and other configuration services according to the device type. It can be divided into training services, configuration services, and automatic discovery services according to functions. The same type of service can be expanded according to the management scale, only need to create instances of multiple services, distributed on the primary and secondary servers.
- Database service module set to provide database services, can be placed as a separate service on a slave server, or combined with other service modules on the same slave server, or on the master server.
- the allocation of services is configured according to the usage scenario.
- the FTP service module 524 (equivalent to the receiving module 40) is configured to provide a file transfer service, so that the slave server synchronization module can synchronize the data files of the master server to the slave server.
- the FTP server module 530 can be on the master server or on the slave server. If deployed on a slave server, the master server uploads the data file to the FTP service address on the slave.
- the synchronization module 520 is focused on implementing distributed management.
- the synchronization module 520 synchronizes the changed file directory to the slave server through FTP (File Transfer Protocol) to update the data file on the slave server.
- FTP File Transfer Protocol
- the first step network management system installation. First install on the main control server, after the installation is complete, the slave's installation package will be generated, and the installation package will be placed on the slave to install.
- the second step the database system.
- the database script is run only when it is installed on the master server, and the installation script is no longer run when the slave is installed.
- the third step upgrade and patch the network management system.
- Upgrade or patch only on the master server notify the synchronization tool to synchronize data to the slave server after completing the upgrade or patching.
- the database upgrade is only upgraded on the master server.
- Other machines update the related files through the synchronization tool, and do not involve upgrading the database. Patching is similar to upgrading, patching on the master server, and synchronizing to other slave servers through the synchronization tool.
- the fourth step expansion of the network management system.
- the synchronization service will start automatically.
- the slave server synchronization service monitors the message and automatically synchronizes all the files on the host.
- Another implementation manner of the distributed management method provided in this embodiment is as follows: In this embodiment, three hosts are taken as an example, that is, one master server and two slave servers. However, in the whole system, the slave can access multiple, not limited to the two slaves here.
- Step 1 Install a distributed network management system on a host (master server). Configure the parameter S01 of each slave server during the installation process, including the service module and network address parameters running on the slave (slave server). After the completion, the host will generate a slave installation package S03 according to the service module deployed on each slave, and will enable an FTP service. The synchronization module on the host informs the slave synchronization module to start the slave installation process S04.
- Step 2 Receive the installation notification of the host synchronization module from the synchronization module on the machine, obtain the host FTP related information and instructions from the installation notification message of the host synchronization module, start the synchronization process, and obtain the installation package of the slave from the host FTP. S05, install on the slave.
- Step 3 When the network management system is upgraded or patched, the upgrade package and the security package are placed on the main control server to perform the upgrade or patch operation. After the main control server is upgraded or patched, the host is deployed according to each slave. The service module generates an upgrade installation package S12 of the slave, and the synchronization module on the host notifies the synchronization module of the slave to start the slave upgrade process.
- Step 4 Receive the upgrade notification of the host synchronization module from the synchronization module on the machine, obtain the host FTP related information and instructions from the installation notification message of the host synchronization module, start the synchronization process, and obtain the upgrade package of the slave from the host FTP. S14, the installation is performed on the slave.
- Step 5 Expand the network management system and install the slave installation package generated in step 1 on the newly added server. After the installation is complete, the synchronization service will start automatically. Then add the slave information on the master server. After sending the startup command, the slave synchronization service monitors the message and automatically synchronizes all the files on the host.
- the existing distributed network management systems are mostly hierarchical management systems.
- the hierarchical implementation and management domain division of multiple network management stations are complicated, and the requirements for hardware devices are high.
- the above solution provided by the embodiment of the present invention can avoid the above problems and implement upgrade and expansion of the network management system.
- a storage medium is further provided, wherein the software includes the above-mentioned software, including but not limited to: an optical disk, a floppy disk, a hard disk, an erasable memory, and the like.
- modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
- the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
- the invention is not limited to any specific combination of hardware and software.
- the update file of the network management system of the slave server is generated, and the technical solution of the slave server is synchronized.
- the distributed management mode cannot meet the technical requirements of the expansion of the network scale, so that the management of the network management system on the master server can be planned to different machines, which provides strong support for the expansion of the network scale. .
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- Information Transfer Between Computers (AREA)
Abstract
本发明提供了一种网管的分布式管理方法及装置，其中，上述方法包括：主控服务器启动对本地网管系统的更新；所述主控服务器生成对从机服务器的网管系统进行更新的从机更新文件；所述主控服务器将所述从机更新文件同步至所述从机服务器。采用本发明提供的上述技术方案，解决了相关技术中，分布式管理模式不能满足网络规模的扩大要求等技术问题，从而可以将主控服务器上对网管系统的管理规划至不同的机器上，为满足网络规模的扩大提供了有力支持。
Description
本发明涉及网管技术领域，尤其是涉及一种网管的分布式管理方法及装置。
随着网络管理软件集中运维、统一管理的发展趋势，网管需要管理大规模、大容量的网络，并且管理的设备类型也由以前按照网络划分的接入网管、核心网管、承载网管等单一职责的网管系统转变为统一综合的网络管理系统。
现有的一些分布式网络管理模式为：
1.现有分布式网管系统大多数是分级管理系统，通过对多个网管站的分级配置和管理域划分，实现对大容量网络的管理。系统一般由上级网管站和下级网管站两大部分构成。上级网管站运行相应的设备，完成对下级网管站的配置，监控等功能；下级网管站利用简单网络管理协议(Simple Network Management Protocol，简称为SNMP)，对网管数据进行采集，上报，监控等。如果要扩大管理容量，需要增加下级网管的部署工作，耗时费力。
2.有些分布式网管系统采用的是功能分布式管理，通过主、从服务器架构，来实现网管功能的水平扩展。主服务器控制整个网管系统的消息分发、进程分配、对外提供网管服务等；从机服务器通过SNMP对网元进行配置管理，也可以提供北向服务(即在北向接口上实现的服务)等。
随着网络规模的增大，无法仅靠单一的设备提供网管服务，即单一设备提供网管服务不能满足网络规模的扩大要求。但是，目前相关技术中，尚无有效的解决方案。
发明内容
针对相关技术中，分布式管理模式不能满足网络规模的扩大要求等技术问题，本发明实施例提供了一种网管的分布式管理方法及装置，以至少解决上述技术问题。
根据本发明的一个实施例，提供了一种网管的分布式管理方法，包括：主控服务器启动对本地网管系统的更新；所述主控服务器生成对从机服务器的网管系统进行更新的从机更新文件；所述主控服务器将所述从机更新文件同步至所述从机服务器。
优选地，所述从机更新文件包括以下至少之一：升级文件、补丁文件。
优选地，主控服务器启动对本地网管系统的更新之前，包括：所述主控服务器启动对所述本地网管系统的安装；所述主控服务器生成用于安装在所述从机服务器中的网管系统的从机安装文件；所述主控服务器将所述从机安装文件同步至所述从机服务器。
优选地，所述主控服务器将所述从机更新文件同步至所述从机服务器之后，还包括：所述主控服务器的网管系统发生改变时，接收所述从机服务器的同步请求；所述主控服务器将反映所述网管系统改变的更新文件同步至所述从机服务器。
优选地，所述主控服务器将所述从机更新文件同步至所述从机服务器包括：所述主控服务器通过文件传输协议FTP将所述从机更新文件同步至所述从机服务器。
根据本发明的另一个实施例，提供了一种网管的分布式管理方法，包括：从机服务器接收来自主控服务器的从机更新文件；所述从机服务器根据所述从机更新文件对安装于所述从机服务器的网管系统进行更新。
优选地，从机服务器接收来自主控服务器的从机更新文件之前，包括：所述从机服务器接收来自所述主控服务器的从机安装文件，该从机安装文件用于在所述从机服务器上安装网管系统；所述从机服务器根据所述从机安装文件在所述从机服务器上安装所述网管系统。
优选地，所述从机服务器根据所述从机更新文件对安装于所述从机服务器的网管系统进行更新之后，还包括：所述从机服务器监测所述主控服务器的网管系统；在监测到所述主控服务器的网管系统发生改变时，向所述主控服务器请求同步反映所述网管系统改变的更新文件。
根据本发明的又一个实施例，提供了一种网管的分布式管理装置，应用于主控服务器，包括：启动模块，设置为启动对本地网管系统的更新；生成模块，设置为生成对从机服务器的网管系统进行更新的从机更新文件；同步模块，设置为将所述从机更新文件同步至所述从机服务器。
优选地，所述启动模块，还设置为启动对所述本地网管系统的安装；所述生成模块，还设置为生成用于安装在所述从机服务器中的网管系统的从机安装文件；所述同步模块，还设置为将所述从机安装文件同步至所述从机服务器。
根据本发明的再一个实施例，提供了一种网管的分布式管理装置，应用于从机服务器，包括：接收模块，设置为接收来自主控服务器的从机更新文件；更新模块，设置为根据所述从机更新文件对安装于所述从机服务器的网管系统进行更新。
优选地，所述接收模块，还设置为接收来自所述主控服务器的从机安装文件，该从机安装文件用于在所述从机服务器上安装网管系统；所述更新模块，还设置为根据所述从机安装文件在所述从机服务器上安装所述网管系统。
通过本发明实施例，采用在主控服务器对本地网管系统进行更新时(或更新后)，生成从机服务器的网管系统的更新文件，并同步到从机服务器的技术方案，解决了相关技术中，分布式管理模式不能满足网络规模的扩大要求等技术问题，从而可以将主控服务器上对网管系统的管理规划至不同的机器上，为满足网络规模的扩大提供了有力支持。
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1为根据本发明实施例的网管的分布式管理方法的流程图；
图2为根据本发明实施例的网管的分布式管理装置的结构框图；
图3为根据本发明实施例的另一网管的分布式管理方法的流程图；
图4为根据本发明实施例的另一网管的分布式管理装置的结构框图；
图5为根据本发明实施例的网管系统的结构框图。
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
针对相关技术中提供的网络分布式管理方案存在不能适应网络规模的扩大等技术问题，本发明实施例基于主从服务器架构，采用多台物理机器组成统一网管系统，各个进程可以根据部署规划启动在不同的物理机器(从机服务器)上，各个物理机器(服
务器)间可以彼此协作，相互通信，组成一套完整的网管系统。并且，本发明实施例中“分布式”可以不依赖于磁阵和第三方全局文件系统等软件来实现。
图1为根据本发明实施例的网管的分布式管理方法的流程图。如图1所示，该方法包括以下处理步骤：
步骤S102，主控服务器启动对本地网管系统的更新；
步骤S104，主控服务器生成对从机服务器的网管系统进行更新的从机更新文件；
步骤S106，主控服务器将上述从机更新文件同步至从机服务器。
通过上述各个处理步骤，由于主控服务器在对网管系统进行更新时或更新后，生成了从机服务器的更新文件，并将其同步至从机服务器，因此，可以将主控服务器上对网管系统的管理规划至不同的机器上。
需要说明的是，上述各个步骤中涉及到的“网管系统”可以理解为用于实现网络管理的网管软件，但不限于此
在本实施例中，上述从机更新文件包括但不限于以下至少之一：升级文件、补丁文件。
在本实施例的一个优选实施过程中，还可以将上述原理应用至从机服务器安装网管系统的场景下，例如可以通过以下方式实现从机服务器上网管系统的安装：主控服务器启动对上述本地网管系统的安装；主控服务器生成用于安装在从机服务器中的网管系统的从机安装文件；主控服务器将上述从机安装文件同步至从机服务器，以实现网管系统在从机服务器上的安装。
为实现主控服务器对从机服务器的实时管理，在主控服务器的网管系统发生改变时，接收从机服务器的同步请求；主控服务器将反映上述网管系统改变的更新文件同步至从机服务器。
在一个优选实施方式中，主控服务器可以通过FTP将上述从机更新文件同步至上述从机服务器。
在本实施例中，还提供一种网管的分布式管理装置，应用于主控服务器，用于实现上述方法，如图2所示，该装置包括：
启动模块20，设置为启动对本地网管系统的更新；
生成模块22，连接至启动模块20，设置为生成对从机服务器的网管系统进行更新的从机更新文件；
同步模块24，连接至生成模块22，设置为将上述从机更新文件同步至从机服务器。
通过上述各个模块实现的功能，同样可以实现将主控服务器上对网管系统的管理规划至不同的机器(例如从机服务器)上。
在一个优选实施方式中，启动模块20，还设置为启动对上述本地网管系统的安装；生成模块22，还设置为生成用于安装在从机服务器中的网管系统的从机安装文件；同步模块24，还设置为将上述从机安装文件同步至从机服务器。
需要说明的是，上述各个模块是可以通过硬件或软件来实现的，对于前者，可以通过以下方式实现：启动模块20、生成模块22和同步模块24位于同一处理器中；或者，启动模块20、生成模块22和同步模块24位于第一处理器、第二处理器和第三处理器中，但不限于此。
在本实施例中，还在从机服务器侧提供一种网管的分布式管理方法，如图3所示，该方法包括：
步骤S302，从机服务器接收来自主控服务器的从机更新文件；
步骤S304，从机服务器根据上述从机更新文件对安装于从机服务器的网管系统进行更新。
在本实施例中，从机服务器在安装网管系统时也可以采用上述原理，例如在一个优选实施方式中，可以采用以下方式实现网管系统在从机服务器上的安装：从机服务器接收来自主控服务器的从机安装文件，该从机安装文件用于在从机服务器上安装网管系统；从机服务器根据上述从机安装文件在从机服务器上安装上述网管系统。
为了实现从机服务器的及时更新，在本实施例中，还可以执行以下处理过程：从机服务器监测主控服务器的网管系统；在监测到主控服务器的网管系统发生改变时，向主控服务器请求同步反映上述网管系统改变的更新文件。
在本实施例中，还提供了一种网管的分布式管理装置，该装置应用于从机服务器，用于实现上述方法，如图4所示，该装置包括：
接收模块40，设置为接收来自主控服务器的从机更新文件，其中，该从机更新文件用于对从机服务器的网管系统进行更新；
更新模块42，连接至接收模块40，设置为根据上述从机更新文件对安装于从机服务器的网管系统进行更新。
在一个优选实施方式中，接收模块40，还设置为接收来自主控服务器的从机安装文件，该从机安装文件用于在从机服务器上安装网管系统；更新模块42，还设置为根据上述从机安装文件在从机服务器上安装上述网管系统。
需要说明的是，上述各个模块是可以通过硬件或软件来实现的，对于前者，可以通过以下方式实现：接收模块42和更新模块42位于同一处理器中；或者，接收模块42和更新模块42分别位于第一处理器、第二处理器中，但不限于此。
为了更好地理解上述实施例，以下结合优选实施例详细说明。
本实施例的目的在于提供一种大容量网管分布式组网下网管系统的部署、升级、扩容方案，以克服现在网管系统单一的管理，面临管理规模瓶颈局面的问题，本实施例中对网管服务分布式部署，通过在物理主机上部署南向服务(即在南向接口上实现的服务)来实现管理规模的增加，在不影响现有网络情况下，针对新增的设备来增加新增的网管服务，平滑稳定的实现扩容。并且，在网管系统升级时，通过对主控服务器的升级，来完成对所有从机服务器的升级，升级过程方便快捷，对现有网络的影响程度小。本实施例主要通过文件同步的方法来实现网管的分布式管理。
为实施上述目的，本实施例采用的技术方案如下：如图5所示，本实施例提供的分布式管理系统包括：
主控服务器50：网管系统在主控服务器上安装部署。安装后，会生成从机服务的安装包。主控服务器负责对从机的管理，如：对从机的增加、删除以及管理服务模块在不同从机上的切换；也负责对从机服务的管理，如：接收到启动或停止网管服务指令后，将指令下发到从机，控制从机上的服务。
从机服务器52：设置为接收主控服务器的指令，不需要在从机服务器上打开管理界面管理服务，只需要被动的接收主控服务器的启用、停止从机上各服务的指令。同时，从机上有个同步服务，用户监控主控服务器上的变动，及时的更新到本机上；
其中，在该分布式关系系统中还可以设置一个客户端：客户端通过主控服务器的地址，连接到网管系统，提供用户系统管理界面，通过用户界面配置、管理设备、业务开通、监控设备告警信息进行设备维护。
主控服务器50包括：
配置管理中心500：设置为配置网管系统的各类参数，包括数据库配置、公共配置等，在公共配置中，可以配置从机信息，增加从机服务器的地址，给从机分配各类服务模块，每个从机的服务模块可以根据服务器硬件配置、性能添加一个或者多个服务。
主控服务模块502：设置为管理各服务模块之间的消息发送,控制从机的同步过程。
FTP服务模块504(相当于同步模块24)：设置为提供文件传输服务，便于从机服务器的同步模块将主控服务器的数据文件同步到从机服务器上。FTP服务器模块可以在主控服务器上，也可以在从机服务器上。如果部署在主服务器上，则从机服务器直接到主控服务器上的FTP服务上进行同步。
可选地，主控模块，还可以包括
从机服务器52包括：
同步模块520(相当于更新模块42)：设置为同步主控服务器上所有文件中，文件包括程序文件、配置数据文件、运行期间数据文件。同步服务使从机和主机文件保持一致。
服务模块522：按类型分为北向服务模块、南向服务模块、数据库服务模块。
其中，北向服务模块：提供上层网管使用的服务，如：Corba、TL1、Syslog、WebService等。这些服务模块可以分布在不同的从机或者主机上运行。
南向服务模块：设置为网络设备的管理，如：配置管理、告警管理、性能管理等。此服务可以按照设备类型划分为接入、承载等配置服务，可以按照功能分为轮训服务、配置服务、自动发现服务等。同类型的服务可以根据管理规模水平扩张，只需要在创建多个服务的实例，分布在主、从服务器上。
数据库服务模块：设置为提供数据库服务，可以作为一个单独的服务放在一个从机服务器上，也可以和其他服务模块合并在同一个从机服务器上，也可以放在主控服务器上。服务的分配根据使用场景配置。
FTP服务模块524(相当于接收模块40)：设置为提供文件传输服务，便于从机服务器同步模块将主控服务器的数据文件同步到从机服务器上。FTP服务器模块530可以在主控服务器上，也可以在从机服务器上。如果部署在从机服务器上，则主控服务器上传数据文件到从机上的FTP服务地址上。
其中，同步模块520，是实现分布式管理的重点，该同步模块520通过FTP(File Transfer Protocol)将发生改动的文件目录同步至从机服务器，以更新从机服务器上的数据文件。
基于上述分布式管理系统，本实施例的一个分布式管理方法的流程如下：
第一步：网管系统安装。先在主控服务器上安装，安装完成后会生成从机的安装包，将安装包放到从机上进行安装。
第二步：数据库系统。仅仅在主控服务器上安装的时候运行数据库脚本，后续从机安装的时候不再运行安装脚本，
第三步：网管系统升级和打补丁。仅仅在主控服务器上升级或打补丁，完成升级或打补丁后通知同步工具进行数据同步到从机服务器。升级过程时，数据库的升级仅仅在主控服务器上进行升级，其他机器是通过同步工具更新升级相关文件，不涉及对数据库升级。打补丁类似于升级，在主控服务器上打补丁，通过同步工具同步到其他从机服务器。
第四步：网管系统扩容。在新增加的物理主机(主控服务器)上安装从机安装包，安装完成后，同步服务会自动启动。再在主控服务器上添加从机的信息，发送启动指令后，从机服务器同步服务监控到消息，会自动去同步主机上所有的文件。
本实施例提供的分布式管理方法的另外一个实现方式如下：本实施方式以3台主机为例，即一台主控服务器，两台从机服务器。但是整个系统中，从机是可以接入多个的，不限于此处的2台从机。
步骤1：在一台主机(主控服务器)上安装分布式网管，安装过程时配置各从机服务器的参数S01，主要包括从机(从机服务器)上运行的服务模块和网络地址参数，安装完成后，主机会根据每个从机上部署的服务模块生成一个从机的安装包S03，并会启用一个FTP服务,由主机上的同步模块通知从机的同步模块开始进行从机安装过程S04。
步骤2：从机上的同步模块接收到主机同步模块的安装通知,从主机同步模块的安装通知消息中获取主机FTP相关信息及指令,开始进行同步过程,从主机FTP上获取本从机的安装包S05，在从机上进行安装。
步骤3：网管系统升级或打补丁时，将升级包和补丁包放在主控服务器上，执行升级或打补丁的操作，主控服务器升级或打补丁完毕后，主机根据每个从机上部署的服务模块生成一个从机的升级安装包S12,由主机上的同步模块通知从机的同步模块开始进行从机升级过程。
步骤4：从机上的同步模块接收到主机同步模块的升级通知,从主机同步模块的安装通知消息中获取主机FTP相关信息及指令,开始进行同步过程,从主机FTP上获取本从机的升级包S14，在从机上进行安装。
步骤5：网管系统扩容，在新增加的服务器上安装步骤1中生成的从机安装包，安装完成后，同步服务会自动启动。再在主控服务器上添加从机的信息，发送启动指令后，从机同步服务监控到消息，会自动去同步主机上所有的文件。
综上所述，本发明实施例实现了以下有益效果：
与现有技术相比较，现有分布式网管系统，大都是分级管理系统，通过多个网管站的分级配置和管理域划分，实施过程较为复杂，而且对硬件设备的需求较多。而本发明实施例提供的上述方案则可以避免上述问题，实现网管系统的升级、扩容。
在另外一个实施例中，还提供了一种软件，该软件用于执行上述实施例及优选实施方式中描述的技术方案。
在另外一个实施例中，还提供了一种存储介质，该存储介质中存储有上述软件，该存储介质包括但不限于：光盘、软盘、硬盘、可擦写存储器等。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
通过本发明实施例提供的上述技术方案，采用在主控服务器对本地网管系统进行更新时(或更新后)，生成从机服务器的网管系统的更新文件，并同步到从机服务器的技术方案，解决了相关技术中，分布式管理模式不能满足网络规模的扩大要求等技术问题，从而可以将主控服务器上对网管系统的管理规划至不同的机器上，为满足网络规模的扩大提供了有力支持。
Claims (12)
- 一种网管的分布式管理方法，包括：主控服务器启动对本地网管系统的更新；所述主控服务器生成对从机服务器的网管系统进行更新的从机更新文件；所述主控服务器将所述从机更新文件同步至所述从机服务器。
- 根据权利要求1所述的方法，其中，所述从机更新文件，包括以下至少之一：升级文件、补丁文件。
- 根据权利要求1所述的方法，其中，主控服务器启动对本地网管系统的更新之前，包括：所述主控服务器启动对所述本地网管系统的安装；所述主控服务器生成用于安装在所述从机服务器中的网管系统的从机安装文件；所述主控服务器将所述从机安装文件同步至所述从机服务器。
- 根据权利要求1所述的方法，其中，所述主控服务器将所述从机更新文件同步至所述从机服务器之后，还包括：所述主控服务器的网管系统发生改变时，接收所述从机服务器的同步请求；所述主控服务器将反映所述网管系统改变的更新文件同步至所述从机服务器。
- 根据权利要求1至4中任一项所述的方法，其中，所述主控服务器将所述从机更新文件同步至所述从机服务器包括：所述主控服务器通过文件传输协议FTP将所述从机更新文件同步至所述从机服务器。
- 一种网管的分布式管理方法，包括：从机服务器接收来自主控服务器的从机更新文件；所述从机服务器根据所述从机更新文件对安装于所述从机服务器的网管系统进行更新。
- 根据权利要求6所述的方法，其中，从机服务器接收来自主控服务器的从机更新文件之前，包括：所述从机服务器接收来自所述主控服务器的从机安装文件，该从机安装文件用于在所述从机服务器上安装网管系统；所述从机服务器根据所述从机安装文件在所述从机服务器上安装所述网管系统。
- 根据权利要求6所述的方法，其中，所述从机服务器根据所述从机更新文件对安装于所述从机服务器的网管系统进行更新之后，还包括：所述从机服务器监测所述主控服务器的网管系统；在监测到所述主控服务器的网管系统发生改变时，向所述主控服务器请求同步反映所述网管系统改变的更新文件。
- 一种网管的分布式管理装置，应用于主控服务器，包括：启动模块，设置为启动对本地网管系统的更新；生成模块，设置为生成对从机服务器的网管系统进行更新的从机更新文件；同步模块，设置为将所述从机更新文件同步至所述从机服务器。
- 根据权利要求9所述的装置，其中，所述启动模块，还设置为启动对所述本地网管系统的安装；所述生成模块，还设置为生成用于安装在所述从机服务器中的网管系统的从机安装文件；所述同步模块，还设置为将所述从机安装文件同步至所述从机服务器。
- 一种网管的分布式管理装置，应用于从机服务器，包括：接收模块，设置为接收来自主控服务器的从机更新文件；更新模块，设置为根据所述从机更新文件对安装于所述从机服务器的网管系统进行更新。
- 根据权利要求11所述的装置，其中，所述接收模块，还设置为接收来自所述主控服务器的从机安装文件，该从机安装文件用于在所述从机服务器上安装网管系统；所述更新模块，还设置为根据所述从机安装文件在所述从机服务器上安装所述网管系统。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410295463.5 | 2014-06-26 | ||
| CN201410295463.5A CN105306237A (zh) | 2014-06-26 | 2014-06-26 | 网管的分布式管理方法及装置 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2015196654A1 true WO2015196654A1 (zh) | 2015-12-30 |
Family
ID=54936607
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2014/088975 WO2015196654A1 (zh) | 2014-06-26 | 2014-10-20 | 网管的分布式管理方法及装置 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN105306237A (zh) |
| WO (1) | WO2015196654A1 (zh) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111444047A (zh) * | 2020-03-27 | 2020-07-24 | 深圳融安网络科技有限公司 | 双机热备份的配置同步方法、双机热备系统及可读存储介质 |
| CN111787067A (zh) * | 2020-06-08 | 2020-10-16 | 浙江保融科技有限公司 | 一种多银行银企直联远程服务调用、管理方法 |
| CN114097588A (zh) * | 2021-10-29 | 2022-03-01 | 瀚云科技有限公司 | 一种灌溉装置的组网方法及装置 |
| CN115344273A (zh) * | 2022-10-19 | 2022-11-15 | 杭州比智科技有限公司 | 一种基于货架系统来运行应用软件的方法及系统 |
| CN117834653A (zh) * | 2023-12-22 | 2024-04-05 | 北京联广通网络科技有限公司 | 一种节点同步分级隔离的数据网网络安全系统 |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110392080B (zh) * | 2018-04-20 | 2023-06-06 | 杭州海康威视系统技术有限公司 | 一种基于分布式系统的部署方法、装置及分布式系统 |
| CN111147272A (zh) * | 2018-11-06 | 2020-05-12 | 厦门雅迅网络股份有限公司 | 一种单服务器及多服务器运营平台升级方法 |
| CN113960954A (zh) * | 2021-02-01 | 2022-01-21 | 厦门市智联信通物联网科技有限公司 | 一种基于微服务架构的分布式集中控制器 |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101621397A (zh) * | 2008-06-30 | 2010-01-06 | 华为技术有限公司 | 一种分布式网管系统及其维护管理方法 |
| CN102546207A (zh) * | 2010-12-23 | 2012-07-04 | 中兴通讯股份有限公司 | 一种分布式集中调度升级网元软件版本的方法和系统 |
| CN102833101A (zh) * | 2012-08-22 | 2012-12-19 | 瑞斯康达科技发展股份有限公司 | 一种分布式网络系统的软件升级方法及设备 |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1917419A (zh) * | 2006-09-04 | 2007-02-21 | 华为技术有限公司 | 增强网元设备软件补丁可靠性的系统及方法 |
| CN101267341A (zh) * | 2008-03-28 | 2008-09-17 | 华为技术有限公司 | 一种分布式网络管理系统、网管服务器和方法 |
| CN102081611B (zh) * | 2009-11-26 | 2012-12-19 | 中兴通讯股份有限公司 | 一种主、备网管系统数据库同步的实现方法及装置 |
| CN102609281B (zh) * | 2012-02-24 | 2016-01-27 | 中国电子科技集团公司第十五研究所 | 分布式软件补丁更新方法及系统 |
-
2014
- 2014-06-26 CN CN201410295463.5A patent/CN105306237A/zh not_active Withdrawn
- 2014-10-20 WO PCT/CN2014/088975 patent/WO2015196654A1/zh active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101621397A (zh) * | 2008-06-30 | 2010-01-06 | 华为技术有限公司 | 一种分布式网管系统及其维护管理方法 |
| CN102546207A (zh) * | 2010-12-23 | 2012-07-04 | 中兴通讯股份有限公司 | 一种分布式集中调度升级网元软件版本的方法和系统 |
| CN102833101A (zh) * | 2012-08-22 | 2012-12-19 | 瑞斯康达科技发展股份有限公司 | 一种分布式网络系统的软件升级方法及设备 |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111444047A (zh) * | 2020-03-27 | 2020-07-24 | 深圳融安网络科技有限公司 | 双机热备份的配置同步方法、双机热备系统及可读存储介质 |
| CN111444047B (zh) * | 2020-03-27 | 2023-12-29 | 深圳融安网络科技有限公司 | 双机热备份的配置同步方法、双机热备系统及可读存储介质 |
| CN111787067A (zh) * | 2020-06-08 | 2020-10-16 | 浙江保融科技有限公司 | 一种多银行银企直联远程服务调用、管理方法 |
| CN111787067B (zh) * | 2020-06-08 | 2023-04-07 | 浙江保融科技股份有限公司 | 一种多银行银企直联远程服务调用、管理方法 |
| CN114097588A (zh) * | 2021-10-29 | 2022-03-01 | 瀚云科技有限公司 | 一种灌溉装置的组网方法及装置 |
| CN114097588B (zh) * | 2021-10-29 | 2023-10-31 | 瀚云科技有限公司 | 一种灌溉装置的组网方法及装置 |
| CN115344273A (zh) * | 2022-10-19 | 2022-11-15 | 杭州比智科技有限公司 | 一种基于货架系统来运行应用软件的方法及系统 |
| CN117834653A (zh) * | 2023-12-22 | 2024-04-05 | 北京联广通网络科技有限公司 | 一种节点同步分级隔离的数据网网络安全系统 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105306237A (zh) | 2016-02-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2015196654A1 (zh) | 网管的分布式管理方法及装置 | |
| CN108809722B (zh) | 一种部署Kubernetes集群的方法、装置和存储介质 | |
| CN103167041B (zh) | 一种支持云环境应用集群自动化部署的系统及方法 | |
| JP6549787B2 (ja) | ネットワークサービスをデプロイするための方法及び装置 | |
| JP6217034B2 (ja) | 関連プラグインの管理方法、装置およびシステム | |
| EP3059900B1 (en) | Network service template management method and device | |
| WO2018141183A1 (zh) | 一种编排管理系统和网络切片处理方法 | |
| WO2014169870A1 (zh) | 虚拟网元自动装载及虚拟机ip地址获取的方法与系统、存储介质 | |
| CN105553741A (zh) | 一种基于云计算的应用系统自动化部署方法 | |
| CN113742031B (zh) | 节点状态信息获取方法、装置、电子设备及可读存储介质 | |
| CN104363122B (zh) | 一种网元的预配置方法和系统 | |
| CN110764918A (zh) | 一种容器集群中主节点管理方法 | |
| CN108780405A (zh) | 网络功能虚拟化环境下应用的管理方法和装置 | |
| CN113965585B (zh) | 一种多云互联方法及装置 | |
| CN115604120B (zh) | 一种多云集群资源共享方法、装置、设备及存储介质 | |
| CN112152843B (zh) | 一种集群节点部署方法、装置、系统和电子设备 | |
| KR20170043966A (ko) | Nfv 시스템 및 vnfm 연동 방법 | |
| CN110784347A (zh) | 一种容器集群的节点管理方法、系统、设备及存储介质 | |
| CN104516744A (zh) | 软件更新方法及系统 | |
| WO2016192432A1 (zh) | 一种网络管理系统部署方法、装置和网络管理系统 | |
| CN107092502A (zh) | 一种基于云操作系统的应用自动配置方法和装置 | |
| CN112181049B (zh) | 集群时间同步方法、装置、系统、设备及可读存储介质 | |
| US20130346962A1 (en) | Mechanism and system for deploying software over clouds | |
| WO2016197953A1 (zh) | 一种部署多模基站的方法及装置 | |
| CN209881824U (zh) | 一种基于私有云平台的数据中心和云计算系统 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14896044 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 14896044 Country of ref document: EP Kind code of ref document: A1 |