WO2015149625A1 - 一种多实例并行的网元接入方法和系统 - Google Patents

一种多实例并行的网元接入方法和系统 Download PDF

Info

Publication number
WO2015149625A1
WO2015149625A1 PCT/CN2015/074530 CN2015074530W WO2015149625A1 WO 2015149625 A1 WO2015149625 A1 WO 2015149625A1 CN 2015074530 W CN2015074530 W CN 2015074530W WO 2015149625 A1 WO2015149625 A1 WO 2015149625A1
Authority
WO
WIPO (PCT)
Prior art keywords
network management
server
network
rmi
address
Prior art date
Application number
PCT/CN2015/074530
Other languages
English (en)
French (fr)
Inventor
谢沛欣
张继坤
薛林
Original Assignee
大唐移动通信设备有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 大唐移动通信设备有限公司 filed Critical 大唐移动通信设备有限公司
Publication of WO2015149625A1 publication Critical patent/WO2015149625A1/zh

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
    • H04L41/02—Standardisation; Integration
    • H04L41/0226—Mapping or translating multiple network management protocols
    • 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
    • H04L41/02—Standardisation; Integration
    • H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]

Definitions

  • the present invention relates to the field of network technologies, and in particular, to a multi-instance parallel network element access method and system.
  • the common access modes of network elements in the network management system are shown in Figure 1.
  • the network element and the network management system implement a protocol conversion and message transmission and reception through a single network management agent.
  • the single network management agent deployment mode shown in Figure 1 can complete the information interaction between the network management server and the network element without any problem.
  • the deployment mode shown in FIG. 1 faces a huge problem of upstream and downstream messages, which causes great pressure on the network management agent.
  • Practice has proved that the deployment of this single network management agent is very likely to cause server crash in the actual network environment, resulting in message backlog and loss, thus affecting the normal operation of the network.
  • the present invention provides a multi-instance parallel network element access method and system, which can solve the problem of message backlog and loss generated when the network management server sends a large number of network element access requests.
  • a multi-instance parallel network element access method wherein a remote method call server RMI SERVER and two Internet access agent agents are set between the network management server and the network element, and the method includes:
  • the network management server sends a network element access request message to the RMI SERVER, where the network element access request message carries the identification identifier of the access network element and the remote method invokes the RMI identifier;
  • the RMI SERVER invokes a network management agent according to the RMI identifier carried in the network element access request message;
  • the called network management agent uses the simple network management protocol SNMP to perform protocol conversion on the network element access request message, and sends the message to the corresponding network element.
  • the RMI SERVER is an operation and maintenance center OMC server.
  • the two servers are deployed on a single server of multiple network cards, and the single server starts multiple IP addresses, and assigns an IP address to each network management agent;
  • the two network management agents of the network management agent are respectively deployed on one server, and the IP address of each network management agent is the IP address of the server where the network management agent is located.
  • the single server starts multiple IP addresses including one primary IP address and the remaining multiple virtual IP addresses.
  • the RMI identifier includes: an IP address of the called network management agent, a port number of the called network management agent, and a called network management agent when the two server agents are deployed on a single server of the multiple network card.
  • An instance name an IP address of the called network management agent bound to the instance name;
  • the RMI identifier includes: an IP address of the called network management agent, a port number of the called network management agent, and the called network management The instance name of the proxy.
  • the IP address used by the SNMP is the IP address of the called network management agent when the two server agents are deployed on a single server of multiple network cards;
  • the IP address used by the SNMP is the first non-loopback IP address of the automatically deployed server with the network management agent.
  • a multi-instance parallel network element access system the system comprises a network management server, a remote method call server RMI SERVER, two Internet access agent and a network element, wherein
  • a network management server configured to send a network element access request message to the RMI SERVER, where the network element access request message has an identification identifier of the access network element and a remote method call RMI identifier;
  • An RMI SERVER configured to invoke a network management agent according to the RMI identifier received in the network element access request message
  • the network management agent is configured to perform the protocol conversion by using the simple network management protocol (SNMP) to send the network element access request message to the corresponding network element.
  • SNMP simple network management protocol
  • the RMI SERVER is an operation and maintenance center OMC server.
  • the two servers are deployed on a single server of multiple network cards, and the single server starts multiple IP addresses, and assigns an IP address to each network management agent;
  • the two network management agents of the network management agent are respectively deployed on one server, and the IP address of each network management agent is the IP address of the server where the network management agent is located.
  • the multiple IP addresses initiated by the single server include one primary IP address and the remaining multiple virtual IP addresses.
  • the RMI identifier includes: an IP address of the invoked network management agent, a port number of the called network management agent, and is invoked when the two server agents are deployed on a single server of the multiple network card.
  • the instance name of the network management agent, and the IP address of the called network management agent bound to the instance name;
  • the RMI identifier includes: an IP address of the called network management agent, a port number of the called network management agent, and the called network management The instance name of the proxy.
  • the IP address used by the SNMP is the IP address of the called network management agent when the two server agents are deployed on a single server of multiple network cards;
  • the IP address used by the SNMP is the first non-loopback IP address of the automatically deployed server with the network management agent.
  • a remote method call server RMI SERVER and two Internet access agent agents are set between the network management server and the network element, and the network management server sends the network element access request carrying the RMI identifier to the RMI SERVER, and the RMI SERVER is based on the RMI.
  • the identifier selects a network management agent, and sends the network element access request to the corresponding network element through the network management agent.
  • the network management server has a large number of network element access requests
  • the network element access request may be distributed to multiple network management agents. Therefore, the pressure of each network management agent is alleviated, and the method effectively avoids the problem of backlog, loss, and even server downtime generated when the network management server has a large number of network element access requests.
  • deploying more than two network management agents on a single server not only improves the processing efficiency of the message, but also improves the utilization of the system memory.
  • the IP address of the called network management agent bound to the instance name is added to the RMI identifier to distinguish the deployments in the same Multiple network management agents on the server.
  • the network management agent IP address of the called network management protocol is used to make the network management agent IP address of the called network management agent avoid the deployment on the same server.
  • more than two network management agents can be deployed on a single server or on more than two servers, thereby increasing deployment flexibility.
  • Figure 1 is a schematic diagram of a single network management agent deployment
  • FIG. 2 is a schematic diagram of deployment of a multi-network management agent in Embodiment 1 of the present invention
  • FIG. 3 is a schematic diagram of a multi-instance parallel network element access method according to Embodiment 1 of the present invention.
  • FIG. 5 is a flowchart of a multi-instance parallel network element access method according to Embodiment 2 of the present invention.
  • FIG. 6 is a flowchart of a multi-instance parallel network element access method in Embodiment 3 of the present invention.
  • FIG. 7 is a schematic structural diagram of a multi-instance parallel network element access system according to Embodiment 4 of the present invention.
  • the embodiment of the present invention provides a multi-instance parallel network element access method.
  • a remote method call server RMI SERVER and two Internet access pipes are set between the network management server and the network element.
  • Agent the method includes the following steps:
  • Step 401 The network management server sends a network element access request message to the remote method invocation server (RMI), where the network element access request message carries the identification identifier of the access network element and the remote method invokes the RMI identifier.
  • RMI remote method invocation server
  • Step 402 The RMI SERVER invokes a network management agent according to the RMI identifier carried in the network element access request message.
  • Step 403 The invoked network management agent uses the Simple Network Management Protocol (SNMP) to convert the network element access request message into a protocol, and sends the message to the corresponding network element.
  • SNMP Simple Network Management Protocol
  • a remote method call server RMI SERVER and two Internet access agent agents are set between the network management server and the network element, and the network management server sends the network element access request carrying the RMI identifier to the RMI SERVER, RMI SERVER.
  • Select a network management agent according to the RMI identifier and send the network element access request to the corresponding network element through the network management agent.
  • the network management server has a large number of network element accesses.
  • the network element access request can be distributed to multiple network management agents, thereby alleviating the pressure of each network management agent. This method effectively avoids the backlog and loss of messages generated when the network management server has a large number of network element access requests. Even the problem of server downtime.
  • Step 501 Set a remote method to call the server RMI SERVER between the network management server and the network element, and two of the network management agents, and deploy two or more network management agents on the single server.
  • two or more network management agents are deployed on a single server of multiple network cards, and a single server starts multiple IP addresses, including one primary IP address and multiple virtual IP addresses, and a single server is deployed on each of them.
  • the network management agent assigns an IP address. Deploying more than two network management agents on a single server not only improves the processing efficiency of messages, but also improves the system memory utilization.
  • Step 502 The network management server sends a network element access request message to the RMI SERVER, where the network element access request message carries the identification identifier of the access network element and the RMI identifier.
  • the RMI SERVER is an operation and maintenance center OMC server
  • the network management server sends a network element access request message to the operation and maintenance center OMC server
  • the network element access request message carries an identification identifier of the access network element
  • the identification identifier of the access network element is the ID of the network element, that is, the number or symbol of the network element is uniquely determined
  • the RMI identifier is also included in the network element access request message, and the RMI identifier includes: the IP address of the called network management agent.
  • the port number of the called network management agent, the instance name of the called network management agent, and the IP address of the called network management agent bound to the instance name.
  • the IP address of the called network management agent bound to the instance name is added to the RMI identifier to distinguish multiple deployed on the same server.
  • Network management agent Since two or more network management agents are deployed on a single server of multiple network adapters, the IP address of the called network management agent bound to the instance name is added to the RMI identifier to distinguish multiple deployed on the same server. Network management agent.
  • Step 503 The RMI SERVER invokes a network management agent according to the RMI identifier received in the network element access request message.
  • the RMI SERVER is an operation maintenance center (OMC) server
  • the operation and maintenance center OMC server invokes a network management agent according to the RMI identifier received in the network element access request message.
  • the operation and maintenance center OMC server finds the corresponding network management agent according to the IP address of the called network management agent bound to the instance name in the RMI identifier, thereby calling the network management agent.
  • Step 504 The called network management agent uses the simple network management protocol SNMP to perform protocol conversion on the network element access request message, and sends the message to the corresponding network element.
  • the SNMP service is first assigned an IP address that is consistent with the IP address of the invoked network management agent.
  • the invoked network management agent uses the SNMP protocol to perform protocol conversion on the network element access request message, and finds the information of the corresponding network element, and sends the information to the corresponding network element.
  • the invoked network management proxy IP address in the SNMP protocol of the network management agent By using the invoked network management proxy IP address in the SNMP protocol of the network management agent, the IP address conflict problem of the SNMP service generated when multiple network management agents deployed on the same server use the SNMP service is avoided.
  • a remote method call server RMI SERVER and two Internet access agent agents are set between the network management server and the network element, and the network management server sends the network element access request carrying the RMI identifier to the RMI SERVER, RMI SERVER. Selecting a network management agent according to the RMI identifier, and sending the network element access request to the corresponding network element through the network management agent.
  • the network management server has a large number of network element access requests, the network element access request may be distributed to multiple network management systems. In the agent, thereby alleviating the pressure of each network management agent, the method effectively avoids the problem of backlog, loss, and even server downtime generated when the network management server has a large number of network element access requests.
  • Step 601 Set a remote method between the network management server and the network element to invoke the server RMI SERVER and two to use the Internet management agent to deploy more than two network management agents on more than two servers.
  • the IP address of the network management agent is the IP address of each server.
  • Step 602 The network management server sends a network element access request message to the RMI SERVER, where the network element access request message carries the identification identifier of the access network element and the RMI identifier.
  • the RMI SERVER is an operation and maintenance center OMC server
  • the network management server sends a network element access request message to the operation and maintenance center OMC server
  • the identification identifier of the access network element in the network element access request message is the network.
  • the ID of the element that is, the number or symbol that uniquely identifies a network element
  • the RMI identifier also included in the network element access request message.
  • the RMI identifier includes: the IP address of the called network management agent, and the port number of the called network management agent. The instance name of the called network management agent.
  • Step 603 The RMI SERVER invokes a network management agent according to the RMI identifier received in the network element access request message.
  • the RMI SERVER is an operation and maintenance center OMC server, and the operation and maintenance center OMC server invokes a network management agent according to the RMI identifier received in the network element access request message, specifically, the RMI SERVER is based on The IP address of the called network management agent in the RMI identifier finds the corresponding server, and then finds the network management agent deployed on the server, thereby calling the network. Pipe agent.
  • Step 604 The called network management agent uses the simple network management protocol SNMP to perform protocol conversion on the network element access request message, and sends the message to the corresponding network element.
  • the first non-loopback IP address of the automatically deployed server with the network management agent is used as the IP address of the SNMP service of the network management agent.
  • the invoked network management agent uses the simple network management protocol SNMP to perform protocol conversion on the network element access request message, and obtains information such as the ID and configuration data of the access network element, and configures data and other information according to the ID of the access network element. Send to the corresponding network element.
  • a remote method call server RMI SERVER and two Internet access agent agents are set between the network management server and the network element, and the network management server sends the network element access request carrying the RMI identifier to the RMI SERVER, RMI SERVER. Selecting a network management agent according to the RMI identifier, and sending the network element access request to the corresponding network element through the network management agent.
  • the network management server has a large number of network element access requests, the network element access request may be distributed to multiple network management systems. In the agent, thereby alleviating the pressure of each network management agent, the method effectively avoids the problem of backlog, loss, and even server downtime generated when the network management server has a large number of network element access requests.
  • the embodiment of the present invention provides a multi-instance parallel network element access system.
  • the system includes a network management server 701, a remote method call server RMI SERVER 702, two Internet access agent 703 and a network element 704.
  • the network management server 701 is configured to send a network element access request message to the RMI SERVER 702, where the network element access request message carries an identification identifier and an RMI identifier of the access network element.
  • the RMI SERVER 702 is configured to invoke a network management agent according to the RMI identifier received in the network element access request message.
  • the network management agent 703 is configured to perform protocol conversion on the network element access request message by using a simple network management protocol (SNMP), and send the message to the corresponding network element 704.
  • SNMP simple network management protocol
  • the RMI SERVER is an operation and maintenance center OMC server.
  • the two servers are deployed on a single server of multiple network cards, and the single server starts multiple IP addresses, and assigns an IP address to each network management agent.
  • the multiple IP addresses initiated by the single server include one primary IP address and the remaining multiple virtual IP addresses.
  • the RMI identifier includes: an IP address of the invoked network management agent, a port number of the called network management agent, an instance name of the invoked network management agent, and a called network management agent bound to the instance name. IP address.
  • the IP address used by the SNMP is the IP address of the called network management agent.
  • the two network management agents of the network management agent are respectively deployed on one server, and the IP address of the network management agent is the IP address of each server.
  • the RMI identifier includes: an IP address of the invoked network management agent, a port number of the called network management agent, and an instance name of the called network management agent.
  • the IP address used by the SNMP is the first non-loopback IP address of the automatically deployed server deployed with the network management agent.
  • a remote method call server RMI SERVER and two Internet access agent agents are set between the network management server and the network element, and the network management server sends the network element access request carrying the RMI identifier to the RMI SERVER, RMI SERVER. Selecting a network management agent according to the RMI identifier, and sending the network element access request to the corresponding network element through the network management agent.
  • the network management server has a large number of network element access requests, the network element access request may be distributed to multiple network management systems. In the agent, thereby alleviating the pressure of each network management agent, the method effectively avoids the problem of backlog, loss, and even server downtime generated when the network management server has a large number of network element access requests.
  • deploying more than two network management agents on a single server not only improves the processing efficiency of the message, but also improves the utilization of the system memory.
  • the IP address of the called network management agent bound to the instance name is added to the RMI identifier to distinguish the deployment in the same Multiple network management agents on the server.
  • the network management agent IP address of the called network management protocol is used to make the network management agent IP address of the called network management agent avoid the deployment on the same server.
  • more than two network management agents may be deployed on a single server or on more than two servers, thereby increasing deployment flexibility.
  • a remote method call server RMI SERVER and two Internet access agent agents are set between the network management server and the network element, and the network management server sends the network element access request carrying the RMI identifier to the RMI SERVER, and the RMI SERVER is based on the RMI.
  • the identifier selects a network management agent, and sends the network element access request to the corresponding network element through the network management agent.
  • the network management server has a large number of network element access requests
  • the network element access request may be distributed to multiple network management agents. Therefore, the pressure of each network management agent is alleviated, and the method effectively avoids the problem of backlog, loss, and even server downtime generated when the network management server has a large number of network element access requests.
  • deploying more than two network management agents on a single server not only improves the processing efficiency of the message, but also improves the utilization of the system memory.
  • the IP address of the called network management agent bound to the instance name is added to the RMI identifier to distinguish the deployments in the same Multiple network management agents on the server.
  • the network management agent IP address of the called network management protocol is used to make the network management agent IP address of the called network management agent avoid the deployment on the same server.
  • more than two network management agents can be deployed on a single server or on more than two servers, thereby increasing deployment flexibility.

Abstract

本发明提供了一种多实例并行的网元接入方法和系统，在网管服务器和网元之间设置远程方法调用服务器RMI SERVER和两个以上的网管代理，该方法包括：网管服务器向RMI SERVER发送网元接入请求消息，该网元接入请求消息中带有接入网元的识别标识和RMI标识；RMI SERVER根据接收到所述网元接入请求消息中带有的RMI标识调用某一网管代理；所述被调用的网管代理利用简单网络管理协议SNMP将所述网元接入请求消息进行协议转换，发送给对应的网元。本发明能够解决当网管服务器发送大量网元接入请求时产生的消息积压和丢失问题。

Description

一种多实例并行的网元接入方法和系统 技术领域
本发明涉及网络技术领域，具体涉及一种多实例并行的网元接入方法和系统。
背景技术
网管系统中网元常见的接入方式如图1所示，网元与网管系统经过单个网管代理来实现协议转化和消息的发送接收。
在网元接入数量不大时，图1所示的单网管代理部署方式可以无障碍地完成网管服务器和网元之间的信息交互。但是在网管服务器发送大量网元接入请求的网络环境中，图1所示的部署方式面临着上游和下游消息量巨大的问题，这样会给网管代理造成巨大的压力。实践证明这种单网管代理的部署的方式在实际的网络环境中极易造成服务器崩溃，导致消息积压、丢失，从而影响网络的正常工作。
发明内容
针对现有技术的不足，本发明提供一种多实例并行的网元接入方法和系统，能够解决当网管服务器发送大量网元接入请求时产生的消息积压和丢失问题。
为实现上述目的，本发明通过以下技术方案予以实现：
一种多实例并行的网元接入方法，在网管服务器和网元之间设置远程方法调用服务器RMI SERVER和两个以上网管代理，该方法包括：
网管服务器向RMI SERVER发送网元接入请求消息，该网元接入请求消息中带有接入网元的识别标识和远程方法调用RMI标识；
RMI SERVER根据所述网元接入请求消息中带有的RMI标识调用某一网管代理；
所述被调用的网管代理利用简单网络管理协议SNMP将所述网元接入请求消息进行协议转换，发送给对应的网元。
其中，所述RMI SERVER为操作维护中心OMC服务器。
其中，所述两个以上网管代理部署在多网卡的单服务器上，所述单服务器启动多个IP地址，为每个网管代理分配一个IP地址；
或，
所述两个以上网管代理中的任一网管代理分别部署在一个服务器上，每个网管代理的IP地址为其所在服务器的IP地址。
其中，所述单服务器启动多个IP地址中包括一个主IP地址和其余多个虚拟IP地址。
其中，当所述两个以上网管代理部署在多网卡的单服务器上时，所述RMI标识包括：被调用的网管代理的IP地址、被调用的网管代理的端口号、被调用的网管代理的实例名、绑定在所述实例名后的被调用的网管代理的IP地址；
当所述两个以上网管代理中的任一网管代理分别部署在一个服务器上时，所述RMI标识包括：被调用的网管代理的IP地址、被调用的网管代理的端口号、被调用的网管代理的实例名。
其中，当所述两个以上网管代理部署在多网卡的单服务器上时，所述SNMP使用的IP地址为被调用的网管代理的IP地址；
当所述两个以上网管代理中的任一网管代理分别部署在一个服务器上时，所述SNMP使用的IP地址为自动获取的部署有网管代理的服务器的第一个非回环的IP地址。
一种多实例并行的网元接入系统，该系统包括网管服务器、远程方法调用服务器RMI SERVER、两个以上网管代理和网元，其中，
网管服务器，用于向所述RMI SERVER发送网元接入请求消息，该网元接入请求消息中带有接入网元的识别标识和远程方法调用RMI标识；
RMI SERVER，用于根据接收到所述网元接入请求消息中带有的RMI标识调用某一网管代理；
网管代理，用于利用简单网络管理协议SNMP将所述网元接入请求消息进行协议转换，发送给对应的网元。
其中，所述RMI SERVER为操作维护中心OMC服务器。
其中，所述两个以上网管代理部署在多网卡的单服务器上，所述单服务器启动多个IP地址，为每个网管代理分配一个IP地址；
或，
所述两个以上网管代理中的任一网管代理分别部署在一个服务器上，每个网管代理的IP地址为其所在服务器的IP地址。
其中，所述单服务器启动的多个IP地址中包括一个主IP地址和其余多个虚拟IP地址。
其中，当所述两个以上网管代理部署在多网卡的单服务器上时，所述RMI标识包括：被调用的网管代理的IP地址、被调用的网管代理的端口号、被调用 的网管代理的实例名、绑定在所述实例名后的被调用的网管代理的IP地址；
当所述两个以上网管代理中的任一网管代理分别部署在一个服务器上时，所述RMI标识包括：被调用的网管代理的IP地址、被调用的网管代理的端口号、被调用的网管代理的实例名。
其中，当所述两个以上网管代理部署在多网卡的单服务器上时，所述SNMP使用的IP地址为被调用的网管代理的IP地址；
当所述两个以上网管代理中的任一网管代理分别部署在一个服务器上时，所述SNMP使用的IP地址为自动获取的部署有网管代理的服务器的第一个非回环的IP地址。
本发明至少具有如下的有益效果：
1、在本发明中，在网管服务器和网元之间设置远程方法调用服务器RMI SERVER和两个以上网管代理，网管服务器将携带RMI标识的网元接入请求发送给RMI SERVER，RMI SERVER根据RMI标识选择某一网管代理，通过网管代理将其网元接入请求发送给对应的网元，当网管服务器有大量网元接入请求时，可以将网元接入请求分散到多个网管代理中，从而缓解每个网管代理的压力，该方法有效避免了在网管服务器有大量网元接入请求时产生的消息积压、丢失，甚至服务器宕机的问题。
2、在本发明中，在单服务器上部署两个以上的网管代理不但提高了消息的处理效率，还提高了系统内存的利用率。
3、在本发明中，当两个以上的网管代理部署在多网卡的单服务器上时，在RMI标识中增加绑定在实例名后面的被调用的网管代理的IP地址，来区分部署在同一服务器上的多个网管代理。
4、在本发明中，当两个以上的网管代理部署在多网卡的单服务器上时，通过令网管代理中的简单网络管理协议SNMP使用被调用的网管代理IP地址，避免了部署在同一服务器上的多个网管代理在使用SNMP服务时，所产生的SNMP服务IP地址冲突问题。
5、本发明中两个以上的网管代理可以部署在单个服务器上，也可以部署在两个以上服务器上，从而增加了部署的灵活性。
当然，实施本发明的任一方法或产品不一定需要同时达到以上所述的所有优点。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例 或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是单网管代理部署示意图；
图2是本发明实施例1中多网管代理部署示意图；
图3是本发明实施例1中多实例并行的网元接入方法的示意图；
图4是本发明实施例1中多实例并行的网元接入方法的流程图；
图5是本发明实施例2中多实例并行的网元接入方法的流程图；
图6是本发明实施例3中多实例并行的网元接入方法的流程图；
图7是本发明实施例4中多实例并行的网元接入系统的结构示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整的描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
实施例1
本发明实施例提出了一种多实例并行的网元接入方法，参见图2、图3和图4，首先，在网管服务器和网元之间设置远程方法调用服务器RMI SERVER和两个以上网管代理，该方法包括如下步骤：
步骤401：网管服务器向远程方法调用服务器RMI(Remote Method Invocation)SERVER发送网元接入请求消息，该网元接入请求消息中带有接入网元的识别标识和远程方法调用RMI标识。
步骤402：RMI SERVER根据所述网元接入请求消息中带有的RMI标识调用某一网管代理。
步骤403：所述被调用的网管代理利用简单网络管理协议SNMP(Simple Network Management Protocol)将所述网元接入请求消息进行协议转换，发送给对应的网元。
可见，在本发明实施例中，在网管服务器和网元之间设置远程方法调用服务器RMI SERVER和两个以上网管代理，网管服务器将携带RMI标识的网元接入请求发送给RMI SERVER，RMI SERVER根据RMI标识选择某一网管代理，通过网管代理将其网元接入请求发送给对应的网元，当网管服务器有大量网元接入 请求时，可以将网元接入请求分散到多个网管代理中，从而缓解每个网管代理的压力，该方法有效避免了在网管服务器有大量网元接入请求时产生的消息积压、丢失，甚至服务器宕机的问题。
实施例2
下面通过一个具体的例子，来详细介绍当两个以上的网管代理部署在单服务器上时，本发明所述的多实例并行的网元接入方法的实现过程，参见图5，包括如下步骤：
步骤501：在网管服务器和网元之间设置远程方法调用服务器RMI SERVER和两个以上网管代理，将两个以上的网管代理部署在单服务器上。
在本步骤中，将两个以上的网管代理部署在多网卡的单服务器上，单服务器启动多个IP地址，包括一个主IP地址和多个虚拟IP地址，单服务器为部署在其上每个网管代理分配一个IP地址。在单服务器上部署两个以上的网管代理不但提高了消息的处理效率，还提高了系统内存的利用率。
步骤502：网管服务器向RMI SERVER发送网元接入请求消息，该网元接入请求消息中带有接入网元的识别标识和RMI标识。
在本步骤中，所述RMI SERVER为操作维护中心OMC服务器，网管服务器向操作维护中心OMC服务器发送网元接入请求消息，网元接入请求消息中带有接入网元的识别标识，其中接入网元的识别标识为网元的ID，即唯一确定一个网元的数字或符号，网元接入请求消息中还带有的RMI标识，RMI标识包括：被调用的网管代理的IP地址、被调用的网管代理的端口号、被调用的网管代理的实例名、绑定在所述实例名后的被调用的网管代理的IP地址。
由于两个以上的网管代理部署在多网卡的单服务器上，所以在RMI标识中增加绑定在实例名后面的被调用的网管代理的IP地址，以此来区分部署在同一服务器上的多个网管代理。
步骤503：RMI SERVER根据接收到所述网元接入请求消息中带有的RMI标识调用某一网管代理。
在本步骤中，所述RMI SERVER为操作维护中心OMC(Operation Maintenance Center)服务器，操作维护中心OMC服务器根据接收到所述网元接入请求消息中带有的RMI标识调用某一网管代理，具体地，操作维护中心OMC服务器根据RMI标识中的绑定在实例名后的被调用的网管代理的IP地址找出对应的网管代理，从而调用该网管代理。
步骤504：所述被调用的网管代理利用简单网络管理协议SNMP将所述网元接入请求消息进行协议转换，发送给对应的网元。
在本步骤中，首先为SNMP服务分配与被调用的网管代理的IP地址一致的IP地址。被调用的网管代理利用SNMP协议将所述网元接入请求消息进行协议转换，找出对应网元的信息，发送给对应的网元。通过令网管代理中的SNMP协议使用被调用的网管代理IP地址，避免了部署在同一服务器上的多个网管代理在使用SNMP服务时，所产生的SNMP服务IP地址冲突问题。
可见，在本发明实施例中，在网管服务器和网元之间设置远程方法调用服务器RMI SERVER和两个以上网管代理，网管服务器将携带RMI标识的网元接入请求发送给RMI SERVER，RMI SERVER根据RMI标识选择某一网管代理，通过网管代理将其网元接入请求发送给对应的网元，当网管服务器有大量网元接入请求时，可以将网元接入请求分散到多个网管代理中，从而缓解每个网管代理的压力，该方法有效避免了在网管服务器有大量网元接入请求时产生的消息积压、丢失，甚至服务器宕机的问题。
实施例3
下面通过一个具体的例子，来详细介绍当两个以上的网管代理部署在两个以上服务器上时，本发明所述的多实例并行的网元接入方法的实现过程，参见图6，包括如下步骤：
步骤601：在网管服务器和网元之间设置远程方法调用服务器RMI SERVER和两个以上网管代理，将两个以上的网管代理部署在两个以上服务器上。
在本步骤中，将两个以上网管代理中的任意一个网管代理分别部署在一个服务器上，网管代理的IP地址为每个服务器的IP地址。
步骤602：网管服务器向RMI SERVER发送网元接入请求消息，该网元接入请求消息中带有接入网元的识别标识和RMI标识。
在本步骤中，所述RMI SERVER为操作维护中心OMC服务器，网管服务器向操作维护中心OMC服务器发送网元接入请求消息，网元接入请求消息中带有接入网元的识别标识为网元的ID，即唯一确定一个网元的数字或符号，网元接入请求消息中还带有的RMI标识，RMI标识包括：被调用的网管代理的IP地址、被调用的网管代理的端口号、被调用的网管代理的实例名。
步骤603：RMI SERVER根据接收到所述网元接入请求消息中带有的RMI标识调用某一网管代理。
在本步骤中，所述RMI SERVER为操作维护中心OMC服务器，操作维护中心OMC服务器根据接收到所述网元接入请求消息中带有的RMI标识调用某一网管代理，具体地，RMI SERVER根据RMI标识中的被调用的网管代理的IP地址找出对应的服务器，进而找出部署在该服务器上的网管代理，从而调用该网 管代理。
步骤604：所述被调用的网管代理利用简单网络管理协议SNMP将所述网元接入请求消息进行协议转换，发送给对应的网元。
在本步骤中，将自动获取的部署有网管代理的服务器的第一个非回环的IP地址作为网管代理的SNMP服务的IP地址。被调用的网管代理利用简单网络管理协议SNMP将所述网元接入请求消息进行协议转换，得到接入网元的ID和配置数据等信息，根据接入网元的ID，将配置数据等信息发送给对应的网元。
可见，在本发明实施例中，在网管服务器和网元之间设置远程方法调用服务器RMI SERVER和两个以上网管代理，网管服务器将携带RMI标识的网元接入请求发送给RMI SERVER，RMI SERVER根据RMI标识选择某一网管代理，通过网管代理将其网元接入请求发送给对应的网元，当网管服务器有大量网元接入请求时，可以将网元接入请求分散到多个网管代理中，从而缓解每个网管代理的压力，该方法有效避免了在网管服务器有大量网元接入请求时产生的消息积压、丢失，甚至服务器宕机的问题。
实施例4
本发明实施例提出了一种多实例并行的网元接入系统，参见图7该系统包括网管服务器701、远程方法调用服务器RMI SERVER 702、两个以上网管代理703和网元704，其中，
网管服务器701，用于向所述RMI SERVER 702发送网元接入请求消息，该网元接入请求消息中带有接入网元的识别标识和RMI标识；
RMI SERVER 702，用于根据接收到所述网元接入请求消息中带有的RMI标识调用某一网管代理；
网管代理703，用于利用简单网络管理协议SNMP将所述网元接入请求消息进行协议转换，发送给对应的网元704。
其中，所述RMI SERVER为操作维护中心OMC服务器。
其中，所述两个以上网管代理部署在多网卡的单服务器上，所述单服务器启动多个IP地址，为每个网管代理分配一个IP地址。
其中，所述单服务器启动的多个IP地址中包括一个主IP地址和其余多个虚拟IP地址。
其中，所述RMI标识包括：被调用的网管代理的IP地址、被调用的网管代理的端口号、被调用的网管代理的实例名、绑定在所述实例名后的被调用的网管代理的IP地址。
其中，所述SNMP使用的IP地址为被调用的网管代理的IP地址。
其中，所述两个以上网管代理中的任意一个网管代理分别部署在一个服务器上，网管代理的IP地址为每个服务器的IP地址。
其中，所述RMI标识包括：被调用的网管代理的IP地址、被调用的网管代理的端口号、被调用的网管代理的实例名。
其中，所述SNMP使用的IP地址为自动获取的部署有网管代理的服务器的第一个非回环的IP地址。
可见，在本发明实施例中，在网管服务器和网元之间设置远程方法调用服务器RMI SERVER和两个以上网管代理，网管服务器将携带RMI标识的网元接入请求发送给RMI SERVER，RMI SERVER根据RMI标识选择某一网管代理，通过网管代理将其网元接入请求发送给对应的网元，当网管服务器有大量网元接入请求时，可以将网元接入请求分散到多个网管代理中，从而缓解每个网管代理的压力，该方法有效避免了在网管服务器有大量网元接入请求时产生的消息积压、丢失，甚至服务器宕机的问题。
在本发明实施例中，在单服务器上部署两个以上的网管代理不但提高了消息的处理效率，还提高了系统内存的利用率。
在本发明实施例中，当两个以上的网管代理部署在多网卡的单服务器上时，在RMI标识中增加绑定在实例名后面的被调用的网管代理的IP地址，来区分部署在同一服务器上的多个网管代理。
在本发明实施例中，当两个以上的网管代理部署在多网卡的单服务器上时，通过令网管代理中的简单网络管理协议SNMP使用被调用的网管代理IP地址，避免了部署在同一服务器上的多个网管代理在使用SNMP服务时，所产生的SNMP服务IP地址冲突问题。
在本发明实施例中，两个以上的网管代理可以部署在单个服务器上，也可以部署在两个以上服务器上，从而增加了部署的灵活性。
工业实用性
1、在本发明中，在网管服务器和网元之间设置远程方法调用服务器RMI SERVER和两个以上网管代理，网管服务器将携带RMI标识的网元接入请求发送给RMI SERVER，RMI SERVER根据RMI标识选择某一网管代理，通过网管代理将其网元接入请求发送给对应的网元，当网管服务器有大量网元接入请求时，可以将网元接入请求分散到多个网管代理中，从而缓解每个网管代理的压力，该方法有效避免了在网管服务器有大量网元接入请求时产生的消息积压、丢失，甚至服务器宕机的问题。
2、在本发明中，在单服务器上部署两个以上的网管代理不但提高了消息的处理效率，还提高了系统内存的利用率。
3、在本发明中，当两个以上的网管代理部署在多网卡的单服务器上时，在RMI标识中增加绑定在实例名后面的被调用的网管代理的IP地址，来区分部署在同一服务器上的多个网管代理。
4、在本发明中，当两个以上的网管代理部署在多网卡的单服务器上时，通过令网管代理中的简单网络管理协议SNMP使用被调用的网管代理IP地址，避免了部署在同一服务器上的多个网管代理在使用SNMP服务时，所产生的SNMP服务IP地址冲突问题。
5、本发明中两个以上的网管代理可以部署在单个服务器上，也可以部署在两个以上服务器上，从而增加了部署的灵活性。
以上实施例仅用于说明本发明的技术方案，而非对其限制；尽管参照前述实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的精神和范围。

Claims (14)

  1. 一种多实例并行的网元接入方法，其特征在于，在网管服务器和网元之间设置远程方法调用服务器RMI SERVER和两个以上网管代理，该方法包括：
    网管服务器向RMI SERVER发送网元接入请求消息，该网元接入请求消息中带有接入网元的识别标识和远程方法调用RMI标识；
    RMI SERVER根据所述网元接入请求消息中带有的RMI标识调用某一网管代理；
    所述被调用的网管代理利用简单网络管理协议SNMP将所述网元接入请求消息进行协议转换，发送给对应的网元。
  2. 根据权利要求1所述的方法，其特征在于，所述RMI SERVER为操作维护中心OMC服务器。
  3. 根据权利要求1或2所述的方法，其特征在于，所述两个以上网管代理部署在多网卡的单服务器上，所述单服务器启动多个IP地址，为每个网管代理分配一个IP地址；
    或，
    所述两个以上网管代理中的任一网管代理分别部署在一个服务器上，每个网管代理的IP地址为其所在服务器的IP地址。
  4. 根据权利要求3所述的方法，其特征在于，所述单服务器启动多个IP地址中包括一个主IP地址和其余多个虚拟IP地址。
  5. 根据权利要求4所述的方法，其特征在于，当所述两个以上网管代理部署在多网卡的单服务器上时，所述RMI标识包括：被调用的网管代理的IP地址、被调用的网管代理的端口号、被调用的网管代理的实例名、绑定在所述实例名后的被调用的网管代理的IP地址；
    当所述两个以上网管代理中的任一网管代理分别部署在一个服务器上时，所述RMI标识包括：被调用的网管代理的IP地址、被调用的网管代理的端口号、被调用的网管代理的实例名。
  6. 根据权利要求5所述的方法，其特征在于，当所述两个以上网管代理部署在多网卡的单服务器上时，所述SNMP使用的IP地址为被调用的网管代理的IP地址；
    当所述两个以上网管代理中的任一网管代理分别部署在一个服务器上时，所述SNMP使用的IP地址为自动获取的部署有网管代理的服务器的第一个非回环 的IP地址。
  7. 一种多实例并行的网元接入系统，其特征在于，该系统包括网管服务器、远程方法调用服务器RMI SERVER、两个以上网管代理和网元，其中，
    网管服务器，用于向所述RMI SERVER发送网元接入请求消息，该网元接入请求消息中带有接入网元的识别标识和远程方法调用RMI标识；
    RMI SERVER，用于根据接收到所述网元接入请求消息中带有的RMI标识调用某一网管代理；
    网管代理，用于利用简单网络管理协议SNMP将所述网元接入请求消息进行协议转换，发送给对应的网元。
  8. 根据权利要求7所述的系统，其特征在于，所述RMI SERVER为操作维护中心OMC服务器。
  9. 根据权利要求7或8所述的系统，其特征在于，所述两个以上网管代理部署在多网卡的单服务器上，所述单服务器启动多个IP地址，为每个网管代理分配一个IP地址；
    或，
    所述两个以上网管代理中的任一网管代理分别部署在一个服务器上，每个网管代理的IP地址为其所在服务器的IP地址。
  10. 根据权利要求9所述的系统，其特征在于，所述单服务器启动的多个IP地址中包括一个主IP地址和其余多个虚拟IP地址。
  11. 根据权利要求10所述的系统，其特征在于，当所述两个以上网管代理部署在多网卡的单服务器上时，所述RMI标识包括：被调用的网管代理的IP地址、被调用的网管代理的端口号、被调用的网管代理的实例名、绑定在所述实例名后的被调用的网管代理的IP地址；
    当所述两个以上网管代理中的任一网管代理分别部署在一个服务器上时，所述RMI标识包括：被调用的网管代理的IP地址、被调用的网管代理的端口号、被调用的网管代理的实例名。
  12. 根据权利要求11所述的系统，其特征在于，当所述两个以上网管代理部署在多网卡的单服务器上时，所述SNMP使用的IP地址为被调用的网管代理的IP地址；
    当所述两个以上网管代理中的任一网管代理分别部署在一个服务器上时，所述SNMP使用的IP地址为自动获取的部署有网管代理的服务器的第一个非回环的IP地址。
  13. 一种实现多实例并行的网元接入方法的计算机程序，其特征在于，实现 权力要求1-6任意一项所述的多实例并行的网元接入方法。
  14. 一种计算机存储介质，其特征在于，所述计算机存储介质用于存储权利要求13所述的计算机程序。
PCT/CN2015/074530 2014-03-31 2015-03-18 一种多实例并行的网元接入方法和系统 WO2015149625A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410126572.4A CN103916274B (zh) 2014-03-31 2014-03-31 一种多实例并行的网元接入方法和系统
CN201410126572.4 2014-03-31

Publications (1)

Publication Number Publication Date
WO2015149625A1 true WO2015149625A1 (zh) 2015-10-08

Family

ID=51041692

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/074530 WO2015149625A1 (zh) 2014-03-31 2015-03-18 一种多实例并行的网元接入方法和系统

Country Status (2)

Country Link
CN (1) CN103916274B (zh)
WO (1) WO2015149625A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103916274B (zh) * 2014-03-31 2017-08-25 大唐移动通信设备有限公司 一种多实例并行的网元接入方法和系统
CN105024847B (zh) * 2015-05-28 2018-08-07 大唐移动通信设备有限公司 单服务器多网元适配器网管系统及配置、启动、运行方法
CN106533716B (zh) * 2015-09-09 2019-09-17 大唐移动通信设备有限公司 一种北向接口的管理方法和系统
CN106790325B (zh) * 2015-11-20 2020-07-10 北京神州泰岳软件股份有限公司 一种访问网络设备的方法和系统
CN107872336B (zh) * 2016-09-26 2021-05-14 中国电信股份有限公司 挂载点标识方法和系统以及标识管理设备
CN109391506B (zh) * 2017-08-14 2020-08-28 大唐移动通信设备有限公司 一种数据包方法及装置
CN111355795B (zh) * 2020-02-26 2023-03-21 北京思特奇信息技术股份有限公司 远程采集Linux主机数据的方法、系统、介质及设备

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1549499A (zh) * 2003-05-07 2004-11-24 中兴通讯股份有限公司 一种基于snmp协议的代理网管的实现方法
CN101299675A (zh) * 2007-04-30 2008-11-05 智邦科技股份有限公司 网络管理系统及其管理方法
CN101312404A (zh) * 2007-05-24 2008-11-26 杭州华三通信技术有限公司 一种snmp消息的处理方法和处理设备
CN101345657A (zh) * 2008-08-28 2009-01-14 中兴通讯股份有限公司 基于简单网络管理协议集群管理多个网元的方法及系统
CN103051478A (zh) * 2012-12-24 2013-04-17 中兴通讯股份有限公司 一种大容量电信网管系统及其设置和应用方法
CN103916274A (zh) * 2014-03-31 2014-07-09 大唐移动通信设备有限公司 一种多实例并行的网元接入方法和系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101494561A (zh) * 2009-03-04 2009-07-29 中兴通讯股份有限公司 一种基于简单网络管理协议的网络管理方法和系统
EP2438709B1 (en) * 2009-06-02 2013-05-08 Nokia Siemens Networks Oy Network element integration

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1549499A (zh) * 2003-05-07 2004-11-24 中兴通讯股份有限公司 一种基于snmp协议的代理网管的实现方法
CN101299675A (zh) * 2007-04-30 2008-11-05 智邦科技股份有限公司 网络管理系统及其管理方法
CN101312404A (zh) * 2007-05-24 2008-11-26 杭州华三通信技术有限公司 一种snmp消息的处理方法和处理设备
CN101345657A (zh) * 2008-08-28 2009-01-14 中兴通讯股份有限公司 基于简单网络管理协议集群管理多个网元的方法及系统
CN103051478A (zh) * 2012-12-24 2013-04-17 中兴通讯股份有限公司 一种大容量电信网管系统及其设置和应用方法
CN103916274A (zh) * 2014-03-31 2014-07-09 大唐移动通信设备有限公司 一种多实例并行的网元接入方法和系统

Also Published As

Publication number Publication date
CN103916274B (zh) 2017-08-25
CN103916274A (zh) 2014-07-09

Similar Documents

Publication Publication Date Title
WO2015149625A1 (zh) 一种多实例并行的网元接入方法和系统
US10110671B2 (en) Method, system, and device for managing server hardware resources in a cloud scheduling environment
US9007945B2 (en) Automated network service discovery and communication
WO2017181876A1 (zh) 一种设备状态及资源信息监测方法、相关设备及系统
CN105024855A (zh) 分布式集群管理系统和方法
US9749354B1 (en) Establishing and transferring connections
CN102497409B (zh) 一种云计算系统资源管理的方法
WO2019090997A1 (zh) 一种数据获取方法、装置、计算机设备及存储介质
TW201519621A (zh) 用於在虛擬區域網路中管理雲端裝置之管理伺服器及其管理方法
JP2012524919A5 (zh)
WO2012163007A1 (zh) 解决网际协议地址分配冲突的方法及相关设备和系统
EP3332521B1 (en) Method and apparatus for scaling in a virtualized network
US9864856B2 (en) Efficient hardware trust verification in data communication systems that comprise network interface cards, central processing units, and data memory buffers
CN104038570B (zh) 一种数据处理方法及装置
WO2018039973A1 (zh) 网络功能处理方法及相关设备
CN112929225B (zh) 会话异常处理方法、装置、计算机设备和存储介质
US20160183229A1 (en) Ip phone network system, server apparatus, ip exchange and resource capacity expansion method
CN111835685A (zh) 一种监控Nginx网络隔离空间的运行状态的方法和服务器
JP2014528611A5 (zh)
US9225670B2 (en) System and method for storage and retrieval of neighboring switch tokens
US10791088B1 (en) Methods for disaggregating subscribers via DHCP address translation and devices thereof
US9798633B2 (en) Access point controller failover system
CN102769540B (zh) 一种全局标签管理方法和设备
US10277700B2 (en) Control plane redundancy system
US8429261B2 (en) Methods and systems for managing a device in a web based enterprise management environment

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: 15773997

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase
122 Ep: pct application non-entry in european phase

Ref document number: 15773997

Country of ref document: EP

Kind code of ref document: A1