1-Segment Routing

Tecnologías De Información Y Comunicación (Instituto Politécnico Nacional)

Scan to open on Studocu

Studocu is not sponsored or endorsed by any college or university

Downloaded by Nguy?n Huy ([email protected])
E922 - SAOS 10 IP, MPLS and VPN Services August
2023

SAOS 10
Segment Routing
Revision B

Copyright © 2022 Ciena Corporation. All rights reserved.

Welcome to SAOS 10 Segment Routing.

Downloaded by Nguy?n Huy

Revision B
([email protected])
 Objectives
In this lesson, you will be able to:

• Explain which problems can be solved with

Segment Routing
• Describe the basic concept of SR and its
technologies
• Describe the term segment and types of
segments
• Explain how the SR network is advertised
by means of IS-IS extensions

• Explain the Anycast IP concept in SR

In this lesson, you will be able to:

• Explain which problems can be solved with Segment Routing
• Describe the basic concept of SR and its technologies
• Describe the term segment and types of segments
• Explain how the SR network is advertised by means of IS-IS extensions
• Explain the Anycast IP concept in SR
 Segment
Routing
Introduction

This section will introduce the concept of Segment Routing.

 Segment Routing vs. Conventional Routing

Segment Routing (SR) utilizes source routing paradigm.

Conventional routing Segment Routing

• Path of the packet is defined by • Sender defines the complete or

every node in the network partial path of the packet

• Paths are encoded in the network • Paths are encoded in the packet
itself header as segments

• At ingress node, only the next hop • The nodes steer the packet based
and the destination is known on these instructions

Topological instruction
Segment
Service based instruction

Segment routing is a new packet forwarding technology which utilizes source

routing paradigm. To get a better understanding, let us compare it with
conventional routing.
• In conventional routing, the path of the packet is defined by every node in
the network. Operators use mechanisms, such as, weight, metric, SRLG
and so on, to define the paths for different types of traffic. Paths are
encoded in the network itself. At the ingress node, only the next hop and
the destination is known.
• In contrast, in a segment routed network, the sender defines the complete
or partial path the packet shall take, or the treatment the packet shall get
on its way to the destination. Paths are encoded in the packet header as an
ordered list of sub-paths or instructions called segments. The nodes steer
the packet through the network based on these instructions.
The segments in Segment Routing can be either topological instructions that
define the topological path, either node, link, that the packet shall take or a
Service based instruction that defines the treatment of the packet.
Ciena's initial Segment Routing implementation is based on topological
instructions.
 SR using Topological Instructions
Instructions
Instructions
Segment 1
Segment 2
Segment 3

E
G
A C 1 2

B D F

Go to G
Packet to G

Instructions

A segment is referred to by its Segment Identifier (SID).

These SIDs are encoded as part of the packet header.

The node receiving the packet understands the identifier and routes the packet further.

Go to E
Use link 1 to F
Go to G
Packet to G

Use link 1 to F
Go to G
Packet to G

Here is a generic example of source based routing using the topological

instructions.
A path is encoded in the packet header on the ingress node itself as a list of
segments to traverse. Each node acts as the topmost instruction and
forwards the packet based on it. Once an instruction is completely processed
or a segment is completed, the segment is popped from the packet. The
packet reaches the destination after all the segments are traversed.
A segment is often referred to by its Segment Identifier (SID) which is
assigned and advertised in different ways depending on the type of Segment
routing control plane being used. These SIDs are encoded as part of the
packet header. The node receiving the packet understands the identifier and
routes the packet further based on it. All the nodes participating in this source
based routing model comprise an SR domain.
 Segment Routing Overview

SR
Source routing: A node specifies a unicast forwarding path that a particular packet will
traverse objective

• Ability to tunnel services (VPN, VPLS, VPWS) from ingress PE to egress

PE IGP-based with or without an explicit path
MPLS tunnels
• Doesn't require forwarding plane or control plane state in intermediate nodes

• Protection for any topology, pre-computation and setup of backup path

without Fast Reroute any additional signaling
• Simpler to operate and more scalable

SDN services • Provides a quicker interaction with the applications

SR developed by Source Packet Routing In Networking (SPRING)

The primary objective of Segment Routing is source routing, which is the

ability for a node to specify a unicast forwarding path, other than the normal
shortest path, that a particular packet will traverse.
• Segment Routing enables IGP-based MPLS tunnels without the addition
of any other signaling protocol. It enables the ability to tunnel services
(VPN, VPLS, VPWS) from ingress PE to egress PE with or without an
explicit path, and without requiring a forwarding plane or a control plane
state in intermediate nodes.
• SR allows to have FRR protection for any topology, pre-computation and
setup of backup path without any additional signaling. This makes it simpler
to operate and more scalable.
• For future SDN services, it provides a quicker interaction with
the applications.
Segment Routing was developed by a working group called Source Packet
Routing in Networking or Spring.
 Segment Routing Tunnels
Segment Segment

Segment
Segment Segment
Segment Segment
P1 P2

P3 P4
PE1 PE2
Segment Segment Segment

Segment Segment

Paths are advertised by link-state routing protocols, IS-IS and OSPF.

SR tunnel
Single MPLS label or stack of MPLS labels
(single segment/ segment list)

Segment list: List of segments (Node, Link) to form a forwarding path.

As mentioned earlier, segments are sub-paths that are joined together to

make a path. As you can see, a segment can be either a node or a link. Paths
are advertised by link-state routing protocols, IS-IS and OSPF.
An SR tunnel, containing a single segment or a segment list is encoded
either as a single MPLS label or an ordered list of hops represented by a
stack of MPLS labels, meaning there is no change to the MPLS data-plane.
Note that the segment list can represents list of segments Node or Link to
form a forwarding path.
 Segment Routing Configuration

IPv4 dynamic single segment non-TE best path

tunnels User-configured explicitly-routed IPv4 SR TE

tunnels

SIDs are allocated from a Segment Routing Global Block (SRGB)

Segment Routing is implemented to create the two types of tunnels, IPv4

dynamic single segment non-TE best path tunnels and user-configured
explicitly-routed IPv4 SR TE tunnels. These tunnels are used for L2VPN
and L3VPN services.
Here you can see a sample Segment Routing configuration. The platform
supports SR over MPLS.
In the MPLS architecture, Segment IDs or SIDs are allocated from a Segment
Routing Global Block (SRGB). SRGB is the range of local labels reserved for
Segment Routing.
 Dynamic SR Best Path Tunnels

• SR enabled for IGP

IGP distributes SID
• Global SID allocated information to all nodes
from SRGB

Install an ingress LSP towards the downstream node

Nodes
Install a transit LSP, if there is router upstream

When Segment Routing is enabled for the IGP and a global SID is allocated
from SRGB, the IGP distributes the SID information to all nodes in the SR
domain. Nodes receiving the labels automatically install an ingress LSP
towards the downstream node, and a transit LSP, if there is router upstream of
the downstream node. Each LSP is uni-directional following the shortest
routing path and no TE attributes.
 Advantages of Segment Routing

Less control plane protocols • Extending existing IGP (OSPF or ISIS), eliminating MPLS control
plane protocols (LDP or RSVP)

• Providing explicit routing, TE, and per-segment differentiated

More control for traffic behavior

Excellent scale benefits • Path states maintained only at ingress node

• Transit and egress nodes do not maintain state for each path

MPLS applications • Changes only in Transport layer; so L3VPN, VPLS, VPWS used as is

Segment Routing offers the advantages listed here.

• Segment Routing is implemented by extending existing Interior Gateway
Protocol (IGP) such as OSPF or ISIS, thereby eliminating the need of
MPLS control plane protocols such as LDP or RSVP.
• SR also provides more control for traffic by providing explicit routing, TE,
and per-segment differentiated behavior.
• The path states are maintained only at the ingress node and the path to
follow is pushed into the packet itself. The transit and egress nodes do not
maintain state for each path traversing through them. The configuration
overhead is less than traditional MPLS.
• All the MPLS Application can be used with Segment Routing. SR only
changes the Transport layer, hence services like L3VPN, VPLS and
VPWS can still be used, as is.
 Types of
Segments

This section covers the types of segments used in Segment Routing.

 • An IGP local segment that represents an
• An IGP global segment that represents an
IGP adjacency
IGP prefix (IP addresses on the node)
• Identifier for IGP adjacency is
• Identifier Prefix-SID; allocated by the locally significant
network operator • Routers generate and distribute
• Prefix-SID: Node segment/SID that adjacency identifiers outside of reserved
identifies the shortest path to the node block
• Ensure that Prefix-SID and node-SID • In SR-TE scenario, SR tunnel needs to
are allocated correctly be routed by means of specific link
• SR architecture defines extensions for
IGP protocols to distribute SID information

In the SR domain, IGP SIDs play a key role as they enable the expression of any path through
the domain. The path is expressed as a single IGP segment or a list of multiple IGP segments.
These segments can be global or local segments.
• Global segments are understood by all nodes in the network, for example, forwarding the packet
to Node B and then Z.
• Local segment are only understood by some specific node, for example, forwarding the packet
by means of a particular interface on Node B. Only Node B understands the instruction.
Segment types are IGP-prefix segment:
• An IGP-prefix segment is an IGP global segment that represents an IGP prefix, that is,
IP addresses on the node.
• The identifier is the Prefix-SID. The Prefix-SID is typically allocated by the network operator
on every node in the SR domain and must be globally unique.
• The Prefix-SID associated with the loopback address of the node is a node segment or node
SID. A node segment identifies the shortest path to the node.
• The network operator must ensure that Prefix-SID and node-SID are allocated correctly to
avoid incorrect routing in the network.
• The Segment Routing architecture defines the extensions for IGP protocols to distribute
SID information. By default SR is disabled globally from an IGP
IGP-adjacency segment:
• An IGP-adjacency segment is an IGP local segment that represents an IGP adjacency, that is, a
unidirectional data link or interface to an adjacent node or a set of data links to the adjacent
node.
• The identifier, also referred to as adjacency-SID, is locally significant and need not be
unique across nodes.
• Routers automatically generate and distribute adjacency identifiers outside of the reserved block
of node IDs, that is, the SRGB.
• It is mostly useful in scenarios in SR-TE cases where the SR tunnel needs to be routed by
means of a specific link.
 Segment
Routing
Technologies

This section covers some overview on Segment Routing technologies.

 SR Control Plane

Control plane is responsible for allocating and distributing the segment information.

• Routing protocols such as IS-IS or OSPF or BGP

Distributed • A node individually:
• Computes the SR policy
• Decides to steer packets on a source-routed policy

• Segments are allocated and instantiated by an SR controller

Centralized • SR controller computes the source-routed policies
• Protocols - NETCONF, PCEP, BGP

• Use of both distributed control plane and centralized controller

Hybrid • Examples - Ciena's 10x nodes & Blue planet software
• Allow customers to select the desired path

In Segment Routing, the control plane is responsible for allocating and

distributing the segment information like segment identifiers and the algorithm.
The SR architecture defines different scenarios in which it can be done, such as
distributed, centralized and hybrid.
In a distributed scenario, the segments are allocated and signaled by the routing
protocols running on each node such as IS-IS or OSPF or BGP. A node
individually computes the SR Policy. A node individually decides to steer packets
on a source- routed policy.
In a centralized scenario, the segments are allocated and instantiated by an SR
controller. The SR controller decides which nodes need to steer which packets
on which source-routed policies. The SR controller computes the source-routed
policies. The SR architecture does not restrict how the controller programs the
network. Network Configuration Protocol (NETCONF), Path Computation
Element Communication Protocol (PCEP), and BGP are some of the protocols
used by the SR controller to program the nodes.
A hybrid scenario involves the use of both a distributed control plane and a
centralized controller. When the destination is outside of the IGP domain, the SR
controller may compute an SR policy on behalf of an IGP node. Ciena's 10x
nodes, along with the Ciena's Blue planet software, is another example of hybrid
mode where the software learns the topology from the nodes. It allows the
customers to select the desired path based on various constraints and use
Ciena's Blue Planet software to program the Ciena switches with the SR policy.
 SR Data Plane

SR can be mapped onto different forwarding planes that support MPLS.

PUSH: Insertion of a segment at the top

Data plane
operations NEXT: Inspection of the next segment

CONTINUE: Segment remains active

Only the SID changes with the change in data plane.

SR is a generic concept which can be mapped onto different forwarding

planes that support source routing, such as, MPLS and IPv6.
When the packet enters an SR domain, there are three kind of operations that
are carried out on the packets by the data plane:
• Push is the instruction consisting of the insertion of a segment at the top
of the segment list.
• When the active segment is completed, NEXT is the instruction
consisting of the inspection of the next segment.
• In the Continue operation, the active segment is not completed and
hence remains active.
These operations are irrespective of the data plane being used. Only the
segment identifier changes with the change in data plane.
 SR MPLS Data Plane

SR data plane consists of MPLS data plane.

• SR can be directly applied to MPLS architecture with no change to the forwarding plane.
• At ingress node, IPv4 packets are encapsulated with list of labels.
• The active segment to process is on the top of the stack.
• Upon completion of a segment, the related label is popped from the stack.
• The process continues until the packet reaches the egress node.

PUSH: One or more labels on top of an incoming packet

SR MPLS
data plane NEXT: Pop topmost label
operations

CONTINUE: Swap incoming label with outgoing label

SR data plane consists of MPLS data plane.

• SR can be directly applied to the MPLS architecture with no change to
the forwarding plane. No change is required as SIDs are instantiated as
MPLS labels in SR.
• In an IPv4 SR-MPLS network, an SR path is instantiated as a stack of labels.
• At ingress node, IPv4 packets are encapsulated with list of labels
and switched out toward the next hop based on the current route
selection.
• The active segment to process is on the top of the stack. The label is
swapped at each transit node along the pre-established label switching
path (LSP) until the active segment is completed.
• Upon completion of a segment, the related label is popped from the
stack. The actions are then taken based on the next label (next active
segment). And the process continues until the packet reaches the
egress node. The packets are then consumed by the egress node if
they are destined to it or forwarded according to their IP destinations.
So with the MPLS forwarding plane, PUSH corresponds to pushing one or
more labels on top of an incoming packet then sending it out of a particular
physical interface or virtual interface. CONTINUE operation corresponds to
swapping the incoming label with an outgoing label. NEXT corresponds to
popping the topmost label.
 SR Traffic Engineering

SR simplifies TE by providing more granular controls to the user and reducing network state.

• The traffic engineered tunnels in SR are instantiated as a stack of segments/labels.

• SR tunnel is referred as an SR policy; Path (list of segments) is referred as candidate-path

Explicit candidate path Dynamic candidate path

• The path is explicitly configured by the • Hops/links/SID list is computed based

operator at the ingress node. on constraint or optimization
objective.
• Multiple prefix and adjacency segments • Ingress router uses local database like
can be combined. Constrained Shortest Path First
(CSPF);
In SDN architecture, it uses Path
Computation Element (PCE).

Traffic engineering is one of the main applications of Segment Routing. SR is

intended to simplify the traffic engineering by providing more granular
controls to the user and reducing the state in the network.
The traffic engineered tunnels in SR are instantiated as a stack of
segments/labels which are added at the ingress node. These segments are
mainly the topological segments in Ciena initial implementation and hence
define the path for the packets steered through these traffic engineered
tunnels. In the context of traffic engineering, the SR tunnel is generally
referred as an SR policy and the path or list of segments is referred as
candidate-path. There can be one or more paths associated with an SR policy
which can be selected based on a preference. These paths can be either
explicit or dynamic.
• In explicit candidate path, the path is explicitly configured by the operator
at the ingress node providing the complete list of hops or SID list to be
added in the packet. Multiple prefix and adjacency segments can be
combined to create such an explicit path TE LSP.
• In a dynamic candidate path, the hops/links/SID list is computed based
on some constraint or an optimization objective provided by the
operator. The headend or ingress router uses either local database like
Constrained Shortest Path First (CSPF) or in SDN architectures, it can
use Path Computation Element (PCE), to get the hops/SID list to add in
the packet header.
 Tunnel T1

Out i/f – AC
User configures Tunnel T1
Node SID - 16001
Destination – Node G
Hops – E, EF – Link1, G

As part of phase 1, Ciena supports explicit-path SR-TE policy associated with

single candidate path.
This figure shows an explicit path tunnel created at ingress using a
combination of Prefix segment and Adjacency segment. The user specifies
the hops as Node E, link EF, Node G for the Tunnel T1. Only the forwarding
entry highlighted in “orange” is created for the SR-TE tunnel T1. No additional
forwarding entries are installed on the transit and egress nodes for the SR-TE
tunnel. The transit and egress nodes utilize the existing forwarding entries,
created as part of initial SR SID/label distribution, to forward the packets. Note
that the figure only shows the entries which are relevant for the TE tunnel T1.
 Segment Routing Mapping Server (SRMS)

IGP node advertising mapping between SID and prefixes advertised by other IGP nodes

• SRMS can be used both for prefixes belonging to SR capable nodes or non-SR capable nodes.

SR interworking with LDP SRMS in SR network

• SR control plane can co-exist with LDP • SRMS assigns Prefix SID for SR nodes
• Required when SR is available in one part • No need to allocate Prefix SID on every node
and LDP is available in another
• Locally configured Prefix SID is preferred

80.80.80.80
Node SID - 16080 10.10.10.10
Node SID - 16010 20.20.20.20
Node SID - 16020 22.22.22.22
Node SID - 16022

8.8.10.1 8.8.10.1 10.10.20.1 10.10.20.2 20.20.22.1 20.20.22.2

PE1 P2 P3 PE4
A Service must be tunneled from PE1 to PE4
over a continuous MPLS tunnel encapsulation.

SRMS is an IGP node that advertises mapping between SID and prefixes
advertised by other IGP nodes. SID/Label Binding TLV is used to advertise
prefixes to SID/Label mappings. SRMS can be used both for advertising label
mapping for prefixes belonging to SR capable nodes or non-SR capable
nodes specifically the LDP capable nodes (for interworking).
• In Segment Routing interworking with LDP, the SR control plane can
co-exist with current label distribution protocols such as LDP. SR
interworking with LDP is required, where SR is available in one part of the
network and LDP is available in another part in the same routing domain.
This is a scenario where node PE1, P2, P3 are SR capable and P3, PE4
are running with LDP.
Note that on node P3, LDP needs to be enabled only on the link towards
PE4. A Service must be tunneled from PE1 to PE4 over a continuous
MPLS Tunnel Encapsulation and hence end to end tunnel is required to be
established.
• In SRMS in SR network, SRMS can also be used within an SR domain to
assign a Prefix SID for the SR nodes. In such a case, the user may not
need to allocated Prefix SID on every node. If the user does allocate
Prefix SID on the node then the locally configured Prefix SID is preferred
over the one received from the SRMS.
 IS-IS Segment
Routing
Extensions

This section will explain the IS-IS extensions of Segment Routing.

 IS-IS Extensions Overview
The new sub-TLVs are added to the existing TLVs and carried as part of the IS-IS Link State PDU (LSP).

TLV Sub-TLV Description

IS-IS router SR-capabilities Indicates support for Segment Routing. Also carries the SRGB label range
capability and start label.

SR-algorithm Advertises the algorithm used for path calculation. The current
implementation supports the default Shortest path first algorithm.
SRMS preference Associate a preference with Segment Routing Mapping Server (SRMS)
sub-TLV advertisements from a particular source.
IS-IS extended IP Prefix-SID Carries the Prefix-SID/index/label for a prefix. The Prefix-SID is
reachability propagated from one level to another by setting some flags in the
Prefix-SID sub-TLV for the prefixes that are not local to the router, that
is, routes that are
• Advertised because of propagation (Level-1 into Level-2)
• Advertised because of leaking (Level-2 into Level-1)
• Advertised because of redistribution
IS-IS extended IS Adj-SID Carries the Adjacency-SID/ index/label for an adjacency in point-to- point
reachability networks.

LAN-Adj-SID Carries the Prefix-SID/ index/ label for an adjacency in LAN

subnetworks.
SID/label binding Advertise prefixes to SID/label mappings.
TLV
Mapping Server Prefix- Contains the SID/index/label value associated with the prefix and
SID sub-TLV range.

The segment information in an SR network is advertised by means of IS-IS

extensions.
The IS-IS protocol is extended to carry SID index and label information for
Segment Routing as part of the regular IS-IS protocol messages. The new
sub- TLVs are added to the existing TLVs and carried as part of the IS-IS Link
State PDU (LSP).
 SR Label Distribution using IS-IS Extensions

SR capabilities exchanged and labels distributed in a SR network using IS-IS extensions

Here is an example of how Segment Routing capabilities are exchanged and

labels are distributed in a Segment Routing network using IS-IS extensions.
In this example, the Prefix-SID has an absolute value. The Prefix-SID can
also be configured as an index. In this case, the index is carried instead of an
absolute label value.
 Anycast IP

Multiple machines shares the same IP address

1.1.1.1

Data Center A

1.1.1.1

Data Center B

1.1.1.1

Data Center C

Anycast IP is a networking technique that allows multiple machines to share

the same IP address. Based on the location of the user request, the router
sends the data packet to the machine in the network that is closest. In other
words, instead of forwarding to a specific device or to all devices in a group,
anycast addresses let network devices forward a packet to, or steer it
through, one or more of the topologically nearest devices in a specific group
of network devices. This is beneficial since it reduces latency and increases
redundancy. If one of the servers were to go offline, an anycast IP would
choose the best path for users and automatically redirect them to the next
closest server.
 Anycast SID

Anycast IP address support is extended to SR

Anycast SID 100

Anycast SID 100

Anycast SID 100

SR-capable devices can represent an anycast address.

The same SRGB is provisioned on all the devices.

Each device advertises the same anycast prefix segment.

The use of anycast IP addresses has been extended to the Segment Routing
network as Anycast SID or segment identifier. This means a group of SR-
capable devices can represent an anycast address, by having the same
Segment Routing Global Block (SRGB) provisioned on all the devices. Each
device in the group advertises the same anycast prefix segment (or Anycast
SID).
 Anycast SID – Use case 1

Resiliency and load balancing at ABRs

Anycast SID 100
ABR1

Label: Node SID

[100,300] 300

ISIS L1 ISIS L1L2 ISIS L1

PE1 PE2

Anycast SID 100

ABR2
Original Path
Alternate Path
• SR-TE is not anchored to specific ABR, instead anchored to Anycast address/ Anycast-SID.
• When one ABR fails, the flow automatically reroutes to shortest-path to other ABR in the
same anycast set

The SR-TE policy is not anchored to reach a specific ABR whose failure
could impact the service. It is anchored to an anycast address/Anycast-SID
and hence the flow automatically reroutes on shortest-path to other ABR part
of the anycast set.
 Anycast SID – Use case 2

Dual-plane disjoint SR-TE path

BLUE Plane
Anycast-SID 100

PE1

Service 1 Node SID 300

Label:[100,300]

PE2 PE3

Service 2 Node SID 400

Label:[200,400] GREEN Plane
Anycast-SID 200 PE4

• Multiple data planes can exist in the network.

• Anycast-SID allows creation of policies.
• Example:
• “Flow of service 1 traffic from PE1 to PE3 must go via BLUE plane” OR
• “Flow of traffic from node PE2 to PE4 must go via GREEN plane”

Dual plane is used to enforce dis-jointness in the network, where the traffic
path towards destination node stays within a set of nodes called plane. There
can be multiple planes in the network, so that different planes in the network
can be used for different kind of traffic types. Anycast-SID allows creation of
such macro policies, such as, “flow of service 1 traffic from node PE1 to PE3
must go via Blue plane” and “flow of service 2 traffic from node PE2 to PE4
must go via Green Plane.” This is practically called a dual-plane disjoint path
architecture.
 Check Your
Knowledge

Its time for a quick question to check what you have learnt.
 Check Your Knowledge

Which of the following operations that are carried out on the packets by the data plane when the
packet enters an SR domain?

a. PUSH

b. SWAP

c. NEXT

d. CONTINUE

Copyright © 2022 Ciena Corporation. All rights reserved. 28

Correct answer is a, c and d

PUSH, NEXT and CONTINUE are operations that are carried out on the
packets by the data plane when the packet enters an SR domain.
 Check Your Knowledge

State TRUE or FALSE.

SR can be directly applied to MPLS architecture with no change to the forwarding plane.

a. True

b. False

Copyright © 2022 Ciena Corporation. All rights reserved. 29

Correct answer is a
SR can be directly applied to MPLS architecture with no change to the
forwarding plane.
 Check Your Knowledge

The traffic engineered tunnels in SR are instantiated as a stack of segments/labels which are
added at the node.

a. all

b. destination

c. ingress

d. egress

Copyright © 2022 Ciena Corporation. All rights reserved. 30

Correct answer is c
The traffic engineered tunnels in SR are instantiated as a stack of
segments/labels which are added at the ingress node.
 Check Your Knowledge

State TRUE or FALSE.

Adj-SID is used to carries the Prefix-SID/ index/ label for an adjacency in LAN subnetworks.

a. True

b. False

Copyright © 2022 Ciena Corporation. All rights reserved. 31

Correct answer is b
Adj-SID is used to carries the Adjacency-SID/ index/label for an
adjacency in point-to-point networks.
 Summary
In this lesson, you learned to:

• Explain which problems can be solved with

Segment Routing
• Describe the basic concept of SR and its
technologies
• Describe the term segment and types of
segments
• Explain how the SR network is advertised
by means of IS-IS extensions

• Explain the Anycast IP concept in SR

In this lesson, you learned to:

• Explain which problems can be solved with Segment Routing
• Describe the basic concept of SR and its technologies.
• Describe the term segment and types of segments
• Explain how the SR network is advertised by means of IS-IS extensions
• Explain the Anycast IP concept in SR
 Thank you

Copyright © 2022 Ciena Corporation. All rights reserved.

You have completed this lesson. You have completed this lesson.