WO2013047355A1 - 通信装置、通信方法及びプログラム - Google Patents

通信装置、通信方法及びプログラム Download PDF

Info

Publication number
WO2013047355A1
WO2013047355A1 PCT/JP2012/074188 JP2012074188W WO2013047355A1 WO 2013047355 A1 WO2013047355 A1 WO 2013047355A1 JP 2012074188 W JP2012074188 W JP 2012074188W WO 2013047355 A1 WO2013047355 A1 WO 2013047355A1
Authority
WO
WIPO (PCT)
Prior art keywords
snmp
port
communication
management
status information
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/JP2012/074188
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
弘和 小澤
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NEC Corp
Original Assignee
NEC Corp
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 NEC Corp filed Critical NEC Corp
Priority to JP2013536223A priority Critical patent/JP5708818B2/ja
Priority to CN201280046512.0A priority patent/CN103843291B/zh
Priority to IN2319CHN2014 priority patent/IN2014CN02319A/en
Priority to US14/344,609 priority patent/US9641355B2/en
Priority to EP12837254.7A priority patent/EP2763352B1/en
Publication of WO2013047355A1 publication Critical patent/WO2013047355A1/ja
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H04L12/4675—Dynamic sharing of VLAN information amongst network nodes
    • H04L12/4679—Arrangements for the registration or de-registration of VLAN attribute values, e.g. VLAN identifiers, port VLAN membership
    • 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
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/13—Flow control; Congestion control in a LAN segment, e.g. ring or bus
    • 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/0233—Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]

Definitions

  • the present invention relates to a technique for managing communication devices using SNMP (Simple Network Management Protocol).
  • SNMP Simple Network Management Protocol
  • a communication apparatus that is a monitoring target of such an operation state discloses its own setting information and operation information in a management information base (MIB) that is a type of database for managing devices in a communication network.
  • MIB management information base
  • the NMS or the local control terminal acquires each information published by the MIB via the network using SNMP.
  • a standard MIB defined by RFC2674 or an extended MIB provided by each device vendor is usually used.
  • FIG. 5 is a diagram showing a data structure of a VLAN of a standard MIB defined by RFC (Request for Comments) 2674.
  • MIB dot1qVlanCurrentTable
  • the status of each port is managed in 1-bit units for each VLAN.
  • VLAN management data 930 is recorded in the MIB for each VLAN.
  • Each VLAN management data 930 records group data 940 that is 1-byte (OCTET STRING) data.
  • the group data 940 records eight individual data 950.
  • Each individual data 950 represents the state of one port with one bit. For example, when the port is used in the VLAN, the individual data 950 has “1”. On the other hand, when the port is not used in the VLAN, the individual data 950 has “0”. Because of this structure, in the standard MIB, data increases by 1 byte in units of 8 ports.
  • the state of each port is managed for each VLAN. Therefore, when confirming the status of the VLAN, an SNMP Get ⁇ Request is transmitted for each VLAN from the NMS to the communication apparatus, and the VLAN management data 930 is acquired. Therefore, the number of Get Requests transmitted from the NMS to the communication device increases as the number of VLANs registered in the communication device increases.
  • the number of VLANs registered in one communication device (that is, the number of registered VLAN IDs) tends to increase. For example, if it is possible to register a maximum of 4094 VLANs in the standard MIB (dot1qVlanCurrentTable), the number of Get Request processes is 4094 times in order to acquire the status of each port for all VLANs.
  • the other management communication is, for example, a state or failure report based on a protocol other than SNMP, or a control communication associated with a change in the network configuration.
  • the problem is particularly noticeable when the communication band of the management network is narrow. In such a case, the other management communication as described above is compressed, and there is a possibility that the service by the network including the communication device may be delayed.
  • an object of the present invention is to provide a technique for reducing the amount of communication when a communication device in which a plurality of VLANs are registered is managed by SNMP.
  • the present invention includes a communication unit that has a plurality of ports and relays data according to a set state of a plurality of VLANs, and a state that indicates whether each of the plurality of VLANs is used for each of the ports
  • a status information management unit that manages information; receives the request for the status information in units of ports according to SNMP; acquires the status information in units of ports from the status information management unit;
  • An SNMP processing unit for transmitting to the device is provided.
  • a state information management step for managing state information indicating whether or not, receiving a request for the state information in units of ports according to SNMP, acquiring the state information in units of ports, and acquiring the acquired state information in accordance with SNMP
  • a communication method comprising: an SNMP processing step for transmitting to the network.
  • the present invention also provides a communication device having a plurality of ports and having a communication unit that relays data according to a plurality of VLAN setting states, and is used by each of the plurality of VLANs for each port.
  • a state information management step for managing state information indicating whether or not there is received; a request for the state information is received in accordance with SNMP in units of ports; the state information is acquired in units of ports;
  • An SNMP processing step to be transmitted to the apparatus is also provided.
  • the present invention it is possible to reduce a communication amount when managing a communication apparatus in which a plurality of VLANs are registered by SNMP.
  • FIG. 1 is a system configuration diagram illustrating a system configuration of a communication device management system according to an embodiment of the present invention. It is a figure showing the outline of the data structure when a MIB process part memorize
  • FIG. 1 is a system configuration diagram showing a system configuration of a communication device management system 1 according to an embodiment of the present invention.
  • the communication device management system 1 includes a management device 10 and a communication device 20.
  • the management device 10 and the communication device 20 are connected to each other via a management network N so that they can communicate with each other.
  • the management device 10 manages the communication device 20 by communication according to SNMP. That is, the management apparatus 10 functions as an NMS and manages the state of the communication apparatus 20 by communication via the management network N.
  • the plurality of communication devices 20 are connected to each other to form a communication network. Each communication device 20 relays data received from other communication devices 20.
  • FIG. 1 three communication devices 20 connected to the management network N are displayed. The state of each communication device 20 is managed by the management device 10.
  • the number of communication devices 20 connected to the management network N need not be limited to three.
  • a communication device 20 (not shown) that forms a communication network with the communication device 20 shown in the figure may be connected to the management network N.
  • other communication devices 20 that form a communication network different from the communication network formed by the illustrated communication device 20 may be connected to the management network N.
  • the management device 10 is configured using an information processing device such as a mainframe, a workstation, or a personal computer.
  • the management device 10 includes a central processing unit (CPU), a memory, an auxiliary storage device, and the like connected by a bus, and functions as a device including the management unit 101 by executing a management program. All or some of the functions of the management apparatus 10 may be realized using hardware such as an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA).
  • ASIC application specific integrated circuit
  • PLD programmable logic device
  • FPGA field programmable gate array
  • the management program may be recorded on a computer-readable recording medium.
  • the computer-readable recording medium is, for example, a portable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, or a storage device such as a hard disk built in the computer system.
  • the management program may be transmitted / received via a telecommunication line.
  • the management unit 101 has a function as an SNMP manager (NMS), and transmits a PDU (Protocol Data Unit) such as Get Request, Get Next Request, or Set Request to the communication device 20 according to SNMP.
  • PDUs such as Get Request, Get Next Request, and Set Request are referred to as request messages.
  • the request message is a message for requesting information indicating the state of the communication device 20 (hereinafter referred to as “state information”).
  • the management unit 101 also receives PDUs such as Get Response and Trap from the communication device 20 and acquires state information indicating the state of the communication device 20.
  • PDUs such as Get Response and Trap are referred to as notification messages.
  • the notification message is a message including state information of the communication device 20.
  • the communication device 20 is a relay device capable of setting a VLAN, such as a router or an L2 switch.
  • the communication device 20 includes a CPU, a memory, an auxiliary storage device, and the like connected by a bus, and executes a managed program.
  • the communication device 20 functions as a device including the SNMP processing unit 201, the MIB processing unit 202, and the communication unit 203. All or some of the functions of the communication device 20 may be realized using hardware such as an ASIC, PLD, or FPGA.
  • the managed program may be recorded on a computer-readable recording medium.
  • the computer-readable recording medium is, for example, a portable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, or a storage device such as a hard disk built in the computer system.
  • the managed program may be transmitted / received via a telecommunication line.
  • the SNMP processing unit 201 has a function as an SNMP agent, and transmits a notification message such as Get Response to a request message such as Get Request, Get Next Request, or Set Request in accordance with SNMP. Further, the SNMP processing unit 201 may spontaneously transmit a notification message such as Trap to the management apparatus 10 according to the setting by the management apparatus 10 or the like.
  • the SNMP processing unit 201 requests the MIB processing unit 202 for status information to be notified to the management apparatus 10.
  • the SNMP processing unit 201 When receiving the status information from the MIB processing unit 202, the SNMP processing unit 201 generates a notification message including the status information according to the SNMP. Then, the SNMP processing unit 201 transmits the generated notification message to the management apparatus 10.
  • the MIB processing unit 202 functions as an MIB, and acquires and stores status information of the communication device 20 provided with the MIB processing unit 202.
  • the MIB processing unit 202 communicates with the communication unit 203 of the communication device 20 with which the MIB processing unit 202 is provided, and acquires state information of the communication unit 203.
  • the MIB processing unit 202 stores the acquired state information in a data structure according to the definition of the extended MIB.
  • FIG. 2 is a diagram illustrating an outline of a data structure when the MIB processing unit 202 stores state information.
  • the MIB processing unit 202 manages information representing the VLAN status for each port.
  • the MIB processing unit 202 records the port management data 30 for each port.
  • Each port management data 30 is given an object ID.
  • the MIB processing unit 202 is assigned an object ID corresponding to the number of ports provided in the communication device 20.
  • the MIB processing unit 202 publishes status information in units of port management data 30.
  • Each port management data 30 records group data 40.
  • Each group data 40 is 1-byte (OCTET STRING) data, and eight individual data 50 are recorded.
  • Each individual data 50 represents the state of the VLAN with one bit for one VLAN. For example, when the port is used in the VLAN, the individual data 50 has “1”. On the other hand, when the port is not used in the VLAN, the individual data 50 has “0”.
  • Each port management data 30 records one or a plurality of group data 40 according to the number of VLANs set in the communication device 20.
  • the MIB processing unit 202 Due to such a structure, in the MIB processing unit 202 according to the extended MIB, data increases by 1 byte for every eight VLANs.
  • the communication device 20 is provided with eight ports, and 4095 VLANs are set. Therefore, eight port management data 30 are recorded in the MIB processing unit 202.
  • Each port management data 30 records 512 group data 40, and each group data 40 records eight individual data 50.
  • the communication unit 203 communicates with another communication device 20 that is communicably connected to the communication device 20.
  • the communication unit 203 has one or more ports, and transfers data that arrives at each port to other ports in accordance with a preset VLAN definition. For example, the communication unit 203 receives data from another communication device 20, and determines a transfer destination based on the header information of the received data and the definition of the VLAN. Then, the communication unit 203 transfers data from the port corresponding to the determined transfer destination.
  • the management device 10 collects information stored in the MIB processing unit 202 of the communication device 20 by performing processing according to SNMP. As a specific example of this collection processing sequence, two processing flows are shown below.
  • FIG. 3 is a diagram illustrating a first sequence as SNMP processing by the management apparatus 10 and the communication apparatus 20.
  • the management unit 101 transmits a request message for each port included in the communication device 20 and receives a notification message for each port.
  • the first sequence will be described in detail.
  • the management device 10 transmits a Get Request (request message) to the communication device 20 via the management network N (step S101).
  • the SNMP processing unit 201 of the communication device 20 confirms the object ID set in the received Get Request by performing PDU analysis (Step S102).
  • the NMP processing unit 201 generates a MIB data processing request for requesting the port management data 30 of the port indicated by the object ID, and transmits it to the MIB processing unit 202 (step S103).
  • the MIB processing unit 202 searches for and acquires the port management data 30 of the requested port in accordance with the received MIB data processing request (step S104). Then, the MIB processing unit 202 returns an MIB data processing response including the acquired port management data 30 to the SNMP processing unit 201 (step S105).
  • the SNMP processing unit 201 extracts the port management data 30 from the received MIB data processing response. Then, the SNMP processing unit 201 generates a Get Response (notification message) including the extracted port management data 30 by executing a PDU creation process (step S106). Then, the SNMP processing unit 201 transmits the generated Get Response to the management apparatus 10 via the management network N (Step S107).
  • the management unit 101 of the management apparatus 10 When the management unit 101 of the management apparatus 10 receives the Get Response from the SNMP processing unit 201 via the management network N, the management unit 101 extracts the port management data 30 from the Get ⁇ Response and acquires information about one port.
  • a series of processes from the process of step S101 to the process of step S107 is referred to as a first unit process, and the management apparatus 10 repeatedly executes the first unit process for each port for which information is to be acquired. For example, when information is acquired for all eight ports provided in the communication device 20, the management device 10 repeatedly executes the first unit process for all ports. That is, the management apparatus 10 can acquire state information regarding all VLANs of the communication apparatus 20 by repeatedly executing the first unit process eight times.
  • the MIB processing unit 202 performs a MIB data update process in addition to the search of the port management data 30 in the process of step S104.
  • FIG. 4 is a diagram illustrating a second sequence as an SNMP process performed by the management apparatus 10 and the communication apparatus 20.
  • the management unit 101 transmits one request message to a plurality of ports included in the communication device 20 and receives a notification message including a status notification regarding the plurality of ports.
  • the second sequence will be described in detail.
  • the management device 10 generates a Get Response (request message) including a plurality of object IDs, and transmits a Get Request (request message) to the communication device 20 via the management network N (step S201).
  • the SNMP processing unit 201 of the communication device 20 When receiving the Get Request, the SNMP processing unit 201 of the communication device 20 performs a PDU analysis process on the received Get Request, and acquires a plurality of object IDs included in the Get Request (Step S202). The SNMP processing unit 201 selects one of the plurality of object IDs included in the Get Request, and generates an MIB data processing request that requests the port management data 30 of the port indicated by the selected object ID. Then, the SNMP processing unit 201 transmits the generated MIB data processing request to the MIB processing unit 202 (step S203).
  • the MIB processing unit 202 searches and acquires the port management data 30 of the requested port in accordance with the received MIB data processing request (step S204). Then, the MIB processing unit 202 returns a MIB data processing response including the acquired port management data 30 to the SNMP processing unit 201 (step S205).
  • a series of processes from the process of step S203 to the process of step S205 is referred to as a second unit process.
  • the SNMP processing unit 201 repeatedly executes the second unit process for all object IDs acquired by the PDU analysis process. That is, the SNMP processing unit 201 repeatedly executes the second unit process for the number of ports specified by Get Request.
  • the SNMP processing unit 201 when Get Request including the object IDs of all eight ports included in the communication device 20 is received, the SNMP processing unit 201 repeatedly executes the second unit process for all the ports. That is, by repeating the second unit process eight times, the SNMP processing unit 201 can acquire state information regarding all VLANs of the communication device 20.
  • the SNMP processing unit 201 When the SNMP processing unit 201 repeatedly executes the second unit processing for all the acquired object IDs, the SNMP processing unit 201 extracts the port management data 30 from each received MIB data processing response. Then, the SNMP processing unit 201 generates a Get Response (notification message) including the extracted plurality of port management data 30 by executing a PDU creation process (step S206). Then, the SNMP processing unit 201 transmits the generated Get Response to the management apparatus 10 via the management network N (Step S207). When receiving the Get Response from the SNMP processing unit 201 via the management network N, the management unit 101 of the management device 10 acquires a plurality of port management data 30 from the Get Response.
  • the MIB processing unit 202 performs a MIB data update process in addition to the search of the port management data 30 in the process of step S204.
  • a process from a MIB data processing request to a MIB data processing response (a process corresponding to the second unit process) is performed for each VLAN. Repeatedly executed. At this time, the processing time required per VLAN is t3. On the other hand, when the process of FIG. 4 described above is performed, the processing time required for the second unit process is t4. Assume that the number of ports of the communication device 20 is 8, and the number of registered VLANs is 4094 for the maximum number.
  • the management device 10 that is an SNMP manager and the communication device 20 that is an SNMP agent can be reduced. Therefore, the amount of communication required for monitoring control of the communication device 20 can be reduced.
  • a list of VLANs is recorded in the MIB processing unit 202 for each port, and is managed with an object ID. Therefore, a request message such as Get Request is transmitted for each port. Therefore, the number of request messages does not increase no matter how many VLANs increase. Therefore, it is possible to reduce the number of times of message processing, and it is possible to shorten the time required for VLAN status acquisition and setting change.
  • VLAN status is represented by binary values of “0” or “1”
  • MIB data can be aggregated to a data capacity of the number of VLANs per port / 8 (bytes). Therefore, in addition to the reduction in the number of messages described above, the communication bandwidth required for communication can be further reduced, and the management network N can be operated efficiently.
  • the CPU usage time of the communication device 20 can be suppressed by reducing the number of times the SNMP message is processed. Therefore, it is possible to suppress the load on other services provided by the communication device 20.
  • C-VID customer VLAN identifier
  • S-VID in the case of S-Trunk using 512 bytes x 3 per port to support Provider Bridge standardized by IEEE802.1ad (Service VLAN identifier)
  • S-VID in the case of C-Bridge may be expressed.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)
  • Small-Scale Networks (AREA)
PCT/JP2012/074188 2011-09-26 2012-09-21 通信装置、通信方法及びプログラム Ceased WO2013047355A1 (ja)

Priority Applications (5)

Application Number Priority Date Filing Date Title
JP2013536223A JP5708818B2 (ja) 2011-09-26 2012-09-21 通信装置、通信方法及びプログラム
CN201280046512.0A CN103843291B (zh) 2011-09-26 2012-09-21 通信设备、通信方法和程序
IN2319CHN2014 IN2014CN02319A (enExample) 2011-09-26 2012-09-21
US14/344,609 US9641355B2 (en) 2011-09-26 2012-09-21 Communication device, communication method, and program
EP12837254.7A EP2763352B1 (en) 2011-09-26 2012-09-21 Communication device, communication method, and program

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2011208639 2011-09-26
JP2011-208639 2011-09-26

Publications (1)

Publication Number Publication Date
WO2013047355A1 true WO2013047355A1 (ja) 2013-04-04

Family

ID=47995387

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2012/074188 Ceased WO2013047355A1 (ja) 2011-09-26 2012-09-21 通信装置、通信方法及びプログラム

Country Status (6)

Country Link
US (1) US9641355B2 (enExample)
EP (1) EP2763352B1 (enExample)
JP (1) JP5708818B2 (enExample)
CN (1) CN103843291B (enExample)
IN (1) IN2014CN02319A (enExample)
WO (1) WO2013047355A1 (enExample)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
ES2617196T3 (es) * 2013-04-19 2017-06-15 Entuity Limited Identificación de rutas en una red de dispositivos de enrutamiento/conmutación mezclados
JP6193473B2 (ja) 2013-04-19 2017-09-06 エンチュイティ リミテッドＥｎｔｕｉｔｙ Ｌｉｍｉｔｅｄ コンピュータ実施方法、コンピュータプログラム製品及びコンピュータ
GB2513188B (en) 2013-04-19 2015-11-25 Entuity Ltd Identification of the paths taken through a network of interconnected devices
GB2527273B (en) 2014-04-11 2016-08-03 Entuity Ltd Executing a loop computer program to identify a path in a network
US20180270200A1 (en) * 2017-03-14 2018-09-20 T-Mobile Usa, Inc. Active Inventory Discovery for Network Security
JP7080096B2 (ja) * 2018-04-12 2022-06-03 株式会社アイ・エル・シー 機器制御装置、機器制御システム、機器制御方法および機器制御プログラム

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007135109A (ja) * 2005-11-11 2007-05-31 Hitachi Ltd 仮想ネットワーク管理方法、仮想ネットワーク管理プログラム、仮想ネットワーク管理システムおよび仮想ネットワーク管理手段
JP2007180768A (ja) 2005-12-27 2007-07-12 Hewlett-Packard Development Co Lp 情報取得装置およびその方法
JP2008124839A (ja) * 2006-11-13 2008-05-29 Ntt Docomo Inc ネットワーク情報収集システム及びネットワーク情報収集方法

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6393472B1 (en) * 1997-12-10 2002-05-21 At&T Corp. Automatic aggregation of network management information in spatial, temporal and functional forms
US7370362B2 (en) * 2005-03-03 2008-05-06 Cisco Technology, Inc. Method and apparatus for locating rogue access point switch ports in a wireless network
CN100341296C (zh) 2005-11-21 2007-10-03 西安交通大学 一种用于MIPv6实验的移动节点切换控制方法
JP2007318553A (ja) * 2006-05-26 2007-12-06 Fujitsu Ltd ネットワーク管理方法
CN102006267B (zh) 2009-09-03 2014-08-13 中兴通讯股份有限公司 基于简单网络协议的接入认证方法及装置
US20110216670A1 (en) * 2010-03-03 2011-09-08 Sriranganath Pradeep Method for determining network topology

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007135109A (ja) * 2005-11-11 2007-05-31 Hitachi Ltd 仮想ネットワーク管理方法、仮想ネットワーク管理プログラム、仮想ネットワーク管理システムおよび仮想ネットワーク管理手段
JP2007180768A (ja) 2005-12-27 2007-07-12 Hewlett-Packard Development Co Lp 情報取得装置およびその方法
JP2008124839A (ja) * 2006-11-13 2008-05-29 Ntt Docomo Inc ネットワーク情報収集システム及びネットワーク情報収集方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2763352A4

Also Published As

Publication number Publication date
EP2763352A4 (en) 2015-06-17
CN103843291A (zh) 2014-06-04
JPWO2013047355A1 (ja) 2015-03-26
US20140347982A1 (en) 2014-11-27
IN2014CN02319A (enExample) 2015-06-19
JP5708818B2 (ja) 2015-04-30
CN103843291B (zh) 2017-06-13
EP2763352B1 (en) 2020-08-19
EP2763352A1 (en) 2014-08-06
US9641355B2 (en) 2017-05-02

Similar Documents

Publication Publication Date Title
JP7035227B2 (ja) データパケット検出方法、デバイス、及びシステム
US9769054B2 (en) Network topology discovery method and system
JP5958570B2 (ja) ネットワークシステム、コントローラ、スイッチ、及びトラフィック監視方法
US10075371B2 (en) Communication system, control apparatus, packet handling operation setting method, and program
JP5708818B2 (ja) 通信装置、通信方法及びプログラム
EP2582099A1 (en) Communication system, logic channel control device, control device, communication method and program
CN103081410B (zh) 通信质量监视系统、通信质量监视方法
JP7026776B2 (ja) 通信方法、通信デバイス、および記憶媒体
JP7040734B2 (ja) フレーム集約方法、ネットワーク設定フレーム送信方法およびデバイス
TW201223205A (en) Communication device, communication system, communication method, and recording medium
KR20140072343A (ko) Ｓｄｎ 망의 장애 대처 방법
CN111371634B (zh) 一种通信方法、装置及系统
KR20140106235A (ko) 오픈플로우 스위치 및 그 패킷 처리 방법
EP2553870B1 (en) An operations, administrations and management proxy and a method for handling operations, administrations and management messages
CN105490937B (zh) 以太虚拟网络网关切换方法和服务商边缘节点设备
CN115473840A (zh) 一种报文发布方法、转发路径处理方法及装置
CN103220228A (zh) 一种bgp路由的发送方法和设备
JP5630094B2 (ja) 通信装置および通信方法
KR20180058594A (ko) Sdn/tap 어플리케이션
US8614958B2 (en) Systems and methods of snooping connectivity fault messages to configure maintenance end point for alarm suppression messages
KR20180058593A (ko) Sdn 화이트박스 스위치
KR20180058592A (ko) Sdn 제어기
JP2017098660A (ja) ネットワークシステム、及びスイッチ
CN111030943A (zh) 一种报文的处理方法、装置、转发设备及存储介质
WO2024154300A1 (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: 12837254

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2012837254

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2013536223

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 14344609

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE