Disclosed is an apparatus and method for segment routing using a remote forwarding adjacency identifier. In one embodiment, a first node in a network receives a packet, wherein the packet is received with a first segment-ID and another segment ID attached thereto. The first node detaches the first and the other segment IDs from the packet. Then the first node attaches a first label to the packet. Eventually, the first node forwards the packet with the attached first label directly to a second node in the network. In one embodiment, the other segment ID corresponds to a forwarding adjacency or tunnel label switched path between the first node and another node.

Various exemplary embodiments relate to a method of offline traffic matrix aware segment routing. The method may include receiving a traffic matrix based upon all the traffic between nodes i and j that is routed in the network; and determining the amount of traffic between nodes i and j will be routed through node k, based on minimizing a maximum link utilization for the traffic matrix by determining that the total amount of flow on a link e in the network is less than the link's capacity.

A first device may determine an Internet Protocol version R (IPvR) interface address associated with a second device, where R is greater than or equal to four. The first device and the second device may be associated with an external border gateway protocol peering session. The first device may generate an Internet Protocol version S (IPvS) interface address based on the IPvR interface address associated with the second device, where S is greater than or equal to six and different than R. The first device may store the IPvS interface address in a routing table. The first device may receive, from the second device, a service route that includes the IPvS interface address, and may provide the service route to a third device. The first device may provide a labeled route to the third device. The labeled route may include a label associated with the IPvS interface address.

A method, performed in a network that includes a group of nodes, includes identifying a path through a set of the nodes, where each node, in the set of nodes, has a data plane and a control plane; establishing a control plane tunnel, associated with the path, within the control plane of the nodes in the set of nodes; establishing a data plane tunnel, associated with the path, within the data plane of the nodes in the set of nodes, where the data plane tunnel is associated with the control plane tunnel and established through the same set of nodes; and transmitting a control message through the control plane tunnel to change a state of the data plane tunnel.

In some embodiments, an apparatus comprises a core network node and a control module within an enterprise network architecture. The core network node is configured to be operatively coupled to a set of wired network nodes and a set of wireless network nodes. The core network node is configured to receive a first tunneled packet associated with a first session from a wired network node from the set of wired network nodes. The core network node is configured to also receive a second tunneled packet associated with a second session from a wireless network node from the set of wireless network nodes through intervening wired network nodes from the set of wired network nodes. The control module is operatively coupled to the core network node. The control module is configured to manage the first session and the second session.

A method and an apparatus for managing a data transmission channel includes obtaining a delay of data transmitted on a first channel and a continuity parameter of the first channel, and a delay of data transmitted on a second channel and a continuity parameter of the second channel; detecting whether a fault event occurs on the first channel; and switching a working channel of a source provider edge (PE) and a sink PE to the second channel when the fault event occurs on the first channel.

In some examples, a controller for a network includes a path computation module that determines, for a plurality of LSPs or other flows having a common source, shortest paths of the network from the common source to respective destinations of the plurality of LSPs based at least on a minimum bandwidth. The path computation module further determines, after determining the shortest paths, a shortest path for the LSP of the plurality of LSPs as the shortest path of the shortest paths of the network from the common source to a destination for the LSP. A path provisioning module of the controller, after the path computation module determines the shortest path for the LSP and in response to the path computation modules routing the LSP to the shortest path for the LSP on a network model of the network, installs the LSP to the network as routed to the shortest path.

In some embodiments, an apparatus includes a first edge device that is operatively coupled to a second edge device via a switch fabric. The first edge device and the second edge device collectively define an edge device network operating with a network-address-based protocol. The first edge device communicates with the second edge device via a multiprotocol label switching (MPLS) tunnel through the switch fabric. Furthermore, the first edge device is operatively coupled to the switch fabric such that a node of the switch fabric can be modified without coordination of the edge device network. Additionally, the first edge device is operatively coupled to the second edge device to define the edge device network such that an edge device of the edge device network can be modified without coordination of the switch fabric.

A mapping relationship between a private network multicast group address, which may be preset to support switching from a default Multicast Distribution Tree (MDT) to a data MDT, and a data group address may be stored in a first PE device. If a private network multi cast data flow corresponding to the mapping relationship satisfies a condition of switching from the default MDT to the data MDT, the first PE device may send a data MDT switch initiation packet including the private network multicast group address and the data group address to a second PE device on the default MDI, so that the second PE device joins the data MDT, a root of which is the first PE device, using the data group address. The first PE device may switch the private network multicast data flow to the data MDT, so that the private network multicast data flow is transmitted on the data MDT.

Techniques are described for routing inter-AS LSPs with a centralized controller taking inter-AS TE metric values for inter-AS links into account. The inter-AS TE metric values, e.g., local preference values, MED values, or EROS, indicate route preferences for routes between ASes. The disclosed techniques enable network devices within either or both of a first AS and a second AS to store inter-AS TE metric values for inter-AS links in TEDs of the network devices. The network devices then send the contents of their TEDs, including the inter-AS TE metric values, to a centralized controller of the first AS and the second AS. The centralized controller computes an inter-AS LSP across the first AS and the second AS based at least in part on the inter-AS TE metric values such that the inter-AS LSP includes a preferred one of the inter-AS links as indicated by the inter-AS TE metric values.