WO2011007399A1 - Dispositif d'agent snmp et procédé de commande d'agent snmp - Google Patents

Dispositif d'agent snmp et procédé de commande d'agent snmp Download PDF

Info

Publication number
WO2011007399A1
WO2011007399A1 PCT/JP2009/003390 JP2009003390W WO2011007399A1 WO 2011007399 A1 WO2011007399 A1 WO 2011007399A1 JP 2009003390 W JP2009003390 W JP 2009003390W WO 2011007399 A1 WO2011007399 A1 WO 2011007399A1
Authority
WO
WIPO (PCT)
Prior art keywords
trap
unit
message
transmission
issuing
Prior art date
Application number
PCT/JP2009/003390
Other languages
English (en)
Japanese (ja)
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 富士通テレコムネットワークス株式会社
Priority to PCT/JP2009/003390 priority Critical patent/WO2011007399A1/fr
Priority to JP2011522631A priority patent/JP5186043B2/ja
Publication of WO2011007399A1 publication Critical patent/WO2011007399A1/fr

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/06—Management of faults, events, alarms or notifications
    • H04L41/0604—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time
    • H04L41/0627—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time by acting on the notification or alarm source
    • 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]
    • 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/04—Network management architectures or arrangements
    • H04L41/046—Network management architectures or arrangements comprising network management agents or mobile agents therefor

Definitions

  • the present invention relates to a data processing technique, and more particularly, to an agent device connected to a manager device that manages an operation state of a device by SNMP (Simple Network Management Protocol) and a control method thereof.
  • SNMP Simple Network Management Protocol
  • the agent device may notify the occurrence of an abnormality in the monitoring target item by spontaneously transmitting a TRAP message to the manager device.
  • occurrences of abnormalities in a plurality of items to be monitored may be detected in a short time, and transmission processing of a plurality of TRAP messages to the manager device may be congested. In this case, some TRAP messages may be discarded without being notified to the manager device.
  • the present invention has been made in view of these problems, and its main object is to provide a technique for notifying the manager device of a plurality of TRAP messages generated by an SNMP agent device without omission. is there.
  • an SNMP agent device is an agent device connected to a manager device that manages an operation state of a device by SNMP, and when a notification condition of a TRAP message is satisfied
  • a TRAP issuing unit that generates a TRAP message to be notified to the manager device, and a TRAP transmitting unit that transmits the TRAP message generated in the TRAP issuing unit to the manager device.
  • the TRAP transmission unit stops at least one of the plurality of TRAP messages when the processing of the plurality of TRAP messages is congested, and the TRAP issuing unit has a condition that the TRAP transmission unit is in an idle state. To output a TRAP message to the TRAP transmission unit.
  • the TRAP message notification condition may be determined based on the knowledge of the system operator and the requirements for the system. For example, the monitoring target items such as the operating state and operating environment of the agent device may be in a predetermined mode. “The processing of a plurality of TRAP messages is congested” may mean that transmission requests for a plurality of TRAP messages are accepted substantially simultaneously by the TRAP transmission unit. For example, a transmission request for a second TRAP message different from the first TRAP message may be received from the TRAP issuing unit during the transmission process of the first TRAP message in the TRAP transmission unit.
  • the TRAP transmission unit is in an idle state indicates a state in which the operation state of the TRAP transmission unit does not cause congestion in transmission processing even when a new TRAP message is received. For example, another TRAP message transmission process may be in an unexecuted state.
  • the TRAP transmitting unit accepts the TRAP transmission request from the TRAP issuing unit when the TRAP transmitting unit is in an idle state. Therefore, it is possible to avoid congestion of transmission processing of a plurality of TRAP messages in the TRAP transmission unit. Thus, even when a plurality of TRAP message notification conditions are satisfied substantially simultaneously, each of the plurality of TRAP messages is transmitted to the manager device without being discarded.
  • the TRAP transmitting unit notifies the TRAP issuing unit of the operating state triggered by the change in its operating state.
  • the TRAP issuing unit refers to the notification content from the TRAP transmitting unit, and the TRAP transmitting unit is idle. You may detect whether it is a state. “The operation state of the device itself has changed” may be that the operation state of the TRAP transmission unit has shifted from the idle state to a state in which a TRAP message transmission process is being executed. It may be a transition from the state to the idle state. According to this aspect, the TRAP issuing unit does not need to inquire the TRAP transmission unit about the operation state of the TRAP transmission unit, and can immediately detect the operation state when the TRAP message should be transmitted.
  • the TRAP issuing unit may include a buffer that temporarily holds the TRAP message.
  • the TRAP issuing unit may hold a TRAP message to be output to the TRAP transmitting unit in a buffer when the TRAP transmitting unit is processing another TRAP message.
  • the “buffer” may be a storage area for storing TRAP message data, or may be implemented as a memory such as a RAM. According to this aspect, while the TRAP message should not be output to the TRAP transmitting unit, the TRAP issuing unit can hold the TRAP message in its own buffer.
  • the TRAP issuing unit may output the TRAP message held in the buffer to the TRAP transmitting unit when the operation state of the TRAP transmitting unit shifts from the processing of the TRAP message to the idle state.
  • the TRAP issuing unit outputs the TRAP message to the TRAP transmitting unit after the processing for transmitting another TRAP message in the TRAP transmitting unit is completed. Thereby, it is possible to avoid congestion of transmission processing of a plurality of TRAP messages in the TRAP transmission unit.
  • This SNMP agent device may include a plurality of TRAP issuing units.
  • Each of the plurality of TRAP issuing units may include a buffer for holding a TRAP message to be output to the TRAP transmitting unit when the TRAP transmitting unit is processing the TRAP message.
  • Each of the “plurality of TRAP issuing units” may generate a TRAP message by detecting a change in state of different monitoring target items.
  • each TRAP issuing unit includes a buffer, the processing load on the TRAP transmitting unit can be reduced as compared with the case where the TRAP transmitting unit includes a buffer. Further, since the plurality of TRAP messages are distributed and stored in the buffers of the individual TRAP issuing units, it is easy to prevent the TRAP messages from being stored exceeding the buffer capacity.
  • Another aspect of the present invention is an SNMP agent control method.
  • This method is a method of controlling an agent device connected to a manager device that manages the operation state of a device by SNMP, and when a TRAP message notification condition is satisfied, a TRAP issuing unit notifies the manager device.
  • causes the agent device to execute a step of outputting a TRAP message to the TRAP transmission unit and a step of the TRAP transmission unit transmitting the TRAP message to the manager device.
  • the present invention it becomes easy to prevent the occurrence of notification omission to the manager device for a plurality of TRAP messages generated by the SNMP agent device.
  • FIG. 6 It is a figure which shows the structure of the SNMP management system which is embodiment of this invention. It is a figure which shows the conventional process sequence about transmission of a TRAP message. It is a figure which shows the conventional process sequence about transmission of a TRAP message. It is a block diagram which shows the function structure of the agent apparatus of FIG. 6 is a flowchart showing the operation of the agent device of FIG. 6 is a flowchart showing the operation of the agent device of FIG. 6 is a flowchart showing the operation of the agent device of FIG. It is a figure which shows the process sequence of this Embodiment about transmission of a TRAP message.
  • FIG. 1 shows a configuration of an SNMP management system 10 according to an embodiment of the present invention.
  • the SNMP management system 10 includes a first agent device 12a, a second agent device 12b, which are collectively referred to as an agent device 12, and a manager device 14.
  • the agent device 12 and the manager device 14 are connected to each other via a LAN (Local Area Network) 16.
  • LAN Local Area Network
  • the manager device 14 is a computer terminal equipped with SNMP manager software.
  • the manager device 14 acquires data indicating the state of a predetermined monitoring target item from the agent device 12. Then, by appropriately notifying the person in charge of the SNMP management system 10 of the status of the monitoring target item, the monitoring and operation of the SNMP management system 10 is supported.
  • the agent device 12 is an SNMP agent device in which SNMP agent software is installed or hardware such as an electronic circuit that provides the same function as the software is installed.
  • it may be a communication device such as a layer 2 switch or a router, or may be a general PC terminal.
  • the agent device 12 voluntarily notifies the manager device 14 of a TRAP message for notifying the state of a predetermined monitoring target item. For example, when the notification condition of the TRAP message is satisfied, typically, when the state change is detected for a predetermined monitoring target item, the agent device 12 manages the data of the TRAP message including the content of the state change. Transmit to device 14.
  • the agent device 12 When transmitting the TRAP message, the agent device 12 generates a TRAP message in the TRAP issuing unit, and transmits the TRAP message to the manager device 14 in the TRAP transmitting unit.
  • the agent apparatus so far, when the transmission processing of each of the plurality of TRAP messages is congested in the TRAP transmission unit, at least one TRAP message is discarded. As a result, a notification failure of the TRAP message to the manager device may occur. Specific examples are shown below.
  • FIG. 2 shows a conventional processing sequence for transmitting a TRAP message.
  • the first TRAP issuing unit When the occurrence of a predetermined event related to a certain monitoring target item is detected, the first TRAP issuing unit generates a TRAP message # 1. Then, the transmission request for the TRAP message # 1 is output to the TRAP transmission unit (S10).
  • the TRAP transmission unit starts transmission processing of the TRAP message # 1 and sends an ARP (Address Resolution Protocol) request for resolving the address of the manager device to the LAN side (S12).
  • ARP Address Resolution Protocol
  • the second TRAP issuing unit detects the occurrence of a predetermined event related to another monitoring target item, and outputs a request for transmitting the TRAP message # 2 to the TRAP transmitting unit (S14).
  • the TRAP transmitting unit discards the TRAP message # 1 (S16).
  • the TRAP transmission unit receives the ARP reply and transmits the TRAP message # 2 to the LAN by sending the TRAP message # 2 to the LAN side (S18).
  • FIG. 3 shows a conventional processing sequence for transmitting a TRAP message.
  • the first TRAP issuing unit outputs a transmission request for TRAP message # 1 to the TRAP transmitting unit (S20), and the TRAP transmitting unit transmits an ARP request to the LAN side (S22).
  • the first TRAP issuing unit detects the occurrence of another event, and outputs a transmission request for the TRAP message # 2 to the TRAP transmitting unit (S24).
  • the TRAP transmitting unit discards the TRAP message # 1 (S26). Then, the TRAP transmission unit accepts the ARP reply and sends TRAP message # 2 to the LAN side (S28).
  • the first TRAP issuing unit and the second TRAP issuing unit store the TRAP message to be notified to the manager device in this buffer. Then, the TRAP transmission unit sequentially acquires TRAP messages from this buffer and transmits them to the manager device.
  • the TRAP transmission unit since the TRAP transmission unit always acquires the TRAP message from the buffer, the access time to the buffer occurs as an overhead.
  • the TRAP transmission unit performs a TRAP message transmission process in a centralized manner, so the processing load is relatively high.
  • a management process such as a buffer free state is weighted and executed, the processing load is further increased. End up.
  • the mounting scale of the TRAP transmission unit for example, the circuit scale may be increased.
  • the TRAP transmission unit notifies the TRAP issuing unit of its operation state at any time.
  • the TRAP issuing unit outputs a TRAP message transmission request to the TRAP transmitting unit on condition that the TRAP transmitting unit is in an idle state.
  • the agent device 12 by providing a buffer in each TRAP issuing unit, both temporary holding of a TRAP message transmission request and prevention of an increase in processing load in the TRAP transmitting unit are realized.
  • FIG. 4 is a block diagram showing a functional configuration of the agent device 12 of FIG.
  • Each block shown in the block diagram of the present specification can be realized in terms of hardware by an element such as a CPU of a computer or a mechanical device, and in terms of software, it can be realized by a computer program or the like.
  • the functional block realized by those cooperation is drawn. Therefore, those skilled in the art will understand that these functional blocks can be realized in various forms by a combination of hardware and software.
  • the agent device 12 includes a first TRAP issuing unit 30a, a second TRAP issuing unit 30b, and a TRAP transmitting unit 20, which are collectively referred to as a TRAP issuing unit 30.
  • the TRAP transmission unit 20 executes a TRAP message transmission process for the manager device 14.
  • the TRAP transmission unit 20 includes a transmission execution unit 22 and a state notification unit 24.
  • the transmission executing unit 22 receives the transmission request data of the TRAP message from the TRAP issuing unit 30. Then, the TRAP message data included in the transmission request data is transmitted to the manager device 14 via the LAN 16.
  • the status notification unit 24 overwrites and updates data stored in a status register 32 of the TRAP issuing unit 30 to be described later with status data indicating the operation status of the transmission execution unit 22.
  • This state data indicates either an “idle state” indicating that the TRAP message is not being transmitted or a “transmission state” indicating that the TRAP message is being transmitted.
  • the state notification unit 24 changes the operation state of the transmission execution unit 22 when detecting the transition from the idle state to the transmission processing state or the transition from the transmission processing state to the idle state. The subsequent operation state is recorded in the state register 32 as needed.
  • the TRAP issuing unit 30 executes a TRAP message generation process to be notified to the manager device 14.
  • the first TRAP issuing unit 30a generates a TRAP message related to the first monitoring target item (hereinafter also referred to as “TRAP message # 1”).
  • the second TRAP issuing unit 30b generates a TRAP message related to the second monitoring target item (hereinafter also referred to as “TRAP message # 2”).
  • the TRAP issuing unit 30 includes a status register 32, a TRAP buffer 34, a TRAP trigger detection unit 36, a TRAP generation unit 38, and a transmission request unit 40.
  • the status register 32 is a register that stores a flag indicating the operation state of the TRAP transmission unit 20, and stores at least one bit. For example, the flag “0” may indicate that the TRAP transmission unit 20 is in an idle state, and the flag “1” may indicate that the TRAP transmission unit 20 is in a transmission processing state.
  • the TRAP buffer 34 is a storage area for temporarily storing TRAP message data.
  • the TRAP trigger detection unit 36 detects the occurrence of a predetermined event as a TRAP message notification condition, specifically, a predetermined state change in a predetermined monitoring target item as a TRAP message notification trigger to the manager device 14. Then, a TRAP message generation request including data indicating the state change is transmitted to the TRAP generation unit 38. For example, when the connection state with the external device is set as the monitoring target item, the occurrence of the link disconnection with the external device may be detected as a TRAP message notification trigger. Further, when the operation state of the line card is set as a monitoring target item, the occurrence of a failure in the line card may be detected as a TRAP message notification trigger.
  • the TRAP generation unit 38 receives a TRAP message generation request from the TRAP trigger detection unit 36. Then, by setting the contents of the state change of the monitoring target item as data of a TRAP message in a predetermined format, a TRAP message to be notified to the manager device 14 is generated.
  • the transmission request unit 40 refers to the status register 32 and identifies the operation state of the TRAP transmission unit 20.
  • the transmission request unit 40 outputs the transmission request data including the TRAP message to be notified to the manager device 14 to the transmission execution unit 22.
  • the transmission request unit 40 suspends the TRAP message transmission request to the transmission execution unit 22 and records the data of the TRAP message in the TRAP buffer 34.
  • the transmission request unit 40 periodically refers to the TRAP buffer 34 and periodically determines whether there is a TRAP message held in the TRAP buffer 34.
  • the TRAP message is held in the TRAP buffer 34 and the TRAP transmission unit 20 is in the idle state, the TRAP message is acquired from the TRAP buffer 34 and the transmission request data is output to the transmission execution unit 22.
  • FIG. 5 is a flowchart showing the operation of the agent device 12 of FIG.
  • the figure shows a processing flow of the TRAP transmission unit 20.
  • the transmission execution unit 22 receives a TRAP message transmission request from the transmission request unit 40 (S30).
  • the state notification unit 24 sets a flag indicating the transmission processing state of the transmission execution unit 22 in the state register 32 (S32).
  • the transmission execution unit 22 transmits TRAP message data to the manager device 14 (S34).
  • the state notification unit 24 sets a flag indicating the idle state of the transmission execution unit 22 in the state register 32 (S36).
  • FIG. 6 is a flowchart showing the operation of the agent device 12 of FIG. The figure shows a processing flow of the TRAP issuing unit 30.
  • the TRAP trigger detection unit 36 detects the occurrence of a predetermined event that triggers a TRAP message notification (S40).
  • the TRAP generator 38 generates TRAP message data indicating the content of the detected event (S42).
  • the transmission request unit 40 refers to the status register 32 and identifies the operation state of the transmission execution unit 22. When the transmission execution unit 22 is in the idle state (Y in S44), the transmission request unit 40 immediately sends a transmission request for the TRAP message to the transmission execution unit 22 (S46). When the transmission execution unit 22 is in a transmission processing state (N in S44), the transmission request unit 40 records the TRAP message in the TRAP buffer 34 instead of sending out a TRAP message transmission request (S48).
  • FIG. 7 is a flowchart showing the operation of the agent device 12 of FIG. This figure shows a processing flow that is periodically executed in the TRAP issuing unit 30.
  • the transmission request unit 40 periodically refers to the TRAP buffer 34 and determines whether or not a TRAP message is held.
  • the transmission request unit 40 transmits the TRAP message held in the TRAP buffer 34.
  • the request is sent to the transmission execution unit 22. If the TRAP message is not held in the TRAP buffer 34 (N in S50) or the transmission execution unit 22 is in the transmission processing state (N in S52), the processing flow of FIG.
  • FIG. 8 shows a processing sequence of the present embodiment for the transmission of the TRAP message.
  • the first TRAP issuing unit 30a detects occurrence of a predetermined event related to a certain monitoring target item, the first TRAP issuing unit 30a generates a TRAP message # 1. Then, the transmission request for the TRAP message # 1 is output to the TRAP transmission unit 20 (S60).
  • the TRAP transmission unit 20 When starting the transmission processing of the TRAP message # 1, the TRAP transmission unit 20 notifies the first TRAP issuing unit 30a and the second TRAP issuing unit 30b that the transmission processing is being performed (S62).
  • flag data indicating a transmission processing in progress state is recorded in the status register 32 of the first TRAP issuing unit 30a and the second TRAP issuing unit 30b.
  • the TRAP transmission unit 20 transmits an ARP request to the LAN side in the transmission process of the TRAP message # 1 (S64).
  • the second TRAP issuing unit 30b detects the occurrence of a predetermined event related to another monitoring target item, and generates a TRAP message # 2. Then, it is determined that the TRAP transmission unit 20 is in a transmission processing state, and the TRAP message # 2 is recorded in the TRAP buffer 34 (S66). The TRAP transmission unit 20 receives the ARP reply and transmits the TRAP message # 1 to the manager device 14 (S68). When the transmission process of the TRAP message # 1 is completed, the TRAP transmission unit 20 notifies the first TRAP issuing unit 30a and the second TRAP issuing unit 30b that the TRAP message # 1 is in an idle state (S70).
  • the second TRAP issuing unit 30b detects that the TRAP message # 2 is held in the TRAP buffer 34 and that the TRAP transmitting unit 20 is in an idle state, and transmits the TRAP message # 2.
  • the request is output to the TRAP transmitter 20 (S72).
  • the TRAP transmission unit 20 notifies the first TRAP issuing unit 30a and the second TRAP issuing unit 30b that the transmission processing is in progress (S74). Thereafter, the TRAP message # 2 transmission process is executed.
  • the operating state of the TRAP transmitting unit 20 is notified to the TRAP issuing unit 30 as needed.
  • the TRAP issuing unit 30 requests the TRAP transmitting unit 20 to transmit a TRAP message on condition that the TRAP transmitting unit 20 is in an idle state. Thereby, it is possible to avoid congestion of transmission processing of a plurality of TRAP messages in the TRAP transmission unit 20. Also, holding the TRAP buffer 34 on the TRAP issuing unit 30 side eliminates the need for buffer management in the TRAP transmitting unit 20. Further, when the TRAP transmission unit 20 is in an idle state, access to the TRAP buffer 34 is not necessary. That is, the number of accesses to the buffer is reduced, and the processing performance of the agent device 12 can be improved.
  • time slots may be assigned to each of the plurality of TRAP issuing units 30 as periods during which a TRAP message transmission request can be output to the TRAP transmitting unit 20.
  • This time slot may be obtained by dividing a predetermined unit time into a plurality of sections.
  • the transmission request unit 40 of each of the plurality of TRAP issuing units 30 identifies the operation state of the transmission execution unit 22 in the time slot allocated to itself, and requests the transmission execution unit 22 to transmit a TRAP message. Execute.
  • a non-requestable period in which no TRAP issuing unit 30 is allowed to transmit a TRAP message may be set.
  • This request impossible period is equal to or longer than a period from when a TRAP message transmission request is output from the TRAP issuing unit 30 to the TRAP transmitting unit 20 until a transmission processing status is notified from the TRAP transmitting unit 20 to the TRAP issuing unit 30. It is desirable. According to this modification, even when a TRAP message is simultaneously generated in each of the plurality of TRAP issuing units 30, it is possible to more reliably avoid congestion of the TRAP message transmission processing in the TRAP transmitting unit 20.
  • the present invention can be used in a system that manages the operating state of a device by SNMP.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)

Abstract

Un dispositif d'agent (12) comprend : une unité de sortie TRAP (30) qui génère un message TRAP ; et une unité d'émission TRAP (20) qui émet le message TRAP vers un dispositif de gestionnaire (14). Lors d'un encombrement d'une pluralité de procédés de message TRAP, l'unité d'émission TRAP (20) met fin au procédé de l'un au moins des messages TRAP. Si l'unité d'émission TRAP se trouve dans un état au repos, l'unité de sortie TRAP (30) délivre en sortie le message TRAP à l'unité d'émission TRAP (20).
PCT/JP2009/003390 2009-07-17 2009-07-17 Dispositif d'agent snmp et procédé de commande d'agent snmp WO2011007399A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/JP2009/003390 WO2011007399A1 (fr) 2009-07-17 2009-07-17 Dispositif d'agent snmp et procédé de commande d'agent snmp
JP2011522631A JP5186043B2 (ja) 2009-07-17 2009-07-17 Ｓｎｍｐエージェント装置およびｓｎｍｐエージェント制御方法

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2009/003390 WO2011007399A1 (fr) 2009-07-17 2009-07-17 Dispositif d'agent snmp et procédé de commande d'agent snmp

Publications (1)

Publication Number Publication Date
WO2011007399A1 true WO2011007399A1 (fr) 2011-01-20

Family

ID=43449020

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2009/003390 WO2011007399A1 (fr) 2009-07-17 2009-07-17 Dispositif d'agent snmp et procédé de commande d'agent snmp

Country Status (2)

Country Link
JP (1) JP5186043B2 (fr)
WO (1) WO2011007399A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH11143800A (ja) * 1997-11-05 1999-05-28 Nec Corp コンピュータの通信フロー制御方式，方法および記録媒 体
WO2001025933A1 (fr) * 1999-10-01 2001-04-12 Fujitsu Limited Systeme de modele d'agent et de gestionnaire
JP2004080397A (ja) * 2002-08-19 2004-03-11 Nec Corp Ｌａｎ監視機能を備えたｓｎｍｐエージェント
WO2008149455A1 (fr) * 2007-06-08 2008-12-11 Fujitsu Limited Gestionnaire, agent, système et procédé de commande de transmission

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4123660B2 (ja) * 1999-03-30 2008-07-23 富士電機機器制御株式会社 プログラマブルコントローラ

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH11143800A (ja) * 1997-11-05 1999-05-28 Nec Corp コンピュータの通信フロー制御方式，方法および記録媒 体
WO2001025933A1 (fr) * 1999-10-01 2001-04-12 Fujitsu Limited Systeme de modele d'agent et de gestionnaire
JP2004080397A (ja) * 2002-08-19 2004-03-11 Nec Corp Ｌａｎ監視機能を備えたｓｎｍｐエージェント
WO2008149455A1 (fr) * 2007-06-08 2008-12-11 Fujitsu Limited Gestionnaire, agent, système et procédé de commande de transmission

Also Published As

Publication number Publication date
JPWO2011007399A1 (ja) 2012-12-20
JP5186043B2 (ja) 2013-04-17

Similar Documents

Publication Publication Date Title
CN110365752B (zh) 业务数据的处理方法、装置、电子设备和存储介质
US20100057901A1 (en) Network management system and node device and management apparatus thereof
KR101618989B1 (ko) Ｓｄｎ 환경에서 네트워크 장치에 대한 장애를 처리하는 방법
US8667181B2 (en) Communication device
JP5229007B2 (ja) 監視システム、ネットワーク機器、監視情報提供方法およびプログラム
JP5673057B2 (ja) 輻輳制御プログラム、情報処理装置および輻輳制御方法
CN110519337B (zh) 一种节点状态判断、采集方法及状态决策器、状态采集器
JP5186043B2 (ja) Ｓｎｍｐエージェント装置およびｓｎｍｐエージェント制御方法
CN116647476A (zh) 网络管理方法、装置、计算机设备、存储介质和程序产品
JP5364600B2 (ja) 監視制御システム、被監視制御装置およびサーバ
JP5378847B2 (ja) 監視装置
JP4818338B2 (ja) 監視サーバ、ネットワーク監視方法
KR20210078115A (ko) 전화 교환 시스템의 메시지 전달 장치 및 방법
JP2007272694A (ja) 通信インターフェース装置及び通信方法
JP5082147B2 (ja) マルチノードシステム、ノード間スイッチ及びデータ中継方法
JP2004260562A (ja) パケット送受信方法、及び装置
JP5121780B2 (ja) 通信ネットワークシステム
WO2023238438A1 (fr) Dispositif de surveillance et procédé de surveillance
JP2007122439A (ja) 通信装置および通信方法
JP6903843B2 (ja) ノード
JP6507858B2 (ja) ネットワーク装置、リソース監視方法およびプログラム
WO2014068977A1 (fr) Dispositif, système et procédé de gestion de réseau
JP2018182689A (ja) ネットワーク監視システム、ネットワーク監視方法、警報中継装置および警報中継プログラム
CN114884794A (zh) 一种通信方法及装置
JP2020120239A (ja) 監視装置、通信システム、監視方法および通信方法

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2011522631

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09847298

Country of ref document: EP

Kind code of ref document: A1