Abstract:
In one embodiment, a network device may participate in an election process to elect one of two or more Provider Edge devices of a Redundancy Group to be a Designated Forwarder for the Redundancy Group, where the Redundancy Group is in a Service Provider network, and where the Redundancy Group serves a Customer Edge device of a customer network. The network device may forward multi-destination traffic to the Customer Edge device according to whether the network device is elected to be the Designated Forwarder for the Redundancy Group. Multi-destination traffic may include multicast traffic, broadcast traffic, or destination unknown unicast traffic.
Abstract:
In one embodiment, a network device may participate in an election process to elect one of two or more Provider Edge devices of a Redundancy Group to be a Designated Forwarder for the Redundancy Group, where the Redundancy Group is in a Service Provider network, and where the Redundancy Group serves a Customer Edge device of a customer network. The network device may forward multi-destination traffic to the Customer Edge device according to whether the network device is elected to be the Designated Forwarder for the Redundancy Group. Multi-destination traffic may include multicast traffic, broadcast traffic, or destination unknown unicast traffic.
Abstract:
In one embodiment, a method includes establishing in a Virtual Private Local Area Network (LAN) Service (VPLS) over Multi-Protocol Label Switching (MPLS) network a floating pseudowire between a first provider edge router and a redundancy group having a plurality of provider edge routers each configured to forward data toward a external device. Each provider edge router in the redundancy group is configured to maintain an active link to the external device. A provider edge router that is not a member of the redundancy group sends data directed to the external device through the floating pseudowire. Only one provider edge router in the redundancy group receives and forwards the particular data to the external device.
Abstract:
In one embodiment, a method includes configuring a first node, located at an edge of a core network and connected to an access ring, with a maintenance end point for a virtual local area network on a port connecting the first node to the access ring. The first node operates in an active mode for the virtual local area network and is in communication with a second node located at the edge of the core network and connected to the access ring. The method further includes receiving and processing at a processor at the first node, continuity check messages from access nodes on the access ring, synchronizing the first node with the second node, and communicating from the first node to the second node to initiate switching of the second node from a backup mode to the active mode for the virtual local area network upon identification of a failure.
Abstract:
A customer edge device is automatically configured. A request for customer edge device configuration data may be transmitted to a provider edge device via an Ethernet-layer operations, administration, maintenance, and provisioning (OAM&P) protocol. The request for configuration data may be relayed from the Ethernet-layer OAM&P protocol to a configuration protocol. The request for configuration data may be transmitted from the provider edge device to a configuration repository server via the configuration protocol. The configuration repository server may transmit the requested configuration data to the provider edge device via the configuration protocol. The provider edge device may relay the configuration data from the configuration protocol to the Ethernet-layer OAM&P protocol and transmit the configuration data to a customer edge device via the Ethernet-layer OAM&P protocol. The customer edge device may automatically configure itself using the configuration data.
Abstract:
A first multicast data packet can be received by a particular edge node, forwarded from another network element in a network, the first packet including data received from a particular device interfacing with the network through a first edge node. The first packet is multicast by the first edge node. The particular edge node is included in a redundancy group including at least one other edge node. The first multicast data packet is examined to identify a first hint corresponding to the particular device. In response to identifying the particular device, it is determined that the particular edge node does not interface with the particular device. It is further determined that the particular edge node is designated as a forwarding node for the redundancy group. Based on these determinations, the first packet is forwarded by the particular edge node while preventing looping and duplicate packet delivery.
Abstract:
In one embodiment, a method includes obtaining an indication that a device is attached to a provider edge. The device has a media access control (MAC) address, wherein the device was previously attached to a first provider edge (PE) of a Multiprotocol Label Switching (MPLS) network. The method also includes issuing a first advertisement that identifies the MAC address. The first advertisement includes a first MAC address mobility attribute arranged to indicate a number of times the MAC address has moved with respect to the MPLS network.
Abstract:
One embodiment is a source router that monitors the performance of an Ethernet network. The source router generates an Ethernet connectivity check request frame that includes a transmission timestamp, and transmits the Ethernet connectivity check request frame to a destination router. The source router receives a reply from the destination router that is transmitted in response to receiving the Ethernet connectivity check request frame and determines a round trip time between the source router and the destination router based on a time of receipt of the reply and the transmission timestamp.
Abstract:
In certain embodiments, monitoring a flow set to detect faults includes identifying, by a first maintenance end point, a flow set comprising flows that utilize a paths from the first maintenance end point through one or more intermediate nodes to a second maintenance end point. Continuity check messages are generated. Each continuity check message is formatted as a data packet that an intermediate node forwards. Each continuity check message comprises a header comprising a maintenance indicator. The continuity check messages are transmitted on the flows to allow the second maintenance end point to monitor the paths.
Abstract:
One embodiment is a source router that monitors the performance of an Ethernet network. The source router generates an Ethernet connectivity check request frame that includes a transmission timestamp, and transmits the Ethernet connectivity check request frame to a destination router. The source router receives a reply from the destination router that is transmitted in response to receiving the Ethernet connectivity check request frame and determines a round trip time between the source router and the destination router based on a time of receipt of the reply and the transmission timestamp.