US20070206492A1 - Hierarchical virtual private lan service protection scheme - Google Patents
Hierarchical virtual private lan service protection scheme Download PDFInfo
- Publication number
- US20070206492A1 US20070206492A1 US11/745,303 US74530307A US2007206492A1 US 20070206492 A1 US20070206492 A1 US 20070206492A1 US 74530307 A US74530307 A US 74530307A US 2007206492 A1 US2007206492 A1 US 2007206492A1
- Authority
- US
- United States
- Prior art keywords
- primary
- virtual bridges
- bridges
- virtual
- backup
- 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.)
- Abandoned
Links
- 238000004891 communication Methods 0.000 claims abstract description 13
- 238000000034 method Methods 0.000 claims description 31
- 230000005641 tunneling Effects 0.000 claims description 9
- 230000008569 process Effects 0.000 claims description 5
- 230000004044 response Effects 0.000 claims description 4
- 230000000977 initiatory effect Effects 0.000 claims description 2
- 230000011664 signaling Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 6
- 238000005538 encapsulation Methods 0.000 description 6
- 230000008859 change Effects 0.000 description 4
- 230000007246 mechanism Effects 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 229910000679 solder Inorganic materials 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 3
- 238000013459 approach Methods 0.000 description 2
- 230000006399 behavior Effects 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000011084 recovery Methods 0.000 description 2
- 230000032683 aging Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000018109 developmental process Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000036039 immunity Effects 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008450 motivation Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000002265 prevention Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000011144 upstream manufacturing Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2212/00—Encapsulation of packets
Definitions
- the present invention relates generally to communication networks, and specifically to methods and systems for providing virtual private LAN services (VPLS).
- VPLS virtual private LAN services
- LANs Local Area Networks
- MAC Media Access Control
- Each computing system connects to a LAN through a MAC device.
- MAC bridges that implement the 802.1D standard allow MAC devices attached to physically separated LANs to appear to each other as if they were attached to a single LAN.
- a MAC bridge functions within the Logical Link Control (LLC) sublayer of the Network Layer defined in ISO/IEC standard 7498-1: 1994, entitled “Information Processing Systems—Open Systems Interconnection-Basic Reference Model—Part 1: The Basic Model” (available from the American National Standards Institute, New York, N.Y.), which is incorporated herein by reference.
- the bridge includes two or more MAC devices that interconnect the bridge ports to respective LANs.
- MAC bridges maintain a database to map destination MAC addresses of the packets they receive to bridge ports.
- the bridge builds the database by means of a learning process, in which it associates the source MAC address of each incoming packet with the port on which the packet was received.
- the bridge receives an incoming packet whose destination address is not located in the database, it broadcasts the packet through all its available ports, except the one through which the packet arrived.
- Other MAC bridges that do not recognize the destination address will further broadcast the packet. Through the broadcast mechanism, the packet will eventually traverse all interconnected bridges, and will ultimately reach its destination.
- a similar broadcast operation is performed independently for having a destination MAC address of a broadcast or multicast group, although the multicast scope may be reduced if the bridge is aware (by use of special protocols) of the physical locations of the target addresses in each multicast group.
- the operation of broadcast or multicast of a packet is referred to (independently of the reason) as a flooding process.
- MPLS Multiprotocol Label Switching
- IP Internet Protocol
- MPLS is described in detail by Rosen et al., in Request for Comments (RFC) 3031 of the Internet Engineering Task Force (IETF), entitled “Multiprotocol Label Switching Architecture” (January, 2001), which is incorporated herein by reference. This RFC, as well as other IETF RFCs and drafts cited hereinbelow, is available at www.ietf.org.
- RFC Request for Comments
- IETF Internet Engineering Task Force
- each packet is assigned to a Forwarding Equivalence Class (FEC) when it enters the network, depending on its destination address.
- FEC Forwarding Equivalence Class
- the packet receives a short, fixed-length label identifying the FEC to which it belongs. All packets in a given FEC are passed through the network over the same path by label-switching routers (LSRs).
- LSRs label-switching routers
- IP routers LSRs simply use the packet label as an index to a look-up table, which specifies the next hop on the path for each FEC and the label that the LSR should attach to the packet for the next hop.
- LSP label-switched path
- MPLS tunnels are in transporting layer-2 packets, such as Ethernet frames or ATM cells, over high-speed, high-performance packet networks.
- Layer-2 packets such as Ethernet frames or ATM cells
- Methods for this purpose are described, for example, by Martini et al., in “Encapsulation Methods for Transport of Ethernet Frames Over IP/MPLS Networks” (IETF draft-ietf-ethernet-encap-00.txt, August, 2002), which is incorporated herein by reference.
- This draft defines mechanisms for encapsulating Ethernet traffic for transportation over IP networks using MPLS or other tunneling methods, such as Generic Routing Encapsulation (GRE), as are known in the art.
- GRE Generic Routing Encapsulation
- L2TPv3 described by Townsley et al in “Layer Two Tunneling Protocol (Version 3) ‘L2TPv3’” (IETF draft-ietf-12tpext-12tp-base-04.txt, November, 2002), which is incorporated herein by reference, is another technique for tunneling layer-2 packets over IP networks, which can be used, inter alia, to carry Ethernet packets within a provider network.
- layer 2 refers to the second layer in the protocol stack defined by the well-known Open Systems Interface (OSI) model, also known as the logical link, data link, or MAC, layer.
- OSI Open Systems Interface
- native Ethernet LANs are connected to the IP network by provider edge (PE) devices, which are linked one to another by tunnels through the IP network.
- PE provider edge
- the sending (ingress) PE device receives Ethernet frames from a customer edge (CE) device on the source LAN. It encapsulates the frames in packets with the label stack required for transmitting the packets through the appropriate tunnel to the receiving (egress) PE device.
- CE customer edge
- the label structure includes a “PW demultiplexer” label (or virtual connection—VC label), which is used by the egress PE device to recognize the context of the packet if multiple connections share the same tunnel. Based on the PW demultiplexer label, the PE device de-encapsulates the frame and, optionally, adds a VLAN tag for transmission on the target LAN to the destination CE device. Details of the PW demultiplexer structure are described by Bryant et al. in an IETF draft entitled “Protocol Layering in PWE3” (IETF draft-ietf-pwe3-protocol-layer-00.txt, May, 2002), which is incorporated herein by reference. Martini et al.
- the IP network emulates Ethernet trunking behavior and can thus be treated as an Ethernet “pseudo wire” (PW).
- PW Ethernet “pseudo wire”
- each PW is a virtual Ethernet point-to-point connection, emulating a physical connection between two Ethernet ports.
- Lasserre et al. describe a method to create a virtual private LAN service (VPLS) using a MPLS network in “Virtual Private LAN Services over MPLS” (IETF draft-lasserre-vkompella-ppvpn-vpls-02.txt, June, 2002), which is incorporated herein by reference.
- VPLS also known as a transparent LAN service—TLS
- TLS transparent LAN service
- a virtual bridge node has “virtual ports,” which are the endpoints of PWs that are part of the VPLS.
- the interfaces to which the users are actually connected are physical ports at the network edges. Both virtual and real interfaces are treated identically from the point of view of frame forwarding and address learning.
- a single provider node can participate in multiple VPLS instances, each belonging to a different user.
- the VPLS network topology is completely specified by the PW connections.
- the PW connections are MPLS tunnels
- the VPLS depends on the MPLS protocol to actually transfer the packets through the network.
- MPLS networks supply an alternative, virtual implementation of layer-2 network communications
- VPLS can be thought of as parallel to conventional virtual bridged local area networks, as specified in the IEEE 802.1Q standard. From the perspective of the end-user, the VPLS network is transparent. The user is provided with the illusion that the provider network is a single LAN domain. User nodes on different physical LANs can thus be joined together through VPLS connections to define a virtual private network (VPN), which appears to the users to be a single Ethernet LAN.
- VPN virtual private network
- VPLS networks are still in the development stage, and there are as yet no clear standards for loop prevention in such networks.
- One possible solution to avoiding loops in VPLS topologies is to configure the VPLS network as a full mesh of tunnels, as specified by Lasserre et al. in the above-mentioned draft.
- each PE is directly connected to every other PE in the same VPN by a single PW.
- Lasserre et al. require that all PEs support a “split horizon” scheme, meaning that a PE must not forward traffic from one PW to another, although it may (and should) forward traffic from one physical port to another and between physical ports and the PWs.
- a packet to be flooded coming from a PW will never be copied to another PW on the full mesh side, but is flooded to all Ethernet ports on the same VPN.
- An Ethernet packet to be flooded arriving from a physical port is copied to all other physical ports and to all the full mesh PWs of the same VPN. This split behavior differs from the traditional model of 802.1D bridges.
- Hierarchical VPLS is an extension to the VPLS model, which is also described by Lasserre et al. in the above-mentioned draft.
- some or all of the physical interfaces on one side of the split horizon can be replaced by point-to-point PWs, which act as logical extensions of physical ports of remote nodes.
- point-to-point PWs act as logical extensions of physical ports of remote nodes.
- Nodes with only point-to-point PWs are considered to be on the “access side” of the network, and are referred to as “edge nodes.”
- Nodes with full mesh PWs are considered to be in the “core side, of the network, and are referred to as “core nodes.”
- the scope of forwarding and flooding is the same as described above for full mesh PWs and physical ports.
- protection against some failures is achieved by backup point-to-point PWs between each edge node and an additional core node (also referred to as “redundant” or “protection” PWs).
- This backup PW connection is in addition to the “standard” PW connection already existing between the edge node and another core node.
- a backup “protection path” through another core node can be used to provide access between the edge node and the rest of the network.
- Hierarchical VPLS has the advantages of reducing significantly both the number of connections in the network and the number of times a packet needs to replicated in the learning process, when compared with a standard full mesh topology.
- the failure protection scheme suggested by Lasserre et al. can result in a long period of traffic outage if a virtual connection fails between an edge node and a core node, or if a core node fails. In most cases, initiation of failure protection depends on MAC address aging and learning schemes, which are inherently slow. Lasserre et al. in the above-mentioned draft make no provisions for handling multiple failures at once.
- the need to handle both standard connections (to edge nodes and other core nodes) and backup protection connections (to edge nodes) complicates the design of the VPLS core nodes and of the network as a whole.
- the present invention seeks to provide improved mechanisms for protection from failure in virtual private networks (VPNs), particularly Ethernet VPNs.
- VPNs virtual private networks
- Ethernet Ethernet
- the embodiments of the present invention that are described hereinbelow are based on VPLS networks, the principles of the present invention are similarly applicable to other types of transparent LAN-over-IP services, using other types of virtual bridge devices.
- a VPN comprises primary core nodes, as in a conventional hierarchical VPLS network, along with one or more standby core nodes.
- Each standby core node has the same topological image in the network (i.e., the same connections) as a corresponding primary core node which it protects. Therefore, if the primary core node fails, the remaining nodes in the network simply redirect all connections from the failed primary core node to the corresponding standby core node. Since the standby core node has the same topology as the failed primary core node, the remaining nodes in the network do not need to re-learn MAC table addresses, and are thus able to recover quickly from the failure. In addition, since there is no topology change, there is no need to clear the MAC tables, so that packet flooding is reduced significantly.
- a network designed in accordance with the present invention can handle multiple simultaneous node failures, as long as at least one core node from each pair of primary and standby core nodes does not fail.
- a data communication network including:
- each such backup virtual bridge being associated with at least one of the primary virtual bridges and connected by at least one secondary virtual connection to at least another one of the primary virtual bridges, so that upon a failure of one of the primary virtual bridges with which it is associated, the backup virtual bridge transmits and receives the data packets over the network via the at least one secondary virtual connection in place of the at least one of the primary virtual bridges.
- the primary and backup virtual bridges are adapted to transmit the packets over the network by tunneling through the network, and the primary and backup virtual bridges are arranged to transmit the packets using a virtual private LAN service (VPLS).
- the primary and backup virtual bridges are adapted to serve as provider edge (PE) devices, and to transmit the packets over pseudo-wires (PWs) connecting to the edge devices, wherein the PWs include tunnels selected from the group of tunnels consisting of multi-protocol label-switched (MPLS) tunnels, Generic Routing Encapsulation (GRE) tunnels, and Layer Two Tunneling Protocol (L2TP) tunnels.
- MPLS multi-protocol label-switched
- GRE Generic Routing Encapsulation
- L2TP Layer Two Tunneling Protocol
- the primary virtual connections define a respective primary topology image for each of the primary virtual bridges
- each of the backup virtual bridges is paired with a corresponding one of the primary virtual bridges and is connected by secondary virtual connections to the other primary virtual bridges so as to define a respective secondary topology image that is substantially identical to the respective primary topology image of the corresponding one of the primary virtual bridges.
- each of the edge devices is connected by point-to-point connections both to a respective one of the backup virtual bridges and to the corresponding one of the primary virtual bridges with which the respective one of the backup virtual bridges is paired.
- the edge devices may be connected to the respective one of the backup virtual bridges in a first star topology and to the corresponding one of the primary virtual bridges in a second star topology. Alternatively, the edge devices are connected to the respective one of the backup virtual bridges and to the corresponding one of the primary virtual bridges in a full mesh topology.
- the primary virtual connections define a first full mesh of the primary virtual bridges
- each of the backup virtual bridges is connected by the secondary virtual connections to both the primary virtual bridges and to the other backup virtual bridges so as to define a second full mesh of the backup virtual bridges and a third full mesh between each one of the backup virtual bridges and the primary virtual bridges, except for the corresponding one of the primary virtual bridges with which the backup virtual bridge is paired.
- each of the primary and backup virtual bridges is adapted to maintain a respective media access control (MAC) table, and to forward the data packets in accordance with entries in the MAC table
- each of the secondary virtual bridges is adapted to periodically synchronize its MAC table with the MAC table of the corresponding one of the primary virtual bridges with which it is paired.
- MAC media access control
- each of the backup virtual bridges is connected by secondary virtual connections to both the primary virtual bridges and to the other backup virtual bridges, so that the primary and second virtual connections define a full mesh of all the primary and secondary virtual bridges.
- each of the edge devices is connected to a respective one of the primary virtual bridges and to a respective one of the backup virtual bridges, so that upon detecting the failure of the respective one of the primary virtual bridges, the edge devices communicate with the network through the backup virtual bridge instead of the respective one of the primary virtual bridges.
- the primary virtual bridges are adapted, upon receiving packets sent by the edge devices through the backup virtual bridge, to communicate with the backup virtual bridge instead of the one of the primary virtual bridges in which the failure occurred.
- the edge devices are adapted to send periodic messages to the primary virtual bridges in accordance with a predetermined signaling protocol, and to detect the failure when the one of the primary virtual bridges does not respond to the messages as expected.
- the predetermined signaling protocol is selected from a group of OAM or topology discovery procedures provided by lower network protocol layers.
- At least one of the backup virtual bridges is connected by a single secondary virtual connection to a selected one of the primary virtual bridges, such that upon the failure of the at least one of the primary virtual bridges with which the at least one of the backup virtual bridges is associated, the at least one of the backup virtual bridges transmits and receives the data packets over the network via the selected one of the primary virtual bridges over the single secondary virtual connection.
- each of the primary virtual bridges is adapted to maintain a respective media access control (MAC) table, and to forward the data packets in accordance with entries in the MAC table, and wherein each of the primary virtual bridges is adapted, upon detecting the failure of the at least one of the primary virtual bridges, to update the entries in the respective MAC table that point to the at least one of the primary virtual bridges so as to point instead to the selected one of the primary virtual bridges.
- MAC media access control
- a method for data communication including:
- FIG. 1 is a block diagram that schematically illustrates a VPN with a protection scheme in accordance with a preferred embodiment of the present invention.
- FIG. 2 is a block diagram that schematically illustrates a detail of a VPN with a protection scheme in accordance with an alternative embodiment of the present invention.
- FIG. 3 is a block diagram that schematically illustrates a VPN with a protection scheme in accordance with an alternative embodiment of the present invention.
- FIG. 1 is a block diagram that schematically illustrates a VPN 20 with a hierarchical VPLS topology, implementing a protection scheme in accordance with a preferred embodiment of the present invention.
- VPN 20 is built around a virtual private LAN service (VPLS), operating within a network 22 , typically an IP or MPLS network.
- the VPLS is based on virtual bridges 30 , 32 , 34 , 36 , 38 , and 40 , or VPLS-capable PEs, which are connected by PWs 70 , 72 , 74 and 76 through network 22 .
- network 22 includes only a small number of PEs and represents only a single VPLS instance, the principles embodied in this network may be extended in a straightforward manner to larger networks and to multiple VPLS instances.
- Three primary virtual bridges 30 , 32 and 34 are connected with each other in a full mesh with PW connections 70 .
- the PW connections comprise MPLS tunnels, but they may alternatively comprise virtual connections of other types, such as GRE or L2TP tunnels.
- Each of the primary core nodes 30 , 32 and 34 is paired with a corresponding backup virtual bridge, referred to as a standby core node, 36 , 38 and 40 , respectively.
- the standby core nodes are connected in the network by redundant backup connections 72 .
- Each standby core node has a topology identical to its corresponding primary core node. For example, standby core node 36 has the same topology image as primary core node 30 .
- Each of the primary and standby core nodes is connected to all the other core nodes in the network except for the standby or primary core node with which it is paired.
- An optional connection 79 between a primary core node and its corresponding standby core node may also be included, as described hereinbelow.
- the core nodes are configured to support a split horizon model. Connections 74 and 76 are made between the core nodes and edge nodes 50 , 52 , 54 , 56 , 58 and 60 , as shown in FIG. 1 . For the sake of simplicity in this figure, only two edge nodes are shown to be connected to each core node. Edge nodes are in turn connected to user terminals via physical interfaces 78 , which are typically Ethernet interfaces, but may alternatively be interfaces of other types, such as frame relay or ATM circuits.
- the VPLS and LAN topologies shown in FIG. 1 are chosen by way of example, and the principles of the present invention may be applied, mutatis mutandis, to alternative VPLS and LAN topologies, as well.
- a primary core node fails, all connections 70 , 74 and 72 to the failed primary core node are no longer used. Backup connections 72 and 76 to the corresponding standby core node are used instead.
- edge nodes 50 and 52 which prior to the failure had been communicating through PW connections 74 with primary core node 30 , begin instead to communicate with standby core node 36 through PW connections 76 .
- the other core nodes typically primary core nodes 32 and 34 , but possibly standby core nodes 38 and 40 if there were other primary core node failures) begin to use backup PW connections 72 to communicate with standby core node 36 .
- the remaining nodes in the network may continue to use the PW associations in their MAC tables that they learned before the failure, except that the tables now point to the backup connections instead of the failed primary connections.
- the other nodes simply redirect all packets that were supposed to be sent to the failed primary core node 30 to the standby core node 36 that protects it. Detection of and response to core node failure proceeds as follows:
- Core node failures are initially detected by edge nodes, using either existing signaling protocols (such as “hello” messages provided by the Label Distribution Protocol—LDP), or using special “ping” operations or OAM (operations, administration, and management) connectivity verification if such a signaling protocol is not available or if faster response is required.
- LDP Label Distribution Protocol
- OAM operations, administration, and management
- edge nodes 50 and 52 detect this failure by one of the methods described above. Edge nodes 50 and 52 then start directing traffic through standby core node 36 . Standby core node 36 relays the traffic to other core nodes in the network. Upon receiving this traffic, the other core nodes in the network begin redirecting traffic formerly directed to primary core node 30 , to flow through standby core node 36 instead.
- a simple communications protocol for synchronizing MAC table databases between each pair of primary and standby core nodes can be invoked regularly to update the standby core node with the current MAC forwarding table stored in the corresponding primary core node. In this way, if a primary core node fails, the MAC table database of the corresponding standby core node is closely synchronized with the MAC table database of the failed node, and flooding caused by unknown MAC addresses is limited to the MAC addresses learned by the failed node since the last synchronization.
- Networks designed in accordance with the present invention can handle certain multiple core node failures, on the condition that at least one node from each pair of primary and standby core nodes does not fail. For example, if primary core node 30 fails, edge node 50 can stop communicating with core node 30 through point-to-point PW connection 74 , and instead begin communicating with standby core node 36 through backup point-to-point PW connection 76 . If primary core node 34 now also fails, the remaining active core nodes, including standby core node 36 , will switch to communicating through PW 72 with standby core node 40 . In this situation edge node 50 can still communicate with edge node 58 through the backup connections and nodes.
- a single standby core node can be assigned to protect multiple primary core nodes, thus reducing the number of core nodes and the number of bi-directional connections in the core side of the network.
- This approach may be desirable in large networks, where the number of connections may be high.
- node 40 may be used to protect against failure of primary core node 30 , as well as primary core node 34 .
- edge nodes 50 and 52 are connected by backup connections 76 to node 40 .
- nodes 32 and 34 Upon detecting a failure of node 30 , nodes 32 and 34 send all packets destined for node 30 to node 40 , instead.
- This change in topology may require either more complicated MAC database coordination between the core nodes, or MAC table clearing after a failure occurs, which may cause packet flooding until the MAC learning database is re-stabilized.
- the standby cores node may use a standard or dedicated signaling protocol to detect that the primary core node has again become active.
- the corresponding standby core node may issue a command to all the edge nodes that have point-to-point PW connections with the primary core node, instructing them to revert to using the connections with the primary core node.
- This approach has the benefit of making possible a synchronized topology change, avoiding a situation in which some edge nodes direct traffic through the primary core node, while other edge nodes direct traffic through the corresponding standby core node.
- An alternative method of restoration of traffic to a primary core node is as follows: Once the primary core node becomes active again, the signaling of network connections between each edge node and the primary core node is re-established. Upon noticing this signaling, each edge node can begin to use its connection to the primary core node instead of the connection to the standby core node. In other words, restoration of traffic to the primary core node is carried out by a similar mechanism to that used to divert the traffic to the standby core node when the primary core node fails. In this case, however, topology recovery may be not synchronized over the whole network, so that some core nodes may continue sending traffic through the standby node for a while.
- the edge nodes should be therefore capable of receiving packets simultaneously from both the standby and the primary core nodes, while sending upstream packets from users to only one of these core nodes.
- an additional point-to-point connection 79 preferably a PW connection, between each primary core node and its corresponding standby core node.
- additional connections can be used to bridge between different edge nodes connected by point-to-point PW connections to the same primary and standby core nodes, as follows:
- edge node will start to use the corresponding standby core node, even if the primary core node itself has not failed. Thus, it may occur that some edge nodes continue to communicate with the primary core node while other edge nodes communicate with the corresponding standby core node. Layer 2 connectivity is still maintained between all the edge nodes, however, through the use of additional connection 79 between the primary and standby core nodes. If such an additional connection is used, the corresponding standby core node should typically not send traffic toward the full mesh of connections 72 unless the primary core node itself has failed.
- FIG. 2 is a block diagram that schematically shows a detail of VPN 20 , illustrating an alternative configuration of the edge nodes, in accordance with a preferred embodiment of the present invention.
- the figure shows a pair of corresponding primary and standby core nodes 80 and 82 , which are capable of split horizon operation between a core mesh of connections 70 and 72 and access mesh of connections 74 and 76 .
- Edge nodes 84 , 86 and 88 are connected to core nodes 80 and 82 by connections 74 and 76 , and are capable of bridging in a full mesh topology created by additional connections 90 between all the edge nodes.
- other VPLS and LAN topologies may be used to connect the edge nodes to the core nodes, as well, as will be apparent to those skilled in the art.
- edge nodes 84 , 86 , and 88 communicate through connections 74 with primary core node 80 , but in this case they communicate through connections 90 among themselves. If primary core node 80 fails, edge nodes 84 , 86 , and 88 begin communicating through backup connections 76 with the corresponding standby core node 82 .
- FIG. 3 is a block diagram that schematically shows VPN 20 in an alternative configuration, in accordance with a preferred embodiment of the present invention.
- the motivation for this configuration is to lower the number of connections in the core of network 22 , at the cost of reduced immunity to multiple nodes failure.
- each of the standby core nodes in the present embodiment is connected by only a single backup connection 72 to one of the primary core nodes. In the absence of any failure, the operation of the network is identical to that described earlier. If one of the primary core nodes fails, however, for example node 30 , the spokes attached to it start to use standby core node 36 , as described above. The topology image of the network is now changed, and the other core nodes must now communicate with node 36 through node 34 , rather than directly.
- the other primary core nodes may adjust to the change in topology in various ways.
- the other nodes when the other nodes detect the failure, they simply flush the MAC table database entries associated with connections 70 that were used to communicate with node 30 .
- each node knows in advance which node is on the alternative path to the standby core node corresponding to each of the primary core nodes. In this case, the other core nodes automatically re-associate the MAC addresses that were previously associated with the connection to the failed node, so that these addresses are associated instead with the connection to the node on the alternative path.
- node 32 prior to the failure in node 30 , node 32 will have learned to associate one set of MAC addresses with connection 70 to node 34 , and to associate another set with connection 70 to node 30 . Node 32 also knows (by means of configuration settings) that in case of failure in node 30 , the corresponding standby node 36 is to be accessed through node 34 . Therefore, when the failure occurs, node 32 simply combines the two sets of MAC addresses into one set, which is associated with the connection to node 34 .
- network 22 uses certain particular protocols for communication routing and tunneling
- principles of the present invention may similarly be applied using protocols and virtual bridges of other types. It will thus be appreciated that the preferred embodiments described above are cited by way of example, and that the present invention is not limited to what has been particularly shown and described hereinabove. Rather, the scope of the present invention includes both combinations and subcombinations of the various features described hereinabove, as well as variations and modifications thereof which would occur to persons skilled in the art upon reading the foregoing description and which are not disclosed in the prior art.
Abstract
A data communication network includes a plurality of primary virtual bridges, interconnected by primary virtual connections so as to transmit and receive data packets over the network to and from edge devices connected thereto. One or more backup virtual bridges, each associated with at least one of the primary virtual bridges, are connected by at least one secondary virtual connection to at least another one of the primary virtual bridges, so that upon a failure of one of the primary virtual bridges with which it is associated, the backup virtual bridge transmits and receives the data packets over the network via the at least one secondary virtual connection in place of the at least one of the primary virtual bridges.
Description
- This application is a continuation Application of, and claims the benefit of priority under 35 U.S.C. §120 from, U.S. application Ser. No. 10/337,382, filed Jan. 7, 2003. The entire content of the above application is incorporated herein by reference.
- The present invention relates generally to communication networks, and specifically to methods and systems for providing virtual private LAN services (VPLS).
- Local Area Networks (LANs) connect computing systems together. LANs of all types can be connected together using Media Access Control (MAC) bridges, as set forth in the “IEEE” Standard for Information Technology, Telecommunications and Information Exchange between Systems, Local and Metropolitan Area Networks, Common Specifications, Part 3: Media Access Control (MAC) Bridges,” published as ANSI/IEEE Standard 802.1D (1998), which is incorporated herein by reference. The 802.1D standard is available at standards.ieee.org/getieee802/download/802.1D-1998.pdf.
- Each computing system connects to a LAN through a MAC device. MAC bridges that implement the 802.1D standard allow MAC devices attached to physically separated LANs to appear to each other as if they were attached to a single LAN. A MAC bridge functions within the Logical Link Control (LLC) sublayer of the Network Layer defined in ISO/IEC standard 7498-1: 1994, entitled “Information Processing Systems—Open Systems Interconnection-Basic Reference Model—Part 1: The Basic Model” (available from the American National Standards Institute, New York, N.Y.), which is incorporated herein by reference. The bridge includes two or more MAC devices that interconnect the bridge ports to respective LANs.
- MAC bridges maintain a database to map destination MAC addresses of the packets they receive to bridge ports. The bridge builds the database by means of a learning process, in which it associates the source MAC address of each incoming packet with the port on which the packet was received. When the bridge receives an incoming packet whose destination address is not located in the database, it broadcasts the packet through all its available ports, except the one through which the packet arrived. Other MAC bridges that do not recognize the destination address will further broadcast the packet. Through the broadcast mechanism, the packet will eventually traverse all interconnected bridges, and will ultimately reach its destination. A similar broadcast operation is performed independently for having a destination MAC address of a broadcast or multicast group, although the multicast scope may be reduced if the bridge is aware (by use of special protocols) of the physical locations of the target addresses in each multicast group. The operation of broadcast or multicast of a packet is referred to (independently of the reason) as a flooding process.
- Multiprotocol Label Switching (MPLS) is gaining popularity as a method for efficient transportation of data packets over connectionless networks, such as Internet Protocol (IP) networks. MPLS is described in detail by Rosen et al., in Request for Comments (RFC) 3031 of the Internet Engineering Task Force (IETF), entitled “Multiprotocol Label Switching Architecture” (January, 2001), which is incorporated herein by reference. This RFC, as well as other IETF RFCs and drafts cited hereinbelow, is available at www.ietf.org. In conventional IP routing, each router along the path of a packet sent through the network analyzes the packet header and independently chooses the next hop for the packet by running a routing algorithm. In MPLS, however, each packet is assigned to a Forwarding Equivalence Class (FEC) when it enters the network, depending on its destination address. The packet receives a short, fixed-length label identifying the FEC to which it belongs. All packets in a given FEC are passed through the network over the same path by label-switching routers (LSRs). Unlike IP routers, LSRs simply use the packet label as an index to a look-up table, which specifies the next hop on the path for each FEC and the label that the LSR should attach to the packet for the next hop.
- Since the flow of packets along a label-switched path (LSP) under MPLS is completely specified by the label applied at the ingress node of the path, a LSP can be treated as a tunnel through the network. Such tunnels are particularly useful in network traffic engineering, as well as communication security. MPLS tunnels are established by “binding” a particular label, assigned at the ingress node to the network, to a particular FEC.
- One of the most promising uses of MPLS tunnels is in transporting layer-2 packets, such as Ethernet frames or ATM cells, over high-speed, high-performance packet networks. Methods for this purpose are described, for example, by Martini et al., in “Encapsulation Methods for Transport of Ethernet Frames Over IP/MPLS Networks” (IETF draft-ietf-ethernet-encap-00.txt, August, 2002), which is incorporated herein by reference. This draft defines mechanisms for encapsulating Ethernet traffic for transportation over IP networks using MPLS or other tunneling methods, such as Generic Routing Encapsulation (GRE), as are known in the art. L2TPv3, described by Townsley et al in “Layer Two Tunneling Protocol (Version 3) ‘L2TPv3’” (IETF draft-ietf-12tpext-12tp-base-04.txt, November, 2002), which is incorporated herein by reference, is another technique for tunneling layer-2 packets over IP networks, which can be used, inter alia, to carry Ethernet packets within a provider network. The term “
layer 2” refers to the second layer in the protocol stack defined by the well-known Open Systems Interface (OSI) model, also known as the logical link, data link, or MAC, layer. - According to the model proposed by Martini et al., native Ethernet LANs are connected to the IP network by provider edge (PE) devices, which are linked one to another by tunnels through the IP network. The sending (ingress) PE device receives Ethernet frames from a customer edge (CE) device on the source LAN. It encapsulates the frames in packets with the label stack required for transmitting the packets through the appropriate tunnel to the receiving (egress) PE device.
- The label structure includes a “PW demultiplexer” label (or virtual connection—VC label), which is used by the egress PE device to recognize the context of the packet if multiple connections share the same tunnel. Based on the PW demultiplexer label, the PE device de-encapsulates the frame and, optionally, adds a VLAN tag for transmission on the target LAN to the destination CE device. Details of the PW demultiplexer structure are described by Bryant et al. in an IETF draft entitled “Protocol Layering in PWE3” (IETF draft-ietf-pwe3-protocol-layer-00.txt, May, 2002), which is incorporated herein by reference. Martini et al. specify label distribution procedures for binding the VC label to the desired service in the case of MPLS transport in a further draft entitled “Transport of
Layer 2 Frames over MPLS” (IETF draft-ietf-pwe3-control-protocol-01.txt, November, 2002), which is also incorporated herein by reference. - As a result of this encapsulation and associated processing functions, the IP network emulates Ethernet trunking behavior and can thus be treated as an Ethernet “pseudo wire” (PW). In other words, from the point of view of native Ethernet LANs that are connected to tunnels through the IP network, each PW is a virtual Ethernet point-to-point connection, emulating a physical connection between two Ethernet ports.
- Taking this functionality a step further, Lasserre et al. describe a method to create a virtual private LAN service (VPLS) using a MPLS network in “Virtual Private LAN Services over MPLS” (IETF draft-lasserre-vkompella-ppvpn-vpls-02.txt, June, 2002), which is incorporated herein by reference. Although this reference is limited in scope to MPLS tunneling, the PW connection between the nodes can more generally be implemented using any available PW protocol, such as GRE or L2TPv3. A VPLS (also known as a transparent LAN service—TLS) provides bridge-like functionality between multiple sites over a large network. Users connect to the VPLS via regular node interfaces, and PWs between the nodes to which the users are connected form the VPLS entity itself. Every node in a VPLS acts as a virtual bridge. A virtual bridge node has “virtual ports,” which are the endpoints of PWs that are part of the VPLS. The interfaces to which the users are actually connected are physical ports at the network edges. Both virtual and real interfaces are treated identically from the point of view of frame forwarding and address learning. A single provider node can participate in multiple VPLS instances, each belonging to a different user.
- The VPLS network topology is completely specified by the PW connections. When the PW connections are MPLS tunnels, the VPLS depends on the MPLS protocol to actually transfer the packets through the network. Since MPLS networks supply an alternative, virtual implementation of layer-2 network communications, VPLS can be thought of as parallel to conventional virtual bridged local area networks, as specified in the IEEE 802.1Q standard. From the perspective of the end-user, the VPLS network is transparent. The user is provided with the illusion that the provider network is a single LAN domain. User nodes on different physical LANs can thus be joined together through VPLS connections to define a virtual private network (VPN), which appears to the users to be a single Ethernet LAN.
- VPLS networks are still in the development stage, and there are as yet no clear standards for loop prevention in such networks. One possible solution to avoiding loops in VPLS topologies is to configure the VPLS network as a full mesh of tunnels, as specified by Lasserre et al. in the above-mentioned draft. In a full mesh, each PE is directly connected to every other PE in the same VPN by a single PW. To avoid loops in the VPN, Lasserre et al. require that all PEs support a “split horizon” scheme, meaning that a PE must not forward traffic from one PW to another, although it may (and should) forward traffic from one physical port to another and between physical ports and the PWs. Considering the scope of flooding generally, a packet to be flooded coming from a PW will never be copied to another PW on the full mesh side, but is flooded to all Ethernet ports on the same VPN. An Ethernet packet to be flooded arriving from a physical port is copied to all other physical ports and to all the full mesh PWs of the same VPN. This split behavior differs from the traditional model of 802.1D bridges.
- “Hierarchical VPLS” is an extension to the VPLS model, which is also described by Lasserre et al. in the above-mentioned draft. In hierarchical VPLS, some or all of the physical interfaces on one side of the split horizon can be replaced by point-to-point PWs, which act as logical extensions of physical ports of remote nodes. In this case, there are both full mesh PWs and point-to-point PWs (and possibly even physical ports) associated with the same VPN. Nodes with only point-to-point PWs are considered to be on the “access side” of the network, and are referred to as “edge nodes.” Nodes with full mesh PWs are considered to be in the “core side, of the network, and are referred to as “core nodes.” The scope of forwarding and flooding is the same as described above for full mesh PWs and physical ports.
- In the Hierarchical VPLS model, protection against some failures is achieved by backup point-to-point PWs between each edge node and an additional core node (also referred to as “redundant” or “protection” PWs). This backup PW connection is in addition to the “standard” PW connection already existing between the edge node and another core node. Thus, if a VC between an edge node and a core node fails, a backup “protection path” through another core node can be used to provide access between the edge node and the rest of the network.
- Hierarchical VPLS has the advantages of reducing significantly both the number of connections in the network and the number of times a packet needs to replicated in the learning process, when compared with a standard full mesh topology. The failure protection scheme suggested by Lasserre et al., however, can result in a long period of traffic outage if a virtual connection fails between an edge node and a core node, or if a core node fails. In most cases, initiation of failure protection depends on MAC address aging and learning schemes, which are inherently slow. Lasserre et al. in the above-mentioned draft make no provisions for handling multiple failures at once. In addition, the need to handle both standard connections (to edge nodes and other core nodes) and backup protection connections (to edge nodes) complicates the design of the VPLS core nodes and of the network as a whole.
- An alternative hierarchical solution for VPLS connectivity is defined by Sodder et al. in an IETF draft entitled “Virtual Hierarchical LAN Services” (IETF draft-sodder-ppvpn-vhls-01.txt, November, 2002) which is incorporated herein by reference. While Sodder's PW encapsulation is different from the format defined in the above-mentioned references, the system topology (called VHLS in the Sodder draft) is very similar to that described above. MAC learning by edge nodes in Sodder's system is carried out hierarchically from the MAC point of view (MAC in MAC encapsulation). In terms of the operation of core devices and network topology, however, VHLS is substantially the same as the VPLS described by Lasserre et al.
- The present invention seeks to provide improved mechanisms for protection from failure in virtual private networks (VPNs), particularly Ethernet VPNs. Although the embodiments of the present invention that are described hereinbelow are based on VPLS networks, the principles of the present invention are similarly applicable to other types of transparent LAN-over-IP services, using other types of virtual bridge devices.
- In preferred embodiments of the present invention, a VPN comprises primary core nodes, as in a conventional hierarchical VPLS network, along with one or more standby core nodes. Each standby core node has the same topological image in the network (i.e., the same connections) as a corresponding primary core node which it protects. Therefore, if the primary core node fails, the remaining nodes in the network simply redirect all connections from the failed primary core node to the corresponding standby core node. Since the standby core node has the same topology as the failed primary core node, the remaining nodes in the network do not need to re-learn MAC table addresses, and are thus able to recover quickly from the failure. In addition, since there is no topology change, there is no need to clear the MAC tables, so that packet flooding is reduced significantly.
- Furthermore, a network designed in accordance with the present invention can handle multiple simultaneous node failures, as long as at least one core node from each pair of primary and standby core nodes does not fail.
- There is therefore provided, in accordance with a preferred embodiment of the present invention, a data communication network, including:
- a plurality of primary virtual bridges, interconnected by primary virtual connections so as to transmit and receive data packets over the network to and from edge devices connected thereto; and
- one or more backup virtual bridges, each such backup virtual bridge being associated with at least one of the primary virtual bridges and connected by at least one secondary virtual connection to at least another one of the primary virtual bridges, so that upon a failure of one of the primary virtual bridges with which it is associated, the backup virtual bridge transmits and receives the data packets over the network via the at least one secondary virtual connection in place of the at least one of the primary virtual bridges.
- Preferably, the primary and backup virtual bridges are adapted to transmit the packets over the network by tunneling through the network, and the primary and backup virtual bridges are arranged to transmit the packets using a virtual private LAN service (VPLS). In a preferred embodiment, the primary and backup virtual bridges are adapted to serve as provider edge (PE) devices, and to transmit the packets over pseudo-wires (PWs) connecting to the edge devices, wherein the PWs include tunnels selected from the group of tunnels consisting of multi-protocol label-switched (MPLS) tunnels, Generic Routing Encapsulation (GRE) tunnels, and Layer Two Tunneling Protocol (L2TP) tunnels.
- Typically, the primary virtual connections define a respective primary topology image for each of the primary virtual bridges, and each of the backup virtual bridges is paired with a corresponding one of the primary virtual bridges and is connected by secondary virtual connections to the other primary virtual bridges so as to define a respective secondary topology image that is substantially identical to the respective primary topology image of the corresponding one of the primary virtual bridges. Preferably, each of the edge devices is connected by point-to-point connections both to a respective one of the backup virtual bridges and to the corresponding one of the primary virtual bridges with which the respective one of the backup virtual bridges is paired. The edge devices may be connected to the respective one of the backup virtual bridges in a first star topology and to the corresponding one of the primary virtual bridges in a second star topology. Alternatively, the edge devices are connected to the respective one of the backup virtual bridges and to the corresponding one of the primary virtual bridges in a full mesh topology.
- In a preferred embodiment, the primary virtual connections define a first full mesh of the primary virtual bridges, and each of the backup virtual bridges is connected by the secondary virtual connections to both the primary virtual bridges and to the other backup virtual bridges so as to define a second full mesh of the backup virtual bridges and a third full mesh between each one of the backup virtual bridges and the primary virtual bridges, except for the corresponding one of the primary virtual bridges with which the backup virtual bridge is paired.
- Typically, each of the primary and backup virtual bridges is adapted to maintain a respective media access control (MAC) table, and to forward the data packets in accordance with entries in the MAC table, and each of the secondary virtual bridges is adapted to periodically synchronize its MAC table with the MAC table of the corresponding one of the primary virtual bridges with which it is paired.
- In a preferred embodiment, each of the backup virtual bridges is connected by secondary virtual connections to both the primary virtual bridges and to the other backup virtual bridges, so that the primary and second virtual connections define a full mesh of all the primary and secondary virtual bridges.
- Preferably, each of the edge devices is connected to a respective one of the primary virtual bridges and to a respective one of the backup virtual bridges, so that upon detecting the failure of the respective one of the primary virtual bridges, the edge devices communicate with the network through the backup virtual bridge instead of the respective one of the primary virtual bridges. Further preferably, the primary virtual bridges are adapted, upon receiving packets sent by the edge devices through the backup virtual bridge, to communicate with the backup virtual bridge instead of the one of the primary virtual bridges in which the failure occurred.
- In a preferred embodiment, the edge devices are adapted to send periodic messages to the primary virtual bridges in accordance with a predetermined signaling protocol, and to detect the failure when the one of the primary virtual bridges does not respond to the messages as expected. Preferably, the predetermined signaling protocol is selected from a group of OAM or topology discovery procedures provided by lower network protocol layers.
- In another preferred embodiment, at least one of the backup virtual bridges is connected by a single secondary virtual connection to a selected one of the primary virtual bridges, such that upon the failure of the at least one of the primary virtual bridges with which the at least one of the backup virtual bridges is associated, the at least one of the backup virtual bridges transmits and receives the data packets over the network via the selected one of the primary virtual bridges over the single secondary virtual connection. Preferably, each of the primary virtual bridges is adapted to maintain a respective media access control (MAC) table, and to forward the data packets in accordance with entries in the MAC table, and wherein each of the primary virtual bridges is adapted, upon detecting the failure of the at least one of the primary virtual bridges, to update the entries in the respective MAC table that point to the at least one of the primary virtual bridges so as to point instead to the selected one of the primary virtual bridges.
- There is also provided, in accordance with a preferred embodiment of the present invention, a method for data communication, including:
- interconnecting a plurality of primary virtual bridges using primary virtual connections through a network;
- linking the primary virtual bridges to edge devices, so as to enable the edge devices to transmit and receive data packets over the network via the primary virtual connections;
- associating a backup virtual bridge with at least a first primary bridge among the plurality of the primary virtual bridges;
- connecting the backup virtual bridge using at least one secondary virtual connection through the network to at least one of the primary virtual bridges other than the first primary virtual bridge; and
- upon a failure of the first primary virtual bridge, transmitting and receiving the data packets to and from the edge devices via the at least one secondary virtual connection using the backup virtual bridge in place of the first primary virtual bridge.
- The present invention will be more fully understood from the following detailed description of the preferred embodiments thereof, taken together with the drawings in which:
-
FIG. 1 is a block diagram that schematically illustrates a VPN with a protection scheme in accordance with a preferred embodiment of the present invention; and -
FIG. 2 is a block diagram that schematically illustrates a detail of a VPN with a protection scheme in accordance with an alternative embodiment of the present invention. -
FIG. 3 is a block diagram that schematically illustrates a VPN with a protection scheme in accordance with an alternative embodiment of the present invention. -
FIG. 1 is a block diagram that schematically illustrates aVPN 20 with a hierarchical VPLS topology, implementing a protection scheme in accordance with a preferred embodiment of the present invention.VPN 20 is built around a virtual private LAN service (VPLS), operating within anetwork 22, typically an IP or MPLS network. The VPLS is based onvirtual bridges PWs network 22. Although for clarity of illustration,network 22 includes only a small number of PEs and represents only a single VPLS instance, the principles embodied in this network may be extended in a straightforward manner to larger networks and to multiple VPLS instances. - Three primary
virtual bridges PW connections 70. Typically, the PW connections comprise MPLS tunnels, but they may alternatively comprise virtual connections of other types, such as GRE or L2TP tunnels. Each of theprimary core nodes redundant backup connections 72. Each standby core node has a topology identical to its corresponding primary core node. For example,standby core node 36 has the same topology image asprimary core node 30. Each of the primary and standby core nodes is connected to all the other core nodes in the network except for the standby or primary core node with which it is paired. Anoptional connection 79 between a primary core node and its corresponding standby core node may also be included, as described hereinbelow. - The core nodes are configured to support a split horizon model.
Connections edge nodes FIG. 1 . For the sake of simplicity in this figure, only two edge nodes are shown to be connected to each core node. Edge nodes are in turn connected to user terminals viaphysical interfaces 78, which are typically Ethernet interfaces, but may alternatively be interfaces of other types, such as frame relay or ATM circuits. The VPLS and LAN topologies shown inFIG. 1 are chosen by way of example, and the principles of the present invention may be applied, mutatis mutandis, to alternative VPLS and LAN topologies, as well. - If a primary core node fails, all
connections Backup connections primary core node 30 fails,edge nodes PW connections 74 withprimary core node 30, begin instead to communicate withstandby core node 36 throughPW connections 76. The other core nodes (typicallyprimary core nodes standby core nodes backup PW connections 72 to communicate withstandby core node 36. - Since the topological position of
standby core node 36 is identical to that ofprimary core node 30, the remaining nodes in the network may continue to use the PW associations in their MAC tables that they learned before the failure, except that the tables now point to the backup connections instead of the failed primary connections. The other nodes simply redirect all packets that were supposed to be sent to the failedprimary core node 30 to thestandby core node 36 that protects it. Detection of and response to core node failure proceeds as follows: - Core node failures are initially detected by edge nodes, using either existing signaling protocols (such as “hello” messages provided by the Label Distribution Protocol—LDP), or using special “ping” operations or OAM (operations, administration, and management) connectivity verification if such a signaling protocol is not available or if faster response is required. Some special network topologies, such as Resilient Packet Rings (RPR), have built-in topology discovery protocols, enabling very fast detection of node failures.
- Upon noticing the failure of a primary core node, all the edge nodes that are connected through point-to-point PWs to the failed primary core node begin communicating through the corresponding standby core node. The standby core node, which is “always on,” then begins relaying the traffic it receives from the edge nodes. Other core nodes in the network, upon receiving this traffic from the standby core node, stop communicating through the failed primary core node and being communicating instead through the corresponding standby core node. Note that this protection scheme does not rely on any special communication protocol between a primary core node and its corresponding standby core node. If a suitable signaling protocol is available, however, between the primary and standby core nodes (like the LDP “hello” or “ping” methods noted above), faster recovery of the network may be possible.
- For example, if
primary core node 30 fails,edge nodes Edge nodes standby core node 36.Standby core node 36 relays the traffic to other core nodes in the network. Upon receiving this traffic, the other core nodes in the network begin redirecting traffic formerly directed toprimary core node 30, to flow throughstandby core node 36 instead. - A simple communications protocol for synchronizing MAC table databases between each pair of primary and standby core nodes can be invoked regularly to update the standby core node with the current MAC forwarding table stored in the corresponding primary core node. In this way, if a primary core node fails, the MAC table database of the corresponding standby core node is closely synchronized with the MAC table database of the failed node, and flooding caused by unknown MAC addresses is limited to the MAC addresses learned by the failed node since the last synchronization.
- Networks designed in accordance with the present invention can handle certain multiple core node failures, on the condition that at least one node from each pair of primary and standby core nodes does not fail. For example, if
primary core node 30 fails,edge node 50 can stop communicating withcore node 30 through point-to-point PW connection 74, and instead begin communicating withstandby core node 36 through backup point-to-point PW connection 76. Ifprimary core node 34 now also fails, the remaining active core nodes, includingstandby core node 36, will switch to communicating throughPW 72 withstandby core node 40. In thissituation edge node 50 can still communicate withedge node 58 through the backup connections and nodes. - Alternatively, instead of a one-to-one pairing of primary and standby core nodes, a single standby core node can be assigned to protect multiple primary core nodes, thus reducing the number of core nodes and the number of bi-directional connections in the core side of the network. This approach may be desirable in large networks, where the number of connections may be high. For example, in the absence of
standby core node 36,node 40 may be used to protect against failure ofprimary core node 30, as well asprimary core node 34. In this case,edge nodes backup connections 76 tonode 40. Upon detecting a failure ofnode 30,nodes node 30 tonode 40, instead. This change in topology, however, may require either more complicated MAC database coordination between the core nodes, or MAC table clearing after a failure occurs, which may cause packet flooding until the MAC learning database is re-stabilized. - After failure, if a primary core node becomes active again, a number of methods may be used for restoring traffic to it if desired. For example, the standby cores node may use a standard or dedicated signaling protocol to detect that the primary core node has again become active. In this case, the corresponding standby core node may issue a command to all the edge nodes that have point-to-point PW connections with the primary core node, instructing them to revert to using the connections with the primary core node. This approach has the benefit of making possible a synchronized topology change, avoiding a situation in which some edge nodes direct traffic through the primary core node, while other edge nodes direct traffic through the corresponding standby core node.
- An alternative method of restoration of traffic to a primary core node is as follows: Once the primary core node becomes active again, the signaling of network connections between each edge node and the primary core node is re-established. Upon noticing this signaling, each edge node can begin to use its connection to the primary core node instead of the connection to the standby core node. In other words, restoration of traffic to the primary core node is carried out by a similar mechanism to that used to divert the traffic to the standby core node when the primary core node fails. In this case, however, topology recovery may be not synchronized over the whole network, so that some core nodes may continue sending traffic through the standby node for a while. The edge nodes should be therefore capable of receiving packets simultaneously from both the standby and the primary core nodes, while sending upstream packets from users to only one of these core nodes.
- To protect against a single connection failure between an edge node and a core node, it is useful to add an additional point-to-
point connection 79, preferably a PW connection, between each primary core node and its corresponding standby core node. These additional connections can be used to bridge between different edge nodes connected by point-to-point PW connections to the same primary and standby core nodes, as follows: - If a connection between an edge node and a primary core node fails, the edge node will start to use the corresponding standby core node, even if the primary core node itself has not failed. Thus, it may occur that some edge nodes continue to communicate with the primary core node while other edge nodes communicate with the corresponding standby core node.
Layer 2 connectivity is still maintained between all the edge nodes, however, through the use ofadditional connection 79 between the primary and standby core nodes. If such an additional connection is used, the corresponding standby core node should typically not send traffic toward the full mesh ofconnections 72 unless the primary core node itself has failed. -
FIG. 2 is a block diagram that schematically shows a detail ofVPN 20, illustrating an alternative configuration of the edge nodes, in accordance with a preferred embodiment of the present invention. The figure shows a pair of corresponding primary andstandby core nodes connections connections Edge nodes core nodes connections additional connections 90 between all the edge nodes. Alternatively, other VPLS and LAN topologies may be used to connect the edge nodes to the core nodes, as well, as will be apparent to those skilled in the art. - As in the embodiment of
FIG. 1 , in normal operation,edge nodes connections 74 withprimary core node 80, but in this case they communicate throughconnections 90 among themselves. Ifprimary core node 80 fails,edge nodes backup connections 76 with the correspondingstandby core node 82. -
FIG. 3 is a block diagram that schematically showsVPN 20 in an alternative configuration, in accordance with a preferred embodiment of the present invention. The motivation for this configuration is to lower the number of connections in the core ofnetwork 22, at the cost of reduced immunity to multiple nodes failure. Althoughnormal connections 70 are configured as in the preceding embodiment, each of the standby core nodes in the present embodiment is connected by only asingle backup connection 72 to one of the primary core nodes. In the absence of any failure, the operation of the network is identical to that described earlier. If one of the primary core nodes fails, however, forexample node 30, the spokes attached to it start to usestandby core node 36, as described above. The topology image of the network is now changed, and the other core nodes must now communicate withnode 36 throughnode 34, rather than directly. - The other primary core nodes may adjust to the change in topology in various ways. In one preferred embodiment, when the other nodes detect the failure, they simply flush the MAC table database entries associated with
connections 70 that were used to communicate withnode 30. In another preferred embodiment, each node knows in advance which node is on the alternative path to the standby core node corresponding to each of the primary core nodes. In this case, the other core nodes automatically re-associate the MAC addresses that were previously associated with the connection to the failed node, so that these addresses are associated instead with the connection to the node on the alternative path. (These new associations in the MAC table are in addition to the already known MAC addresses learned normally on the same connection.) Continuing with the above example, prior to the failure innode 30,node 32 will have learned to associate one set of MAC addresses withconnection 70 tonode 34, and to associate another set withconnection 70 tonode 30.Node 32 also knows (by means of configuration settings) that in case of failure innode 30, the correspondingstandby node 36 is to be accessed throughnode 34. Therefore, when the failure occurs,node 32 simply combines the two sets of MAC addresses into one set, which is associated with the connection tonode 34. - Although
network 22, as described hereinabove, uses certain particular protocols for communication routing and tunneling, the principles of the present invention may similarly be applied using protocols and virtual bridges of other types. It will thus be appreciated that the preferred embodiments described above are cited by way of example, and that the present invention is not limited to what has been particularly shown and described hereinabove. Rather, the scope of the present invention includes both combinations and subcombinations of the various features described hereinabove, as well as variations and modifications thereof which would occur to persons skilled in the art upon reading the foregoing description and which are not disclosed in the prior art.
Claims (24)
1. A date communication network, comprising;
a plurality of primary virtual bridges, interconnected by primary virtual connections so as to transmit and receive data packets over the network to and from edge devices connected thereto, wherein the primary virtual connections define a respective primary topology image for each of the primary virtual bridges; and
a corresponding plurality of backup virtual bridges, wherein each of the backup virtual bridges is paired with a corresponding one of the primary virtual bridges and is connected to the other primary virtual bridges by secondary virtual connections that are identical to the primary virtual connections of the corresponding one of the primary virtual bridges, thus defining a respective secondary topology image that is identical to the respective primary topology image of the corresponding one of the primary virtual bridges,
wherein upon a failure of the corresponding one of the primary virtual bridges with which it is associated, each of the backup virtual bridges forwards and receives the data packets over the network via the secondary virtual connections in place of the corresponding one of the primary virtual bridges.
2. The network according to claim 1 , wherein each of the primary and backup virtual bridges is adapted to maintain a respective media access control (MAC) table, and to forward the data packets in accordance with entries in the MAC table.
3. The network according to claim 2 , wherein each of the primary virtual bridges is adapted, upon detecting the failure of one of the primary virtual bridges, to update the entries in the respective MAC table that point to the one of the primary virtual bridges so as to point instead to the corresponding one of the backup virtual bridges.
4. The network according to claim 2 , wherein each of the backup virtual bridges is adapted, following the failure of the corresponding one of the primary virtual bridges, to update the entries in the respective MAC table using a MAC learning process.
5. The network according to claim 4 , wherein each of the backup virtual bridges is adapted, while the corresponding one of the primary virtual bridges with which it is paired is operational, to periodically synchronize its MAC table with the MAC table of the corresponding one of the primary virtual bridges.
6. The network according to claim 1 , wherein the primary and backup virtual bridges are adapted to transmit the packets over the network by tunneling through the network.
7. The network according to claim 6 , wherein the primary and backup virtual bridges are arranged to transmit the packets using a virtual private LAN service (VPLS).
8. The network according to claim 7 , wherein the primary and backup virtual bridges are adapted to serve as provider edge (PE) devices, and to transmit the packets over pseudo-wires (PWs) connecting to the edge devices.
9. The network according to claim 1 , wherein the primary virtual connections define a first full mesh of the primary virtual bridges, and wherein each of the backup virtual bridges is connected by the secondary virtual connections to both the primary virtual bridges and to the other backup virtual bridges so as to define a second full mesh of the backup virtual bridges and a third full mesh between each one of the backup virtual bridges and the primary virtual bridges, except for the corresponding one of the primary virtual bridges with which the backup virtual bridge is paired.
10. The network according to claim 1 , wherein each of the backup virtual bridges is connected by secondary virtual connections to both the primary virtual bridges and to the other backup virtual bridges, so that the primary and secondary virtual connections define a full mesh of all the primary and backup virtual bridges.
11. The network according to claim 1 , wherein each of the edge devices is connected both to a respective one of the backup virtual bridges and to the corresponding one of the primary virtual bridges with which the respective one of the backup virtual bridges is paired, so that upon detecting the failure of the corresponding one of the primary virtual bridges, the edge devices communicate with the network through the respective one of the backup virtual bridges instead of the corresponding one of the primary virtual bridges.
12. The network according to claim 11 , wherein the primary virtual bridges are adapted, upon receiving packets sent by the edge devices through the backup virtual bridge, to communicate with the respective one of the backup virtual bridges instead of the one of the primary virtual bridges in which the failure occurred.
13. A method for data communication, comprising:
interconnecting a plurality of primary virtual bridges using primary virtual connections through a network, wherein the primary virtual connections define a respective primary topology image for each of the primary virtual bridges;
linking the primary virtual bridges to edge devices, so as to enable the edge devices to transmit and receive data packets over the network via the primary virtual connections;
associating a plurality of backup virtual bridges with the plurality of the primary virtual bridges, such that each of the backup virtual bridges is paired with a corresponding one of the primary virtual bridges;
configuring secondary virtual connections between the backup virtual bridges and the primary virtual bridges such that each of the backup virtual bridges is connected to the other primary virtual bridges by secondary virtual connections that are identical to the primary virtual connections of the corresponding one of the primary virtual bridges, thus defining a respective secondary topology image that is identical to the respective primary topology image of the corresponding one of the primary virtual bridges; and
upon a failure of the corresponding one of the primary virtual bridges, forwarding and receiving the data packets to and from the edge devices via the secondary virtual connections using one of the backup virtual bridges in place of the corresponding one of the primary virtual bridges.
14. The method according to claim 13 , and comprising maintaining a respective media access control (MAC) table at each of the primary and backup virtual bridges, wherein forwarding the data packets comprises forwarding the data packets in accordance with entries in the respective MAC table.
15. The method according to claim 14 , wherein forwarding the data packets comprises, upon detecting the failure of one of the primary virtual bridges, updating the entries that point to the one of the primary virtual bridges in the respective MAC table of others of the primary virtual bridges so as to point instead to the corresponding one of the backup virtual bridges.
16. The method according to claim 14 , wherein forwarding the data packets comprises, following the failure of the corresponding one of the primary virtual bridges, updating the entries in the respective MAC table of the one of the backup virtual bridges using a MAC learning process.
17. The method according to claim 16 , and comprising, while the corresponding one of the primary virtual bridges with which it is paired is operational, periodically synchronizing the MAC table of each of the backup virtual bridges with the MAC table of the corresponding one of the primary virtual bridges.
18. The method according to claim 13 , wherein forwarding and receiving the packets comprises transmitting the packets by tunneling through the network.
19. The method according to claim 18 , wherein transmitting the packets comprises forwarding and receiving the packets using a virtual private LAN service (VPLS).
20. The method according to claim 19 , wherein the primary and backup virtual bridges are adapted to serve as provider edge (PE) devices, and wherein forwarding and receiving the packets comprises forwarding and receiving the packets over pseudo-wires (PWs) connecting to the PE devices.
21. The method according to claim 13 , wherein interconnecting the plurality of primary virtual bridges comprises arranging the primary virtual connections to define a first full mesh of the primary virtual bridges, and wherein configuring the secondary virtual connections comprises arranging the secondary virtual connections to define a second full mesh of the backup virtual bridges and a third full mesh between each one of the backup virtual bridges and the primary virtual bridges, except for the corresponding one of the primary virtual bridges with which the backup virtual bridges is paired.
22. The method according to claim 13 , wherein interconnecting the plurality of primary virtual bridges and configuring the secondary virtual connections comprise configuring the primary and secondary virtual connections so as to define a full mesh of all the primary and secondary virtual bridges.
23. The method according to claim 13 , wherein configuring the secondary virtual connections comprises connecting each of the edge devices to a respective one of the backup virtual bridges, in addition to the corresponding one of the primary virtual bridges with which the respective one of the backup virtual bridges is paired, and wherein forwarding and receiving the data packets comprises detecting the failure of the corresponding one of the primary virtual bridges at one or more of the edge devices, and initiating communication from the one or more of the edge devices to the one of the backup virtual bridges in response to detecting the failure.
24. The method according to claim 23 , wherein forwarding and receiving the data packets further comprises receiving at the primary virtual bridges the data packets sent by the edge devices through the one of the backup virtual bridges, and in response to receiving the data packets, diverting communication traffic from the primary virtual bridges to the one of the backup virtual bridges.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/745,303 US20070206492A1 (en) | 2003-01-07 | 2007-05-07 | Hierarchical virtual private lan service protection scheme |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/337,382 US7283465B2 (en) | 2003-01-07 | 2003-01-07 | Hierarchical virtual private LAN service protection scheme |
US11/745,303 US20070206492A1 (en) | 2003-01-07 | 2007-05-07 | Hierarchical virtual private lan service protection scheme |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/337,382 Continuation US7283465B2 (en) | 2003-01-07 | 2003-01-07 | Hierarchical virtual private LAN service protection scheme |
Publications (1)
Publication Number | Publication Date |
---|---|
US20070206492A1 true US20070206492A1 (en) | 2007-09-06 |
Family
ID=32681229
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/337,382 Active 2024-10-02 US7283465B2 (en) | 2003-01-07 | 2003-01-07 | Hierarchical virtual private LAN service protection scheme |
US11/745,303 Abandoned US20070206492A1 (en) | 2003-01-07 | 2007-05-07 | Hierarchical virtual private lan service protection scheme |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/337,382 Active 2024-10-02 US7283465B2 (en) | 2003-01-07 | 2003-01-07 | Hierarchical virtual private LAN service protection scheme |
Country Status (1)
Country | Link |
---|---|
US (2) | US7283465B2 (en) |
Cited By (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040151181A1 (en) * | 2003-02-04 | 2004-08-05 | Chu Thomas P. | Methods and systems for providing MPLS-based layer-2 virtual private network services |
US20050271035A1 (en) * | 2004-06-07 | 2005-12-08 | Native Networks Technologies, Ltd. | Method for enabling multipoint network services over a ring topology network |
US20060080421A1 (en) * | 2003-09-03 | 2006-04-13 | Sbc Knowledge Ventures, L.P. | Method and system for automating membership discovery in a distributed computer network |
US20060120279A1 (en) * | 2003-09-10 | 2006-06-08 | Yasuyuki Mitsumori | Node redundancy method, interface card, interface device, node device, and packet ring network system |
US20080175234A1 (en) * | 2005-09-30 | 2008-07-24 | Huawei Technologies Co., Ltd. | Method and device for protective switching of pseudo-wires on packet switching network |
US7649904B1 (en) * | 2008-02-20 | 2010-01-19 | Juniper Networks, Inc. | Seamless split-horizon flooding of layer two (L2) network traffic on non-native and mixed architectures |
US7652984B1 (en) * | 2007-03-14 | 2010-01-26 | Cello Partnership | Geographic redundancy and resource optimization for security gateways in wireless networks |
US7801150B1 (en) * | 2006-02-14 | 2010-09-21 | Juniper Networks, Inc. | Multiple media access control (MAC) addresses |
US20110058518A1 (en) * | 2009-09-09 | 2011-03-10 | Comtech Ef Data Corp. | Multi-Channel Single Carrier Per Channel (SCPC) Systems and Related Methods |
US7965623B1 (en) * | 2002-10-15 | 2011-06-21 | Garrettcom, Inc. | LAN switch with rapid fault recovery |
US7990993B1 (en) * | 2008-02-20 | 2011-08-02 | Juniper Networks, Inc. | Platform-independent control plane and lower-level derivation of forwarding structures |
US20130212394A1 (en) * | 2010-06-02 | 2013-08-15 | Hangzhou H3C Technologies Co., Ltd. | Method for 802.1X Authentication, Access Device and Access Control Device |
WO2014040553A1 (en) * | 2012-09-14 | 2014-03-20 | 中兴通讯股份有限公司 | Method, system and apparatus for establishing communication link |
US20140321330A1 (en) * | 2011-09-19 | 2014-10-30 | Telefonaktiebolaget L M Ericsson (Publ) | Controller placement for fast failover in the split architecture |
US8908686B1 (en) | 2010-12-08 | 2014-12-09 | Juniper Networks, Inc. | Distributed generation of hierarchical multicast forwarding structures |
US8948174B2 (en) | 2011-06-29 | 2015-02-03 | Juniper Networks, Inc. | Variable-based forwarding path construction for packet processing within a network device |
CN109510771A (en) * | 2017-09-15 | 2019-03-22 | 北京华为数字技术有限公司 | Multicast transmission method and relevant device |
Families Citing this family (95)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7830787B1 (en) | 2001-09-25 | 2010-11-09 | Cisco Technology, Inc. | Flooding control for multicast distribution tunnel |
US7283465B2 (en) | 2003-01-07 | 2007-10-16 | Corrigent Systems Ltd. | Hierarchical virtual private LAN service protection scheme |
US7570648B2 (en) * | 2003-02-03 | 2009-08-04 | At&T Intellectual Property I, L.P. | Enhanced H-VPLS service architecture using control word |
US7643424B2 (en) * | 2003-03-22 | 2010-01-05 | At&T Intellectual Property L, L.P. | Ethernet architecture with data packet encapsulation |
US7826452B1 (en) * | 2003-03-24 | 2010-11-02 | Marvell International Ltd. | Efficient host-controller address learning in ethernet switches |
US7613201B1 (en) * | 2003-04-18 | 2009-11-03 | Rmi Corporation | Stacked network switch using resilient packet ring communication protocol |
US7792987B1 (en) * | 2003-04-21 | 2010-09-07 | Juniper Networks, Inc. | Supporting virtual private networks using a first network topology for forwarding and a subset of the first network topology or a smaller topology for signaling |
US7558194B2 (en) * | 2003-04-28 | 2009-07-07 | Alcatel-Lucent Usa Inc. | Virtual private network fault tolerance |
US7813345B2 (en) * | 2003-06-05 | 2010-10-12 | At&T Intellectual Property I, L.P. | MAC learning using VC-LSP dedicated for broadcast and unknown frames |
US7489681B1 (en) * | 2003-06-13 | 2009-02-10 | Redback Networks, Inc. | Method and apparatus for virtual circuit routes |
US8028050B2 (en) * | 2003-06-13 | 2011-09-27 | Alcatel-Lucent Usa Inc. | Restoration for virtual private networks |
US8737200B1 (en) * | 2003-06-25 | 2014-05-27 | Rockstar Consortium Us Lp | MPLS/IP pseudo-wire and layer-2 virtual private network resiliency |
US7483374B2 (en) * | 2003-08-05 | 2009-01-27 | Scalent Systems, Inc. | Method and apparatus for achieving dynamic capacity and high availability in multi-stage data networks using adaptive flow-based routing |
US8718057B1 (en) * | 2004-01-20 | 2014-05-06 | Nortel Networks Limited | Ethernet LAN service enhancements |
US7925778B1 (en) | 2004-02-13 | 2011-04-12 | Cisco Technology, Inc. | Method and apparatus for providing multicast messages across a data communication network |
US8392509B1 (en) * | 2004-03-26 | 2013-03-05 | Cisco Technology, Inc. | Ethernet local management interface (E-LMI) |
US20050220096A1 (en) | 2004-04-06 | 2005-10-06 | Robert Friskney | Traffic engineering in frame-based carrier networks |
US8923292B2 (en) | 2004-04-06 | 2014-12-30 | Rockstar Consortium Us Lp | Differential forwarding in address-based carrier networks |
US8422500B2 (en) | 2004-07-02 | 2013-04-16 | Rockstar Consortium Us Lp | VLAN support of differentiated services |
WO2006008885A1 (en) * | 2004-07-16 | 2006-01-26 | Brother Kogyo Kabushiki Kaisha | Connection mode control device, connection mode control method, and connection mode control program |
US8619774B2 (en) * | 2004-10-26 | 2013-12-31 | Cisco Technology, Inc. | Method and apparatus for providing multicast messages within a virtual private network across a data communication network |
US8086755B2 (en) * | 2004-11-29 | 2011-12-27 | Egenera, Inc. | Distributed multicast system and method in a network |
US20060133383A1 (en) * | 2004-12-22 | 2006-06-22 | Russell Homer | Communications system with scan table identification |
US7590130B2 (en) * | 2004-12-22 | 2009-09-15 | Exar Corporation | Communications system with first and second scan tables |
US20060182113A1 (en) * | 2005-02-17 | 2006-08-17 | Lucent Technologies Inc. | Automatic discovery of pseudo-wire peer addresses in ethernet-based networks |
US7668139B2 (en) * | 2005-03-23 | 2010-02-23 | Intel Corporation | Mobile handover utilizing multicast in a multi-protocol label switching (MPLS)-based network |
CN100407725C (en) * | 2005-04-15 | 2008-07-30 | 华为技术有限公司 | Method for realizing multi-protocol tag exchange bidirectional protection switching |
CN100502303C (en) * | 2005-04-15 | 2009-06-17 | 华为技术有限公司 | Method for managing fault of Ethernet and multi-protocol tag exchange network interconnection |
US8213435B2 (en) | 2005-04-28 | 2012-07-03 | Cisco Technology, Inc. | Comprehensive model for VPLS |
US8194656B2 (en) | 2005-04-28 | 2012-06-05 | Cisco Technology, Inc. | Metro ethernet network with scaled broadcast and service instance domains |
US9088669B2 (en) * | 2005-04-28 | 2015-07-21 | Cisco Technology, Inc. | Scalable system and method for DSL subscriber traffic over an Ethernet network |
US7835370B2 (en) * | 2005-04-28 | 2010-11-16 | Cisco Technology, Inc. | System and method for DSL subscriber identification over ethernet network |
US8018854B1 (en) * | 2005-05-03 | 2011-09-13 | Eastern Research Inc. | Facility and equipment testing for packet networks |
US8094663B2 (en) * | 2005-05-31 | 2012-01-10 | Cisco Technology, Inc. | System and method for authentication of SP ethernet aggregation networks |
US8175078B2 (en) * | 2005-07-11 | 2012-05-08 | Cisco Technology, Inc. | Redundant pseudowires between Ethernet access domains |
US7855950B2 (en) * | 2005-08-01 | 2010-12-21 | Cisco Technology, Inc. | Congruent forwarding paths for unicast and multicast traffic |
CN1913523A (en) * | 2005-08-09 | 2007-02-14 | 华为技术有限公司 | Method for implementing layer level virtual private exchange service |
US9088619B2 (en) * | 2005-09-14 | 2015-07-21 | Cisco Technology, Inc. | Quality of service based on logical port identifier for broadband aggregation networks |
US8369330B2 (en) * | 2005-10-05 | 2013-02-05 | Rockstar Consortium LP | Provider backbone bridging—provider backbone transport internetworking |
US7738401B2 (en) * | 2005-10-20 | 2010-06-15 | At&T Intellectual Property I, L.P. | System and method for overlaying a hierarchical network design on a full mesh network |
US7808930B2 (en) * | 2005-10-26 | 2010-10-05 | Cisco Technology, Inc. | Dynamic multipoint tree rearrangement |
US8199637B2 (en) * | 2005-11-16 | 2012-06-12 | Orckit Corrigent, Ltd. | VPLS remote failure indication |
US8441919B2 (en) * | 2006-01-18 | 2013-05-14 | Cisco Technology, Inc. | Dynamic protection against failure of a head-end node of one or more TE-LSPs |
US8284656B2 (en) * | 2006-04-28 | 2012-10-09 | Alcatel Lucent | System and method for resilient VPLS over multi-nodal APS protected provider edge nodes |
US7715309B2 (en) * | 2006-05-24 | 2010-05-11 | At&T Intellectual Property I, L.P. | Method and apparatus for reliable communications in a packet network |
FR2906426A1 (en) * | 2006-09-25 | 2008-03-28 | France Telecom | SYSTEM FOR SECURING ACCESS TO A DESTINATION OF A VIRTUAL PRIVATE NETWORK |
WO2008043374A1 (en) * | 2006-10-09 | 2008-04-17 | Telefonaktiebolaget Lm Ericsson (Publ) | Resiliency schemes in communications networks |
JP2008113955A (en) * | 2006-11-07 | 2008-05-22 | Aruze Corp | Game machine |
JP4880761B2 (en) * | 2006-12-29 | 2012-02-22 | テレフオンアクチーボラゲット エル エム エリクソン(パブル) | Data provision method |
US8504727B2 (en) * | 2007-01-17 | 2013-08-06 | Rockstar Consortium Us Lp | Method and apparatus for interworking ethernet and MPLS networks |
US7975024B2 (en) * | 2007-02-14 | 2011-07-05 | Yakov Nudler | Virtual personal computer access over multiple network sites |
JP4946599B2 (en) * | 2007-04-24 | 2012-06-06 | 富士通株式会社 | Ring node and redundancy method |
US8804534B2 (en) * | 2007-05-19 | 2014-08-12 | Cisco Technology, Inc. | Interworking between MPLS/IP and Ethernet OAM mechanisms |
US8054840B2 (en) * | 2007-06-12 | 2011-11-08 | International Business Machines Corporation | Data center virtual local area network system and method |
US8531941B2 (en) * | 2007-07-13 | 2013-09-10 | Cisco Technology, Inc. | Intra-domain and inter-domain bridging over MPLS using MAC distribution via border gateway protocol |
US9276769B2 (en) * | 2007-09-19 | 2016-03-01 | Coriant Operations, Inc. | Circuit bundle for resiliency/protection of circuits |
JP4729119B2 (en) * | 2007-10-25 | 2011-07-20 | 富士通株式会社 | Communication device in label switching network |
US8325706B2 (en) * | 2007-11-26 | 2012-12-04 | Verizon Patent And Licensing Inc. | Hierarchical segmented label switched paths |
US8279867B2 (en) * | 2008-03-02 | 2012-10-02 | Jeffrey Alan Carley | Method and apparatus for reducing flood traffic in switches |
US7969866B2 (en) * | 2008-03-31 | 2011-06-28 | Telefonaktiebolaget L M Ericsson (Publ) | Hierarchical virtual private LAN service hub connectivity failure recovery |
JP5157685B2 (en) * | 2008-07-02 | 2013-03-06 | 日本電気株式会社 | COMMUNICATION SYSTEM, NETWORK DEVICE, COMMUNICATION RECOVERY METHOD USED FOR THEM, AND PROGRAM THEREOF |
US7969981B2 (en) * | 2008-09-02 | 2011-06-28 | Cisco Technology, Inc. | System and method for multicasting in an internet protocol virtual private network environment |
JP2010088080A (en) * | 2008-10-03 | 2010-04-15 | Fujitsu Ltd | Communication apparatus and communication method |
US8385245B2 (en) * | 2008-11-13 | 2013-02-26 | Cisco Technology, Inc. | System and method for multicasting in a network environment |
US8064338B2 (en) * | 2008-12-31 | 2011-11-22 | Telefonaktiebolaget L M Ericsson (Publ) | HVPLS hub connectivity failure recovery with dynamic spoke pseudowires |
FI122403B (en) * | 2009-01-14 | 2011-12-30 | Tellabs Oy | Method, system and apparatus for relaying data transmission frames |
US7961599B2 (en) * | 2009-03-03 | 2011-06-14 | Alcatel Lucent | Pseudowire tunnel redundancy |
US8325598B2 (en) * | 2009-05-20 | 2012-12-04 | Verizon Patent And Licensing Inc. | Automatic protection switching of virtual connections |
US9197550B2 (en) * | 2009-12-17 | 2015-11-24 | Alcatel Lucent | Method and device for determining forwarding rule for data packet |
US20110170403A1 (en) * | 2010-01-08 | 2011-07-14 | Futurewei Technologies, Inc. | Service Movement in Link State Controlled Layer Two Networks |
US8966040B2 (en) | 2010-07-06 | 2015-02-24 | Nicira, Inc. | Use of network information base structure to establish communication between applications |
US9680750B2 (en) | 2010-07-06 | 2017-06-13 | Nicira, Inc. | Use of tunnels to hide network addresses |
US9075661B2 (en) | 2010-10-20 | 2015-07-07 | Microsoft Technology Licensing, Llc | Placing objects on hosts using hard and soft constraints |
US8799453B2 (en) | 2010-10-20 | 2014-08-05 | Microsoft Corporation | Managing networks and machines for an online service |
US8296267B2 (en) | 2010-10-20 | 2012-10-23 | Microsoft Corporation | Upgrade of highly available farm server groups |
US8751656B2 (en) | 2010-10-20 | 2014-06-10 | Microsoft Corporation | Machine manager for deploying and managing machines |
US8386501B2 (en) | 2010-10-20 | 2013-02-26 | Microsoft Corporation | Dynamically splitting multi-tenant databases |
US8417737B2 (en) | 2010-10-20 | 2013-04-09 | Microsoft Corporation | Online database availability during upgrade |
US8514746B1 (en) * | 2010-11-08 | 2013-08-20 | Juniper Networks, Inc. | Priority inversion with spanning tree protocol to trigger path switching |
US8850550B2 (en) | 2010-11-23 | 2014-09-30 | Microsoft Corporation | Using cached security tokens in an online service |
US9721030B2 (en) | 2010-12-09 | 2017-08-01 | Microsoft Technology Licensing, Llc | Codeless sharing of spreadsheet objects |
IL215009A0 (en) * | 2011-09-06 | 2011-10-31 | Eci Telecom Ltd | Technique for managing e-tree services in mpls networks |
JP6035726B2 (en) * | 2011-11-02 | 2016-11-30 | 富士通株式会社 | Connection control apparatus, storage system, and connection control apparatus control method |
EP2748750B1 (en) | 2011-11-15 | 2020-03-18 | Nicira Inc. | Firewalls in logical networks |
US9292351B2 (en) * | 2012-06-15 | 2016-03-22 | Verizon Patent And Licensing Inc. | Distributed fabric architecture in a cloud computing environment |
US9036638B2 (en) * | 2012-08-09 | 2015-05-19 | International Business Machines Corporation | Avoiding unknown unicast floods resulting from MAC address table overflows |
CN103560869B (en) * | 2013-09-10 | 2016-10-12 | 杭州华三通信技术有限公司 | A kind of VPLS link switching, auxiliary switching device and method |
US10171336B2 (en) * | 2015-12-16 | 2019-01-01 | Telefonaktiebolaget Lm Ericsson (Publ) | Openflow configured horizontally split hybrid SDN nodes |
CN107086958B (en) * | 2016-02-16 | 2020-02-18 | 中国移动通信集团江苏有限公司 | Data transmission method, wap gateway and system |
US10412009B2 (en) * | 2016-03-10 | 2019-09-10 | Arista Networks, Inc. | Next hop groups |
US10057334B2 (en) * | 2016-11-14 | 2018-08-21 | Futurewei Technologies, Inc. | Quad full mesh and dimension driven network architecture |
CN108206759B (en) * | 2016-12-20 | 2021-02-09 | 华为技术有限公司 | Method, equipment and system for forwarding message |
US20230078931A1 (en) * | 2020-02-28 | 2023-03-16 | Nippon Telegraph And Telephone Corporation | Network system and network switching method |
US11240098B2 (en) * | 2020-04-03 | 2022-02-01 | Charter Communications Operating, Llc | Automatic local gateway router backup of a network gateway router |
CN114500168B (en) * | 2021-12-27 | 2023-12-12 | 浙江中控技术股份有限公司 | Distributed control system cross-wide area network communication method and gateway |
Citations (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6058116A (en) * | 1998-04-15 | 2000-05-02 | 3Com Corporation | Interconnected trunk cluster arrangement |
US6222820B1 (en) * | 1998-05-28 | 2001-04-24 | 3Com Corporation | Method of VCC/VPC redundancy for asynchronous transfer mode networks |
US20020024974A1 (en) * | 2000-07-31 | 2002-02-28 | Georgios Karagiannis | Jitter reduction in Differentiated Services (DiffServ) networks |
US20020118700A1 (en) * | 2001-01-09 | 2002-08-29 | Orckit Communications Ltd. | Flow allocation in a ring topology |
US20020176371A1 (en) * | 2001-05-24 | 2002-11-28 | Behnam Behzadi | Method and system for preventing transmission loops in a label switching domain |
US20030009594A1 (en) * | 2000-02-04 | 2003-01-09 | Mcelligott Adrian | Method and apparatus for identifying locale of internet users |
US20030021226A1 (en) * | 2001-07-24 | 2003-01-30 | Gal Mor | Interconnect and gateway protection in bidirectional ring networks |
US20030074469A1 (en) * | 2001-10-15 | 2003-04-17 | Alcatel | Method and apparatus for transparent LAN-to-LAN connection between two customer locations through a RPR data transport network |
US20030147345A1 (en) * | 2002-02-06 | 2003-08-07 | Nec Corporation | Multiring control method, node using the method, and control program |
US20030154315A1 (en) * | 2002-02-12 | 2003-08-14 | Robert Sultan | Spatial reuse and multi-point interconnection in bridge-interconnected ring networks |
US20040022268A1 (en) * | 2002-08-02 | 2004-02-05 | Alcatel | Method and apparatus for end-to-end connection between an RPR and an MPLS network |
US6741553B1 (en) * | 1999-12-08 | 2004-05-25 | Nortel Networks Limited | Method and system for protecting virtual traffic in a communications network |
US20040170184A1 (en) * | 2003-02-07 | 2004-09-02 | Masanori Hashimoto | RPR network system |
US20040179472A1 (en) * | 2003-03-14 | 2004-09-16 | Farid Khalilzadeh | Shared path protection method and system |
US20050226265A1 (en) * | 2003-04-24 | 2005-10-13 | Kou Takatori | Inter-ring connection device and data transfer control method |
US7062642B1 (en) * | 2000-05-20 | 2006-06-13 | Ciena Corporation | Policy based provisioning of network device resources |
Family Cites Families (58)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US2696235A (en) * | 1952-08-29 | 1954-12-07 | Roger L Toffolon | Cargo container |
US2724418A (en) * | 1953-03-02 | 1955-11-22 | Goodrich Co B F | Fluid-receiving container with volumeresponsive pressure-relief and overflow valve assembly |
BE646539A (en) * | 1963-04-19 | 1964-07-31 | ||
US3416762A (en) * | 1967-02-20 | 1968-12-17 | Richard T. Headrick | Restraining means for pillow tanks |
US3919030A (en) * | 1974-06-12 | 1975-11-11 | Rubber Dynamics Corp | Elastic storage tank and method for making the same |
US3978901A (en) * | 1975-06-20 | 1976-09-07 | Jones Walter C | Elastic storage tank |
FR2381618A1 (en) * | 1977-02-24 | 1978-09-22 | Ouest Cie | METHOD OF MANUFACTURING A FLEXIBLE SAFETY TANK FOR HYDROCARBONS, ESPECIALLY FOR INDUSTRIAL VEHICLES |
US4247678A (en) * | 1979-08-17 | 1981-01-27 | The Goodyear Tire & Rubber Company | Polyurethane derived from both an aliphatic dicarboxylic acid and an aromatic dicarboxylic acid and fuel container made therefrom |
US4668535A (en) * | 1983-06-09 | 1987-05-26 | Goodyear Aerospace Corporation | Process for preparing a fuel tank of polyurethane laminate having contiguous contrasting layers |
US4487913A (en) * | 1984-03-12 | 1984-12-11 | Goodyear Aerospace Corporation | Fuel and hydrolysis resistant polyurethane |
US4573508A (en) * | 1985-04-04 | 1986-03-04 | Goodyear Aerospace Corporation | Collapsible storage tank |
US4854481A (en) * | 1988-05-09 | 1989-08-08 | The Gates Rubber Company | Collapsible fluid storage receptacle |
US4865096A (en) * | 1988-08-16 | 1989-09-12 | American Fuel Cell And Coated Fabrics Company | Lightweight pillow tank |
US5626313A (en) * | 1989-06-02 | 1997-05-06 | Minowitz Manufacturing Company | Engine assembly including fuel storage bladder |
US5047495A (en) * | 1989-08-28 | 1991-09-10 | The G. F. Goodrich Company | Polyurethane for flexible fuel containers |
US5636358A (en) * | 1991-09-27 | 1997-06-03 | Emc Corporation | Method and apparatus for transferring data in a storage device including a dual-port buffer |
US5321393A (en) * | 1992-04-10 | 1994-06-14 | Alcatel Network Systems, Inc. | Spare card connection and switching circuitry for high-speed telecommunications interfaces |
US5199793A (en) * | 1992-05-07 | 1993-04-06 | Jackson Chad S | Collapsible storage bag |
DE9303805U1 (en) * | 1993-03-15 | 1993-06-09 | Blumenkron, Jorge Lopez, Puebla, Mx | |
US5368395A (en) * | 1993-04-13 | 1994-11-29 | Ilc Dover, Inc. | Flexible storage tank with removable inner liner |
EP0749663B1 (en) * | 1994-03-08 | 1999-12-01 | Excel Switching Corporation | Telecommunications switch with improved redundancy |
US5473599A (en) * | 1994-04-22 | 1995-12-05 | Cisco Systems, Incorporated | Standby router protocol |
JP2826468B2 (en) | 1994-04-27 | 1998-11-18 | 日本電気 株式会社 | Line switching device |
NL1002989C2 (en) * | 1996-05-02 | 1997-11-06 | Hubertus Franciscus Cornelius | Device for the storage of pumpable material and a fixing and transporting device for this. |
US5755425A (en) * | 1996-06-20 | 1998-05-26 | The United States Of America As Represented By The Secretary Of The Navy | Fitting for flexible fuel bladder |
JPH1011369A (en) * | 1996-06-27 | 1998-01-16 | Hitachi Ltd | Communication system and information processor with hot standby switching function |
US6339595B1 (en) * | 1997-12-23 | 2002-01-15 | Cisco Technology, Inc. | Peer-model support for virtual private networks with potentially overlapping addresses |
US6032194A (en) * | 1997-12-24 | 2000-02-29 | Cisco Technology, Inc. | Method and apparatus for rapidly reconfiguring computer networks |
US5967370A (en) * | 1998-03-26 | 1999-10-19 | Nettles; Jay R. | Fuel bag kit having an inflatable-deflatable fuel bag and a fuel bag storage container |
US6275493B1 (en) * | 1998-04-02 | 2001-08-14 | Nortel Networks Limited | Method and apparatus for caching switched virtual circuits in an ATM network |
US6466985B1 (en) * | 1998-04-10 | 2002-10-15 | At&T Corp. | Method and apparatus for providing quality of service using the internet protocol |
US6314106B1 (en) * | 1998-04-20 | 2001-11-06 | Alcatel Internetworking, Inc. | Receive processing for dedicated bandwidth data communication switch backplane |
US6604136B1 (en) * | 1998-06-27 | 2003-08-05 | Intel Corporation | Application programming interfaces and methods enabling a host to interface with a network processor |
US6304575B1 (en) * | 1998-08-31 | 2001-10-16 | Cisco Technology, Inc. | Token ring spanning tree protocol |
US6330229B1 (en) * | 1998-11-09 | 2001-12-11 | 3Com Corporation | Spanning tree with rapid forwarding database updates |
US6205488B1 (en) * | 1998-11-13 | 2001-03-20 | Nortel Networks Limited | Internet protocol virtual private network realization using multi-protocol label switching tunnels |
US6628624B1 (en) * | 1998-12-09 | 2003-09-30 | Cisco Technology, Inc. | Value-added features for the spanning tree protocol |
US6101964A (en) * | 1999-01-19 | 2000-08-15 | Edward R. Lesesne | Floatable auxiliary fuel tank |
US6760775B1 (en) * | 1999-03-05 | 2004-07-06 | At&T Corp. | System, method and apparatus for network service load and reliability management |
US6359858B1 (en) * | 1999-06-03 | 2002-03-19 | Fujitsu Network Communications, Inc. | Switching redundancy control |
US6879594B1 (en) * | 1999-06-07 | 2005-04-12 | Nortel Networks Limited | System and method for loop avoidance in multi-protocol label switching |
US6446131B1 (en) * | 1999-06-19 | 2002-09-03 | Hewlett-Packard Company | Bridges and other layer-two devices for forwarding MAC frames |
US6636478B1 (en) * | 2000-05-03 | 2003-10-21 | Metro Optix, Inc. | Configurable scalable communications equipment protection method system |
US6778496B1 (en) * | 2000-06-07 | 2004-08-17 | Lucent Technologies Inc. | Distributed call admission and load balancing method and apparatus for packet networks |
US6886043B1 (en) * | 2000-06-28 | 2005-04-26 | Nortel Networks Limited | Communications network |
US6765921B1 (en) * | 2000-06-28 | 2004-07-20 | Nortel Networks Limited | Communications network |
US6724880B1 (en) * | 2000-08-11 | 2004-04-20 | Nortel Networks Limited | Method and apparatus for sparing communications circuits |
US6879559B1 (en) * | 2000-10-31 | 2005-04-12 | Chiaro Networks, Ltd. | Router line card protection using one-for-N redundancy |
JP4183379B2 (en) * | 2000-11-27 | 2008-11-19 | 富士通株式会社 | Network and edge router |
US20020176450A1 (en) * | 2001-01-31 | 2002-11-28 | Sycamore Networks, Inc. | System and methods for selectively transmitting ethernet traffic over SONET/SDH optical network |
US20020110087A1 (en) * | 2001-02-14 | 2002-08-15 | David Zelig | Efficient setup of label-switched connections |
US7003690B2 (en) * | 2001-05-30 | 2006-02-21 | Juniper Networks, Inc. | Method and apparatus for redundancy switching in line cards |
US7127523B2 (en) * | 2001-07-27 | 2006-10-24 | Corrigent Systems Ltd. | Spanning tree protocol traffic in a transparent LAN |
US7647422B2 (en) * | 2001-11-06 | 2010-01-12 | Enterasys Networks, Inc. | VPN failure recovery |
US7042839B2 (en) * | 2002-02-07 | 2006-05-09 | Fujitsu Limited | Scaleable line-based protection for connection oriented communications protocols |
US6978395B2 (en) * | 2002-04-10 | 2005-12-20 | Adc Dsl Systems, Inc. | Protection switching of interface cards in communication system |
US7032135B2 (en) * | 2002-08-02 | 2006-04-18 | Corrigent Systems Ltd. | Equipment protection using a partial star architecture |
US7283465B2 (en) | 2003-01-07 | 2007-10-16 | Corrigent Systems Ltd. | Hierarchical virtual private LAN service protection scheme |
-
2003
- 2003-01-07 US US10/337,382 patent/US7283465B2/en active Active
-
2007
- 2007-05-07 US US11/745,303 patent/US20070206492A1/en not_active Abandoned
Patent Citations (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6058116A (en) * | 1998-04-15 | 2000-05-02 | 3Com Corporation | Interconnected trunk cluster arrangement |
US6222820B1 (en) * | 1998-05-28 | 2001-04-24 | 3Com Corporation | Method of VCC/VPC redundancy for asynchronous transfer mode networks |
US6741553B1 (en) * | 1999-12-08 | 2004-05-25 | Nortel Networks Limited | Method and system for protecting virtual traffic in a communications network |
US20030009594A1 (en) * | 2000-02-04 | 2003-01-09 | Mcelligott Adrian | Method and apparatus for identifying locale of internet users |
US7062642B1 (en) * | 2000-05-20 | 2006-06-13 | Ciena Corporation | Policy based provisioning of network device resources |
US20020024974A1 (en) * | 2000-07-31 | 2002-02-28 | Georgios Karagiannis | Jitter reduction in Differentiated Services (DiffServ) networks |
US20020118700A1 (en) * | 2001-01-09 | 2002-08-29 | Orckit Communications Ltd. | Flow allocation in a ring topology |
US7035279B2 (en) * | 2001-01-09 | 2006-04-25 | Corrigent Systems Ltd. | Flow allocation in a ring topology |
US20020176371A1 (en) * | 2001-05-24 | 2002-11-28 | Behnam Behzadi | Method and system for preventing transmission loops in a label switching domain |
US20030021226A1 (en) * | 2001-07-24 | 2003-01-30 | Gal Mor | Interconnect and gateway protection in bidirectional ring networks |
US20030074469A1 (en) * | 2001-10-15 | 2003-04-17 | Alcatel | Method and apparatus for transparent LAN-to-LAN connection between two customer locations through a RPR data transport network |
US20030147345A1 (en) * | 2002-02-06 | 2003-08-07 | Nec Corporation | Multiring control method, node using the method, and control program |
US20030154315A1 (en) * | 2002-02-12 | 2003-08-14 | Robert Sultan | Spatial reuse and multi-point interconnection in bridge-interconnected ring networks |
US20040022268A1 (en) * | 2002-08-02 | 2004-02-05 | Alcatel | Method and apparatus for end-to-end connection between an RPR and an MPLS network |
US20040170184A1 (en) * | 2003-02-07 | 2004-09-02 | Masanori Hashimoto | RPR network system |
US20040179472A1 (en) * | 2003-03-14 | 2004-09-16 | Farid Khalilzadeh | Shared path protection method and system |
US20050226265A1 (en) * | 2003-04-24 | 2005-10-13 | Kou Takatori | Inter-ring connection device and data transfer control method |
Cited By (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7965623B1 (en) * | 2002-10-15 | 2011-06-21 | Garrettcom, Inc. | LAN switch with rapid fault recovery |
USRE43811E1 (en) | 2002-10-15 | 2012-11-20 | Belden Inc. | LAN switch with rapid fault recovery |
US7872991B2 (en) * | 2003-02-04 | 2011-01-18 | Alcatel-Lucent Usa Inc. | Methods and systems for providing MPLS-based layer-2 virtual private network services |
US20040151181A1 (en) * | 2003-02-04 | 2004-08-05 | Chu Thomas P. | Methods and systems for providing MPLS-based layer-2 virtual private network services |
US8098665B2 (en) * | 2003-09-03 | 2012-01-17 | At&T Intellectual Property I, L.P. | Method and system for automating membership discovery in a distributed computer network |
US20060080421A1 (en) * | 2003-09-03 | 2006-04-13 | Sbc Knowledge Ventures, L.P. | Method and system for automating membership discovery in a distributed computer network |
US7447212B2 (en) * | 2003-09-03 | 2008-11-04 | At&T Intellectual Property I, L.P. | Method and system for automating membership discovery in a distributed computer network |
US20090028162A1 (en) * | 2003-09-03 | 2009-01-29 | At&T Intellectual Property I, L.P. | Method and system for automating membership discovery in a distributed computer network |
US20060120279A1 (en) * | 2003-09-10 | 2006-06-08 | Yasuyuki Mitsumori | Node redundancy method, interface card, interface device, node device, and packet ring network system |
US7724644B2 (en) * | 2003-09-10 | 2010-05-25 | Fujitsu Limited | Node redundancy method, interface card, interface device, node device, and packet ring network system |
US7733812B2 (en) * | 2004-06-07 | 2010-06-08 | Alcatel | Method for enabling multipoint network services over a ring topology network |
US20050271035A1 (en) * | 2004-06-07 | 2005-12-08 | Native Networks Technologies, Ltd. | Method for enabling multipoint network services over a ring topology network |
US20080175234A1 (en) * | 2005-09-30 | 2008-07-24 | Huawei Technologies Co., Ltd. | Method and device for protective switching of pseudo-wires on packet switching network |
US20100306571A1 (en) * | 2006-02-14 | 2010-12-02 | Juniper Networks, Inc. | Multiple media access control (mac) addresses |
US7801150B1 (en) * | 2006-02-14 | 2010-09-21 | Juniper Networks, Inc. | Multiple media access control (MAC) addresses |
US8493959B2 (en) | 2006-02-14 | 2013-07-23 | Juniper Networks, Inc. | Multiple media access control (MAC) addresses |
US7652984B1 (en) * | 2007-03-14 | 2010-01-26 | Cello Partnership | Geographic redundancy and resource optimization for security gateways in wireless networks |
US7990993B1 (en) * | 2008-02-20 | 2011-08-02 | Juniper Networks, Inc. | Platform-independent control plane and lower-level derivation of forwarding structures |
US7649904B1 (en) * | 2008-02-20 | 2010-01-19 | Juniper Networks, Inc. | Seamless split-horizon flooding of layer two (L2) network traffic on non-native and mixed architectures |
US20110058518A1 (en) * | 2009-09-09 | 2011-03-10 | Comtech Ef Data Corp. | Multi-Channel Single Carrier Per Channel (SCPC) Systems and Related Methods |
US20130212394A1 (en) * | 2010-06-02 | 2013-08-15 | Hangzhou H3C Technologies Co., Ltd. | Method for 802.1X Authentication, Access Device and Access Control Device |
US9066231B2 (en) * | 2010-06-02 | 2015-06-23 | Hangzhou H3C Technologies Co., Ltd. | Method for 802.1X authentication, access device and access control device |
US9838327B1 (en) | 2010-12-08 | 2017-12-05 | Juniper Networks, Inc. | Distributed generation of hierarchical multicast forwarding structures |
US8908686B1 (en) | 2010-12-08 | 2014-12-09 | Juniper Networks, Inc. | Distributed generation of hierarchical multicast forwarding structures |
US9736036B2 (en) | 2011-06-29 | 2017-08-15 | Juniper Networks, Inc. | Variable-based forwarding path construction for packet processing within a network device |
US8948174B2 (en) | 2011-06-29 | 2015-02-03 | Juniper Networks, Inc. | Variable-based forwarding path construction for packet processing within a network device |
US20140321330A1 (en) * | 2011-09-19 | 2014-10-30 | Telefonaktiebolaget L M Ericsson (Publ) | Controller placement for fast failover in the split architecture |
US9059928B2 (en) * | 2011-09-19 | 2015-06-16 | Telefonaktiebolaget L M Ericsson (Publ) | Controller placement for fast failover in the split architecture |
US9225591B2 (en) | 2011-09-19 | 2015-12-29 | Telefonaktiebolaget L M Ericsson (Publ) | Controller placement for fast failover in the split architecture |
CN104247344A (en) * | 2012-02-22 | 2014-12-24 | 瑞典爱立信有限公司 | Controller placement for fast failover in the split architecture |
WO2014040553A1 (en) * | 2012-09-14 | 2014-03-20 | 中兴通讯股份有限公司 | Method, system and apparatus for establishing communication link |
CN109510771A (en) * | 2017-09-15 | 2019-03-22 | 北京华为数字技术有限公司 | Multicast transmission method and relevant device |
Also Published As
Publication number | Publication date |
---|---|
US20040133619A1 (en) | 2004-07-08 |
US7283465B2 (en) | 2007-10-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7283465B2 (en) | Hierarchical virtual private LAN service protection scheme | |
US7339929B2 (en) | Virtual private LAN service using a multicast protocol | |
US7643409B2 (en) | Computer network with point-to-point pseudowire redundancy | |
EP1557006B1 (en) | Modified spanning tree protocol for metropolitan area network | |
US7127523B2 (en) | Spanning tree protocol traffic in a transparent LAN | |
EP2104994B1 (en) | Hash-based multi-homing | |
US7974223B2 (en) | Virtual private LAN service over ring networks | |
Lasserre et al. | Virtual private LAN service (VPLS) using label distribution protocol (LDP) signaling | |
US7593400B2 (en) | MAC address learning in a distributed bridge | |
US8804748B2 (en) | Hitless node insertion for Ethernet networks | |
US7269135B2 (en) | Methods and systems for providing redundant connectivity across a network using a tunneling protocol | |
EP1780960B1 (en) | Ring LSP topology for supporting VPNs over MPLS-based networks | |
US20110194404A1 (en) | System and method for fast protection of dual-homed virtual private lan service (vpls) spokes | |
EP2033377B1 (en) | Forced medium access control (MAC) learning in bridged ethernet networks | |
US20120236730A1 (en) | Method, device and system for processing service traffic based on pseudo wires | |
US20130272114A1 (en) | Pseudo wire switching method and device | |
US8199637B2 (en) | VPLS remote failure indication | |
US20030026209A1 (en) | Avoiding overlapping segments in transparent lan services on ring-based networks | |
US20120269056A1 (en) | Method, device, and system for protecting semi-ring network | |
Huynh et al. | RRR: Rapid ring recovery submillisecond decentralized recovery for ethernet ring | |
Huynh et al. | RRR: Rapid Ring Recovery | |
Umayabashi et al. | Improving ethernet reliability and stability using global open ethernet technology |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |