Abstract:
A method is provided in one example embodiment and includes establishing a virtual trunk link (trunkl - trunkn) between a first network element (extGWl - extGWn) and a second network element (intGWl - intGWn). The first and second network elements are located in gateway element ISGW2 at a first site (site2), and the first site and a second site comprise at least a portion of an overlay network (SEGMENT 10010, SEGMENT 10020). The method further includes receiving data traffic at the first network element, which data traffic is associated with a segment of the overlay network, and mapping a first network identifier (SEGMENT 10010) allocated to the overlay network segment at the first network element to a virtual trunk link (trunkl- trunkn) and a VLAN ID. The method additionally includes forwarding the data traffic from the first network element to the second network element via the virtual trunk link with the VLAN ID. Preferably, two types of VXLAN gateways are thus connected, or paired, through virtual trunk links to facilitate VXLAN extension across multiple sites. In gateway element ISGW2, multiple VXLAN gateway virtual machines are deployed in pairs. They are categorized into two types, internal and external gateways. Internal VXLAN gateways connect to VXLAN tunnel endpoints (VTEPs) within the site and may run control protocols such as BGP or use internal Virtual Supervisor Module (VSM) to Virtual Ethernet Module (VEM) communication mechanism for VTEP and segment discovery within a site or for that matter multicast within that site. In contrast, external VXLAN gateways connect to gateways of other sites. The allocation of VLAN 20 to support segment ID mapping is a matter internal to to gateway element ISGW2. Scalable and stable multi-site connectivity can thus be provided.
Abstract:
A method is provided in one example embodiment and includes receiving at a network element a flow offload decision for a first service node comprising a portion of a service chain for processing a flow; recording the flow offload decision against the first service node at the network element; and propagating the flow offload decision backward on a service path to which the flow belongs if the first service node is hosted at the network element. Embodiments may also include propagating the flow offload decision backward on a service path to which the flow belongs if the flow offload decision is a propagated flow offload decision and the network element hosts a second service node that immediately precedes the service node on behalf of which the propagated flow offload decision was received and a flow offload decision has already been received by the network element from the second service node.