Abstract:
Techniques for a head-end node in one or more network autonomous systems to utilize a protocol to instantiate services on tail-end nodes. The head-end node can use a service request mechanism that is enabled by the protocol to request service instantiation on the tail-end node without a network operator having to manually configure the tail-end node, or even having access to the tail-end node. Additionally, the protocol may further provide mechanisms to define handling attributes for traffic of the service (e.g., Service-Level Agreement (SLA) parameters, an underlay transport protocol, etc.), service acknowledgement mechanisms for the head-end node to determine that the service was instantiated on the tail-end node, and so forth. In this way, a head-end node can be used to instantiate a service on a tail-end node without a network operator having to have direct access to the tail-end node to manually configure the tail-end node.
Abstract:
In one embodiment, segment routing (SR) network processing of packets is performed on packets having a segment identifier structure providing processing and/or memory efficiencies. Responsive to an identified particular segment routing policy, the particular router retrieves from memory a dynamic segment routing identifier portion of the particular SR policy that includes a SR node value and a SR function value. The SR function value identifies segment routing processing to be performed by a router in the network identified based on the SR node value. A segment routing discriminator is independently identified, possibly being a fixed value for all segment identifiers in the network. Before sending into the network, a complete segment identifier is added to the particular packet by combining the segment routing discriminator with the dynamic segment routing identifier portion. The particular packet including the complete segment identifier is sent into the network.
Abstract:
In one embodiment, a method according to the present disclosure includes receiving a topology change message at a core edge node and performing a network address information removal operation. The core edge node participates in network communications with one or more access network nodes of an access network using an access network protocol. The topology change message indicates that a topology change has occurred in the access network, and the topology change message conforms to the access network protocol. The network address information removal operation removes network address information stored by the core edge node, and the network address information is used by the core edge node in participating in the network communications.
Abstract:
Systems, methods, and computer-readable media for fast convergence for virtual ethernet segments in EVPN and PBB-EVPN networks are disclosed. A first provider edge (PE) device can receive one or more advertising messages corresponding to one or more virtual ethernet segments, wherein each of the one or more advertising messages can include a port identifier. The first PE device maintains a table including the one or more virtual ethernet segments and the corresponding port identifier. The first PE device can receive a failure message from a second PE device that identifies a first port on the second PE device, and identifies, based on the table, at least one affected virtual ethernet segment that is associated with the first port. The first PE device can remove any routes that are associated with the at least one affected virtual ethernet segment and trigger mass designated-forwarding election for impacted virtual ethernet segments.
Abstract:
In one embodiment, a method according to the present disclosure includes receiving a topology change message at a core edge node and performing a network address information removal operation. The core edge node participates in network communications with one or more access network nodes of an access network using an access network protocol. The topology change message indicates that a topology change has occurred in the access network, and the topology change message conforms to the access network protocol. The network address information removal operation removes network address information stored by the core edge node, and the network address information is used by the core edge node in participating in the network communications.
Abstract:
In one embodiment, Ethernet Virtual Private Network (EVPN) is implemented using Internet Protocol Version 6 (IPv6) Segment Routing (SRv6) underlay network and SRv6-enhanced Border Gateway Protocol (BGP) signaling. A particular route associated with a particular Internet Protocol Version 6 (IPv6) Segment Routing (SRv6) Segment Identifier (SID) is advertised in a particular route advertisement message of a routing protocol (e.g., BGP). The SID includes a locator of a particular router and a function encoding representing a particular EVPN end function of the particular router, with the particular SID including a routable prefix to the particular router. The particular router receives a particular packet including the particular SID; and in response, the particular router performs the particular EVPN end function on the particular packet. In one embodiment, the particular packet includes a Segment Routing Header (SRH) including the particular SID as the currently active SID.
Abstract:
Systems, methods, and computer-readable media for fast convergence for virtual ethernet segments in EVPN and PBB-EVPN networks are disclosed. A first provider edge (PE) device can receive one or more advertising messages corresponding to one or more virtual ethernet segments, wherein each of the one or more advertising messages can include a port identifier. The first PE device maintains a table including the one or more virtual ethernet segments and the corresponding port identifier. The first PE device can receive a failure message from a second PE device that identifies a first port on the second PE device, and identifies, based on the table, at least one affected virtual ethernet segment that is associated with the first port. The first PE device can remove any routes that are associated with the at least one affected virtual ethernet segment and trigger mass designated-forwarding election for impacted virtual ethernet segments.
Abstract:
Systems, methods and computer-readable storage media are provided for performing Internet Protocol (IP) address resolution within a network through a control plane or network controller approach. A provider edge (PE) device receives an Address Resolution Protocol (ARP) request message from a locally connected customer edge (CE) device. The PE device transmits the ARP request message to other locally connected CE devices and generates an IP address resolution request message that includes the IP address of a destination CE device. The IP address resolution request message is transmitted to other PE devices within the network. The PE device receives remote adjacency information associated with the destination CE device and transmits an ARP reply message to the locally connected CE device.
Abstract:
Disclosed herein are systems, methods, and computer-readable media for forwarding data in response to a detected local area network failure. In one aspect, a method includes identifying one or more EVPN services in a local area network. In one aspect, the method includes allocating one or more FRR labels, each of the FRR labels corresponding to each of the EVPN services. In one aspect, the method includes broadcasting the FRR labels to a plurality of network appliances of the LAN. In one aspect, the method includes determining one or more EVI-EAD routes associated with the FRR labels. In one aspect, the method includes detecting a LAN failure of one of the plurality of the network appliances. In one aspect, the method includes forwarding incoming data to another one of the plurality of the network appliances in accordance with the determined EVI-EAD routes, in response to detecting the LAN failure.
Abstract:
Techniques for a head-end node in one or more network autonomous systems to utilize a protocol to instantiate services on tail-end nodes. The head-end node can use a service request mechanism that is enabled by the protocol to request service instantiation on the tail-end node without a network operator having to manually configure the tail-end node, or even having access to the tail-end node. Additionally, the protocol may provide mechanisms to define handling attributes for traffic of the service (e.g., quality of service (QoS) attributes, Maximum Transmission Unit (MTU) settings, etc.), service acknowledgement mechanisms for the head-end node to determine that the service was instantiated on the tail-end node, and so forth. In this way, a head-end node can be used to instantiate a service on a tail-end node without a network operator having to have direct access to the tail-end node to manually configure the tail-end node.