US20050083933A1 - Enhanced DVMRP for destination-based forwarding of multicast data - Google Patents
Enhanced DVMRP for destination-based forwarding of multicast data Download PDFInfo
- Publication number
- US20050083933A1 US20050083933A1 US10/751,153 US75115303A US2005083933A1 US 20050083933 A1 US20050083933 A1 US 20050083933A1 US 75115303 A US75115303 A US 75115303A US 2005083933 A1 US2005083933 A1 US 2005083933A1
- Authority
- US
- United States
- Prior art keywords
- router
- dvmrp
- multicast
- destination
- enhanced
- 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.)
- Granted
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/16—Multipoint routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
-
- 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
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
- H04L45/033—Topology update or discovery by updating distance vector protocols
-
- 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/12—Shortest path evaluation
- H04L45/124—Shortest path evaluation using a combination of metrics
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
- H04L65/611—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for multicast or broadcast
Definitions
- the invention generally relates to Internet Protocol (IP) multicast routing in a data network.
- IP Internet Protocol
- the invention pertains to a method by which a multicast router can prevent loops and enhance stability in a multi-access, multicast network.
- Multicast routing is the forwarding of Internet Protocol (IP) multicast packets based on the Distance Vector Multicast Routing Protocol (DVMRP) and Internet Group Management Protocol (IGMP).
- DVMRP protocol is an Internet routing protocol that provides an efficient mechanism to dynamically generate IP multicast delivery trees while preventing multicast traffic from creating duplicate packets and routing loops in a network.
- a multicast delivery tree is used by a DVMRP router to distribute a multicast stream from a multicast source to multicast clients wishing to receive the stream without flooding the network with duplicate packets and without sending unwanted traffic into a network.
- the multicast routers in the network exchange neighbor probe messages on local multicast-capable network interfaces that are configured to run DVMRP.
- a probe message sent by a given router on a particular interface includes its own IP address and the IP address of the neighbor DVMRP router, if known, from which the given router has received a probe message on the particular interface.
- two neighboring multicast routers confirm their adjacency to each other and establish a peer relationship when each receives a probe message including its own address from the neighbor router.
- the local interface on which the DVMRP router is detected is referred to as a branch interface.
- the interface is referred to as a leaf interface.
- the router After a DVMRP router has identified its neighboring DVMRP routers, the router will transmit route report messages on those branch interfaces and accept route report messages from the neighboring routers.
- the initial route report message includes information on the DVMRP router's local interfaces.
- the route report may include more detailed information about the routes reachable through the router and the associated cost metrics, e.g. a hop count.
- a router constructs a DVMRP routing table from which the router can make forwarding decisions needed for various nodes.
- the routing table in conjunction with the cost metrics can be used to determine an optimal transmission path, i.e. a best route to the router from a multicast source. If the route that has already been advertised to a neighbor router later becomes inaccessible, a flash route report is sent indicating that the route is no longer accessible.
- the route reports are periodically refreshed at a report interval.
- the router may distribute a multicast stream to other nodes in the network including other DVMRP routers.
- a DVMRP router Upon receipt of a multicast stream, a DVMRP router first performs a reverse path forwarding (RPF) check in which it determines from the DVMRP routing table whether the stream was received on the interface associated with the best route from the multicast source to the router. If the stream is not received on the associated interface, also referred to as the upstream interface, the packet is filtered to prevent a client in a multi-access network from receiving duplicate packets. If the multicast stream is received on the upstream interface, the DVMRP router is configured to propagate the multicast packets downstream to the outer edges of the network.
- RPF reverse path forwarding
- the DVMRP router Upon receipt, the DVMRP router first broadcasts the multicast stream to branch interfaces associated with dependent routers and leaf interfaces from which the router has received an IGMP join message requesting the multicast stream.
- a dependent router is an adjacent downstream router that relies on a particular upstream router for receipt of a multicast transmission. If there is more than one upstream path to the source, the DVMRP router with the lowest metric to the source network is selected as the designated forwarder, which then assumes responsibility for forwarding data toward clients in the multi-access network. If there are two or more DVMRP routers with the lowest metric, the router with the lowest IP address is selected.
- the upstream router and designated forwarder(s) are generally determined for each combination of source and destination networks listed in the router's routing table.
- a dependent DVMRP router communicates its dependency on the upstream router by sending the upstream router a route report including a cost metric equal to the original cost metric received by the upstream router plus an “infinity,” i.e., 32, value.
- the upstream DVMRP router adds the downstream router to a list of dependent routers.
- Each DVMRP router broadcasts the multicast stream to its dependent routers until the stream reaches one or more DVMRP routers at the edge of the network.
- the multicast stream is transmitted to any multicast group members, i.e. clients, registered in the local group member database.
- the edge router forwards a “prune” message to the upstream router to terminate the transmission to the particular downstream path.
- Other downstream DVMRP routers between the source and the router may forward the prune message upstream on the condition that there are no group members on the router leaf interfaces or group members accessible through a dependent router.
- distribution of the multicast stream is limited to an optimal per-source-multicast delivery tree representing the best routes from a source to all members of a multicast group.
- a new client can request the multicast stream, causing its edge router to propagate a “graft” message upstream until a DVMRP router in possession of the multicast stream adds the appropriate branch to the multicast delivery tree.
- the multicast delivery tree is periodically refreshed as prune messages expire and the cycle of broadcasting and pruning repeated.
- DVMRP routers are generally required to make multicast forwarding decisions based on both the multicast destination IP address as well as the IP address of the multicast server at the source of the multicast stream.
- the source address in particular may be used to distinguish multicast streams having the same multicast group address but originating from different servers present in the multi-access network. In some multicast routers, however, the source address is ignored and only the destination group address and the incoming interface are used as criteria for routing multicast traffic. If uncorrected, such a router has the potential to cause multicast storms by improperly generating duplicate packets, thereby consuming network bandwidth and burdening network resources. There is therefore a need for a technique allowing such a multicast router to properly interoperate with a multicast network comprising DVMRP routers.
- the invention in the preferred embodiment features an enhanced DVMRP protocol for regulating multicast traffic in a destination-based forwarding router.
- the enhanced DVMRP router transmits one or more restricted route reports, each of the restricted route reports omitting the routes associated with one or more of its branch interfaces.
- a route report may omit reference to branch interfaces to prevent branch-to-branch routing of multicast streams that may cause a destination-based forwarding router in a multi-access network to transmit duplicate packets to a group member.
- the enhanced DVMRP router transmits a conventional DVMRP route report to the first neighbor multicast router it detects. As one or more additional neighbor multicast routers are detected on new branch interfaces, the enhanced DVMRP router transmits a flash update to the neighbor multicast routers previously detected. The flash report uses an unreachable metric for the new branch interface to prevent the enhanced DVMRP router from performing branch-to-branch multicast routing from the previously-detected neighbor multicast routers to the newly-detected neighbor multicast router. The enhanced DVMRP router also transmits a restricted route report to the new neighbor multicast router to prevent branch-to-branch multicast routing from the new neighbor multicast router to the previously-detected neighbor multicast routers.
- the enhanced DVMRP protocol allows network architects to design redundancy into a network using destination-based forwarding routers.
- the DBF routers may be configured to have multiple branch interfaces while still routing data traffic to and from the leaf network to those interfaces.
- FIG. 1 is a functional block diagram of a multicast network with which the enhanced DVMRP router of the preferred embodiment may be employed;
- FIG. 2 is a per-source-broadcast tree for a first server in the multicast network implementing a standard destination-based forwarding router;
- FIG. 3 is a multicast flow diagram including a first multicast data stream from the first server and a second multicast stream from a second server, in the multicast network implementing a standard destination-based forwarding router;
- FIG. 4 is a per-source-broadcast tree for the second server in the multicast network
- FIG. 5 is the enhanced DVMRP protocol, in accordance with the preferred embodiment of the present invention.
- FIG. 6 is a per-source-broadcast tree for the first multicast server, in the multicast network including a destination-based forwarding router enabled with the enhanced DVMRP protocol of the preferred embodiment;
- FIG. 7 is a multicast flow diagram including a first multicast data stream from the first server and a second multicast stream from the second server, in the multicast network including a destination-based forwarding router enabled with the enhanced DVMRP protocol of the preferred embodiment.
- FIG. 1 Illustrated in FIG. 1 is a functional block diagram of a multicast network with which the enhanced DVMRP router of the preferred embodiment may be employed.
- the multicast network 100 preferably comprises a plurality of multicast routers including multicast router A 102 , multicast router B 103 , and multicast router D 104 , each of which is enabled with the multicast routing protocol DVMRP.
- the multicast router X 105 is a destination-based forwarding router unable to make multicast routing decisions based on the multicast source address.
- router X 105 at the edge of the network 100 is enabled with an enhanced DVMRP protocol in accordance with the preferred embodiment.
- the multicast network 100 further includes a plurality of multi-access network domains including network N 1 , N 2 , N 3 , N 4 , N 5 , N 6 , each of which may include one or more multicast group members, including clients 120 , 122 , 124 enabled with IGMP.
- the interface cost/metric for each router's 102 - 105 network connection is the same, e.g., a value of 1.
- the network N 1 and network N 2 in this example include a first multicast server S 1 110 and second multicast server S 2 112 , respectively, that generate IP packets in the form of multicast streams characterized by a multicast group address, namely 255.1.1.1.
- the multicast network 100 and constituent networks N 1 -N 6 may comprise or operably couple to one or more other communication network such as the Internet, a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), or a combination thereof.
- DBF destination-based forwarding
- router X 105 is a DBF router
- routers 102 - 104 are DVMRP routers able to perform routing using the multicast source address.
- a DBF router uses the destination group address and the incoming interface as criteria for routing multicast traffic and not the source address of the multicast server. Without the source address, a DBF router cannot distinguish a plurality of different multicast streams with the same multicast group address received on the same local interface, thereby potentially forwarding duplicate packets that may cause a multicast storm.
- the multicast routers 102 - 105 exchange probe messages, detect branch interfaces that link the routers, and establish peer relationships. Route reports are subsequently exchanged on those branch interfaces and per-source-broadcast trees compiled.
- the per-source-broadcast tree for server S 1 110 in this example is illustrated in FIG. 2 .
- the router X 105 and router B 103 typically express their dependency on router A 102 for traffic from network N 1 , i.e., server S 1 110 .
- Router D 104 also expresses its dependency on router B 103 for traffic from network N 2 .
- router D 104 expresses dependency on router B 103 because it possesses a lower cost metric (i.e., minimizing hops, for example).
- the first server 110 begins to transmit a first multicast stream having a multicast group IP address of 255.1.1.1.
- the first multicast stream is broadcast from router A 102 to router X 105 and router B 103 , and to router D 104 via router B 103 .
- router D 104 also has access to network N 6
- router X 106 is elected the designated forwarder for clients on network N 6 .
- router D 104 sends prune message to router B 103 .
- Router B 103 sends a prune message to router A 102 in the absence of any multicast group members in network N 5 or any routers dependent on router B 103 .
- router A 102 Upon receipt of the prune message, router A 102 discontinues broadcasting the first multicast stream to the branch interface associated with network N 3 . Illustrated in FIG. 3 is the resulting multicast data stream distribution through the multicast network 100 , a stream that includes the stream 301 to router A, stream 302 to router X, and stream 303 to the client C 1 120 in the network N 6 .
- the routers 102 - 105 also compile a per-source-broadcast tree for the second server S 2 112 .
- the per-source-broadcast tree for the second server S 2 112 is illustrated in FIG. 4 .
- router A 102 and router D 104 express their dependency on router B 103 for traffic originating from N 2 , i.e. server S 2 112 .
- router X 104 is accessible through either router A 102 or router D 104
- router X 105 expresses its dependency on router A 102 for multicast traffic from network N 2 because router A's IP address is lower than router D's IP address .
- the second server 112 begins transmitting a second multicast stream while the first server S 1 110 is still transmitting the first multicast stream, both streams having a multicast group IP address of 255.1.1.1.
- the packets sent from the second server S 2 112 are not the same as that sent from the first server S 1 110 .
- the second multicast stream is broadcast from router B 103 to router A 102 and router D 104 , and from router A 103 to router X 106 and network N 4 .
- network N 6 is accessible through router X 105
- router D 104 is elected the designated forwarder for clients on N 6 due to the lower cost metric through router D 106 .
- the resulting multicast data stream propagating in the multicast network 100 includes the stream 311 to router B, stream 312 to router D, and stream 313 to client C 2 122 in network N 6 .
- the multicast stream 314 sent by router B 103 to router A 102 is forwarded to client C 3 124 in network N 4 .
- the second multicast stream 315 from the second server S 2 122 is visible to the DBF router X 105 on the same branch interface attached to network N 4 with which it receives the first multicast stream 303 from the first server S 1 120 . If router X 105 were a standard DVMRP router, it would recognize that router D 104 is the designated forwarder for network N 6 and refrain from forwarding the second multicast stream 316 to network N 6 . The router X 105 , however, does not take into consideration the source IP address of server S 2 122 .
- the DBF router X 105 Since the DBF router X 105 already has a forwarding entry installed in its hardware, it forwards every multicast packet destined to the multicast group IP address 255.1.1.1 arriving on this branch interface (connected to network N 4 ) to network N 6 , including the multicast packets 316 from server S 2 122 . Consequently, client C 2 122 receives duplicate packets 316 for the first multicast stream 313 .
- the presence of duplicate packets results in routing loops that waste network bandwidth and can cause unnecessary work for other devices attached to the network.
- the DBF router of the preferred embodiment and second example below employs an enhanced DVMRP (EDVMRP) protocol in order to reliably interoperate in a DVMRP network. Illustrated in FIG. 5 is the enhancement of the EDVMRP protocol of the preferred embodiment over the standard DVMRP protocol. Consistent with standard DVMRP routers, the EDVMRP router transmits DVMRP probe messages on its local interfaces (step 500 ) and monitors (step 502 ) those interfaces for DVMRP probe messages from neighbor multicast routers that are adjacent to the EDVMRP router or accessible via a multi-access network link.
- EDVMRP enhanced DVMRP
- leaf interfaces At startup, all DVMRP-enabled interfaces of the router are considered leaf interfaces. A leaf interface will not transition to branch interface until a neighbor multicast router is discovered on the interface. If a neighbor router is discovered on an interface, the router internally marks the interface as a branch interface.
- the branch test 504 When a probe message is received and a branch interface detected, the branch test 504 is answered in the affirmative. If the newly discovered neighbor router is the first branch detected or the only branch known to the router, the previous branch test 506 is answered in the negative. On the assumption that there is only one branch interface detected, the EDVMRP router transmits (step 508 ) a conventional route report addressed to the ALL_DVMRP_ROUTERS multicast address on what is now a known branch interface. Each subsequent neighbor discovery on that same branch interface will result in a unicast route report to the particular neighbor, at least until such time that the report interval has expired and the route reports again addressed to the ALL_DVMRP_ROUTERS multicast address.
- the one or more route reports transmitted on the first branch interface comprise information on each of the EDVMRP router interfaces, which are at this point all leaf interfaces.
- the previous branch test 506 is answered in the affirmative.
- the EDVMRP router sends each previously detected neighbor multicast router (step 510 ) a DVMRP flash update to remove any local routes associated with the other DVMRP-enabled interfaces previously listed as being accessible through the newly detected branch interface and to remove any references to dependent multicast routers on the newly detected branch interface.
- removal is accomplished using a multicast transmission of an unreachability metric (32) in association with the newly detected branch.
- the EDVMRP router also sends a restricted route report (step 512 ) on the newly detected branch interface.
- the restricted route report includes a listing of the routes accessible through the EDVMRP router's leaf interfaces along with the good cost metrics associated with those routes.
- the restricted route report omits reference to one or more previously detected branches and the routes learned off of them. Future route report messages sent in accordance with the report interval also omit the references to routes reachable through any branch interface other than the branch on which the router report is being transmitted.
- the EDVMRP router continues to monitor for DVMRP Probe messages (step 502 ).
- the neighbor multicast routers do not express dependency on the EDVMRP router.
- the EDVMRP router effectively prevents other routers from establishing a dependency, thereby avoiding the need to perform branch-to-branch routing of multicast traffic through the EDVMRP router.
- the neighbor routers will continue to learn about the routes at the leaf interfaces of the EDVMRP router and will expect traffic from those networks to be routed to them.
- the EDVMRP router of the preferred embodiment may still express a dependency upon its neighbors for multicast traffic. The neighbors will continue to route traffic towards the EDVMRP router, which in turn may forward it as needed to clients on its leaf interfaces.
- the EDVMRP router in the preferred embodiment is made to behave as a DVMRP router at the edge while eliminating multicast routing loops.
- the EDVMRP router of the preferred embodiment prevents multicast looping.
- the DBF router X 105 is a EDVMRP router present in the multicast network 100 .
- the routers 102 - 105 compile the per-source-broadcast tree for each of the multicast servers.
- the per-source-broadcast tree 600 for the first multicast server S 1 110 is illustrated in FIG. 6 .
- router A 102 broadcasts the first multicast stream to router X 105 and to router B 103 .
- router D 104 recognizes itself as the designated forwarder for traffic from network N 1 to network N 6 because router X 105 failed to advertise to network N 6 and router D that it had a better metric than router D, thereby preventing EDVMRP router X 105 from becoming the designated forwarder for client C 1 120 .
- the first multicast stream is forwarded by router B 103 to router D 104 .
- router D 104 becomes the designated forwarder for client C 1 120 .
- the first multicast stream 701 sent to client C 1 120 includes a second stream 702 to router B 103 , a third stream 703 to router D 104 , and a fourth stream 704 forwarded to client C 1 120 in network N 6 .
- the second server 112 begins transmitting the second multicast stream while the first server S 1 110 is still transmitting the first multicast stream, both streams having a multicast group IP address of 255.1.1.1.
- the broadcast distribution of the second multicast stream is in accordance with the per-source-broadcast tree of illustrated in FIG. 4 .
- the multicast stream is then broadcast from router B 103 to router A 102 and router D 104 , and to router X 106 via router A 103 . Referring to the multicast flow diagram of FIG.
- the resulting second multicast stream propagating in the multicast network 100 includes the stream 711 to router B 103 , stream 712 to router D 104 , stream 713 to client C 2 122 in network N 6 , and stream 714 to router A 102 .
- router X 105 sees the stream 715 transmitted to client C 3 124 but is prevented from forwarding the stream to client C 1 120 in network N 6 because of the EDVMRP router X 105 forwarding logic that bars branch-to-branch routing.
- the EDVMRP router X 105 avoids the multicast loop that occurred in the prior example employing the conventional DBF router.
- the multicast network 100 with the EDVMRP router X 105 eliminates duplicate packets and loops, thereby making the network substantially more stable.
- the EDVMRP router is adapted to permit a network administrator to toggle between the enhanced DVMRP mode discussed above and standard DVMRP.
- the methods of the present invention are performed by an EDVMRP-enabled multicast router executing sequences of instructions retained in memory at the device or in another computer-readable medium.
- the term computer-readable medium as used herein refers to any medium that participates in providing instructions to one or more processors for execution. Such a medium may take many forms, including but not limited to, non-volatile media and volatile media. Non-volatile media includes, but are not limited to, hard disks, optical or magnetic disks, floppy disks, magnetic tape, or any other magnetic medium, CD-ROMs and other optical media, for example.
- the one or more processors and computer-readable medium may be embodied in one or more devices located in proximity to or remotely from the network administrator viewing the topology display.
Abstract
Description
- This application claims the benefit of U.S. provisional application Ser. No. 60/497,873, entitled “DVMRP Modifications to Support Destination-based Forwarding Hardware,” filed Aug. 25, 2003, the contents of which is hereby incorporated herein by reference for all purposes.
- The invention generally relates to Internet Protocol (IP) multicast routing in a data network. In particular, the invention pertains to a method by which a multicast router can prevent loops and enhance stability in a multi-access, multicast network.
- Multicast routing is the forwarding of Internet Protocol (IP) multicast packets based on the Distance Vector Multicast Routing Protocol (DVMRP) and Internet Group Management Protocol (IGMP). The DVMRP protocol is an Internet routing protocol that provides an efficient mechanism to dynamically generate IP multicast delivery trees while preventing multicast traffic from creating duplicate packets and routing loops in a network. A multicast delivery tree is used by a DVMRP router to distribute a multicast stream from a multicast source to multicast clients wishing to receive the stream without flooding the network with duplicate packets and without sending unwanted traffic into a network. Before building a multicast delivery tree, the multicast routers in the network exchange neighbor probe messages on local multicast-capable network interfaces that are configured to run DVMRP. A probe message sent by a given router on a particular interface includes its own IP address and the IP address of the neighbor DVMRP router, if known, from which the given router has received a probe message on the particular interface. In this manner, two neighboring multicast routers confirm their adjacency to each other and establish a peer relationship when each receives a probe message including its own address from the neighbor router. When a neighbor DVMRP router is detected, the local interface on which the DVMRP router is detected is referred to as a branch interface. In the absence of an adjacent DVMRP router, the interface is referred to as a leaf interface.
- After a DVMRP router has identified its neighboring DVMRP routers, the router will transmit route report messages on those branch interfaces and accept route report messages from the neighboring routers. The initial route report message includes information on the DVMRP router's local interfaces. As the router learns of the other DVMRP routers in the network, the route report may include more detailed information about the routes reachable through the router and the associated cost metrics, e.g. a hop count. With the received route reports, a router constructs a DVMRP routing table from which the router can make forwarding decisions needed for various nodes. The routing table in conjunction with the cost metrics can be used to determine an optimal transmission path, i.e. a best route to the router from a multicast source. If the route that has already been advertised to a neighbor router later becomes inaccessible, a flash route report is sent indicating that the route is no longer accessible. The route reports are periodically refreshed at a report interval.
- Even before the DVMRP router has compiled a complete routing table, the router may distribute a multicast stream to other nodes in the network including other DVMRP routers. Upon receipt of a multicast stream, a DVMRP router first performs a reverse path forwarding (RPF) check in which it determines from the DVMRP routing table whether the stream was received on the interface associated with the best route from the multicast source to the router. If the stream is not received on the associated interface, also referred to as the upstream interface, the packet is filtered to prevent a client in a multi-access network from receiving duplicate packets. If the multicast stream is received on the upstream interface, the DVMRP router is configured to propagate the multicast packets downstream to the outer edges of the network.
- Upon receipt, the DVMRP router first broadcasts the multicast stream to branch interfaces associated with dependent routers and leaf interfaces from which the router has received an IGMP join message requesting the multicast stream. A dependent router is an adjacent downstream router that relies on a particular upstream router for receipt of a multicast transmission. If there is more than one upstream path to the source, the DVMRP router with the lowest metric to the source network is selected as the designated forwarder, which then assumes responsibility for forwarding data toward clients in the multi-access network. If there are two or more DVMRP routers with the lowest metric, the router with the lowest IP address is selected. The upstream router and designated forwarder(s) are generally determined for each combination of source and destination networks listed in the router's routing table. A dependent DVMRP router communicates its dependency on the upstream router by sending the upstream router a route report including a cost metric equal to the original cost metric received by the upstream router plus an “infinity,” i.e., 32, value. Upon receipt of the report including a metric between infinity and twice infinity, i.e., 64, the upstream DVMRP router adds the downstream router to a list of dependent routers.
- Each DVMRP router broadcasts the multicast stream to its dependent routers until the stream reaches one or more DVMRP routers at the edge of the network. At the edge routers, the multicast stream is transmitted to any multicast group members, i.e. clients, registered in the local group member database. In the absence of any clients, the edge router forwards a “prune” message to the upstream router to terminate the transmission to the particular downstream path. Other downstream DVMRP routers between the source and the router may forward the prune message upstream on the condition that there are no group members on the router leaf interfaces or group members accessible through a dependent router. Upon completion of the pruning, distribution of the multicast stream is limited to an optimal per-source-multicast delivery tree representing the best routes from a source to all members of a multicast group. At any point, a new client can request the multicast stream, causing its edge router to propagate a “graft” message upstream until a DVMRP router in possession of the multicast stream adds the appropriate branch to the multicast delivery tree. The multicast delivery tree is periodically refreshed as prune messages expire and the cycle of broadcasting and pruning repeated.
- In order for one or more multicast streams to be efficiently distributed throughout the network without unnecessary duplication, DVMRP routers are generally required to make multicast forwarding decisions based on both the multicast destination IP address as well as the IP address of the multicast server at the source of the multicast stream. The source address in particular may be used to distinguish multicast streams having the same multicast group address but originating from different servers present in the multi-access network. In some multicast routers, however, the source address is ignored and only the destination group address and the incoming interface are used as criteria for routing multicast traffic. If uncorrected, such a router has the potential to cause multicast storms by improperly generating duplicate packets, thereby consuming network bandwidth and burdening network resources. There is therefore a need for a technique allowing such a multicast router to properly interoperate with a multicast network comprising DVMRP routers.
- The invention in the preferred embodiment features an enhanced DVMRP protocol for regulating multicast traffic in a destination-based forwarding router. As a plurality of neighbor multicast routers are detected and route reports exchanged, the enhanced DVMRP router transmits one or more restricted route reports, each of the restricted route reports omitting the routes associated with one or more of its branch interfaces. A route report, in particular, may omit reference to branch interfaces to prevent branch-to-branch routing of multicast streams that may cause a destination-based forwarding router in a multi-access network to transmit duplicate packets to a group member.
- In some embodiments, the enhanced DVMRP router transmits a conventional DVMRP route report to the first neighbor multicast router it detects. As one or more additional neighbor multicast routers are detected on new branch interfaces, the enhanced DVMRP router transmits a flash update to the neighbor multicast routers previously detected. The flash report uses an unreachable metric for the new branch interface to prevent the enhanced DVMRP router from performing branch-to-branch multicast routing from the previously-detected neighbor multicast routers to the newly-detected neighbor multicast router. The enhanced DVMRP router also transmits a restricted route report to the new neighbor multicast router to prevent branch-to-branch multicast routing from the new neighbor multicast router to the previously-detected neighbor multicast routers.
- In addition to preventing multicast looping, for example, the enhanced DVMRP protocol allows network architects to design redundancy into a network using destination-based forwarding routers. The DBF routers may be configured to have multiple branch interfaces while still routing data traffic to and from the leaf network to those interfaces.
- The present invention is illustrated by way of example and not limitation in the figures of the accompanying drawings, and in which:
-
FIG. 1 is a functional block diagram of a multicast network with which the enhanced DVMRP router of the preferred embodiment may be employed; -
FIG. 2 is a per-source-broadcast tree for a first server in the multicast network implementing a standard destination-based forwarding router; -
FIG. 3 is a multicast flow diagram including a first multicast data stream from the first server and a second multicast stream from a second server, in the multicast network implementing a standard destination-based forwarding router; -
FIG. 4 is a per-source-broadcast tree for the second server in the multicast network; -
FIG. 5 is the enhanced DVMRP protocol, in accordance with the preferred embodiment of the present invention; -
FIG. 6 is a per-source-broadcast tree for the first multicast server, in the multicast network including a destination-based forwarding router enabled with the enhanced DVMRP protocol of the preferred embodiment; and -
FIG. 7 is a multicast flow diagram including a first multicast data stream from the first server and a second multicast stream from the second server, in the multicast network including a destination-based forwarding router enabled with the enhanced DVMRP protocol of the preferred embodiment. - Illustrated in
FIG. 1 is a functional block diagram of a multicast network with which the enhanced DVMRP router of the preferred embodiment may be employed. Themulticast network 100 preferably comprises a plurality of multicast routers includingmulticast router A 102,multicast router B 103, andmulticast router D 104, each of which is enabled with the multicast routing protocol DVMRP. In the first example of two examples discussed below, themulticast router X 105 is a destination-based forwarding router unable to make multicast routing decisions based on the multicast source address. In a second example,router X 105 at the edge of thenetwork 100 is enabled with an enhanced DVMRP protocol in accordance with the preferred embodiment. - The
multicast network 100 further includes a plurality of multi-access network domains including network N1, N2, N3, N4, N5, N6, each of which may include one or more multicast group members, includingclients multicast server S1 110 and secondmulticast server S2 112, respectively, that generate IP packets in the form of multicast streams characterized by a multicast group address, namely 255.1.1.1. Themulticast network 100 and constituent networks N1-N6 may comprise or operably couple to one or more other communication network such as the Internet, a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), or a combination thereof. - With reference to
FIGS. 2-4 , the first example discussed immediately below demonstrates how a destination-based forwarding (DBF) router in themulticast network 100 may give rise to a multicast loop. It is assumed for purposes of this example only thatrouter X 105 is a DBF router, while routers 102-104 are DVMRP routers able to perform routing using the multicast source address. A DBF router uses the destination group address and the incoming interface as criteria for routing multicast traffic and not the source address of the multicast server. Without the source address, a DBF router cannot distinguish a plurality of different multicast streams with the same multicast group address received on the same local interface, thereby potentially forwarding duplicate packets that may cause a multicast storm. - At start-up or initialization, the multicast routers 102-105 exchange probe messages, detect branch interfaces that link the routers, and establish peer relationships. Route reports are subsequently exchanged on those branch interfaces and per-source-broadcast trees compiled. The per-source-broadcast tree for
server S1 110 in this example is illustrated inFIG. 2 . In constructing the first server per-source-broadcast tree 200, the router X 105 androuter B 103 typically express their dependency onrouter A 102 for traffic from network N1, i.e.,server S1 110.Router D 104 also expresses its dependency onrouter B 103 for traffic from network N2. Although there are paths betweenrouter D 104 andfirst server S1 110 through both router X 105 androuter B 103,router D 104 expresses dependency onrouter B 103 because it possesses a lower cost metric (i.e., minimizing hops, for example). - Assume for purposes of example that the
first server 110 begins to transmit a first multicast stream having a multicast group IP address of 255.1.1.1. In accordance with the firstserver broadcast tree 200, the first multicast stream is broadcast fromrouter A 102 to router X 105 androuter B 103, and torouter D 104 viarouter B 103. Althoughrouter D 104 also has access to network N6, router X 106 is elected the designated forwarder for clients on network N6. In the absence of any interested multicast group members,router D 104 sends prune message torouter B 103.Router B 103, in turn, sends a prune message torouter A 102 in the absence of any multicast group members in network N5 or any routers dependent onrouter B 103. Upon receipt of the prune message,router A 102 discontinues broadcasting the first multicast stream to the branch interface associated with network N3. Illustrated inFIG. 3 is the resulting multicast data stream distribution through themulticast network 100, a stream that includes thestream 301 to router A,stream 302 to router X, and stream 303 to theclient C1 120 in the network N6. - In addition to the per-source-broadcast tree for
server S1 110, the routers 102-105 also compile a per-source-broadcast tree for thesecond server S2 112. The per-source-broadcast tree for thesecond server S2 112 is illustrated inFIG. 4 . In constructing the per-source-broadcast tree 400 for thesecond server S2 112,router A 102 androuter D 104 express their dependency onrouter B 103 for traffic originating from N2, i.e.server S2 112. Althoughrouter X 104 is accessible through eitherrouter A 102 orrouter D 104,router X 105 expresses its dependency onrouter A 102 for multicast traffic from network N2 because router A's IP address is lower than router D's IP address . - Assume now for purposes of example that the
second server 112 begins transmitting a second multicast stream while thefirst server S1 110 is still transmitting the first multicast stream, both streams having a multicast group IP address of 255.1.1.1. The packets sent from thesecond server S2 112 are not the same as that sent from thefirst server S1 110. In accordance with the secondserver broadcast tree 400, the second multicast stream is broadcast fromrouter B 103 torouter A 102 androuter D 104, and fromrouter A 103 to router X 106 and network N4. Although network N6 is accessible throughrouter X 105,router D 104 is elected the designated forwarder for clients on N6 due to the lower cost metric through router D 106. Assumingclient C2 122 in network N6 has advertised an IGMP join message for the second multicast stream fromsecond server 112,router D 104 will refrain from sending prune message upstream. Similarly, an IGMP join message fromclient C3 124 in network N4 will preventrouter A 102 from sending a prune message upstream. The resulting multicast data stream propagating in themulticast network 100, illustrated inFIG. 3 , includes thestream 311 to router B,stream 312 to router D, and stream 313 toclient C2 122 in network N6. Themulticast stream 314 sent byrouter B 103 torouter A 102 is forwarded toclient C3 124 in network N4. - Unfortunately, the
second multicast stream 315 from thesecond server S2 122 is visible to theDBF router X 105 on the same branch interface attached to network N4 with which it receives thefirst multicast stream 303 from thefirst server S1 120. Ifrouter X 105 were a standard DVMRP router, it would recognize thatrouter D 104 is the designated forwarder for network N6 and refrain from forwarding thesecond multicast stream 316 to network N6. Therouter X 105, however, does not take into consideration the source IP address ofserver S2 122. Since theDBF router X 105 already has a forwarding entry installed in its hardware, it forwards every multicast packet destined to the multicast group IP address 255.1.1.1 arriving on this branch interface (connected to network N4) to network N6, including themulticast packets 316 fromserver S2 122. Consequently,client C2 122 receivesduplicate packets 316 for thefirst multicast stream 313. The presence of duplicate packets results in routing loops that waste network bandwidth and can cause unnecessary work for other devices attached to the network. - In order to avoid the problems that have plagued standard DBF routers in the first example above, the DBF router of the preferred embodiment and second example below employs an enhanced DVMRP (EDVMRP) protocol in order to reliably interoperate in a DVMRP network. Illustrated in
FIG. 5 is the enhancement of the EDVMRP protocol of the preferred embodiment over the standard DVMRP protocol. Consistent with standard DVMRP routers, the EDVMRP router transmits DVMRP probe messages on its local interfaces (step 500) and monitors (step 502) those interfaces for DVMRP probe messages from neighbor multicast routers that are adjacent to the EDVMRP router or accessible via a multi-access network link. At startup, all DVMRP-enabled interfaces of the router are considered leaf interfaces. A leaf interface will not transition to branch interface until a neighbor multicast router is discovered on the interface. If a neighbor router is discovered on an interface, the router internally marks the interface as a branch interface. - When a probe message is received and a branch interface detected, the
branch test 504 is answered in the affirmative. If the newly discovered neighbor router is the first branch detected or the only branch known to the router, theprevious branch test 506 is answered in the negative. On the assumption that there is only one branch interface detected, the EDVMRP router transmits (step 508) a conventional route report addressed to the ALL_DVMRP_ROUTERS multicast address on what is now a known branch interface. Each subsequent neighbor discovery on that same branch interface will result in a unicast route report to the particular neighbor, at least until such time that the report interval has expired and the route reports again addressed to the ALL_DVMRP_ROUTERS multicast address. The one or more route reports transmitted on the first branch interface comprise information on each of the EDVMRP router interfaces, which are at this point all leaf interfaces. - If the probe message received is detected on an interface other than the previously detected branch interface, the
previous branch test 506 is answered in the affirmative. The EDVMRP router sends each previously detected neighbor multicast router (step 510) a DVMRP flash update to remove any local routes associated with the other DVMRP-enabled interfaces previously listed as being accessible through the newly detected branch interface and to remove any references to dependent multicast routers on the newly detected branch interface. In the preferred embodiment, removal is accomplished using a multicast transmission of an unreachability metric (32) in association with the newly detected branch. - The EDVMRP router also sends a restricted route report (step 512) on the newly detected branch interface. The restricted route report includes a listing of the routes accessible through the EDVMRP router's leaf interfaces along with the good cost metrics associated with those routes. The restricted route report, however, omits reference to one or more previously detected branches and the routes learned off of them. Future route report messages sent in accordance with the report interval also omit the references to routes reachable through any branch interface other than the branch on which the router report is being transmitted. The EDVMRP router continues to monitor for DVMRP Probe messages (step 502).
- Since the routes associated with branch interfaces are no longer included in the outgoing route reports from the EDVMRP router, the neighbor multicast routers do not express dependency on the EDVMRP router. In the absence of the information of the branch interfaces represented in the multicast routing tables of the neighbor multicast routers, the EDVMRP router effectively prevents other routers from establishing a dependency, thereby avoiding the need to perform branch-to-branch routing of multicast traffic through the EDVMRP router. The neighbor routers will continue to learn about the routes at the leaf interfaces of the EDVMRP router and will expect traffic from those networks to be routed to them. One skilled in the art will recognize that the EDVMRP router of the preferred embodiment may still express a dependency upon its neighbors for multicast traffic. The neighbors will continue to route traffic towards the EDVMRP router, which in turn may forward it as needed to clients on its leaf interfaces. The EDVMRP router in the preferred embodiment is made to behave as a DVMRP router at the edge while eliminating multicast routing loops.
- The manner by which the EDVMRP router of the preferred embodiment prevents multicast looping is illustrated by way of example. Assume for purposes of this example that the
DBF router X 105 is a EDVMRP router present in themulticast network 100. When the routers 102-105 are initialized and the route reports and restricted route reports are exchanged, the routers 102-105 compile the per-source-broadcast tree for each of the multicast servers. The per-source-broadcast tree 600 for the firstmulticast server S1 110 is illustrated inFIG. 6 . As before,router A 102 broadcasts the first multicast stream to router X 105 and torouter B 103. Unlike the previous example, however,router D 104 recognizes itself as the designated forwarder for traffic from network N1 to network N6 becauserouter X 105 failed to advertise to network N6 and router D that it had a better metric than router D, thereby preventingEDVMRP router X 105 from becoming the designated forwarder forclient C1 120. Instead, the first multicast stream is forwarded byrouter B 103 torouter D 104. Believing that traffic from network N1 is inaccessible throughrouter X 105,router D 104 becomes the designated forwarder forclient C1 120. As illustrated in the multicast flow diagram ofFIG. 7 , thefirst multicast stream 701 sent toclient C1 120 includes asecond stream 702 torouter B 103, athird stream 703 torouter D 104, and afourth stream 704 forwarded toclient C1 120 in network N6. - Assume now for purposes of this example that the
second server 112 begins transmitting the second multicast stream while thefirst server S1 110 is still transmitting the first multicast stream, both streams having a multicast group IP address of 255.1.1.1. As described above, the broadcast distribution of the second multicast stream is in accordance with the per-source-broadcast tree of illustrated inFIG. 4 . The multicast stream is then broadcast fromrouter B 103 torouter A 102 androuter D 104, and to router X 106 viarouter A 103. Referring to the multicast flow diagram ofFIG. 7 , the resulting second multicast stream propagating in themulticast network 100 includes thestream 711 torouter B 103,stream 712 torouter D 104,stream 713 toclient C2 122 in network N6, and stream 714 torouter A 102. As before,router X 105 sees thestream 715 transmitted toclient C3 124 but is prevented from forwarding the stream toclient C1 120 in network N6 because of theEDVMRP router X 105 forwarding logic that bars branch-to-branch routing. By barring branch-to-branch multicast routing, theEDVMRP router X 105 avoids the multicast loop that occurred in the prior example employing the conventional DBF router. As a consequence, themulticast network 100 with theEDVMRP router X 105 eliminates duplicate packets and loops, thereby making the network substantially more stable. - In a second embodiment of the present invention, the EDVMRP router is adapted to permit a network administrator to toggle between the enhanced DVMRP mode discussed above and standard DVMRP.
- One skilled in the art will also recognize that one or more steps practiced by the apparatus, module, or method of the present invention may be implemented in software running in connection with a programmable microprocessor; implemented in hardware utilizing either a combination of microprocessors or other specially designed application specific integrated circuits and programmable logic devices; or various combinations thereof. Thus, embodiments of the invention are not limited to any specific combination of hardware circuitry and software.
- In some embodiments, the methods of the present invention are performed by an EDVMRP-enabled multicast router executing sequences of instructions retained in memory at the device or in another computer-readable medium. The term computer-readable medium as used herein refers to any medium that participates in providing instructions to one or more processors for execution. Such a medium may take many forms, including but not limited to, non-volatile media and volatile media. Non-volatile media includes, but are not limited to, hard disks, optical or magnetic disks, floppy disks, magnetic tape, or any other magnetic medium, CD-ROMs and other optical media, for example. The one or more processors and computer-readable medium may be embodied in one or more devices located in proximity to or remotely from the network administrator viewing the topology display.
- Although the description above contains many specifications, these should not be construed as limiting the scope of the invention but as merely providing illustrations of some of the presently preferred embodiments of this invention.
- Therefore, the invention has been disclosed by way of example and not limitation, and reference should be made to the following claims to determine the scope of the present invention.
Claims (15)
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/751,153 US7522596B2 (en) | 2003-08-25 | 2003-12-31 | Enhanced DVMRP for destination-based forwarding of multicast data |
EP04019899A EP1511244A3 (en) | 2003-08-25 | 2004-08-23 | Hardware abstraction interfacing system and method |
CNA2004100571413A CN1592305A (en) | 2003-08-25 | 2004-08-24 | Enhanced DVMRP for data transmitting |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US49787303P | 2003-08-25 | 2003-08-25 | |
US10/751,153 US7522596B2 (en) | 2003-08-25 | 2003-12-31 | Enhanced DVMRP for destination-based forwarding of multicast data |
Publications (2)
Publication Number | Publication Date |
---|---|
US20050083933A1 true US20050083933A1 (en) | 2005-04-21 |
US7522596B2 US7522596B2 (en) | 2009-04-21 |
Family
ID=34108118
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/751,153 Expired - Fee Related US7522596B2 (en) | 2003-08-25 | 2003-12-31 | Enhanced DVMRP for destination-based forwarding of multicast data |
Country Status (3)
Country | Link |
---|---|
US (1) | US7522596B2 (en) |
EP (1) | EP1511244A3 (en) |
CN (1) | CN1592305A (en) |
Cited By (52)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050198371A1 (en) * | 2004-02-19 | 2005-09-08 | Smith Michael R. | Interface bundles in virtual network devices |
US20050243826A1 (en) * | 2004-04-28 | 2005-11-03 | Smith Michael R | Intelligent adjunct network device |
US20050259649A1 (en) * | 2004-05-19 | 2005-11-24 | Smith Michael R | System and method for implementing multiple spanning trees per network |
US20050259646A1 (en) * | 2004-05-19 | 2005-11-24 | Smith Michael R | Virtual network device clusters |
US20060023718A1 (en) * | 2004-07-08 | 2006-02-02 | Christophe Joly | Network device architecture for centralized packet processing |
US20060039384A1 (en) * | 2004-08-17 | 2006-02-23 | Sitaram Dontu | System and method for preventing erroneous link aggregation due to component relocation |
US20080146230A1 (en) * | 2006-12-18 | 2008-06-19 | Cisco Technology, Inc. | Fast handoff for wireless devices in a wired-wireless network |
US20090086641A1 (en) * | 2004-06-30 | 2009-04-02 | Faisal Mushtaq | Method and Apparatus for Detecting Support for A Protocol Defining Supplemental Headers |
US7839843B2 (en) | 2003-09-18 | 2010-11-23 | Cisco Technology, Inc. | Distributed forwarding in virtual network devices |
US20110058499A1 (en) * | 2009-01-30 | 2011-03-10 | Nec Laboratories America Inc | Method for inferring physical network topology from end-to-end measurement |
US7944846B1 (en) * | 2005-08-18 | 2011-05-17 | Avaya Inc. | DVMRP border router for reverse path forwarding validation with external sources |
US8208370B1 (en) | 2004-03-31 | 2012-06-26 | Cisco Technology, Inc. | Method and system for fast link failover |
WO2012112162A1 (en) * | 2011-02-18 | 2012-08-23 | Hewlett-Packard Development Company, L. P. | Methods for controlling elections in a multicast network |
US8526427B1 (en) | 2003-10-21 | 2013-09-03 | Cisco Technology, Inc. | Port-based loadsharing for a satellite switch |
US8611252B2 (en) * | 2006-06-09 | 2013-12-17 | Cisco Technology, Inc. | Method of routing multicast traffic |
US8625603B1 (en) * | 2006-05-16 | 2014-01-07 | Cisco Technology, Inc. | Systems and methods for multicast switching in a private VLAN |
US20140219079A1 (en) * | 2013-02-04 | 2014-08-07 | Cisco Technology, Inc. | Provisioning of a new node joining an existing cluster in a data center environment |
US8861520B1 (en) * | 2011-02-24 | 2014-10-14 | Directpacket Research, Inc. | Packet cloning for enhanced delivery of communication from a source device to one or more destination devices |
US20150030023A1 (en) * | 2013-07-25 | 2015-01-29 | Board Of Trustees, Southern Illinois University | Multicast routing protocol for computer networks |
US8995275B1 (en) * | 2012-07-31 | 2015-03-31 | Rockwell Collins, Inc. | Methods and systems for network traffic routing |
US9286047B1 (en) | 2013-02-13 | 2016-03-15 | Cisco Technology, Inc. | Deployment and upgrade of network devices in a network environment |
US20170346721A1 (en) * | 2016-05-31 | 2017-11-30 | Cisco Technology, Inc. | Bidirectional multicasting over virtual port channel |
US10116493B2 (en) | 2014-11-21 | 2018-10-30 | Cisco Technology, Inc. | Recovering from virtual port channel peer failure |
US10116530B2 (en) | 2015-06-05 | 2018-10-30 | Cisco Technology, Inc. | Technologies for determining sensor deployment characteristics |
US10142163B2 (en) | 2016-03-07 | 2018-11-27 | Cisco Technology, Inc | BFD over VxLAN on vPC uplinks |
US10142353B2 (en) | 2015-06-05 | 2018-11-27 | Cisco Technology, Inc. | System for monitoring and managing datacenters |
US10193750B2 (en) | 2016-09-07 | 2019-01-29 | Cisco Technology, Inc. | Managing virtual port channel switch peers from software-defined network controller |
US10225179B2 (en) | 2013-11-05 | 2019-03-05 | Cisco Technology, Inc. | Virtual port channel bounce in overlay network |
US10250446B2 (en) | 2017-03-27 | 2019-04-02 | Cisco Technology, Inc. | Distributed policy store |
US10289438B2 (en) | 2016-06-16 | 2019-05-14 | Cisco Technology, Inc. | Techniques for coordination of application components deployed on distributed virtual machines |
US10374904B2 (en) | 2015-05-15 | 2019-08-06 | Cisco Technology, Inc. | Diagnostic network visualization |
US10523512B2 (en) | 2017-03-24 | 2019-12-31 | Cisco Technology, Inc. | Network agent for generating platform specific network policies |
US10523541B2 (en) | 2017-10-25 | 2019-12-31 | Cisco Technology, Inc. | Federated network and application data analytics platform |
US10547509B2 (en) | 2017-06-19 | 2020-01-28 | Cisco Technology, Inc. | Validation of a virtual port channel (VPC) endpoint in the network fabric |
US10554501B2 (en) | 2017-10-23 | 2020-02-04 | Cisco Technology, Inc. | Network migration assistant |
US10574575B2 (en) | 2018-01-25 | 2020-02-25 | Cisco Technology, Inc. | Network flow stitching using middle box flow stitching |
US10594560B2 (en) | 2017-03-27 | 2020-03-17 | Cisco Technology, Inc. | Intent driven network policy platform |
US10594542B2 (en) | 2017-10-27 | 2020-03-17 | Cisco Technology, Inc. | System and method for network root cause analysis |
US10680887B2 (en) | 2017-07-21 | 2020-06-09 | Cisco Technology, Inc. | Remote device status audit and recovery |
US10708152B2 (en) | 2017-03-23 | 2020-07-07 | Cisco Technology, Inc. | Predicting application and network performance |
US10708183B2 (en) | 2016-07-21 | 2020-07-07 | Cisco Technology, Inc. | System and method of providing segment routing as a service |
US10764141B2 (en) | 2017-03-27 | 2020-09-01 | Cisco Technology, Inc. | Network agent for reporting to a network policy system |
US10797970B2 (en) | 2015-06-05 | 2020-10-06 | Cisco Technology, Inc. | Interactive hierarchical network chord diagram for application dependency mapping |
US10798015B2 (en) | 2018-01-25 | 2020-10-06 | Cisco Technology, Inc. | Discovery of middleboxes using traffic flow stitching |
US10826803B2 (en) | 2018-01-25 | 2020-11-03 | Cisco Technology, Inc. | Mechanism for facilitating efficient policy updates |
US10873794B2 (en) | 2017-03-28 | 2020-12-22 | Cisco Technology, Inc. | Flowlet resolution for application performance monitoring and management |
US10972388B2 (en) | 2016-11-22 | 2021-04-06 | Cisco Technology, Inc. | Federated microburst detection |
US10999149B2 (en) | 2018-01-25 | 2021-05-04 | Cisco Technology, Inc. | Automatic configuration discovery based on traffic flow data |
US11128700B2 (en) | 2018-01-26 | 2021-09-21 | Cisco Technology, Inc. | Load balancing configuration based on traffic flow telemetry |
US11233821B2 (en) | 2018-01-04 | 2022-01-25 | Cisco Technology, Inc. | Network intrusion counter-intelligence |
US11411799B2 (en) * | 2017-07-21 | 2022-08-09 | Cisco Technology, Inc. | Scalable statistics and analytics mechanisms in cloud networking |
US11509501B2 (en) | 2016-07-20 | 2022-11-22 | Cisco Technology, Inc. | Automatic port verification and policy application for rogue devices |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101227310B (en) * | 2008-01-29 | 2011-04-20 | 华为技术有限公司 | System, apparatus and method for obtaining multicast topology information |
CN102244582B (en) * | 2010-05-13 | 2013-12-25 | 杭州华三通信技术有限公司 | Multicast transmission method and system thereof in BIDIR-PIM network |
EP2671349A1 (en) * | 2011-01-31 | 2013-12-11 | Hewlett-Packard Development Company, L.P. | Methods for handling conflicts in a multicast routing election |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5517494A (en) * | 1994-09-30 | 1996-05-14 | Apple Computer, Inc. | Method and system of multicast routing for groups with a single transmitter |
US5999530A (en) * | 1995-10-12 | 1999-12-07 | 3Com Corporation | Method and apparatus for transparent intermediate system based filtering on a LAN of multicast packets |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6331983B1 (en) | 1997-05-06 | 2001-12-18 | Enterasys Networks, Inc. | Multicast switching |
-
2003
- 2003-12-31 US US10/751,153 patent/US7522596B2/en not_active Expired - Fee Related
-
2004
- 2004-08-23 EP EP04019899A patent/EP1511244A3/en not_active Withdrawn
- 2004-08-24 CN CNA2004100571413A patent/CN1592305A/en active Pending
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5517494A (en) * | 1994-09-30 | 1996-05-14 | Apple Computer, Inc. | Method and system of multicast routing for groups with a single transmitter |
US5999530A (en) * | 1995-10-12 | 1999-12-07 | 3Com Corporation | Method and apparatus for transparent intermediate system based filtering on a LAN of multicast packets |
Cited By (151)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7839843B2 (en) | 2003-09-18 | 2010-11-23 | Cisco Technology, Inc. | Distributed forwarding in virtual network devices |
US8526427B1 (en) | 2003-10-21 | 2013-09-03 | Cisco Technology, Inc. | Port-based loadsharing for a satellite switch |
US20150195218A1 (en) * | 2004-02-19 | 2015-07-09 | Cisco Technology, Inc. | Interface Bundles In Virtual Network Devices |
US20050198371A1 (en) * | 2004-02-19 | 2005-09-08 | Smith Michael R. | Interface bundles in virtual network devices |
US10069765B2 (en) * | 2004-02-19 | 2018-09-04 | Cisco Technology, Inc. | Interface bundles in virtual network devices |
US8990430B2 (en) * | 2004-02-19 | 2015-03-24 | Cisco Technology, Inc. | Interface bundles in virtual network devices |
US8208370B1 (en) | 2004-03-31 | 2012-06-26 | Cisco Technology, Inc. | Method and system for fast link failover |
US8755382B2 (en) | 2004-04-28 | 2014-06-17 | Cisco Technology, Inc. | Intelligent adjunct network device |
US9621419B2 (en) | 2004-04-28 | 2017-04-11 | Cisco Technology, Inc. | Determining when to switch to a standby intelligent adjunct network device |
US7889733B2 (en) | 2004-04-28 | 2011-02-15 | Cisco Technology, Inc. | Intelligent adjunct network device |
US20050243826A1 (en) * | 2004-04-28 | 2005-11-03 | Smith Michael R | Intelligent adjunct network device |
US20110134923A1 (en) * | 2004-04-28 | 2011-06-09 | Smith Michael R | Intelligent Adjunct Network Device |
US7706364B2 (en) * | 2004-05-19 | 2010-04-27 | Cisco Technology, Inc. | Virtual network device clusters |
US7710957B2 (en) | 2004-05-19 | 2010-05-04 | Cisco Technology, Inc. | System and method for implementing multiple spanning trees per network |
US20050259646A1 (en) * | 2004-05-19 | 2005-11-24 | Smith Michael R | Virtual network device clusters |
US20050259649A1 (en) * | 2004-05-19 | 2005-11-24 | Smith Michael R | System and method for implementing multiple spanning trees per network |
US20090086641A1 (en) * | 2004-06-30 | 2009-04-02 | Faisal Mushtaq | Method and Apparatus for Detecting Support for A Protocol Defining Supplemental Headers |
US8059652B2 (en) | 2004-06-30 | 2011-11-15 | Cisco Technology, Inc. | Method and apparatus for detecting support for a protocol defining supplemental headers |
US7822025B1 (en) | 2004-07-08 | 2010-10-26 | Cisco Technology, Inc. | Network device architecture for centralized packet processing |
US8929207B1 (en) | 2004-07-08 | 2015-01-06 | Cisco Technology, Inc. | Network device architecture for centralized packet processing |
US7808983B2 (en) | 2004-07-08 | 2010-10-05 | Cisco Technology, Inc. | Network device architecture for centralized packet processing |
US20060023718A1 (en) * | 2004-07-08 | 2006-02-02 | Christophe Joly | Network device architecture for centralized packet processing |
US8730976B2 (en) | 2004-08-17 | 2014-05-20 | Cisco Technology, Inc. | System and method for preventing erroneous link aggregation due to component relocation |
US20060039384A1 (en) * | 2004-08-17 | 2006-02-23 | Sitaram Dontu | System and method for preventing erroneous link aggregation due to component relocation |
US7944846B1 (en) * | 2005-08-18 | 2011-05-17 | Avaya Inc. | DVMRP border router for reverse path forwarding validation with external sources |
US8625603B1 (en) * | 2006-05-16 | 2014-01-07 | Cisco Technology, Inc. | Systems and methods for multicast switching in a private VLAN |
US9059943B2 (en) | 2006-06-09 | 2015-06-16 | Cisco Technology, Inc. | Method of routing multicast traffic |
US9338079B2 (en) | 2006-06-09 | 2016-05-10 | Cisco Technology, Inc. | Method of routing multicast traffic |
US8611252B2 (en) * | 2006-06-09 | 2013-12-17 | Cisco Technology, Inc. | Method of routing multicast traffic |
US8532070B2 (en) | 2006-12-18 | 2013-09-10 | Cisco Technology, Inc. | Fast handoff for wireless devices in a wired-wireless network |
US20080146230A1 (en) * | 2006-12-18 | 2008-06-19 | Cisco Technology, Inc. | Fast handoff for wireless devices in a wired-wireless network |
WO2008076859A3 (en) * | 2006-12-18 | 2008-09-18 | Cisco Tech Inc | Fast handoff for wireless devices in a wired-wireless network |
US20110058499A1 (en) * | 2009-01-30 | 2011-03-10 | Nec Laboratories America Inc | Method for inferring physical network topology from end-to-end measurement |
US8264988B2 (en) * | 2009-01-30 | 2012-09-11 | Nec Laboratories America, Inc. | Method for inferring physical network topology from end-to-end measurement |
US9031070B2 (en) | 2011-02-18 | 2015-05-12 | Hewlett-Packard Development Company, L.P. | Methods for controlling elections in a multicast network |
WO2012112162A1 (en) * | 2011-02-18 | 2012-08-23 | Hewlett-Packard Development Company, L. P. | Methods for controlling elections in a multicast network |
US8861520B1 (en) * | 2011-02-24 | 2014-10-14 | Directpacket Research, Inc. | Packet cloning for enhanced delivery of communication from a source device to one or more destination devices |
US8995275B1 (en) * | 2012-07-31 | 2015-03-31 | Rockwell Collins, Inc. | Methods and systems for network traffic routing |
US9130836B2 (en) * | 2013-02-04 | 2015-09-08 | Cisco Technology, Inc. | Provisoning of a new node joining an existing cluster in a data center environment |
US20140219079A1 (en) * | 2013-02-04 | 2014-08-07 | Cisco Technology, Inc. | Provisioning of a new node joining an existing cluster in a data center environment |
US9286047B1 (en) | 2013-02-13 | 2016-03-15 | Cisco Technology, Inc. | Deployment and upgrade of network devices in a network environment |
US10177977B1 (en) | 2013-02-13 | 2019-01-08 | Cisco Technology, Inc. | Deployment and upgrade of network devices in a network environment |
US9461832B2 (en) * | 2013-07-25 | 2016-10-04 | Board Of Trustees, Southern Illinois University | Multicast routing protocol for computer networks |
US20150030023A1 (en) * | 2013-07-25 | 2015-01-29 | Board Of Trustees, Southern Illinois University | Multicast routing protocol for computer networks |
US11411770B2 (en) | 2013-11-05 | 2022-08-09 | Cisco Technology, Inc. | Virtual port channel bounce in overlay network |
US10225179B2 (en) | 2013-11-05 | 2019-03-05 | Cisco Technology, Inc. | Virtual port channel bounce in overlay network |
US10116493B2 (en) | 2014-11-21 | 2018-10-30 | Cisco Technology, Inc. | Recovering from virtual port channel peer failure |
US10819563B2 (en) | 2014-11-21 | 2020-10-27 | Cisco Technology, Inc. | Recovering from virtual port channel peer failure |
US10374904B2 (en) | 2015-05-15 | 2019-08-06 | Cisco Technology, Inc. | Diagnostic network visualization |
US11128552B2 (en) | 2015-06-05 | 2021-09-21 | Cisco Technology, Inc. | Round trip time (RTT) measurement based upon sequence number |
US11153184B2 (en) | 2015-06-05 | 2021-10-19 | Cisco Technology, Inc. | Technologies for annotating process and user information for network flows |
US10142353B2 (en) | 2015-06-05 | 2018-11-27 | Cisco Technology, Inc. | System for monitoring and managing datacenters |
US10177998B2 (en) | 2015-06-05 | 2019-01-08 | Cisco Technology, Inc. | Augmenting flow data for improved network monitoring and management |
US10181987B2 (en) | 2015-06-05 | 2019-01-15 | Cisco Technology, Inc. | High availability of collectors of traffic reported by network sensors |
US11522775B2 (en) | 2015-06-05 | 2022-12-06 | Cisco Technology, Inc. | Application monitoring prioritization |
US11516098B2 (en) | 2015-06-05 | 2022-11-29 | Cisco Technology, Inc. | Round trip time (RTT) measurement based upon sequence number |
US10230597B2 (en) | 2015-06-05 | 2019-03-12 | Cisco Technology, Inc. | Optimizations for application dependency mapping |
US10243817B2 (en) | 2015-06-05 | 2019-03-26 | Cisco Technology, Inc. | System and method of assigning reputation scores to hosts |
US11502922B2 (en) | 2015-06-05 | 2022-11-15 | Cisco Technology, Inc. | Technologies for managing compromised sensors in virtualized environments |
US11496377B2 (en) | 2015-06-05 | 2022-11-08 | Cisco Technology, Inc. | Anomaly detection through header field entropy |
US10305757B2 (en) | 2015-06-05 | 2019-05-28 | Cisco Technology, Inc. | Determining a reputation of a network entity |
US10320630B2 (en) | 2015-06-05 | 2019-06-11 | Cisco Technology, Inc. | Hierarchichal sharding of flows from sensors to collectors |
US10326673B2 (en) | 2015-06-05 | 2019-06-18 | Cisco Technology, Inc. | Techniques for determining network topologies |
US10326672B2 (en) | 2015-06-05 | 2019-06-18 | Cisco Technology, Inc. | MDL-based clustering for application dependency mapping |
US11477097B2 (en) | 2015-06-05 | 2022-10-18 | Cisco Technology, Inc. | Hierarchichal sharding of flows from sensors to collectors |
US10129117B2 (en) | 2015-06-05 | 2018-11-13 | Cisco Technology, Inc. | Conditional policies |
US10439904B2 (en) | 2015-06-05 | 2019-10-08 | Cisco Technology, Inc. | System and method of determining malicious processes |
US10454793B2 (en) | 2015-06-05 | 2019-10-22 | Cisco Technology, Inc. | System and method of detecting whether a source of a packet flow transmits packets which bypass an operating system stack |
US10505828B2 (en) | 2015-06-05 | 2019-12-10 | Cisco Technology, Inc. | Technologies for managing compromised sensors in virtualized environments |
US10516585B2 (en) | 2015-06-05 | 2019-12-24 | Cisco Technology, Inc. | System and method for network information mapping and displaying |
US10516586B2 (en) | 2015-06-05 | 2019-12-24 | Cisco Technology, Inc. | Identifying bogon address spaces |
US11601349B2 (en) | 2015-06-05 | 2023-03-07 | Cisco Technology, Inc. | System and method of detecting hidden processes by analyzing packet flows |
US11968103B2 (en) | 2015-06-05 | 2024-04-23 | Cisco Technology, Inc. | Policy utilization analysis |
US10536357B2 (en) | 2015-06-05 | 2020-01-14 | Cisco Technology, Inc. | Late data detection in data center |
US10171319B2 (en) | 2015-06-05 | 2019-01-01 | Cisco Technology, Inc. | Technologies for annotating process and user information for network flows |
US11968102B2 (en) | 2015-06-05 | 2024-04-23 | Cisco Technology, Inc. | System and method of detecting packet loss in a distributed sensor-collector architecture |
US10567247B2 (en) | 2015-06-05 | 2020-02-18 | Cisco Technology, Inc. | Intra-datacenter attack detection |
US11936663B2 (en) | 2015-06-05 | 2024-03-19 | Cisco Technology, Inc. | System for monitoring and managing datacenters |
US11431592B2 (en) | 2015-06-05 | 2022-08-30 | Cisco Technology, Inc. | System and method of detecting whether a source of a packet flow transmits packets which bypass an operating system stack |
US11924073B2 (en) | 2015-06-05 | 2024-03-05 | Cisco Technology, Inc. | System and method of assigning reputation scores to hosts |
US10623283B2 (en) | 2015-06-05 | 2020-04-14 | Cisco Technology, Inc. | Anomaly detection through header field entropy |
US10623282B2 (en) | 2015-06-05 | 2020-04-14 | Cisco Technology, Inc. | System and method of detecting hidden processes by analyzing packet flows |
US10623284B2 (en) | 2015-06-05 | 2020-04-14 | Cisco Technology, Inc. | Determining a reputation of a network entity |
US10659324B2 (en) | 2015-06-05 | 2020-05-19 | Cisco Technology, Inc. | Application monitoring prioritization |
US11924072B2 (en) | 2015-06-05 | 2024-03-05 | Cisco Technology, Inc. | Technologies for annotating process and user information for network flows |
US10686804B2 (en) | 2015-06-05 | 2020-06-16 | Cisco Technology, Inc. | System for monitoring and managing datacenters |
US10693749B2 (en) | 2015-06-05 | 2020-06-23 | Cisco Technology, Inc. | Synthetic data for determining health of a network security system |
US11637762B2 (en) | 2015-06-05 | 2023-04-25 | Cisco Technology, Inc. | MDL-based clustering for dependency mapping |
US11405291B2 (en) | 2015-06-05 | 2022-08-02 | Cisco Technology, Inc. | Generate a communication graph using an application dependency mapping (ADM) pipeline |
US10728119B2 (en) | 2015-06-05 | 2020-07-28 | Cisco Technology, Inc. | Cluster discovery via multi-domain fusion for application dependency mapping |
US10735283B2 (en) | 2015-06-05 | 2020-08-04 | Cisco Technology, Inc. | Unique ID generation for sensors |
US10742529B2 (en) | 2015-06-05 | 2020-08-11 | Cisco Technology, Inc. | Hierarchichal sharding of flows from sensors to collectors |
US11368378B2 (en) | 2015-06-05 | 2022-06-21 | Cisco Technology, Inc. | Identifying bogon address spaces |
US11252058B2 (en) | 2015-06-05 | 2022-02-15 | Cisco Technology, Inc. | System and method for user optimized application dependency mapping |
US10797970B2 (en) | 2015-06-05 | 2020-10-06 | Cisco Technology, Inc. | Interactive hierarchical network chord diagram for application dependency mapping |
US11902120B2 (en) | 2015-06-05 | 2024-02-13 | Cisco Technology, Inc. | Synthetic data for determining health of a network security system |
US10116531B2 (en) | 2015-06-05 | 2018-10-30 | Cisco Technology, Inc | Round trip time (RTT) measurement based upon sequence number |
US11902122B2 (en) | 2015-06-05 | 2024-02-13 | Cisco Technology, Inc. | Application monitoring prioritization |
US10862776B2 (en) | 2015-06-05 | 2020-12-08 | Cisco Technology, Inc. | System and method of spoof detection |
US11252060B2 (en) | 2015-06-05 | 2022-02-15 | Cisco Technology, Inc. | Data center traffic analytics synchronization |
US11902121B2 (en) | 2015-06-05 | 2024-02-13 | Cisco Technology, Inc. | System and method of detecting whether a source of a packet flow transmits packets which bypass an operating system stack |
US10904116B2 (en) | 2015-06-05 | 2021-01-26 | Cisco Technology, Inc. | Policy utilization analysis |
US11894996B2 (en) | 2015-06-05 | 2024-02-06 | Cisco Technology, Inc. | Technologies for annotating process and user information for network flows |
US10917319B2 (en) | 2015-06-05 | 2021-02-09 | Cisco Technology, Inc. | MDL-based clustering for dependency mapping |
US11528283B2 (en) | 2015-06-05 | 2022-12-13 | Cisco Technology, Inc. | System for monitoring and managing datacenters |
US10979322B2 (en) | 2015-06-05 | 2021-04-13 | Cisco Technology, Inc. | Techniques for determining network anomalies in data center networks |
US10116530B2 (en) | 2015-06-05 | 2018-10-30 | Cisco Technology, Inc. | Technologies for determining sensor deployment characteristics |
US11700190B2 (en) | 2015-06-05 | 2023-07-11 | Cisco Technology, Inc. | Technologies for annotating process and user information for network flows |
US11695659B2 (en) | 2015-06-05 | 2023-07-04 | Cisco Technology, Inc. | Unique ID generation for sensors |
US11102093B2 (en) | 2015-06-05 | 2021-08-24 | Cisco Technology, Inc. | System and method of assigning reputation scores to hosts |
US11121948B2 (en) | 2015-06-05 | 2021-09-14 | Cisco Technology, Inc. | Auto update of sensor configuration |
US10142163B2 (en) | 2016-03-07 | 2018-11-27 | Cisco Technology, Inc | BFD over VxLAN on vPC uplinks |
US20170346721A1 (en) * | 2016-05-31 | 2017-11-30 | Cisco Technology, Inc. | Bidirectional multicasting over virtual port channel |
US10333828B2 (en) * | 2016-05-31 | 2019-06-25 | Cisco Technology, Inc. | Bidirectional multicasting over virtual port channel |
US10289438B2 (en) | 2016-06-16 | 2019-05-14 | Cisco Technology, Inc. | Techniques for coordination of application components deployed on distributed virtual machines |
US11509501B2 (en) | 2016-07-20 | 2022-11-22 | Cisco Technology, Inc. | Automatic port verification and policy application for rogue devices |
US11283712B2 (en) | 2016-07-21 | 2022-03-22 | Cisco Technology, Inc. | System and method of providing segment routing as a service |
US10708183B2 (en) | 2016-07-21 | 2020-07-07 | Cisco Technology, Inc. | System and method of providing segment routing as a service |
US10193750B2 (en) | 2016-09-07 | 2019-01-29 | Cisco Technology, Inc. | Managing virtual port channel switch peers from software-defined network controller |
US10749742B2 (en) | 2016-09-07 | 2020-08-18 | Cisco Technology, Inc. | Managing virtual port channel switch peers from software-defined network controller |
US10972388B2 (en) | 2016-11-22 | 2021-04-06 | Cisco Technology, Inc. | Federated microburst detection |
US11088929B2 (en) | 2017-03-23 | 2021-08-10 | Cisco Technology, Inc. | Predicting application and network performance |
US10708152B2 (en) | 2017-03-23 | 2020-07-07 | Cisco Technology, Inc. | Predicting application and network performance |
US10523512B2 (en) | 2017-03-24 | 2019-12-31 | Cisco Technology, Inc. | Network agent for generating platform specific network policies |
US11252038B2 (en) | 2017-03-24 | 2022-02-15 | Cisco Technology, Inc. | Network agent for generating platform specific network policies |
US10594560B2 (en) | 2017-03-27 | 2020-03-17 | Cisco Technology, Inc. | Intent driven network policy platform |
US10764141B2 (en) | 2017-03-27 | 2020-09-01 | Cisco Technology, Inc. | Network agent for reporting to a network policy system |
US10250446B2 (en) | 2017-03-27 | 2019-04-02 | Cisco Technology, Inc. | Distributed policy store |
US11509535B2 (en) | 2017-03-27 | 2022-11-22 | Cisco Technology, Inc. | Network agent for reporting to a network policy system |
US11146454B2 (en) | 2017-03-27 | 2021-10-12 | Cisco Technology, Inc. | Intent driven network policy platform |
US10873794B2 (en) | 2017-03-28 | 2020-12-22 | Cisco Technology, Inc. | Flowlet resolution for application performance monitoring and management |
US11683618B2 (en) | 2017-03-28 | 2023-06-20 | Cisco Technology, Inc. | Application performance monitoring and management platform with anomalous flowlet resolution |
US11202132B2 (en) | 2017-03-28 | 2021-12-14 | Cisco Technology, Inc. | Application performance monitoring and management platform with anomalous flowlet resolution |
US11863921B2 (en) | 2017-03-28 | 2024-01-02 | Cisco Technology, Inc. | Application performance monitoring and management platform with anomalous flowlet resolution |
US10547509B2 (en) | 2017-06-19 | 2020-01-28 | Cisco Technology, Inc. | Validation of a virtual port channel (VPC) endpoint in the network fabric |
US11438234B2 (en) | 2017-06-19 | 2022-09-06 | Cisco Technology, Inc. | Validation of a virtual port channel (VPC) endpoint in the network fabric |
US10873506B2 (en) | 2017-06-19 | 2020-12-22 | Cisco Technology, Inc. | Validation of a virtual port channel (VPC) endpoint in the network fabric |
US11411799B2 (en) * | 2017-07-21 | 2022-08-09 | Cisco Technology, Inc. | Scalable statistics and analytics mechanisms in cloud networking |
US10680887B2 (en) | 2017-07-21 | 2020-06-09 | Cisco Technology, Inc. | Remote device status audit and recovery |
US11044170B2 (en) | 2017-10-23 | 2021-06-22 | Cisco Technology, Inc. | Network migration assistant |
US10554501B2 (en) | 2017-10-23 | 2020-02-04 | Cisco Technology, Inc. | Network migration assistant |
US10523541B2 (en) | 2017-10-25 | 2019-12-31 | Cisco Technology, Inc. | Federated network and application data analytics platform |
US10904071B2 (en) | 2017-10-27 | 2021-01-26 | Cisco Technology, Inc. | System and method for network root cause analysis |
US10594542B2 (en) | 2017-10-27 | 2020-03-17 | Cisco Technology, Inc. | System and method for network root cause analysis |
US11750653B2 (en) | 2018-01-04 | 2023-09-05 | Cisco Technology, Inc. | Network intrusion counter-intelligence |
US11233821B2 (en) | 2018-01-04 | 2022-01-25 | Cisco Technology, Inc. | Network intrusion counter-intelligence |
US10999149B2 (en) | 2018-01-25 | 2021-05-04 | Cisco Technology, Inc. | Automatic configuration discovery based on traffic flow data |
US10826803B2 (en) | 2018-01-25 | 2020-11-03 | Cisco Technology, Inc. | Mechanism for facilitating efficient policy updates |
US10798015B2 (en) | 2018-01-25 | 2020-10-06 | Cisco Technology, Inc. | Discovery of middleboxes using traffic flow stitching |
US10574575B2 (en) | 2018-01-25 | 2020-02-25 | Cisco Technology, Inc. | Network flow stitching using middle box flow stitching |
US11128700B2 (en) | 2018-01-26 | 2021-09-21 | Cisco Technology, Inc. | Load balancing configuration based on traffic flow telemetry |
Also Published As
Publication number | Publication date |
---|---|
CN1592305A (en) | 2005-03-09 |
EP1511244A2 (en) | 2005-03-02 |
US7522596B2 (en) | 2009-04-21 |
EP1511244A3 (en) | 2007-03-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7522596B2 (en) | Enhanced DVMRP for destination-based forwarding of multicast data | |
US6654371B1 (en) | Method and apparatus for forwarding multicast data by relaying IGMP group membership | |
Moy | Multicast extensions to OSPF | |
US7447225B2 (en) | Multiple multicast forwarder prevention during NSF recovery of control failures in a router | |
EP2622805B1 (en) | Method for pruning a multicast branch, protocol independent multicast router, and layer-2 exchange | |
US8218429B2 (en) | Method and device for multicast traffic redundancy protection | |
US7835378B2 (en) | Root node redundancy for multipoint-to-multipoint transport trees | |
US10270604B2 (en) | PIM join entropy | |
US20030193958A1 (en) | Methods for providing rendezvous point router redundancy in sparse mode multicast networks | |
US11509572B2 (en) | Optimizing IP multicast delivery with use of local source nodes and the propagation of advertisements therefor | |
CA2311139A1 (en) | System, device, and method for distributing multicast routing information in a protocol independent multicast network | |
US8774181B1 (en) | Reducing unnecessary upstream traffic in PIM-bidirectional mode | |
Ballardie et al. | Core Based Tree (CBT) Multicast | |
Moy | RFC1584: Multicast Extensions to OSPF | |
US7899928B1 (en) | Efficient multicast packet handling in a layer 2 network | |
US11582054B2 (en) | Multicast source discovery protocol (MSDP) loop avoidance | |
US6928075B2 (en) | Method and apparatus for aggregating multicast interfaces | |
Cisco | Configuring IP Multicast Layer 3 Switching | |
Cisco | Internet Protocol (IP) Multicast | |
US11018886B1 (en) | Methods and apparatus for selectively filtering an IP multicast data stream for selected group members of a multicast group | |
EP3923529A1 (en) | Multicast source discovery protocol (msdp) loop avoidance | |
Hardwick et al. | IP multicast explained | |
Capan | Survey of different multicast routing protocols | |
Danilov et al. | MANET multicast with multiple gateways | |
Singh et al. | Approaches to Maintain Bi-connectivity for Resilience in Overlaid Multicasting |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: ALCATEL INTERNETWORKING, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:FINE, MARK;GRAFF, JEREMY;MARINAN, KELLY;REEL/FRAME:014336/0196 Effective date: 20040205 |
|
AS | Assignment |
Owner name: ALCATEL, FRANCE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ALCATEL INTERNETWORKING, INC.;REEL/FRAME:014387/0835 Effective date: 20040223 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
AS | Assignment |
Owner name: ALCATEL LUCENT, FRANCE Free format text: CHANGE OF NAME;ASSIGNOR:ALCATEL;REEL/FRAME:022305/0929 Effective date: 20061130 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
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: 20210421 |