Large-scale network remote management method and recording medium recording large-scale network remote management program
Abstract
[Task] Large-scale network remote management method and large-scale network remote that can suppress the increase in traffic due to the increase in managed devices, reduce the load on the manager, and maintain the same level of reliability as before even if the network expands. A recording medium on which a management program is recorded is provided.
Solution.The manager 51 makes a periodic collection request for management information to the first manager 11a of the transfer route, and the first sub-manager transfers the management information of the subordinate agent group 57a to the next sub-manager 11b of the transfer route in response to the request. Sub-manager 11 adds the management information of the subordinate agent group 57 to the management information from the previous sub-manager and transfers it to the next sub-manager, and the last sub-manager 11n is the management transferred from the previous sub-manager. After adding the management information of the subordinate agent to the information, the management information is collectively notified to the manager 51.

Term
Term ended
Projected expiry passed 18 February 2019, 7.6 years ago.
- Priority and filed
- Published
- Projected expiry
- Today
8 claims: 4 independent, 4 dependent
- 1【特許請求の範囲】 【請求項1】 ネットワークの資源単位にその構成情報および状態情報を含む管理情報を管理する複数のエージェント、ネットワーク管理プログラムを用いてエージェントの管理情報を管理および制御するマネージャ、および前記エージェントの各々に対応して設けられ、この対応して設けられている配下のエージェントとマネージャ間の通信を中継する複数のサブマネージャを有するネットワークであって、 複数のサブマネージャ間における転送順序を所定の転送ルートとして予め定めておき、 マネージャは、前記転送ルートの先頭マネージャに対して管理情報の定期収集要求を行い、 該先頭サブマネージャは、前記定期収集要求に応答して、自分自身の配下のエージェントが管理する管理情報を前記転送ルートに従って自分自身の次のサブマネージャに転送し、 転送ルート上の各サブマネージャは、転送ルートにおいて自分自身より前のサブマネージャから転送される管理情報に応答し、該管理情報に自分自身の配下のエージェントが管理する管理情報を付加した後、転送ルート上の次のサブマネージャに転送し、 転送ルート上の最後のサブマネージャは、転送ルートにおいて自分自身より前のサブマネージャから転送されてくる管理情報に応答し、該管理情報に対して自分自身の配下のエージェントが管理する管理情報を付加した後、この付加されたすべての管理情報をまとめてマネージャに通知することを特徴とする大規模ネットワーク遠隔管理方法。
- 2【請求項2】 前記先頭サブマネージャが前記定期収集要求に応答しない場合、転送ルートにおいて先頭サブマネージャの下位のサブマネージャが前記定期収集要求に応答して、自分自身の配下のエージェントが管理する管理情報を前記転送ルートに従って自分自身の次のサブマネージャに転送することを特徴とする請求項1記載の大規模ネットワーク遠隔管理方法。
- 3【請求項3】 各サブマネージャは、転送先サブマネージャが応答しない場合、転送ルートに従って前記転送先サブマネージャの次のサブマネージャに転送先を変更することを特徴とする請求項1記載の大規模ネットワーク遠隔管理方法。
- 4【請求項4】 各サブマネージャは、転送先サブマネージャのすべてが応答しない場合、自分自身が転送ルート上の最後のサブマネージャとして、管理情報をまとめてマネージャに通知することを特徴とする請求項3記載の大規模ネットワーク遠隔管理方法。
- 5【請求項5】 ネットワークの資源単位にその構成情報および状態情報を含む管理情報を管理する複数のエージェント、ネットワーク管理プログラムを用いて各エージェントの管理情報を管理および制御するマネージャ、および前記エージェントの各々に対応して設けられ、この対応して設けられている配下のエージェントとマネージャ間の通信を中継する複数のサブマネージャを有するネットワークであって、 複数のサブマネージャ間における転送順序を所定の転送ルートとして予め定めておき、 マネージャは、前記転送ルートの先頭マネージャに対して管理情報の定期収集要求を行い、 該先頭サブマネージャは、前記定期収集要求に応答して、自分自身の配下のエージェントが管理する管理情報を前記転送ルートに従って自分自身の次のサブマネージャに転送し、 転送ルート上の各サブマネージャは、転送ルートにおいて自分自身より前のサブマネージャから転送される管理情報に応答し、該管理情報に自分自身の配下のエージェントが管理する管理情報を付加した後、転送ルート上の次のサブマネージャに転送し、 転送ルート上の最後のサブマネージャは、転送ルートにおいて自分自身より前のサブマネージャから転送されてくる管理情報に応答し、該管理情報に対して自分自身の配下のエージェントが管理する管理情報を付加した後、この付加されたすべての管理情報をまとめてマネージャに通知することを特徴とする大規模ネットワーク遠隔管理プログラムを記録した記録媒体。
- 6【請求項6】 前記先頭サブマネージャが前記定期収集要求に応答しない場合、転送ルートにおいて先頭サブマネージャの下位のサブマネージャが前記定期収集要求に応答して、自分自身の配下のエージェントが管理する管理情報を前記転送ルートに従って自分自身の次のサブマネージャに転送することを特徴とする請求項5記載の大規模ネットワーク遠隔管理プログラムを記録した記録媒体。
- 7【請求項7】 各サブマネージャは、転送先サブマネージャが応答しない場合、転送ルートに従って前記転送先サブマネージャの次のサブマネージャに転送先を変更することを特徴とする請求項5記載の大規模ネットワーク遠隔管理プログラムを記録した記録媒体。
- 8【請求項8】 各サブマネージャは、転送先サブマネージャのすべてが応答しない場合、自分自身が転送ルート上の最後のサブマネージャとして、管理情報をまとめてマネージャに通知することを特徴とする請求項7記載の大規模ネットワーク遠隔管理プログラムを記録した記録媒体。
Independent claims8
95 paragraphs in 1 section, as filed
Description: TECHNICAL FIELD [Detailed description of the invention]
【0001】
[Technical field to which the invention belongs]
The present invention relates to a large-scale network remote management method in which a manager collects management information managed by a plurality of agents from each agent and manages them collectively, and in particular, a large-scale method capable of reducing management packets between the manager and each agent. Related to network remote management methods and recording media on which large-scale network remote management programs are recorded.
【0002】
[Conventional technology]
FIG. 5 is a diagram showing an example of a network management method using SNMP (Simple Network Management Protocol), which is widely used as a network management protocol for the Internet. The communication network management system by SNMP is composed of an SNMP manager 51 that manages the network and an agent 53 that is a target device to be managed. Agent 53 stores a collection of data elements called management information base (MIB) 55, such as hardware switch settings and variable values stored in memory, as management information. The manager 51 issues a request to the agent 53 and manages it by referring to or rewriting these MIB data.
【0003】
However, as the scale of the network to be managed increases, the number of these management packets increases as the number of devices to be managed increases, and the load on the manager who manages the network also increases, which is a problem.
【0004】
As a method of solving this problem, as shown in FIG. 6, for example, a sub-manager 59 is installed between the manager 51 and the agent group 57 including the agent 53, and the sub-manager 59 manages the management information of the subordinate agent group 57. In summary, by relaying the communication between the manager 51 and the agent group 57, a method of distributing the traffic to the manager 51 and the load of the manager 51 can be considered.
【0005】
[Problems to be Solved by the Invention]
In the conventional method described above, the above problems can be solved by installing the sub-manager 59, but as the network becomes larger, the number of sub-managers 59 increases, and the manager 51 and the sub-managers increase. The number of management packets when exchanging management information between 59 increases, and the load on the manager 51 also increases. In order to further distribute, it is necessary to deepen the hierarchy, but if a failure occurs in the upper sub-manager 59 that relays, the influence on the subordinates will be widespread, so the higher the hierarchy, the higher. The problem remains that reliability is required.
【0006】
The present invention has been made in view of the above, and an object of the present invention is to suppress an increase in traffic due to an increase in the number of managed devices, reduce the load on the manager, and even if the network is expanded, the conventional invention is used. It is an object of the present invention to provide a recording medium in which a large-scale network remote management method and a large-scale network remote management program that can maintain the same degree of reliability are recorded.
【0007】
[Means for solving problems]
In order to achieve the above object, the present invention according to claim 1 manages management information of agents by using a plurality of agents that manage management information including configuration information and status information in each resource unit of the network, and a network management program. A network having a manager to control and a plurality of sub-managers provided corresponding to each of the agents and relaying communication between the agents and managers under the correspondingly provided, and a plurality of subs. The transfer order between managers is predetermined as a predetermined transfer route, the manager makes a periodic collection request for management information to the first manager of the transfer route, and the first sub-manager responds to the periodic collection request. Then, the management information managed by the agent under its own is transferred to its own next sub-manager according to the transfer route, and each sub-manager on the transfer route is transferred from the sub-manager before itself in the transfer route. In response to the management information to be executed, after adding the management information managed by the agent under its own to the management information, the transfer is made to the next submanager on the transfer route, and the last submanager on the transfer route is In response to the management information transferred from the sub-manager before itself in the transfer route, after adding the management information managed by the agent under its own to the management information, all the added management The gist is to summarize the information and notify the manager.
【0008】
In the present invention according to claim 1, the manager makes a periodic collection request for management information to the head manager of the transfer route, and the head sub-manager receives the management information of the subordinate agent after the transfer route in response to the request. Transfer to the sub-manager of, each sub-manager adds the management information of the subordinate agent to the management information from the previous sub-manager, transfers to the next sub-manager, and the last sub-manager transfers from the previous sub-manager After adding the management information of the subordinate agents to the management information that is received, the management information is collectively notified to the manager, so even if the network expands further and the number of sub-managers increases, the management packets to the manager will increase. It is possible to suppress the increase in traffic and the increase in the load on the manager.
【0009】
Further, in the present invention according to claim 2, when the first sub-manager does not respond to the periodic collection request in the invention according to claim 1, a sub-manager lower than the first sub-manager in the transfer route responds to the periodic collection request. In response, the gist is to transfer the management information managed by the agent under one's own to the next sub-manager of one's own according to the transfer route. Specifically, if the first sub-manager does not respond to the periodic collection request, the manager makes a periodic collection request to the next sub-manager of the first sub-manager according to the transfer route, and the sub-manager responds to the periodic collection request. Then, the management information managed by the agent under his / her own is transferred to his / her next sub-manager according to the transfer route.
【0010】
In the present invention according to claim 2, when the first sub-manager does not respond to the periodic collection request, the sub-managers below the first sub-manager respond to the periodic collection request in the forwarding route, so that the first sub-manager responds to the periodic collection request for some reason. Even if the sub-manager cannot respond, the sub-manager can respond and respond appropriately to the periodic collection request from the manager.
【0011】
Further, in the invention of claim 1, if the transfer destination sub-manager does not respond to each sub-manager, the invention according to claim 3 becomes the next sub-manager of the transfer destination sub-manager according to the transfer route. The gist is to change the transfer destination.
【0012】
In the present invention according to claim 3, the sub-manager changes the transfer destination to the next sub-manager when the transfer destination sub-manager does not respond, so that the transfer of management information is performed even if the sub-manager cannot respond for some reason. In addition to being able to perform processing appropriately, it is also possible to identify sub-managers who cannot respond for some reason.
【0013】
The present invention according to claim 4 is managed by each sub-manager as the last sub-manager on the transfer route when all of the transfer destination sub-managers do not respond in the invention according to claim 3. The gist is to summarize the information and notify the manager.
【0014】
In the present invention according to claim 4, when all of the transfer destination sub-managers do not respond, the sub-manager himself / herself acts as the last sub-manager and notifies the manager of the management information collectively. Even if all the sub-managers are abnormal, the management information up to that point can be collectively notified to the manager.
【0015】
The present invention according to claim 5 is a plurality of agents that manage management information including configuration information and status information for each resource unit of the network, and a manager that manages and controls the management information of each agent by using a network management program. , And a network having a plurality of sub-managers corresponding to each of the agents and relaying communication between the correspondingly provided subordinate agents and managers, and transfer between the plurality of sub-managers. The order is predetermined as a predetermined transfer route, the manager makes a periodic collection request for management information to the head manager of the transfer route, and the head sub-manager responds to the periodic collection request and himself / herself. The management information managed by the agent under the transfer route is transferred to the next sub-manager of itself according to the transfer route, and each sub-manager on the transfer route is transferred from the sub-manager before itself in the transfer route. After adding the management information managed by the agent under its own control to the management information, the information is transferred to the next submanager on the transfer route, and the last submanager on the transfer route is himself / herself in the transfer route. In response to the management information transferred from the sub-manager before itself, after adding the management information managed by the agent under its own to the management information, all the added management information is put together. The gist is to record a large-scale network remote management program to be notified to the manager on a recording medium.
【0016】
In the present invention according to claim 5, the manager makes a periodic collection request for management information to the head manager of the transfer route, and the head sub-manager responds to the request and sends the management information of the subordinate agent to the next of the transfer route. Transfer to the sub-manager of, each sub-manager adds the management information of the subordinate agent to the management information from the previous sub-manager, transfers to the next sub-manager, and the last sub-manager transfers from the previous sub-manager Since the large-scale network remote management program that collectively notifies the manager of the management information after adding the management information of the subordinate agent to the management information that is received is recorded on the recording medium, the recording medium is used. It is possible to improve the distribution.
【0017】
Further, in the invention of claim 6, when the head sub-manager does not respond to the periodic collection request, a sub-manager subordinate to the head sub-manager in the transfer route responds to the periodic collection request. The gist is to record on a recording medium a large-scale network remote management program that responds and transfers management information managed by an agent under its own control to its own next sub-manager according to the transfer route.
【0018】
In the present invention according to claim 6, when the head sub-manager does not respond to the periodic collection request, a large-scale network remote management program in which a sub-manager subordinate to the head sub-manager responds to the periodic collection request is recorded in the forwarding route. Since it is recorded on a medium, the recording medium can be used to improve its circulation.
【0019】
According to the invention of claim 7, if the transfer destination sub-manager does not respond to each sub-manager in the invention of claim 5, the transfer destination is transferred to the next sub-manager of the transfer destination sub-manager according to the transfer route. The gist is to record a large-scale network remote management program on a recording medium.
【0020】
In the present invention according to claim 7, if the transfer destination sub-manager does not respond, the sub-manager records a large-scale network remote management program that changes the transfer destination to the next sub-manager on the recording medium. The recording medium can be used to improve its circulation.
【0021】
Further, in the invention of claim 7, in the invention of claim 7, in each sub-manager, if all of the transfer destination sub-managers do not respond, the present invention itself is the last sub-manager on the transfer route. The gist is to record a large-scale network remote management program that collectively notifies the manager of management information on a recording medium.
【0022】
In the present invention according to claim 8, the sub-manager is a large-scale network remote management program that collectively notifies the manager of management information as the last sub-manager when all of the transfer destination sub-managers do not respond. Is recorded on a recording medium, so that the recording medium can be used to improve its circulation.
【0023】
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing a system configuration for implementing a large-scale network remote management method according to an embodiment of the present invention. In the figure, the manager 51 that manages and controls the management information of each agent by using the configuration and network management program of a plurality of agent groups 57a to 57n that manage the management information including the configuration information and the status information for each resource unit of the network. The configuration of is the same as the conventional one, but it is provided corresponding to each of the agent groups 57a to 57n, and relays the communication between each agent group 57 under the correspondingly provided and the manager 51. The plurality of sub-managers 11a to 11n transfer the management information acquired by each sub-manager 11 from the agent group 57 under it as shown by arrows 21 and 23 between the sub-managers by a predetermined transfer route between the sub-managers. It is very different from the conventional one in that it is configured to obtain. In this embodiment, the predetermined transfer route is set as sub-manager 11a sub-manager 11b sub-manager 11c ... sub-manager 11n, and sub-manager 11a is the first sub-manager and the sub-manager. 11n is the last submanager. Further, in FIG. 1, the arrow 21 indicates a transfer request from the upper sub-manager 11 to the next sub-manager 11 in the transfer route, and the arrow 23 indicates the response from the lower sub-manager 11 to the upper sub-manager 11. There is.
【0024】
Each sub-manager 11 configured in this way receives the management information managed by the agent group 57 under its own control, transfers this management information to the next sub-manager 11 in the transfer route, and also transfers the management information to the next sub-manager 11 in the transfer route. The sub-manager 11 that receives the management information transferred from is added the management information managed by the agent group 57 under its own control, and is transferred to the next sub-manager 11. That is, the sub-manager 11b that receives the management information from the sub-manager 11a adds the management information of the agent group 57b under its own control to the received management information, transfers it to the next sub-manager 11c, and transfers it to the sub-manager 11c. Adds the management information of the agent group 57c under its own to the management information received from the sub-manager 11b, and transfers it to the next sub-manager 11d. Similarly, each sub-manager 11 on the transfer route adds the management information of the agent group 57 under its own control to the management information transferred, and transfers the information to the next agent group 57. .. Then, the sub-manager 11n received at the end adds the management information of the agent group 57 under its own control to the received management information, and then collectively notifies the manager 51 of the management information.
【0025】
Next, the operations of the manager 51 and the sub-manager 11 will be described with reference to the flowcharts shown in FIGS. 2 to 4.
【0026】
First, the operation of the manager 51 will be described with reference to the flowchart shown in FIG. In FIG. 2, when the periodic collection cycle of management information is reached (step S11), the manager 51 is on the transfer route based on a predetermined transfer route configured among a plurality of sub-managers 11 to transfer the management information. Make a periodic collection request for management information with the first sub-manager 11a as the representative sub-manager (step S13). Then, it monitors whether or not there is a response from the first sub-manager 11a (step S15), and if there is a response, the manager 51 returns to step S11 and waits until the next periodic collection cycle, but if there is no response, , The next sub-manager 11 on the transfer route is set as the first sub-manager (step S17), and the process returns to step S13 to make a periodic collection request for management information to this sub-manager. If there is a response from the next submanager, it waits until the next periodic collection cycle. If there is no response from the next sub-manager, the operation of making a periodic collection request for management information is repeated with the next sub-manager on the transfer route as the first sub-manager.
【0027】
Next, the operation of the sub-manager 11 when there is a periodic collection request for management information from the manager 51 will be described with reference to the flowchart shown in FIG. When the sub-manager 11 receives the periodic collection request for management information from the manager 51 (step S21), the sub-manager 11 returns a response to the manager 51 (step S23). The sub-manager 11 then checks for the next sub-manager 11 on the forwarding route (step S25). If there is a next sub-manager 11, it checks if the next sub-manager 11 responds (step S27), and when the next sub-manager 11 responds, the sub-manager 11 is a group of agents under its own control. Transfer the management information of 57 to the next sub-manager 11 (step S29), and then return to the first step.
【0028】
Also, in the check for whether or not there is the next sub-manager 11 in step S25, if there is no next sub-manager 11, the manager 51 is notified of the management information of the agent under its own control (step S31). , Go back to the first step.
【0029】
Next, the operation of the sub-manager 11 when management information is received from another sub-manager 11 on the transfer route will be described with reference to the flowchart shown in FIG.
【0030】
When each sub-manager 11 receives the management information transferred from the other sub-managers 11 located higher on the transfer route (step S41), each sub-manager 11 responds to the transfer source which is the other sub-manager 11 located higher. Return (step S43) and then check for the next submanager 11 on the forwarding route (step S45). If there is a sub-manager 11 under this level, check whether the next sub-manager 11 responded (step S47), and if there is no response, return to step S45 and repeat the same operation to respond. Until then, it skips to the next sub-manager 11 on the transfer route, and when there is a response, it adds the management information of the agent group 57 under its own control and transfers it to the next sub-manager 11 (step S49). Then go back to the first step and repeat the same operation.
【0031】
Also, in the check in step S45, if there is no next sub-manager 11, that is, if there is no subsequent sub-manager 11, the management information of the agent group 57 under its own is added. , Notify manager 51 of management information (step S51).
【0032】
As described above, in the present embodiment, the manager 51 makes a periodic collection request for management information to the head manager 11a of the transfer route, and the head sub-manager 11a transfers the management information of the subordinate agent group 57 in response to the request. Transfer to the next sub-manager 11b of the root, each sub-manager 11 adds the management information of the subordinate agent group 57 to the management information from the previous sub-manager 11, transfers to the next sub-manager 11, and finally The sub-manager 11 adds the management information of the subordinate agent group 57 to the management information transferred from the previous sub-manager 11, and then collectively notifies the manager 51 of the management information.
【0033】
If the first submanager 11a does not respond to the periodic collection request from the manager 51, the lower submanager of the first submanager, specifically the lower submanager, which can respond to the forwarding route, is the highest submanager that can respond. In response to the periodic collection request, the management information of the agents 57 under its own control is transferred to the next sub-manager of its own according to the transfer route. Further, each sub-manager 11 changes the transfer destination to the next sub-manager of the transfer-destination sub-manager according to the transfer route when the transfer-destination sub-manager 11 does not respond. Furthermore, if all of the transfer destination sub-managers 11 do not respond, each sub-manager 11 is set to notify the manager 51 of the management information collectively as the last sub-manager 11 on the transfer route. ..
【0034】
[Effect of the invention]
As described above, according to the present invention, the manager makes a periodic collection request for management information to the head manager of the transfer route, and the head sub-manager receives the management information of the subordinate agent next to the transfer route in response to the request. Transfer to the sub-manager of, each sub-manager adds the management information of the subordinate agent to the management information from the previous sub-manager, transfers to the next sub-manager, and the last sub-manager transfers from the previous sub-manager After adding the management information of the subordinate agent to the management information that is received, the management information is collectively notified to the manager, so even if the network expands further and the number of sub-managers increases, the management packets to the manager will increase. It is possible to suppress the increase in traffic and the increase in the load on the manager.
【0035】
Further, according to the present invention, when the first sub-manager does not respond to the periodic collection request, the sub-managers below the first sub-manager respond to the periodic collection request in the transfer route, so that the first sub-manager cannot respond for some reason. However, the sub-managers in the lower level can respond and respond appropriately to the periodic collection request from the manager, and it is also possible to identify the sub-manager who does not respond for some reason. Also, even if the sub-manager is abnormal, only the subordinate agents are affected.
【0036】
Further, according to the present invention, if the transfer destination sub-manager does not respond, the sub-manager changes the transfer destination to the next sub-manager, so that the transfer process of management information is suitable even if the sub-manager cannot respond for some reason. It can be done reliably, and it is also possible to identify sub-managers who cannot respond for some reason. Also, even if the sub-manager is abnormal, only the subordinate agents are affected.
【0037】
According to the present invention, when all of the transfer destination sub-managers do not respond, the sub-manager notifies the manager of the management information collectively as the last sub-manager, so that all the sub-managers after the transfer destination are abnormal. Even in that case, the management information up to that point can be collectively notified to the manager.
[Simple explanation of drawings]
[Figure 1]
It is a figure which shows the system configuration which carries out the large-scale network remote management method which concerns on one Embodiment of this invention.
[Figure 2]
It is a flowchart which shows the operation of a manager.
[Fig. 3]
It is a flowchart which shows the operation of a sub-manager when there is a periodical collection request of management information from a manager.
[Fig. 4]
It is a flowchart which shows the operation of a sub-manager when management information is received from another sub-manager on a transfer route.
[Fig. 5]
It is explanatory drawing which shows an example of the conventional network management method using the SNMP protocol.
[Fig. 6]
It is a figure for demonstrating the conventional network management method which provided the sub-manager between a manager and each agent group.
[Explanation of symbols]
11a ~ 11n sub-manager 51 Manager 57a ~ 57n Agents
7 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US7769969B2 | Cited by | United States of America | Applicant |
| KR100533153B1 | Cited by | Republic of Korea | Search report |
| JPWO2009004701A1 | Cited by | Japan | Search report |
| JP4893828B2 | Cited by | Japan | Search report |
| US8615682B2 | Cited by | United States of America | Applicant |
| JP2005157521A | Cited by | Japan | Search report |
| JP2007258814A | Cited by | Japan | Examiner |
2 priority claims, no other members on record
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 4062299 | Japan | A | |
| JP19990040622 | – | – | – |
Numbers
- Publication
- 2000-242585
- Publication, DOCDB
- 2000242585
- Publication, EPODOC
- JP2000242585
- Application
- 11040622
- Application, DOCDB
- 4062299
- Application, EPODOC
- JP19990040622
Titles2
- Japanese
- 大規模ネットワーク遠隔管理方法および大規模ネットワーク遠隔管理プログラムを記録した記録媒体
- English
- PROBLEM TO BE SOLVED: To record a large-scale network remote management method and a large-scale network remote management program.
Classification
- IPC, 4
- G06F13 00
- H04L12 24
- H04L12 26
- H04L12 28