US7693092B2 - Multicast tree monitoring method and system in IP network - Google Patents
Multicast tree monitoring method and system in IP network Download PDFInfo
- Publication number
- US7693092B2 US7693092B2 US11/854,122 US85412207A US7693092B2 US 7693092 B2 US7693092 B2 US 7693092B2 US 85412207 A US85412207 A US 85412207A US 7693092 B2 US7693092 B2 US 7693092B2
- Authority
- US
- United States
- Prior art keywords
- packets
- multicast
- transmission
- test packets
- network
- 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.)
- Expired - Fee Related, expires
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/16—Multipoint routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/48—Routing tree calculation
Definitions
- the present invention relates to a multicast tree monitoring method and a multicast tree monitoring system in an IP (Internet Protocol) network and further to a network monitoring device, router, and transmission terminal thereof.
- IP Internet Protocol
- Stream-type IP multicast networks which use multicast IP addresses to transmit for example video information from one transmission terminal to a large number of members (receiving terminals) are being constructed and are being used by large numbers of users,
- this video information is transferred as multicast frames via predetermined routers over the IP network to be provided to predetermined members.
- the video information must accurately reach all of the predetermined members.
- this video information must not end up being transmitted by mistake to destinations other than those of the predetermined members. that is, the transmission routes of the multicast frames must be the designed transmission routes. Verifying that they are the designed transmission routes is important for, e.g., the carriers.
- multicast tree monitoring is performed by for example the carriers at various times such as the start of transmission of the video information or at the time of occurrence of a fault.
- the present invention refers to a method and a system for such “multicast tree monitoring”.
- Patent Document 1 describes to
- set a field management process (FM) on a network set field client processes (FC) at the hosts ( 1 to 3 ), set a subnet monitoring process (SM) in each subnet, have the field management process (FM) decide the connection points between the subnets when the field management process (FM) receives a request for generation of an information bus as a means for communication among a plurality of terminals on the network via the field client processes (FC) from the user, and emit and set instructions for setting multicast tunneling to the subnet monitoring processes (SM) in response to this so that the terminals designate the multicast addresses and transmit “data and dynamically generate the information bus which supports communication between groups”
- Patent Document 1 Japanese Patent Publication (A) No 2001-156855.
- FIG. 28 is a diagram showing a case study of a fault in an IP multicast network.
- the figure shows the state where video information from a transmission terminal (camera) is transmitted along a multicast tree through a plurality of routers to a plurality (in the figure, two) receiving terminals.
- RPT Rendezvous Point Tree
- PIM-SM Protocol Independent Multicast Sparse Mode
- RP Rendezvous Point
- DR Designated Router
- the present invention considering the above problems, has as its object the provision of a method and system for monitoring a multicast tree which does not require knowledge of the method for confirming setting information for all devices, which does not demand performance of the previously stated ping operation etc., and therefore enables both confirmation of the multicast tree and confirmation of communication and quality in a short time by using a simple technique.
- a certain amount of monitoring test packets, differentiated from usual multicast frames is transmitted continuously from a source of transmission of video information, for example, a transmission terminal ( 2 T), in accordance with an instruction from a network monitoring device ( 4 ).
- the network monitoring device ( 4 ) collects pass status information (for example, MIB information) generated by each router ( 3 ) which receives the continuous test packets and passes therethrough.
- the network monitoring device ( 4 ) uses the collected pass status information and topology information which is held by itself to judge the transmission directions of the test packets at each router ( 3 ), and searches for and specifies the multicast tree based on the results of the judgment.
- FIG. 1 is a view showing the basic configuration of a multicast tree monitoring system 10 according to the present invention.
- FIG. 2 is a flow chart showing a monitoring operation of the multicast tree monitoring system 10 shown in FIG. 1 .
- FIG. 3 is a view showing a specific image of an IP network 1 to which the multicast tree monitoring system based on the present invention is applied.
- FIG. 4 is a view showing an example of a specific configuration of the multicast tree monitoring system 10 based on the present invention.
- FIG. 5 is the view (part 1 ) of part of FIG. 3 taken out in order to explain a route judgment operation of the present invention.
- FIG. 6 is a view showing an example of the configuration of a topology management table 34 .
- FIG. 7 is a view showing the results of judgment by a judgment unit 33 with the items of the judgment conditions embedded
- FIG. 8 is a view illustrating the results of judgment of the route status.
- FIG. 9 is a view illustrating the results of judgment by a final judgment unit 33 .
- FIG. 10 is the view (part 2 ) showing part of FIG. 3 taken out in order to explain a route judgment operation of the present invention.
- FIG. 11 is a view showing the final results of judgment by the judgment unit 33 based on FIG. 10 .
- FIG. 12 is a view showing a first example of objects of an MIB.
- FIG. 13 is a view showing a second example of objects of an MIB.
- FIG. 14 is a view showing a third example of objects of an MIB.
- FIG. 15 is a view showing an IP network ( FIG. 3 ) to which the first embodiment of the present invention is applied.
- FIG. 16 is a flowchart (part 1 ) showing the operation of the first embodiment executed in FIG. 15 .
- FIG. 17 is a flowchart (part 2 ) showing the operation of the first embodiment executed in FIG. 15 .
- FIG. 18 is a view showing an IP network to which a second embodiment of the present invention is applied ( FIG. 3 ).
- FIG. 19 is a flowchart (part 1 ) showing the operation of the second embodiment executed in FIG. 18 .
- FIG. 20 is a flowchart (part 2 ) showing the operation of the second embodiment executed in FIG. 18 .
- FIG. 21 is a view showing an IP network to which a third embodiment (#1) of the present invention is applied ( FIG. 3 ).
- FIG. 22 is a flowchart (part 1 ) showing the operation of the third embodiment (#1) executed in FIG. 21 .
- FIG. 23 is a flowchart (part 2 ) showing the operation of the third embodiment (#1) executed in FIG. 21 .
- FIG. 24 is a view showing an IP network to which the third embodiment (#2) of the present invention is applied ( FIG. 3 ).
- FIG. 25 is a flowchart (part 1 ) showing the operation of the third embodiment (#2) executed in FIG. 24 .
- FIG. 26 is a view showing an IP network to which a fault detection system is applied as a fourth embodiment.
- FIGS. 27( a ) to ( d ) are views showing the header format of a transmission frame.
- FIG. 28 is a view showing a case study of a fault in an IP multicast network.
- FIG. 29 is a viewing showing an example of a transmission route for explaining one problem of the prior art.
- FIG. 1 is a view showing the basic configuration of a multicast tree monitoring system according to the present invention.
- the monitoring system is shown by reference numeral 10 .
- Typical components are shown by reference numerals 11 to 14 .
- the multicast tree monitoring system 10 according to the present invention can be formed within an IP network 1 .
- This IP network 1 is comprised of terminals 2 , routers 3 , and a network monitoring device 4 which searches for the transmission routes of the multicast frames.
- this IP network 1 is comprised of a transmission terminal (TX) 2 T transmitting multicast frames, a plurality of receiving terminals (RX) 2 R receiving the multicast frames, and a plurality of routers 3 on tree-shaped multicast frame transmission routes from this transmission terminal 2 T to the plurality of receiving terminals 2 R.
- the multicast tree monitoring system 10 formed in this IP network 1 is typically comprised of an instruction functional part 11 , a transmitting functional part 12 , a status information generating functional part 13 , and a judgment functional part 14 .
- the main functions of these functional parts 11 to 14 are as follows.
- the instruction functional part 11 is provided in the network monitoring device 4 and is provided with a function of instructing the transmission terminal 2 T to transmit monitoring test packets differentiated from normally transmitted multicast frames,
- the transmitting functional part 12 is provided in the transmission terminal 2 T and is provided with a function of transmitting the test packet toward the routers 3 in accordance with the instruction,
- the status information generating functional part 13 is provided in each router 3 receiving and passing the transmitted test packets and is provided with a function of generating pass status information of the passed test packets, and
- the judgment functional part 14 is provided in the network monitoring device 4 and is provided with a function of judging the transmission directions of the test packets on the IP network 1 based on the pass status information collected from the routers 3 and specifying the tree-shaped multicast frame transmission routes based on the results of judgment.
- FIG. 2 is a flow chart showing the multicast tree monitoring method executed in the multicast tree monitoring system 10 of the above FIG. 1 . That is, the multicast tree monitoring method according to the present invention for searching for the transmission routes of the multicast frames by the network monitoring device 4 is executed by steps S 11 to S 14 shown in the figure.
- Step S 11 The network monitoring device 4 instructs the transmission terminal 2 T to transmit monitoring test packets differentiated from normally transmitted multicast frames,
- Step S 12 The transmission terminal 2 T transmits the test packets toward the routers 3 in accordance with the instruction
- Step S 13 Each of the routers 3 receiving and passing the transmitted test packets generates pass status information of the test packets,
- Step S 14 The network monitoring device 4 judges the transmission directions of the test packets on the IP network 1 based on the pass status information collected from the routers 3 and specifies the tree-shaped transmission routes based on the results of judgment.
- the monitoring test packets are selected from any of
- test packets a predetermined certain amount of the test packets is continuously transmitted.
- the pass status information is preferably generated as network management database MIB (Management Information Base) information.
- MIB Management Information Base
- the judgment is performed by referring to a topology management table, in the network monitoring device 4 , holding the connections with the neighboring routers.
- FIG. 1 and FIG. 2 The basic concept of the system and method according to the present invention was shown referring to FIG. 1 and FIG. 2 . Next, this will be shown while referring to more specific embodiments.
- FIG. 3 is a view showing a specific image of the IP network 1 to which the multicast tree monitoring system based on the present invention is applied. Note that throughout all of the figures, similar components are assigned the same reference numerals or symbols.
- the figure specifically shows the IP network 1 .
- the description of the multicast tree monitoring system explained above (reference numerals 11 to 14 of FIG. 1 ) is omitted.
- This is to make the image of the transmission routes of the multicast tree according to the present invention much easier to understand. That is, referring to this figure, the state where the multicast frames (video information) from the transmission terminal 2 T (in the example of the figure, a camera) pass through predetermined routers 3 on the IP network 1 and are transferred to predetermined receiving terminals 2 R (in the example of this figure, computers) is shown.
- the transfer routes become transmission routes 5 forming the multicast tree.
- this network monitoring device 4 includes the instruction functional part 11 and judgment functional part 14 of FIG. 1 .
- this network monitoring device 4 for example, the multicast tree monitor server, is usually provided in the IP network 1 .
- This existing server has the functional parts 11 and 14 newly added to them according to the present invention.
- This network monitoring device 4 includes, further, a topology management table, status information (MIB) collection unit, and the like.
- the transmission terminal (shown as a camera) 2 T of FIG. 3 is a so-called multicast stream transmission device.
- the transmission device ( 2 T) sends test packets comprised of any of
- the components forming the multicast tree monitoring system 10 will be shown more specifically.
- FIG. 4 is a view showing an example of the specific configuration of a multicast tree monitoring system 10 based on the present invention.
- this device 4 was shown as both an instruction functional part 11 which instructs the transmission terminal 2 T to transmit monitoring test packets differentiated from the normally transmitted multicast frames and a judgment functional part 14 which judges the transmission directions of the test packets on the IP network 1 based on the pass status information of the test packets generated by each router 3 which received and passed the transmitted test packets and specifies the tree-shaped multicast frame transmission routes by the results of judgment, but in FIG. 4 , the instruction functional part 11 is comprised of the tree monitoring execution instruction unit 21 .
- this is comprised of a status information collection unit 31 which collects the pass status information from each router 3 , a status information storage unit 32 which stores the collected pass status information, and a multicast path judgment unit 33 which judges the transmission directions based on the stored pass status information.
- This judgment functional part 14 is designed to perform the above judgment when the difference between the pass status information, stored in the status information storage unit 32 , immediately before the transmission of the test packets and the pass status information after the transmission of the test packets is large. This is because the fact that the difference is large means that the test packets passed through the routers 3 .
- the judgment functional part 14 has the topology management table 34 holding the connections with the neighboring routers and refers to it for judgment of the transmission directions.
- the judgment functional part 14 preferably has a tree display unit 35 for displaying the tree-shaped multicast frame transmission routes 5 specified by the results of judgment to the operator.
- the terminal 2 T was shown as the transmitting functional part 12 which receives the instruction from the network monitoring device 4 to transmit the monitoring test packets differentiated from the normally transmitted multicast frames and transmits the test packets to the routers 3 , but in FIG. 4 , the transmitting functional part 12 is comprised of both a tree monitoring request receiving unit 41 which receives the instruction from the network monitoring device 4 to transmit the monitoring test packets and a test packet transmitting unit 42 which receives the instruction and generates and transmits the test packets Pt.
- test packets Pt generated and transmitted by this test packet transmitting unit 42 are selected from any of the previously stated packets (i), (ii), and (iii). A predetermined certain amount of the test packets Pt is continually transmitted.
- each router 3 was shown as the status information generation functional part 13 generating the pass status information of the test packets when receiving and passing the test packets Pt transmitted by the transmission terminal 2 T for use for the search by the network monitoring device 4 , but in FIG. 4 this status information generation functional part 13 is comprised of a network management database (MIB) 51 and a status information transmitting unit 52 transmitting the pass status information generated from this network management database (MIB) 51 to the network monitoring device 4 directly or via the transmission terminal 2 T.
- MIB network management database
- the switch unit 53 performs the role of the existing inherent routing of the router 3 .
- the function of fault detection in the IP network 1 can be simply realized. Due to this, the judgment functional part 14 shown in FIG. 4 can be further provided with a fault judgment unit 36 generating fault detection information ALM when judging that the tree-shaped multicast frame transmission routes 5 specified by the results of judgment by the judgment unit 33 do not reach all of the receiving terminals 2 R which should receive the multicast frames.
- the network monitor device 4 is a “multicast tree monitor server”, and the status information collection unit 31 is an “SNMP transmitting/receiving unit” (SNMP: Simple Network Management Protocol). Further, the status information storage unit 32 is an “MIB information storage unit”. Furthermore, the transmission terminal 2 T shown in FIG. 4 is a “multicast frame transmission device”, and the network management database (DB) in each router 3 shown in FIG. 4 is an “MIB” and the status information transmitting unit is an “SNMP transmitting/receiving unit”.
- the multicast tree monitoring system 10 of the present invention is comprised of a multicast tree monitor server ( 4 ), multicast frame transmission device ( 2 T), and routers 3 .
- the multicast path judgment unit 33 instructs the transmission of test packets for tree monitoring to the multicast frame transmission device ( 2 T),
- the routers 3 acquires the MIB information from the routers 3 by instructing the collection of the MIB (for example, RMON (Remote Network Monitoring) MIB) to the SNMP transmitting/receiving unit ( 31 ),
- the MIB for example, RMON (Remote Network Monitoring) MIB
- the tree monitoring execution instruction unit 21 notifies the multicast frame transmission device ( 2 T) of the addresses of the transmitted test packets, the packet sizes of the test packets, the TTL, and the port numbers to the transmission device ( 2 T) and notifies the results of execution from the transmission device ( 2 T) to the multicast path judgment unit 33 . Due to this, it is possible to extract the MIB information and the time exceeded packets at the ICMP (Internet Control Message Protocol) required for identification of the tree.
- ICMP Internet Control Message Protocol
- the topology management table 34 stores the physical connection information of each router 3 with the neighboring routers. Due to this, it can be learned which interfaces the multicast test packets use.
- the MIB information storage unit ( 32 ) stores the MIB information collected from the routers 3 . Due to this, the multicast path judgment unit 33 can analyze the necessary MIB information.
- the SNMP transmitting/receiving unit 31 is designed to execute an SNMP command for collecting the MIB information from the routers 3 in accordance with an instruction from the multicast path judgment unit 33 . Due to this, it can collect information stored in the MIB information storage unit ( 32 ).
- the tree display unit 35 is designed to be able to display the configuration of the tree recognized by the multicast path judgment unit 33 to the operator. Due to this, visualization of the tree is achieved and convenience is obtained.
- the tree monitoring request receiving unit 41 is designed to receive instructions and parameters from the tree monitoring execution instruction unit 21 of the multicast tree monitor server ( 4 ) and instruct the execution of transmission to the test packet transmitting unit 42 and
- the test packet transmitting unit 42 is designed to transmit the test packets by the specified address, TTL, port number, and packet size. Due to this, the multicast tree monitor server ( 4 ) can collect the necessary MIB information and the like.
- the switch unit 53 is designed to route test packets from the multicast frame transmission device ( 2 T). Due to this, the test packets can be routed to other routers or the receiving terminals 2 R.
- the SNMP transmitting/receiving unit ( 52 ) is designed to respond with the MIB information to an SNMP request from the multicast tree monitor server ( 4 ). Due to this, the multicast tree monitor server can collect the necessary MIB information.
- the MIB ( 51 ) is designed to collect the number of received packets and the like based on the reception of the test packets. Due to this, the multicast tree monitor server ( 4 ) can collect the necessary MIB information.
- the server ( 4 ) collects the MIB information of each interface and searches for the interfaces with the large inflow of the specific test packets to find the inflow directions of the test packets so as to be able to verify the flow of the multicast test packets.
- the server ( 4 ) can analyze the ICMP time exceeded packets transmitted by routers 3 toward the multicast frame transmission device ( 2 T) and obtain a grasp of the number of hops from the multicast stream transmission device ( 2 T).
- FIG. 5 is a view showing part of FIG. 3 taken out in order to explain the route judgment operation of the present invention.
- reference numeral 3 represents a router as shown in FIG. 3
- the routers are shown differentiated such as Router 1 , Router 2 , . . .
- the interfaces of the routers are shown differentiated as the ports P 1 , P 2 , and P 3 .
- the black dots and white dots near the ports (P) show the magnitude of inflow of the test packets into the interfaces (ports) and show an example of large inflow of test packets to the ports with the white dots.
- the transmission directions of the multicast packets are specified according to the magnitude of the inflow of the test packets.
- the topology management table 34 of FIG. 4 ) becomes effective.
- FIG. 6 is a view showing an example of the configuration of the topology management table 34 . However, this shows the management table for the “Router 1 ” among the routers 3 . The other “Router 2 ” and “Router 3 ” are also provided with individual management tables.
- the ports P 1 , P 2 , and P 3 of the router (Router 1 ) 3 are connected to the port P 2 of the neighboring Router 2 , the port PI of the neighboring Router 3 , and the port P 1 of the neighboring Router 5 , so the contents of the topology management table 34 for the Router 1 become as shown in FIG. 6 .
- FIG. 7 is a view showing the results of judgment by the judgment unit 33 in which the judgment conditions are embedded. Whether the inflow of the test packets is large or small is judged by setting some threshold value and deciding whether the inflow is larger or smaller than it.
- FIG. 8 is a view illustrating the results of judgment of the route status.
- the right arrow, the left arrow, and the two-headed arrow of the figure show the transmission directions of the test packets at the ports P 1 , P 2 , and P 3 of the Router 1 , that is, the route status (pass status at each router).
- the Table 34 shown in FIG. 9 is completed.
- FIG. 9 is a view illustrating the results of judgment by the final judgment unit 33 . Due to this, the transmission routes of the multicast frames are specified, and the search of the multicast tree is terminated.
- FIG, 10 is a view showing part of FIG. 3 taken out in order to explain the route judgment operation of the present invention. It differs from FIG. 5 in not showing black dots and white dots.
- the test packets used in FIG. 10 are test packets of the third type (iii), that is, the type utilizing the TTL. These differ from test packets of the first type (i) in FIG. 5 , that is, of the type using short data lengths and test packets of the second type (ii), that is, of the type using unused source addresses and/or unused destination addresses.
- time exceeded packets are collected at the status information collection unit 31
- time exceeded packets are collected at the status information collection unit 31
- FIG. 11 is a view showing the results of judgment by the final judgment unit 33 when the test packets having the above TTL as parameters are utilized. This stands on a network the same as in FIG. 5 , so the results of judgment naturally become the same as the results of judgment of FIG. 9 .
- FIG. 12 is a view showing a first example of the objects of an MIB and shows the first type (i) of the test packets,
- FIG. 13 is a view showing a second example of the objects of an MIB and shows the second type (ii) of the test packets,
- FIG. 14 is a view showing a third example of the objects of an MIB and shows the third type (iii) of the test packets.
- FIG. 12 shows test packets of the first type (i) having data lengths not usually used as multicast frames as Pt. Packets with data lengths of less than 64 bytes are used as the test packets.
- FIG. 13 shows the characteristic of test packets of the second type (ii) having unused source IP addresses or unused destination multicast IP addresses.
- FIG. 14 shows the characteristics of test packets of the third type (iii) with packet effective time periods TTL (Time To Live) set from 1 to a predetermined N.
- TTL Time To Live
- FIG. 12 to FIG. 14 show the NIB information which becomes necessary for determination of the multicast tree.
- NIB information which becomes necessary for determination of the multicast tree.
- first, second, and third embodiments using the test packets of the first type (i), the second type (ii), and the third type (iii) will be explained. Note that these first, second, and third embodiments are embodiments of the configurations explained in the above FIG. 4 to FIG. 14 on the IP network 1 of FIG. 3 .
- FIG. 15 is a view showing an IP network ( FIG. 3 ) to which the first embodiment of the present invention is applied,
- FIG. 16 is a flowchart (part 1 ) showing the operation of the first embodiment executed at FIG. 15 .
- FIG. 17 is the same flowchart (part 2 ).
- the operation under the first embodiment becomes as in the following 1 to 6.
- the transmission terminal multicast frame transmission device
- an encoder ( 2 E) which formats video information to the MPEG or the like is shown.
- MIB EthernetStatsUndersizePkts
- MIB EthernetStatsUndersizesPkts
- Step S 21 The monitor server ( 4 ) receives the count value of the test packets (in the first embodiment, the etherStatsUndersizePkts of the top row of FIG. 12 ) to be sent from now over the IP network 1 from the MIB ( 51 of FIG. 4 ) of each router 3 . This is to obtain the initial count value immediately before the monitor test of etherStatsUndersizePkts in the MIB ( 51 ). That is, when the inflow of the test packets is much greater than the initial count value, it judges that the test packets passed through that router,
- Step S 22 The monitor server ( 4 ) designates the number of test packets to be sent in a large amount in a short time and then instructs the transmission thereof to the encoder ( 2 E).
- Step S 23 The encoder ( 2 E) receiving the above transmission instruction starts transmission of packets comprised of only the RTP headers as test packets from the test packet transmitting unit ( 42 of FIG. 4 ).
- Step S 24 The encoder ( 2 E) ends the transmission of the test packets, then notifies this end to the monitor server ( 4 ).
- Step S 25 By the end of transmission of the test packets, a router through which the test packets passed should be greatly increased in the MIB information, that is, the count value, of the test packets, that is, the etherStatsUndersizePkts. Therefore, the monitor server ( 4 ) receives the information of the count value of the etherStatsUndersizePkts once again from the MIB ( 51 ) of each router 3 .
- Step S 26 The monitor server ( 4 ) judges by the judgment unit ( 33 of FIG. 4 ) whether the count value, that is, the inflow of the test packets, has exceeded the above threshold value TH.
- Step S 27 If the threshold value TH is exceeded, it is judged that “There is input of a multicast”, and this is set in the topology management table 34 ,
- Step S 28 If the threshold value TH is not exceeded, it is judged that “There is no input of a multicast”, and this is set in the topology management table 34 . Note that the “There is input of a multicast” and “There is no input of a multicast” correspond to representation in FIG. 9 of white dots and black dots.
- Step S 30 The pass status of the test packets in each router 3 is thereby learned and this is displayed on a display unit ( 35 of FIG. 4 ).
- the multicast tree monitoring system 10 uses
- a multicast frame transmission device ( 2 T) which transmits packets of less than 64 bytes size almost never sent over the network as monitoring use test packets
- a multicast tree monitor server ( 4 ) which collects MIB information (etherStatsUndersizePkts) showing the inflow of packets of less than 64 bytes size, and
- routers 3 which generate MIB information based on the inflow of the test packets and is configured so that
- the monitor server ( 4 ) judges the interfaces (ports) of each router 3 to which packets having the transmission sizes instructed to the transmission device ( 2 T) are input from the MIB information and judges the transmission directions of the frames at the connected interfaces based on the inflow directions of the packets found from the connections shown in the topology management table 34 and the MIB information.
- FIG. 18 is a view showing an IP network ( FIG. 3 ) to which the second embodiment of the present invention is applied,
- FIG. 19 is a flowchart (part 1 ) showing the operation of the second embodiment executed in FIG. 18 .
- FIG. 20 is the same flowchart (part 2 ).
- MIB information (addressMapSource and addressMapNetworkAddress) from each router 3 and specify input ports of the test addresses,
- FIG. 19 and FIG. 20 The more detailed flow of the processing will be explained referring to FIG. 19 and FIG. 20 . Note that among the steps of the flowchart shown in FIG. 19 and FIG. 20 , steps substantially the same as the steps of FIG. 16 and FIG. 17 are shown by the same step numbers as the corresponding steps in FIG. 16 and FIG, 17 , that is, S 22 , S 24 , and S 26 to S 30 .
- the steps characterizing the second embodiment are S 31 , S 32 , and S 33 .
- Step S 31 The monitor server ( 4 ) receives the count value of the test packets to be sent over the IP network 1 from now (in the second embodiment, the packets shown in FIG. 13 ) from the MIB ( 51 of FIG. 4 ) of each router 3 . This is to obtain the initial count value in the MIB ( 51 ) immediately before the monitoring test. That is, when the inflow of the test packets right before the test is much greater than the initial count value, it judges that the test packets passed through that router.
- Step S 32 The packets having the IP addresses dedicated to the test packets in the second embodiment (see top row of FIG. 13 ) are transmitted toward each router 3 .
- Step S 33 The MIB information for the packets prescribed in FIG. 13 is received from each router 3 .
- the subsequent steps are the same as the case of the first embodiment (S 26 to S 30 ).
- the multicast tree monitoring system 10 uses
- a multicast frame transmission device ( 2 T) which transmits monitor test packets with a specific source IP address or specific destination multicast IP addresses
- a multicast tree monitor server ( 4 ) which collects MIB information specifying the input interfaces (ports) of the test packets (addressMapSource and addressMapNetworkAddress) and MIB information measuring the inflow of the test packets (n1MatrixSDoctets), and
- routers 3 generating MIB information based on the inflow of the test packets and is configured so that
- the monitor server ( 4 ) judges the routers 3 at which packets having the transmission address and transmission amounts instructed to the transmission device ( 2 T) are observed by n1MatrixSDOctets and judges the transmission directions of the multicast tree at the connection links shown in the topology management table 34 from the results of collection of the addressMapSource and the addressmapNetworkAddress.
- FIG. 21 is a view showing an IP network ( FIG. 3 ) to which the third embodiment (#1) of the present invention is applied,
- FIG. 22 is a flowchart (part 1 ) showing the operation of the third embodiment (#1) executed in FIG. 21 .
- FIG. 23 is the same flowchart (part 2 ).
- MIB icmpTimeExcds
- MIB information (addressMapSource and addressMapNetworkAddress) from each router 3 and specify input ports of the test addresses,
- FIG. 22 and FIG. 23 The more detailed flow of the processing will be explained referring to FIG. 22 and FIG. 23 . Note that among the steps of the flowchart shown in FIG. 22 and FIG. 23 , steps substantially the same as the steps of FIG. 16 and FIG. 17 are shown by the same step numbers as the corresponding steps in FIG. 16 and FIG. 17 , that is, S 22 , S 24 , and S 26 to S 30 .
- Step S 41 The monitor server ( 4 ) receives the count value of the test packets to be sent over the IP network 1 from now (in the third embodiment (#1), the packets shown in FIG. 14 ) from the MIB ( 51 of FIG. 4 ) of each router 3 . This is to obtain the initial count value in the MIB ( 51 ) of the packets of FIG. 14 immediately before the monitoring test. That is, when the inflow of the test packets right before the test is much greater than the initial count value, it judges that the test packets passed through that router.
- Step S 42 Exactly the designated number of packets designated from TTL 1 to TTLN are transmitted toward each router 3 .
- Step S 43 The MIB information for the packets prescribed in FIG. 14 is received directly from each router 3 by the monitor server ( 4 ).
- the subsequent steps are the same as the case of the first embodiment (S 26 to S 30 ).
- a multicast tree monitor server ( 4 ) which collects MIB information specifying the input interfaces (ports) of the test packets (addressMapSource and addressMapNetworkAddress) and the MIB information showing that the TTL of the test packets has become 0 and the packets are discarded (icmpOutTimeExcds), and
- routers 3 which generate MIB information based on the transmission of the icmpOutTimeExcds packets and
- the monitor server ( 4 ) extracts the routers 3 transmitting the icmpOutTimeExcds packets for exactly the number of packets instructed to the transmission device ( 2 T) and judges the transmission directions of the multicast tree at the connection links of the topology management table 34 based on the results of collection of the addressMapSource and addressMapNetworkAddress.
- FIG. 24 is a view showing an IP network to which the third embodiment (#2) of the present invention is applied.
- FIG. 25 is a flowchart showing the operation of the third embodiment (#2) executed in FIG. 24 .
- steps 22 and S 30 are as explained above, while steps 51 to 54 form the characterizing features of the third embodiment (#2).
- Step S 51 Corresponds to the aforementioned step 2 as explained in FIG. 24
- Steps S 52 and S 53 Correspond to the aforementioned steps 3 and 4 as explained in FIG. 24 .
- the encoder ( 2 E) prepares a router list arranging the time exceeded packets received by the encoder ( 2 E) from the routers 3 in the order of TTL 1 to N based on the transmission port numbers given in the time exceeded packets and transfers this to the monitor server ( 4 ),
- step S 53 the router list of the packets arranged in the order of the TTL 1 to N received by the encoder ( 2 E) is analyzed by the judgment unit 33 in the monitor server ( 4 ) ( FIG. 4 ) and the transfer routes (pass status information) of the test packets are judged.
- Step 54 Based on the transfer routes of the test packets, the directions of the multicast are set in the topology management table 34 .
- the multicast tree monitoring system 10 uses
- a multicast tree monitor server ( 4 ) which collects the returned ICMP time exceeded packets from the transmission device ( 2 T), and
- routers 3 which transmit the information of the ICMP time exceeded packets to the monitor server ( 4 ) and is configured so as
- a fault detection system in the IP network 1 is provided. That is, the multicast tree monitoring system 10 of the present invention can also function as a fault detection system. This was already explained as the fault detection judgment unit 36 of FIG. 4 , but here the overall fault detection system will be shown.
- FIG. 26 is a view showing an IP network to which the fault detection system of the fourth embodiment is applied.
- a break in the optical fiber or a fault of a router 3 causes a fault at an F (fault) point in the figure. If utilizing the multicast tree monitoring of the present invention, such a fault location (F) can be simply specified.
- the previously stated third embodiment is used. That is, if the transmission terminal 2 T sends test packets with TTLs set from 1 to N over the network, the routers 3 return time exceeded packets to the transmission terminal 2 T and the count values of the counters corresponding to the routers are increased at the monitor server ( 4 ).
- test packets cannot reach the routers at the downstream side of the fault location (F point) ( 3 a , 3 b , and 3 c ). Due to this, as shown by the dotted lines Aa, Ab, and Ac in FIG. 26 , the ICMP time exceeded packets are not returned, Due to this, the count values of the counters corresponding to these routers 3 a , 3 b , and 3 c seen from the monitor server ( 4 ) remain stopped at fixed values. As a result, the monitor server ( 4 ) deduces that the fault occurred around the router ( 3 a ) nearest the transmission terminal 2 T among these routers and emits fault detection information ALM from the fault judgment unit 36 .
- the fault was found by detecting the absence of ICMP time exceeded packets, but the invention is not limited to this. It is also possible to find the fault in the same way by monitoring for an absence of MIB information.
- the existence of the specific test packets is important. Due to this, in the above explanation, the RTP header, TTL, transmission source port number, and the like can be used. Therefore, an example of the transmission frames forming the test packets will be shown.
- FIGS. 27( a ) to ( d ) are views showing the header format of the transmission frames.
- (a) of the figure shows an overall Ether frame.
- the IP header, UDP header, and RTP header in it are shown in detail in (b), (c), and (d) of the figure.
- the test packets of the first type (i) can be realized by generation of frames of the 56 bytes up to the RTP header (d) shown here. Further, the test packets of the other types (ii) and (iii) can be realized by setting the TTL (b) in the IP header or the port numbers (c) in the UDP header etc. to desired values in the header information of each layer.
- a simple technique may be used for verification of the multicast tree and confirmation of communication and monitoring of the multicast tree, which used to take several hours to examine, can be completed in several minutes.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims (13)
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2005/004697 WO2006098024A1 (en) | 2005-03-16 | 2005-03-16 | Multicast tree monitoring method and system in ip network |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2005/004697 Continuation WO2006098024A1 (en) | 2005-03-16 | 2005-03-16 | Multicast tree monitoring method and system in ip network |
Publications (2)
Publication Number | Publication Date |
---|---|
US20080175172A1 US20080175172A1 (en) | 2008-07-24 |
US7693092B2 true US7693092B2 (en) | 2010-04-06 |
Family
ID=36991384
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/854,122 Expired - Fee Related US7693092B2 (en) | 2005-03-16 | 2007-09-12 | Multicast tree monitoring method and system in IP network |
Country Status (3)
Country | Link |
---|---|
US (1) | US7693092B2 (en) |
JP (1) | JP4381448B2 (en) |
WO (1) | WO2006098024A1 (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090290500A1 (en) * | 2008-05-22 | 2009-11-26 | Fujitsu Limited | Measurement managing apparatus and communication system |
US20100246415A1 (en) * | 2007-11-21 | 2010-09-30 | Fujitsu Limited | Network testing method and system |
US9025494B1 (en) * | 2012-03-27 | 2015-05-05 | Infoblox Inc. | IPv6 network device discovery |
US9413623B2 (en) | 2012-04-26 | 2016-08-09 | Hewlett Packard Enterprise Development Lp | Multicast routing path check |
US9419985B1 (en) * | 2012-09-25 | 2016-08-16 | Morta Security Inc | Interrogating malware |
Families Citing this family (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4579995B2 (en) * | 2008-01-28 | 2010-11-10 | 日本電信電話株式会社 | Route identification system |
JP4627324B2 (en) * | 2008-02-12 | 2011-02-09 | 日本電信電話株式会社 | Multicast route identification method |
US8599725B2 (en) | 2008-03-17 | 2013-12-03 | Comcast Cable Communications, Llc | Representing and searching network multicast trees |
US8259594B2 (en) | 2008-03-17 | 2012-09-04 | Comcast Cable Holding, Llc | Method for detecting video tiling |
JP4829940B2 (en) * | 2008-08-12 | 2011-12-07 | 日本電信電話株式会社 | IP multicast communication monitoring method and system |
JP5109940B2 (en) * | 2008-11-20 | 2012-12-26 | 富士通株式会社 | Input edge router identification method, program, and computer |
JP5316178B2 (en) * | 2009-04-07 | 2013-10-16 | 富士通株式会社 | Communication path estimation program, method and computer |
US9077633B2 (en) | 2010-06-29 | 2015-07-07 | Telefonaktiebolaget L M Ericsson (Publ) | Method and an apparatus for evaluating network performance |
JP5593152B2 (en) * | 2010-07-20 | 2014-09-17 | 株式会社日立国際電気 | Data recording system, data recording apparatus, management apparatus, and communication amount control method |
US8948001B2 (en) * | 2012-06-26 | 2015-02-03 | Juniper Networks, Inc. | Service plane triggered fast reroute protection |
US20160194379A1 (en) | 2013-08-13 | 2016-07-07 | Elastagen Pty Ltd | Regeneration of Damaged Tissue |
JP7180200B2 (en) * | 2018-08-21 | 2022-11-30 | 日本電信電話株式会社 | Relay device and relay method |
US11283639B2 (en) * | 2019-03-07 | 2022-03-22 | Hewlett Packard Enterprise Development Lp | Multicast flow anomaly identification |
CN114500228B (en) * | 2021-12-29 | 2024-03-29 | 深圳市共进电子股份有限公司 | Automatic test method and automatic test system |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020041586A1 (en) * | 2000-10-11 | 2002-04-11 | Hiroshi Hayashino | Communications control method |
US20020181485A1 (en) * | 1999-05-25 | 2002-12-05 | Yang Cao | Apparatus and method for internet protocol flow ring protection switching |
US20030065944A1 (en) * | 2001-09-28 | 2003-04-03 | Mao Yu Ming | Method and apparatus for implementing a layer 3/layer 7 firewall in an L2 device |
US20030090996A1 (en) * | 2001-11-09 | 2003-05-15 | Fujitsu Network Communications, Inc. | Focused link state advertisements |
US20040034800A1 (en) * | 2002-08-09 | 2004-02-19 | Anil Singhal | Intrusion detection system and network flow director method |
JP2005064636A (en) | 2003-08-08 | 2005-03-10 | Nippon Telegr & Teleph Corp <Ntt> | Contents distribution path creation method, consistency confirmation method of contents distribution path, estimate method of user terminal influenced by contents distribution, program for contents distribution path management apparatus, and contents distribution path management apparatus |
US20050240797A1 (en) * | 2004-01-23 | 2005-10-27 | Fredrik Orava | Restoration mechanism for network topologies |
-
2005
- 2005-03-16 WO PCT/JP2005/004697 patent/WO2006098024A1/en not_active Application Discontinuation
- 2005-03-16 JP JP2007507994A patent/JP4381448B2/en not_active Expired - Fee Related
-
2007
- 2007-09-12 US US11/854,122 patent/US7693092B2/en not_active Expired - Fee Related
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020181485A1 (en) * | 1999-05-25 | 2002-12-05 | Yang Cao | Apparatus and method for internet protocol flow ring protection switching |
US20020041586A1 (en) * | 2000-10-11 | 2002-04-11 | Hiroshi Hayashino | Communications control method |
US20030065944A1 (en) * | 2001-09-28 | 2003-04-03 | Mao Yu Ming | Method and apparatus for implementing a layer 3/layer 7 firewall in an L2 device |
US20030090996A1 (en) * | 2001-11-09 | 2003-05-15 | Fujitsu Network Communications, Inc. | Focused link state advertisements |
US20040034800A1 (en) * | 2002-08-09 | 2004-02-19 | Anil Singhal | Intrusion detection system and network flow director method |
JP2005064636A (en) | 2003-08-08 | 2005-03-10 | Nippon Telegr & Teleph Corp <Ntt> | Contents distribution path creation method, consistency confirmation method of contents distribution path, estimate method of user terminal influenced by contents distribution, program for contents distribution path management apparatus, and contents distribution path management apparatus |
US20050240797A1 (en) * | 2004-01-23 | 2005-10-27 | Fredrik Orava | Restoration mechanism for network topologies |
Non-Patent Citations (2)
Title |
---|
International Search Report dated Jun. 21, 2005, from the corresponding International Application. |
Yutaka Kikuchi, et al. "A Method of Exploring Distribution Trees of IPv6 Multicast" Information Processing Society of Japan, vol. 2002, No. 61, Jun. 28, 2002, pp. 49-54. |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100246415A1 (en) * | 2007-11-21 | 2010-09-30 | Fujitsu Limited | Network testing method and system |
US20090290500A1 (en) * | 2008-05-22 | 2009-11-26 | Fujitsu Limited | Measurement managing apparatus and communication system |
US8054755B2 (en) * | 2008-05-22 | 2011-11-08 | Fujitsu Limited | Measurement managing apparatus and communication system |
US9025494B1 (en) * | 2012-03-27 | 2015-05-05 | Infoblox Inc. | IPv6 network device discovery |
US9413623B2 (en) | 2012-04-26 | 2016-08-09 | Hewlett Packard Enterprise Development Lp | Multicast routing path check |
US9419985B1 (en) * | 2012-09-25 | 2016-08-16 | Morta Security Inc | Interrogating malware |
US20160308893A1 (en) * | 2012-09-25 | 2016-10-20 | Morta Security Inc | Interrogating malware |
US10015179B2 (en) * | 2012-09-25 | 2018-07-03 | Palo Alto Networks, Inc. | Interrogating malware |
Also Published As
Publication number | Publication date |
---|---|
JPWO2006098024A1 (en) | 2008-08-21 |
WO2006098024A1 (en) | 2006-09-21 |
JP4381448B2 (en) | 2009-12-09 |
US20080175172A1 (en) | 2008-07-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7693092B2 (en) | Multicast tree monitoring method and system in IP network | |
CN113079091B (en) | Active stream following detection method, network equipment and communication system | |
US11095546B2 (en) | Network device service quality detection method and apparatus | |
EP4102785A1 (en) | Message processing method and apparatus, and network device and storage medium | |
US10419322B2 (en) | Method of collecting information about test devices in a network | |
EP1791294B1 (en) | Diagnostic tool and method for troubleshooting multicast connectivity flow problem(s) in a layer 2 aggregation network | |
JP5300076B2 (en) | Computer system and computer system monitoring method | |
US9191290B2 (en) | Methods and devices for monitoring a data path | |
US9313116B2 (en) | Enhanced retry method | |
US8274911B2 (en) | Network monitoring system and path extracting method | |
US6608817B1 (en) | Method and apparatus for connection-oriented multiplexing and switching network analysis, management, and troubleshooting | |
EP2557731B1 (en) | Method and system for independently implementing fault location by intermediate node | |
EP2509261B1 (en) | Monitoring of a network element in a packet-switched network | |
EP2629468A1 (en) | Failure localisation in a MPLS-TP network | |
CA2977129A1 (en) | Managing traffic control in a network mitigating ddos | |
US20120134365A1 (en) | Method and network device for associated channel capability negotiation | |
JP6332544B1 (en) | Network management apparatus, network system, method, and program | |
JP4627324B2 (en) | Multicast route identification method | |
US20070115838A1 (en) | Method and system for loop-back and continue in packet-based network | |
US20090067834A1 (en) | GMPLS Fast Re-route for OADM and AUX 10Mbps Support | |
US10742539B2 (en) | Control apparatus, communication system, relay apparatus control method, and program | |
EP4280559A1 (en) | Method and apparatus for performing protection switching in segment routing (sr) network | |
US20230231792A1 (en) | System and method for micro tap instructions in packets in a telecommunications network to diagnose network issues | |
CN114598596B (en) | Method, device and system for managing tunnels | |
KR101334459B1 (en) | System and method for testing multicast distribution tree of multicast virtual private network |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: FUJITSU LIMITED, JAPAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NISHI, TETSUYA;REEL/FRAME:019816/0549 Effective date: 20070801 Owner name: FUJITSU LIMITED,JAPAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NISHI, TETSUYA;REEL/FRAME:019816/0549 Effective date: 20070801 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552) Year of fee payment: 8 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20220406 |