Available

as PDF

SROS Express for Experienced

Professionals Operation, Administration,
Maintenance & Provisioning
Lab Guides

SROS Express for Experienced Professionals Operation, Administration, Maintenance

& Provisioning | ER00198-V-2000 V0

©
1 Nokia 2020 Confidential
 Disclaimer
The information in this document applies solely to the hardware/software product (“Product”) specified herein, and
only as specified herein. Reference to “Nokia” later in this document shall mean the respective company within
Nokia Group of Companies with whom you have entered into the Agreement (as defined below).
The contents of this document are proprietary related specifications or other documentation. accuracy, reliability or contents of this
This document
and confidential is intended
property of Nokia.for
This use by Nokia's customers
Accordingly, if the user of (“You”)
this documentonly,givesand it document.
may not beSHALL
NOKIA used NOTexcept for the
BE RESPONSIBLE
purposes defined in the agreement
document is provided subject to confidentiality
obligations of the applicable agreement(s).
between You and Nokia (“Agreement”)
Nokia Feedback on the contents of this
document, Nokia may freely use, disclose,
under which this document
IN ANY EVENT FOR ERRORS IN THIS DOCUMENT
or for
is
distributed. No part of this document may be used,
reproduce, license,copied, reproduced,
distribute and otherwise modified
any loss ofor
datatransmitted in any form or
or income or any special,
means without the prior written permission
This document is intended for use of Nokia’s
customers and collaborators only for the
of Nokia. If You have not entered
commercialize the feedback in any Nokia
product, technology, service, specification or
into an Agreement applicable to the
incidental, consequential, indirect or direct
damages howsoever caused, that might arise
Product,
purpose orforifwhich
thatthisAgreement has expired
document is submitted otherordocumentation.
has been terminated, You mayfrom nottheuse
use ofthis document
this document or any in any manner
contents
and You are obliged to return
by Nokia. No part of this document may be
it to
reproduced or made available to the public or to
Nokia and destroy or delete
Nokia operates a policy of ongoing
any copies thereof. The
of this document.
document has been
prepared
any thirdtoparty
beinused
any form byor means
professional
without the and properlyNokia
development. trained
reservespersonnel,
the right to make and You Thisassume
document and fulltheresponsibility when using
product(s) it describes
it. Nokia welcomes your comments as part
prior written permission of Nokia. This
document is to be used by properly trained
of the process of continuous development
changes and improvements to any of the
products and/or services described in this
and improvement of the
are protected by copyright according to the
applicable laws.
documentation.
professional personnel. Any use of the contents document or withdraw this document at any
in this document is limited strictly to the use(s) time without prior notice. Nokia is a registered trademark of Nokia
This document and
specifically created itsapplicable
in the contents are provided as a convenience to You. Any Corporation. information Other or statements
product and company concerning
the suitability, capacity, fitness for purpose
agreement(s) under which the document is
submitted. The user of this document may
or performance of the Product are
The contents of this document are provided "as
is". Except as required by applicable law, no
given solely on an “as is” and “as
names mentioned herein may be trademarks or
trade names of their respective owners.
available” basis
voluntarily insuggestions,
provide this document,
comments or and Nokia reserves
warranties of any kind,the right
either toorchange
express implied, any such information and statements
without notice. Nokia has made
other feedback to Nokia in respect of the
contents of this document ("Feedback"). Such
all reasonable efforts to ensure
including, but not limited to, the implied
that
warranties of merchantability and fitness for a
the content of this document is adequate and
free of material
Feedback may be errors and
used in Nokia omissions,
products and and Nokia
particular will correct
purpose, are made inerrors
relation tothat
the You identify in this document. Nokia's total
liability for any errors in the document is strictly limited to the correction of such error(s). Nokia does not warrant
that the© use of
2 Nokia the software in the Product will be uninterrupted
2020 Confidential or error-free.
NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF
AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE
LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR
CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS
INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE
INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.
This document is Nokia proprietary and confidential information, which may not be distributed or disclosed to any
third parties without the prior written consent of Nokia. Nokia is a registered trademark of Nokia Corporation.
Other product names mentioned in this document may be trademarks of their respective owners.

Important notice on product safety

This product may present safety risks due to laser, electricity, heat, and other sources of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only
after having carefully read the safety information applicable to this product.
The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental
Information” part of this document or documentation set.

Nokia is continually striving to reduce the adverse environmental effects of its products and services. We would like
to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please
recycle product packaging and follow the recommendations for power use and proper disposal of our products and
their components.
If you should have questions regarding our Environmental Policy or any of the environmental services we offer,
please contact us at Nokia for any additional information.

Export Control Marks: undefined

This course is subject to the European Export Control Restrictions.
© Nokia 2020 - Nokia Confidential

The reproduction, transmission or use of this document or its contents is not permitted without express written
authority.
Offenders will be liable for damages. All rights, including rights created by patent grant or registration of utility
model or design, are reserved.
Technical modifications possible.
Course Outline
Welcome to SROS Express for Experienced Professionals Operation, Administration,
Maintenance & Provisioning

1 - Starting Up
1.1 - Lab Setup and Assignment
2 - System and Network configuration
2.1 - CLI Card Port
3 - IGP Configuration
3.1 - OSPF ISIS BFD
4 - MPLS Configuration
4.1 - MPLS LDP RSVP-TE
5 - Services Configuration
5.1 - Service Architecture
5.2 - EPIPE VPLS VPRN
5.3 - VPLS BGP-AD
5.4 - IES RVPLS Introduction
5.5 - BGP
5.6 - EVPN
5.7 - Segment Routing
6 - Quality of Service
6.1 - QoS
Course Objectives
Welcome to SROS Express for Experienced Professionals Operation, Administration,
Maintenance & Provisioning

Upon completion of this course, you should be able to:

• Log in to the system and recognize basic SROS CLI structure

• Verify Card, Port, MDA and Interface configurations and practice advanced SROS CLI
commands
• Configure and verify the OSPF, IS-IS routing protocol
• Configure and verify LDP and RSVP-TE as MPLS label signaling protocols
• Explain traffic engineering capabilities of RSVP-TE
• Describe resilience techniques used by both LDP and RSVP-TE
• Carry out preliminary steps required prior to service configuration
• Configure and verify Epipe, EVPN, VPLS, VPRN, VPLS BGP-AD, IES, rVPLS, and EVPN
services
• Provide basic IPv4 and IPv6 iBGP and eBGP configuration, policy development, scaling
iBGP with route reflector, and operations on Nokia’s Service Routers
• Describe the concept of Segment Routing and carry out basic configuration
• Explain and configure Quality of Service (QoS)
 Lab Setup and Assignment

ER00198-V-2000 V0 - S01M01 Ed0

1 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S01M01 Ed0 1
Learning Objectives
Upon completion of this module, you should be able to:
• Identify the IP address and lab set-up for this course

2 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S01M01 Ed0 2
 ToC Slide

Table of Contents

Lab Setup
Wrap-up

3 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S01M01 Ed0 3
 Lab Setup

4 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S01M01 Ed0 4
Lab Introduction

This course is developed using R20.2 R1(classic-cli) on Azure cloud lab.

Management (BOF) IP address of routers will be changed when different Pod is used for the
training. Please check with your instructor for details.

5 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S01M01 Ed0 5
Pod Assignment and Management IP Addresses

Router login ID and password

• admin, admin
PC login ID and password
• root, root

Check with the lab manager about the management IP addresses for the routers and PCs.

Group Core Router Edge Router PC

Students 1 & 2 (Pod1) R1 R5 PC9

Students 3 & 4 (Pod2) R2 R6 PC10

Students 5 & 6 (Pod3) R3 R7 PC11

Students 7 & 8 (Pod4) R4 R8 PC12

6 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S01M01 Ed0 6
 Router System Addresses and PC Interface
PC9 R5 R6 PC10

eth1 eth1

10.10.10.1/32 10.10.10.2/32
10.10.10.5/32 3ffe::1:101:101/128 3ffe::1:202:202/128 10.10.10.6/32
3ffe::1:505:505/128 R1 R2 3ffe::1:606:606/128

R3 R4
PC11 10.10.10.3/32 10.10.10.4/32 PC12
3ffe::1:303:303/128 3ffe::1:404:404/128
eth1 eth1

R7 R8
10.10.10.7/32 10.10.10.8/32
3ffe::1:707:707/128 3ffe::1:808:808/128
7 Nokia 2020
© Nokia Confidential

System Address – AS 65100

R1 – 10.10.10.1/32
R2 – 10.10.10.2/32
R5 – 10.10.10.5/32
R6 – 10.10.10.6/32
R3 – 10.10.10.3/32
R4 – 10.10.10.4/32
R7 – 10.10.10.7/32
R8 – 10.10.10.8/32

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S01M01 Ed0 7
 IPv4 Addresses and Ports
PC9 R5 R6 PC10
1/1/4 1/1/4
eth1 1/1/5 10.1.5.5/28 10.2.6.6/28 1/1/5 eth1

R1 R2
1/1/5 1/1/2 1/1/2 1/1/5
10.1.5.1/28 10.1.2.1/28 10.1.2.2/28 10.2.6.2/28

1/1/1 1/1/1
10.1.3.1/28 10.2.4.2/28

1/1/1 1/1/1
10.1.3.3/28 10.2.4.4/28

1/1/5 1/1/2 1/1/2 1/1/5

10.3.7.3/28 10.3.4.3/28 10.3.4.4/28 10.4.8.4/28
R3 R4
PC11 PC12

eth1 1/1/5 1/1/5 eth1

1/1/4 1/1/4
10.3.7.7/28 10.4.8.8/28
R7 R8

8 Nokia 2020
© Nokia Confidential

R1 to R4 are Border or Core routers.

R5 to R8 are Edge routers.

Each pair of students has one Border and one Edge routers.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S01M01 Ed0 8
 IPv6 Addresses and Ports
PC9 R5 R6 PC10
1/1/4 1/1/4
eth1 1/1/5 2001:db8:15::1:5:5/64 2001:db8:26::2:6:6/64 1/1/5 eth1

R1 R2
1/1/5 1/1/2 1/1/5
2001:db8:15::1:5:1/64 2001:db8:12::1:2:1/64 2001:db8:26::2:6:2/64
1/1/2
2001:db8:12::1:2:2/64
1/1/1 1/1/1
2001:db8:13::1:3:1/64 2001:db8:24::2:4:2/64

1/1/1 1/1/1
2001:db8:13::1:3:3/64 2001:db8:24::2:4:4/64
1/1/2
2001:db8:34::3:4:4/64
1/1/5 1/1/2 1/1/5
2001:db8:37::3:7:3/64 2001:db8:34::3:4:3/64 2001:db8:48::4:8:4/64
R3 R4
PC11 PC12

eth1 1/1/5 1/1/5 eth1

1/1/4 1/1/4
2001:db8:37::3:7:7/64 2001:db8:48::4:8:8/64
R7 R8

9 Nokia 2020
© Nokia Confidential

R1 to R4 are Border or Core routers.

R5 to R8 are Edge routers.

Each pair of students has one Border and one Edge routers.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S01M01 Ed0 9
Wrap-up
In this module we have covered the following items:
• IP address and lab set-up for this course

10Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S01M01 Ed0 10
11Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S01M01 Ed0 11
 CLI Card Port

ER00198-V-2000 V0 - S02M01 Ed0

1 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 1
Learning Objectives
Upon completion of this module, you should be able to:
• Log in to the system
• Recognize Basic SROS CLI structure
• Identify Rollback and Candidate Edit configurations
• Verify Card, Port, MDA and Interface configurations
• Practice Advanced SROS CLI commands

2 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 2
 ToC Slide

Table of Contents

Lab Setup
Basic SROS CLI
Card, Port, and Interface
Advanced SROS CLI
Wrap-up

3 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 3
 Lab Setup

4 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 4
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y) based on their comments.

Initial rollback config file (X) - Initial – OSPF, ISIS, BFD.

• /admin rollback revert X

To compare current config with the final lab answer:

• /admin rollback compare active-cfg to Y

5 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 5
 Basic SROS CLI

6 Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 6
LabLab
Instruction Format
Instruction Format
Note: The following information explains the format used for the labs and is for information
purposes
Switch only.
to notes view!

The CLI system prompt is shown in bolded text followed by # or $, for example:

Node#
or In case you are ready sooner
Node>config>system>security# then the other participants in
any of the labs we will do, an
The CLI command string is shown after the text in bold. optional chapter with CLI tips
and tricks is available at the end.
show time
configure system name <Rx> 

<PEx> is the string (in this case the name of the routers), you do not need to type the <>, in
7 Nokia 2020
© Nokia Confidential
this case the name must be replaced by your string, e.g., R1. In this example:
configure system name R1 

Many of the exercises will be explained using example configuration.

The info command shows us the configuration at the pwc (Present Working Context).

Warning: In the examples we look at a router Rx and the configuration in this router, xx is a
reference to your box number. All address values (addresses and strings) are to be replaced
with your values.

Example:

A:R1>config>router# interface "toR4" PWC is interface toR4.

A:R1>config>router>if# info
----------------------------------------------
address 10.1.4.1/24
port 1/1/2
----------------------------------------------

To view the entire configuration file:

admin display-config

NOTE: Not all commands are mandatory in this lab guide (like show and info), but network and
the underlying layers must be configured before proceeding to the next lab.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 7
Auto Complete
Auto Complete
3 ways to auto-complete commands
Switch to notes view!
Command completion can be achieved by:

Abbreviation, if keystrokes entered are unique enough. The command is auto-completed

R1>config# ro [ENTER]  and activated.
R1>config>router# 

Tab Key or Space Key to auto-complete the command.

R1>config# ro [SPACE]  The command is auto-completed.
R1>config# router 

R1>config# ro [TAB]  TAB will also auto-complete on

R1>config# router  strings/names.
8 Nokia 2020
© Nokia Confidential
If match is not unique CLI will display possible matches:
R1>config# r [TAB] 
redundancy router 

Help: use ?

If you get stuck in commands, try the question mark (?), it will display all possible option with
basic explanation.

A:Rx# configure router ?

- router [<router-name>]

<router-name> : "Base"|"management" Default - Base

[no] aggregate - Create/delete an aggregate route

[no] allow-icmp-red* - Allow or drop ICMP Redirects received on the
management interface
[no] allow-icmp6-re* - Allow or drop IPv6 ICMP Redirects received on the
management interface
[no] autonomous-sys* - Configure the AS number for the router
[no] bgp + Create/Configure or delete BGP instance
[no] confederation - Create/delete confederation autonomous systems within
an AS
dhcp + Configure local DHCP servers
dhcp6 + Configure local DHCPv6 servers
…

Detailed info will pop up. The command stays at it‘s PWC.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 8
Searching Commands
Searching Commands
Tree search
Switch to notes view!
The tree view in our CLI allows us a quick overview of possible commands.
tree flat allows us to search commands.
This way, only keywords need to be remembered to find back the command line in SR-OS.

A:Rx# tree flat

admin
admin application-assurance
admin application-assurance upgrade
admin certificate
admin certificate display
admin certificate export
admin certificate gen-keypair
admin certificate gen-local-cert-req
admin certificate import
admin certificate reload
admin
9 Nokia compare
© 2020 Nokia Confidential

admin debug-save
…

Since the list of commands is very large, narrow it down with match commands.
Example, you want to find all OSPF Neighbors this router has, but you do not know the
command.
Multiple match
A:Rx# tree flat | match ospf | match show
show router ospf
show router ospf area
show router ospf database
show router ospf interface
show router ospf lfa-coverage
show router ospf neighbor
show router ospf opaque-database
show router ospf range
show router ospf routes

Now try to find following commands:

Hint: You can repeat the previous commands using arrow up/down.
• All OSPF debug commands
• How to display the route table

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 9
Logging onOn
Logging
1. With reference to the lab diagram, each student login to their Core (R1 to R4) and Edge (R5 to R8)
routersto
Switch using sshview!
notes and run the following commands:

show system security ssh

show system connections
/config system security  info

Use the command info to show the most important, often non-default, settings within a
configuration context. The info detail command shows ALL settings, including the default, within
a configuration context.

A:R1# configure system security

A:R1>config>system>security# info
----------------------------------------------
no per-peer-queuing
cpu-protection
10Nokia 2020
© link-specific-rate max
Nokia Confidential

policy 254 create

exit
policy 255 create
exit
port-overall-rate 15000
exit
dist-cpu-protection
policy "_default-access-policy" create
exit
policy "_default-network-policy" create
exit
exit

show command does not have any impact on the configuration. They just provide the user with
information. But rather than with the info command, the show commands provide a structured report.
show commands can be launched at any context (since they do not have any impact)

show system information

show chassis
show version
show uptime
show system cpu
show system connections
show users
show log log-id 99

2. Change the login idle timeout (default 30 minutes) using the command:
configure system login-control idle-timeout 500

A:R1# configure system login-control

A:R1>config>system>login-control# idle-timeout 500
A:R1>config>system>login-control# info
----------------------------------------------
idle-timeout 500
----------------------------------------------

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 10
Boot Option
Boot FileFile
Option (BOF)
(BOF)
When a 7705 SAR and 7750 SR boots up, it executes the boot loader (boot.ldr) located on the
Compact
SwitchFlash cardview!
to notes CF3:, then loads the BOF (bof.cfg), also on CF3:, which tells the router
where to find the image (.tim files) and configuration files (.cfg files). The bof also configures
the management Ethernet and serial console ports (default serial port speed 115200) and
activates persistence, used for the NSP application.

1. Check the BOF file (Warning, do not change anything)

A:R1# show bof

==============================================================================
BOF (Memory)
==============================================================================
primary-image cf3:\timos\
primary-config cf3:\config.cfg
license-file tftp://10.0.10.100/license.txt
address 10.0.10.1/24 active
© autonegotiate
11Nokia 2020 Nokia Confidential
duplex full
speed 100
wait 3
persist off
no li-local-save
no li-separate
no fips-140-2
console-speed 115200
system-base-mac 00:25:ba:01:00:00
==============================================================================

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 11
FileFile
System and
System Boot
and Cycle
Boot Cycle
1. Try out the following file commands such as dir and type config.cfg
Switch to notes view!
A:R1# file
A:R1>file cf3:\ # dir

Volume in drive cf3 on slot A is SROS VM.

Volume in drive cf3 on slot A is formatted as FAT32

Directory of cf3:\

05/05/2018 07:36p <DIR> .ssh/

05/10/2018 06:23a 811 config.cfg
<< skip >>

12Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 12
NTPNTP
(Network Time Protocol)
[Optional]

Time and date

Switch are view!
to notes important in a node (e.g. Alarm timestamp). It is also important that all
nodes have the same date and time configured.
We can configure the time and date of the node manually, or we can use an NTP server.

1. Configure the NTP server (10.0.10.100).

Before configuration:

A:Rx# show system ntp

========================================================================
NTP Status
========================================================================
Configured : No

13Nokia 2020
© Nokia Confidential

Configuration example:

A:Rx>config>system>time# info
----------------------------------------------
ntp
server 10.0.10.100
no shutdown
exit

Run the show command again:

A:Rx>config>system>time# show system ntp

==============================================================================
NTP Status
==============================================================================
Configured : Yes Stratum : 3
Admin Status : up Oper Status : up
Server Enabled : No Server Authenticate : No
Clock Source : 10.0.10.100
Auth Check : Yes
Current Date & Time: 2020/06/02 07:54:52 UTC
==============================================================================

Try also the following commands:

show system ntp all 
show system ntp detail 

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 13
Rollback Configuration

SROS offers the following useful commands for config rollback management:
Show the rollback files that are saved on the router:
• show system rollback

Change the router’s configure to rollback file index X:

• /admin rollback revert X

Append the active config to the top of the rollback file index (i.e., latest-rb):
• /admin rollback save comment “xyz”

Compare the current active config with a rollback file index:

• /admin rollback compare active-cfg to X

14Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 14
Rollback Configuration Commands

Students login to their Core and Edge routers to exercise the following rollback
configuration commands:
• show system rollback
• /admin rollback revert X
• /admin rollback compare active-cfg to X

15Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 15
Answer – Rollback Configuration Commands

Index and comment of each rollback config file are shown:

A:R1# show system rollback
===============================================================================
Rollback Information
===============================================================================
Rollback Location : cf3:\ER00098\R1
Max Local Rollback Files : 50
Max Remote Rollback Files : 10
Save
Last Rollback Save Result : Successful
Last Save Completion Time : 2020/06/12 13:54:04 UTC
Revert
In Progress : No
Last Revert Initiated User : admin
Last Revert Checkpoint File: cf3:\ER00098\R1.rb.1
Last Revert Result : Successful
Last Revert Initiated Time : 2020/06/16 07:59:06 UTC
Last Revert Completion Time: 2020/06/16 07:59:06 UTC
Delete
Last Rollback Delete Result: None

===============================================================================
Rollback Files
===============================================================================
Idx Suffix Creation Time Release User
Comment
-------------------------------------------------------------------------------
1 .rb.1 2020/06/14 06:07:26 UTC C-20.2.R1 admin
Initial - OSPF, ISIS and BFD
2 .rb.2 2020/06/14 05:57:38 UTC C-20.2.R1 admin
Final - OSPF, ISIS and BFD

16Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 16
Candidate Edit

Beside Rollback, SROS also offers transactional config editing via Candidate Config.

17Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 17
Candidate Edit [cont.]
When in Candidate mode, commands entered will take no effect to the router until candidate commit command is
issued. A:Rx# candidate edit exclusive
Exclusive – Allow only one
A:Rx>edit-cfg# configure transactional edition session
A:Rx>edit-cfg>config# filter ip-filter 10 create
A:Rx>edit-cfg>config>filter>ip-filter# entry 10 create
A:Rx>edit-cfg>config>filter>ip-filter>entry# match 10.0.0.0/8
A:Rx>edit-cfg>config>filter>ip-filter>entry>match# exit
A:Rx>edit-cfg>config>filter>ip-filter>entry# action forward
A:Rx>edit-cfg>config>filter>ip-filter>entry# exit
A:Rx>edit-cfg>config>filter>ip-filter# exit all
A:Rx>edit-cfg#
A:Rx>edit-cfg# candidate view Cannot use the info command
---------------------------------------------- in candidate edit mode
1: configure
2: filter
3: ip-filter "10" create
4: entry 10 create
5: match
6: src-ip "10.0.0.0/8"
7: exit
8:* action forward
9: exita
10: exit
11: exit
12: exit
---------------------------------------------- If no candidate confirm is
A:Rx>edit-cfg# issued within 10 minutes, the
A:Rx>edit-cfg# candidate commit confirm 10 changes made by candidate
Processing current config... 0.020 s commit are rollback or undone
Saving checkpoint file... OK
INFO: CLI Successfully executed 12 lines in 0.000 s.
A:Rx#
18Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 18
 Card, Port, and Interface

19Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 19
Objectives

The objectives of this lab exercise is to allow students to understand the setup of port,
card, MDA and interface using the initial lab configuration.

The subsequent lab exercises will add various networking features on top of this initial
router configuration.

20Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 20
Lab - Card and MDA

Each pair of students' log in to their Core (R1 to R4) and Edge (R5 to R8) routers to examine the
hardware setup of the routers:
• show system information
• show chassis
• show redundancy synchronization
• show card
• show mda
• show port

Highlight the important information that are revived by the commands.

21Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 21
 Answer – System Information
Important information shown:
• Name of the system
• System Type
• Software version
• Up time
• Management IP address
A:R1# show system information

===============================================================================
System Information
===============================================================================
System Name : R1
System Type : 7750 SR-12e
Chassis Topology : Standalone
System Version : C-20.2.R1

System Active Slot : A

System Up Time : 11 days, 23:31:06.83 (hr:min:sec)

BOF Source : cf3:

Image Source : primary
Config Source : primary
Last Booted Config File: cf3:\config.cfg
<< skip >>
Management IP Addr : 10.0.10.1/24

22Nokia 2020
© Nokia Confidential

Depending on the chassis type and IOM type, the following modes can be configured:
• Chassis Mode A: This mode corresponds to scaling and feature set associated with iom-20g
• Chassis Mode B: This mode corresponds to scaling and feature set associated with
iom-20g-b
• Chassis Mode C: This mode corresponds to scaling and feature set associated with iom2-20g
• Chassis Mode D: This mode corresponds to scaling and feature set associated with iom3-xp

When configuring a chassis mode, use Chassis Mode that aligns with the earliest generation of
IOM installed. If the chassis mode is not explicitly provisioned in the configuration file, the
chassis will come up in Mode A by default.
In Mode A:
• iom-20g-b comes online if provisioned as iom-20g or iom-20g-b
• iom2-20g comes online if provisioned as iom-20g, iom-20g-b or iom2-20g
• iom3 comes online if provisioned as iom3

All IOMs must be IOM3-XP or IMMs in order to configure chassis mode D.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 22
Answer – Chassis
Chassis Mode does not apply to the SAR or SAS, 7950 XRS. Mainly used in 7750 SR family.
Different chassis modes support different cards and features (e.g., IPv6).
A:R1# show chassis
===============================================================================
System Information
===============================================================================
Name : R1
Type : 7750 SR-12e
Chassis Topology : Standalone
Location : (Not Specified)
Coordinates : (Not Specified)
CLLI code :
Number of slots : 11
Oper number of slots : 11
Num of faceplate ports/connectors : 12
Num of physical ports : 12
Critical LED state : Off
Major LED state : Off
Minor LED state : Off
Over Temperature state : OK
Base MAC address : 00:25:ba:01:00:00
Fabric Speed : S4
FP Generations : FP3
System Profile : none
===============================================================================
Chassis Summary
===============================================================================
Chassis Role Status
-------------------------------------------------------------------------------
1 Standalone up
===============================================================================
23Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 23
Answer – Non-Stop Routing

Non-Stop Routing is available when redundancy Switching Fabric Module (SFM) is employed:
• Below SR does not support non-stop routing as it has only one SFM
A:R1# show card
Card Summary
===============================================================================
Slot Provisioned Type Admin Operational Comments A:R1# show redundancy synchronization
Equipped Type (if different) State State
------------------------------------------------------------------------------- ===========================================================
1 iom4-e-b up up Synchronization Information
2 (not provisioned) up unprovisioned ===========================================================
iom4-e-b Standby Status : disabled
A cpm5 up up/active Last Standby Failure : N/A
B cpm5 up down/standby Standby Up Time : N/A
(not equipped) Standby Version : N/A
=============================================================================== Failover Time : N/A
Failover Reason : N/A
Boot/Config Sync Mode : None
A:R1# show sfm Boot/Config Sync Status : No synchronization
=============================================================================== Last Config File Sync Time : Never
SFM Summary Last Boot Env Sync Time : Never
=============================================================================== Rollback Sync Mode : None
Slot Provisioned Type Admin Operational Comments Rollback Sync Status : No Rollback synchronization
Equipped Type (if different) State State Last Rollback Sync Time : Never
------------------------------------------------------------------------------- Certificate Sync : Enabled
1 m-sfm6-12e up up Cert Sync Status : unknown
2 (not provisioned) up unprovisioned Last Cert Sync Time : Never
m-sfm6-12e
3 (not provisioned) up unprovisioned
m-sfm6-12e
===============================================================================

24Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 24
Answer – Card and MDA
• Slot/Card 1 is equipped with IOM, iom4-e-b that is UP.
A:R1# show card
===============================================================================
Card Summary
===============================================================================
Slot Provisioned Type Admin Operational Comments
Equipped Type (if different) State State
-------------------------------------------------------------------------------
1 iom4-e-b up up
2 (not provisioned) up unprovisioned
iom4-e-b
A cpm5 up up/active
B cpm5 up down/standby
(not equipped)
===============================================================================

• IOM, iom4-e-b can contain two MDA cards. The 1st MDA slot is equipped with
the 12 port 1Gb/10Gb Ethernet card that is operational.
A:R1# show mda
===============================================================================
MDA Summary
===============================================================================
Slot Mda Provisioned Type Admin Operational
Equipped Type (if different) State State
-------------------------------------------------------------------------------
1 1 me12-10/1gb-sfp+ up up
2 (not provisioned) up unprovisioned
me-isa2-ms
===============================================================================

• The 2nd MDA is an isa-ms card but it has not yet provisioned by the user.
25Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 25
Answer – Port
A:R1# show port
===============================================================================
• Status of the 12 ports Ports on Slot 1
===============================================================================
MDA, Port Admin Link Port Cfg Oper LAG/ Port Port Port C/QS/S/XFP/
me12-10/1gb-sfp+ Id State State MTU MTU Bndl Mode Encp Type MDIMDX
-------------------------------------------------------------------------------
shown 1/1/1
1/1/2
Up
Up
Yes Up
Yes Up
8704 8704
8704 8704
- netw null vspeed 10GBASE-LR *
- netw null vspeed 10GBASE-LR *
- Example: port 1/1/3 1/1/3 Up Yes Up 8704 8704 - netw null vspeed 10GBASE-LR *
means 1/1/4
<< skip >>
Up Yes Up 8704 8704 - netw null vspeed 10GBASE-LR *

slot 1, MDA 1, port 3 1/1/11 Down No Down 8704 8704 - netw null vspeed 10GBASE-LR *
1/1/12 Down No Down 8704 8704 - netw null vspeed 10GBASE-LR *

===============================================================================
Ports on Slot A
- Switching Fabric A ===============================================================================
Port Admin Link Port Cfg Oper LAG/ Port Port Port C/QS/S/XFP/
(primary) Id State State MTU MTU Bndl Mode Encp Type MDIMDX
-------------------------------------------------------------------------------
A/1 Up Yes Up 1514 1514 - netw null faste MDI
A/3 Down No Ghost 1514 1514 - netw null faste
A/4 Up No Ghost 1514 1514 - netw null faste

===============================================================================
Ports on Slot B
- Switching Fabric B ===============================================================================
Port Admin Link Port Cfg Oper LAG/ Port Port Port C/QS/S/XFP/
(Backup) Id State State MTU MTU Bndl Mode Encp Type MDIMDX
-------------------------------------------------------------------------------
B/1 Up No Ghost 1514 1514 - netw null faste
B/3 Down No Ghost 1514 1514 - netw null faste
B/4 Up No Ghost 1514 1514 - netw null faste

26Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 26
Interface Connectivity and Route-Table

To get familiar with the initial lab setup, each pair of students should log in to their Edge and Core
routers and use the following commands to verify the IPv4 and IPv6 connectivity of the Interfaces and
their addresses:
• Show IPv4 and IPv6 routing table:
- show router route-table
- show router route-table ipv6
• IPv4 and IPv6 system address connectivity:
- ping 10.10.10.x
- ping 2001:db8:xy::x:y:x
• IPv4 and IPv6 network port connectivity:
- ping 10.x.y.z
- ping 3ffe::1:x0x:x0x

Explain the ping results.

27Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 27
Answer – Ping Connectivity Test

IPv4 and IPv6 ping to their adjacent neighbor interfaces are OK.
A:R1# ping 10.1.2.2
PING 10.1.2.2 56 data bytes
64 bytes from 10.1.2.2: icmp_seq=1 ttl=64 time=4.37ms.
64 bytes from 10.1.2.2: icmp_seq=2 ttl=64 time=2.35ms.
64 bytes from 10.1.2.2: icmp_seq=3 ttl=64 time=1.97ms.

A:R1# ping 2001:db8:12::1:2:2

PING 2001:db8:12::1:2:2 56 data bytes
64 bytes from 2001:db8:12::1:2:2 icmp_seq=1 hlim=64 time=5.39ms.
64 bytes from 2001:db8:12::1:2:2 icmp_seq=2 hlim=64 time=1.79ms.
64 bytes from 2001:db8:12::1:2:2 icmp_seq=3 hlim=64 time=2.00ms.

Ping to your own system address is fine but since there is no IPv4 and IPv6 IGP protocols running yet, ping to remote
IPv4 and IPv6 system addresses fails.
A:R1# ping 10.10.10.1
PING 10.10.10.1 56 data bytes
64 bytes from 10.10.10.1: icmp_seq=1 ttl=64 time=0.055ms.
64 bytes from 10.10.10.1: icmp_seq=2 ttl=64 time=0.047ms.
64 bytes from 10.10.10.1: icmp_seq=3 ttl=64 time=0.050ms.

A:R1# ping 10.10.10.2

PING 10.10.10.2 56 data bytes
No route to destination. Address: 10.10.10.2, Router: Base
No route to destination. Address: 10.10.10.2, Router: Base

28Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 28
Answer – IPv4 Route-Table

IPv4 routing table:

A:R1# show router route-table

===============================================================================
Route Table (Router: Base)
===============================================================================
Dest Prefix[Flags] Type Proto Age Pref
Next Hop[Interface Name] Metric
-------------------------------------------------------------------------------
1.1.1.1/32 Local Local 04d01h10m 0
loopback 0
10.1.2.0/28 Local Local 04d01h10m 0
toR2 0
10.1.3.0/28 Local Local 04d01h10m 0
toR3 0
10.1.5.0/28 Local Local 04d00h25m 0
toR5 0
10.10.10.1/32 Local Local 04d01h10m 0
system 0
-------------------------------------------------------------------------------
No. of Routes: 5
Flags: n = Number of times nexthop is repeated
B = BGP backup route available
L = LFA nexthop available
S = Sticky ECMP requested
===============================================================================
29Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 29
Answer – IPv6 Route-Table

IPv6 routing table:

A:R1# show router route-table ipv6

===============================================================================
IPv6 Route Table (Router: Base)
===============================================================================
Dest Prefix[Flags] Type Proto Age Pref
Next Hop[Interface Name] Metric
-------------------------------------------------------------------------------
2001:db8:0:1::1/128 Local Local 06h20m55s 0
loopback 0
2001:db8:12::/64 Local Local 06h20m55s 0
toR2 0
2001:db8:13::/64 Local Local 06h20m55s 0
toR3 0
2001:db8:15::/64 Local Local 06h20m56s 0
toR5 0
3ffe::1:101:101/128 Local Local 06h20m56s 0
system 0
-------------------------------------------------------------------------------
No. of Routes: 5
Flags: n = Number of times nexthop is repeated
B = BGP backup route available
L = LFA nexthop available
S = Sticky ECMP requested
===============================================================================
30Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 30
 Advanced SROS CLI

31Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 31
CLICLI
Tips and
Tips Tricks
and Tricks
If you happen to be faster then the other students in the training, here are some tips and
tricks to keep
Switch you busy.
to notes view!

Ranges in CLI
With ranges, commands can be given to a set of objects at once. If you like to activate ports
1/1/9, 1/1/10, and 1/1/11. Use the command,
configure port 1/1/[9..11] no shutdown

A:R1# configure port 1/1/[9..11] no shutdown

A:R1# show port
==============================================================================
Ports on Slot 1
==============================================================================
Port Admin Link Port Cfg Oper LAG/ Port Port Port C/QS/S/XFP/
Id State State MTU MTU Bndl Mode Encp Type MDIMDX
------------------------------------------------------------------------------
<< ©32
skip
Nokia 2020
>> Nokia Confidential
1/1/7 Up Yes Up 8704 8704 - netw null vspeed 10GBASE-LR *
1/1/8 Up Yes Up 8704 8704 - netw null vspeed 10GBASE-LR *
1/1/9 Up Yes Up 8704 8704 - netw null vspeed 10GBASE-LR *
1/1/10 Up Yes Up 8704 8704 - netw null vspeed 10GBASE-LR *
1/1/11 Up Yes Up 8704 8704 - netw null vspeed 10GBASE-LR *

Note that the autocomplete does not work after range specification.

Multiple Range Commands

Up to a maximum of 6 ranges are supported. For instance, executing a command like configure
filter ip-filter [1..2] create entry [1..2] create no match

Is same as executing the following four commands (loop within a loop):

configure filter ip-filter 1 create entry 1 create no match 
• configure filter ip-filter 1 create entry 1 create no match 
• configure filter ip-filter 1 create entry 2 create no match 
• configure filter ip-filter 2 create entry 1 create no match 
• configure filter ip-filter 2 create entry 2 create no match 

A:R1# configure filter ip-filter [1..2] create entry [1..2] create no match
A:R1# /configure filter
A:R1>config>filter# info
----------------------------------------------
ip-filter 1 create
entry 1 create
exit
entry 2 create
exit
exit
ip-filter 2 create
entry 1 create
exit
entry 2 create
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 32
CLICLI
Tips and
Tips Tricks
and [cont.]
Tricks [cont.]
This allows us to provide non-contiguous numbers up to a maximum of 20. For instance,
executing thenotes
Switch to command
view! configure filter ip-filter [1,2,5,9] create
default-action forward is same as executing the following four commands (single
loop):

• configure filter ip-filter 1 create default-action forward 

• configure filter ip-filter 2 create default-action forward 
• configure filter ip-filter 5 create default-action forward 
• configure filter ip-filter 9 create default-action forward 

Referenced Range Commands

We have multiple ranges allowed, we can also backward reference another pre-existing range
on the command line. For instance, in the following command configure filter ip-
filter [1..2] create entry [$0] create no match
33Nokia 2020
© Nokia Confidential

The first range [1..2], creates a variable 0, and the second range reference [$0] references the
variable 0. This command will result in the execution of two commands (single loop):
• configure filter ip-filter 1 create entry 1 create no match 
• configure filter ip-filter 2 create entry 2 create no match 

The first range is referenced to create the second range.

Let's consider configure filter ip-filter [1,2] create entry [11..12]

create match src-ip 10.10.[$1].10/32 
The first range [1,2], creates a variable 0, the second range [11..12] creates a variable 1,
whereas the third range [$1] creates a reference to variable 1. In this case 11 and 12 will be
used. This will result in an execution of four commands (loop within a loop):

• configure filter ip-filter 1 create entry 11 create match

src-ip 10.10.11.10/32
• configure filter ip-filter 1 create entry 12 create match
src-ip 10.10.12.10/32
• configure filter ip-filter 2 create entry 11 create match
src-ip 10.10.11.10/32
• configure filter ip-filter 2 create entry 12 create match
src-ip 10.10.12.10/32

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 33
Environment: Create
Environment: Create
You can switch off the need for create for your session using the command.
environment
Switch to notesno create 
view!

From then on you never have to specify the create anymore.

configure service epipe 8888 customer 1 is same as

configure service epipe 8888 customer 1 create

Environment: Reduce prompt

The CLI prompt can be reduced such as environment reduced-prompt 2 

A:R1# configure router interface "system"

A:R1>config>router>if#
34Nokia 2020
© Nokia Confidential
A:R1#
A:R1# environment reduced-prompt 2
A:R1#
A:R1# configure router interface "system"
A:R1>...router>if#

Recalling History

Recalling history command gives you the previous commands. One can be re-issued with the
<#>!

A:R1# history
39 environment reduced-prompt 2
40 configure router interface "system"
41 environment no reduced-prompt
42 show version
43 admin display-config
44 history
A:R1#
A:R1# !42
A:R1# show version
TiMOS-C-20.2.R1 cpm/x86_64 Nokia 7750 SR Copyright (c) 2000-2020 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Sat Feb 29 10:39:32 PST 2020 by builder in
/builds/c/202B/R1/panos/main/sros

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 34
Improving Search
Improving Skills
Search Skills
match is case sensitive.
Switch to notes view!
A:PExx# show port | match up  (No results)

A:R1# show port | match up

A:R1# show port | match Up

1/1/1 Up Yes Up 8704 8704 - netw null vspeed 10GBASE-LR *
1/1/2 Up Yes Up 8704 8704 - netw null vspeed 10GBASE-LR *
1/1/3 Up Yes Up 8704 8704 - netw null vspeed 10GBASE-LR *
1/1/4 Up Yes Up 8704 8704 - netw null vspeed 10GBASE-LR *
1/1/5 Up Yes Up 8704 8704 - netw null vspeed 10GBASE-LR *
1/1/6 Up Yes Up 8704 8704 - netw null vspeed 10GBASE-LR *
1/1/7 Up Yes Up 8704 8704 - netw null vspeed 10GBASE-LR *
1/1/8 Up Yes Up 8704 8704 - netw null vspeed 10GBASE-LR *
A/1 Up Yes Up 1514 1514 - netw null faste MDI
A/4 Up No Ghost 1514 1514 - netw null faste
B/1 Up No Ghost 1514 1514 - netw null faste
35 Nokia Confidential
B/4© Nokia 2020 Up No Ghost 1514 1514 - netw null faste

Something shutdown in the router?

Search the configuration and include some pre-lines to find the context:
admin display-config | match shutdown pre-lines 3 

A:R1# admin display-config | match shutdown pre-lines 3

exit
time
sntp
shutdown
#--------------------------------------------------
***Output omitted***

show port | match ?

A:R1# show port | match ?

- match <pattern> context {parents|children|all} [ignore-case] [max-count
<lines-count>] [expression]
- match <pattern> [ignore-case] [invert-match] [pre-lines <pre-lines>]
[post-lines <lines-count>] [max-count <lines-count>]
[expression]

<pattern> : string or regular expression - [200 chars max]

<pre-lines> : [0..100]
<lines-count> : [1..2147483647]
<expression> : Keyword - Interpret the pattern as a regex expression

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 35
Wrap-up
In this module we have covered the following items:
• Log in to the system
• Basic SROS CLI structure
• Rollback and Candidate Edit configurations
• Card, Port, MDA and Interface configurations
• Advanced SROS CLI commands

36Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 36
37Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S02M01 Ed0 37
 OSPF ISIS BFD

ER00198-V-2000 V0 - S03M01 Ed0

1 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 1
Learning Objectives
Upon completion of this module, you should be able to:
• Activate IGP in the network:
- OSPF
- ISIS
- Metrics
- Preference
- Routing policy redistribution
- Internal and External routes distribution
• Configure Bidirectional Forward Detection (BFD)

2 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 2
 ToC Slide

Table of Contents

Lab Setup
OSPF
ISIS
IGP Metric
Loopfree-Alternate
Policy and IGP Route Redistribution
OSPFv3
BFD
Wrap-up

3 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 3
 Lab Setup

4 Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 4
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y) based on their comments.

Initial rollback config file (X) - Initial - OSPF, ISIS and BFD.
• /admin rollback revert X

Final rollback config file (Y) – Final - OSPF.

To compare current config with the final lab answer:

• /admin rollback compare active-cfg to Y

5 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 5
 OSPF

6 Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 6
LabLab
1 – 1OSPF IPv4
– OSPF Configuration
IPv4 Configuration
Each pair of student will configure their Edge (R5 – R8) and Core (R1 – R4) routers such that all
routers in to
Switch thenotes
lab are in OSPF area 0.0.0.0 to support IPv4 routing.
view!

Configuration of OSPF is done at interface level. The interface is added to an OSPF area.

Example configuration
1. Make sure you also activate OSPF toward each neighbor in the network.

2. Verify your configuration.

PEx# show router route-table 

PEx# show router fib 1  ( IOM card)
PEx# show router ospf status 
PEx# show router ospf area 
PEx# show router ospf interface 
7 Nokia 2020
© Nokia Confidential
PEx# show router ospf database 

Note: The system interface should not be configured point to point. Unless otherwise
specified, the default values are followed.

Loopfree-alternates: is required for LDP FRR (Label Distribution Protocol – Fast ReRoute).

See further.
Traffic engineering: is required for MPLS tunnels created with RSVP-TE – see further.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 7
 Answer 1 – OSPF IPv4 Configuration and Verification

Each router has OSPF neighbors with its adjacent core and edge routers.
A:R1>config>router>ospf# info A:R5>config>router>ospf# info
---------------------------------------------- ----------------------------------------------
area 0.0.0.0 area 0.0.0.0
interface "system" interface "system"
no shutdown no shutdown
exit exit
interface "toR2" interface "toR1"
interface-type point-to-point interface-type point-to-point
no shutdown no shutdown
exit exit
interface "toR3" exit
interface-type point-to-point no shutdown
no shutdown
exit
interface "toR5"
interface-type point-to-point
no shutdown
exit
exit
no shutdown

8 Nokia 2020
© Nokia Confidential

Similarly, other groups can perform these configurations with respect to their assigned routers.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 8
Answer 1 –1IPv4
Answer Route-Table
– IPv4 Route-Table
Locally defined and OSPF learnt route entries form the routing table.
Switch to notes view!
A:R1# show router route-table

==============================================================================
Route Table (Router: Base)
==============================================================================
Dest Prefix[Flags] Type Proto Age
Pref
Next Hop[Interface Name] Metric
------------------------------------------------------------------------------
1.1.1.1/32 Local Local 04d00h42m 0
loopback 0
10.1.2.0/28 Local Local 04d00h42m 0
toR2 0
10.1.3.0/28 Local Local 04d00h42m 0
toR3 0
10.1.5.0/28 Local Local 04d00h42m 0
toR5
9 Nokia 2020
© Nokia Confidential 0
10.2.4.0/28 Remote OSPF 00h22m00s 10
10.1.2.2 20
10.2.6.0/28 Remote OSPF 00h22m00s 10
10.1.2.2 20
10.3.4.0/28 Remote OSPF 00h18m44s 10
10.1.3.3 20
10.3.7.0/28 Remote OSPF 00h18m44s 10
10.1.3.3 20
10.4.8.0/28 Remote OSPF 00h16m36s 10
10.1.2.2 30
10.10.10.1/32 Local Local 04d00h42m 0
system 0
10.10.10.2/32 Remote OSPF 00h22m00s 10
10.1.2.2 10
10.10.10.3/32 Remote OSPF 00h18m44s 10
10.1.3.3 10
10.10.10.4/32 Remote OSPF 00h16m36s 10
10.1.2.2 20
10.10.10.5/32 Remote OSPF 00h05m10s 10
10.1.5.5 10
10.10.10.6/32 Remote OSPF 00h03m23s 10
10.1.2.2 20
10.10.10.7/32 Remote OSPF 00h01m46s 10
10.1.3.3 20
10.10.10.8/32 Remote OSPF 00h00m23s 10
10.1.2.2 30
------------------------------------------------------------------------------
No. of Routes: 17
Flags: n = Number of times nexthop is repeated
B = BGP backup route available
L = LFA nexthop available
S = Sticky ECMP requested
==============================================================================

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 9
Answer 1 –1FIB
Answer – FIB
The 17 route entries are complied and downloaded onto the IOM’s Forwarding Information
Base (FIB).
The 17 route entries are complied and downloaded onto the IOM’s Forwarding Information Base (FIB).

A:R1# show router fib 1

==============================================================================
FIB Display
==============================================================================
Prefix [Flags] Protocol
NextHop
------------------------------------------------------------------------------
1.1.1.1/32 LOCAL
1.1.1.1 (loopback)
10.1.2.0/28 LOCAL
10.1.2.0 (toR2)
10.1.3.0/28 LOCAL
10.1.3.0 (toR3)
10.1.5.0/28 LOCAL
10.1.5.0
10Nokia 2020
© (toR5) Nokia Confidential

10.2.4.0/28 OSPF
10.1.2.2 (toR2)
10.2.6.0/28 OSPF
10.1.2.2 (toR2)
10.3.4.0/28 OSPF
10.1.3.3 (toR3)
10.3.7.0/28 OSPF
10.1.3.3 (toR3)
10.4.8.0/28 OSPF
10.1.2.2 (toR2)
10.10.10.1/32 LOCAL
10.10.10.1 (system)
10.10.10.2/32 OSPF
10.1.2.2 (toR2)
10.10.10.3/32 OSPF
10.1.3.3 (toR3)
10.10.10.4/32 OSPF
10.1.2.2 (toR2)
10.10.10.5/32 OSPF
10.1.5.5 (toR5)
10.10.10.6/32 OSPF
10.1.2.2 (toR2)
10.10.10.7/32 OSPF
10.1.3.3 (toR3)
10.10.10.8/32 OSPF
10.1.2.2 (toR2)
------------------------------------------------------------------------------
Total Entries : 17
------------------------------------------------------------------------------
==============================================================================

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 10
Answer 1 - Area and Interface

OSPF Area:
A:R1# show router ospf area

==================================================================
Rtr Base OSPFv2 Instance 0 Areas
==================================================================
Area Id Type SPF Runs LSA Count LSA Cksum Sum
------------------------------------------------------------------
0.0.0.0 Standard 13 16 0x5f39e
------------------------------------------------------------------
No. of OSPF Areas: 1
==================================================================

A:R5# show router ospf area

==================================================================
Rtr Base OSPFv2 Instance 0 Areas
==================================================================
Area Id Type SPF Runs LSA Count LSA Cksum Sum
------------------------------------------------------------------
0.0.0.0 Standard 7 16 0x5f19f
------------------------------------------------------------------
No. of OSPF Areas: 1
==================================================================

11Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 11
Answer 1 - Area and Interface [cont.]

OSPF Interfaces:
A:R1# show router ospf interface

===============================================================================
Rtr Base OSPFv2 Instance 0 Interfaces
===============================================================================
If Name Area Id Designated Rtr Bkup Desig Rtr Adm Oper
-------------------------------------------------------------------------------
system 0.0.0.0 10.10.10.1 0.0.0.0 Up DR
toR2 0.0.0.0 0.0.0.0 0.0.0.0 Up PToP
toR3 0.0.0.0 0.0.0.0 0.0.0.0 Up PToP
toR5 0.0.0.0 0.0.0.0 0.0.0.0 Up PToP
-------------------------------------------------------------------------------
No. of OSPF Interfaces: 4
===============================================================================

A:R5# show router ospf interface

===============================================================================
Rtr Base OSPFv2 Instance 0 Interfaces
===============================================================================
If Name Area Id Designated Rtr Bkup Desig Rtr Adm Oper
-------------------------------------------------------------------------------
system 0.0.0.0 10.10.10.5 0.0.0.0 Up DR
toR1 0.0.0.0 0.0.0.0 0.0.0.0 Up PToP
-------------------------------------------------------------------------------
No. of OSPF Interfaces: 2

12Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 12
Answer 1 - Status and Database

OSPF Status: OSPF Database:

A:R1# show router ospf status A:R1# show router ospf database

======================================================= ===============================================================================
Rtr Base OSPFv2 Instance 0 Status Rtr Base OSPFv2 Instance 0 Link State Database (type: All)
======================================================= ===============================================================================
OSPF Cfg Router Id : 0.0.0.0 Type Area Id Link State Id Adv Rtr Id Age Sequence Cksum
OSPF Oper Router Id : 10.10.10.1 -------------------------------------------------------------------------------
OSPF Version : 2 Router 0.0.0.0 10.10.10.1 10.10.10.1 797 0x80000009 0x2c4
OSPF Admin Status : Enabled Router 0.0.0.0 10.10.10.2 10.10.10.2 696 0x80000008 0x8c2c
OSPF Oper Status : Enabled Router 0.0.0.0 10.10.10.3 10.10.10.3 599 0x80000008 0xf0b8
Graceful Restart : Disabled Router 0.0.0.0 10.10.10.4 10.10.10.4 518 0x80000008 0xa9f0
GR Helper Mode : Disabled Router 0.0.0.0 10.10.10.5 10.10.10.5 798 0x80000004 0x17e
GR Strict LSA Checking : Enabled (operational down) Router 0.0.0.0 10.10.10.6 10.10.10.6 698 0x80000004 0x6d09
<< skip >> Router 0.0.0.0 10.10.10.7 10.10.10.7 600 0x80000004 0xd993
Router 0.0.0.0 10.10.10.8 10.10.10.8 519 0x80000004 0xe281
-------------------------------------------------------------------------------
No. of LSAs: 8
===============================================================================

13Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 13
Answer 1 - Status and Database [cont.]

OSPF Status: OSPF Database:

A:R5# show router ospf status A:R5# show router ospf database

========================================================= ===============================================================================
Rtr Base OSPFv2 Instance 0 Status Rtr Base OSPFv2 Instance 0 Link State Database (type: All)
========================================================= ===============================================================================
OSPF Cfg Router Id : 0.0.0.0 Type Area Id Link State Id Adv Rtr Id Age Sequence Cksum
OSPF Oper Router Id : 10.10.10.5 -------------------------------------------------------------------------------
OSPF Version : 2 Router 0.0.0.0 10.10.10.1 10.10.10.1 898 0x80000009 0x2c4
OSPF Admin Status : Enabled Router 0.0.0.0 10.10.10.2 10.10.10.2 797 0x80000008 0x8c2c
OSPF Oper Status : Enabled Router 0.0.0.0 10.10.10.3 10.10.10.3 700 0x80000008 0xf0b8
Graceful Restart : Disabled Router 0.0.0.0 10.10.10.4 10.10.10.4 619 0x80000008 0xa9f0
GR Helper Mode : Disabled Router 0.0.0.0 10.10.10.5 10.10.10.5 897 0x80000004 0x17e
GR Strict LSA Checking : Enabled (operational down) Router 0.0.0.0 10.10.10.6 10.10.10.6 799 0x80000004 0x6d09
<< skip >> Router 0.0.0.0 10.10.10.7 10.10.10.7 701 0x80000004 0xd993
Router 0.0.0.0 10.10.10.8 10.10.10.8 620 0x80000004 0xe281
-------------------------------------------------------------------------------
No. of LSAs: 8
===============================================================================

14Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 14
Answer 1 -1Showing
Answer OSPF
- Showing OSPFDefault
DefaultValues
Values
To see the default values: info detail
Switch to notes view!
Try this with the system interface.
Note that the default values are not show with the info command or with the
admin display-config

A:R1# configure router ospf

A:R1>config>router>ospf# area 0.0.0.0
A:R1>config>router>ospf>area# interface "system"
A:R1>config>router>ospf>area>if# info detail
----------------------------------------------
passive
no interface-type
advertise-subnet
no node-sid
no rib-priority
15Nokia 2020
©
priority 1 Nokia Confidential
hello-interval 10
dead-interval 40
retransmit-interval 5
transit-delay 1
no mtu
no load-balancing-weight
no poll-interval
no metric
no auth-keychain
no authentication-type
no authentication-key
no bfd-enable
no lsa-filter-out
no adjacency-sid
no loopfree-alternate-exclude
no lfa-policy-map
sid-protection
advertise-router-capability
no shutdown
----------------------------------------------

Also try this one:

admin display-config | match ospf context all 

Find out the difference between following commands:

admin display-config | match ospf context parents 

admin display-config | match ospf context children 

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 15
Debugging OSPF
Debugging OSPF
Possible debug commands on OPSF:
Switch to notes view!
A:R1# debug router ospf
A:R1>debug>router>ospf#
[no] area - Debug OSPFv2 area
[no] area-range - Debug OSPFv2 area range
[no] cspf - Debug OSPFv2 cspf
[no] graceful-resta* - Debug OSPFv2 graceful-restart
[no] interface - Debug OSPFv2 interface
[no] leak - Debug OSPFv2 leaked external routes
[no] lsdb - Debug OSPFv2 link-state database (LSDB)
[no] misc - Debug OSPFv2 miscellaneous events
[no] neighbor - Debug OSPFv2 neighbor
[no] nssa-range - Debug OSPFv2 NSSA range
[no] packet - Debug OSPFv2 packets
[no] rsvp-shortcut - Debug OSPFv2 rsvp-shortcut
[no] rtm - Debug OSPFv2 rtm
[no] sham-neighbor - Debug OSPFv2 sham-link neighbor
[no]
16Nokia spf
© 2020 - Debug OSPFv2Nokia
spf Confidential
[no] tunnel-endpoint - Debug OSPFv2 tunnel endpoint
[no] virtual-neighb* - Debug OSPFv2 virtual neighbor

Try debugging of OSPF packets by creating a log to session and invoke the following debug
command:
/debug router ospf packet 

A:R1# configure log log-id 6

A:R1>config>log>log-id$ from debug-trace
A:R1>config>log>log-id$ to session
A:R1>config>log>log-id$

A:R1# debug router ospf packet

A:R1#
1 2020/06/17 15:10:26.443 UTC MINOR: DEBUG #2001 Base OSPFv2
"OSPFv2: PKT

>> Outgoing OSPF packet on I/F toR2 area 0.0.0.0

OSPF Version : 2
Router Id : 10.10.10.1
Area Id : 0.0.0.0
Checksum : d393
Auth Type : Null
Auth Key : 00 00 00 00 00 00 00 00
Packet Type : HELLO
Packet Length : 48 “
...

To stop debugging messages from showing onto the screen, run the command:
/no debug 

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 16
 ISIS

17Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 17
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y) based on their comments.

Initial rollback config file (X) – Final OSPF.

• /admin rollback revert X

Final rollback config file (Y) – Final - ISIS.

To compare current config with the final lab answer:

• /admin rollback compare active-cfg to Y

18Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 18
ISISISIS

ISIS is configured in a rather similar way as OSPF. Notice the small differences.
Switch to notes view!
1. Configure IS-IS using area 49.0000
2. Add all your interfaces

A:R1>config>router>isis# info
----------------------------------------------
area-id 49.0000
reference-bandwidth 100000000 One command to enable ISIS IPv6
ipv6-routing native
level 1 on ISIS Adjacent
wide-metrics-only
exit
level 2
wide-metrics-only
exit
interface "system"
19Nokia 2020
© no shutdown Nokia Confidential
exit
interface "toR2"
interface-type point-to-point
no shutdown
exit
interface "toR3"
interface-type point-to-point
no shutdown
exit
interface "toR5"
interface-type point-to-point
no shutdown
exit
no shutdown
----------------------------------------------

Note: It is common practice to configure the interfaces point-to-point rather than the default
broadcast to avoid the DIS overhead.
Note: With this command the reference bandwidth can be set and the metrics of the links will
be calculated: reference-bandwidth/bandwidth (In OSPF this is done by default).

3. Special case for IS-IS: In regular IS-IS SPF operation, “narrow metrics” are used, meaning the
maximum metric value of any given link will be limited to 63, regardless of the result of
calculation in relation to the reference bandwidth given above. To overcome this restriction,
“wide metrics” can be enabled, which is an additional attribute carried in the so called
“traffic engineering TLVs (Type-Length-Value packet field formats). Wide metric support
necessitates the support for traffic engineering extensions on the IGP, which is an optionally
enabled feature. Some other uses of traffic engineering is discussed further in the next
MPLS section.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 19
ISISISIS
[cont.]
[cont.]
4. Try following commands:
Switch to notes view!
A:R1# show router isis ?
- isis all
- isis [<isis-instance>]

<isis-instance> : [0..31]
<all> : keyword

adjacency - Display ISIS adjacency information

bier-info - Display ISIS BIER Info sub-TLV
capabilities - Display ISIS capability information
database - Display ISIS database information
hostname - Display ISIS system-id to hostname mapping
interface - Display ISIS interface information
lfa-coverage - Display ISIS LFA coverage
link-group-mem* - Display ISIS link-group-member status
link-group-sta*
20Nokia 2020
©
- Display ISISNokia
link-group
Confidential
status
mapping-server - Display ISIS mapping server information
prefix-sids - Display ISIS prefix-sids
routes - Display ISIS routes
sid-stats - Display ISIS sid statistics
spf-log - Display ISIS SPF Log information
sr-adj-sets - Display ISIS SR adjacency sets
sr-lfa-coverage - Display ISIS SR LFA coverage
statistics - Display ISIS statistics
status - Display ISIS status
summary-address - Display ISIS summary addresses
topology - Display ISIS topology

show router route-table protocol isis 

It is very likely you do not see any entries, why?

This is because we are running both OSPF and ISIS IGP at the same time and OSPF has a
higher priority (or preference) than ISIS and thus OSPF routes are selected for the routing
table instead of ISIS routes.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 20
ISISISIS
[cont.]
[cont.]
5. View ISIS adjacency show router isis adjacency 
Switch to notes view!
A:R1# show router isis adjacency

==============================================================================
Rtr Base ISIS Instance 0 Adjacency
==============================================================================
System ID Usage State Hold Interface MT-ID
------------------------------------------------------------------------------
R2 L1L2 Up 22 toR2 0
R3 L1L2 Up 25 toR3 0
R5 L1L2 Up 26 toR5 0
------------------------------------------------------------------------------
Adjacencies : 3
==============================================================================

6. View the IS-IS link state database show router isis database 
21Nokia 2020
© Nokia Confidential

A:R1# show router isis database

==============================================================================
Rtr Base ISIS Instance 0 Database
==============================================================================
LSP ID Sequence Checksum Lifetime Attributes
------------------------------------------------------------------------------
Displaying Level 1 database
------------------------------------------------------------------------------
R1.00-00 0xa 0xb70e 967 L1L2
R2.00-00 0xb 0x80cd 1026 L1L2
R3.00-00 0x9 0xf0e8 976 L1L2
R4.00-00 0xa 0x5210 1000 L1L2
R5.00-00 0x8 0x44aa 943 L1L2
R6.00-00 0x8 0x7436 975 L1L2
R7.00-00 0x8 0x2f37 1060 L1L2
R8.00-00 0x8 0xe938 1018 L1L2
Level (1) LSP Count : 8

Displaying Level 2 database

------------------------------------------------------------------------------
R1.00-00 0xa 0xb70e 974 L1L2
R2.00-00 0xb 0x80cd 1074 L1L2
R3.00-00 0xa 0xeee9 881 L1L2
R4.00-00 0xb 0x5011 935 L1L2
R5.00-00 0x9 0x42ab 1052 L1L2
R6.00-00 0x9 0x7237 904 L1L2
R7.00-00 0x8 0x2f37 1040 L1L2
R8.00-00 0x8 0xe938 995 L1L2
Level (2) LSP Count : 8
==============================================================================

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 21
ISISISIS
[cont.]
[cont.]
[Optional]
7. Switch
Turn on tosimple authentication (password) with a matching authentication key (choose one
notes view!
with your neighbor).

A:Rx>config>router>isis>if# hello-authentication-type password 

A:Rx>config>router>isis>if# hello-authentication-key
<your_password> 

Note: This configuration must match between neighbors’ interfaces or the adjacency will fail.

22Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 22
Configure ISISISIS
Configure
Possible debug commands on ISIS:
Switch to notes view!
A:R1# debug router isis ?
- isis [<isis-instance>]
- no isis [<isis-instance>]

<isis-instance> : [0..31]

[no] adjacency - Enable/disable debugging for ISIS adjacency

[no] cspf - Enable/disable debugging for ISIS cspf
[no] graceful-resta* - Enable/disable debugging for ISIS graceful-restart
[no] interface - Enable/disable debugging for ISIS interface
[no] leak - Enable/disable debugging for ISIS leaks
[no] lsdb - Enable/disable debugging for ISIS LSDB
[no] misc - Enable/disable debugging for ISIS misc
[no] packet - Enable/disable debugging for ISIS packet
[no] rtm - Enable/disable debugging for ISIS RTM
[no]
23Nokia spf
© 2020 - Enable/disable debugging
Nokia Confidential for ISIS SPF
[no] summary - Enable/disable debugging for ISIS summary addresses
[no] tunnel-endpoint - Enable/disable debugging for an ISIS tunnel endpoint

Create a log for debug-trace and debug ISIS packets to the ssh session.

A:R1# configure log log-id 9

A:R1>config>log>log-id$ from debug-trace
A:R1>config>log>log-id$ to session
A:R1>config>log>log-id$

A:R1# debug router isis packet

1 2020/06/18 14:47:37.280 UTC MINOR: DEBUG #2001 Base ISIS

"ISIS: PKT
(VR 1,Inst 0)TX L2 CSNP on ifId 3"

2 2020/06/18 14:47:37.282 UTC MINOR: DEBUG #2001 Base ISIS

"ISIS: PKT
(VR 1,Inst 0)xSNP:LSP 0100.1001.0001.00-00, rem life 1112 seqNum 0xe checksum
0x
af12"

3 2020/06/18 14:47:37.282 UTC MINOR: DEBUG #2001 Base ISIS

"ISIS: PKT
(VR 1,Inst 0)xSNP:LSP 0100.1001.0002.00-00, rem life 1111 seqNum 0xe checksum
0x
57f3“
...

To stop debugging messages from showing onto the screen, run the command:
/no debug 

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 23
 IGP Metric

24Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 24
OSPF andand
OSPF ISISISIS
Metrics
Metrics
1. Verify that the routing table contains all the destinations. What is the metric of the system
interface
Switch toof the opposite
notes view! router? Trace the route to this IP-address. What path is taken?

A:R8# show router route-table

==============================================================================
Route Table (Router: Base)
==============================================================================
Dest Prefix[Flags] Type Proto Age Pref
Next Hop[Interface Name] Metric
------------------------------------------------------------------------------
<< skip >>
10.10.10.4/32 Remote OSPF 00h47m52s 10
10.4.8.4 10
10.10.10.5/32 Remote OSPF 00h47m55s 10
10.4.8.4 40

Since OSPF has a lower preference than ISIS and the two protocols learn the same routes, only OSPF
routes are found in the route-table.
25Nokia 2020
© Nokia Confidential

The default link metric for OSPF is 10. From R8 to R5, the total link cost is therefore 40.

A:R8# traceroute 10.10.10.5

traceroute to 10.10.10.5, 30 hops max, 40 byte packets
1 10.4.8.4 (10.4.8.4) 2.13 ms 5.51 ms 1.35 ms
2 10.2.4.2 (10.2.4.2) 3.06 ms 3.43 ms 2.82 ms
3 10.1.2.1 (10.1.2.1) 3.99 ms 3.74 ms 7.84 ms
4 10.10.10.5 (10.10.10.5) 4.88 ms 4.43 ms 5.33 ms

2. Adjust the metric of the outgoing interface of the Edge router (R5 to R8) to 5000.
configure router ospf area 0 interface <toRx> metric 5000 
configure router isis interface <toRx> level 1 metric 5000 

3. Repeat Step 1. What has changed?

A:R8>config>router>ospf>area# show router route-table

==============================================================================
Route Table (Router: Base)
==============================================================================
Dest Prefix[Flags] Type Proto Age
Pref
Next Hop[Interface Name] Metric
------------------------------------------------------------------------------
<< skip >>
10.10.10.5/32 Remote OSPF 00h00m05s 10
10.4.8.4 5030

From R8 to R5, the metric now changes to 5030 instead of 40.

Changes of ISIS metric is not important in this step as OSPF routes with lower preference are selected
by the router to install them in its route-table. In other words, between IGP protocols, lower preference
(e.g., OSPF has a lower preference than ISIS) is selected. When an IGP protocol is selected, the path with
the lowest cost for a given destination is selected and installed into the route-table.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 25
OSPF andand
OSPF ISISISIS
Metrics [cont.]
Metrics [cont.]
Note: When a router learns more then one route to a certain destination, the best route will be
selected.
SwitchThe preference
to notes view! value of every protocol is different. The protocol with lowest
preference value will be selected. Then, if this routing protocol still offers more then one route
to the destination, the route with the lowest metric will be selected and inserted into the
routing table.
The administrator can influence this process by changing the preference and the metrics as
demonstrated in this lab exercise (metric). When a prefix has multiple routes with equal
preferences and metrics, only one is selected except when ECMP is activated
(Equal Cost Multi Path) – see further.

26Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 26
 Loopfree-Alternate

27Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 27
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y) based on their comments.

Initial rollback config file (X) – Final-ISIS.

• /admin rollback revert X

Final rollback config file (Y) – Final-OSPF, ISIS, LFA.

To compare current config with the final lab answer:

• /admin rollback compare active-cfg to Y

28Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 28
IP Fast ReRoute
IP Fast ReRoute
Loopfree-alternate (LFA) routes are pre-computed backup routes that are installed in the
forwarding
Switch totable toview!
notes achieve less than 50ms failure recovery before IGP convergence kick-in.

1. Add the following configuration to the core routers (R1 to R4):

router
ip-fast-reroute
ospf
traffic-engineering
loopfree-alternates
exit

Run the following commands to verify LFA routes.

show router route-table

29Nokia 2020
© Nokia Confidential
show route fib 1

A:R1>config>router# info
----------------------------------------------
<< skip >>
ip-fast-reroute
#--------------------------------------------------
echo "OSPFv2 Configuration"
#--------------------------------------------------
ospf 0
traffic-engineering
loopfree-alternates
exit
<< skip>>

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 29
IP Fast ReRoute
IP Fast [cont.]
ReRoute [cont.]
LFA routes are pre-computed and found on the route-table.
Switch to notes view!
A:R1# show router route-table

==============================================================================
Route Table (Router: Base)
==============================================================================
Dest Prefix[Flags] Type Proto Age
Pref
Next Hop[Interface Name] Metric
------------------------------------------------------------------------------
1.1.1.1/32 Local Local 04d02h03m 0
loopback 0
10.1.2.0/28 Local Local 04d02h03m 0
toR2 0
10.1.3.0/28 Local Local 04d02h03m 0
toR3 0
10.1.5.0/28 Local Local 04d02h03m 0
toR5
30Nokia 2020
© Nokia Confidential 0
10.2.4.0/28 Remote OSPF 01h42m39s 10
10.1.2.2 20
10.2.6.0/28 Remote OSPF 01h42m39s 10
10.1.2.2 20
10.3.4.0/28 Remote OSPF 01h39m22s 10
10.1.3.3 20
10.3.7.0/28 Remote OSPF 01h39m22s 10
10.1.3.3 20
10.4.8.0/28 [L] Remote OSPF 01h37m15s 10
10.1.2.2 30
10.10.10.1/32 Local Local 04d02h03m 0
system 0
10.10.10.2/32 Remote OSPF 01h42m39s 10
10.1.2.2 10
10.10.10.3/32 Remote OSPF 01h39m22s 10
10.1.3.3 10
10.10.10.4/32 [L] Remote OSPF 01h37m15s 10
10.1.2.2 20
10.10.10.5/32 Remote OSPF 01h25m49s 10
10.1.5.5 10
10.10.10.6/32 Remote OSPF 01h24m01s 10
10.1.2.2 20
10.10.10.7/32 Remote OSPF 01h22m24s 10
10.1.3.3 20
10.10.10.8/32 [L] Remote OSPF 01h21m01s 10
10.1.2.2 30
------------------------------------------------------------------------------
No. of Routes: 17
Flags: n = Number of times nexthop is repeated
B = BGP backup route available
L = LFA nexthop available
S = Sticky ECMP requested
==============================================================================

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 30
IP Fast ReRoute
IP Fast [cont.]
ReRoute [cont.]
LFA routes are installed in the forwarding table to achieve very fast failover time until IGP
convergence completes
Switch to notes view! to bypass the failed link.

A:R1# show router fib 1

==============================================================================
FIB Display
==============================================================================
Prefix [Flags] Protocol
NextHop
------------------------------------------------------------------------------
1.1.1.1/32 LOCAL
1.1.1.1 (loopback)
10.1.2.0/28 LOCAL
10.1.2.0 (toR2)
10.1.3.0/28 LOCAL
10.1.3.0 (toR3)
10.1.5.0/28 LOCAL
10.1.5.0
31Nokia 2020
© (toR5) Nokia Confidential

10.2.4.0/28 OSPF
10.1.2.2 (toR2)
10.2.6.0/28 OSPF
10.1.2.2 (toR2)
10.3.4.0/28 OSPF
10.1.3.3 (toR3)
10.3.7.0/28 OSPF
10.1.3.3 (toR3)
10.4.8.0/28 OSPF
10.1.2.2 (toR2)
10.1.3.3 (toR3) (LFA)
10.10.10.1/32 LOCAL
10.10.10.1 (system)
10.10.10.2/32 OSPF
10.1.2.2 (toR2)
10.10.10.3/32 OSPF
10.1.3.3 (toR3)
10.10.10.4/32 OSPF
10.1.2.2 (toR2)
10.1.3.3 (toR3) (LFA)
10.10.10.5/32 OSPF
10.1.5.5 (toR5)
10.10.10.6/32 OSPF
10.1.2.2 (toR2)
10.10.10.7/32 OSPF
10.1.3.3 (toR3)
10.10.10.8/32 OSPF
10.1.2.2 (toR2)
10.1.3.3 (toR3) (LFA)
------------------------------------------------------------------------------
Total Entries : 17
------------------------------------------------------------------------------
==============================================================================

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 31
 Policy and IGP Route Redistribution

32Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 32
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y) based on their comments.

Initial rollback config file (X) – Final-OSPF, ISIS, LFA.

• /admin rollback revert X

Final rollback config file (Y) – Final-OSPF, ISIS Policy and IGP Route Redistribution.

To compare current config with the final lab answer:

• /admin rollback compare active-cfg to Y

33Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 33
Route Policies
Route and
Policies Redistribution
and Redistribution
1. Each Edge and Core routers are pre-configured with a loopback interface x.x.x.x/32. For
example,
Switch R5 hasview!
to notes a loopback interface 5.5.5.5/32.

2. Check if this new IP address has been added to the route-table of your PE as a “Local”
entry.

3. Ask your neighbors to ping this IP address. Also try to ping their newly created loopback
interface IP addresses. Why doesn’t this work?

4. Create a policy on your PE that will accept the directly connected (sub)networks (including
loopback).

A:PExx>config>router# info
----------------------------------------------
policy-options
begin Begin
34Nokia 2020
©
policy-statement "policy-to-distribute"
Nokia Confidential
entry 10
from
protocol direct
exit
action accept
exit
exit
default-action reject
exit
commit Commit
exit
----------------------------------------------

Configuring policies:

Policies need to be configured in editing mode. Meaning that the configuration is not active
until decided by the operator.

Starting the editing mode is done using the begin command.

To activate the policy, type the commit command.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 34
Route Policies
Route and
Policies Redistribution
and Redistribution[cont.]
[cont.]
5. Verify the policy.
Switch to notes view!
show router policy 

Note: Until now, only a policy statement has been configured. It is not yet assigned to a
routing protocol and is therefore not being used yet.

6. Apply the policy as an export policy to OSPF and ISIS. This will redistribute the connected
(sub)network into your IGP domain.

A:Rx>config>router>ospf># export <policy_name> 

A:Rx>config>router>isis># export <policy_name> 

7. In the case of OSPF, the PE router needs to be marked as an ASBR (Autonomous System
Boundary Router) in order to get redistribution to work. This is not required for IS-IS.
35Nokia 2020
© Nokia Confidential

Rx>config>router>ospf># asbr 

8. When all the nodes have finished step 6, verify the routing table. You should have 4 new
entries: the added local directly connected (sub)network and the others learned remotely
over your IGP.

9. Repeat step 3. Is the ping successful now?

A:R5# ping 6.6.6.6

PING 6.6.6.6 56 data bytes
64 bytes from 6.6.6.6: icmp_seq=1 ttl=62 time=4.66ms.
64 bytes from 6.6.6.6: icmp_seq=2 ttl=62 time=6.77ms.
64 bytes from 6.6.6.6: icmp_seq=3 ttl=62 time=3.58ms.
64 bytes from 6.6.6.6: icmp_seq=4 ttl=62 time=3.39ms.
64 bytes from 6.6.6.6: icmp_seq=5 ttl=62 time=3.60ms.

---- 6.6.6.6 PING Statistics ----

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 3.39ms, avg = 4.40ms, max = 6.77ms, stddev = 1.26ms

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 35
Route Policies
Route and
Policies Redistribution
and Redistribution[cont.]
[cont.]
10. OSPF and ISIS Internal and External Route Re-distribution
Switch to notes view!
Use the following commands and explain why loopback routes such as 5.5.5.5/32 distributed by ISIS
instead of OSPF are being installed onto the route-table when OSPF has a lower preference than ISIS:
show router route-table
show router isis routes <x.x.x.x/32> detail
show router ospf routes <x.x.x.x/32> detail
ISIS routes for remote loopback addresses are installed into the routing table instead of OSPF.

A:R1# show router route-table

==============================================================================
Route Table (Router: Base)
==============================================================================
Dest Prefix[Flags] Type Proto Age Pref
Next Hop[Interface Name] Metric
------------------------------------------------------------------------------
1.1.1.1/32 Local Local 04d15h39m 0
loopback
36Nokia 2020
© Nokia Confidential 0
2.2.2.2/32 Remote ISIS 14h32m12s 15
10.1.2.2 100
5.5.5.5/32 Remote ISIS 00h30m09s 15
10.1.5.5 100
6.6.6.6/32 Remote ISIS 00h49m09s 15
10.1.2.2 200
<< skip >>

ISIS redistributes direct routes or loopback as Internet L1 route having preference of 15.

A:R1# show router isis routes 5.5.5.5/32 detail

==============================================================================
Rtr Base ISIS Instance 0 Route Table (detail)
==============================================================================
Prefix : 5.5.5.5/32
Prefix Status : Active Level : 1
NextHop : 10.1.5.5
Metric : 100 Type : Internal
SPF Version : 7 SysID/Hostname : R5
MT : 0 AdminTag : 0

OSPF redistributes direct routes or loopback via ASBR are considered External OSPF routes with
preference of 150. Therefore, routers install the ISIS advertised loopback routes.

A:R1>show router ospf routes 5.5.5.5/32 detail

==============================================================================
Rtr Base OSPFv2 Instance 0 Route Table (detail)
==============================================================================
Destination Type(Dest) Stat
NHIP NHIF Cost[E2] Area Type
Weight:Cfg/Norm
------------------------------------------------------------------------------
5.5.5.5/32 E2 (HOST) N (R)
10.1.5.5 5 100:1 0.0.0.0

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 36
Route Policies
Route and
Policies Redistribution
and Redistribution[cont.]
[cont.]
The following shows the OSPF and ISIS Internal and External route preference:
Switch to notes view!

Default Preference Table

37Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 37
 OSPFv3

38Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 38
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y) based on their comments.

Initial rollback config file (X) – Final-OSPF, ISIS Policy and IGP Route Redistribution.
• /admin rollback revert X

Final rollback config file (Y) – Final-OSPFv3.

To compare current config with the final lab answer:

• /admin rollback compare active-cfg to Y

39Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 39
OSPF3 – IPv6
OSPF3 – IPv6
In ISIS we can activate IPv6 support with one command ipv6-routing native. But what
about OSPF?
Switch We will
to notes activate a new protocol, OSPF3.
view!

A:R2>config>router>ospf3# info
----------------------------------------------
loopfree-alternates
area 0.0.0.0
interface "system"
no shutdown
exit
interface "toR1"
interface-type point-to-point
no shutdown
exit
interface "toR4"
interface-type point-to-point
no shutdown
exit
40Nokia 2020
© Nokia Confidential
interface "toR6"
interface-type point-to-point
no shutdown
exit
exit
no shutdown

Note that we have NOT specified any Policy to re-distribute loopback addresses except the
IPv6 system interface in OSPF3 and thus these routes are not being advertised by OSPF3.
However, we still have ISIS re-distributing IPv4 and IPv6 of these loopback routes and thus we
should expect seeing these ISIS learnt IPv6 loopback routes in the route-table.
Try following show commands:
show router ospf3 neighbor 

A:R5# show router ospf3 neighbor

==============================================================================
Rtr Base OSPFv3 Instance 0 Neighbors
==============================================================================
Interface-Name Rtr Id State Pri RetxQ TTL
Area-Id
------------------------------------------------------------------------------
toR1 10.10.10.1 Full 1 0 34
0.0.0.0
------------------------------------------------------------------------------
No. of Neighbors: 1
==============================================================================

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 40
OSPF3 – IPv6 [cont.]
OSPF3 – IPv6 [cont.]
show router ospf3 interface 

Switch to notes view!

A:R5# show router ospf3 interface

==============================================================================
Rtr Base OSPFv3 Instance 0 Interfaces
==============================================================================
If Name Area Id Designated Rtr Bkup Desig Rtr Adm Oper
------------------------------------------------------------------------------
system 0.0.0.0 10.10.10.5 0.0.0.0 Up DR
toR1 0.0.0.0 0.0.0.0 0.0.0.0 Up PToP
------------------------------------------------------------------------------
No. of OSPF Interfaces: 2
==============================================================================

show router ospf3 database 

41Nokia 2020
© Nokia Confidential

A:R5# show router ospf3 database

==============================================================================
Rtr Base OSPFv3 Instance 0 Link State Database (type: All)
==============================================================================
Type Area Id Link State Id Adv Rtr Id Age Sequence Cksum
------------------------------------------------------------------------------
Router 0.0.0.0 0.0.0.0 10.10.10.1 50 0x8000001d 0x5a60
Router 0.0.0.0 0.0.0.0 10.10.10.2 105 0x8000001e 0x6256
Router 0.0.0.0 0.0.0.0 10.10.10.5 753 0x8000001b 0xf265
Router 0.0.0.0 0.0.0.0 10.10.10.6 235 0x8000001c 0x154
IA Pfx 0.0.0.0 0.0.0.0 10.10.10.1 1988 0x8000001c 0x9942
IA Pfx 0.0.0.0 0.0.0.0 10.10.10.2 1617 0x8000001d 0x664c
<< skip >>

show router ospf3 database type router adv-router <system address> detail 

A:R5# show router ospf3 database type router adv-router 10.10.10.1 detail
==============================================================================
Rtr Base OSPFv3 Instance 0 Link State Database (type: Router) (detail)
==============================================================================
Router LSA for Area 0.0.0.0
------------------------------------------------------------------------------
Area Id : 0.0.0.0 Adv Router Id : 10.10.10.1
Link State Id : 0.0.0.0 (0)
LSA Type : Router
Sequence No : 0x80000003 Checksum : 0x73f
Age : 139 Length : 72
Options : ----R--EV6
Flags : Link Count : 3
Link Type (1) : P2P Link Nbr Rtr ID (1) : 10.10.10.2
I/F Index (1) : 3 Nbr I/F Index (1): 3
Metric (1) : 10
Link Type (2) : P2P Link Nbr Rtr ID (2) : 10.10.10.3
I/F Index (2) : 4 Nbr I/F Index (2): 3
Metric (2) : 10
Link Type (3) : P2P Link Nbr Rtr ID (3) : 10.10.10.5
I/F Index (3) : 5 Nbr I/F Index (3): 3
Metric (3) : 10

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 41
OSPF3 – IPv6
OSPF3 [cont.]
– IPv6 [cont.]
show router ospf3 database type intra-area-pfx detail 
Switch to notes view!

A:R5# show router ospf3 database type intra-area-pfx detail

==============================================================================
Rtr Base OSPFv3 Instance 0 Link State Database (type: IA Pfx) (detail)
==============================================================================
IA Pfx LSA for Area 0.0.0.0
------------------------------------------------------------------------------
Area Id : 0.0.0.0 Adv Router Id : 10.10.10.1
Link State Id : 0.0.0.0 (0)
LSA Type : IA Pfx
Sequence No : 0x8000001c Checksum : 0x9942
Age : 2091 Length : 88
Ref Ls Type : 2001 Ref Ls Id : 0
Ref Adv Rtr : 10.10.10.1 No of Pfxs : 4
Prefix (1) : 3ffe::1:101:101/128
Pfx©42Nokia
Options
2020 (1) : LA Metric (1)
Nokia Confidential : 0
<< skip >>

show router route-table ipv6 

A:R5# show router route-table ipv6

==============================================================================
IPv6 Route Table (Router: Base)
==============================================================================
Dest Prefix[Flags] Type Proto Age
Pref
Next Hop[Interface Name] Metric
------------------------------------------------------------------------------
2001:db8:0:1::1/128 Remote ISIS 14h53m12s 15
fe80::69ff:fe00:105-"toR1" 100
2001:db8:0:2::2/128 Remote ISIS 14h53m12s 15
fe80::69ff:fe00:105-"toR1" 200
2001:db8:0:5::5/128 Local Local 04d15h45m 0
loopback 0
2001:db8:0:6::6/128 Remote ISIS 01h10m10s 15
fe80::69ff:fe00:105-"toR1" 300
2001:db8:12::/64 Remote OSPF3 14h53m11s 10
fe80::69ff:fe00:105-"toR1" 200
2001:db8:13::/64 Remote OSPF3 14h53m11s 10
fe80::69ff:fe00:105-"toR1" 200

IPv6 ISIS learnt loopback routes as shown in the route-table. Interface addresses are
distributed by both OSPF3 and ISIS but since OSPF3 has a lower Preference than ISIS. Thus
OSPF IPv6 interface routes are installed in the route-table.

show router fib 1 ipv6 

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 42
 BFD

43Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 43
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y) based on their comments.

Initial rollback config file (X) – Final-OSPFv3.

• /admin rollback revert X

Final rollback config file (Y) – Final-BFD.

To compare current config with the final lab answer:

• /admin rollback compare active-cfg to Y

44Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 44
Bi-directional Forward
Bi-directional Detection
Forward Detection
Bi-Directional Forwarding Detection (BFD) is a light-weight protocol which provides rapid path
failure detection
Switch between
to notes view! two systems.
If a system running BFD stops receiving BFD messages on an interface, it will determine that
there has been a failure in the path and notifies other protocols associated with the interface.
BFD is useful in situations where two nodes are interconnected through either an optical
(DWDM) or Ethernet network.

As general rule, the following steps are required to configure and enable a BFD session when
peers are directly connected:
1. Configure BFD parameters on the peering interfaces.
2. Check that the Layer 3 protocol, that is to be bound to BFD, is up and running.
3. Enable BFD under the Layer 3 protocol interface.

A:R1>config>router# info
----------------------------------------------
45Nokia 2020
© Nokia Confidential
interface "toR5"
address 10.1.5.1/28
port 1/1/5
ipv6
address 2001:db8:15::1:5:1/64
exit
bfd 100 receive 100 multiplier 3
no shutdown
exit

A:R1>config>router>ospf# area 0.0.0.0

A:R1>config>router>ospf>area# info
----------------------------------------------
<< skip >> OSPF
interface "toR5"
interface-type point-to-point
bfd-enable
no shutdown
exit

A:R1>config>router# isis
A:R1>config>router>isis# info
----------------------------------------------
<< skip >> ISIS
interface "toR5"
interface-type point-to-point
bfd-enable ipv4
no shutdown
exit

Similar steps need to be performed on interface & protocol where BFD has to be applied.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 45
Bi-directional Forward
Bi-directional Detection
Forward Detection[cont.]
[cont.]
Note that BFD can be implemented in following cases:
• BFD for to
Switch ISISnotes view!
• BFD for OSPF
• BFD for PIM
• BFD for Static route
• BFD IES
• BFD for RSVP
• BFD on RSVP LSP’s
• BFD for T-LDP
• BFD on LDP interfaces
• BFD support of OSPF CE-PE adjacencies
• BFD over IPSec tunnel
• BFD over VRRP
Run the following BFD commands verify the BFD configurations
show router bfd interface

46Nokia 2020
© Nokia Confidential
A:R5# show router bfd interface
==============================================================================
BFD Interface
==============================================================================
Interface name Tx Interval Rx Interval Multiplier
------------------------------------------------------------------------------
toR1 100 100 3
------------------------------------------------------------------------------
No. of BFD Interfaces: 1

If the BFD-enabled interface toR1 does not receive BFD hello messages for 3 times each separated by
100ms (i.e., totally 300ms), R5 will declare interface toR1 is down and starts IGP convergent.
show router bfd session

A:R5# show router bfd session

==============================================================================
Legend:
Session Id = Interface Name | LSP Name | Prefix | RSVP Sess Name | Service Id
wp = Working path pp = Protecting path
==============================================================================
BFD Session
==============================================================================
Session Id State Tx Pkts Rx Pkts
Rem Addr/Info/SdpId:VcId Multipl Tx Intvl Rx Intvl
Protocols Type LAG Port LAG ID
------------------------------------------------------------------------------
toR1 Up 578948 578946
10.1.5.1 3 100 100
ospf2 isis iom N/A N/A
------------------------------------------------------------------------------
No. of BFD sessions: 1

BFD is applied to OSPF2 and ISIS but not OSPF3.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 46
Wrap-up
In this module we have covered the following items:
• IGP in the network:
- OSPF
- ISIS
- Metrics
- Preference
- Routing policy redistribution
- Internal and External routes distribution
• Bidirectional Forward Detection (BFD)

47Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 47
48Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S03M01 Ed0 48
 MPLS LDP RSVP-TE

ER00198-V-2000 V0 - S04M01 Ed0

1 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 1
Learning Objectives
Upon completion of this module, you should be able to:
• Configure:
̵ LDP
̵ Loop Free Alternate LDP
̵ LDP FRR
̵ Equal Cost Multi Path (ECMP)
̵ LDP-shortcut
̵ RSVP-TE with bandwidth constraints
̵ Limiting oversubscription
̵ MPLS Fast Reroute
̵ RSVP-shortcut

2 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 2
 ToC Slide

Table of Contents

Lab Setup
MPLS LDP
MPLS RSVP-TE
Wrap-up

3 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 3
 Lab Setup

4 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 4
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y) based on their comments.

Initial rollback config file (X) - Final - BFD.

• /admin rollback revert X

With this initial config, all routers have IGP and BFD connectivity.

Final rollback config file (Y) - Final - MPLS LDP.

To compare current config with the final lab answer:

• /admin rollback compare active-cfg to Y

5 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 5
 MPLS LDP

6 Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 6
Configure LDP
Configure LDP
We now have OSPF and ISIS IPv4 and IPv6 provisioned on all Edge and Core routers.
Let Switch
us setup MPLS view!
to notes LDP and RSVP-TE Transport Tunnel signaling protocols so that
Transport Tunnels can be established among routers to support future network services.
1. Each pair of students login to their Edge and Core routers and enable LDP on all router
interfaces. The below example shows R1 and R5 have a LDP session.

A:R1>config>router>ldp# info A:R5>config>router>ldp$ info

------------------------------------------- -----------------------------------------
interface-parameters interface-parameters
interface "toR2" dual-stack interface "toR1" dual-stack
ipv4 ipv4
no shutdown no shutdown
exit exit
ipv6 ipv6
no shutdown no shutdown
exit exit
no shutdown no shutdown
7 Nokia 2020
© exit Nokia Confidential exit
interface "toR3" dual-stack exit
ipv4 targeted-session
no shutdown exit
exit no shutdown
ipv6
no shutdown
exit
no shutdown
exit
interface "toR5" dual-stack
ipv4
no shutdown
exit
ipv6
no shutdown
exit
no shutdown
exit
exit
targeted-session
exit
no shutdown

Run the following LDP show commands to verify LDP status:

show router ldp status 
show router ldp discovery 
show router ldp session 
show router ldp parameters 
show router ldp interface 
show router tunnel-table 

Invoke the following commands to find out the LDP and IGP paths to the opposite Edge
router’s system address. For example, for R5, its opposite router is R8. Compare the
paths between the two commands:
oam lsp-trace prefix 10.10.10.X/32 
traceroute 10.10.10.X 

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 7
LDPLDP
Verification
Verification
show router ldp session
If the two to
Switch ends of aview!
notes LDP session area provisioned correctly, the LPD’s status should be
established.

A:R1# show router ldp session

==============================================================================
LDP IPv4 Sessions
==============================================================================
Peer LDP Id Adj Type State Msg Sent Msg Recv Up Time
------------------------------------------------------------------------------
10.10.10.2:0 Link Established 372 374 0d 00:15:33
10.10.10.3:0 Link Established 362 365 0d 00:15:06
10.10.10.5:0 Link Established 352 354 0d 00:14:34
------------------------------------------------------------------------------
No. of IPv4 Sessions: 3
==============================================================================
8 Nokia 2020
© Nokia Confidential
==============================================================================
LDP IPv6 Sessions
==============================================================================
Peer LDP Id
Adj Type State Msg Sent Msg Recv Up Time
------------------------------------------------------------------------------
3ffe::1:202:202[0]
Link Established 370 373 0d 00:15:33
3ffe::1:303:303[0]
Link Established 361 362 0d 00:15:06
3ffe::1:505:505[0]
Link Established 355 355 0d 00:14:34
------------------------------------------------------------------------------
No. of IPv6 Sessions: 3
==============================================================================

show router tunnel-table

Each router should has a LDP tunnel to the other router as Transport Tunnel for network
services.

A:R1# show router tunnel-table

===========================================================================
IPv4 Tunnel Table (Router: Base)
===========================================================================
Destination Owner Encap TunnelId Pref Nexthop Metric
----------------------------------------------------------------------------
10.10.10.2/32 ldp MPLS 65541 9 10.1.2.2 100
10.10.10.3/32 ldp MPLS 65543 9 10.1.3.3 100
10.10.10.4/32 ldp MPLS 65545 9 10.1.2.2 200
10.10.10.5/32 ldp MPLS 65539 9 10.1.5.5 100
10.10.10.6/32 ldp MPLS 65547 9 10.1.2.2 200
10.10.10.7/32 ldp MPLS 65549 9 10.1.3.3 200
10.10.10.8/32 ldp MPLS 65551 9 10.1.2.2 300
----------------------------------------------------------------------------
Flags: B = BGP backup route available
E = inactive best-external BGP route

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 8
Verify LDP
Verify and
LDP IP IP
and Paths
Paths
oam lsp-trace prefix <x.x.x.x>/32
Identify
Switchthe
toLSP path
notes signaled by LDP.
view!

A:R8# oam lsp-trace prefix 10.10.10.5/32

lsp-trace to 10.10.10.5/32: 0 hops min, 0 hops max, 104 byte packets
1 10.10.10.4 rtt=3.44ms rc=8(DSRtrMatchLabel) rsc=1
2 10.10.10.2 rtt=3.78ms rc=8(DSRtrMatchLabel) rsc=1
3 10.10.10.1 rtt=4.03ms rc=8(DSRtrMatchLabel) rsc=1
4 10.10.10.5 rtt=4.56ms rc=3(EgressRtr) rsc=1

traceroute <x.x.x.x>
Identify the IP path determined by IGP such as OSPF or ISIS.

9 Nokia 2020
© Nokia Confidential
A:R8# traceroute 10.10.10.5
traceroute to 10.10.10.5, 30 hops max, 40 byte packets
1 10.4.8.4 (10.4.8.4) 1.30 ms 3.02 ms 1.24 ms
2 10.2.4.2 (10.2.4.2) 2.81 ms 2.53 ms 2.56 ms
3 10.1.2.1 (10.1.2.1) 3.18 ms 2.53 ms 2.61 ms
4 10.10.10.5 (10.10.10.5) 3.09 ms 4.26 ms 6.36 ms

Since LDP establishes LSPs based on the IGP paths to the destination endpoints,
lsp-trace and traceroute list identical paths between two end-points based on
IGP.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 9
Verify LDP
Verify Label
LDP Binding
Label Binding
2. Verify the Label Information Base (LIB) using the command show router ldp
bindings
Switch view! Why are some of the ingress and egress labels empty?
active.
to notes

A:R1# show router ldp bindings active

========================================================================
LDP Bindings (IPv4 LSR ID 10.10.10.1)
(IPv6 LSR ID 3ffe::1:101:101)
========================================================================
Label Status:
U - Label In Use, N - Label Not In Use, W - Label Withdrawn
WP - Label Withdraw Pending, BU - Alternate For Fast Re-Route
e - Label ELC
FEC Flags:
LF - Lower FEC, UF - Upper FEC, M - Community Mismatch, BA - ASBR
Backup FEC
(S) - Static (M) - Multi-homed Secondary Support
(B) - BGP Next Hop (BU) - Alternate Next-hop for Fast Re-Route
10Nokia 2020(I) - SR-ISIS Next Hop (O) -Nokia
© SR-OSPF
Confidential Next Hop
(C) - FEC resolved with class-based-forwarding
==============================================================================
LDP IPv4 Prefix Bindings (Active)
==============================================================================
Prefix Op
IngLbl EgrLbl
EgrNextHop EgrIf/LspId
------------------------------------------------------------------------------
10.10.10.1/32 Pop
524287 --
-- --

10.10.10.2/32 Push
-- 524287
10.1.2.2 1/1/2

10.10.10.2/32 Swap
524285 524287
10.1.2.2 1/1/2

10.10.10.3/32 Push
-- 524287
10.1.3.3 1/1/1

10.10.10.3/32 Swap
524283 524287
10.1.3.3 1/1/1

10.10.10.4/32 Push
-- 524281
10.1.2.2 1/1/2
<< skip >>

Some LDP labels that do not make sense for LDP operations are blanked out (i.e., marked
as --). For example, for R1’s ingress label 524287, R1 will pop it because it is addressed to R1’s
system interface. It will not swap the label to any Egress label for its system interface.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 10
Configure LDP Fast Reroute (FRR)
Configure LDP Fast Reroute (FRR)
LDP FRR improves convergence in case of a single link or single node failure in the network.
Convergence time will be in the order of 10s of milliseconds. This is important to some application
Switch to notes view!
services (like VoIP) which are sensitive to traffic loss when running over the MPLS network. Without
using FRR, link and/or node failures inside an MPLS LDP network result in traffic loss in the order of
100s of milliseconds.

LDP used the IGP configuration: Loopfree alternates. Since Edge routers have only one link to the its
Core router without alternate path, setup FRR on the Core Routers (R1 to R4) as follows:
1. Enable and provision LDP on all your network interfaces.
OSPF:

A:R1>config>router>ospf# info
------------------------------------
traffic-engineering
loopfree-alternates
exit
11Nokia 2020
©
area 0.0.0.0 Nokia Confidential
interface "system"
…

ISIS:

A:R1>config>router>isis# info
-----------------------------------
area-id 49.0000
traffic-engineering
loopfree-alternates
exit
ipv6-routing native

2. Now activate FRR in the LDP configuration.

A:R1>config>router>ldp# info
----------------------------------------------
fast-reroute
interface-parameters
interface "toR2" dual-stack
ipv4
no shutdown
exit
ipv6
no shutdown
exit
no shutdown
exit
interface "toR3" dual-stack
ipv4
no shutdown
exit
<< skip >>

3. On Core routers R1 to R4, run the command show router ldp binding active to highlight
the backup next-hop for FRR.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 11
Verify LDP Fast Reroute (FRR)
Verify LDP Fast Reroute (FRR)
R1 has two paths to R4 via either R2 or R3.
Switch to notes view!
A:R1# show router ldp bindings active
==============================================================================
LDP Bindings (IPv4 LSR ID 10.10.10.1)
(IPv6 LSR ID 3ffe::1:101:101)
==============================================================================
Label Status:
U - Label In Use, N - Label Not In Use, W - Label Withdrawn
WP - Label Withdraw Pending, BU - Alternate For Fast Re-Route
e - Label ELC
FEC Flags:
LF - Lower FEC, UF - Upper FEC, M - Community Mismatch,
BA - ASBR Backup FEC
(S) - Static (M) - Multi-homed Secondary Support
(B) - BGP Next Hop (BU) - Alternate Next-hop for Fast Re-Route
(I) - SR-ISIS Next Hop (O) - SR-OSPF Next Hop
(C) - FEC resolved with class-based-forwarding
==============================================================================
LDP IPv4 Prefix Bindings (Active)
==============================================================================
12Nokia 2020
© Nokia Confidential
Prefix Op
IngLbl EgrLbl
EgrNextHop EgrIf/LspId
------------------------------------------------------------------------------
10.10.10.1/32 Pop
524287 --
-- --

10.10.10.2/32 Push
-- 524287
10.1.2.2 1/1/2

10.10.10.2/32 Swap
524285 524287
10.1.2.2 1/1/2

10.10.10.3/32 Push
-- 524287
10.1.3.3 1/1/1

10.10.10.3/32 Swap
524283 524287
10.1.3.3 1/1/1

10.10.10.4/32 Push
-- 524281
10.1.2.2 1/1/2

10.10.10.4/32 Push
-- 524281BU
10.1.3.3 1/1/1

10.10.10.4/32 Swap
524281 524281 Backup FRR
10.1.2.2 1/1/2

10.10.10.4/32 Swap
524281 524281BU
10.1.3.3 1/1/1
<<skip>>

If R1 receive the label 524281 for R4, it will swap the label to 524281 and forward the packet to
R2 for R4. The alternate FRR path is via R3 to R4 using egress label 524281.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 12
Equal Cost Multi Path (ECMP) via LDP
Equal Cost Multi Path (ECMP) via LDP
FRR offers pre-calculated backup paths for a given end-point when multiple paths are
available
Switchfor
to fast
notesfailover.
view! However, only one path is being used to forward traffic as by
default, ECMP = 1. We can use ECMP to load share traffic for a given end-points when
multiple paths to the end-points are available. Students enable ecmp 2 on Core routers
(R1 to R4) and explain the LDP bindings before and after ecmp 2.

show router ldp binding active

Before ecmp 2 is provisioned at the Core routers, the available multiple paths for a given
end-point is being used as FRR as FRR is still active from the previous lab.

A:R1>config>router>ldp# show router ldp bindings active

==============================================================================
LDP Bindings (IPv4 LSR ID 10.10.10.1)
13Nokia 2020
©
(IPv6 LSR ID 3ffe::1:101:101)
Nokia Confidential
==============================================================================
Label Status:
U - Label In Use, N - Label Not In Use, W - Label Withdrawn
WP - Label Withdraw Pending, BU - Alternate For Fast Re-Route
e - Label ELC
FEC Flags:
LF - Lower FEC, UF - Upper FEC, M - Community Mismatch, BA - ASBR
Backup FEC
(S) - Static (M) - Multi-homed Secondary Support
(B) - BGP Next Hop (BU) - Alternate Next-hop for Fast Re-Route
(I) - SR-ISIS Next Hop (O) - SR-OSPF Next Hop
(C) - FEC resolved with class-based-forwarding
==============================================================================
LDP IPv4 Prefix Bindings (Active)
==============================================================================
Prefix Op
IngLbl EgrLbl
EgrNextHop EgrIf/LspId
------------------------------------------------------------------------------
<< skip >>

10.10.10.3/32 Swap
524283 524287
10.1.3.3 1/1/1

10.10.10.4/32 Push
-- 524281
10.1.2.2 1/1/2

10.10.10.4/32 Push
-- 524281BU
10.1.3.3 1/1/1

10.10.10.4/32 Swap
524281 524281
10.1.2.2 1/1/2 Multiple paths from R1 to R4
are being used for FRR
10.10.10.4/32 Swap
524281 524281BU instead of load sharing as
10.1.3.3 1/1/1 ECMP = 1 by default
1/1/1

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 13
Equal Cost Multi Path (ECMP) via LDP [cont.]
Equal Cost Multi Path (ECMP) via LDP [cont.]

Apply ecmp
Switch to2notes
for the Core routers (R1 to R4) .
view!
configure router ecmp 2 

A:R1>config>router# info
----------------------------------------------
<< skip >>
autonomous-system 65100
ecmp 2
ip-fast-reroute

14Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 14
Equal Cost Multi Path (ECMP) via LDP [cont.]
Equal Cost Multi Path (ECMP) via LDP [cont.]
With ecmp 2, the multiple paths between R1 and R4 are now being used for forwarding
traffic for load
Switch sharing
to notes view!purpose instead of FRR and thus there is no Alternate FRR unless
more than 2 paths are available between R1 and R4, for example:

show router ldp binding active 

A:R1# show router ldp bindings active

<< skip >>

==============================================================================
LDP IPv4 Prefix Bindings (Active)
==============================================================================
Prefix Op
IngLbl EgrLbl
EgrNextHop EgrIf/LspId
------------------------------------------------------------------------------
<< skip >>
15Nokia 2020
© Nokia Confidential

10.10.10.4/32 Push
-- 524281
10.1.2.2 1/1/2

10.10.10.4/32 Push
-- 524281
10.1.3.3 1/1/1

10.10.10.4/32 Swap
524281 524281
10.1.2.2 1/1/2

10.10.10.4/32 Swap Multiple paths from R1 to R4

524281 524281
are now being used for load
10.1.3.3 1/1/1
sharing as ECMP = 2. No FRR as
there are only two paths
between R1 and R4

Verify the LSP setup by LDP using the following oam commands:
oam lsp-ping prefix <10.10.10.X>/32 

A:R1# oam lsp-ping prefix 10.10.10.4/32

LSP-PING 10.10.10.4/32: 80 bytes MPLS payload
Seq=1, send from intf toR2, reply from 10.10.10.4
udp-data-len=32 ttl=255 rtt=4.66ms rc=3 (EgressRtr)

---- LSP 10.10.10.4/32 PING Statistics ----

1 packets sent, 1 packets received, 0.00% packet loss
round-trip min = 4.66ms, avg = 4.66ms, max = 4.66ms, stddev = 0.000ms

oam lsp-trace prefix <10.10.10.X>/32 

A:R1# oam lsp-trace prefix 10.10.10.4/32

lsp-trace to 10.10.10.4/32: 0 hops min, 0 hops max, 104 byte packets
1 10.10.10.2 rtt=2.62ms rc=8(DSRtrMatchLabel) rsc=1
2 10.10.10.4 rtt=2.67ms rc=3(EgressRtr) rsc=1

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 15
LDPLDP
Shortcut forfor
Shortcut IGPIGP

When LDP shortcut is enabled, LDP populates the RTM (Route Table Manager) with next-hop
entries corresponding
Switch to all prefixes for which it activated an LDP Forwarding Equivalence Class
to notes view!
(FEC). For a given prefix, two route entries are populated in RTM. One corresponds to the LDP
shortcut next-hop and has an owner of LDP. The other one is the regular IP next-hop. The LDP
shortcut next-hop always has preference over the regular IP next-hop for forwarding user
packets and specified control packets over a given outgoing interface to the route next-hop.

ldp-shortcut has a preference of 9, which has a higher priority (i.e., lower preference) than
OSPF and ISIS but lower than static routes.
Before using ldp-shortcut, remote system addresses are resolved using regular IP next-hop.

A:Rx# show router route-table

==============================================================================
Route Table (Router: Base)
==============================================================================
16Nokia 2020
© Nokia Confidential
Dest Prefix[Flags] Type Proto Age Pref
Next Hop[Interface Name] Metric
------------------------------------------------------------------------------
10.10.10.1/32 Local Local 04d20h59m 0
system 0
10.10.10.2/32 Remote OSPF 17h47m42s 10
10.1.3.3 300
10.10.10.3/32 Remote OSPF 19h57m40s 10
10.1.3.3 100

<< skip >>

With ldp-shortcut using the command configure router ldp-shortcut 

A:Rx# show router route-table

==============================================================================
Route Table (Router: Base)
==============================================================================
Dest Prefix[Flags] Type Proto Age Pref
Next Hop[Interface Name] Metric
------------------------------------------------------------------------------
10.10.10.1/32 Local Local 04d21h00m 0
system 0
10.10.10.2/32 Remote LDP 00h00m04s 9
10.1.3.3 (tunneled) 300
10.10.10.3/32 Remote LDP 00h00m04s 9
10.1.3.3 (tunneled) 100

<< skip >>

Now, all tunnel LSPs that resolve

an IGP next hop will replace the IP
next hops.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 16
 MPLS RSVP-TE

17Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 17
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y) based on their comments.

Initial rollback config file (X) - Final - MPLS LDP.

• /admin rollback revert X

With this initial config, all routers have IGP and BFD connectivity.

Final rollback config file (Y) - Final - MPLS RSVP-TE.

To compare current config with the final lab answer:

• /admin rollback compare active-cfg to Y

18Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 18
Configure RSVP-TE
Configure with
RSVP-TE Bandwidth
with BandwidthConstraints
Constraints
Steps to prepare our network:
MPLS reliestoon
Switch traffic
notes engineering, activated in the IGP’s.
view!
1. Enable traffic-engineering on your IGP.
configure router ospf traffic-engineering 
configure router isis traffic-engineering 

2. Verify the status of traffic-engineering on your IGP. Where can you see that traffic-
engineering is enabled?
show router ospf status 
show router isis status 

3. If not previously configured, enable MPLS on your system and the network interfaces.

A:R1>config>router>mpls# info
----------------------------------------------
19Nokia 2020
© Nokia Confidential
interface "system"
no shutdown
exit
interface "toR5"
no shutdown
exit
interface "toR2"
no shutdown
exit
interface "toR3"
no shutdown
exit
no shutdown

4. The previous step automatically enables RSVP on the interfaces. Make sure RSVP is no
shutdown. Verify.
show router mpls interface 
show router rsvp interface 

A:R1>config>router>rsvp# info
----------------------------------------------
interface "system"
no shutdown
exit
interface "toR5"
no shutdown
exit
interface "toR2"
no shutdown
exit
interface "toR3"
no shutdown
exit
no shutdown

Optional: You can add BFD to your rsvp interfaces.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 19
Limiting Oversubscription
Limiting Oversubscription
Optional: You might want to limit the possible oversubscription.
5. Verify
Switchthe capacity
to notes of your port facing your clockwise neighbour. What is the operational
view!
speed?

show port <X/X/X> 

Note: <X/X/X> = the port number facing your clockwise neighbour.

6. Set the total maximum amount of reservable bandwidth by RSVP to 100% on the RSVP
interface. Verify the available bandwidth.

Rx# configure router rsvp interface <toRx> 

Rx>config>router>rsvp>if# subscription 100 
Note: You can oversubscribe the interface up to 1000 percent.
20Nokia 2020
© Nokia Confidential
show router rsvp interface <toRx> detail 

A:R4>config>router>rsvp>if# show router rsvp interface "toR2" detail

==============================================================================
RSVP Interface (Detailed) : toR2
==============================================================================
------------------------------------------------------------------------------
Interface : toR2
------------------------------------------------------------------------------
Interface : toR2
Port ID : 1/1/1
Admin State : Up Oper State : Up
Active Sessions : 0 Active Resvs : 0
Total Sessions : 0
Subscription : 100 % Port Speed : 1000 Mbps
Total BW : 1000 Mbps Aggregate : Dsabl
Hello Interval : 3000 ms Hello Timeouts : 0
Key Type Auth : Disabled
Keychain Auth : Disabled
Auth Rx Seq Num : n/a Auth Key Id : n/a
Auth Tx Seq Num : n/a Auth Win Size : n/a
Refresh Reduc. : Disabled Reliable Deli. : Disabled
Bfd Enabled : No Graceful Shut. : Disabled
ImplicitNullLabel : Disabled* GR helper : Disabled

Percent Link Bandwidth for Class Types*

Link Bw CT0 : 100 Link Bw CT4 : 0
Link Bw CT1 : 0 Link Bw CT5 : 0
Link Bw CT2 : 0 Link Bw CT6 : 0
Link Bw CT3 : 0 Link Bw CT7 : 0

Bandwidth Constraints for Class Types (Kbps)

BC0 : 1000000 BC4 : 0
BC1 : 0 BC5 : 0
BC2 : 0 BC6 : 0
BC3 : 0 BC7 : 0

<< skip >>

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 20
Path Configuration
Path Configuration
Label Switched Paths (LSP) is the actual MPLS tunnel and we can add constraints when we
build LSP. to
Switch One of the
notes constraints is Path. A path is a template with hops specified. Can be
view!
reused for several LSP’s.
Each pair of students prepare LSP paths on their Core router (e.g., R1 to R4) toward the Edge
routers (e.g., R5 to R8). The following uses R1 as an example to show the LSP paths it needs to
setup to the Edge routers. Similar setups are needed for R2 to R4.

R1 Clockwise Path – R2 R6
RSVP-TE Loose

21Nokia 2020
© Nokia Confidential

Diagonal Path –
RSVP-TE Strict
R3 R4

R7 R8

1. Clockwise Path – Loose RSVP-TE:

Use a loose RSVP-TE signaled path instead of a strict path. A loose path follows the path of
LDP or IGP but we can add constraints such as bandwidth later. E.g., R1’s clockwise Edge router
is R6.
• R1 – R6
• R2 – R8
• R3 – R5
• R4 – R7

2. Counter-clockwise Path – LDP:

LDP follows IGP path and cannot add path constraints. E.g., R1’s counter-clockwise Edge router
is R7.
• R1 – R7
• R2 – R5
• R3 – R8
• R4 – R6

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 21
Path Configuration [cont.]
Path Configuration [cont.]
As the LSP would be signaled by LDP, there no need of an explicit path. Link LDP sessions to all
peers are already established for the interface configured under LDP.
Switch to notes view!
LDP signaled path verification:
Use the following command to verify the LSP signaled by LDP for the Edge router that is
counter-clockwise to the Core router.
oam ldp-treetrace prefix 10.10.10.x
ping 10.10.10.x
traceroute 10.10.10.x
(x can be 5 to 8)

A:R1# oam ldp-treetrace prefix 10.10.10.7/32

ldp-treetrace for Prefix 10.10.10.7/32:

10.3.7.7, ttl = 2 dst = 127.1.0.255 rc = EgressRtr status =

Done
22Nokia 2020
© Nokia Confidential

Hops: 10.1.3.3

ldp-treetrace discovery state: Done

ldp-treetrace discovery status: ' OK '
Total number of discovered paths: 1
Total number of failed traces: 0

3. Diagonal Path – Strict RSVP-TE:

Select a path that is different from the IGP path. IGP path can be found using the command
traceroute 10.10.10.x where x can be 5 to 8. E.g., IGP path from R1 to R8 is R1-R2-
R4-R8. Therefore, the opposite RSVP-TE Strict path from R1 to R8 is R1-R3-R4-R8.
• R1 – R8
• R2 – R7
• R3 – R6
• R4 –R5

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 22
Path Configuration
Path [cont.]
Configuration [cont.]
The following shows the IGP and LDP path from R1 to R8.
Switch to notes view!

A:R1# traceroute 10.10.10.8

traceroute to 10.10.10.8, 30 hops max, 40 byte packets
1 10.1.2.2 (10.1.2.2) 1.25 ms 0.759 ms 0.935 ms
2 10.2.4.4 (10.2.4.4) 1.35 ms 2.44 ms 1.31 ms
3 10.10.10.8 (10.10.10.8) 2.17 ms 1.98 ms 2.07 ms

A:R1# oam ldp-treetrace prefix 10.10.10.8/32

ldp-treetrace for Prefix 10.10.10.8/32:

10.4.8.8, ttl = 3 dst = 127.1.0.255 rc =

EgressRtr
23Nokia 2020
©
status = Done Nokia Confidential
Hops: 10.2.4.4 10.1.2.2

ldp-treetrace discovery state: Done

ldp-treetrace discovery status: ' OK '
Total number of discovered paths: 1
Total number of failed traces: 0

Since LDP follows IGP paths, IP and LDP traces show the same path of R1-R2-R4-R8. Therefore,
create an opposite RSVP-TE strict path R1-R3-R4-R8. Add loose path as secondary and fast-
reroute one-to-one for this RSVP path.

3.1 Loose path – Secondary

Add a loose path as secondary for the diagonal LSP.

It is important to note that LSP is uni-directional. Therefore, the above RSVP-TE and LDP
signaled paths on the Core routers create only an uni-directional LSP from the Core to Edge
routers. A similar RSVP-TE signaled paths should be should from the Edge to the Core routers
in order to have a symmetrical traffic path. The RSVP-TE config on the Edge routers are
omitted in here for brevity.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 23
Path Verification
Path Verification
Example of paths created in the Core router:
Switch to notes view!
A:R1>config>router>mpls# info
------------------------------------------------------------------------------
interface "system"
no shutdown
exit
interface "toR5"
no shutdown
exit
interface "toR2"
no shutdown
exit
interface "toR3"
no shutdown
exit
path "loose"
no shutdown In case of strict hops, use next
24Nokia 2020
© exit Nokia Confidential hop interface address.
path "to-R8-strict"
hop 10 10.1.3.3 strict Physical connectivity between
hop 20 10.3.4.4 strict the routers is required
hop 30 10.4.8.8 strict
no shutdown
exit
path "to-R6-loose"
hop 10 10.10.10.2 loose
In case of loose hops, you can
hop 20 10.10.10.6 loose use system interface address
no shutdown
exit
<< skip >>

Make sure you create paths on every Core router (R1 to R4) in the network. Also create
secondary paths, but you might also just create one ‘loose’ path with no hops specified.
show router mpls path 

A:R1# show router mpls path

==============================================================================
MPLS Path:
==============================================================================
Path Name Admin PathIdx
Hop Index IP Address/SID-Label Strict/Loose
------------------------------------------------------------------------------
loose Up 1
no hops n/a n/a

to-R8-strict Up 2
10 10.1.3.3 Strict
20 10.3.4.4 Strict
30 10.4.8.8 Strict

to-R6-loose Up 3
10 10.10.10.2 Loose
20 10.10.10.6 Loose

------------------------------------------------------------------------------
Total Paths : 3
==============================================================================

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 24
LSPLSP
Configuration
Configuration
If the paths are ready, now create LSP’s.
Switch to notes view!
1. Configure an LSP to all the other Edge routers in the network. Combine primary,
secondary.

A:R1>config>router>mpls# info
------------------------------------------------------------------------------
<< skip >>
lsp "lsp-toR8"
to 10.10.10.8
path-computation-method local-cspf
fast-reroute one-to-one
exit
primary "to-R8-strict"
exit
secondary "loose" LSP with primary, secondary and
exit Fast-Reroute (see further)
25Nokia 2020
© no shutdown Nokia Confidential
exit
lsp "lsp-toR6"
to 10.10.10.6
path-computation-method local-cspf
primary "to-R6-loose"
exit
no shutdown LSP with primary only
exit
no shutdown

2. When configuring the primary, try <?> to see what other constraints can be added
(bandwidth, exclude, hop-limit).

A:Rxx>config>router>mpls>lsp>primary#
[no] adaptive - Enable/Disable make-before-break functionality for the
LSP path
[no] backup-class-t* - Configure backup class-type for the LSP path
[no] bandwidth - Amount of bandwidth to be reserved for the path
bfd + Configure BFD for MPLS primary LSP
[no] class-type - Configure class-type for the LSP path
[no] exclude - Configure administrative groups that should be
excluded when the LSP path is setup
[no] hop-limit - Max number of hops that an LSP will traverse including
ingress and egress routers - overrides LSP
hop-limit
[no] include - Configure administrative groups that should be
included when the LSP path is setup
[no] priority - Configure setup and hold priority
[no] record - Enable/disable recording of all hops that an LSP path
traverses
[no] record-label - Enable/disable recording of recording of labels at
each node that an LSP path traverses
[no] shutdown - Administratively enable/disable the LSP path

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 25
LSPLSP
Verification
Verification
3. Use the following commands to verify the status of the LSPs and Paths:
Switch to notes view!
show router mpls path lsp-binding 
show router mpls lsp detail 
show router mpls lsp path detail 

Overview of the tunnels available:

A:R1# show router tunnel-table

==============================================================================
IPv4 Tunnel Table (Router: Base)
==============================================================================
Destination Owner Encap TunnelId Pref Nexthop Metric
Color
------------------------------------------------------------------------------
10.10.10.2/32
26Nokia 2020
© ldp MPLSNokia 65551
Confidential 9 10.1.2.2 10
10.10.10.3/32 ldp MPLS 65553 9 10.1.3.3 10
10.10.10.4/32 ldp MPLS 65555 9 10.1.2.2 20
10.10.10.4/32 ldp MPLS 65555 9 10.1.3.3 20
10.10.10.5/32 ldp MPLS 65557 9 10.1.5.5 10
10.10.10.6/32 rsvp MPLS 2 7 10.1.2.2 20
10.10.10.6/32 ldp MPLS 65559 9 10.1.2.2 20
10.10.10.7/32 ldp MPLS 65562 9 10.1.3.3 20
10.10.10.8/32 rsvp MPLS 1 7 10.1.3.3 30
10.10.10.8/32 ldp MPLS 65563 9 10.1.2.2 30
10.10.10.8/32 ldp MPLS 65563 9 10.1.3.3 30
------------------------------------------------------------------------------

RSVP-TE signaled path verification:

Perform LSP ping and trace on the primary and secondary path of the LSP’s that are signaled
by RSVP-TE (i.e., clockwise and diagonal Edge routers). Are the pings successful? What path is
taken by the primary path of the LSP? Does it follow the strict path as configured? Are the
OAM LSP ping and trace successful over the secondary path of the LSP?

oam lsp-ping <lsp-toRx> path <to-Rx-strict> 

oam lsp-ping <lsp-toRx> path loose 
oam lsp-trace <lsp-toRx> path <to-Rx-strict> 
oam lsp-trace <lsp-toRx> path loose 

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 26
LSPLSP
Verification [cont.]
Verification [cont.]

A:R1# oam lsp-ping "lsp-toR8" path "to-R8-strict"

Switch to
LSP-PING notes view!92 bytes MPLS payload
lsp-toR8:
Seq=1, send from intf toR3, reply from 10.10.10.8
udp-data-len=32 ttl=255 rtt=6.16ms rc=3 (EgressRtr)

---- LSP lsp-toR8 PING Statistics ----

1 packets sent, 1 packets received, 0.00% packet loss
round-trip min = 6.16ms, avg = 6.16ms, max = 6.16ms, stddev = 0.000ms

A:R1# oam lsp-trace "lsp-toR8" path "to-R8-strict"

lsp-trace to lsp-toR8: 0 hops min, 0 hops max, 116 byte packets
1 10.10.10.3 rtt=3.30ms rc=8(DSRtrMatchLabel) rsc=1
2 10.10.10.4 rtt=4.23ms rc=8(DSRtrMatchLabel) rsc=1
3 10.10.10.8 rtt=3.83ms rc=3(EgressRtr) rsc=1

A:R1# oam lsp-ping "lsp-toR6" path "to-R6-loose"

LSP-PING
27Nokia 2020 lsp-toR6: 92 bytes MPLS payload
© Nokia Confidential

Seq=1, send from intf toR2, reply from 10.10.10.6

udp-data-len=32 ttl=255 rtt=3.99ms rc=3 (EgressRtr)

---- LSP lsp-toR6 PING Statistics ----

1 packets sent, 1 packets received, 0.00% packet loss
round-trip min = 3.99ms, avg = 3.99ms, max = 3.99ms, stddev = 0.000ms

A:R1# oam lsp-trace "lsp-toR6" path "to-R6-loose"

lsp-trace to lsp-toR6: 0 hops min, 0 hops max, 116 byte packets
1 10.10.10.2 rtt=3.11ms rc=8(DSRtrMatchLabel) rsc=1
2 10.10.10.6 rtt=3.19ms rc=3(EgressRtr) rsc=1

A:R1# oam lsp-ping "lsp-toR8" path "loose"

LSP-PING lsp-toR8: 0 bytes MPLS payload
Send failed. Unable to get LSP label info

---- LSP lsp-toR8 PING Statistics ----

1 packets sent, 0 packets received, 100.00% packet loss

A:R1# oam lsp-trace "lsp-toR8" path "loose"

lsp-trace to lsp-toR8: 0 hops min, 0 hops max, 0 byte packets

Send failed. Unable to get LSP label info

Change the secondary path to standby mode and repeat your test. Does the OAM ping and
trace over the secondary path successful now?

configure router mpls lsp <lsp-toRx> secondary loose standby 

show router mpls status 

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 27
LSPLSP
Verification [cont.]
Verification [cont.]

A:R1# oam lsp-ping "lsp-toR8" path "loose"

Switch to
LSP-PING notes view!92 bytes MPLS payload
lsp-toR8:
Seq=1, send from intf toR3, reply from 10.10.10.8
udp-data-len=32 ttl=255 rtt=5.04ms rc=3 (EgressRtr)

---- LSP lsp-toR8 PING Statistics ----

1 packets sent, 1 packets received, 0.00% packet loss
round-trip min = 5.04ms, avg = 5.04ms, max = 5.04ms, stddev = 0.000ms

A:R1# oam lsp-trace "lsp-toR8" path "loose"

lsp-trace to lsp-toR8: 0 hops min, 0 hops max, 116 byte packets
1 10.10.10.3 rtt=2.33ms rc=8(DSRtrMatchLabel) rsc=1
2 10.10.10.4 rtt=3.16ms rc=8(DSRtrMatchLabel) rsc=1
3 10.10.10.8 rtt=3.61ms rc=3(EgressRtr) rsc=1

Try following commands:

tools
© dump mpls-resource 
28Nokia 2020 Nokia Confidential

tools dump router mpls 

tools perform router mpls resignal lsp <lsp-toRx> path <to-Rx-strict> 
In the debug command tree, the MPLS event type can be selected.
debug router mpls lsp <“xxx“> event all 

A:admin@R1# tools dump mpls-resources

Global MPLS Resource Usage
-------------------------+------------+-------------+-------------+
| Total | Allocated | Free |
-------------------------+------------+-------------+-------------+
mpls NHLFE | 262126 | 37 | 262089 |
RSVP | | 19 | |
LDP | | 18 | |
BGP | | 0 | |
MPLS-TP | | 0 | |
SR | | 0 | |
BIER | | 0 | |
TREE-SID | | 0 | |
mpls labels | 524256 | 22 | 524234 |
RSVP | | 6 | |
LDP | | 16 | |
BGP | | 0 | |
MPLS-TP | | 0 | |
STATIC-SVC | | 0 | |
SR | | 0 | |
BIER | | 0 | |
RESERVED-BLK | | 0 | |
mpls LTN (FTN) | 131072 | 17 | 131055 |
RSVP | | 3 | |
LDP | | 14 | |
BGP | | 0 | |
MPLS-TP | | 0 | |
SR | | 0 | |
BIER | | 0 | |
TREE-SID | | 0 | |

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 28
LSPLSP
Verification [cont.]
Verification [cont.]

[tools dump router mpls]

Switch to notes view!
A:admin@R1#

bypass-tunnel - Dump tools for MPLS bypass tunnel

forwarding-policies - Dump tools for MPLS Forwarding Policies
ftn - Dump ftn information for MPLS
ilm - Dump ilm information for MPLS
logger-event- - Dump logger-event-bundling information for MPLS
bundling
lspinfo - Dump LSP information for MPLS
memory-usage - Dump memory usage information for MPLS
te-lspinfo - Dump TE LSP information for MPLS
tp-interface - Dump MPLS-TP interface information
tp-tunnel - Dump MPLS-TP tunnel information

29Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 29
TE TE
Metric Configuration
Metric Configuration
Beside the hop constraint (strict or loose) that can be applied for RSVP-TE signaled LSPs, other
constraints such
Switch to as TE-metric
notes view! can be used to alter routing. For example, the RSVP-TE signaled LSPs
using loose path normally follow the IGP path. However, the path can be altered by TE-metric.
1. Each pair of students run the following commands on their Core router (R1 to R4) to verify the IP
and LSP path for the clockwise LSP to the Edge router. For example, for R1, the clockwise Edge
router is R6 using the LSP “to-R6-loose”:

traceroute 10.10.10.6 

A:R1# traceroute 10.10.10.6

traceroute to 10.10.10.6, 30 hops max, 40 byte packets
1 10.1.2.2 (10.1.2.2) 1.74 ms 1.88 ms 2.11 ms
2 10.10.10.6 (10.10.10.6) 4.26 ms 2.27 ms 3.05 ms

oam lsp-trace "lsp-toR6" path "to-R6-loose"

30Nokia 2020
© Nokia Confidential

A:R1# oam lsp-trace "lsp-toR6" path "to-R6-loose"

lsp-trace to lsp-toR6: 0 hops min, 0 hops max, 116 byte packets
1 10.10.10.2 rtt=2.46ms rc=8(DSRtrMatchLabel) rsc=1
2 10.10.10.6 rtt=3.52ms rc=3(EgressRtr) rsc=1

The RSVP-TE loose path follows the IGP path and thus the path from R1 to R6 is the same for both IP
and LSP.
2. Apply te-metric 500 to the adjacent router of the IGP path. For R1, the adjacent router of the
IGP path is R2. Also, enable metric-type te under relevant LSP. Make sure underlying IGP
has traffic-engineering configured.

A:R1>config>router>mpls# info
------------------------------------------------------------------------------
interface "system"
no shutdown
exit
interface "toR2"
te-metric 500
no shutdown
exit
<< skip >>
path "loose"
no shutdown
exit
path "to-R6-loose"
hop 10 10.10.10.2 loose
hop 20 10.10.10.6 loose
no shutdown
exit
<< skip >>
lsp "lsp-toR6"
to 10.10.10.6
path-computation-method local-cspf
metric-type te
primary "to-R6-loose"
exit
no shutdown
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 30
TE TE
Metric Verification
Metric Verification
With high te-metric between R1 and R2 and metric-type te enabled, the IP path
between
SwitchR1
toand R2view!
notes remains the same but the LSP lsp-toR6 using the loose path takes a
different route with the lowest aggregated te-metric.

traceroute 10.10.10.6 

A:R1# traceroute 10.10.10.6

traceroute to 10.10.10.6, 30 hops max, 40 byte packets
1 10.1.2.2 (10.1.2.2) 3.33 ms 1.86 ms 2.40 ms
2 10.10.10.6 (10.10.10.6) 3.03 ms 2.75 ms 2.74 ms

oam lsp-trace "lsp-toR6" path "to-R6-loose"

A:R1# oam lsp-trace "lsp-toR6"

lsp-trace to lsp-toR6: 0 hops min, 0 hops max, 116 byte packets
31Nokia 2020
© Nokia Confidential
1 10.10.10.3 rtt=3.62ms rc=8(DSRtrMatchLabel) rsc=1
2 10.10.10.4 rtt=5.14ms rc=8(DSRtrMatchLabel) rsc=1
3 10.10.10.2 rtt=3.60ms rc=8(DSRtrMatchLabel) rsc=1
4 10.10.10.6 rtt=4.19ms rc=3(EgressRtr) rsc=1

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 31
Configure One-to-One
Configure FRR
One-to-One FRR
If lab TE-Metric is just completed, make sure we reset the lab by running the following
procedures:
Switch to notes view!
• Remove and te-metric and metric-type te.
• Shutdown the interface under MPLS where te-metric was applied and remove it, and no
shutdown the link back again.
1. On the Core routers (R1 to R4), configure Fast Reroute using the one-to-one method with
node protection on the LSP to the diagonal Edge router. E.g., for R1, LSP to-R8-strict is the
diagonal LSP to the Edge router R8.

configure router mpls lsp <lsp-toRx> fast-reroute one-to-one 

A:R1>config>router>mpls# info
------------------------------------------------------------------------------
<< skip >>
lsp "lsp-toR8"
32Nokia 2020
© to 10.10.10.8 Nokia Confidential
path-computation-method local-cspf
fast-reroute one-to-one
exit
primary "to-R8-strict"
exit
secondary "loose"
exit
no shutdown
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 32
Configure One-to-One
Configure FRR
One-to-One FRR[cont.]
[cont.]

2. Run the following commands to identify the FRR one-to-one detour, detour-transit and
Switch to notes view!
detour-terminate.
show router rsvp session detour detail

A:R1# show router rsvp session detour detail

------------------------------------------------------------------------------
LSP : lsp-toR8::to-R8-strict_detour
------------------------------------------------------------------------------
From : 10.10.10.1 To : 10.10.10.8
Tunnel ID : 1 LSP ID : 18950
Style : SE State : Up
Session Type : Originate (Detour)
In Interface : n/a Out Interface : 1/1/2
In IF Name : n/a
Out IF Name : toR2
In Label : n/a Out Label : 524266
Previous
33Nokia 2020 Hop
© : n/a Next Hop
Nokia Confidential : 10.1.2.2
SetupPriority : 7 Hold Priority : 0
Class Type : 0
SubGrpOrig ID : 0 SubGrpOrig Addr:
P2MP ID : 0
FrrAvailType : N/A
FrrSrlgStrict : N/A SrlgDisjoint : N/A

Path Recd : 0 Path Sent : 7

Resv Recd : 6 Resv Sent : 1
Summary msgs :
SPath Recd : 0 SPath Sent : 0
SResv Recd : 0 SResv Sent : 0
LSP Attr Flags : N/A
==============================================================================

The primary path from R1 to R8 is R1R3R4R8 determined by the RSVP signaled lsp-toR8
with path to-R8-strict. The detour is via R2 with next-hop interface 10.1.2.2 using out Label
524266.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 33
Configure One-to-One
Configure FRR
One-to-One FRR[cont.]
[cont.]
show router rsvp session detour-transit
Switch to notes view!
A:R1# show router rsvp session detour-transit

==============================================================================
RSVP Sessions
==============================================================================
RSVP Session Name
From To Tunnel ID LSP ID State
------------------------------------------------------------------------------
lsp-toR6::to-R6-strict_detour
10.10.10.3 10.10.10.6 1 15872 Up

lsp-toR7::to-R7-strict_detour
10.10.10.2 10.10.10.7 1 9728 Up

------------------------------------------------------------------------------
Sessions : 2
==============================================================================
34Nokia 2020
© Nokia Confidential

show router rsvp session detour-terminate

A:R1# show router rsvp session detour-terminate

==============================================================================
RSVP Sessions
==============================================================================
RSVP Session Name
From To Tunnel ID LSP ID State
------------------------------------------------------------------------------
lsp-toR5::to-R5-strict_detour
10.10.10.4 10.10.10.5 1 25600 Up

lsp-toR8::to-R8-strict_detour
10.10.10.1 10.10.10.8 1 18950 Up

------------------------------------------------------------------------------
Sessions : 2
==============================================================================

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 34
RSVP Shortcut
RSVP Shortcut
1. In Lab 1 LDP shortcut, we learnt that IP routing-table’s next-hop resolution can be affected
by LDPtoshortcut.
Switch On the Core routers (R1 to R4), explain the routing table.
notes view!

A:R1# show router route-table

==============================================================================
Route Table (Router: Base)
==============================================================================
Dest Prefix[Flags] Type Proto Age
Pref
Next Hop[Interface Name] Metric
------------------------------------------------------------------------------
<< skip link routing entries >>
10.10.10.1/32 Local Local 01d09h20m 0
system 0
10.10.10.2/32 Remote LDP 01d09h19m 9
10.1.2.2 (tunneled) 100
10.10.10.3/32 Remote LDP 00h00m04s 9
10.1.3.3 (tunneled)
35Nokia 2020
© Nokia Confidential 100
10.10.10.4/32 [L] Remote LDP 00h00m04s 9
10.1.2.2 (tunneled) 200
10.10.10.5/32 Remote LDP 01d09h19m 9
10.1.5.5 (tunneled) 100
10.10.10.6/32 Remote LDP 00h14m49s 9
10.1.2.2 (tunneled) 200
10.10.10.7/32 Remote LDP 00h00m05s 9
10.1.3.3 (tunneled) 200
10.10.10.8/32 [L] Remote OSPF 00h14m49s 10
10.1.2.2

Since ldp-shortcut is enabled on all routers in Lab 1, LDP tunnels are used as the next-hop in
the routing table.
With the above routing table, perform a traceroute from the Core router to the diagonal Edge
router to identify the path before we apply RSVP-shortcut.

A:R1# traceroute 10.10.10.8

traceroute to 10.10.10.8, 30 hops max, 40 byte packets
1 10.1.2.2 (10.1.2.2) 1.61 ms 1.45 ms 1.65 ms
2 10.2.4.4 (10.2.4.4) 2.81 ms 4.81 ms 3.10 ms
3 10.10.10.8 (10.10.10.8) 4.02 ms 12.4 ms 6.17 ms

From R1 to R8, the normal IGP path is R1-R2-R4-R8.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 35
RSVP Shortcut
RSVP [cont.]
Shortcut [cont.]

2. Configure RSVP-TE Shortcut on the OSPF instance and verify the routing table again.
Switch to notes view!

A:Rxx>config>router>ospf# info
------------------------------------------------------------------------------
traffic-engineering
<< skip >>
igp-shortcut
tunnel-next-hop
family ipv4
resolution filter
resolution-filter
rsvp
exit
exit
exit
exit
no shutdown
36Nokia 2020
© Nokia Confidential

When RSVP shortcut is enabled, whenever RSVP tunnel to a remote end-point is available, the
next hops in the routing table are updated accordingly. For example, R1 has RSVP-TE signaled
LSPs to R6 and R8. Therefore, when RSVP shortcut is enabled, the next hops to these two
destinations are RSVP signaled LSP tunnels.

A:R1# show router route-table

==============================================================================
Route Table (Router: Base)
==============================================================================
Dest Prefix[Flags] Type Proto Age Pref
Next Hop[Interface Name] Metric
------------------------------------------------------------------------------
<< skip >>
10.10.10.1/32 Local Local 05d08h17m 0
system 0
10.10.10.2/32 Remote LDP 23h02m32s 9
10.1.2.2 (tunneled) 10
10.10.10.3/32 Remote LDP 23h02m32s 9
10.1.3.3 (tunneled) 10
10.10.10.4/32 [L] Remote LDP 00h02m08s 9
10.1.2.2 (tunneled) 20
10.10.10.5/32 Remote LDP 23h02m32s 9
10.1.5.5 (tunneled) 10
10.10.10.6/32 Remote OSPF 00h02m08s 10
10.10.10.6 (tunneled:RSVP:2) 20
10.10.10.7/32 Remote LDP 23h02m32s 9
10.1.3.3 (tunneled) 20
10.10.10.8/32 Remote OSPF 00h02m08s 10
10.10.10.8 (tunneled:RSVP:1) 30

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 36
RSVP Shortcut
RSVP [cont.]
Shortcut [cont.]

The following shows the priority (highest is better) of shortcuts installed onto RTM:
1. Switch to notes view!
RSVP shortcut
2. LDP shortcut
3. IGP learnt routes

Repeat the traceroute from the Core router to the diagonal Edge router to verify that the
path is now following the RSVP path.

A:R1# traceroute 10.10.10.8

traceroute to 10.10.10.8, 30 hops max, 40 byte packets
1 10.1.3.3 (10.1.3.3) 1.85 ms 1.69 ms 1.58 ms
2 10.3.4.4 (10.3.4.4) 2.79 ms 2.74 ms 2.76 ms
3 10.10.10.8 (10.10.10.8) 4.06 ms 4.98 ms 5.05ms

With©37Nokia
RSVP-shortcut,
2020 the path from R1 to R8Nokia
now follows the RSVP path R1-R3-R4-R8.
Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 37
Wrap-up
In this module we have covered the following items:
• Configured:
̵ LDP
̵ Loop Free Alternate LDP
̵ LDP FRR
̵ Equal Cost Multi Path (ECMP)
̵ LDP-shortcut
̵ RSVP-TE with bandwidth constraints
̵ Limiting oversubscription
̵ MPLS Fast Reroute
̵ RSVP-shortcut

38Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 38
39Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S04M01 Ed0 39
 Service Architecture

ER00198-V-2000 V0 - S05M01 Ed0

1 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M01 Ed0 1
Learning Objectives
Upon completion of this module, you should be able to:
• Configure:
̵ Customer
̵ Port preparation
̵ MTU
̵ Full mesh SDP’s
̵ OAM

2 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M01 Ed0 2
 ToC Slide

Table of Contents

Lab Setup
Service Architecture
Wrap-up

3 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M01 Ed0 3
 Lab Setup

4 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M01 Ed0 4
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y).

Initial rollback config file’s comment (X) – Final-MPLS RSVP-TE.

• /admin rollback revert X

Final rollback config file’s comment (Y) – Final-Services SDP.

To compare current config with the final lab answer:

• /admin rollback compare active-cfg to Y

5 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M01 Ed0 5
 Service Architecture

6 Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M01 Ed0 6
Configure Customer
Configure and
Customer Access
and AccessPort
Port
1. On Edge routers (R5 to R8), create customer 100 as we are going to build network services
among Edge
Switch to routers.
notes view! Core routers (R1 to R4) are just for transporting network services.
Provide the customer a description, contact information and a phone number.

Note: A customer is locally significant, but it is advisable to be consistent throughout the

network .

A:PExx>config>service# info
---------------------------------------------- Default customer 1 is
customer 1 name "1" create always available.
description "Default customer"
exit
customer 100 name "100" create
description "EDU Ottawa, Canada"
exit
7 Nokia 2020
© Nokia Confidential

On the Edge routers (R5 to R8), specify port 1/1/5 as an Access Port for terminating
customer 100’s network services’ (e.g., epipe, VPLS, VPRN) traffic in the later lab
Exercises.

Access Port Config:

1. Change the port facing the customer (see lab diagram) to an access port.

A:R5# configure port 1/1/5

A:R5>config>port# info
----------------------------------------------
description "Access port to terminate customer traffic"
ethernet
mode access
encap-type dot1q
mtu 9212
lldp
dest-mac nearest-bridge
admin-status tx-rx
notification
tx-tlvs port-desc sys-name sys-desc sys-cap
tx-mgmt-address system
exit
exit
exit
no shutdown

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M01 Ed0 7
Configure Customer
Configure and
Customer Access
and AccessPort
Port[cont.]
[cont.]

2. Show port list.

Switch to notes view!

A:R5# show port

==============================================================================
Ports on Slot 1
==============================================================================
Port Admin Link Port Cfg Oper LAG/ Port Port Port C/QS/S/XFP/
Id State State MTU MTU Bndl Mode Encp Type MDIMDX
------------------------------------------------------------------------------
1/1/1 Up Yes Up 9212 9212 - netw null vspeed 10GBASE-LR *
1/1/2 Up Yes Up 9212 9212 - netw null vspeed 10GBASE-LR *
1/1/3 Up Yes Up 9212 9212 - netw null vspeed 10GBASE-LR *
1/1/4 Up Yes Up 9212 9212 - netw null vspeed 10GBASE-LR *
1/1/5 Up Yes Up 9212 9212 - accs dotq vspeed 10GBASE-LR *
1/1/6 Up Yes Up 9212 9212 - netw null vspeed 10GBASE-LR *
8 Nokia 2020
© Nokia Confidential
1/1/7 Up Yes Up 9212 9212 - netw null vspeed 10GBASE-LR *
<< skip >>

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M01 Ed0 8
SAPSAP
andand
SDPSDP
To build VPN services such as ePipe and VPLS, we use the service model with the
following
Switchcomponents:
to notes view!

• SAP= Service Access Point, where customer traffic enters the service.
• Service= defines the behaviour of the service
• Customer= owns the service
• SDP= Service Distribution Path, tunnel access to get to the other sites

Each MPLS network service such as ePipe, VPLS and VPRN establish Transport and Service
labels to identify the network and service endpoints respectively. SDP identifies the Transport
tunnel for carrying the service tunnel and traffic to the network destinations or endpoints. This
is very similar to IP and UDP/TCP ports.

In the below diagram, network service IDs 25 and 50 share the same SDP transport (SDP 3 and
5) between the two PEs but the network services are belonged two different customers 100
9 Nokia 2020
© Nokia Confidential
and 200. Nevertheless, the two customers’ traffic are separated by different service IDs.

The initial rollback config has pre-defined MPLS LSP and path configured among the Edge
routers (R5/R8 and R6/R7) for RSVP-TE transport tunnel signaling. Verify the path and LSP
status:

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M01 Ed0 9
SAPSAP
andand
SDP [cont.]
SDP [cont.]
The initial rollback configuration has pre-defined MPLS LSP and path configured among the
Edge routers
Switch (R5/R8
to notes and R6/R7) for RSVP-TE transport tunnel signaling. Verify the path and
view!
LSP status:

A:R5# show router mpls path

==============================================================================
MPLS Path:
==============================================================================
Path Name Admin
PathIdx
Hop Index IP Address/SID-Label Strict/Loose
------------------------------------------------------------------------------
loose Up 1
no hops n/a n/a

------------------------------------------------------------------------------
Total Paths : 1
10Nokia 2020
© Nokia Confidential
==============================================================================

A:R5# show router mpls lsp

==============================================================================
MPLS LSPs (Originating)
==============================================================================
LSP Name To Tun Fastfail Adm Opr
Id Config
------------------------------------------------------------------------------
lsp-toR8 10.10.10.8 1 No Up Up
------------------------------------------------------------------------------
LSPs : 1

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M01 Ed0 10
FullFull
Mesh SDP
Mesh Configuration
SDP Configuration
SDP’s allow us to tunnel (i.e. Transport Tunnel) network services’ traffic to the remote
endpoint
Switchor
toPE.
notes view!
1. On the Edge routers (R5 to R8), configure a full mesh of SDPs to other Edge routers using
different Transport Tunnel signalling protocols such as LDP, RSVP and GRE.

Edge Router (R5 – R8):

SDP 10x LDP (R5/R6, R7/R8)

SDP 20x RSVP (R5/R8, R6/R7)

SDP 30x GRE (R5/R7, R6/R8)

X is the destination Edge router. For example, R5 has a LDP signaled SDP to R6 and the SDP is
106. Similarly, R5 has a RSVP signaled SDP to R8. Therefore, the SDP from R5 to R8 is 208.
Warning: GRE will not work if ‘shortcuts’ is active.NokiaDeactivate shortcuts on LDP and RSVP before
configuring GRE, if necessary.
11Nokia 2020
© Confidential

R5 and R8 fully meshed SDP config.

A:R5# configure service A:R8# configure service

A:R5>config>service# info A:R8>config>service# info
----------------------------------------- -----------------------------------------
sdp 106 mpls create sdp 107 mpls create
description "LDP SDP to R6" description "LDP SDP to R7"
far-end 10.10.10.6 far-end 10.10.10.7
ldp ldp
keep-alive keep-alive
shutdown shutdown
exit exit
no shutdown no shutdown
exit exit
sdp 208 mpls create sdp 205 mpls create
description "RSVP-TE SDP to R8" description "RSVP-TE SDP to R5"
far-end 10.10.10.8 far-end 10.10.10.5
lsp "lsp-toR8" lsp "lsp-toR5"
keep-alive keep-alive
shutdown shutdown
exit exit
no shutdown no shutdown
exit exit
sdp 307 create sdp 306 create
description "GRE SDP to R7" description "GRE SDP to R6"
far-end 10.10.10.7 far-end 10.10.10.6
keep-alive keep-alive
shutdown shutdown
exit exit
no shutdown no shutdown
exit exit
customer 1 create customer 1 create
description "Default customer" description "Default customer"
exit exit
customer 100 create customer 100 create
description "EDU Ottawa" description "EDU Ottawa"
contact "Derek Cheung" contact "Derek Cheung"
phone "+613-7654321" phone "+613-7654321"
exit exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M01 Ed0 11
FullFull
Mesh SDP
Mesh Configuration
SDP Configuration[cont.]
[cont.]
R6 and R7 fully meshed SDP config.
Switch to notes view!
A:R6# configure service A:R7# configure service
A:R6>config>service# info A:R7>config>service# info
------------------------------------------- -------------------------------------------
sdp 105 mpls create sdp 108 mpls create
description "LDP SDP to R5" description "LDP SDP to R8"
far-end 10.10.10.5 far-end 10.10.10.8
ldp ldp
keep-alive keep-alive
shutdown shutdown
exit exit
no shutdown no shutdown
exit exit
sdp 207 mpls create sdp 206 mpls create
description "RSVT-TE SDP to R7" description "RSVP-TE SDP to R6"
far-end 10.10.10.7 far-end 10.10.10.6
lsp "lsp-toR7" lsp "lsp-toR6"
12Nokia 2020
©
keep-alive Nokia Confidential
keep-alive
shutdown shutdown
exit exit
no shutdown no shutdown
exit exit
sdp 308 create sdp 305 create
description "GRE SDP to R8" description "GRE SDP to R5"
far-end 10.10.10.8 far-end 10.10.10.5
keep-alive keep-alive
shutdown shutdown
exit exit
no shutdown no shutdown
exit exit
customer 1 create customer 1 create
description "Default customer" description "Default customer"
exit exit
customer 100 create customer 100 create
description "EDU Ottawa" description "EDU Ottawa"
contact "Derek Cheung" contact "Derek Cheung"
phone "+613-7654321" phone "+613-7654321"
exit exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M01 Ed0 12
FullFull
Mesh SDP Verification
Mesh SDP Verification
Verify the configured SDPs. Each Edge router (R5 to R8) should have 3 SDPs using
LDP,Switch
RSVP-TE and GRE
to notes view!for Transport tunnel signaling.
show service sdp 

R5:

A:R5# show service sdp

============================================================================
Services: Service Destination Points
============================================================================
SdpId AdmMTU OprMTU Far End Adm Opr Del LSP Sig
----------------------------------------------------------------------------
106 0 9190 10.10.10.6 Up Up MPLS L TLDP
208 0 9190 10.10.10.8 Up Up MPLS R TLDP
307 0 9170 10.10.10.7 Up Up GRE n/a TLDP
----------------------------------------------------------------------------
13Nokia 2020
© Nokia Confidential
Number of SDPs : 3
----------------------------------------------------------------------------
Legend: R = RSVP, L = LDP, B = BGP, M = MPLS-TP, n/a = Not Applicable
I = SR-ISIS, O = SR-OSPF, T = SR-TE, F = FPE
============================================================================

R6:

A:R6# show service sdp

============================================================================
Services: Service Destination Points
============================================================================
SdpId AdmMTU OprMTU Far End Adm Opr Del LSP Sig
----------------------------------------------------------------------------
105 0 9190 10.10.10.5 Up Up MPLS L TLDP
207 0 9190 10.10.10.7 Up Up MPLS R TLDP
308 0 9170 10.10.10.8 Up Up GRE n/a TLDP
----------------------------------------------------------------------------
Number of SDPs : 3
----------------------------------------------------------------------------
Legend: R = RSVP, L = LDP, B = BGP, M = MPLS-TP, n/a = Not Applicable
I = SR-ISIS, O = SR-OSPF, T = SR-TE, F = FPE
============================================================================

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M01 Ed0 13
FullFull
Mesh SDP Verification [cont.]
Mesh SDP Verification [cont.]

R7:
Switch to notes view!

A:R7# show service sdp

============================================================================
Services: Service Destination Points
============================================================================
SdpId AdmMTU OprMTU Far End Adm Opr Del LSP Sig
----------------------------------------------------------------------------
108 0 9190 10.10.10.8 Up Up MPLS L TLDP
206 0 9190 10.10.10.6 Up Up MPLS R TLDP
305 0 9170 10.10.10.5 Up Up GRE n/a TLDP
----------------------------------------------------------------------------
Number of SDPs : 3
----------------------------------------------------------------------------
Legend: R = RSVP, L = LDP, B = BGP, M = MPLS-TP, n/a = Not Applicable
14Nokia 2020I = SR-ISIS, O = SR-OSPF, T Nokia
© = SR-TE,
Confidential F = FPE
============================================================================

R8:

A:R8# show service sdp

============================================================================
Services: Service Destination Points
============================================================================
SdpId AdmMTU OprMTU Far End Adm Opr Del LSP Sig
----------------------------------------------------------------------------
107 0 9190 10.10.10.7 Up Up MPLS L TLDP
205 0 9190 10.10.10.5 Up Up MPLS R TLDP
306 0 9170 10.10.10.6 Up Up GRE n/a TLDP
----------------------------------------------------------------------------
Number of SDPs : 3
----------------------------------------------------------------------------
Legend: R = RSVP, L = LDP, B = BGP, M = MPLS-TP, n/a = Not Applicable
I = SR-ISIS, O = SR-OSPF, T = SR-TE, F = FPE
============================================================================

Note: In case the SDPs are remaining in the operationally down state, check with the
command, show service sdp details and carefully look for clues.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M01 Ed0 14
OAM Tools
OAM Tools
Note: SDP Ping performs in-band uni-directional or round-trip connectivity tests on SDPs. The
SDPSwitch
Ping OAM packets
to notes view!are sent in-band, in the tunnel encapsulation, so it will follow the same
path as traffic within the service. The SDP Ping response can be received out-of-band in the
control plane, or in-band using the data plane for a round-trip test.

1. Perform a uni-directional SDP Ping. What is the Path MTU? Why is there no Remote SDP-ID?

oam sdp-ping <XXX> 

Note: You have tested the local SDP but have not performed a round-trip test.. <XXX> is the
local SDP.

A:R5# oam sdp-ping 208

--------------------------------------------------------------------
15Nokia 2020
© Nokia Confidential
Actual IP Address - Local : 10.10.10.5
Expected Peer IP - Remote : 10.10.10.5
Actual IP Address - Remote : 10.10.10.8
Expected Peer IP - Local : 10.10.10.8
IP Address Mismatch : No
--------------------------------------------------------------------
Err SDP-ID Info Local Remote
--------------------------------------------------
SDP-ID: 208 N/A
Administrative State: Up N/A
Operative State: Up N/A
Path MTU: 9190 N/A
Response SDP Used: No
IP Interface State: Up
Forwarding Class be be
Profile In Out

Request Result: Sent - Reply Received

RTT: 3.04(ms)

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M01 Ed0 15
OAM Tools [cont.]
OAM Tools [cont.]

Path MTU 9190 (Network 9212 port MTU – 22 Ethernet, Transport and Service headers = 9190
Switch
bytes) to notes
is only view! value. We will measure the actual Path MTU later as there can be
a calculated
equipment in the network path that limits the Path MTU.

2. Perform a round-trip SDP Ping Test. What is the Remote SDP-ID?

oam sdp-ping <XXX> resp-sdp <YYY> 

Note: This is a round-trip test, both directions are using the SDP. <XXX> is the local
SDP and <YYY> is the remote SDP.

A:R5# oam sdp-ping 208 resp-sdp 205

--------------------------------------------------------------------
Actual IP Address - Local : 10.10.10.5
Expected Peer IP - Remote : 10.10.10.5
16Nokia 2020
© Nokia Confidential
Actual IP Address - Remote : 10.10.10.8
Expected Peer IP - Local : 10.10.10.8
IP Address Mismatch : No
--------------------------------------------------------------------
Err SDP-ID Info Local Remote
--------------------------------------------------
SDP-ID: 208 205
Administrative State: Up Up
Operative State: Up Up
Path MTU: 9190 N/A
Response SDP Used: Yes
IP Interface State: Up
Forwarding Class be be
Profile In Out

Request Result: Sent - Reply Received

RTT: 2.70(ms)

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M01 Ed0 16
OAM Tools
OAM [cont.]
Tools [cont.]
3. Discover the MTU size supported over your SDPs. What is the MTU?
Switch to notes view!
Note: The Path MTU Discovery tool provides a powerful tool that enables a service provider to
get the exact MTU supported between the service ingress and service termination points
(accurate to one byte). It is important to understand the MTU of the entire path end-to-end
when provisioning services, especially for Virtual Leased Line (VLL) services where the service
must support the ability to transmit the largest customer packet.

oam sdp-mtu <XXX> size-inc 1490 1500 step 10 

Note: <XXX> is the local SDP.

A:R5# oam sdp-mtu 208 size-inc 1490 1500 step 1

Size Sent Response
----------------------------
17Nokia 2020
© Nokia Confidential
1490 . Success
1491 . Success
1492 . Success
1493 ... Request Timeout

Maximum Response Size: 1492

The calculated Path MTU from R5 to R8 via RSVP-TE signaled SDP 208 is 9190 bytes. However,
the measured Path MTU is only 1492 bytes. In other words, some network equipment (e.g.,
Ethernet bridges) along the data path between R5 to R8 has limited the Path MTU to only 1492
bytes.
[hint: default Ethernet MTU (1514) – Ethernet, MPLS transport and Service headers (22) = 1492]

SDP signaled by RSVP-TE and LDP has a 22 bytes network header comprising Ethernet (14),
MPLS Transport (4) and Service (4) Headers. For GRE signaled SDP, the network header is 42
bytes.

A:R5>config>service# oam sdp-mtu 307 size-inc 1470 1500 step 1

Size Sent Response
----------------------------
1470 . Success
1471 . Success
1472 . Success
1473 ... Request Timeout

Maximum Response Size: 1472

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M01 Ed0 17
OAM Tools [cont.]
OAM Tools [cont.]
In general, we set the Network Port’s MTU to the maximum value (.e.g, 9212 bytes)
supported bynotes
Switch to the hardware
view! since multiple network services can use the network port and
thus the network port’s MTU should not be adjusted to suit a particular network service.

SDP or Path MTU is automatically calculated by subtracting the transmission header (22
bytes for RSVP-TE and LDP and 42 bytes for GRE) from the Network Port’s MTU.
Therefore, the maximum path MTU for RSVP-TE or LDP signaled SDP is 9190 bytes.

The setting of the Service or VC MTU will be covered in the next lab.

18Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M01 Ed0 18
Wrap-up
In this module we have covered the following items:
• Configured:
̵ Customer
̵ Port preparation
̵ MTU
̵ Full mesh SDP’s
̵ OAM

19Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M01 Ed0 19
20Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M01 Ed0 20
 EPIPE VPLS VPRN

ER00198-V-2000 V0 - S05M02 Ed0

1 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 1
Learning Objectives
Upon completion of this module, you should be able to:
• Perform the following operations:
- Configure an Epipe (VLL) service
- Verify an Epipe
- Configure a VPLS
- Verify a VPLS
- Configure the Virtual Private Network Service (VPRN)
- VPRN verification

• Understand:
- Service Label
- VC ID
- Route Target
- Route Distinguisher
- MP-BGP

2 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 2
 ToC Slide

Table of Contents

Lab Setup
EPIPE
VPLS
VPRN
Wrap-up

3 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 3
 Lab Setup

4 Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
------------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 4
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y).

Initial rollback config file’s comment (X) – Final-Services SDP.

• /admin rollback revert X

Final rollback config file’s comment (Y) – Final – Epipe.

To compare current config with the final lab answer:
• /admin rollback compare active-cfg to Y

5 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 5
 EPIPE

6 Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
------------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 6
Epipe Configuration
Epipe Configuration
Two Epipes (customer 100) are created among the Edge routers as follows:
R5 – R8:
• Switch to notes view!
- SAP 1/1/5:0
- Service and VC IDs = 58
- R5’s SDP = 208, R8’s SDP = 205
• R6 – R7:
- SAP 1/1/5:0
- Service and VC IDs = 67
- R6’s SDP = 207, R7’s SDP = 206

It is a common practice to have Service ID = VC ID. However, since the Service ID is only local
significant, Service IDs on both ends can be different. However, VC ID (i.e., MPLS Service Label)
needs to match on both ends.

Verify port 1/1/5 has a dot1q encapsulation and it is an Access port. If the incoming traffic has
©7 Nokia 2020 Nokia Confidential
a VLAN tag of non-zero such as 123, the SAP definition would be SAP 1/1/5:123.

1. The following shows the Epipe 58 setup for Students 1, 2, 7 and 8. Students 3, 4, 5 and 6
for Epipe 67 have a similar setup but different Service and VC IDs.

A:R5# configure port 1/1/5

A:R5>config>port# info
----------------------------------------------
description "Access port to terminate customer traffic"
ethernet
mode access
encap-type dot1q
lldp
dest-mac nearest-bridge
<< skip >>

A:R5>config>service# info A:R8>config>service# info

----------------------------------------- ----------------------------------------
sdp 208 mpls create sdp 205 mpls create
description "RSVP-TE SDP to R8" description "RSVP-TE SDP to R5"
far-end 10.10.10.8 far-end 10.10.10.5
lsp "lsp-toR8" lsp "lsp-toR5"
keep-alive keep-alive
shutdown shutdown
exit exit
no shutdown no shutdown
exit exit
epipe 58 customer 100 create epipe 58 customer 100 create
sap 1/1/5:0 create sap 1/1/5:0 create
no shutdown no shutdown
exit exit
spoke-sdp 208:58 create spoke-sdp 205:58 create
no shutdown no shutdown
exit exit
no shutdown no shutdown
exit exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 7
Epipe Transport
Epipe Tunnel
Transport Verification
Tunnel Verification
2. Verify the Epipe. What are the Transport Labels used to reach the remote PE? What are the
Service labels
Switch to notesused to reach the Epipe on the remote PE?
view!

/config router mpls 

A:R5>config>router>mpls# info
----------------------------------------------
interface "system"
no shutdown
exit
interface "toR1"
no shutdown
exit
path "loose"
no shutdown
exit
lsp "lsp-toR8"
8 Nokia 2020
© to 10.10.10.8 Nokia Confidential
path-computation-method local-cspf
primary "loose"
exit
no shutdown

show router rsvp session 

A:R5# show router rsvp session

==============================================================================
RSVP Sessions
==============================================================================
RSVP Session Name
From To Tunnel ID LSP ID State
------------------------------------------------------------------------------
lsp-toR5::to-R5-strict
10.10.10.4 10.10.10.5 1 10752 Up

lsp-toR5::to-R5-loose
10.10.10.3 10.10.10.5 2 62464 Up

lsp-toR8::loose
10.10.10.5 10.10.10.8 1 56320 Up

lsp-toR5::loose
10.10.10.8 10.10.10.5 1 60928 Up

------------------------------------------------------------------------------
Sessions : 4
==============================================================================

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 8
Epipe Transport
Epipe Tunnel
Transport Verification
Tunnel Verification[cont.]
[cont.]
show router rsvp session lsp-name <lsp name> detail 
Switch to notes view!
A:R5# show router rsvp session lsp-name "lsp-toR8::loose" detail

==============================================================================
RSVP Sessions (Detailed)
==============================================================================
------------------------------------------------------------------------------
LSP : lsp-toR8::loose
------------------------------------------------------------------------------
From : 10.10.10.5 To : 10.10.10.8
Tunnel ID : 1 LSP ID : 56320
Style : SE State : Up
Session Type : Originate
In Interface : n/a Out Interface : 1/1/4
In IF Name : n/a
Out IF Name : toR1
In Label : n/a Out Label : 524265
Previous
9 Nokia 2020 Hop
© : n/a Next
Nokia Confidential Hop : 10.1.5.1
Hops :
<< skip >>

The egress Transport Label used by R5 to reach R8 is 524265. Similarly, the egress Transport
Label used by R8 to reach R5 is 524264.

A:R8# show router rsvp session lsp-name "lsp-toR5::loose" detail

==============================================================================
RSVP Sessions (Detailed)
==============================================================================
------------------------------------------------------------------------------
LSP : lsp-toR5::loose
------------------------------------------------------------------------------
From : 10.10.10.8 To : 10.10.10.5
Tunnel ID : 1 LSP ID : 60928
Style : SE State : Up
Session Type : Originate
In Interface : n/a Out Interface : 1/1/4
In IF Name : n/a
Out IF Name : toR4
In Label : n/a Out Label : 524264
Previous Hop : n/a Next Hop : 10.4.8.4
Hops :
<< skip >>

Note that Transport Labels are swapped (i.e., change) hop-by-hop until it reaches the
destination PE where there destination PE will pop the Transport Label (by default, SROS
disables penultimate hop popping).

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 9
Epipe Transport
Epipe Tunnel
Transport Verification
Tunnel Verification[cont.]
[cont.]
While Transport Tunnel Label is swapped or changed during transit, Service Tunnel’s Label does not
change as ittoisnotes
Switch used to identify the endpoint’s service.
view!
show service sdp 
SDP 208 uses RSVP-TE to signal the Transport Tunnel and TLDP to signal the Service Tunnel.

A:R5# show service sdp

============================================================================
Services: Service Destination Points
============================================================================
SdpId AdmMTU OprMTU Far End Adm Opr Del LSP Sig
----------------------------------------------------------------------------
106 0 9190 10.10.10.6 Up Up MPLS L TLDP
208 0 9190 10.10.10.8 Up Up MPLS R TLDP
307 0 9170 10.10.10.7 Up Up GRE n/a TLDP

A:R5# show service id 58 labels

10Nokia 2020
© Nokia Confidential
==============================================================================
Martini Service Labels
==============================================================================
Svc Id Sdp Binding Type I.Lbl E.Lbl
------------------------------------------------------------------------------
58 208:58 Spok 524268 524268
------------------------------------------------------------------------------
Number of Bound SDPs : 1
------------------------------------------------------------------------------

A:R8# show service id 58 labels

==============================================================================
Martini Service Labels
==============================================================================
Svc Id Sdp Binding Type I.Lbl E.Lbl
------------------------------------------------------------------------------
58 205:58 Spok 524268 524268
------------------------------------------------------------------------------
Number of Bound SDPs : 1
------------------------------------------------------------------------------

show service id 67 labels  (for R6 and R7)

R5 has 3 SDPs but only SDP 208 established by RSVP-TE is being used. The Ingress and Egress Labels
are the Service Labels that should match the other end (e.g., R8). Note again that Service Labels do not
change during transit.

A:R5# show service service-using

==============================================================================
Services
==============================================================================
ServiceId Type Adm Opr CustomerId Service Name
------------------------------------------------------------------------------
58 Epipe Up Up 100
2147483648 IES Up Down 1 _tmnx_InternalIesService
2147483649 intVpls Up Down 1 _tmnx_InternalVplsService

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 10
Epipe Service
Epipe Tunnel
Service Verification
Tunnel Verification
show service id 58 base  (for R5 and R8)
show service
Switch id 67 base 
to notes view! (for R6 and R7)

A:R5# show service id 58 base

==============================================================================
Service Basic Information
==============================================================================
Service Id : 58 Vpn Id : 0
Service Type : Epipe
MACSec enabled : no
Name : 58
Description : (Not Specified)
Customer Id : 100 Creation Origin : manual
Last Status Change: 06/25/2020 10:49:43
Last Mgmt Change : 06/25/2020 10:49:02
Test Service : No
Admin State : Up Oper State : Up
MTU : 1514
Vc ©11
Switching
Nokia 2020 : False Nokia Confidential

SAP Count : 1 SDP Bind Count : 1

Per Svc Hashing : Disabled
Vxlan Src Tep Ip : N/A
Force QTag Fwd : Disabled
Oper Group : <none>

------------------------------------------------------------------------------
Service Access & Destination Points
------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
------------------------------------------------------------------------------
sap:1/1/5:0 q-tag 9212 9212 Up Up
sdp:208:58 S(10.10.10.8) Spok 0 9190 Up Up
==============================================================================

Same Service Labels shown as of the command show service sdp-using

show service sap-using 

A:R5# show service sap-using

==============================================================================
Service Access Points
==============================================================================
PortId SvcId Ing. Ing. Egr. Egr. Adm Opr
QoS Fltr QoS Fltr
------------------------------------------------------------------------------
1/1/5:0 58 1 none 1 none Up Up
------------------------------------------------------------------------------
Number of SAPs : 1
------------------------------------------------------------------------------

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 11
OAM Tools
OAM Tools
1. Verify the Epipe service with ping traffic using PCs connected to the SAPs. Each pair of
students
Switch configure
to notes view!their PCs (PC9 to PC12) as follows:
• ifconfig eth1 192.168.1.9/24 (for PC9)
• ifconfig eth1 192.168.1.10/24 (for PC10)
• ifconfig eth1 192.168.1.11/24 (for PC11)
• ifconfig eth1 192.168.1.12/24 (for PC12)

• Verify that PC9 can ping to PC12 through Epipe 58 and PC10 can ping to PC11 through Epipe
67. However, PC9 cannot ping to PC10 even though they are on the same subnet because
the two Epipes are using different Transport and Service Labels.

[root@pc9 ~]# ping 192.168.1.12

PING 192.168.1.12 (192.168.1.12) 56(84) bytes of data.
64 bytes from 192.168.1.12: icmp_seq=1 ttl=64 time=3.89 ms
64 bytes from 192.168.1.12: icmp_seq=2 ttl=64 time=3.17 ms
12Nokia 2020
© Nokia Confidential

[root@pc9 ~]# ping 192.168.1.10

PING 192.168.1.10 (192.168.1.10) 56(84) bytes of data.
From 192.168.1.9 icmp_seq=1 Destination Host Unreachable
From 192.168.1.9 icmp_seq=2 Destination Host Unreachable

2. Verify the operation of your Epipe service using the Service Ping utility.

Note: Nokia’s Service Ping feature provides end-to-end connectivity testing for an individual
service. The Service Ping operates at a higher level than the SDP diagnostics in that it verifies
an individual service and not the collection of services carried within an SDP. The Service Ping is
initiated from a router to verify round-trip connectivity and delay to the far-end of the service.
Nokia’s implementation functions for both GRE and MPLS tunnels and tests the following from
edge-to-edge:
• Tunnel connectivity
• VC label mapping verification
• Service existence
• Service provisioned parameter verification
• Round trip path verification
• Service dynamic configuration verification

R5
- oam svc-ping 10.10.10.8 service 58 
R6
- oam svc-ping 10.10.10.7 service 67 
R7
- oam svc-ping 10.10.10.6 service 67 
R8
- oam svc-ping 10.10.10.5 service 58 

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 12
OAM Tools
OAM [cont.]
Tools [cont.]
oam svc-ping 10.10.10.8 service 58
Switch to notes view!
A:R5# oam svc-ping 10.10.10.8 service 58
Service-ID: 58

Err Info Local Remote

-----------------------------------------------------
Type: EPIPE EPIPE
Admin State: Up Up
Oper State: Up Up
Service-MTU: 1514 1514
Customer ID: 100 100

IP Interface State: Up
Actual IP Addr: 10.10.10.5 10.10.10.8
Expected Peer IP: 10.10.10.8 10.10.10.5

SDP Path Used: No No

SDP-ID:
13Nokia 2020
© 208 205
Nokia Confidential
Admin State: Up Up
Operative State: Up Up
Binding Admin State:Up Up
Binding Oper State: Up Up
Binding VC ID: 58 58
Binding Type: Spoke Spoke
Binding Vc-type: Ether Ether
Binding Vlan-vc-tag:N/A N/A

Egress Label: 524268 524268

Ingress Label: 524268 524268
Egress Label Type: Signaled Signaled
Ingress Label Type: Signaled Signaled

Request Result: Sent - Reply Received

Epipe Service Labels match on both Edge routers.

In this service ping test the actual data path that customer traffic would take through the
service was not used. OAM messages were sent and received over the control plane rather
than the data plane. You can use the local-sdp and remote-sdp parameters to send the oam
packets over the same path as customer traffic.

Note: The svc-ping is a useful OAM feature for a VLL but it does require that the port out to
the CPE is up, i.e. there is something connected to the port such as a PC NIC card, when a
service is first configured this may not be the case and so a VCCV-Ping is a better test of a VLL
when first configured.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 13
OAM Tools
OAM [cont.]
Tools [cont.]
By specifying local-sdp and remote-sdp, the actual SDP data path is used for verifying the
connectivity
Switch to the two
notes endpoints of the Epipe.
view!

A:R5# oam svc-ping 10.10.10.8 service 58 local-sdp remote-sdp

Service-ID: 58

Err Info Local Remote

-----------------------------------------------------
Type: EPIPE EPIPE
Admin State: Up Up
Oper State: Up Up
Service-MTU: 1514 1514
Customer ID: 100 100

IP Interface State: Up
Actual IP Addr: 10.10.10.5 10.10.10.8
Expected Peer IP: 10.10.10.8 10.10.10.5

SDP Path Used:

14Nokia 2020
© Yes Yes
Nokia Confidential

SDP-ID: 208 205

Admin State: Up Up
Operative State: Up Up
Binding Admin State:Up Up
Binding Oper State: Up Up
Binding VC ID: 58 58
Binding Type: Spoke Spoke
Binding Vc-type: Ether Ether
Binding Vlan-vc-tag:N/A N/A

Egress Label: 524268 524268

Ingress Label: 524268 524268
Egress Label Type: Signaled Signaled
Ingress Label Type: Signaled Signaled

Request Result: Sent - Reply Received

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 14
OAM Tools
OAM [cont.]
Tools [cont.]
3. Verify the operation of your Epipe service using the VCCV Ping utility.
Switch to notes view!
Note: Nokia’s VCCV Ping feature provides end-to-end connectivity verification for an individual
Epipe and is used to check connectivity of a VLL in-band. It checks that the destination (target)
PE is the egress for the Layer 2 FEC. It provides a cross-check between the data plane and the
control plane. It is in-band, meaning that the VCCV ping message is sent using the same
encapsulation and along the same path as user packets in that VLL. This is equivalent to the
LSP ping for a VLL service. VCCV ping reuses an LSP ping message format and can be used to
test a VLL configured over an MPLS and GRE SDP. VCCV creates an IP control channel within
the Epipe between R5/R8 or R6/R7. Destination router for the Epipe should be able to
distinguish, on the receive side, VCCV control messages from user packets on that VLL. 7750
SR uses the router alert label immediately above the VC label to identify the VCCV-ping
message. This method has a drawback that if ECMP is applied to the outer LSP label, such as
the transport label, the VCCV message will not follow the same path as the user packets. When
sending the label mapping message for the VLL, routers include an optional VCCV TLV in the
15Nokia 2020
© Nokia Confidential
PW FEC interface parameter field. The TLV indicates that the control channel will make use of
the router alert label method.

R5
- oam vccv-ping 208:58 reply-mode ip-routed 
R6
- oam vccv-ping 207:67 reply-mode ip-routed 
R7
- oam vccv-ping 206:67 reply-mode ip-routed 
R8
- oam vccv-ping 205:58 reply-mode ip-routed 

A:R5# oam vccv-ping 208:58 reply-mode ip-routed

VCCV-PING 208:58 88 bytes MPLS payload
Seq=1, send from intf toR1 to NH 10.1.5.1
send from lsp lsp-toR8
reply from 10.10.10.8 via IP
udp-data-len=32 rtt=6.02ms rc=3 (EgressRtr)

---- VCCV PING 208:58 Statistics ----

1 packets sent, 1 packets received, 0.00% packet loss
round-trip min = 6.02ms, avg = 6.02ms, max = 6.02ms, stddev = 0.000ms

A:R5# oam vccv-trace 208:58 reply-mode ip-routed

VCCV-TRACE 208:58 with 88 bytes of MPLS payload
1 10.10.10.8 rtt=5.95ms rc=3(EgressRtr)

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 15
 VPLS

16Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
------------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 16
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y).

Initial rollback config file’s comment (X) – Final-Epipe.

• /admin rollback revert X

Final rollback config file’s comment (Y) – Final-Epipe, VPLS.

To compare current config with the final lab answer:
• /admin rollback compare active-cfg to Y

17Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 17
 VPLS Configuration
VPLS Configuration
VPLS services offer Ethernet switching. Normally this would require STP as loop prevention
mechanism,
Switch to but this
notes protocol is not efficient (links will be blocked).
view!
The Nokia’s implementation allows an alternative to STP: meshed bindings.
If switching instances are linked with Mesh-SDP bindings, the traffic cannot re-enter the
network and create a loop.
Take a look at the different behavior below to see the difference between SAP, Spoke-binding
and Mesh-binding.

MESH SDP
MESH SDP MESH SDP
SAP

MESH SDP
VPLS 300
MESH SDP MESH SDP
VPLS 300 VPLS 300

SAP SPOKE SDP

SAP SPOKE SDP
18Nokia 2020
© SPOKE SDP SAP Nokia Confidential

PC
SAP- floods to Spoke SDP- Floods to Mesh SDP- Floods to SAPs
everybody everybody and spoke SPDs only

The problem with mesh-binding is that all instances must be connected through an SDP with
all other switching instances. In large VPLS services this could become a scaling problem.
Combining Spoke-bindings between smaller full-mesh networks is the solution (i.e., hierarchical
VPLS).
For redundancy more Spoke binding can be set up, but then STP or managed VPLS is required
to prevent L2 looping.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 18
VPLS Configuration
VPLS [cont.]
Configuration [cont.]
1. Each pair of students login to their Edge routers (R5 to R8) and create VPLS 600 (customer
100) with
Switch fully meshed
to notes view! SDP to each other Edge routers.
• Shutdown and remove sap 1/1/5:0 from Epipe 58 and 67 and re-use the sap for VPLS 600.
STP not required with mesh-sdp
and thus it is shutdown
A:R5# configure service A:R6# configure service
A:R5>config>service# info A:R6>config>service# info
------------------------------------ -------------------------------------
vpls 600 name "600" customer vpls 600 name "600" customer
100 create 100 create
stp stp
shutdown shutdown
exit exit
sap 1/1/5:0 create sap 1/1/5:0 create
no shutdown no shutdown
exit exit
mesh-sdp 106:600 create mesh-sdp 105:600 create
19Nokia 2020
© no shutdown Nokia Confidential no shutdown
exit exit
mesh-sdp 208:600 create mesh-sdp 207:600 create
no shutdown no shutdown
exit exit
mesh-sdp 307:600 create mesh-sdp 308:600 create
no shutdown no shutdown
exit exit
no shutdown no shutdown
exit exit

A:R7>config>service# info A:R8# configure service

------------------------------------- A:R8>config>service# info
vpls 600 name "600" customer -------------------------------------
100 create vpls 600 name "600" customer
stp 100 create
shutdown stp
exit shutdown
sap 1/1/5:0 create exit
no shutdown sap 1/1/5:0 create
exit no shutdown
mesh-sdp 108:600 create exit
no shutdown mesh-sdp 107:600 create
exit no shutdown
mesh-sdp 206:600 create exit
no shutdown mesh-sdp 205:600 create
exit no shutdown
mesh-sdp 305:600 create exit
no shutdown mesh-sdp 306:600 create
exit no shutdown
no shutdown exit
exit no shutdown
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 19
VPLS Verification
VPLS Verification
1. Verify the VPLS. What are the Service labels used to reach the other PEs?
Switch to notes view!
• The following shows the service labels and Tunnels that are used by R5 to connect to all
remote Edge routers to form the VPLS.

A:R5# show service id 600 labels

==============================================================================
Martini Service Labels
==============================================================================
Svc Id Sdp Binding Type I.Lbl E.Lbl
------------------------------------------------------------------------------
600 106:600 Mesh 524267 524267
600 208:600 Mesh 524266 524266
600 307:600 Mesh 524265 524265

A:R6#
20Nokia show
© 2020 service id 600 labels Nokia Confidential

==============================================================================
Martini Service Labels
==============================================================================
Svc Id Sdp Binding Type I.Lbl E.Lbl
------------------------------------------------------------------------------
600 105:600 Mesh 524267 524267
600 207:600 Mesh 524266 524266
600 308:600 Mesh 524265 524265

A:R7# show service id 600 labels

==============================================================================
Martini Service Labels
==============================================================================
Svc Id Sdp Binding Type I.Lbl E.Lbl
------------------------------------------------------------------------------
600 108:600 Mesh 524267 524267
600 206:600 Mesh 524266 524266
600 305:600 Mesh 524265 524265

A:R8# show service id 600 labels

==============================================================================
Martini Service Labels
==============================================================================
Svc Id Sdp Binding Type I.Lbl E.Lbl
------------------------------------------------------------------------------
600 107:600 Mesh 524267 524267
600 205:600 Mesh 524266 524266
600 306:600 Mesh 524265 524265

• Each Edge router has a similar Service Labels/Tunnels setup to the rest of the Edge routers
to form the VPLS.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 20
VPLS Verification
VPLS [cont.]
Verification [cont.]
2. Show the VPLS service details using the command show service id 600 all 
Switch to notes view!
A:R8# show service id 600 base

==============================================================================
Service Basic Information
==============================================================================
Service Id : 600 Vpn Id : 0
Service Type : VPLS
MACSec enabled : no
Name : 600
Description : (Not Specified)
Customer Id : 100 Creation Origin : manual
Last Status Change: 06/25/2020 14:55:30
Last Mgmt Change : 06/25/2020 14:55:30
Etree Mode : Disabled
Admin State : Up Oper State : Up
MTU : 1514
SAP©21Nokia
Count 2020 : 1 SDP Bind Count
Nokia Confidential : 3
Snd Flush on Fail : Disabled Host Conn Verify : Disabled
SHCV pol IPv4 : None
Propagate MacFlush: Disabled Per Svc Hashing : Disabled
Allow IP Intf Bind: Disabled
Fwd-IPv4-Mcast-To*: Disabled Fwd-IPv6-Mcast-To*: Disabled
Mcast IPv6 scope : mac-based
Def. Gateway IP : None
Def. Gateway MAC : None
Temp Flood Time : Disabled Temp Flood : Inactive
Temp Flood Chg Cnt: 0
SPI load-balance : Disabled
TEID load-balance : Disabled
Src Tep IP : N/A
Vxlan ECMP : Disabled
MPLS ECMP : Disabled
VSD Domain : <none>

------------------------------------------------------------------------------
Service Access & Destination Points
------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
------------------------------------------------------------------------------
sap:1/1/5:0 q-tag 9212 9212 Up Up
sdp:107:600 M(10.10.10.7) Mesh 0 9190 Up Up
sdp:205:600 M(10.10.10.5) Mesh 0 9190 Up Up
sdp:306:600 M(10.10.10.6) Mesh 0 9170 Up Up
==============================================================================

All mesh-sdp and SAP are UP.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 21
VPLS Verification
VPLS [cont.]
Verification [cont.]
2. In the previous Epipe lab, two unrelated Epipes are created and even thought the PCs connected
to the Epipes are on the same IP subnets of 192.168.1.0/24, only PCs on the two ends of a
Switch
common toEpipe
notescan
view!
reach each other. In VPLS 600, all PCs should be able to reach each others.

[root@pc9 ~]# ping 192.168.1.10

PING 192.168.1.10 (192.168.1.10) 56(84) bytes of data.
64 bytes from 192.168.1.10: icmp_seq=1 ttl=64 time=3.58 ms
64 bytes from 192.168.1.10: icmp_seq=2 ttl=64 time=2.46 ms

[root@pc9 ~]# ping 192.168.1.11

PING 192.168.1.11 (192.168.1.11) 56(84) bytes of data.
64 bytes from 192.168.1.11: icmp_seq=1 ttl=64 time=2.92 ms
64 bytes from 192.168.1.11: icmp_seq=2 ttl=64 time=2.70 ms

[root@pc9 ~]# ping 192.168.1.12

PING 192.168.1.12 (192.168.1.12) 56(84) bytes of data.
64 bytes from 192.168.1.12: icmp_seq=1 ttl=64 time=3.71 ms
64 bytes from 192.168.1.12: icmp_seq=2 ttl=64 time=2.91 ms
22Nokia 2020
© Nokia Confidential

4. Verify the forwarding database. What are the age timers? How can you verify the age timer per
mac entry?
• show service fdb-mac 
• show service fdb-mac expiry 

A:R5# show service fdb-mac

==============================================================================
Service Forwarding Database
==============================================================================
ServId MAC Source-Identifier Type/Age Last Change
------------------------------------------------------------------------------
600 02:00:a8:00:c9:01 sap:1/1/5:0 L/0 06/25/20 15:11:23
600 02:00:a8:00:ca:01 sdp:106:600 L/30 06/25/20 15:08:04
600 02:00:a8:00:cb:01 sdp:307:600 L/30 06/25/20 15:10:15
600 02:00:a8:00:cc:01 sdp:208:600 L/0 06/25/20 15:11:47
------------------------------------------------------------------------------
No. of Entries: 4
Legend: L=Learned O=Oam P=Protected-MAC C=Conditional S=Static Lf=Leaf

MAC addresses learnt from SAP expires earlier than MAC addresses learnt from remote VPLS
endpoints and it takes more resources (e.g.., time, CPM cycles) to learnt remote MAC addresses.

A:R5# show service fdb-mac expiry

==============================================================================
Service Forwarding Database
==============================================================================
ServId MAC Source-Identifier Type/Expiry Last Change
------------------------------------------------------------------------------
600 02:00:a8:00:c9:01 sap:1/1/5:0 L/240 06/25/20 15:11:23
600 02:00:a8:00:ca:01 sdp:106:600 L/810 06/25/20 15:08:04
600 02:00:a8:00:cb:01 sdp:307:600 L/810 06/25/20 15:10:15
600 02:00:a8:00:cc:01 sdp:208:600 L/840 06/25/20 15:11:47
------------------------------------------------------------------------------
No. of Entries: 4

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 22
 VPRN

23Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
------------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 23
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y).

Initial rollback config file’s comment (X) – Final-Epipe, VPLS.

• /admin rollback revert X

Final rollback config file’s comment (Y) – Final-Epipe, VPLS, VPRN.

To compare current config with the final lab answer:
• /admin rollback compare active-cfg to Y

24Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 24
VPRN Configuration
VPRN Configuration
VPRN configure comprises the following steps:
• MP-BGP
Switch toamong all routers with VPRN for distributing VPN ID.
notes view!
- VPN ID is same as Service Label used in Epipe and VPLS but Service Labels are
distributed via TLDP and VPN ID is distributed via MP-BGP.
• VPRN service provisioning on the routers.

Since VPRN is a L3 routing service, each PC (PC9 to PC12) should have different IP subnets.
Change the IP addresses of PC9 to PC12 to different subnets to verify VPRN 700’s layer 3
routing capability as follows:
• PC9
- ifconfig eth1 192.168.9.2/24
- ip route add 192.168.0.0/16 via 192.168.9.1 dev eth1
• PC10
- ifconfig eth1 192.168.10.2/24
- ip route add 192.168.0.0/16 via 192.168.10.1 dev eth1
25Nokia 2020
© Nokia Confidential
• PC11
- ifconfig eth1 192.168.11.2/24
- ip route add 192.168.0.0/16 via 192.168.11.1 dev eth1
• PC12
- ifconfig eth1 192.168.12.2/24
- ip route add 192.168.0.0/16 via 192.168.12.1 dev eth1

Check with instructor, if facing any issue in configuring static route.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 25
VPRN MP-BGP
VPRN Configuration
MP-BGP Configuration
1. Students login to their Edge routers (R5 to R8) and setup MP-iBGP. Verify MP-iBGP using
show to
Switch router bgp summary. Ensure all BGP neighbors are UP.
notes view!

A:R5>config>router>bgp# info A:R6>config>router>bgp# info

------------------------------------- -------------------------------------
group "mp-ibgp" group "mp-ibgp"
family vpn-ipv4 family vpn-ipv4
peer-as 65100 peer-as 65100
neighbor 10.10.10.6 neighbor 10.10.10.5
exit exit
neighbor 10.10.10.7 neighbor 10.10.10.7
exit exit
neighbor 10.10.10.8 neighbor 10.10.10.8
exit exit
exit exit
no shutdown no shutdown

A:R7>config>router>bgp#
26Nokia 2020
© info A:R8# configure router bgp
Nokia Confidential

------------------------------------- -------------------------------------
group "mp-ibgp" group "mp-ibgp"
family vpn-ipv4 family vpn-ipv4
peer-as 65100 peer-as 65100
neighbor 10.10.10.5 neighbor 10.10.10.5
exit exit
neighbor 10.10.10.6 neighbor 10.10.10.6
exit exit
neighbor 10.10.10.8 neighbor 10.10.10.7
exit exit
exit exit
no shutdown no shutdown

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 26
VPRN MP-BGP
VPRN Verification
MP-BGP Verification
Ensure that each Edge router has 3 vpn-ipv4 BGP neighbors.
Switch to notes view!
A:R5# show router bgp summary
==============================================================================
BGP Router ID:10.10.10.5 AS:65100 Local AS:65100
==============================================================================
BGP Admin State : Up BGP Oper State : Up
Total Peer Groups : 1 Total Peers : 3
Total VPN Peer Groups : 0 Total VPN Peers : 0
Total BGP Paths : 36 Total Path Memory : 9504

<< skip >>

==============================================================================
BGP Summary
==============================================================================
Legend : D - Dynamic Neighbor
==============================================================================
Neighbor
27Nokia 2020
© Nokia Confidential
Description
AS PktRcvd InQ Up/Down State|Rcv/Act/Sent (Addr Family)
PktSent OutQ
------------------------------------------------------------------------------
10.10.10.6
65100 31 0 00h14m08s 0/0/0 (VpnIPv4)
32 0
10.10.10.7
65100 30 0 00h13m59s 0/0/0 (VpnIPv4)
31 0
10.10.10.8
65100 30 0 00h13m50s 0/0/0 (VpnIPv4)
32 0

Note that this is 0/0/0 routes for Rec/Act/Sent because we have yet to set up VPRN 700 to
use MP-BGP for VPN ID distribution.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 27
VPRN FullFull
VPRN Mesh Service
Mesh Configuration
Service Configuration
1. Configure VPRN 700 on each Edge router as follows:
Switch to notes view!
In the VPLS lab, all Edge routers (R5 to R8) have VPLS 600 and thus it forms a virtual L2 WAN
LAN for PC9 to PC12 on the same IP subnet of 192.168.1.x/24. In this lab, a VPRN 700
(customer 100) is create among all Edge routers with the following criteria:
• vrf-target = target:65100:700
• route-distinguisher = 65100:700
• SAP 1/1/5:0
- Remove the sap 1/1/5:0 from VPLS 600 or Epipe service and use it for VPRN 700
• auto-bind-tunnel resolution any
- Note: In VRPN, a shortcut exists to alleviate the creation of SDP-bindings manually.
The auto-bind command creates fully meshed SDP’s in one command. When this
option is used, there is no need to explicitly specify the SDP’s as in the previous
step.
28Nokia 2020
© Nokia Confidential
MP-iBGP supporting vpn-ipv4 family is enabled among the Edge routers for exchange vpn-ipv4
routes in the previous lab.

A:R5>config>service# info A:R6>config>service# info

------------------------------------- -------------------------------------
<< skip >> << skip >>
vprn 700 customer 100 create vprn 700 customer 100 create
autonomous-system 65100 autonomous-system 65100
route-distinguisher 65100:700 route-distinguisher 65100:700
auto-bind-tunnel auto-bind-tunnel
resolution any resolution any
exit exit
vrf-target target:65100:700 vrf-target target:65100:700
interface "toPC9" create interface "toPC10" create
address 192.168.9.1/24 address 192.168.10.1/24
sap 1/1/5:0 create sap 1/1/5:0 create
exit exit
exit exit
no shutdown no shutdown
exit exit

A:R7>config>service# info A:R8>config>service# info

------------------------------------- -------------------------------------
<< skip >> << skip >>
vprn 700 customer 100 create vprn 700 customer 100 create
autonomous-system 65100 autonomous-system 65100
route-distinguisher 65100:700 route-distinguisher 65100:700
auto-bind-tunnel auto-bind-tunnel
resolution any resolution any
exit exit
vrf-target target:65100:700 vrf-target target:65100:700
interface "toPC11" create interface "toPC12" create
address 192.168.11.1/24 address 192.168.12.1/24
sap 1/1/5:0 create sap 1/1/5:0 create
exit exit
exit exit
no shutdown no shutdown
exit exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 28
VPRN FullFull
VPRN Mesh Service
Mesh Verification
Service Verification
2. Verify VPRN 700 with the command show service id 700 base
Switch to notes view!
A:R5# show service id 700 base

==============================================================================
Service Basic Information
==============================================================================
Service Id : 700 Vpn Id : 0
Service Type : VPRN
MACSec enabled : no
Name : 700
Description : (Not Specified)
Customer Id : 100 Creation Origin : manual
Last Status Change: 06/26/2020 08:05:01
Last Mgmt Change : 06/26/2020 08:05:01
Admin State : Up Oper State : Up

Router Oper State : Up

Route
29Nokia Dist.
© 2020 : 65100:700 VPRN Type
Nokia Confidential : regular
Oper Route Dist : 65100:700
Oper RD Type : configured
AS Number : 65100 Router Id : 10.10.10.5
ECMP : Enabled ECMP Max Routes : 1
Max IPv4 Routes : No Limit

Auto Bind Tunnel

Resolution : any
Weighted ECMP : Disabled ECMP Max Routes : 1

Max IPv6 Routes : No Limit

Ignore NH Metric : Disabled
Hash Label : Disabled
Entropy Label : Disabled
Vrf Target : target:65100:700
Vrf Import : None
Vrf Export : None
MVPN Vrf Target : None
MVPN Vrf Import : None
MVPN Vrf Export : None
Car. Sup C-VPN : Disabled
Label mode : vrf
BGP VPN Backup : Disabled
BGP Export Inactv : Disabled
LOG all events : Disabled

SAP Count : 1 SDP Bind Count : 0

VSD Domain : <none>

------------------------------------------------------------------------------
Service Access & Destination Points
------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
------------------------------------------------------------------------------
sap:1/1/5:0 q-tag 9212 9212 Up Up
==============================================================================

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 29
VPRN FullFull
VPRN Mesh Service
Mesh Verification
Service Verification[cont.]
[cont.]
Verify VPRN 700 routes with the command show router 700 route-table

Switch to notes view!

A:R5# show router 700 route-table
==============================================================================
Route Table (Service: 700)
==============================================================================
Dest Prefix[Flags] Type Proto Age Pref
Next Hop[Interface Name] Metric
------------------------------------------------------------------------------
192.168.9.0/24 Local Local 00h27m31s 0
toPC9 0
192.168.10.0/24 Remote BGP VPN 00h27m07s 170
10.10.10.6 (tunneled) LDP 0
192.168.11.0/24 Remote BGP VPN 00h26m53s 170
10.10.10.7 (tunneled) GRE 0
192.168.12.0/24 Remote BGP VPN 00h26m26s 170
10.10.10.8 (tunneled:RSVP:1) RSVP 0
------------------------------------------------------------------------------
No. of Routes: 4
30Nokia 2020
© Nokia Confidential

In the lab, each Edge router has a SDP to each remote Edge routers using LDP, RSVP-TE or GRE transport tunnel
signaling protocol.

A:R8# show router 700 route-table

==============================================================================
Route Table (Service: 700)
==============================================================================
Dest Prefix[Flags] Type Proto Age Pref
Next Hop[Interface Name] Metric
------------------------------------------------------------------------------
192.168.9.0/24 Remote BGP VPN 00h27m49s 170
10.10.10.5 (tunneled:RSVP:1) 0
192.168.10.0/24 Remote BGP VPN 00h27m36s 170
10.10.10.6 (tunneled) 0
192.168.11.0/24 Remote BGP VPN 00h27m43s 170
10.10.10.7 (tunneled) 0
192.168.12.0/24 Local Local 00h27m30s 0
toPC2 0
------------------------------------------------------------------------------
No. of Routes: 4

3. End-to-End VRPN verification. Each group of students login to their PCs (PC9 to PC12) and ping the other PCs
via VPRN 700.

[root@pc9 ~]# ping 192.168.10.2

PING 192.168.10.2 (192.168.10.2) 56(84) bytes of data.
64 bytes from 192.168.10.2: icmp_seq=1 ttl=62 time=2.97 ms
64 bytes from 192.168.10.2: icmp_seq=2 ttl=62 time=2.57 ms
[root@pc9 ~]# ping 192.168.11.2
PING 192.168.11.2 (192.168.11.2) 56(84) bytes of data.
64 bytes from 192.168.11.2: icmp_seq=1 ttl=62 time=5.97 ms
64 bytes from 192.168.11.2: icmp_seq=2 ttl=62 time=2.26 ms
[root@pc9 ~]# ping 192.168.12.2
PING 192.168.12.2 (192.168.12.2) 56(84) bytes of data.
64 bytes from 192.168.12.2: icmp_seq=1 ttl=62 time=4.67 ms
64 bytes from 192.168.12.2: icmp_seq=2 ttl=62 time=3.56 ms

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 30
VPRN FullFull
VPRN Mesh Service
Mesh Verification
Service Verification[cont.]
[cont.]
End-to-End VRPN verification. Each group of students login to their PCs (PC9 to PC12) and ping the
other PCs via VPRN 700.
Switch to notes view!

A:R5# oam vprn-ping 700 source 192.168.9.2 destination 192.168.11.2

Seq Rcvd-on Reply-Path Size RTT

----------------------------------------------------------------------------
[Send request Seq. 1.]
1 sap:1/1/5:0 In-Band 84 2.23ms
Node-Id 10.10.10.7
----------------------------------------------------------------------------

A:R5# oam vprn-ping 700 source 192.168.9.2 destination 192.168.12.2

Seq Rcvd-on Reply-Path Size RTT

----------------------------------------------------------------------------
[Send request Seq. 1.]
1 ©31Nokia
sap:1/1/5:0
2020 Nokia Confidential
In-Band 84 3.42ms
Node-Id 10.10.10.8
----------------------------------------------------------------------------

A:R5# oam vprn-trace 700 source 192.168.9.2 destination 192.168.12.2

TTL Seq Rcvd-on Reply-Path RTT

----------------------------------------------------------------------------
[Send request TTL: 1, Seq. 1.]
1 1 cpm In-Band 5.49ms
Node-Id 10.10.10.8
Requestor 10.10.10.5
Route: 192.168.12.0/24
Vpn Label: 524264 Metrics 40 Pref 170 Owner bgpVpn
Next Hops: [1] rsvp tunnel
Route Targets: [1]: target:65100:700
Responder 10.10.10.8
Route: 192.168.12.0/24
Vpn Label: 0 Metrics 0 Pref 0 Owner local
Next Hops: [1] ifIdx 4 nextHopIp 192.168.12.2

[Send request TTL: 2, Seq. 1.]

2 1 sap:1/1/5:0 In-Band 5.29ms
Node-Id 10.10.10.8
Requestor 10.10.10.5
Route: 192.168.12.0/24
Vpn Label: 524264 Metrics 40 Pref 170 Owner bgpVpn
Next Hops: [1] rsvp tunnel
Route Targets: [1]: target:65100:700
Responder 10.10.10.8
Route: 192.168.12.0/24
Vpn Label: 0 Metrics 0 Pref 0 Owner local
Next Hops: [1] ifIdx 4 nextHopIp 192.168.12.2

----------------------------------------------------------------------------

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 31
VPRN FullFull
VPRN Mesh Service
Mesh Verification
Service Verification[cont.]
[cont.]

A:R7# oam vprn-trace 700 source 192.168.11.2 destination 192.168.12.2

Switch to notes view!
TTL Seq Rcvd-on Reply-Path RTT
----------------------------------------------------------------------------
[Send request TTL: 1, Seq. 1.]
1 1 cpm In-Band 5.40ms
Node-Id 10.10.10.8
Requestor 10.10.10.7
Route: 192.168.12.0/24
Vpn Label: 524264 Metrics 30 Pref 170 Owner bgpVpn
Next Hops: [1] ldp tunnel
Route Targets: [1]: target:65100:700
Responder 10.10.10.8
Route: 192.168.12.0/24
Vpn Label: 0 Metrics 0 Pref 0 Owner local
Next Hops: [1] ifIdx 4 nextHopIp 192.168.12.2

[Send request TTL: 2, Seq. 1.]

2 1 sap:1/1/5:0 In-Band 4.74ms
32Nokia 2020
© Nokia Confidential
Node-Id 10.10.10.8
Requestor 10.10.10.7
Route: 192.168.12.0/24
Vpn Label: 524264 Metrics 30 Pref 170 Owner bgpVpn
Next Hops: [1] ldp tunnel
Route Targets: [1]: target:65100:700
Responder 10.10.10.8
Route: 192.168.12.0/24
Vpn Label: 0 Metrics 0 Pref 0 Owner local
Next Hops: [1] ifIdx 4 nextHopIp 192.168.12.2

----------------------------------------------------------------------------

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 32
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y).

Initial rollback config file’s comment (X) – Final-Epipe, VPLS, VPRN.

• /admin rollback revert X

Final rollback config file’s comment (Y) – Final-VPRN import-export policies.

To compare current config with the final lab answer:
• /admin rollback compare active-cfg to Y

33Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 33
VPRN Import and Export Policies

In the previous VPRN full mesh lab exercise, all VPRN 700 in Edge routers R5 to R8 use the
same VRF target, vrf-target target:65100:700 and thus all the VPRN routes such as
192.168.x.x/24 are exchanged and reachable by all VPRN 700.

In this lab exercise, we will maintain reachability of 192.168.x.x/24 subnet in VPRN among all
Edge routers R5 to R8 but at the same time, define the following two subnets are reachable
as follows:
• R5 (172.16.58.5/24) and R8 (172.16.58.8/24)
• R6 (172.16.67.6/24) and R7 (172.16.67.7/24)

34Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 34
VPRN Import and Export Policies [cont.]

Each pair of students modify VPRN 700 of their Edge router as follows:
• Develop a policy-statement, export_vpn_extranet to tag prefix with community:
- 192.168.x.0/24 exact - target:65100:700
- 172.16.x.y/24 longer – target:65100:xy
• Develop a policy-statement, import_vpn_extranet to import VPRN 700 and Extranet routes
• Replace VPRN 700’s VRF target, vrf-target target:65100:700 by:
- vrf-import import_vpn_extranet
- vrf-export export_vpn_extranet

Verify that VPRN 700 in R5 to R8 can still reach the subnet 192.168.x.y/24 but for subnet
172.16.xy.z, only the corresponding pair of Edge routers can reach the extranet subnet.

35Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 35
VRF Target Policy Statement (R5)

A:R5# /configure router policy-options

A:R5>config>router>policy-options# info
----------------------------------------------
prefix-list "vpn700"
prefix 192.168.9.0/24 exact
exit
prefix-list "extranet"
prefix 172.16.58.0/24 longer
exit
community "vpn700" members "target:65100:700"
community "extranet" members "target:65100:58"
policy-statement "export_vpn_extranet"
entry 10
from
prefix-list "vpn700"
exit
action accept
community add "vpn700"
exit
exit
entry 20
from
prefix-list "extranet"
exit
action accept
community add "extranet"
exit
exit
default-action drop
exit
exit
policy-statement "import_vpn_extranet"
entry 10
from
community "vpn700"
exit
action accept
exit
exit
entry 20
from
community "extranet"
exit
action accept
exit
exit
default-action drop
exit
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 36
VRF Target Policy Statement (R8)

A:R8# /configure router policy-options

A:R8>config>router>policy-options# info
----------------------------------------------
prefix-list "vpn700"
prefix 192.168.12.0/24 exact
exit
prefix-list "extranet"
prefix 172.16.58.0/24 longer
exit
community "vpn700" members "target:65100:700"
community "extranet" members "target:65100:58"
policy-statement "export_vpn_extranet"
entry 10
from
prefix-list "vpn700"
exit
action accept
community add "vpn700"
exit
exit
entry 20
from
prefix-list "extranet"
exit
action accept
community add "extranet"
exit
exit
default-action drop
exit
exit
policy-statement "import_vpn_extranet"
entry 10
from
community "vpn700"
exit
action accept
exit
exit
entry 20
from
community "extranet"
exit
action accept
exit
exit
default-action drop
exit
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 37
VRF Target Policy Statement (R6)

A:R6# configure router policy-options

A:R6>config>router>policy-options# info
----------------------------------------------
prefix-list "vpn700"
prefix 192.168.10.0/24 exact
exit
prefix-list "extranet"
prefix 172.16.67.0/24 longer
exit
community "vpn700" members "target:65100:700"
community "extranet" members "target:65100:67"
policy-statement "export_vpn_extranet"
entry 10
from
prefix-list "vpn700"
exit
action accept
community add "vpn700"
exit
exit
entry 20
from
prefix-list "extranet"
exit
action accept
community add "extranet"
exit
exit
default-action drop
exit
exit
policy-statement "import_vpn_extranet"
entry 10
from
community "vpn700"
exit
action accept
exit
exit
entry 20
from
community "extranet"
exit
action accept
exit
exit
default-action drop
exit
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 38
VRF Target Policy Statement (R7)

A:R7# configure router policy-options

A:R7>config>router>policy-options# info
----------------------------------------------
prefix-list "vpn700"
prefix 192.168.11.0/24 exact
exit
prefix-list "extranet"
prefix 172.16.67.0/24 longer
exit
community "vpn700" members "target:65100:700"
community "extranet" members "target:65100:67"
policy-statement "export_vpn_extranet"
entry 10
from
prefix-list "vpn700"
exit
action accept
community add "vpn700"
exit
exit
entry 20
from
prefix-list "extranet"
exit
action accept
community add "extranet"
exit
exit
default-action drop
exit
exit
policy-statement "import_vpn_extranet"
entry 10
from
community "vpn700"
exit
action accept
exit
exit
entry 20
from
community "extranet"
exit
action accept
exit
exit
default-action drop
exit
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 39
VPRN 700 (R5 to R8)

R5’s VPRN 700 R8’s VPRN 700

A:R5# configure service vprn 700 A:R8# configure service vprn 700
A:R5>config>service>vprn# info A:R8>config>service>vprn# info
---------------------------------------------- ----------------------------------------------
vrf-import "import_vpn_extranet" vrf-import "import_vpn_extranet"
vrf-export "export_vpn_extranet" vrf-export "export_vpn_extranet"
autonomous-system 65100 autonomous-system 65100
route-distinguisher 65100:700 route-distinguisher 65100:700
auto-bind-tunnel auto-bind-tunnel
resolution any resolution any
exit exit
interface "toPC9" create interface "toPC12" create
address 192.168.9.1/24 address 192.168.12.1/24
sap 1/1/5:0 create sap 1/1/5:0 create
exit exit
exit exit
interface "extranet58" create interface "extranet58" create
address 172.16.58.5/24 address 172.16.58.8/24
loopback loopback
exit exit
no shutdown no shutdown

40Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 40
VPRN 700 (R6 to R7)

R6’s VPRN 700 R7’s VPRN 700

A:R6# configure service vprn 700 A:R7# configure service vprn 700
A:R6>config>service>vprn# info A:R7>config>service>vprn# info
---------------------------------------------- ----------------------------------------------
vrf-import "import_vpn_extranet" vrf-import "import_vpn_extranet"
vrf-export "export_vpn_extranet" vrf-export "export_vpn_extranet"
autonomous-system 65100 autonomous-system 65100
route-distinguisher 65100:700 route-distinguisher 65100:700
auto-bind-tunnel auto-bind-tunnel
resolution any resolution any
exit exit
interface "toPC10" create interface "toPC11" create
address 192.168.10.1/24 address 192.168.11.1/24
sap 1/1/5:0 create sap 1/1/5:0 create
exit exit
exit exit
interface "intranet67" create interface "intranet67" create
address 172.16.67.6/24 address 172.16.67.7/24
loopback loopback
exit exit
no shutdown no shutdown

41Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 41
Route Verification

All Edge routers (R5 to R8) have the VPN700 and Extranet routes.

A:R5# show router 700 route-table

===============================================================================
Route Table (Service: 700)
===============================================================================
Dest Prefix[Flags] Type Proto Age Pref
Next Hop[Interface Name] Metric
-------------------------------------------------------------------------------
172.16.58.0/24 Local Local 01h16m22s 0
extranet58 0
172.16.58.8/32 Remote BGP VPN 00h32m19s 170
10.10.10.8 (tunneled:RSVP:1) 40
192.168.9.0/24 Local Local 01h16m15s 0
toPC9 0
192.168.10.0/24 Remote BGP VPN 00h33m42s 170
10.10.10.6 (tunneled) 30
192.168.11.0/24 Remote BGP VPN 00h33m42s 170
10.10.10.7 (tunneled) 30
192.168.12.0/24 Remote BGP VPN 00h33m42s 170
10.10.10.8 (tunneled:RSVP:1) 40
-------------------------------------------------------------------------------

42Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 42
Route Verification [cont.]

Ping to VPRN 700’s subnet 192.168.x.y are OK.

A:R5# ping router 700 192.168.10.2 source 192.168.9.1

PING 192.168.10.2 56 data bytes
64 bytes from 192.168.10.2: icmp_seq=1 ttl=63 time=6.85ms.
64 bytes from 192.168.10.2: icmp_seq=2 ttl=63 time=4.64ms.
64 bytes from 192.168.10.2: icmp_seq=3 ttl=63 time=4.75ms.

A:R5# ping router 700 192.168.11.2 source 192.168.9.1

PING 192.168.11.2 56 data bytes
64 bytes from 192.168.11.2: icmp_seq=1 ttl=63 time=2.11ms.
64 bytes from 192.168.11.2: icmp_seq=2 ttl=63 time=1.69ms.
64 bytes from 192.168.11.2: icmp_seq=3 ttl=63 time=1.85ms.

A:R5# ping router 700 192.168.12.2 source 192.168.9.1

PING 192.168.12.2 56 data bytes
64 bytes from 192.168.12.2: icmp_seq=1 ttl=63 time=3.13ms.
64 bytes from 192.168.12.2: icmp_seq=2 ttl=63 time=2.34ms.
64 bytes from 192.168.12.2: icmp_seq=3 ttl=63 time=2.23ms.
64 bytes from 192.168.12.2: icmp_seq=4 ttl=63 time=2.42ms.

43Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 43
Route Verification [cont.]

Ping Extranet is OK.

A:R5# ping router 700 172.16.58.8 source 172.16.58.5
PING 172.16.58.8 56 data bytes
64 bytes from 172.16.58.8: icmp_seq=1 ttl=64 time=2.52ms.
64 bytes from 172.16.58.8: icmp_seq=2 ttl=64 time=2.14ms.
64 bytes from 172.16.58.8: icmp_seq=3 ttl=64 time=1.91ms.
64 bytes from 172.16.58.8: icmp_seq=4 ttl=64 time=1.87ms.

Ping across Intranet failed as expected.

A:R5# ping router 700 172.16.67.7 source 172.16.58.5
PING 172.16.67.7 56 data bytes
No route to destination. Address: 172.16.67.7, Service: 700
No route to destination. Address: 172.16.67.7, Service: 700
No route to destination. Address: 172.16.67.7, Service: 700
No route to destination. Address: 172.16.67.7, Service: 700.

44Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 44
 Wrap-up
In this module we have covered the following items:
• Perform the following operations:
- Configure an Epipe (VLL) service
- Verify an Epipe
- Configure a VPLS
- Verify a VPLS
- Configure the Virtual Private Network Service (VPRN)
- VPRN verification

• Understand:
- Service Label
- VC ID
- Route Target
- Route Distinguisher
- MP-BGP

45Nokia 2020
© Nokia Confidential

Nokia’s MPLS network service implementation complies to standard RFCs and specifications. For
more information about multi-vendor MPLS network service interop, please refer to
http://clcnetwork.wordpress.com.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 45
46Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M02 Ed0 46
 VPLS BGP-AD

ER00198-V-2000 V0 - S05M03 Ed0

1 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M03 Ed0 1
Learning Objectives
Upon completion of this module, you should be able to:
• Configure and verify MP-BGP with L2-VPN family
• Configure and verify VPLS BGP-AD

2 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M03 Ed0 2
 ToC Slide

Table of Contents

Lab Setup
VPLS using BGP-AD
Wrap-up

3 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M03 Ed0 3
 Lab Setup

4 Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
------------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M03 Ed0 4
Initial Lab Condition

In the core network, to support VPLS using BGP-AD, an IGP protocol such as OSPF or ISIS must be
operational. LDP signaling must be operational to signal transport tunnels between Edge routers.
In this lab, the students will verify:
• All network interfaces on R1-R8 are operational.
• OSPF/ISIS is correctly configured and operational within the network core.
• All IGP adjacencies are operational.
• Ports towards lab PCs are configured as access ports with dot1Q encapsulation.

5 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M03 Ed0 5
 Router System Addresses and PC Interface
10.10.10.5/32 10.10.10.6/32
PC9 3ffe::1:505:505/128 3ffe::1:606:606/128 PC10

10.10.10.1/32 10.10.10.2/32
3ffe::1:101:101/128 3ffe::1:202:202/128

R5 R1 R2
eth1 192.168.1.9/24 R6 eth1 192.168.1.10/24

PC11 R7 R3 R4 R8 PC12
10.10.10.3/32 10.10.10.4/32
3ffe::1:303:303/128 3ffe::1:404:404/128

eth1 192.168.1.11/24 10.10.10.7/32 10.10.10.8/32 eth1 192.168.1.12/24

3ffe::1:707:707/128 3ffe::1:808:808/128

6 Nokia 2020
© Nokia Confidential

System Address – AS 65100

R1 – 10.10.10.1/32
R2 – 10.10.10.2/32
R5 – 10.10.10.5/32
R6 – 10.10.10.6/32
R3 – 10.10.10.3/32
R4 – 10.10.10.4/32
R7 – 10.10.10.7/32
R8 – 10.10.10.8/32

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M03 Ed0 6
Physical Ports
PC9 AS 65100 PC10
1/1/5 1/1/5
eth1 eth1
1/1/4 1/1/4
R5 R1 R2
R6
1/1/2
1/1/5 1/1/5

1/1/1 1/1/1

1/1/5 1/1/5
1/1/2

PC11 R3 R4 R8 PC12
1/1/4 1/1/4
1/1/5 1/1/5
eth1 eth1

R7

7 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M03 Ed0 7
 VPLS 15 using BGP-AD
Goal - All PCs can ping with each other over VPLS 15.
PC9 PC10
Pod1 Pod2

R5 R1 R2 R6

VPLS using
BGP-AD

PC11 R3 R4 R8 PC12

Pod3 Pod4

R7
8 Nokia 2020
© Nokia Confidential

Student1 and Student2 – Pod1

Student3 and Student4 – Pod2

Student5 and student6 – Pod3

Student7 and Student8 – Pod4

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M03 Ed0 8
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y).

Initial rollback config file’s comment (X) – Final-Services SDP.

• /admin rollback revert X

Final rollback config file’s comment (Y) – Final – VPLS BGP-AD.

To compare current config with the final lab answer:

• /admin rollback compare active-cfg to Y

9 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M03 Ed0 9
 VPLS using BGP-AD

10Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
------------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M03 Ed0 10
VPLS BGP-AD
VPLS using
BGP-AD Auto-Provisioned
using Auto-ProvisionedSDPs
SDPs
BGP auto-discovery is intended to simplify the deployment of LDP VPLS services. It can also be
used in anytonetwork
Switch using LDP VPLS. Networks that are already using manually provisioned
notes view!
SDP bindings may enable BGP AD to simplify the provisioning of new services. BGP AD
supports automatic discovery of all VPLS edge devices, or PE routers, participating in a VPLS
service. When MP-BGP is enabled, or already deployed in a network, the same BGP
auto-discovery mechanism can be used for both L2 VPN and L3 VPN services. The main
advantage offered by BGP AD is the ability to automatically create and bind SDPs to all PE
routers participating in the LDP VPLS signaled service. SR OS LDP VPLS has many industry
standard and proprietary resiliency features. BGP AD simplifies provisioning of LDP VPLS
without compromising resiliency.

PE2

SDP
11Nokia 2020
© Nokia Confidential

CE

PE1

SDP
VPLS

CE

SDP

PE3 CE

VPLS instance where the SDPs are auto-provisioned:

• SDPs are instantiated by a PE router using LDP signaling upon receipt of BGP
auto-discovery (BGP-AD) updates from peer PE routers.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M03 Ed0 11
Configure MP-BGP
Configure MP-BGP
1. Each pair of students login to their Edge routers (R5 to R8) and configure MP-BGP
neighbors
Switch to allview!
to notes other Edge routers.

Note: A route reflector is recommended in a large network to scale BGP well and to simplify
the BGP configuration when new PEs are added in the network.

A:R5# configure router bgp A:R6# configure router bgp

A:R5>config>router>bgp# info A:R6>config>router>bgp# info
------------------------------------- -------------------------------------
group "mpbgp" group "mpbgp"
family l2-vpn family l2-vpn
peer-as 65100 peer-as 65100
neighbor 10.10.10.6 neighbor 10.10.10.5
exit exit
neighbor 10.10.10.7 neighbor 10.10.10.7
exit exit
neighbor 10.10.10.8 neighbor 10.10.10.8
12Nokia 2020
© exit Nokia Confidential exit
exit exit
no shutdown no shutdown
------------------------------------- -------------------------------------

A:R7# configure router bgp A:R8# configure router bgp

A:R7>config>router>bgp# info A:R8>config>router>bgp# info
------------------------------------- -------------------------------------
group "mpbgp" group "mpbgp"
family l2-vpn family l2-vpn
peer-as 65100 peer-as 65100
neighbor 10.10.10.5 neighbor 10.10.10.5
exit exit
neighbor 10.10.10.6 neighbor 10.10.10.6
exit exit
neighbor 10.10.10.8 neighbor 10.10.10.7
exit exit
exit exit
no shutdown no shutdown
------------------------------------- -------------------------------------

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M03 Ed0 12
Verify MP-BGP
Verify MP-BGP
Verify the neighboring router with which MP-BGP sessions are established. Ensure that each Edge
router has 3 neighbors.
Switch to notes view!
A:R5# show router bgp summary
==============================================================================
BGP Router ID:10.10.10.5 AS:65100 Local AS:65100
==============================================================================
BGP Admin State : Up BGP Oper State : Up
Total Peer Groups : 1 Total Peers : 3
Total VPN Peer Groups : 0 Total VPN Peers : 0
Total BGP Paths : 56 Total Path Memory : 19328
<< skip >>
BGP Summary
Legend : D - Dynamic Neighbor
==============================================================================
Neighbor
Description
AS PktRcvd InQ Up/Down State|Rcv/Act/Sent (Addr Family)
PktSent OutQ
------------------------------------------------------------------------------
13Nokia 2020
© Nokia Confidential

10.10.10.6
65100 263 0 02h09m33s 1/1/1 (L2VPN)
263 0
10.10.10.7
65100 263 0 02h09m33s 1/1/1 (L2VPN)
263 0
10.10.10.8
65100 263 0 02h09m33s 1/1/1 (L2VPN)
263 0
------------------------------------------------------------------------------

A:R8# show router bgp summary

==============================================================================
BGP Router ID:10.10.10.8 AS:65100 Local AS:65100
==============================================================================
BGP Admin State : Up BGP Oper State : Up
Total Peer Groups : 1 Total Peers : 3
Total VPN Peer Groups : 0 Total VPN Peers : 0
Total BGP Paths : 56 Total Path Memory : 19328
<< skip>>
BGP Summary
Legend : D - Dynamic Neighbor
==============================================================================
Neighbor
Description
AS PktRcvd InQ Up/Down State|Rcv/Act/Sent (Addr Family)
PktSent OutQ
------------------------------------------------------------------------------
10.10.10.5
65100 268 0 02h12m20s 1/1/1 (L2VPN)
269 0
10.10.10.6
65100 268 0 02h12m20s 1/1/1 (L2VPN)
269 0
10.10.10.7
65100 268 0 02h12m16s 1/1/1 (L2VPN)
268 0
------------------------------------------------------------------------------

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M03 Ed0 13
Configure a pw-template
Configure a pw-template
Pseudowire templates are used by BGP to dynamically instantiate Service Distribution Point
(SDP) bindings,
Switch for view!
to notes a given service they are used to signal the egress service de-multiplex or
labels used by remote PEs to reach the local PE.
The template determines the signaling parameters of the pseudowire, control word presence,
plus other usage characteristics such as Split Horizon Groups, MAC-pinning, filters, etc.
The MPLS transport tunnel between PE routers can be signaled using either LDP or RSVP.
LDP based pseudowires can be automatically instantiated. RSVP based SDPs have to be
pre-provisioned.
In order to use an LDP transport tunnel for data flow between PEs, it is necessary for link layer
LDP to be configured between all PEs/Ps so that a transport label for each PE’s system
interface address is available. Using this mechanism SDPs can be auto-instantiated.

A:R5# configure service pw-template 1 create

A:R5>config>service>pw-template#
14Nokia 2020
© Nokia Confidential
split-horizon-group "mesh"
exit

A:R6# configure service pw-template 1 create

A:R6>config>service>pw-template#
split-horizon-group "mesh"
exit

A:R7# configure service pw-template 1 create

A:R7>config>service>pw-template#
split-horizon-group "mesh"
exit

A:R8# configure service pw-template 1 create

A:R8>config>service>pw-template#
split-horizon-group "mesh"
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M03 Ed0 14
Verify thethe
Verify pw-template
pw-template

Switch
A:R5# to notes
show view!pw-template
service

==============================================================================
PW Template information
==============================================================================
PW Template Id SDP Last Update
------------------------------------------------------------------------------
1 Auto-mpls 07/03/2020 07:03:29
==============================================================================

A:R8# show service pw-template

==============================================================================
PW Template information
==============================================================================
PW Template Id SDP Last Update
------------------------------------------------------------------------------
1 Auto-mpls 07/03/2020 07:03:33
==============================================================================
15Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M03 Ed0 15
Configure thethe
Configure VPLS BGP-AD
VPLS BGP-AD

Each pair of students login to their Edge routers (R5 to R8) and create VPLS 15 (customer 1)
Switch to notes view!
with pw-template.

Verify port 1/1/5 has a dot1q encapsulation and it is an Access port. If the incoming traffic has
a VLAN tag of non-zero such as 123, the SAP definition would be SAP 1/1/5:123.

Shutdown and remove sap 1/1/5:0 from Epipe/VPLS/VPRN (if in use) and re-use the sap for
VPLS 15.

A:R5# configure service vpls 15 customer 1 create

A:R5>config>service>vpls$
bgp
route-distinguisher 65100:15
route-target export target:65100:15 import target:65100:15
pw-template-binding 1
16Nokia 2020
© exit Nokia Confidential

exit
bgp-ad
vpls-id 65100:15
no shutdown
exit
stp
shutdown
exit
sap 1/1/5:0 create
no shutdown
exit
no shutdown

Note: Ensure LDP signaling must be operational on all routers with their interfaces to signal
transport tunnels between nodes.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M03 Ed0 16
Verify thethe
Verify VPLS BGP-AD
VPLS BGP-AD
Verify the service you have created.
Switch to notes view!
A:R5# show service id 15 bgp-ad

------------------------------------------------------------------------------
BGP Auto-discovery Information
------------------------------------------------------------------------------
Admin State : Up
Vpls Id : 65100:15
Prefix : 10.10.10.5
------------------------------------------------------------------------------

A:R8# show service id 15 bgp-ad

------------------------------------------------------------------------------
BGP Auto-discovery Information
------------------------------------------------------------------------------
Admin State : Up
Vpls Id
17Nokia
© 2020 : 65100:15 Nokia Confidential
Prefix : 10.10.10.8
------------------------------------------------------------------------------

A:R5# show service id 15 base

==============================================================================
Service Basic Information
==============================================================================
Service Id : 15 Vpn Id : 0
Service Type : VPLS
MACSec enabled : no
Name : 15
Description : (Not Specified)
Customer Id : 1 Creation Origin : manual
Last Status Change: 07/03/2020 07:03:36
Last Mgmt Change : 07/03/2020 07:04:30
Etree Mode : Disabled
Admin State : Up Oper State : Up
MTU : 1514
SAP Count : 1 SDP Bind Count : 3
<< skip >>

------------------------------------------------------------------------------
Service Access & Destination Points
------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
------------------------------------------------------------------------------
sap:1/1/5:0 q-tag 1518 1518 Up Up
sdp:32765:4294967293 SB(10.10.10.7) BgpAd 0 8682 Up Up
sdp:32766:4294967294 SB(10.10.10.6) BgpAd 0 8682 Up Up
sdp:32767:4294967295 SB(10.10.10.8) BgpAd 0 8682 Up Up
==============================================================================

Dynamic bgp-l2vpn  SDPs

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M03 Ed0 17
Verify thethe
Verify Auto Created
Auto SDP
Created SDP
All SDPs should be listed for the far-end devices.
Switch to notes view!
A:R5# show service sdp

============================================================================
Services: Service Destination Points
============================================================================
SdpId AdmMTU OprMTU Far End Adm Opr Del LSP Sig
----------------------------------------------------------------------------
32765 0 8682 10.10.10.7 Up Up MPLS L/B TLDP
32766 0 8682 10.10.10.6 Up Up MPLS L/B TLDP
32767 0 8682 10.10.10.8 Up Up MPLS L/B TLDP
----------------------------------------------------------------------------
Number of SDPs : 3

A:R6# show service sdp

============================================================================
Services: Service Destination Points
============================================================================
18Nokia 2020
© Nokia Confidential
SdpId AdmMTU OprMTU Far End Adm Opr Del LSP Sig
----------------------------------------------------------------------------
32765 0 8682 10.10.10.7 Up Up MPLS L/B TLDP
32766 0 8682 10.10.10.5 Up Up MPLS L/B TLDP
32767 0 8682 10.10.10.8 Up Up MPLS L/B TLDP
----------------------------------------------------------------------------
Number of SDPs : 3
----------------------------------------------------------------------------

A:R7# show service sdp

============================================================================
Services: Service Destination Points
============================================================================
SdpId AdmMTU OprMTU Far End Adm Opr Del LSP Sig
----------------------------------------------------------------------------
32765 0 8682 10.10.10.8 Up Up MPLS L/B TLDP
32766 0 8682 10.10.10.6 Up Up MPLS L/B TLDP
32767 0 8682 10.10.10.5 Up Up MPLS L/B TLDP
----------------------------------------------------------------------------
Number of SDPs : 3
----------------------------------------------------------------------------

A:R8# show service sdp

============================================================================
Services: Service Destination Points
============================================================================
SdpId AdmMTU OprMTU Far End Adm Opr Del LSP Sig
----------------------------------------------------------------------------
32765 0 8682 10.10.10.7 Up Up MPLS L/B TLDP
32766 0 8682 10.10.10.5 Up Up MPLS L/B TLDP
32767 0 8682 10.10.10.6 Up Up MPLS L/B TLDP
----------------------------------------------------------------------------
Number of SDPs : 3
----------------------------------------------------------------------------
Legend: R = RSVP, L = LDP, B = BGP, M = MPLS-TP, n/a = Not Applicable
I = SR-ISIS, O = SR-OSPF, T = SR-TE, F = FPE
============================================================================

Note: The SDPs are auto-provisioned using BGP. The SDP Id may be different for your group/scenario
at the time of performing this lab.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M03 Ed0 18
Verify Service
Verify Service
1. Verify the VPLS service with ping traffic using PCs connected to the SAPs. Each pair of
students
Switch configure
to notes view!their PCs (PC9 to PC12) as follows:
• ifconfig eth1 192.168.1.9/24 (for PC9)
• ifconfig eth1 192.168.1.10/24 (for PC10)
• ifconfig eth1 192.168.1.11/24 (for PC11)
• ifconfig eth1 192.168.1.12/24 (for PC12)

• Verify that PC9 can ping to PC10, 11 and 12 through VPLS 15.

[root@PC9 ~]# ping 192.168.1.10

PING 192.168.1.10 (192.168.1.10) 56(84) bytes of data.
64 bytes from 192.168.1.10: icmp_seq=1 ttl=64 time=9.79 ms
64 bytes from 192.168.1.10: icmp_seq=2 ttl=64 time=3.55 ms
64 bytes from 192.168.1.10: icmp_seq=3 ttl=64 time=4.16 ms
64 bytes from 192.168.1.10: icmp_seq=4 ttl=64 time=4.66 ms
64 bytes from 192.168.1.10: icmp_seq=5 ttl=64 time=4.08 ms
19Nokia 2020
© Nokia Confidential

[root@PC9 ~]# ping 192.168.1.11

PING 192.168.1.11 (192.168.1.11) 56(84) bytes of data.
64 bytes from 192.168.1.11: icmp_seq=1 ttl=64 time=10.0 ms
64 bytes from 192.168.1.11: icmp_seq=2 ttl=64 time=3.66 ms
64 bytes from 192.168.1.11: icmp_seq=3 ttl=64 time=4.11 ms
64 bytes from 192.168.1.11: icmp_seq=4 ttl=64 time=4.06 ms
64 bytes from 192.168.1.11: icmp_seq=5 ttl=64 time=4.12 ms

[root@PC9 ~]# ping 192.168.1.12

PING 192.168.1.12 (192.168.1.12) 56(84) bytes of data.
64 bytes from 192.168.1.12: icmp_seq=1 ttl=64 time=11.8 ms
64 bytes from 192.168.1.12: icmp_seq=2 ttl=64 time=4.62 ms
64 bytes from 192.168.1.12: icmp_seq=3 ttl=64 time=4.94 ms
64 bytes from 192.168.1.12: icmp_seq=4 ttl=64 time=5.09 ms
64 bytes from 192.168.1.12: icmp_seq=5 ttl=64 time=4.37 ms

Verify the MAC addresses learnt on the VPLS.

A:R5# show service fdb-mac

==============================================================================
Service Forwarding Database
==============================================================================
ServId MAC Source-Identifier Type Last Change
Transport:Tnl-Id Age
------------------------------------------------------------------------------
15 02:00:a8:00:c9:01 sap:1/1/5:0 L/0 07/03/20 10:55:28
15 02:00:a8:00:ca:01 sdp:32765:4294967292 L/0 07/03/20 10:55:52
15 02:00:a8:00:cb:01 sdp:32763:4294967290 L/0 07/03/20 10:55:36
15 02:00:a8:00:cc:01 sdp:32764:4294967291 L/0 07/03/20 10:55:28
------------------------------------------------------------------------------
No. of Entries: 4
------------------------------------------------------------------------------
Legend: L=Learned O=Oam P=Protected-MAC C=Conditional S=Static Lf=Leaf
==============================================================================

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M03 Ed0 19
Wrap-up
In this module we have covered the following items:
• Configured and verified MP-BGP with L2-VPN family
• Configured and verified VPLS BGP-AD

20Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M03 Ed0 20
21Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M03 Ed0 21
 IES RVPLS Introduction

ER00198-V-2000 V0 - S05M04 Ed0

1 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M04 Ed0 1
Learning Objectives
Upon completion of this module, you should be able to:
• Configure and verify:
- Internet Enhanced Service (IES)
- Routed VPLS Service (rVPLS)

2 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M04 Ed0 2
 ToC Slide

Table of Contents

Lab Setup
Internet Enhanced Services (IES)
Routed VPLS (rVPLS)
Wrap-up

3 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M04 Ed0 3
 Lab Setup

4 Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
------------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M04 Ed0 4
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y).

Initial rollback config file’s comment (X) – Final – Epipe, VPLS and VPRN.
• /admin rollback revert X

Final rollback config file’s comment (Y) – Final – IES.

To compare current config with the final lab answer:

• /admin rollback compare active-cfg to Y

5 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M04 Ed0 5
 Internet Enhanced Services (IES)

6 Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
------------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M04 Ed0 6
IESIES
Configuration
Configuration
A VPRN is a routed layer 3 network service where each VPRN has its own virtual routing and forwarding
table (VRF).to
Switch A service router can has many instances of VPRN each having its own VRF.
notes view!

An IES is also a routed layer 3 network service but using the Global Routing Table (GRT). Therefore, while
each service router can have many instances of IESs, they all sharing the same GRT. IP addresses of the
network and access ports can also be found on the GRT.

An IES can have many Interfaces with one or more SAPs, IP addresses and ports/loopbacks. IES
Interfaces can be included in IGP or EBP (e.g., static, OSPF, ISIS and BGP) for the address prefixes to be
distributed to other systems.

IES can terminate spoke-SDPs such as an Epipe, or VPLS and forms complex network service such as
routed-VPLS (rVPLS). Local rVPLS can also be formed using internal “hook” instead of WAN spoke-sdp
as shown in Lab 2
IES uses only IP and thus there is no need to provision any MPLS, or LDP unless WAN rVPLS is needed.
7 Nokia 2020
©
IES 10
Nokia Confidential

Subnet X SAP

PC
1. Each pair of students login to their Edge routers (R5 to R8) and configure an IES 10 (customer 1)
with:
• Interface toSubnetX
• address 192.168.X.1/24
- where X can be 9 to 12
• sap 1/1/5:0

A:R5>config>service# info A:R6>config>service# info

------------------------------------- -------------------------------------
ies 10 customer 1 create ies 10 customer 1 create
interface "toSubnet9" create interface "toSubnet10" create
address 192.168.9.1/24 address 192.168.10.1/24
sap 1/1/5:0 create sap 1/1/5:0 create
exit exit
exit exit
no shutdown no shutdown
exit exit

A:R7>config>service# info A:R8>config>service# info

------------------------------------- -------------------------------------
ies 10 customer 1 create ies 10 customer 1 create
interface "toSubnet11" create interface "toSubnet12" create
address 192.168.11.1/24 address 192.168.12.1/24
sap 1/1/5:0 create sap 1/1/5:0 create
exit exit
exit exit
no shutdown no shutdown
exit exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M04 Ed0 7
IES Verification
IES Verification
2. Add the IES interface toSubnetX onto OSPF area 0.0.0.0 and use the following commands
to verify
Switch to IES interface
notes view! addresses reachability.
• show router route-table
• ping 192.168.X.1/24

A:R5>config>router>ospf# info
----------------------------------------------
traffic-engineering
loopfree-alternates
exit
area 0.0.0.0
interface "system"
no shutdown
exit
interface "toR1"
interface-type point-to-point
bfd-enable
no shutdown
8 Nokia 2020
© Nokia Confidential
exit
interface "toSubnet9"
no shutdown
exit
exit
no shutdown
----------------------------------------------

All local and remote IES interfaces are shown up.

A:R5# show router route-table

==============================================================================
Route Table (Router: Base)
==============================================================================
Dest Prefix[Flags] Type Proto Age Pref
Next Hop[Interface Name] Metric
------------------------------------------------------------------------------
<< skip >>
192.168.9.0/24 Local Local 00h09m54s 0
toSubnet9 0
192.168.10.0/24 Remote OSPF 00h04m53s 10
10.1.5.1 40
192.168.11.0/24 Remote OSPF 00h04m19s 10
10.1.5.1 40
192.168.12.0/24 Remote OSPF 00h03m41s 10
10.1.5.1 50
------------------------------------------------------------------------------
No. of Routes: 21

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M04 Ed0 8
IES Verification [cont.]
IES Verification [cont.]
Ping to all IES’ interfaces are successful as they are in the Global Routing Table via OSPF.
Switch to notes view!
A:R5# ping 192.168.10.1
PING 192.168.10.1 56 data bytes
64 bytes from 192.168.10.1: icmp_seq=1 ttl=62 time=2.07ms.
64 bytes from 192.168.10.1: icmp_seq=2 ttl=62 time=1.83ms.

A:R5# ping 192.168.11.1

PING 192.168.11.1 56 data bytes
64 bytes from 192.168.11.1: icmp_seq=1 ttl=62 time=2.02ms.
64 bytes from 192.168.11.1: icmp_seq=2 ttl=62 time=1.94ms.

A:R5# ping 192.168.12.1

PING 192.168.12.1 56 data bytes
64 bytes from 192.168.12.1: icmp_seq=1 ttl=61 time=3.59ms.
64 ©9bytes
Nokia 2020 from 192.168.12.1: icmp_seq=2 ttl=61 time=2.38ms.
Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M04 Ed0 9
 Routed VPLS (rVPLS)

10Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
------------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M04 Ed0 10
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y).

Initial rollback config file’s comment (X) – Final – IES.

• /admin rollback revert X

Final rollback config file’s comment (Y) – Final – IES and rVPLS.

To compare current config with the final lab answer:

• /admin rollback compare active-cfg to Y

11Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M04 Ed0 11
rVPLS Introduction

rVPLS is a popular access traffic aggregation service to offer a subnet with local L2 switching and remote
L3 routing such as a cell site where multiple pieces of equipment need to communicate locally (i.e.,
switching) and remotely (i.e., routing).

For security, SROS offers internal connection to interconnect VPLS and IES/VPRN within a router without
using physical S-Hooks.
PE

VPLS
No external ports
Traditional Method Routed VPLS
PE
PE PE

VPLS VPLS VPLS

External Cable Internal
(S-Hook) Connection
IES or IES or
VPRN L3 Interface VPRN L3 Interface

12Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M04 Ed0 12
rVPLS Configuration

1. Each pair of student log on to their Edge routers from R5 to R8 to:

Modify ies 10:

• shutdown and remove existing sap 1/1/5:0 for vpls 800
• ip-mtu 1500
• vpls rvpls_800

Create a new vpls 800:

• sap 1/1/5:0
• sap 1/1/5:50
• allow-ip-int-bind
• service-mtu 1514
• service-name “rvpls_800”

Explain service-mtu 1514, ip-mtu 1500 and rvpls_800

13Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M04 Ed0 13
rVPLS Configuration [cont.]

sap 1/1/5:0 of ies 10 in the previous lab is now moved to VPLS 800
sap 1/1/5:50 illustrates that additional SAPs can be created under vpls 800 for L2 local switching and remote L3 routing

A:R5>config>service# info A:R6>config>service# info

---------------------------------------------- ----------------------------------------------
ies 10 customer 1 create ies 10 customer 1 create
interface "toSubnet9" create interface "toSubnet10" create
address 192.168.9.1/24 address 192.168.10.1/24
ip-mtu 1500 ip-mtu 1500
vpls "rvpls_800" vpls "rvpls_800"
exit exit
exit exit
no shutdown no shutdown
exit exit
vpls 800 name "rvpls_800" customer 100 create vpls 800 name "rvpls_800" customer 100 create
allow-ip-int-bind allow-ip-int-bind
exit exit
stp stp
shutdown shutdown
exit exit
sap 1/1/5:0 create sap 1/1/5:0 create
no shutdown no shutdown
exit exit
sap 1/1/5:50 create sap 1/1/5:50 create
no shutdown no shutdown
exit exit
no shutdown no shutdown
exit exit

14Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M04 Ed0 14
rVPLS Configuration [cont.]

A:R7>config>service# info A:R8>config>service# info

---------------------------------------------- ----------------------------------------------
ies 10 customer 1 create ies 10 customer 1 create
interface "toSubnet11" create interface "toSubnet12" create
address 192.168.9.1/24 address 192.168.9.1/24
ip-mtu 1500 ip-mtu 1500
vpls "rvpls_800" vpls "rvpls_800"
exit exit
exit exit
no shutdown no shutdown
exit exit
vpls 800 name "rvpls_800" customer 100 create vpls 800 name "rvpls_800" customer 100 create
allow-ip-int-bind allow-ip-int-bind
exit exit
stp stp
shutdown shutdown
exit exit
sap 1/1/5:0 create sap 1/1/5:0 create
no shutdown no shutdown
exit exit
sap 1/1/5:50 create sap 1/1/5:50 create
no shutdown no shutdown
exit exit
no shutdown no shutdown
exit exit

15Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M04 Ed0 15
rVPLS Configuration [cont.]

rvpls_800 in vpls 800 and ies 10 forms the internal connection between the L2 and L3 services without
any physical external cable for security.

Ethernet NIC’s payload MTU is 1500 bytes excluding the 14 bytes Ethernet header (18 bytes for dot1q *
match).

If an application sends a packet that is greater than 1500 Ethernet payload, the IP stack of the host will
fragment the packet into multiple smaller Ethernet frame with Ethernet payloads up to 1500 bytes
maximum.

VPLS service is a layer 2 network service that needs to transport the Ethernet header and thus its
service-mtu = 1514 bytes.

IES is a layer 3 network service that strips off layer 2 header. Therefore, ip-mtu is 1500 bytes.

16Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M04 Ed0 16
Connectivity and MTU Verification

2. On the PC (sender) connected to the Edge router, invoke the commands:

• ping 192.168.X.2 –s 1472
• ping 192.168.X.2 –s 1473
- X can be 9 to 12

While the PC is pinging, on the receiving PC, invoke the command to explain the packet
fragmentation and ping packet sizes:
• tcpdump –i eth1 –v

Explain why use ping’s payload of 1472 and 1473 bytes?

17Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M04 Ed0 17
Connectivity and MTU Verification [cont.]

Ping’s header is 8 bytes. Together with the 20 bytes IP header, the maximum Ping’s payload without
causing packet fragmentation is 1500 - 8 - 20 = 1472 bytes.

When ping between R5 and R6 over the rVPLS service with ping’s payload of 1472 bytes, which fits inside
one Ethernet frame, only one ping packet is delivered at the far end R6.
[root@PC9 ~]# ping 192.168.10.2 -s 1472
PING 192.168.10.2 (192.168.10.2) 1472(1500) bytes of data.
1480 bytes from 192.168.10.2: icmp_seq=1 ttl=60 time=4.67 ms
1480 bytes from 192.168.10.2: icmp_seq=2 ttl=60 time=4.24 ms
1480 bytes from 192.168.10.2: icmp_seq=3 ttl=60 time=4.93 ms

[root@PC10 ~]# tcpdump -i eth1 -v

, Mask 255.255.255.0, Priority 1
Designated Router 192.168.10.1
20:24:15.123767 IP (tos 0x0, ttl 60, id 0, offset 0, flags [DF], proto ICMP (1), length 1500)
192.168.9.2 > 192.168.10.2: ICMP echo request, id 24839, seq 1, length 1480

20:24:15.123797 IP (tos 0x0, ttl 64, id 25835, offset 0, flags [none], proto ICMP (1), length 1500)
192.168.10.2 > 192.168.9.2: ICMP echo reply, id 24839, seq 1, length 1480

18Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M04 Ed0 18
Connectivity and MTU Verification [cont.]

When ping’s payload is 1473 bytes, the PC’s IP stack needs to fragment the ping payload into two
Ethernet frames:
• ICMP ping’s Length exclude the 20 bytes IP header (i.e., 1472 + 8 = 1480 bytes)
[root@PC9 ~]# ping 192.168.10.2 -s 1473
PING 192.168.10.2 (192.168.10.2) 1473(1501) bytes of data.
1481 bytes from 192.168.10.2: icmp_seq=1 ttl=60 time=3.95 ms
1481 bytes from 192.168.10.2: icmp_seq=2 ttl=60 time=4.73 ms
1481 bytes from 192.168.10.2: icmp_seq=3 ttl=60 time=5.13 ms

Due to packet fragmentation, two fragmented ping packets are sent for each ping request and
response. The destination host needs to re-assemble the fragmented packets.
[root@PC10 ~]# tcpdump -i eth1 -v
tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes

20:20:19.388575 IP (tos 0x0, ttl 60, id 41106, offset 0, flags [+], proto ICMP (1), length 1500)
192.168.9.2 > 192.168.10.2: ICMP echo request, id 24583, seq 18, length 1480
20:20:19.388878 IP (tos 0x0, ttl 60, id 41106, offset 1480, flags [none], proto ICMP (1), length 21)
192.168.9.2 > 192.168.10.2: icmp

20:20:19.388908 IP (tos 0x0, ttl 64, id 25829, offset 0, flags [+], proto ICMP (1), length 1500)
192.168.10.2 > 192.168.9.2: ICMP echo reply, id 24583, seq 18, length 1480
20:20:19.388949 IP (tos 0x0, ttl 64, id 25829, offset 1480, flags [none], proto ICMP (1), length 21)
192.168.10.2 > 192.168.9.2: icmp

19Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M04 Ed0 19
Wrap-up
In this module we have covered the following items:
• Configuring and verifying:
- Internet Enhanced Service (IES)
- Routed VPLS Service (rVPLS)

20Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M04 Ed0 20
21Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M04 Ed0 21
 BGP

ER00198-V-2000 V0 - S05M05 Ed0

1 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 1
Learning Objectives
Upon completion of this module, you should be able to:
• Configure the common IPv4 and IPv6 iBGP and eBGP setup on Nokia’s Service
Router, including:
̵ iBGP with the next-hop-self setup for an Autonomous System (AS)
̵ eBGP setup across multiple Autonomous Systems (ASes)
̵ iBGP and eBPG import and export policies for traffic steering by using community, local
preference, or prefix list
̵ IPv6 eBGP by using the IPv6 interface local link address
̵ Route Reflectors and redundancy for iBGP scalability

2 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 2
 ToC Slide

Table of Contents

BGP Lab Setup

Initial BGP Lab Setup
Edge Router iBGP
Edge Router iBGP Access Service Export Policy
Border Router eBGP and Default Traffic Path
Inter-AS Traffic Steering
Scaling iBGP with RR
IPv6 iBGP and eBGP
Wrap-up

3 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 3
 BGP Lab Setup

4 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 4
 Service Router System Addresses
10.100.100.5/32 10.100.100.6/32
2001:db8:a:500::5/128 2001:db8:a:600::6/128
R5 R6

R1 R2

10.100.100.1/32 10.100.100.2/32
2001:db8:a:100::1/128 2001:db8:a:200::2/128

10.200.200.3/32 10.200.200.4/32
2001:db8:a:300::3/128 2001:db8:a:400::4/128

R3 R4

R7 R8
10.200.200.7/32 10.200.200.8/32
2001:db8:a:700::7/128 2001:db8:a:800::8/128

5 Nokia 2020
© Nokia Confidential

System Address – AS 65100

R1 – 10.10.100.1/32
R2 – 10.10.100.2/32
R5 – 10.10.100.5/32
R6 – 10.10.100.6/32

System Address – AS 65200

R3 – 10.10.200.3/32
R4 – 10.10.200.4/32
R7 – 10.10.200.7/32
R8 – 10.10.200.8/32

Router Management IP can be different for each training beacuse different lab pods can be
used.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 5
 Service Router Link Address

10.5.6.5 10.5.6.6
R5 R6
10.1.5.5 R2 10.2.6.6
R1
10.1.2.1 10.1.2.2
10.1.5.1 10.2.6.2

10.1.3.1 10.2.4.2

10.1.3.3 10.2.4.4

10.3.7.3 10.4.8.4
10.3.4.3 10.3.4.4

10.7.3.7 R3 R4 10.4.8.8

R7 R8
10.7.8.7 10.7.8.8

6 Nokia 2020
© Nokia Confidential

System Address – AS 65100

R1 – 10.10.100.1/32
R2 – 10.10.100.2/32
R5 – 10.10.100.5/32
R6 – 10.10.100.6/32

System Address – AS 65200

R3 – 10.10.200.3/32
R4 – 10.10.200.4/32
R7 – 10.10.200.7/32
R8 – 10.10.200.8/32

Router Management IP can be different for each training beacuse different lab pods can be
used.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 6
 Service Router Physical Port and Autonomous System
AS 65100

1/1/2
R5 R6
1/1/4 1/1/4
R1 R2

1/1/2
1/1/5 1/1/5

1/1/1 1/1/1

1/1/5 1/1/5
1/1/2

1/1/4 R3 R4 1/1/4
R7 R8
1/1/2

AS 65200
7 Nokia 2020
© Nokia Confidential

R1 to R4 are Border or Core routers.

R5 to R8 are Edge routers.

Each pair of students has one Border and one Edge router.

R1, R2, R5, and R6 are in AS 65100.

R3, R4, R7, and R8 are in AS 65200.

OSPF is used in each AS for router connectivity.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 7
 Lab Pods and Student Assignment
BGP_Pod1 BGP_Pod2

R5 R6

R1 R2

R3 R4
R7 R8
BGP_Pod3 BGP_Pod4

8 Nokia 2020
© Nokia Confidential

Student1 and student2 – BGP_Pod1

Student3 and student4 – BGP_Pod2

Student5 and student6 – BGP_Pod3

Student7 and student8 – BGP_Pod4

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 8
Student Lab Assignment
Group Border/Core Router Edge Router AS

Student1 R1 R5 65100
Student2 10.100.100.1/32 10.100.100.5/32
(BGP_Pod1) 2001:db8:a:100::1/128 2001:db8:a:500::5/128

Student3 R2 R6
Student4 10.100.100.2/32 10.100.100.6/32
(BGP_Pod2) 2001:db8:a:200::2/128 2001:db8:a:600::6/128

Student5 R3 R7 65200
Student6 10.200.200.3/32 10.200.200.7/32
(BGP_Pod3) 2001:db8:a:300::3/128 2001:db8:a:700::7/128

Student7 R4 R8
Student8 10.200.200.4/32 10.200.200.8/32
(BGP_Pod4) 2001:db8:a:400::4/128 2001:db8:a:800::8/128

9 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 9
Student Lab Assignment [cont.]
Customer Networks Customer Networks
(Access Service) (Access Service)

Edge Router Edge Router

Border Router Border Router

Internet

• Set up iBGP full neighbor connections within an AS.

• Develop export policies on Edge routers to tag and export the customer networks. The import policy may be needed
for additional traffic control.
• Set up eBGP neighbor connections between ASes.
• Develop import and export policies on Border routers to use tags (communities) on customer networks (set by the
Edge routers) for inter-AS traffic steering.

10Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 10
 BGP Commands and Database
BGP database flow chart and commands:

11Nokia 2020
© Nokia Confidential

Please refer to the student guide for more information about BGP commands, and the various
route databases that are used for processing BGP packet input.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 11
 Initial BGP Lab Setup

12Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 12
Lab Objectives

iBGP neighbor connections rely on IGP ( for example, OSPF or ISIS) for IP connectivity among the routers
within an AS because not all the routers are directly connected.

The objectives of this lab are to:

• Understand the initial lab setup and let students become familiar with the lab
• Identify the SR configuration (for example, OSPF) that has been predefined so that students can focus on BGP-related
configuration and verification

13Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 13
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y).

Initial rollback config file’s comment - BGP - Initial with OSPF working.
• /admin rollback revert X

Final rollback config file’s comment – n/a.

To compare current config with the final lab answer:

• /admin rollback compare active-cfg to Y

14Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 14
IGP within an AS Config

OSPF has been set up in the initial lab config so that the routers in AS 65100 and AS65200 can reach
the routers within their ASes.

Use the following commands to verify OSPF config and IP connectivity within an AS:
• /config router ospf
• show router ospf neighbor
• show router route-table
• ping 10.X00.X00.Y
̵ X can be 1 or 2
̵ Y for AS 65100
• R1, R2, R5, and R6
̵ Y for AS 65200
• R3, R4, R7, and R8

15Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 15
IGPIGP
within anan
within ASAS
Config [cont.]
Config [cont.]

Exercise 1.1:
1. Switch to notesverifies
Each student view! the OSPF setup of their Border and Edge routers and routing table
and explains the output of the commands.

Border router OSPF config:

A:BGP_Pod1_R1>config>router>ospf# info
----------------------------------------------
area 0.0.0.0
interface "system"
no shutdown
exit
interface "toR2"
no shutdown
exit
interface "toR5"
no shutdown
16Nokia 2020
© Nokia Confidential
exit
exit
no shutdown
----------------------------------------------

Edge router OSPF config:

A:BGP_Pod1_R5>config>router>ospf# info
----------------------------------------------
area 0.0.0.0
interface "system"
no shutdown
exit
interface "toR1"
no shutdown
exit
interface "toR6"
no shutdown
exit
exit
no shutdown
----------------------------------------------

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 16
IGPIGP
within anan
within ASAS
Verification
Verification
OSPF Neighbor:
Switch to notes view!
Each router should have two OSPF neighbors that are in FULL state for exchanging OSPF
routes within the AS.

A:BGP_Pod1_R1# show router ospf neighbor

=============================================================================
Rtr Base OSPFv2 Instance 0 Neighbors
=============================================================================
Interface-Name Rtr Id State Pri RetxQ TTL
Area-Id
-----------------------------------------------------------------------------
toR2 10.100.100.2 Full 1 0 32
0.0.0.0
toR5 10.100.100.5 Full 1 0 36
0.0.0.0
17
© Nokia 2020 Nokia Confidential

-----------------------------------------------------------------------------
No. of Neighbors: 2

A:BGP_Pod1_R5# show router ospf neighbor

=============================================================================
Rtr Base OSPFv2 Instance 0 Neighbors
=============================================================================
Interface-Name Rtr Id State Pri RetxQ TTL
Area-Id
-----------------------------------------------------------------------------
toR1 10.100.100.1 Full 1 0 34
0.0.0.0
toR6 10.100.100.6 Full 1 0 32
0.0.0.0
-----------------------------------------------------------------------------
No. of Neighbors: 2

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 17
IGPIGP
within anan
within ASAS
Verification
Verification[cont.]
[cont.]
IP Connectivity within an AS through OSPF:
Switch to notes view!
The routing table shows that each router successfully learns the system (10.x00.x00.y) and link
addresses or of the other routers within an AS through OSPF.

A:BGP_Pod1_R1# show router route-table

===================================================================
Route Table (Router: Base)
===================================================================
Dest Prefix[Flags] Type Proto Age
Pref
Next Hop[Interface Name] Metric
-----------------------------------------------------------------------------
10.1.2.0/27 Local Local 00h04m37s 0
toR2 0
10.1.3.0/27
18Nokia 2020
© Nokia Confidential Local Local 00h04m37s 0
toR3 0
10.1.5.0/27 Local Local 00h04m37s 0
toR5 0
10.2.6.0/27 Remote OSPF 00h02m40s 10
10.1.2.2 20
10.5.6.0/27 Remote OSPF 00h02m02s 10
10.1.5.5 20
10.100.100.1/32 Local Local 00h04m37s 0
system 0
10.100.100.2/32 Remote OSPF 00h03m23s 10
10.1.2.2 10
10.100.100.5/32 Remote OSPF 00h03m01s 10
10.1.5.5 10
10.100.100.6/32 Remote OSPF 00h02m33s 10
10.1.2.2 20
------------------------------------------------------------------------------
No. of Routes: 9
Flags: n = Number of times nexthop is repeated
B = BGP backup route available
L = LFA nexthop available
S = Sticky ECMP requested

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 18
IGPIGP
within anan
within ASAS
Verification
Verification[cont.]
[cont.]
Router Ping Verification:
Switch to notes view!
Verify that the routers within an AS can ping to each other’s system interface (for
example,10.x00.x00.y). Note that the system interfaces of routers within an AS are advertised and
included in the routing tables:

A:BGP_Pod1_R5# ping 10.100.100.1

PING 10.100.100.1 56 data bytes
64 bytes from 10.100.100.1: icmp_seq=1 ttl=64 time=2.78ms.
64 bytes from 10.100.100.1: icmp_seq=2 ttl=64 time=1.70ms.

A:BGP_Pod1_R5# ping 10.100.100.2

PING 10.100.100.2 56 data bytes
64 bytes from 10.100.100.2: icmp_seq=1 ttl=63 time=3.98ms.
64 bytes from 10.100.100.2: icmp_seq=2 ttl=63 time=3.28ms.

A:BGP_Pod1_R5#
19Nokia 2020
©
ping 10.100.100.6 Nokia Confidential
PING 10.100.100.6 56 data bytes
64 bytes from 10.100.100.6: icmp_seq=1 ttl=64 time=2.32ms.
64 bytes from 10.100.100.6: icmp_seq=2 ttl=64 time=2.18ms.

A:BGP_Pod1_R1# show router route-table

==============================================================================
Route Table (Router: Base)
==============================================================================
Dest Prefix[Flags] Type Proto Age
Pref
Next Hop[Interface Name] Metric
------------------------------------------------------------------------------
10.1.2.0/27 Local Local 03d01h08m 0
toR2 0
10.1.3.0/27 Local Local 02d22h40m 0
toR3 0
10.1.5.0/27 Local Local 03d01h08m 0
toR5 0
10.2.6.0/27 Remote OSPF 03d00h07m 10
10.1.2.2 200
10.5.6.0/27 Remote OSPF 03d00h07m 10
10.1.5.5 200
10.100.100.1/32 Local Local 00h19m14s 0
system 0
10.100.100.2/32 Remote OSPF 00h18m49s 10
10.1.2.2 100
10.100.100.5/32 Remote OSPF 00h18m01s 10
10.1.5.5 100
10.100.100.6/32 Remote OSPF 00h17m40s 10
10.1.2.2 200
------------------------------------------------------------------------------
No. of Routes: 9
Flags: n = Number of times nexthop is repeated

The system addresses of remote nodes in an AS are distributed through OSPF.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 19
 Edge Router iBGP

20Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 20
iBGP Lab Objectives

In the previous lab, we verified that the routers within an AS can reach each other’s system interfaces
through the setup of OSPF. This is important because the iBGP neighboring within an AS relies on the
reachability of the system interfaces of the routers within the AS.
Before we can import and export customer networks that are terminating onto the Edge routers of an
AS, we need to set up the iBGP connections among all the routers within an AS.
Full Mesh iBGP neighboring among routers within an AS is required as because iBGP speakers do not re-
forward the received iBGP routes (split horizon). This create [N * (N -1) / N] iBGP neighbor connections
for the N routers within an AS.
• The Route Reflector lab shows how we can relax the Full Mesh iBGP neighboring requirement later.

By default, a BGP speaker exports only its BGP routes. All other direct and IGP-learned routes are not
exported unless there is an appropriate policy.

21Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 21
iBGP Lab Objectives [cont.]

The objectives of this lab are to:

• Configure iBGP full mesh neighbor connections among the routers within an AS so that we can import and export
customer networks through router policies later
• Become familiar with the SROS BGP commands to configure and verify iBGP setup
• Understand what types of routes are imported and exported, by default, by a BGP speaker without any route policy

22Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 22
 Introduction to iBGP Setup

Full mesh iBGP neighbor connections. Similar setup in AS 65200.

IP Access (Customer Networks) IP Access (Customer Networks)

Emulated by Loopback Emulated by Loopback

AS 65100

Edge Router

R5 R2 R6
R1

Core/Border Router

iBGP Neighbor
Internet Backbone

Edge routers terminate the IP access services (or customer networks) that are emulated by the loopback addresses at
the Edge routers.

23Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 23
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number.

Initial rollback config file’s comment – BGP - Initial with OSPF working.

Final rollback config file’s comment - BGP – iBGP full mesh neighbor in AS.

Use the command /admin rollback revert X to set the initial lab condition, if
necessary.

24Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 24
iBGP Config

Each group configure iBGP for the Border and Edge routers so that they can establish iBGP full mesh
neighbor connections with each other.

Use the following commands to configure and verify iBGP setup:

• config router bgp
• show router bgp summary
• show router bgp routes ipv4
• show router bgp neighbor 10.x00.x00.y advertised-routes ipv4
• show router bgp neighbor 10.x00.x00.y received-routes ipv4

25Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 25
iBGP Config [cont.]

A simple iBGP config looks like the following:

A:BGP_Pod1_R1>config>router>bgp# info
----------------------------------------------
group "iBGP"
description "AS65100 iBGP Mesh"
family ipv4
type internal
peer-as 65100
neighbor 10.100.100.2
description "BGP_Pod2_R2"
exit
neighbor 10.100.100.5
description "BGP_Pod1_R5"
exit
neighbor 10.100.100.6
description "BGP_Pod2_R6"
exit
exit
no shutdown

26Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 26
iBGP Verification
iBGP Verification
Exercise 2.1:
iBGP Config:
Switch to notes view!
Each group builds iBGP full mesh neighbor connections on their Border and Edge routers for
the AS.

Core router iBGP config:

A:BGP_Pod1_R1>config>router>bgp# info
----------------------------------------------
description "BGP_Pod1_R1"
group "iBGP"
description "AS65100 iBGP Mesh"
family ipv4
type internal
peer-as 65100
27Nokia 2020
©
neighbor 10.100.100.2Nokia Confidential
description "BGP_Pod2_R2"
exit
neighbor 10.100.100.5
description "BGP_Pod1_R5"
exit
neighbor 10.100.100.6
description "BGP_Pod2_R6"
exit
exit
no shutdown

Edge router iBGP config:

A:BGP_Pod1_R5# configure router bgp

A:BGP_Pod1_R5>config>router>bgp# info
----------------------------------------------
description "BGP_Pod1_R5"
group "iBGP"
description "AS65100 iBGP Mesh"
family ipv4
type internal
peer-as 65100
neighbor 10.100.100.1
description "BGP_Pod1_R1"
exit
neighbor 10.100.100.2
description "BGP_Pod2_R2"
exit
neighbor 10.100.100.6
description "BGP_Pod2_R6"
exit
exit
no shutdown

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 27
iBGP Verification
iBGP [cont.]
Verification [cont.]
iBGP Neighbor Connection Verification:
Switch to notes view!
Use the command show router bgp summary to verify the iBGP neighbor connections.

A:BGP_Pod1_R5# show router bgp summary

=============================================================================
BGP Router ID:10.100.100.5 AS:65100 Local AS:65100
=============================================================================
BGP Admin State : Up BGP Oper State : Up
Total Peer Groups : 1 Total Peers : 3
Total BGP Paths : 13 Total Path Memory : 2392

<< skip >>

=============================================================================
BGP Summary
=============================================================================
28Nokia 2020
© Nokia Confidential

Legend : D - Dynamic Neighbor

=============================================================================
Neighbor
Description
AS PktRcvd InQ Up/Down State|Rcv/Act/Sent (Addr Family)
PktSent OutQ
-----------------------------------------------------------------------------
10.100.100.1
BGP_Pod1_R1
65100 136 0 01h06m21s 0/0/0 (IPv4)
137 0
10.100.100.2
BGP_Pod2_R2
65100 136 0 01h06m21s 0/0/0 (IPv4)
137 0
10.100.100.6
BGP_Pod2_R6
65100 135 0 01h06m21s 0/0/0 (IPv4)
137 0

The iBGP neighbor connections are set up successfully when the State|Rcv/Act/Sent shows the
BGP routes that are sent and received (even 0).

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 28
iBGP Verification
iBGP [cont.]
Verification [cont.]
Default iBGP Route Import And Export Without Route Policy:
Switch to notes view!
The following shows that no BGP route is imported and exported by the Border and Edge
routers:

A:BGP_Pod1_R5# show router bgp routes ipv4

=============================================================================
BGP Router ID:10.100.100.5 AS:65100 Local AS:65100
=============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete

=============================================================================
BGP IPv4 Routes
29Nokia 2020
© Nokia Confidential
=============================================================================
Flag Network LocalPref MED
Nexthop (Router) Path-Id Label
As-Path
-----------------------------------------------------------------------------
No Matching Entries Found

A:BGP_Pod1_R5# show router bgp neighbor 10.100.100.1 advertised-routes ipv4

=============================================================================
BGP Router ID:10.100.100.5 AS:65100 Local AS:65100
=============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete

=============================================================================
BGP IPv4 Routes
=============================================================================
Flag Network LocalPref MED
Nexthop (Router) Path-Id Label
As-Path
-----------------------------------------------------------------------------
No Matching Entries Found

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 29
iBGP Verification
iBGP [cont.]
Verification [cont.]

Switch to notes view!

A:BGP_Pod1_R5# show router bgp neighbor 10.100.100.1 received-routes ipv4
=============================================================================
BGP Router ID:10.100.100.5 AS:65100 Local AS:65100
=============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete

=============================================================================
BGP IPv4 Routes
=============================================================================
Flag Network LocalPref MED
Nexthop (Router) Path-Id Label
©
As-Path
30Nokia 2020 Nokia Confidential
-----------------------------------------------------------------------------
No Matching Entries Found

That is the reason why the command show router bgp summary revives that no BGP
routes are being exchanged within an AS although the iBGP neighbor connections have been
established successfully.

By default, BGP speakers import and export only BGP routes. No direct, or IGP-learned routes,
are exchanged through BGP by default. Therefore, all loopback addresses ( such as IP access
services or customer networks) on the Edge routers are not visible by the other routers within
the AS.

In the next lab, we will add the BGP export policy onto the Edge routers so that all the routers
within as AS have visibility about the IP access services or customer networks terminating onto
the Edge routers.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 30
 Edge Router iBGP Access Service
Export Policy

31Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 31
iBGP Export Policy Objectives

We now understand that, by default, a BGP speaker exchanges only BGP routes over iBGP connections.
All other routes, such as direct or IGP-learned routes, need export policies so that other iBGP peers can
learn those routes.

The objectives of this lab are:

• To configure and understand the route policy to export the Edge routers’ loopback addresses (or IP access service) to
the other iBGP peers within an AS
• To configure the basic BGP attributes that are set for the exported routes, such as next-hop, communities, local-
preference and origin codes

32Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 32
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number.

Initial rollback config file’s comment – BGP – iBGP full mesh neighbor in AS.

Final rollback config file’s comment - BGP - Edge router export access service within its AS.

Use the command /admin rollback revert X to set the initial lab condition, if
necessary.

33Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 33
iBGP Export Config

Each group of students configures their Edge routers to export the following loopback addresses that have been
predefined in the SR config.

R5 – 172.17.100.5/24 and 172.17.101.5/24

R6 - 172.17.102.6/24 and 172.17.103.6/24
R7 – 172.65.200.7/24 and 172.65.201.7/24
R8 - 172.65.202.8/24 and 172.65.203.8/24

Note again that the loopback addresses represent the IP Access Service or the customer networks that terminate onto
the Edge routers.

If the iBGP export policy is successful, all routers within the AS can reach or ping to these loopback addresses or customer
networks.

34Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 34
iBGP Export Config [cont.]

On the Edge routers, develop an iBGP export policy to export all access service routes to all iBGP peers.
The following is a sample config:
policy-options
begin
prefix-list "access_services"
prefix 172.17.100.0/24 longer
...
exit
policy-statement "export_access_services"
entry 10
from
protocol direct
prefix-list "access_services"
exit
action accept
exit
exit
default-action reject
exit
commit
exit

35Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 35
iBGP Export Config [cont.]

Include the newly developed export policy onto the iBGP setup:

A:BGP_Pod3_R7>config>router>bgp# info
----------------------------------------------
group "iBGP"
description "AS65200 mesh"
family ipv4
type internal
export "export_access_services"
peer-as 65200
neighbor 10.200.200.3
description "BGP_Pod3_R3"
exit
neighbor 10.200.200.4
description "BGP_Pod4_R4"
exit
neighbor 10.200.200.8
description "BGP_Pod4_R8"
exit
exit

36Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 36
iBGP Export Config [cont.]

Use the following commands for this lab:

• config router policy-option
• config router bgp summary
• show router bgp routes
• show route route-table
• show router bgp routes 172.xx.x00.x
• show router bgp routes 172.xx.x00.x details
• show router bgp routes 172.xx.x00.x hunt
• show router bgp neighbor 10.x.x.x advertised-routes
• show router bgp neighbor 10.x.x.x received-routes

37Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 37
iBGP Export
iBGP Policy
Export Config
Policy Config– R5
– R5and
andR6
R6
Exercise 3.1:
iBGP Access
Switch to Service Export Policy (R5 and R6):
notes view!

Each group examines the pre-configured IP access service routes (or loopback addresses) at
the Edge router.

A:BGP_Pod1_R5>config>router# info
----------------------------------------------
interface "access_service1"
address 172.17.100.5/24
loopback
no shutdown
exit
interface "access_service2"
address 172.17.101.5/24
loopback
38Nokia 2020
© Nokia Confidential
no shutdown
exit

Each group develops the following export policy at the Edge router and adds it onto the BGP’s
iBGP export policy.

R5:

A:BGP_Pod1_R5>config>router# info
----------------------------------------------
policy-options
begin
prefix-list "access_services"
prefix 172.17.100.0/24 longer
prefix 172.17.101.0/24 longer
exit
policy-statement "export_access_services"
entry 10
from
protocol direct
prefix-list "access_services"
exit
action accept
exit
exit
default-action reject
exit
commit
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 38
iBGP Export
iBGP Policy
Export Config
Policy Config– R5
– R5and
andR6
R6[cont.]
[cont.]
R5:
Switch to notes view!
#--------------------------------------------------
echo "BGP Configuration"
#--------------------------------------------------
bgp
group "iBGP"
description "AS65100 iBGP Mesh"
family ipv4
type internal
export "export_access_services"
peer-as 65100
neighbor 10.100.100.1
description "BGP_Pod1_R1"
exit
neighbor 10.100.100.2
39Nokia 2020
©
description "BGP_Pod2_R2"
Nokia Confidential
exit
neighbor 10.100.100.6
description "BGP_Pod2_R6"
exit
exit
no shutdown

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 39
iBGP Export
iBGP Policy
Export Config
Policy Config– R5
– R5and
andR6
R6[cont.]
[cont.]
R6:
Switch to notes view!
A:BGP_Pod2_R6>config>router# info
---------------------------------------------------
policy-options
begin
prefix-list "access_services"
prefix 172.17.102.0/24 longer
prefix 172.17.103.0/24 longer
exit
policy-statement "export_access_services"
entry 10
from
protocol direct
prefix-list "access_services"
exit
40Nokia 2020
©
action accept Nokia Confidential
exit
exit
default-action reject
exit
commit
exit

bgp
group "iBGP"
description "AS65100 iBGP Mesh"
family ipv4
type internal
export "export_access_services"
peer-as 65100
neighbor 10.100.100.1
description "BGP_Pod1_R1"
exit
neighbor 10.100.100.2
description "BGP_Pod2_R2"
exit
neighbor 10.100.100.5
description "BGP_Pod1_R5"
exit
exit
no shutdown
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 40
iBGP Export
iBGP Policy
Export Config
Policy Config– R7
– R7and
andR8
R8
iBGP Access Service Export Policy R7 and R8:
R7: Switch to notes view!

A:BGP_Pod3_R7>config>router# info
----------------------------------------------
policy-options
begin
prefix-list "access_services"
prefix 172.65.200.0/24 longer
prefix 172.65.201.0/24 longer
exit
policy-statement "export_access_services"
entry 10
from
protocol direct
prefix-list "access_services"
41Nokia 2020
© exit Nokia Confidential

action accept
exit
exit
default-action reject
exit
commit
exit

bgp
group "iBGP"
description "AS65200 mesh"
family ipv4
type internal
export "export_access_services"
peer-as 65200
neighbor 10.200.200.3
description "BGP_Pod3_R3"
exit
neighbor 10.200.200.4
description "BGP_Pod4_R4"
exit
neighbor 10.200.200.8
description "BGP_Pod4_R8"
exit
exit
no shutdown
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 41
iBGP Export
iBGP Policy
Export Config
Policy Config– R7
– R7and
andR8
R8[cont.]
[cont.]
R8:
Switch to notes view!
A:BGP_Pod4_R8>config>router# info
----------------------------------------------
policy-options
begin
prefix-list "access_services"
prefix 172.65.202.0/24 longer
prefix 172.65.203.0/24 longer
exit
policy-statement "export_access_services"
entry 10
from
protocol direct
prefix-list "access_services"
exit
42Nokia 2020
©
action accept Nokia Confidential
exit
exit
default-action reject
exit
commit
exit

bgp
group "iBGP"
description "AS65200 mesh"
family ipv4
type internal
export "export_access_services"
peer-as 65200
neighbor 10.200.200.3
description "BGP_Pod3_R3"
exit
neighbor 10.200.200.4
description "BGP_Pod4_R4"
exit
neighbor 10.200.200.7
description "BGP_Pod3_R7"
exit
exit
no shutdown
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 42
iBGP Export
iBGP Policy
Export Verification
Policy Verification
Routing Table and BGP Routes:
Switch to notes view!
If the Edge routers’ export policy is successfully applied to the iBGP config, all the routers
within the AS should receive the Edge routers’ loopback addresses and can ping to the
loopback addresses to verify reachability.

A:BGP_Pod1_R1# show router route-table

==============================================================================
Route Table (Router: Base)
==============================================================================
Dest Prefix[Flags] Type Proto Age
Pref
Next Hop[Interface Name] Metric
------------------------------------------------------------------------------
10.1.2.0/27 Local Local 16h36m13s 0
43Nokia 2020
© Nokia Confidential
toR2 0
10.1.3.0/27 Local Local 16h36m13s 0
toR3 0
10.1.5.0/27 Local Local 16h36m13s 0
toR5 0
10.2.6.0/27 Remote OSPF 16h34m16s 10
10.1.2.2 20
10.5.6.0/27 Remote OSPF 14h59m19s 10
10.1.5.5 20
10.100.100.1/32 Local Local 16h36m13s 0
system 0
10.100.100.2/32 Remote OSPF 16h34m59s 10
10.1.2.2 10
10.100.100.5/32 Remote OSPF 16h34m37s 10
10.1.5.5 10
10.100.100.6/32 Remote OSPF 16h34m09s 10
10.1.2.2 20
172.17.100.0/24 Remote BGP 00h04m20s 170
10.1.5.5 10
172.17.101.0/24 Remote BGP 00h04m20s 170
10.1.5.5 10
172.17.102.0/24 Remote BGP 00h03m15s 170
10.1.2.2 20
172.17.103.0/24 Remote BGP 00h03m15s 170
10.1.2.2 20
------------------------------------------------------------------------------
No. of Routes: 13
Flags: n = Number of times nexthop is repeated
B = BGP backup route available
L = LFA nexthop available
S = Sticky ECMP requested

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 43
iBGP Export
iBGP Policy
Export Verification
Policy Verification[cont.]
[cont.]

Switch to notes view!

AS61000

A:BGP_Pod1_R1# ping 172.17.100.5

PING 172.17.100.5 56 data bytes
64 bytes from 172.17.100.5: icmp_seq=1 ttl=64 time=1.86ms.
64 bytes from 172.17.100.5: icmp_seq=2 ttl=64 time=0.783ms.

A:BGP_Pod1_R1# ping 172.17.101.5

PING 172.17.101.5 56 data bytes
64 bytes from 172.17.101.5: icmp_seq=1 ttl=64 time=1.42ms.
64 bytes from 172.17.101.5: icmp_seq=2 ttl=64 time=1.74ms.

A:BGP_Pod1_R1# ping 172.17.102.6

PING 172.17.102.6 56 data bytes
64 ©44
bytes
Nokia 2020
from 172.17.102.6: icmp_seq=1 ttl=63 time=3.16ms.
Nokia Confidential
64 bytes from 172.17.102.6: icmp_seq=2 ttl=63 time=2.75ms.

A:BGP_Pod1_R1# ping 172.17.103.6

PING 172.17.103.6 56 data bytes
64 bytes from 172.17.103.6: icmp_seq=1 ttl=63 time=2.54ms.
64 bytes from 172.17.103.6: icmp_seq=2 ttl=63 time=2.95ms.

AS62000

A:BGP_Pod3_R3>config>router# ping 172.65.200.7

PING 172.65.200.7 56 data bytes
64 bytes from 172.65.200.7: icmp_seq=1 ttl=64 time=1.54ms.
64 bytes from 172.65.200.7: icmp_seq=2 ttl=64 time=1.70ms.

A:BGP_Pod3_R3>config>router# ping 172.65.201.7

PING 172.65.201.7 56 data bytes
64 bytes from 172.65.201.7: icmp_seq=1 ttl=64 time=1.42ms.
64 bytes from 172.65.201.7: icmp_seq=2 ttl=64 time=1.28ms.

A:BGP_Pod3_R3>config>router# ping 172.65.202.8

PING 172.65.202.8 56 data bytes
64 bytes from 172.65.202.8: icmp_seq=1 ttl=63 time=2.52ms.
64 bytes from 172.65.202.8: icmp_seq=2 ttl=63 time=3.01ms.

A:BGP_Pod3_R3>config>router# ping 172.65.203.8

PING 172.65.203.8 56 data bytes
64 bytes from 172.65.203.8: icmp_seq=1 ttl=63 time=2.23ms.
64 bytes from 172.65.203.8: icmp_seq=2 ttl=63 time=6.81ms.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 44
iBGP Export
iBGP Policy
Export Verification
Policy Verification[cont.]
[cont.]
Edge Router’s iBGP Export Policy Verification:
Switch to notes view!
The loopback address 172.17.100.5/24 belongs to R5, and the following command shows that
R5 advertises this loopback address to all its iBGP peers in the AS through their iBGP neighbor
connections.

A:BGP_Pod1_R5# show router bgp routes 172.17.100.0/24 hunt

==============================================================================
BGP Router ID:10.100.100.5 AS:65100 Local AS:65100
==============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete

==============================================================================
45Nokia 2020
© Nokia Confidential
BGP IPv4 Routes
==============================================================================
------------------------------------------------------------------------------
RIB In Entries
------------------------------------------------------------------------------

------------------------------------------------------------------------------
RIB Out Entries
------------------------------------------------------------------------------
Network : 172.17.100.0/24
Nexthop : 10.100.100.5
Path Id : None
To : 10.100.100.6
Res. Protocol : INVALID Res. Metric : 0
Res. Nexthop : n/a
Local Pref. : 100 Interface Name : NotAvailable
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : n/a
Connector : None
Community : No Community Members
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.6
Origin : IGP
AS-Path : No As-Path
Route Tag : 0
Neighbor-AS : n/a
Orig Validation: NotFound
Source Class : 0 Dest Class : 0

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 45
iBGP Export
iBGP Policy
Export Verification
Policy Verification[cont.]
[cont.]

Switch to notes view!

Network : 172.17.100.0/24
Nexthop : 10.100.100.5
Path Id : None
To : 10.100.100.2
Res. Protocol : INVALID Res. Metric : 0
Res. Nexthop : n/a
Local Pref. : 100 Interface Name : NotAvailable
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : n/a
Connector : None
Community : No Community Members
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.2
Origin
46Nokia 2020
©
: IGP Nokia Confidential
AS-Path : No As-Path
Route Tag : 0
Neighbor-AS : n/a
Orig Validation: NotFound
Source Class : 0 Dest Class : 0

Network : 172.17.100.0/24
Nexthop : 10.100.100.5
Path Id : None
To : 10.100.100.1
Res. Protocol : INVALID Res. Metric : 0
Res. Nexthop : n/a
Local Pref. : 100 Interface Name : NotAvailable
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : n/a
Connector : None
Community : No Community Members
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.1
Origin : IGP
AS-Path : No As-Path
Route Tag : 0
Neighbor-AS : n/a
Orig Validation: NotFound
Source Class : 0 Dest Class : 0

------------------------------------------------------------------------------
Routes : 3

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 46
iBGP Advertised
iBGP Routes
Advertised Verification
Routes Verification
BGP Routes Advertised and Received:
Switch to notes view!
The following command shows the Edge router, R5 has successfully exported all its loopback
addresses (or access service routes) to its iBGP peer, R1:

A:BGP_Pod1_R1# show router bgp neighbor 10.100.100.5 received-routes ipv4

==============================================================================
BGP Router ID:10.100.100.1 AS:65100 Local AS:65100
==============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete

==============================================================================
BGP IPv4 Routes
47Nokia 2020
© Nokia Confidential
==============================================================================
Flag Network LocalPref MED
Nexthop (Router) Path-Id Label
As-Path
------------------------------------------------------------------------------
u*>i 172.17.100.0/24 100 None
10.100.100.5 None -
No As-Path
u*>i 172.17.101.0/24 100 None
10.100.100.5 None -
No As-Path
------------------------------------------------------------------------------
Routes : 2

Since there is no BGP export policy on the Border router, no BGP routes are advertised by
Core routers back to Edge routers.

A:BGP_Pod1_R1# show router bgp neighbor 10.100.100.5 advertised-routes ipv4

==============================================================================
BGP Router ID:10.100.100.1 AS:65100 Local AS:65100
==============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete

==============================================================================
BGP IPv4 Routes
==============================================================================
Flag Network LocalPref MED
Nexthop (Router) Path-Id Label
As-Path
------------------------------------------------------------------------------
No Matching Entries Found

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 47
AddAdd
Loopback Address
Loopback (R7
Address (R7and
andR8)
R8)
iBGP Route Advertisement and Selection:
Switch to notes view!
Since each iBGP speaker has Full Mesh iBGP connections to each other, they do not
re-forward the received iBGP routes. Since there is only one copy or originator for each route,
the iBGP peers do not have to perform any BGP route selection.

A:BGP_Pod1_R1# show router bgp routes 172.17.103.0/24 detail

==============================================================================
BGP Router ID:10.100.100.1 AS:65100 Local AS:65100
==============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete

==============================================================================
48Nokia 2020
© Nokia Confidential
BGP IPv4 Routes
==============================================================================
Original Attributes

Network : 172.17.103.0/24
Nexthop : 10.100.100.6
Path Id : None
From : 10.100.100.6
Res. Protocol : OSPF Res. Metric : 20
Res. Nexthop : 10.1.2.2
Local Pref. : 100 Interface Name : toR2
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 20
Connector : None
Community : No Community Members
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.6
Fwd Class : None Priority : None
Flags : Used Valid Best IGP
Route Source : Internal
AS-Path : No As-Path
Route Tag : 0
Neighbor-AS : n/a
Orig Validation: NotFound
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 00h33m38s

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 48
AddAdd
Loopback Address
Loopback (R7
Address (R7and
andR8)
R8)[cont.]
[cont.]

Switch to notes view!

Modified Attributes

Network : 172.17.103.0/24
Nexthop : 10.100.100.6
Path Id : None
From : 10.100.100.6
Res. Protocol : OSPF Res. Metric : 20
Res. Nexthop : 10.1.2.2
Local Pref. : 100 Interface Name : toR2
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 20
Connector : None
Community : No Community Members
Cluster : No Cluster Members
Originator
49Nokia 2020
© Id : None Peer Router Id
Nokia Confidential : 10.100.100.6
Fwd Class : None Priority : None
Flags : Used Valid Best IGP
Route Source : Internal
AS-Path : No As-Path
Route Tag : 0
Neighbor-AS : n/a
Orig Validation: NotFound
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 00h33m38s

------------------------------------------------------------------------------
------------------------------------------------------------------------------
Routes : 1

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 49
Route Export
Route Verification
Export Verification
The edge routers’ loopback addresses are received by their Border routers with the following
default BGP
Switch to attribute:
notes view!

Local Preference = 100

MED = None
Origin = IGP

A:BGP_Pod1_R1# show router bgp routes 172.17.101.0/24 detail

==============================================================================
BGP Router ID:10.100.100.1 AS:65100 Local AS:65100
==============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete
50Nokia 2020
© Nokia Confidential
==============================================================================
BGP IPv4 Routes
==============================================================================
Original Attributes

Network : 172.17.101.0/24
Nexthop : 10.100.100.5
Path Id : None
From : 10.100.100.5
Res. Protocol : OSPF Res. Metric : 10
Res. Nexthop : 10.1.5.5
Local Pref. : 100 Interface Name : toR5
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 10
Connector : None
Community : No Community Members
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.5
Fwd Class : None Priority : None
Flags : Used Valid Best IGP
Route Source : Internal
AS-Path : No As-Path
Route Tag : 0
Neighbor-AS : n/a
Orig Validation: NotFound
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 00h36m22s

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 50
Route Export
Route Verification
Export Verification[cont.]
[cont.]

Switch to notes view!

Modified Attributes:

Network : 172.17.101.0/24
Nexthop : 10.100.100.5
Path Id : None
From : 10.100.100.5
Res. Protocol : OSPF Res. Metric : 10
Res. Nexthop : 10.1.5.5
Local Pref. : 100 Interface Name : toR5
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 10
Connector : None
Community : No Community Members
Cluster : No Cluster Members
Originator
51Nokia 2020
©
Id : None Peer Router Id
Nokia Confidential
: 10.100.100.5
Fwd Class : None Priority : None
Flags : Used Valid Best IGP
Route Source : Internal
AS-Path : No As-Path
Route Tag : 0
Neighbor-AS : n/a
Orig Validation: NotFound
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 00h36m22s

------------------------------------------------------------------------------
------------------------------------------------------------------------------
Routes : 1

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 51
 Border Router eBGP and Default
Traffic Path

52Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 52
Introduction to eBGP Lab

We just completed the iBGP export policy lab where routers within an AS can reach the Edge routers’
access service addresses or loopback addresses for the customer networks.

The end goal of most BGP setups is to enable customers’ networks terminated at the Edge routers (i.e.,
IP access service) to reach the Internet or other ASes through the Border routers of the AS. This can be
achieved by implementing eBGP connections among the Border routers of the ASes.

53Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 53
eBGP Lab Setup

AS 65100 Edge Router

Core/Border Router
R5 R2 R6
R1
eBGP Neighbor

iBGP Neighbor

R3 R4

eBGP connections are set up between the Border routers of AS 65100 (R1 and R2) and AS 65200 (R3
and R4) so that customer networks terminating at the Edge routers of the two ASes can reach each
other.

54Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 54
Lab Objectives

The objectives of this lab exercise are to:

• Set up eBGP connections between AS 65100 and AS 65200 for the exchange of their IP access service routes or
customer networks.
• Understand the default eBGP inter-AS traffic flow so that we can implement our desired inter-AS traffic control in the
later lab exercises.
• Understand the default eBGP route import and export behaviors on the Border routers.
• Understand the next-hop-self setting in the Border routers’ iBGP config to enable their Edge routers to resolve the
next-hop to another AS through the Border routers.
• BGP route-selection process.

55Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 55
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number.

Initial rollback config file’s comment – BGP - Edge router export access service within its AS.

Final rollback config file’s comment – BGP – eBGP peering with iBGP next-hop-self at Border
routers.

Use the command /admin rollback revert X to set the initial lab condition, if
necessary.

56Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 56
Border Router eBGP Config and Verification

On the Border routers of each AS, develop an eBGP connection to the neighboring AS Border routers for exchange
customer network routes.
A:BGP_Pod1_R1>config>router>bgp# info
----------------------------------------------
group "eBGP"
description "eBGP to AS65200"
family ipv4
loop-detect discard-route
type external
peer-as 65200
neighbor 10.1.3.3
description "BGP_Pod3_R3"
exit
exit

Set the loop-detect to discard-route for AS loopback routes.

Since a BGP speaker exports and imports its BGP routes by default and there is no special export policy on the eBGP
connection, all the AS BGP routes (for example, customer networks) are exchanged although they use the default BGP
behavior to route traffic across the ASes.

57Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 57
Border Router eBGP Config and Verification [cont.]

On the Border routers, use the following commands to verify the eBGP connections:
• config router bgp summary
• show router bgp routes
• show route route-table
• show router bgp routes 172.xx.x00.x
• show router bgp routes 172.xx.x00.x details
• show router bgp routes 172.xx.x00.x hunt
• show router bgp neighbor 10.x.x.x advertised-routes
• show router bgp neighbor 10.x.x.x received-routes

Explain the Border router’s route-selection process and priority routes.

58Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 58
Border Router
Border eBGP
Router Config
eBGP Config
Exercise 4.1:
1. Switch
On each
to Border router, configure the eBGP setup as follows:
notes view!
R1:

A:BGP_Pod1_R1>config>router>bgp# info
----------------------------------------------
group "eBGP"
description "eBGP to AS65200"
family ipv4
loop-detect discard-route
type external
peer-as 65200
neighbor 10.1.3.3
description "BGP_Pod3_R3"
exit
exit
59Nokia 2020
© Nokia Confidential

R2:

A:BGP_Pod2_R2>config>router>bgp# info
----------------------------------------------
group "eBGP"
description "eBGP to AS65200"
family ipv4
loop-detect discard-route
type external
peer-as 65200
neighbor 10.2.4.4
description "BGP_Pod4_R4"
exit
exit

R3:

A:BGP_Pod3_R3>config>router>bgp# info
----------------------------------------------
group "eBGP"
description "eBGP to AS65100"
family ipv4
loop-detect discard-route
type external
peer-as 65100
neighbor 10.1.3.1
description "BGP_Pod1_R1"
exit
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 59
Border Router
Border eBGP
Router Config
eBGP Config[cont.]
[cont.]
R4:
Switch to notes view!

A:BGP_Pod4_R4>config>router>bgp# info
----------------------------------------------
group "eBGP"
description "eBGP to AS65100"
family ipv4
loop-detect discard-route
type external
peer-as 65100
neighbor 10.2.4.2
description "BGP_Pod2_R2"
exit
exit

60Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 60
Border Router
Border eBGP
Router Config
eBGP Config[cont.]
[cont.]
Exercise 4.2:
Verify the to
Switch eBGP connection.
notes view! eBGP connection should be set up between the two Border
routers of AS 65100 and AS 65200.

A:BGP_Pod1_R1# show router bgp summary

==============================================================================
BGP Router ID:10.100.100.1 AS:65100 Local AS:65100
==============================================================================
BGP Admin State : Up BGP Oper State : Up
Total Peer Groups : 2 Total Peers : 4
Total VPN Peer Groups : 0 Total VPN Peers : 0
Total BGP Paths : 18 Total Path Memory : 6200
<< skip >>

==============================================================================
BGP Summary
==============================================================================
61Nokia 2020
© Nokia Confidential

Legend : D - Dynamic Neighbor

==============================================================================
Neighbor
Description
AS PktRcvd InQ Up/Down State|Rcv/Act/Sent (Addr Family)
PktSent OutQ
------------------------------------------------------------------------------
10.1.3.3
BGP_Pod3_R3
65200 12 0 00h03m01s 4/4/8 (IPv4)
14 0
10.100.100.2
BGP_Pod2_R2
65100 164 0 01h20m16s 0/0/4 (IPv4)
171 0
10.100.100.5
BGP_Pod1_R5
65100 162 0 01h17m43s 2/2/4 (IPv4)
171 0
10.100.100.6
BGP_Pod2_R6
65100 159 0 01h17m17s 2/2/4 (IPv4)
171 0
------------------------------------------------------------------------------

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 61
Border Router
Border eBGP
Router Route
eBGP RouteSelection
Selection
Exercise 4.3:
Since theretoare
Switch twoview!
notes Border routers for each AS for redundancy purpose, every eBGP route
shows up on the destination Border router as eBGP and iBGP routes. For example, for the
prefix 172.65.200.0/24 from AS 65200, it appears to the Border router R1 as:
• An eBGP route from R3
• An iBGP route from R2

The following shows the eBGP and iBGP routes for 172.65.200.0/24 on R1:

A:BGP_Pod1_R1# show router bgp routes 172.65.200.0/24

==============================================================================
BGP Router ID:10.100.100.1 AS:65100 Local AS:65100
==============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
62Nokia 2020
© l - leaked, x - stale, > - best, b - backup, p - purge
Nokia Confidential

Origin codes : i - IGP, e - EGP, ? - incomplete

==============================================================================
BGP IPv4 Routes
==============================================================================
Flag Network LocalPref MED
Nexthop (Router) Path-Id Label
As-Path
------------------------------------------------------------------------------
u*>i 172.65.200.0/24 None None
10.1.3.3 None -
65200
i 172.65.200.0/24 100 None
10.2.4.4 None -
65200
------------------------------------------------------------------------------
Routes : 2

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 62
Border Router
Border eBGP
Router Route
eBGP RouteSelection
Selection[cont.]
[cont.]
Only the route from R3 (eBGP) is valid (*). The other route from R2 is invalid for R1 beacuse R1
cannot resolve
Switch the view!
to notes next hop address of 10.2.4.4. The following command explains the finding.

A:BGP_Pod1_R1>config>router>bgp# show router bgp routes 172.65.200.0/24 detail

==============================================================================
BGP Router ID:10.100.100.1 AS:65100 Local AS:65100
==============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete
==============================================================================
BGP IPv4 Routes
==============================================================================
Original Attributes
Network : 172.65.200.0/24
Nexthop
63Nokia 2020
© : 10.1.3.3 Nokia Confidential

Path Id : None
From : 10.1.3.3
Res. Protocol : LOCAL Res. Metric : 0
Res. Nexthop : 10.1.3.3
Local Pref. : n/a Interface Name : toR3
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 0
Connector : None
Community : No Community Members
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.200.200.3
Fwd Class : None Priority : None
Flags : Used Valid Best IGP
Route Source : External
AS-Path : 65200
Route Tag : 0
Neighbor-AS : 65200
Orig Validation: NotFound
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 00h12m04s

Modified Attributes

Network : 172.65.200.0/24
Nexthop : 10.1.3.3
Path Id : None
From : 10.1.3.3
Res. Protocol : LOCAL Res. Metric : 0
Res. Nexthop : 10.1.3.3
Local Pref. : None Interface Name : toR3
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 0
Connector : None
Community : No Community Members

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 63
Border Router
Border eBGP
Router Route
eBGP RouteSelection
Selection[cont.]
[cont.]

Switch to notes view!

Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.200.200.3
Fwd Class : None Priority : None
Flags : Used Valid Best IGP
Route Source : External
AS-Path : 65200
Route Tag : 0
Neighbor-AS : 65200
Orig Validation: NotFound
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 00h12m04s

------------------------------------------------------------------------------

Original Attributes
64Nokia 2020
© Nokia Confidential

Network : 172.65.200.0/24
Nexthop : 10.2.4.4
Path Id : None
From : 10.100.100.2
Res. Protocol : INVALID Res. Metric : 0
Res. Nexthop : Unresolved
Local Pref. : 100 Interface Name : NotAvailable
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 0
Connector : None
Community : No Community Members
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.2
Fwd Class : None Priority : None
Flags : Invalid IGP Nexthop-Unresolved
Route Source : Internal
AS-Path : 65200
Route Tag : 0
Neighbor-AS : 65200
Orig Validation: NotFound
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 00h09m30s

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 64
Border Router
Border eBGP
Router Route
eBGP RouteSelection
Selection[cont.]
[cont.]

Switch to notes view!

Modified Attributes

Network : 172.65.200.0/24
Nexthop : 10.2.4.4
Path Id : None
From : 10.100.100.2
Res. Protocol : INVALID Res. Metric : 0
Res. Nexthop : Unresolved
Local Pref. : 100 Interface Name : NotAvailable
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 0
Connector : None
Community : No Community Members
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.2
65Nokia 2020
© Nokia Confidential
Fwd Class : None Priority : None
Flags : Invalid IGP Nexthop-Unresolved
Route Source : Internal
AS-Path : 65200
Route Tag : 0
Neighbor-AS : 65200
Orig Validation: NotFound
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 00h10m15s

------------------------------------------------------------------------------
------------------------------------------------------------------------------
Routes : 2
==============================================================================

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 65
Border Router
Border eBGP
Router Route
eBGP RouteSelection
Selection[cont.]
[cont.]
The Border router, R1 selects the received eBGP route from R3 and R1 advertises this route to
all its connected
Switch iBGP
to notes and eBGP peers to:
view!
• R5 (10.100.100.5) - iBGP
• R6 (10.100.100.6) - iBGP
• R2 (10.100.100.2) - iBGP
• R3 (10.1.3.3) – eBGP, AS loopback route for R3

A:BGP_Pod1_R1>config>router>bgp# show router bgp routes 172.65.200.0/24 hunt

==============================================================================
BGP Router ID:10.100.100.1 AS:65100 Local AS:65100
==============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete
66Nokia 2020
© Nokia Confidential
==============================================================================
BGP IPv4 Routes
==============================================================================
------------------------------------------------------------------------------
RIB In Entries
------------------------------------------------------------------------------
Network : 172.65.200.0/24
Nexthop : 10.1.3.3
Path Id : None
From : 10.1.3.3
Res. Protocol : LOCAL Res. Metric : 0
Res. Nexthop : 10.1.3.3
Local Pref. : None Interface Name : toR3
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 0
Connector : None
Community : No Community Members
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.200.200.3
Fwd Class : None Priority : None
Flags : Used Valid Best IGP
Route Source : External
AS-Path : 65200
Route Tag : 0
Neighbor-AS : 65200
Orig Validation: NotFound
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 00h20m38s

Network : 172.65.200.0/24
Nexthop : 10.2.4.4
Path Id : None
From : 10.100.100.2
Res. Protocol : INVALID Res. Metric : 0

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 66
Border Router
Border eBGP
Router Route
eBGP RouteSelection
Selection[cont.]
[cont.]

Switch to notes view!

Res. Nexthop : Unresolved
Local Pref. : 100 Interface Name : NotAvailable
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 0
Connector : None
Community : No Community Members
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.2
Fwd Class : None Priority : None
Flags : Invalid IGP Nexthop-Unresolved
Route Source : Internal
AS-Path : 65200
Route Tag : 0
Neighbor-AS : 65200
Orig Validation: NotFound
67Nokia 2020
© Nokia Confidential
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 00h17m52s

------------------------------------------------------------------------------
RIB Out Entries
------------------------------------------------------------------------------
Network : 172.65.200.0/24
Nexthop : 10.1.3.3
Path Id : None
To : 10.100.100.2
Res. Protocol : INVALID Res. Metric : 0
Res. Nexthop : n/a
Local Pref. : 100 Interface Name : NotAvailable
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 0
Connector : None
Community : No Community Members
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.2
Origin : IGP
AS-Path : 65200
Route Tag : 0
Neighbor-AS : 65200
Orig Validation: NotFound
Source Class : 0 Dest Class : 0

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 67
Border Router
Border eBGP
Router Route
eBGP RouteSelection
Selection[cont.]
[cont.]

Switch to notes view!

Network : 172.65.200.0/24
Nexthop : 10.1.3.3
Path Id : None
To : 10.100.100.5
Res. Protocol : INVALID Res. Metric : 0
Res. Nexthop : n/a
Local Pref. : 100 Interface Name : NotAvailable
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 0
Connector : None
Community : No Community Members
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.5
Origin : IGP
AS-Path : 65200
68Nokia 2020
© Nokia Confidential
Route Tag : 0
Neighbor-AS : 65200
Orig Validation: NotFound
Source Class : 0 Dest Class : 0

Network : 172.65.200.0/24
Nexthop : 10.1.3.3
Path Id : None
To : 10.100.100.6
Res. Protocol : INVALID Res. Metric : 0
Res. Nexthop : n/a
Local Pref. : 100 Interface Name : NotAvailable
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 0
Connector : None
Community : No Community Members
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.6
Origin : IGP
AS-Path : 65200
Route Tag : 0
Neighbor-AS : 65200
Orig Validation: NotFound
Source Class : 0 Dest Class : 0

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 68
Border Router
Border eBGP
Router Route
eBGP RouteSelection
Selection[cont.]
[cont.]

Switch to notes view!

Network : 172.65.200.0/24
Nexthop : 10.1.3.1
Path Id : None
To : 10.1.3.3
Res. Protocol : INVALID Res. Metric : 0
Res. Nexthop : n/a
Local Pref. : n/a Interface Name : NotAvailable
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 0
Connector : None
Community : No Community Members
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.200.200.3
Origin : IGP
AS-Path : 65100 65200
69Nokia 2020
© Nokia Confidential
Route Tag : 0
Neighbor-AS : 65100
Orig Validation: NotFound
Source Class : 0 Dest Class : 0

------------------------------------------------------------------------------
Routes : 6
==============================================================================

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 69
Border Router
Border eBGP
Router Route
eBGP RouteSelection
Selection[cont.]
[cont.]

Note that when R1 advertises this route 172.65.200.0/24 to its iBGP peers, the next-hop for
thisSwitch
route to notes
is set to view!
10.1.3.3. All the iBGP peers in AS 65100 cannot resolve this next-hop except
R1 because R1 is directly connected to R3 with 10.1.3.1. Therefore, this route is not imported or
accepted by the iBGP peers in AS 65100.
Both routes are invalid for R5 because R5 cannot resolve the next-hop 10.1.3.3 or 10.2.4.4.

A:BGP_Pod1_R5# show router bgp routes 172.65.200.0/24

==============================================================================
BGP Router ID:10.100.100.5 AS:65100 Local AS:65100
==============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete
70Nokia 2020
© Nokia Confidential

==============================================================================
BGP IPv4 Routes
==============================================================================
Flag Network LocalPref MED
Nexthop (Router) Path-Id Label
As-Path
------------------------------------------------------------------------------
i 172.65.200.0/24 100 None
10.1.3.3 None -
65200
i 172.65.200.0/24 100 None
10.2.4.4 None -
65200
------------------------------------------------------------------------------
Routes : 2

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 70
Border Router
Border eBGP
Router Route
eBGP RouteSelection
Selection[cont.]
[cont.]
Therefore, R5 cannot reach 172.65.200.x beacuse the routes are not installed in its routing
table.
Switch to notes view!

A:BGP_Pod1_R5# show router route-table 172.65.200.0/24

==============================================================================
Route Table (Router: Base)
==============================================================================
Dest Prefix[Flags] Type Proto Age
Pref
Next Hop[Interface Name] Metric
------------------------------------------------------------------------------
------------------------------------------------------------------------------
No. of Routes: 0

71Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 71
Remote Route and next-hop-self

On the Border routers, add next-hop-self in their iBGP config so that their iBGP peers can resolve the next-hop of the
eBGP routes (that have now become the Border routers’ system addresses) advertised by the Border routers.
On all the Border routers R1, R2, R3, and R4, add next-hop-self onto the iBGP group.

A:BGP_Pod1_R1>config>router>bgp# info
----------------------------------------------
group "iBGP"
description "AS65100 iBGP Mesh"
family ipv4
next-hop-self
type internal
peer-as 65100
neighbor 10.100.100.2
description "BGP_Pod2_R2"
exit
neighbor 10.100.100.5
description "BGP_Pod1_R5"
exit
neighbor 10.100.100.6
description "BGP_Pod2_R6"
exit
exit
no shutdown

72Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 72
Remote Route
Remote and
Route next-hop-self
and next-hop-self[cont.]
[cont.]
Exercise 4.4:
On Switch
the Edge routers,
to notes re-verify the eBGP routes. All routes are valid now when next-hop-self is
view!
used at the Border routers. The eBGP prefix 172.65.200.0/24 now has a next-hop 10.100.100.1
instead of 10.1.3.3 and since 10.100.100.1 is the system interface of R1, R5 can resolve this
address and thus mark this route as valid.

A:BGP_Pod1_R5>config>router>bgp# show router bgp routes

==============================================================================
BGP Router ID:10.100.100.5 AS:65100 Local AS:65100
==============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete

==============================================================================
73Nokia 2020
© Nokia Confidential
BGP IPv4 Routes
==============================================================================
Flag Network LocalPref MED
Nexthop (Router) Path-Id Label
As-Path
------------------------------------------------------------------------------
u*>i 172.17.102.0/24 100 None
10.100.100.6 None -
No As-Path
u*>i 172.17.103.0/24 100 None
10.100.100.6 None -
No As-Path
u*>i 172.65.200.0/24 100 None
10.100.100.1 None -
65200
*i 172.65.200.0/24 100 None
10.100.100.2 None -
65200
u*>i 172.65.201.0/24 100 None
10.100.100.1 None -
65200
*i 172.65.201.0/24 100 None
10.100.100.2 None -
65200
u*>i 172.65.202.8/32 100 None
10.100.100.1 None -
65200
*i 172.65.202.8/32 100 None
10.100.100.2 None -
65200
u*>i 172.65.203.8/32 100 None
10.100.100.1 None -
65200
*i 172.65.203.8/32 100 None
10.100.100.2 None -
65200
------------------------------------------------------------------------------
Routes : 10

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 73
Remote Route
Remote and
Route next-hop-self
and next-hop-self[cont.]
[cont.]
Ping among the customer networks between AS 65100 and AS 65200 are now successful.
Switch to notes view!
AS 65100

A:BGP_Pod1_R5# ping 172.65.201.7 source 172.17.100.5

PING 172.65.201.7 56 data bytes
64 bytes from 172.65.201.7: icmp_seq=1 ttl=62 time=3.45ms.
64 bytes from 172.65.201.7: icmp_seq=2 ttl=62 time=3.29ms.

A:BGP_Pod1_R5# ping 172.65.202.8 source 172.17.100.5

PING 172.65.202.8 56 data bytes
64 bytes from 172.65.202.8: icmp_seq=1 ttl=61 time=4.29ms.
64 bytes from 172.65.202.8: icmp_seq=2 ttl=61 time=3.71ms.

AS 65200
74Nokia 2020
© Nokia Confidential

A:BGP_Pod3_R7# ping 172.17.100.5 source 172.65.200.7

PING 172.17.100.5 56 data bytes
64 bytes from 172.17.100.5: icmp_seq=1 ttl=62 time=4.28ms.
64 bytes from 172.17.100.5: icmp_seq=2 ttl=62 time=3.58ms.

A:BGP_Pod3_R7# ping 172.17.102.6 source 172.65.200.7

PING 172.17.102.6 56 data bytes
64 bytes from 172.17.102.6: icmp_seq=1 ttl=61 time=4.46ms.
64 bytes from 172.17.102.6: icmp_seq=2 ttl=61 time=5.13ms.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 74
Remote Route
Remote and
Route next-hop-self
and next-hop-self[cont.]
[cont.]
Since there are two Border routers for each AS, the Edge routers of the AS receive two
advertisement for aview!
Switch to notes given eBGP route from the two Border routers for redundancy purpose.
For example, R5 receives the eBGP route 172.65.200.0/24 advertisement from both R1 and R2
and they are both valid. R5 selects the route from R1 because it has a lower IGP next-hop cost
(R5 – R1 – R3 - R7) instead of (R5 – R2 – R1 – R3 - R7). There is the default BGP route selection
criteria.

A:BGP_Pod1_R5>config>router>bgp# show router bgp routes 172.65.200.0/24 detail

==============================================================================
BGP Router ID:10.100.100.5 AS:65100 Local AS:65100
==============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete
75Nokia 2020
© Nokia Confidential
==============================================================================
BGP IPv4 Routes
==============================================================================
Original Attributes

Network : 172.65.200.0/24
Nexthop : 10.100.100.1
Path Id : None
From : 10.100.100.1
Res. Protocol : OSPF Res. Metric : 10
Res. Nexthop : 10.1.5.1
Local Pref. : 100 Interface Name : toR1
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 10
Connector : None
Community : No Community Members
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.1
Fwd Class : None Priority : None
Flags : Used Valid Best IGP
Route Source : Internal
AS-Path : 65200
Route Tag : 0
Neighbor-AS : 65200
Orig Validation: NotFound
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 00h08m07s

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 75
Remote Route
Remote and
Route next-hop-self
and next-hop-self[cont.]
[cont.]

Switch to notes view!

Modified Attributes
Network : 172.65.200.0/24
Nexthop : 10.100.100.1
Path Id : None
From : 10.100.100.1
Res. Protocol : OSPF Res. Metric : 10
Res. Nexthop : 10.1.5.1
Local Pref. : 100 Interface Name : toR1
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 10
Connector : None
Community : No Community Members
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.1
Fwd Class : None Priority : None
76Nokia 2020
© Nokia Confidential
Flags : Used Valid Best IGP
Route Source : Internal
AS-Path : 65200
Route Tag : 0
Neighbor-AS : 65200
Orig Validation: NotFound
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 00h08m07s
------------------------------------------------------------------------------

Original Attributes
Network : 172.65.200.0/24
Nexthop : 10.100.100.2
Path Id : None
From : 10.100.100.2
Res. Protocol : OSPF Res. Metric : 20
Res. Nexthop : 10.1.5.1
Local Pref. : 100 Interface Name : toR1
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 20
Connector : None
Community : No Community Members
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.2
Fwd Class : None Priority : None
Flags : Valid IGP
TieBreakReason : NHCost
Route Source : Internal
AS-Path : 65200
Route Tag : 0
Neighbor-AS : 65200
Orig Validation: NotFound
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 00h07m45s

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 76
Remote Route
Remote and
Route next-hop-self
and next-hop-self[cont.]
[cont.]

Switch to notes view!

Modified Attributes

Network : 172.65.200.0/24
Nexthop : 10.100.100.2
Path Id : None
From : 10.100.100.2
Res. Protocol : OSPF Res. Metric : 20
Res. Nexthop : 10.1.5.1
Local Pref. : 100 Interface Name : toR1
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 20
Connector : None
Community : No Community Members
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.2
77Nokia 2020
© Nokia Confidential
Fwd Class : None Priority : None
Flags : Valid IGP
TieBreakReason : NHCost
Route Source : Internal
AS-Path : 65200
Route Tag : 0
Neighbor-AS : 65200
Orig Validation: NotFound
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 00h07m46s
------------------------------------------------------------------------------
------------------------------------------------------------------------------
Routes : 2

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 77
 Inter-AS Traffic Steering

78Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 78
Introduction to the Inter-AS Traffic Steering Lab

So far, we have established eBGP connections between the two ASes and we can verify that the two
ASes can reach each other’s customer networks or Edge routers’ loopback addresses.

There is no eBGP export policy at the Border routers, and the inter-AS traffic simply follow the default
BGP behavior, such as:
• eBGP - Prefer the received eBGP routes rather than the iBGP routes for a given prefix
• iBGP – Prefer routes from the sender that has the lowest next-hop cost

One of the key advantages of BGP over the other routing protocols is that we can easily deploy the
desired traffic steering policy to influence the traffic path within and outside of our own AS.

In this lab, we will implement traffic steering to keep the West-side and East-side traffic to R1, R3 (West)
and R2, R4 (East) as their primary path to avoid wide-area routing by using the destined AS.

79Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 79
Inter-AS Traffic Steering Requirements

The following are the inter-AS traffic requirements:

• Inter-AS traffic policies apply only to the customer access service prefixes 172.x.x.x only.
• R1 and R2 of AS 65100 are the West- and East-side traffic-entrance routers, for respectively.
• R3 and R4 of AS 65200 are the West- and East-side traffic-entrance routers, respectively.
̵ If traffic is destined to the East side of the customer network, such as R8., the traffic path from R5 should be
R5 – R1 – R2 – R4 – R8. It should not be R5 – R1 – R3 – R4 – R8 as because this utilizes the AS 65200 long- haul link
between R3 – R4 to route the AS 65100 traffic.
• Use AS 65100 and AS 65200 published community / local preference settings for inter-AS traffic steering because it is
the most common inter-AS traffic steering mechanism employed by most carriers.

80Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 80
Inter-AS Traffic Steering Requirements [cont.]

• The AS 65100 published local preference policy for community tagged routes:
Community Received Local Preference Set
65100:80 80
65100:120 120
• The AS 65200 published local preference policy for community tagged routes:
Community Received Local Preference Set
65200:80 80
65200:120 120
• For example, if an AS 65100 router receives a route with community 65100:120, the router sets the
route with Local Preference 120, which gives the router having higher priority than other routers with
the default 100 Local Preference.

81Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 81
Inter-AS Traffic Steering Lab Objectives

The objectives of this lab are to:

• Understand the general BGP network design to tag the Edge routers’ customer networks (or loopback addresses) with
community tags for the Border routers to apply inter-AS traffic steering policy
• Configure Edge routers with the iBGP export policy with communities for inter-AS traffic steering
• Configure Border routers with the eBGP import and export polices to take advantage of the Edge routers’ tagged
routes for inter-AS traffic steering
• Understand the common community/local preference inter-AS traffic steering method used by most carriers in the
world

82Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 82
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number.

Initial rollback config file’s comment – BGP - eBGP peering with iBGP next-hop-self at Border
routers.

Final rollback config file’s comment – BGP - Inter-AS East and West side traffic steering.

Use the command /admin rollback revert X to set the initial lab condition, if
necessary.

83Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 83
Default BGP
Default Traffic
BGP Flow
Traffic Flow
Exercise 5.1:
1. Switch
Beforetodeveloping the Inter-AS policy at the Border routers, let us check the current
notes view!
inter-AS traffic path by using the default BGP routing behavior without the import and
export policies.

AS 65100 – traceroute from R5 to R8

AS 65200 – traceroute from R7 to R6

The following explains the traceroute result from R5 to R8. Similar results are obtained for R7
to R6.

A:BGP_Pod1_R5# traceroute 172.65.202.8 source 172.17.100.5

traceroute to 172.65.202.8 from 172.17.100.5, 30 hops max, 40 byte packets
1 10.1.5.1 (10.1.5.1) 1.97 ms 3.07 ms 1.77 ms
2 10.1.3.3 (10.1.3.3) 2.77 ms 3.27 ms 3.05 ms
84Nokia 2020
© Nokia Confidential
3 10.3.4.4 (10.3.4.4) 3.88 ms 4.08 ms 3.82 ms
4 172.65.202.8 (172.65.202.8) 5.23 ms 7.52 ms 4.68 ms

From R5 to R8, the traffic path is R5 – R1 – R3 – R4 – R8. This is not our desired inter-AS traffic
path because R5 in AS 65100 relies on the West-to-East long-haul route R3-R4 to route its
traffic. This is not desirable.

The desirable traffic path from R5 to R8 should be R5 – R1 – R2 – R4 – R8. In this way, AS 65100
is using its long-haul resource to route the East-side traffic to the AS 65200 East-side
entrance router, R4.

On R1 in AS 65100, it should pick R2 as its next-hop router for prefix 172.65.202/0/24 because
it is the AS 65100 East-side exit router to the AS 65200 East-side entrance router R4. The
command show router bgp routes 172.65.200.0/24 detail on R1 shows
that it picked R3 instead of R2 because it preferred the eBGP routes from R3 instead of the
iBGP route from R2 for the prefix 172.65.200.0/24.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 84
Default BGP
Default Traffic
BGP Flow
Traffic [cont.]
Flow [cont.]

Switch to notes view!

A:BGP_Pod1_R1>config>router>bgp# show router bgp routes 172.65.200.0/24 hunt
==============================================================================
BGP Router ID:10.100.100.1 AS:65100 Local AS:65100
==============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete

==============================================================================
BGP IPv4 Routes
==============================================================================
------------------------------------------------------------------------------
RIB In Entries
------------------------------------------------------------------------------
Network : 172.65.200.0/24
85Nokia 2020
© Nokia Confidential
Nexthop : 10.1.3.3
Path Id : None
From : 10.1.3.3
Res. Protocol : LOCAL Res. Metric : 0
Res. Nexthop : 10.1.3.3
Local Pref. : None Interface Name : toR3
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 0
Connector : None
Community : No Community Members
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.200.200.3
Fwd Class : None Priority : None
Flags : Used Valid Best IGP
Route Source : External
AS-Path : 65200
Route Tag : 0
Neighbor-AS : 65200
Orig Validation: NotFound
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 01h52m34s

Network : 172.65.200.0/24
Nexthop : 10.100.100.2
Path Id : None
From : 10.100.100.2
Res. Protocol : OSPF Res. Metric : 10
Res. Nexthop : 10.1.2.2
Local Pref. : 100 Interface Name : toR2
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 10
Connector : None
Community : No Community Members

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 85
Default BGP
Default Traffic
BGP Flow
Traffic [cont.]
Flow [cont.]

Switch to notes view!

Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.2
Fwd Class : None Priority : None
Flags : Valid IGP
TieBreakReason : EBGPRoute
Route Source : Internal
AS-Path : 65200
Route Tag : 0
Neighbor-AS : 65200
Orig Validation: NotFound
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 01h13m25s

Similarly, AS 65200 R7 uses AS 65100 West-to-East long-haul bandwidth to route its traffic to
86Nokia 2020
© Nokia Confidential
R6.

A:BGP_Pod3_R7# traceroute 172.17.102.6 source 172.65.200.7

traceroute to 172.17.102.6 from 172.65.200.7, 30 hops max, 40 byte packets
1 10.3.7.3 (10.3.7.3) 2.00 ms 2.07 ms 2.01 ms
2 10.1.3.1 (10.1.3.1) 2.95 ms 3.04 ms 5.06 ms
3 10.1.2.2 (10.1.2.2) 4.01 ms 5.34 ms 4.23 ms
4 172.17.102.6 (172.17.102.6) 7.65 ms 8.46 ms 5.38 ms

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 86
Edge Router’s
Edge iBGP
Router’s Export
iBGP ExportPolicy
Policy
Before we implement any route policies on the Border routers, we need the Edge routers to
tag Switch
their IPtoaccess
notes service
view! route with the appropriate tags or communities so that the Border
routers can apply the necessary import and export policies to achieve the desired Inter-AS
traffic flow.

Exercise 5.2:
2. Each group applies the below iBGP route export policy to tag their IP access service routes
(or loopback addresses) with the appropriate community so that the Border routers can
implement the necessary route policy to achieve the desired inter-AS traffic flow.
R5:

A:BGP_Pod1_R5>config>router>policy-options# info
----------------------------------------------
prefix-list "access_services"
prefix 172.17.100.0/24 longer
87Nokia 2020
© Nokia Confidential
prefix 172.17.101.0/24 longer
exit
community "AS65100_East"
members "65100:26"
exit
community "AS65100_West"
members "65100:15"
exit
policy-statement "export_access_services"
entry 10
from
protocol direct
prefix-list "access_services"
exit
action accept
community add "AS65100_West"
exit
exit
default-action drop
exit
exit
----------------------------------------------

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 87
Edge Router’s
Edge iBGP
Router’s Export
iBGP ExportPolicy
Policy[cont.]
[cont.]

Switch to notes view!

A:BGP_Pod1_R5>config>router>bgp# info
----------------------------------------------
group "iBGP"
description "AS65100 iBGP Mesh"
family ipv4
type internal
export "export_access_services"
<< skip >>

R6:

A:BGP_Pod2_R6>config>router>policy-options# info
----------------------------------------------
prefix-list "access_services"
88Nokia 2020
© Nokia Confidential
prefix 172.17.102.0/24 longer
prefix 172.17.103.0/24 longer
exit
community "AS65100_East"
members "65100:26"
exit
community "AS65100_West"
members "65100:15"
exit
policy-statement "export_access_services"
entry 10
from
protocol direct
prefix-list "access_services"
exit
action accept
community add "AS65100_East"
exit
exit
default-action drop
exit
exit
----------------------------------------------

A:BGP_Pod2_R6>config>router>bgp# info
----------------------------------------------
group "iBGP"
description "AS65100 iBGP Mesh"
family ipv4
type internal
export "export_access_services"
<< skip >>

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 88
Edge Router’s
Edge iBGP
Router’s Export
iBGP ExportPolicy
Policy[cont.]
[cont.]
R7:
Switch to notes view!
A:BGP_Pod3_R7>config>router>policy-options# info
----------------------------------------------
prefix-list "access_services"
prefix 172.65.200.0/24 longer
prefix 172.65.201.0/24 longer
exit
community "AS65200_East"
members "65200:48"
exit
community "AS65200_West"
members "65200:37"
exit
policy-statement "export_access_services"
entry 10
89Nokia 2020
©
from Nokia Confidential
protocol direct
prefix-list "access_services"
exit
action accept
community add "AS65200_West"
exit
exit
default-action drop
exit
exit
----------------------------------------------

A:BGP_Pod3_R7>config>router>bgp# info
----------------------------------------------
group "iBGP"
description "AS65200 mesh"
family ipv4
type internal
export "export_access_services"
<< skip >>

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 89
Edge Router’s
Edge iBGP
Router’s Export
iBGP ExportPolicy
Policy[cont.]
[cont.]
R8:
Switch to notes view!
A:BGP_Pod4_R8>config>router>policy-options# info
----------------------------------------------
prefix-list "access_services"
prefix 172.65.202.0/24 longer
prefix 172.65.203.0/24 longer
exit
community "AS65200_East"
members "65200:48"
exit
community "AS65200_West"
members "65200:37"
exit
policy-statement "export_access_services"
entry 10
90Nokia 2020
©
from Nokia Confidential
protocol direct
prefix-list "access_services"
exit
action accept
community add "AS65200_East"
exit
exit
default-action drop
exit
exit
----------------------------------------------

A:BGP_Pod4_R8>config>router>bgp# info
----------------------------------------------
group "iBGP"
description "AS65200 mesh"
family ipv4
type internal
export "export_access_services"
<< skip >>

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 90
Edge Router’s
Edge iBGP
Router’s Export
iBGP ExportPolicy
Policy[cont.]
[cont.]
Exercise 5.3:
3. Switch
To verify that the
to notes iBGP export policy is working, check the route to see whether the desired
view!
community tag are set.

Route 172.17.100.0/24 is tagged with the community 65100:15, which indicate that it is a
West-side route. Therefore, the entrance router for AS65100 for this route should be R1 and
the exit router for AS 65200 should be R3.

A:BGP_Pod1_R1# show router bgp routes 172.17.100.0/24 detail

==============================================================================
BGP Router ID:10.100.100.1 AS:65100 Local AS:65100
==============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
91Nokia 2020
© l - leaked, x - stale, > - best, b - backup, p - purge
Nokia Confidential

Origin codes : i - IGP, e - EGP, ? - incomplete

==============================================================================
BGP IPv4 Routes
==============================================================================
Original Attributes

Network : 172.17.100.0/24
Nexthop : 10.100.100.5
Path Id : None
From : 10.100.100.5
Res. Protocol : OSPF Res. Metric : 10
Res. Nexthop : 10.1.5.5
Local Pref. : 100 Interface Name : toR5
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 10
Connector : None
Community : 65100:15
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.5
Fwd Class : None Priority : None
Flags : Used Valid Best IGP
Route Source : Internal
AS-Path : No As-Path
Route Tag : 0
Neighbor-AS : n/a
Orig Validation: NotFound
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 00h08m03s

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 91
Edge Router’s
Edge iBGP
Router’s Export
iBGP ExportPolicy
PolicyVerification
Verification

Switch to notes view!

Modified Attributes

Network : 172.17.100.0/24
Nexthop : 10.100.100.5
Path Id : None
From : 10.100.100.5
Res. Protocol : OSPF Res. Metric : 10
Res. Nexthop : 10.1.5.5
Local Pref. : 100 Interface Name : toR5
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 10
Connector : None
Community : 65100:15
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.5
92Nokia 2020
© Nokia Confidential
Fwd Class : None Priority : None
Flags : Used Valid Best IGP
Route Source : Internal
AS-Path : No As-Path
Route Tag : 0
Neighbor-AS : n/a
Orig Validation: NotFound
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 00h08m03s
------------------------------------------------------------------------------
------------------------------------------------------------------------------
Routes : 1

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 92
Edge Router’s
Edge iBGP
Router’s Export
iBGP ExportPolicy
PolicyVerification
Verification[cont.]
[cont.]
Exercise 5.4:
4. Switch
With Edge routers
to notes tagging their routes for East or West side, the Border routers can now
view!
implement the following polices to comply to the Inter-AS traffic steering requirements

R1:

A:BGP_Pod1_R1>config>router>policy-options# info
----------------------------------------------
community "AS65100_East" members "65100:26"
community "AS65100_West" members "65100:15"
community "AS65100_LP_low" members "65100:80"
community "AS65200_LP_low" members "65200:80"
community "AS65100_LP_high" members "65100:120"
community "AS65200_LP_high" members "65200:120"
as-path "AS65200_originated_routes" expression "65200+"
policy-statement "import_access_services_set_LP"
93Nokia 2020
© Nokia Confidential
entry 10
from
as-path "AS65200_originated_routes"
community "AS65100_LP_low"
exit
action accept
local-preference 80
exit
exit
entry 20
from
as-path "AS65200_originated_routes"
community "AS65100_LP_high"
exit
action accept
local-preference 120
exit
exit
exit
policy-statement "export_access_services_and_community"
entry 10
from
community "AS65100_East"
exit
action accept
community replace "AS65200_LP_low"
exit
exit
entry 20
from
community "AS65100_West"
exit
action accept
community replace "AS65200_LP_high"
exit
exit
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 93
Core Router’s
Core eBGP
Router’s Import
eBGP Importand
andExport
ExportPolicies
Policies

Switch to notes view!

A:BGP_Pod1_R1>config>router>bgp# info
----------------------------------------------
group "eBGP"
description "eBGP to AS65200"
family ipv4
loop-detect discard-route
type external
import "import_access_services_set_LP"
export "export_access_services_and_community"
peer-as 65200
neighbor 10.1.3.3
description "BGP_Pod3_R3"
exit
exit

R2: ©94Nokia 2020 Nokia Confidential

A:BGP_Pod2_R2>config>router>policy-options# info
----------------------------------------------
community "AS65100_East" members "65100:26"
community "AS65100_West" members "65100:15"
community "AS65100_LP_low" members "65100:80"
community "AS65200_LP_low" members "65200:80"
community "AS65100_LP_high" members "65100:120"
community "AS65200_LP_high" members "65200:120"
as-path "AS65200_originated_routes" expression "65200+"
policy-statement "import_access_services_set_LP"
entry 10
from
as-path "AS65200_originated_routes"
community "AS65100_LP_low"
exit
action accept
local-preference 80
exit
exit
entry 20
from
as-path "AS65200_originated_routes"
community "AS65100_LP_high"
exit
action accept
local-preference 120
exit
exit
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 94
Core Router’s
Core eBGP
Router’s Import
eBGP Importand
andExport
ExportPolicies
Policies[cont.]
[cont.]

Switch to notes view!

policy-statement "export_access_services_and_community"
entry 10
from
community "AS65100_East"
exit
action accept
community replace "AS65200_LP_high"
exit
exit
entry 20
from
community "AS65100_West"
exit
action accept
community replace "AS65200_LP_low"
exit
95Nokia 2020
© Nokia Confidential
exit
exit

A:BGP_Pod2_R2>config>router>bgp# info
----------------------------------------------
group "eBGP"
description "eBGP to AS65200"
family ipv4
loop-detect discard-route
type external
import "import_access_services_set_LP"
export "export_access_services_and_community"
peer-as 65200
neighbor 10.2.4.4
description "BGP_Pod4_R4"
exit
exit

R3:

A:BGP_Pod3_R3>config>router>policy-options# info
----------------------------------------------
community "AS65200_East" members "65200:48"
community "AS65200_West" members "65200:37"
community "AS65100_LP_low" members "65100:80"
community "AS65200_LP_low" members "65200:80"
community "AS65100_LP_high" members "65100:120"
community "AS65200_LP_high" members "65200:120"
as-path "AS65100_originated_routes" expression "65100+"

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 95
Core Router’s
Core eBGP
Router’s Import
eBGP Importand
andExport
ExportPolicies
Policies[cont.]
[cont.]

Switch to notes view!

policy-statement "import_access_services_set_LP"
entry 10
from
as-path "AS65100_originated_routes"
community "AS65200_LP_low"
exit
action accept
local-preference 80
exit
exit
entry 20
from
as-path "AS65100_originated_routes"
community "AS65200_LP_high"
exit
action accept
96Nokia 2020
© Nokia Confidential
local-preference 120
exit
exit
exit
policy-statement "export_access_services_and_community"
entry 10
from
community "AS65200_East"
exit
action accept
community replace "AS65100_LP_low"
exit
exit
entry 20
from
community "AS65200_West"
exit
action accept
community replace "AS65100_LP_high"
exit
exit
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 96
Core Router’s
Core eBGP
Router’s Import
eBGP Importand
andExport
ExportPolicies
Policies[cont.]
[cont.]

Switch to notes view!

A:BGP_Pod3_R3>config>router>bgp# info
----------------------------------------------
group "eBGP"
description "eBGP to AS65100"
family ipv4
loop-detect discard-route
type external
import "import_access_services_set_LP"
export "export_access_services_and_community"
peer-as 65100
neighbor 10.1.3.1
description "BGP_Pod1_R1"
exit
exit

97Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 97
Core Router’s
Core eBGP
Router’s Import
eBGP Importand
andExport
ExportPolicies
Policies[cont.]
[cont.]

Switch to notes view!

A:BGP_Pod4_R4>config>router>policy-options# info
----------------------------------------------
community "AS65200_East" members "65200:48"
community "AS65200_West" members "65200:37"
community "AS65100_LP_low" members "65100:80"
community "AS65200_LP_low" members "65200:80"
community "AS65100_LP_high" members "65100:120"
community "AS65200_LP_high" members "65200:120"
as-path "AS65100_originated_routes" expression "65100+"
policy-statement "import_access_services_set_LP"
entry 10
from
as-path "AS65100_originated_routes"
community "AS65200_LP_low"
exit
action accept
98Nokia 2020
© Nokia Confidential
local-preference 80
exit
exit
entry 20
from
as-path "AS65100_originated_routes"
community "AS65200_LP_high"
exit
action accept
local-preference 120
exit
exit
exit
policy-statement "export_access_services_and_community"
entry 10
from
community "AS65200_East"
exit
action accept
community replace "AS65100_LP_high"
exit
exit
entry 20
from
community "AS65200_West"
exit
action accept
community replace "AS65100_LP_low"
exit
exit
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 98
Core Router’s
Core eBGP
Router’s Import
eBGP Importand
andExport
ExportPolicies
Policies[cont.]
[cont.]

Switch to notes view!

A:BGP_Pod4_R4>config>router>bgp# info
----------------------------------------------
group "eBGP"
description "eBGP to AS65100"
family ipv4
loop-detect discard-route
type external
import "import_access_services_set_LP"
export "export_access_services_and_community"
peer-as 65100
neighbor 10.2.4.2
description "BGP_Pod2_R2"
exit
exit

99Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 99
Inter-AS Traffic
Inter-AS Steering
Traffic Verification
Steering Verification
Exercise 5.5:
5. Switch
Verify the traceroute
to notes view! from R5 to R8 and from R7 to R6 to ensure that the desired traffic
entrance routers are used.
R5:

A:BGP_Pod1_R5# traceroute 172.65.200.7 source 172.17.100.5

traceroute to 172.65.200.7 from 172.17.100.5, 30 hops max, 40 byte packets
1 10.1.5.1 (10.1.5.1) 1.82 ms 1.69 ms 2.07 ms
2 10.1.3.3 (10.1.3.3) 2.79 ms 2.98 ms 3.14 ms
3 172.65.200.7 (172.65.200.7) 4.32 ms 5.91 ms 4.16 ms

A:BGP_Pod1_R5# traceroute 172.65.202.8 source 172.17.100.5

traceroute to 172.65.202.8 from 172.17.100.5, 30 hops max, 40 byte packets
1 10.1.5.1 (10.1.5.1) 2.06 ms 1.99 ms 2.09 ms
2 10.1.2.2 (10.1.2.2) 2.90 ms 3.26 ms 3.28 ms
310 10.2.4.4 (10.2.4.4) 4.33 ms 4.25 ms 4.63 ms
4©0 Nokia 2020
172.65.202.8 (172.65.202.8) Nokia Confidential
6.98 ms 6.96 ms 5.46 ms

R7:

A:BGP_Pod3_R7# traceroute 172.17.100.5 source 172.65.200.7

traceroute to 172.17.100.5 from 172.65.200.7, 30 hops max, 40 byte packets
1 10.3.7.3 (10.3.7.3) 1.81 ms 1.85 ms 1.90 ms
2 10.1.3.1 (10.1.3.1) 3.57 ms 3.18 ms 3.09 ms
3 172.17.100.5 (172.17.100.5) 4.02 ms 3.95 ms 3.72 ms

A:BGP_Pod3_R7# traceroute 172.17.102.6 source 172.65.200.7

traceroute to 172.17.102.6 from 172.65.200.7, 30 hops max, 40 byte packets
1 10.3.7.3 (10.3.7.3) 1.95 ms 1.88 ms 1.54 ms
2 10.3.4.4 (10.3.4.4) 3.07 ms 3.43 ms 3.12 ms
3 10.2.4.2 (10.2.4.2) 4.74 ms 3.95 ms 6.29 ms
4 172.17.102.6 (172.17.102.6) 6.23 ms 4.67 ms 4.80 ms

The desired traffic entrance and exit routers for AS 65100 and AS 65200 are verified; they
comply with the inter-AS traffic steering requirement set up earlier.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 100
Inter-AS Traffic
Inter-AS Steering
Traffic Verification
Steering Verification[cont.]
[cont.]

On R1, it receives the R5’s route 172.17.100.0/24 that is tagged with Community 65100:15. This
is a Switch to notes
West-side view!
route. Since R1 is on the West side, it uses its eBGP export policy to advertise
this route to R3 with Community 65200:120. In other words, R3 gives a higher local preference
priority of 120 to this route and, thus, sets itself up as the exit router in AS 65200 for this
prefix.
The following command shows the RIB-IN for the prefix 172.17.100.0/24 with Community
65100:15 becoming a route with Community 65200:120 at RIB-OUT.

A:BGP_Pod1_R1# show router bgp routes 172.17.100.0/24 hunt

==============================================================================
BGP Router ID:10.100.100.1 AS:65100 Local AS:65100
==============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
10
1 Nokia 2020
©
l - leaked, x - stale, > - best, b - backup, p - purge
Nokia Confidential
Origin codes : i - IGP, e - EGP, ? - incomplete

==============================================================================
BGP IPv4 Routes
==============================================================================
------------------------------------------------------------------------------
RIB In Entries
------------------------------------------------------------------------------
Network : 172.17.100.0/24
Nexthop : 10.100.100.5
Path Id : None
From : 10.100.100.5
Res. Protocol : OSPF Res. Metric : 10
Res. Nexthop : 10.1.5.5
Local Pref. : 100 Interface Name : toR5
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 10
Connector : None
Community : 65100:15
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.5
Fwd Class : None Priority : None
Flags : Used Valid Best IGP
Route Source : Internal
AS-Path : No As-Path
Route Tag : 0
Neighbor-AS : n/a
Orig Validation: NotFound
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 00h24m15s

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 101
Inter-AS Traffic
Inter-AS Steering
Traffic Verification
Steering Verification[cont.]
[cont.]

Switch to notes view!

------------------------------------------------------------------------------
RIB Out Entries
------------------------------------------------------------------------------
Network : 172.17.100.0/24
Nexthop : 10.1.3.1
Path Id : None
To : 10.1.3.3
Res. Protocol : INVALID Res. Metric : 0
Res. Nexthop : n/a
Local Pref. : n/a Interface Name : NotAvailable
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 10
Connector : None
Community : 65200:120
Cluster
10 : No Cluster Members
2 Nokia 2020
© Nokia Confidential
Originator Id : None Peer Router Id : 10.200.200.3
Origin : IGP
AS-Path : 65100
Route Tag : 0
Neighbor-AS : 65100
Orig Validation: NotFound
Source Class : 0 Dest Class : 0

------------------------------------------------------------------------------
Routes : 2

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 102
Inter-AS Traffic
Inter-AS Steering
Traffic Verification
Steering Verification[cont.]
[cont.]
When R3 receives this eBGP route advertisement from R1 with the community 65200:120, it
set Switch
the local
to preference
notes view! of this route from n/a to 120.

A:BGP_Pod3_R3# show router bgp routes 172.17.100.0/24 detail

==============================================================================
BGP Router ID:10.200.200.3 AS:65200 Local AS:65200
==============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete

==============================================================================
BGP IPv4 Routes
==============================================================================
Original Attributes
10
3 Nokia 2020
© Nokia Confidential

Network : 172.17.100.0/24
Nexthop : 10.1.3.1
Path Id : None
From : 10.1.3.1
Res. Protocol : LOCAL Res. Metric : 0
Res. Nexthop : 10.1.3.1
Local Pref. : n/a Interface Name : toR1
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 0
Connector : None
Community : 65200:120
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.1
Fwd Class : None Priority : None
Flags : Used Valid Best IGP
Route Source : External
AS-Path : 65100
Route Tag : 0
Neighbor-AS : 65100
Orig Validation: NotFound
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 00h11m53s

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 103
Inter-AS Traffic
Inter-AS Steering
Traffic Verification
Steering Verification[cont.]
[cont.]

Switch to notes view!

Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.1
Fwd Class : None Priority : None
Flags : Used Valid Best IGP
Route Source : External
AS-Path : 65100
Route Tag : 0
Neighbor-AS : 65100
Orig Validation: NotFound
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 00h09m13s

Modified Attributes

Network
10 : 172.17.100.0/24
4 Nokia 2020
© Nokia Confidential
Nexthop : 10.1.3.1
Path Id : None
From : 10.1.3.1
Res. Protocol : LOCAL Res. Metric : 0
Res. Nexthop : 10.1.3.1
Local Pref. : 120 Interface Name : toR1
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 0
Connector : None
Community : 65200:120
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.1
Fwd Class : None Priority : None
Flags : Used Valid Best IGP
Route Source : External
AS-Path : 65100
Route Tag : 0
Neighbor-AS : 65100
Orig Validation: NotFound
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 00h11m53s

------------------------------------------------------------------------------
------------------------------------------------------------------------------
Routes : 1

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 104
Inter-AS Traffic
Inter-AS Steering
Traffic Verification
Steering Verification[cont.]
[cont.]
R3 then advertises this route 172.17.100.0/24 with local preference 120 to all its iBGP peers to
set Switch
itself up
toas the view!
notes exit router for AS 65200 for the prefix.

A:BGP_Pod3_R3# show router bgp routes 172.17.100.0/24 hunt

==============================================================================
BGP Router ID:10.200.200.3 AS:65200 Local AS:65200
==============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete

==============================================================================
BGP IPv4 Routes
==============================================================================
------------------------------------------------------------------------------
RIB©10 In 2020
5 Nokia Entries Nokia Confidential

------------------------------------------------------------------------------
Network : 172.17.100.0/24
Nexthop : 10.1.3.1
Path Id : None
From : 10.1.3.1
Res. Protocol : LOCAL Res. Metric : 0
Res. Nexthop : 10.1.3.1
Local Pref. : 120 Interface Name : toR1
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 0
Connector : None
Community : 65200:120
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.1
Fwd Class : None Priority : None
Flags : Used Valid Best IGP
Route Source : External
AS-Path : 65100
Route Tag : 0
Neighbor-AS : 65100
Orig Validation: NotFound
Source Class : 0 Dest Class : 0
Add Paths Send : Default
Last Modified : 00h13m35s

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 105
Inter-AS Traffic
Inter-AS Steering
Traffic Verification
Steering Verification[cont.]
[cont.]

Switch to notes view!

------------------------------------------------------------------------------
RIB Out Entries
------------------------------------------------------------------------------
Network : 172.17.100.0/24
Nexthop : 10.200.200.3
Path Id : None
To : 10.200.200.8
Res. Protocol : INVALID Res. Metric : 0
Res. Nexthop : n/a
Local Pref. : 120 Interface Name : NotAvailable
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 0
Connector : None
Community : 65200:120
Cluster
10 : No Cluster Members
6 Nokia 2020
© Nokia Confidential
Originator Id : None Peer Router Id : 10.200.200.8
Origin : IGP
AS-Path : 65100
Route Tag : 0
Neighbor-AS : 65100
Orig Validation: NotFound
Source Class : 0 Dest Class : 0

Network : 172.17.100.0/24
Nexthop : 10.200.200.3
Path Id : None
To : 10.200.200.7
Res. Protocol : INVALID Res. Metric : 0
Res. Nexthop : n/a
Local Pref. : 120 Interface Name : NotAvailable
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 0
Connector : None
Community : 65200:120
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.200.200.7
Origin : IGP
AS-Path : 65100
Route Tag : 0
Neighbor-AS : 65100
Orig Validation: NotFound
Source Class : 0 Dest Class : 0

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 106
Inter-AS Traffic
Inter-AS Steering
Traffic Verification
Steering Verification[cont.]
[cont.]

Switch to notes view!

Network : 172.17.100.0/24
Nexthop : 10.200.200.3
Path Id : None
To : 10.200.200.4
Res. Protocol : INVALID Res. Metric : 0
Res. Nexthop : n/a
Local Pref. : 120 Interface Name : NotAvailable
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 0
Connector : None
Community : 65200:120
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.200.200.4
Origin : IGP
AS-Path
10 : 65100
7 Nokia 2020
© Nokia Confidential
Route Tag : 0
Neighbor-AS : 65100
Orig Validation: NotFound
Source Class : 0 Dest Class : 0

Network : 172.17.100.0/24
Nexthop : 10.1.3.3
Path Id : None
To : 10.1.3.1
Res. Protocol : INVALID Res. Metric : 0
Res. Nexthop : n/a
Local Pref. : n/a Interface Name : NotAvailable
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 0
Connector : None
Community : 65200:120
Cluster : No Cluster Members
Originator Id : None Peer Router Id : 10.100.100.1
Origin : IGP
AS-Path : 65200 65100
Route Tag : 0
Neighbor-AS : 65200
Orig Validation: NotFound
Source Class : 0 Dest Class : 0
------------------------------------------------------------------------------
Routes : 5

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 107
 Scaling iBGP with RR

10
8 Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 108
Introduction to the Route Reflector (RR) Lab

In lab 2, we set up the full mesh iBGP neighbor connections within each AS. The end results is that there
will be [N * (N – 1) / N] iBGP neighbor connections where N is the number of iBGP speakers in the AS.

Route Reflectors (RRs) can reduce the number of iBGP neighbor connections to N or 2N if two RRs are
used for redundancy purpose.

10
9 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 109
Route Reflector Lab Setup
Four RR clusters are set up:

BGP_Pod2
R5 R6

R1 (RR) R2 (RR)

Cluster 10.100.100.1 Cluster 10.100.100.2

Cluster 10.200.200.3 Cluster 10.200.200.4

R3 (RR) R4 (RR)

R7 R8

11
0 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 110
Route Reflector Lab Objectives

R1 and R2 are the RRs for the R5 and R6 RR clients:

• R1 cluster – 10.100.100.1
• R2 cluster – 10.100.100.2

R3 and R4 are the RRs for the R7 and R8 RR clients:

• R3 cluster – 10.200.200.3
• R4 cluster – 10.200.200.4

The objectives of this lab are to:

• Set up the RR clusters to reduce the number of iBGP neighbor connections in an AS.
• Verify the RR redundancy to support iBGP neighbor connections during RR failure.

11
1 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 111
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number.

Initial rollback config file’s comment – BGP - inter-AS East and West side traffic steering.

Final rollback config file’s comment – BGP - scalable iBGP with Route Reflector Redundancy.

Use the command /admin rollback revert X to set the initial lab condition, if
necessary.

11
2 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 112
Route Reflector
Route config
Reflector Config
Exercise 6.1:
1. Switch
Each group configures
to notes view! their Border and Edge routers for the RR operation with the Border
router being the RR.

An Router Reflector Cluster is defined in the iBGP policy of the Border Routers R1 and R2 for
AS 65100, and R3 and R4 for AS 65200.

A:BGP_Pod1_R1>config>router>bgp# info
----------------------------------------------
group "iBGP"
description "Route Reflector for R5 and R6"
family ipv4
next-hop-self
type internal
peer-as 65100
11
3 Nokia 2020
©
neighbor 10.100.100.5Nokia Confidential
description "RR for R5"
cluster 10.100.100.1
exit
neighbor 10.100.100.6
description "RR for R6"
cluster 10.100.100.1
exit
exit
no shutdown
group "iBGP-RR-redundancy"
description "iBGP to redundancy RR"
family ipv4
type internal
peer-as 65100
neighbor 10.100.100.2
description "iBGP to redundancy RR"
exit
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 113
Route Reflector
Route config
Reflector [cont.]
Config [cont.]

Switch to notes view!

A:BGP_Pod2_R2>config>router>bgp# info
----------------------------------------------
group "iBGP"
description "Route Reflector for R5 and R6"
family ipv4
next-hop-self
type internal
peer-as 65100
neighbor 10.100.100.5
description "RR for R5"
cluster 10.100.100.2
exit
neighbor 10.100.100.6
description "RR for R6"
cluster 10.100.100.2
11 exit
4 Nokia 2020
© Nokia Confidential
exit
group "iBGP-RR-redundancy"
description "iBGP to redundancy RR"
family ipv4
type internal
peer-as 65100
neighbor 10.100.100.1
description "iBGP to redundancy RR"
exit
exit
no shutdown

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 114
Route Reflector
Route config
Reflector [cont.]
Config [cont.]

Switch to notes view!

A:BGP_Pod3_R3>config>router>bgp# info
----------------------------------------------
group "iBGP"
description "Route Reflector for R7 and R8"
family ipv4
next-hop-self
type internal
peer-as 65200
neighbor 10.200.200.7
description "RR for R7"
cluster 10.200.200.3
exit
neighbor 10.200.200.8
description "RR for R8"
11
cluster 10.200.200.3
5 Nokia 2020
© exit Nokia Confidential

exit
group "iBGP-RR-redundancy"
description "iBGP to redundancy RR"
family ipv4
type internal
peer-as 65200
neighbor 10.200.200.4
description "iBGP to redundancy RR"
exit
exit
no shutdown
----------------------------------------------

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 115
Route Reflector
Route config
Reflector [cont.]
Config [cont.]

Switch to notes view!

A:BGP_Pod4_R4>config>router>bgp# info
----------------------------------------------
group "iBGP"
description "Route Reflector for R7 and R8"
family ipv4
next-hop-self
type internal
peer-as 65200
neighbor 10.200.200.7
description "RR for R7"
cluster 10.200.200.4
exit
neighbor 10.200.200.8
description "RR for R8"
11
cluster 10.200.200.4
6 Nokia 2020
© exit Nokia Confidential

exit
group "iBGP-RR-redundancy"
description "iBGP to redundancy RR"
family ipv4
type internal
peer-as 65200
neighbor 10.200.200.3
description "iBGP to redundancy RR"
exit
exit
no shutdown
----------------------------------------------

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 116
Route Reflector
Route config
Reflector [cont.]
Config [cont.]
On the Edge routers, remove any iBGP neighbor configuration except to the RRs.
Switch to notes view!
A:BGP_Pod1_R5>config>router>bgp# info
----------------------------------------------
group "iBGP"
description "client for cluster 10.100.100.1 and 10.100.100.2"
family ipv4
type internal
export "export_access_services"
peer-as 65100
neighbor 10.100.100.1
description "client for cluster 10.100.100.1"
exit
neighbor 10.100.100.2
description "client for cluster 10.100.100.2"
exit
11
7 Nokia 2020
©
exit Nokia Confidential
no shutdown

A:BGP_Pod2_R6>config>router>bgp# info
----------------------------------------------
group "iBGP"
description "client for cluster 10.100.100.1 and 10.100.100.2"
family ipv4
type internal
export "export_access_services"
peer-as 65100
neighbor 10.100.100.1
description "client for cluster 10.100.100.1"
exit
neighbor 10.100.100.2
description "client for cluster 10.100.100.2"
exit
exit
no shutdown

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 117
Route Reflector
Route config
Reflector [cont.]
Config [cont.]

Switch to notes view!

A:BGP_Pod3_R7>config>router>bgp# info
----------------------------------------------
group "iBGP"
description "client for cluster 10.200.200.3 and 10.200.200.4"
family ipv4
type internal
export "export_access_services"
peer-as 65200
neighbor 10.200.200.3
description "client for cluster 10.200.200.3"
exit
neighbor 10.200.200.4
description "client for cluster 10.200.200.4"
exit
exit
11 no shutdown
8 Nokia 2020
© Nokia Confidential
----------------------------------------------

A:BGP_Pod4_R8>config>router>bgp# info
----------------------------------------------
group "iBGP"
description "client for cluster 10.200.200.3 and 10.200.200.4"
family ipv4
type internal
export "export_access_services"
peer-as 65200
neighbor 10.200.200.3
description "client for cluster 10.200.200.3"
exit
neighbor 10.200.200.4
description "client for cluster 10.200.200.4"
exit
exit
no shutdown
----------------------------------------------

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 118
Route Reflector
Route config
Reflector [cont.]
Config [cont.]
On the Edge router, the command show router bgp summary verifies whether the
iBGPSwitch
neighbor setup
to notes to the RR is successful or not. The following command shows that R5 has
view!
successful iBGP neighbor connections to its RRs, R1 and R2.

A:BGP_Pod1_R5# show router bgp summary

==============================================================================
BGP Router ID:10.100.100.5 AS:65100 Local AS:65100
==============================================================================
BGP Admin State : Up BGP Oper State : Up
Total Peer Groups : 1 Total Peers : 2
Total VPN Peer Groups : 0 Total VPN Peers : 0
Total BGP Paths : 26 Total Path Memory : 9056
<< skip >>

==============================================================================
11
BGP©9 Nokia
Summary
2020 Nokia Confidential

==============================================================================
Legend : D - Dynamic Neighbor
==============================================================================
Neighbor
Description
AS PktRcvd InQ Up/Down State|Rcv/Act/Sent (Addr Family)
PktSent OutQ
------------------------------------------------------------------------------
10.100.100.1
client for cluster 10.100.100.1
65100 11414 0 01d07h36m 8/6/2 (IPv4)
3806 0
10.100.100.2
client for cluster 10.100.100.2
65100 11392 0 01d06h11m 8/0/2 (IPv4)
3647 0

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 119
Route Reflector
Route config
Reflector [cont.]
Config [cont.]
Although R5 does not have an iBGP connection to R6 in AS 65100 through the RRs, it receives
theSwitch
iBGP route advertisement
to notes view! for the R6 customer network 172.17.102.0/24.

A:BGP_Pod1_R5# show router bgp routes 172.17.102.0/24

==============================================================================
BGP Router ID:10.100.100.5 AS:65100 Local AS:65100
==============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete

==============================================================================
BGP IPv4 Routes
==============================================================================
Flag Network LocalPref MED
12
0 Nokia Nexthop
© 2020 (Router) Nokia Confidential Path-Id Label
As-Path
------------------------------------------------------------------------------
u*>i 172.17.102.0/24 100 None
10.100.100.1 None -
No As-Path
*i 172.17.102.0/24 100 None
10.100.100.2 None -
No As-Path
------------------------------------------------------------------------------
Routes : 2

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 120
Route Reflector
Route config
Reflector [cont.]
Config [cont.]
On R1, run the following command to verify that client reflection is enabled for R5.
Switch to notes view!
A:BGP_Pod1_R1# show router bgp neighbor 10.100.100.5
==============================================================================
BGP Neighbor
==============================================================================
------------------------------------------------------------------------------
Peer : 10.100.100.5
Description : RR for R5
Group : iBGP
------------------------------------------------------------------------------
Peer AS : 65100 Peer Port : 49953
Peer Address : 10.100.100.5
Local AS : 65100 Local Port : 179
Local Address : 10.100.100.1
Peer Type : Internal Dynamic Peer : No
State
12
1 Nokia 2020
©
: Established Nokia Confidential
Last State : Established
Last Event : recvOpen
Last Error : Cease (Connection Collision Resolution)
Local Family : IPv4
Remote Family : IPv4
Hold Time : 90 Keep Alive : 30
Min Hold Time : 0
Active Hold Time : 90 Active Keep Alive : 30
Cluster Id : 10.100.100.1

When R1 advertises the R5 customer network, such as 172.17.100.0/24, it adds its cluster ID
onto the routes.

A:BGP_Pod1_R1# show router bgp routes 172.17.100.0/24 hunt

RIB Out Entries
------------------------------------------------------------------------------
Network : 172.17.100.0/24
Nexthop : 10.100.100.1
Path Id : None
To : 10.100.100.5
Res. Protocol : INVALID Res. Metric : 0
Res. Nexthop : n/a
Local Pref. : 100 Interface Name : NotAvailable
Aggregator AS : None Aggregator : None
Atomic Aggr. : Not Atomic MED : None
AIGP Metric : None IGP Cost : 10
Connector : None
Community : 65100:15
Cluster : 10.100.100.1
Originator Id : 10.100.100.5 Peer Router Id : 10.100.100.5
Origin : IGP
AS-Path : No As-Path
Route Tag : 0
Neighbor-AS : n/a
Orig Validation: NotFound
Source Class : 0 Dest Class : 0

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 121
Route Reflector
Route config
Reflector [cont.]
Config [cont.]
If one of the RR is down, the other RR will maintains iBGP and eBGP router advertisement for
redundancy
Switch topurpose.
notes view!

2. On R5, do a traceroute to the R6 customer network to verify the path before RR failure.

A:BGP_Pod1_R5>config>router>bgp# traceroute 172.17.102.6 source 172.17.100.5

traceroute to 172.17.102.6 from 172.17.100.5, 30 hops max, 40 byte packets
1 10.1.5.1 (10.1.5.1) 2.49 ms 1.70 ms 1.55 ms
2 10.1.2.2 (10.1.2.2) 1.56 ms 2.94 ms 3.01 ms
3 172.17.102.6 (172.17.102.6) 4.21 ms 4.50 ms 3.68 ms

On R1, shut down the iBGP process to simulate a RR failure and repeat the above traceroute
command again.
12
2 Nokia 2020
© Nokia Confidential
A:BGP_Pod1_R1>config>router>bgp# info
----------------------------------------------
group "iBGP"
shutdown
description "Route Reflector for R5 and R6"
family ipv4
next-hop-self
type internal
peer-as 65100
neighbor 10.100.100.5
description "RR for R5"
cluster 10.100.100.1
exit
neighbor 10.100.100.6
description "RR for R6"
cluster 10.100.100.1
exit
exit

R5 can still maintain the connectivity even when R1 (RR) is down.

A:BGP_Pod1_R5>config>router>bgp# traceroute 172.17.102.6 source 172.17.100.5

traceroute to 172.17.102.6 from 172.17.100.5, 30 hops max, 40 byte packets
1 10.1.5.1 (10.1.5.1) 2.54 ms 1.72 ms 1.74 ms
2 10.1.2.2 (10.1.2.2) 2.88 ms 2.86 ms 2.99 ms
3 172.17.102.6 (172.17.102.6) 3.87 ms 3.72 ms 4.04 ms

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 122
 IPv6 iBGP and eBGP

12
3 Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 123
Introduction to IPv6 iBGP and eBGP Labs

The setup of IPv6 iBGP and eBGP is similar to that of IPv4, except that the IPv6 address format is
different from that in IPv4.

If IGP uses OSPFv2, then OSPFv3 is needed to support the IPv6 BGP operations.

The IPv6 local link address is assigned automatically to each IPv6 interface; and it can be useful for the
IPv6 eBGP operations for establishing an eBGP neighbor connection.

12
4 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 124
IPv6 iBGP and eBGP Lab Objectives

The objectives of this lab exercise are to:

• Understand IPv6 iBGP and eBGP configuration
• Use the IPv6 route policy to import and export the IPv6 route
• Use the IPv6 link local address for the eBGP neighbor connection

12
5 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 125
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number.

Initial rollback config file’s comment – BGP – initial IPv6 iBGP and eBGP .

Final rollback config file’s comment – BGP – final IPv6 iBGP and eBGP .

Use the command /admin rollback revert X to set the initial lab condition, if
necessary.

12
6 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 126
Initial IPv6 Lab Verification

Similar to IPv4 BGP config, IPv6 iBGP needs IPv6 IGP to establish IPv6 connectivity among all of the IPv6
iBGP peers in the AS.

The OSPF3 support of IPv6 is pre-setup in the IPv6 initial lab config so that students can focus on IPv6
BGP-related config and verification.

Use the following IPv6 commands:

• /config router ospf3
• Show router opsf3 neighbor
• Show router route-table ipv6

Once the routers can ping the IPv6 system addresses distributed by OSPF3 within an AS, the IPv6 iBGP
neighbor connection can be set up (next exercise).

12
7 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 127
Initial IPv6
Initial Lab
IPv6 Verification
Lab Verification[cont.]
[cont.]
Exercise 7.1:
Each grouptoverifies
Switch the OSPF3 config in their Border and Edge routers. Verify the OSPF3 for
notes view!
IPv6 neighbor status.

Border Router OSPF3 Config:

A:BGP_Pod1_R1# configure router ospf3

A:BGP_Pod1_R1>config>router>ospf3# info
----------------------------------------------
area 0.0.0.0
interface "system"
no shutdown
exit
interface "toR2"
interface-type point-to-point
12 no shutdown
8 Nokia 2020
© Nokia Confidential
exit
interface "toR5"
interface-type point-to-point
no shutdown
exit
exit
no shutdown

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 128
Initial IPv6
Initial Lab
IPv6 Verification
Lab Verification[cont.]
[cont.]
Edge Roter OSPF3 Config:
Switch to notes view!
A:BGP_Pod1_R5>config>router>ospf3# info
----------------------------------------------
area 0.0.0.0
interface "system"
no shutdown
exit
interface "toR1"
interface-type point-to-point
no shutdown
exit
interface "toR6"
interface-type point-to-point
no shutdown
exit
12
9 Nokia 2020
©
exit Nokia Confidential
no shutdown

With the OSPF3 config in the Border and Edge routers, verify their OSPF3 neighbor status.
Both the Border and Edge routers have successfully established the OSPF3 IPv6 neighbor
condition with Full State to exchange OSPF3 routes.

A:BGP_Pod1_R1# show router ospf3 neighbor

==============================================================================
Rtr Base OSPFv3 Instance 0 Neighbors
==============================================================================
Interface-Name Rtr Id State Pri RetxQ TTL
Area-Id
------------------------------------------------------------------------------
toR2 10.100.100.2 Full 1 0 34
0.0.0.0
toR5 10.100.100.5 Full 1 0 32
0.0.0.0
------------------------------------------------------------------------------
No. of Neighbors: 2

A:BGP_Pod1_R5>config>router>ospf3# show router ospf3 neighbor

==============================================================================
Rtr Base OSPFv3 Instance 0 Neighbors
==============================================================================
Interface-Name Rtr Id State Pri RetxQ TTL
Area-Id
------------------------------------------------------------------------------
toR1 10.100.100.1 Full 1 0 33
0.0.0.0
toR6 10.100.100.6 Full 1 0 39
0.0.0.0
------------------------------------------------------------------------------
No. of Neighbors: 2

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 129
IPv6 iBGP Setup and Verification

With OSPF3 running to distribute the IPv6 system addresses, the routers within the IGP domain (such as
AS) can contact each other to provide IPv6 connectivity for setting up IPv6 iBGP config.

Setup full Mesh IPv6 iBGP neighbor connections among the routers in the AS.

Develop an export policy to export the loopback IPv6 address ( or the IP access service for customers’
IPv6 networks) of the Edge routers so that the routers within the AS can reach all the IPv6 customer
networks.

13
0 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 130
IPv6 iBGP
IPv6 Setup
iBGP and
Setup Verification
and Verification[cont.]
[cont.]
Exercise 7.2:
IPv6Switch
iBGP Config:
to notes view!

Each group sets up IPv6 iBGP configuration at the Border and Edge routers.

A:BGP_Pod1_R1>config>router>bgp# info
----------------------------------------------
group "IPv6_iBGP"
family ipv6
peer-as 65100
neighbor 2001:db8:a:200::2
exit
neighbor 2001:db8:a:500::5
exit
neighbor 2001:db8:a:600::6
13 exit
1 Nokia 2020
© Nokia Confidential
exit
no shutdown

A:BGP_Pod1_R5>config>router>bgp# info
----------------------------------------------
group "IPv6_iBGP"
family ipv6
type internal
peer-as 65100
neighbor 2001:db8:a:100::1
exit
neighbor 2001:db8:a:200::2
exit
neighbor 2001:db8:a:600::6
exit
exit
no shutdown

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 131
IPv6 iBGP
IPv6 Setup
iBGP and
Setup Verification
and Verification[cont.]
[cont.]
Verify the IPv6 iBGP neighbor connection.
Switch to notes view!
A:BGP_Pod1_R1# show router bgp summary
==============================================================================
BGP Router ID:10.100.100.1 AS:65100 Local AS:65100
==============================================================================
BGP Admin State : Up BGP Oper State : Up
Total Peer Groups : 3 Total Peers : 7

<< skip >>

==============================================================================
BGP Summary
==============================================================================
Legend : D - Dynamic Neighbor
==============================================================================
Neighbor
13
2 Nokia 2020
© Nokia Confidential
Description
AS PktRcvd InQ Up/Down State|Rcv/Act/Sent (Addr Family)
PktSent OutQ
------------------------------------------------------------------------------
10.1.3.3
BGP_Pod3_R3
65200 2526 0 20h56m27s 4/4/8 (IPv4)
2526 0
10.100.100.2
BGP_Pod2_R2
65100 2524 0 19h30m38s 4/0/4 (IPv4)
2359 0
10.100.100.5
BGP_Pod1_R5
65100 2517 0 20h56m27s 2/2/4 (IPv4)
2530 0
10.100.100.6
BGP_Pod2_R6
65100 2517 0 20h56m27s 2/2/4 (IPv4)
2527 0
2001:db8:a:200::2
65100 97 0 00h47m10s 0/0/0 (IPv6)
97 0
2001:db8:a:500::5
65100 103 0 00h49m50s 1/1/0 (IPv6)
104 0
2001:db8:a:600::6
65100 102 0 00h49m29s 1/1/0 (IPv6)
104 0

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 132
IPv6 iBGP
IPv6 Setup
iBGP and
Setup Verification
and Verification[cont.]
[cont.]

Switch to notes view!

A:BGP_Pod1_R5# show router bgp summary
==============================================================================
BGP Router ID:10.100.100.5 AS:65100 Local AS:65100
==============================================================================
BGP Admin State : Up BGP Oper State : Up
Total Peer Groups : 2 Total Peers : 6
Total BGP Paths : 20 Total Path Memory : 3696

<< skip >>

==============================================================================
BGP Summary
==============================================================================
Legend : D - Dynamic Neighbor
==============================================================================
Neighbor
13
3 Nokia 2020
© Nokia Confidential
Description
AS PktRcvd InQ Up/Down State|Rcv/Act/Sent (Addr Family)
PktSent OutQ
------------------------------------------------------------------------------
10.100.100.1
BGP_Pod1_R1
65100 10125 0 20h57m19s 4/4/2 (IPv4)
2526 0
10.100.100.2
BGP_Pod2_R2
65100 10102 0 19h31m30s 4/0/2 (IPv4)
2367 0
10.100.100.6
BGP_Pod2_R6
65100 2285 0 19h00m56s 2/2/2 (IPv4)
2286 0
2001:db8:a:100::1
65100 104 0 00h50m41s 0/0/1 (IPv6)
105 0
2001:db8:a:200::2
65100 104 0 00h50m41s 0/0/1 (IPv6)
105 0
2001:db8:a:600::6
65100 104 0 00h50m20s 1/1/1 (IPv6)
105 0

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 133
Edge Router Customer Network iBGP Export policy

On the Edge routers, develop an iBGP export policy to export the IPv6 loopback routes ( or customer
networks) to all the iBGP neighbors so that all the routers within the AS can reach those networks.

Use a ping to verify that all of the routers within the AS can reach these IPv6 loopback addresses to
verify the Edge router’s iBGP export policy.

13
4 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 134
Edge Router
Edge Customer
Router Network
Customer NetworkiBGP
iBGPExport
ExportPolicy
policy[cont.]
[cont.]
Exercise 7.3:
On Switch
each Edge router,
to notes develop an export policy to export its IPv6 loopback address (or
view!
customer networks terminating at the Edge router) to all the iBGP neighbors.

A:BGP_Pod1_R5>config>router>policy-options# info
----------------------------------------------
prefix-list "IPv6_loopback"
prefix 2001:db8:a:501::1/128 exact
exit
policy-statement "export_IPv6"
entry 10
from
protocol direct
prefix-list "IPv6_loopback"
exit
13 action accept
5 Nokia 2020
© Nokia Confidential
exit
exit
exit

A:BGP_Pod2_R6>config>router>policy-options# info
----------------------------------------------
prefix-list "IPv6_loopback"
prefix 2001:db8:a:601::1/128 exact
exit
policy-statement "export_IPv6"
entry 10
from
protocol direct
prefix-list "IPv6_loopback"
exit
action accept
exit
exit
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 135
Edge Router
Edge Customer
Router Network
Customer NetworkiBGP
iBGPExport
ExportPolicy
policy[cont.]
[cont.]

Switch to notes view!

A:BGP_Pod3_R7>config>router>policy-options# info
----------------------------------------------
prefix-list "IPv6_loopback"
prefix 2001:db8:a:701::1/128 exact
exit
policy-statement "export_IPv6"
entry 10
from
protocol direct
prefix-list "IPv6_loopback"
exit
action accept
exit
exit
13
6 Nokia 2020
©
exit Nokia Confidential

A:BGP_Pod4_R8>config>router>policy-options# info
----------------------------------------------
prefix-list "IPv6_loopback"
prefix 2001:db8:a:801::1/128 exact
exit
policy-statement "export_IPv6"
entry 10
from
protocol direct
prefix-list "IPv6_loopback"
exit
action accept
exit
exit
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 136
Edge Router
Edge Customer
Router Network
Customer NetworkiBGP
iBGPExport
ExportPolicy
policy[cont.]
[cont.]
Include the Edge router’s export policy to its IPv6 iBGP config.
Switch to notes view!
A:BGP_Pod1_R5>config>router>bgp# info
----------------------------------------------
group "IPv6_iBGP"
family ipv6
type internal
export "export_IPv6"
peer-as 65100
neighbor 2001:db8:a:100::1
exit
neighbor 2001:db8:a:200::2
exit
neighbor 2001:db8:a:600::6
exit
exit
13
7 Nokia 2020
©
no shutdown Nokia Confidential

Verify that all iBGP neighbors in the AS received these IPv6 loopback addresses and can ping to
them.

A:BGP_Pod2_R2>config>router# show router route-table ipv6

==============================================================================
IPv6 Route Table (Router: Base)
==============================================================================
Dest Prefix[Flags] Type Proto Age
Pref
Next Hop[Interface Name] Metric
------------------------------------------------------------------------------
2001:db8:a:100::1/128 Remote OSPF3 18h57m21s 10
fe80::69ff:fe00:102-"toR1" 100
2001:db8:a:200::2/128 Local Local 05d22h20m 0
system 0
2001:db8:a:500::5/128 Remote OSPF3 18h57m16s 10
fe80::69ff:fe00:102-"toR1" 200
2001:db8:a:501::1/128 Remote BGP 00h58m09s 170
fe80::69ff:fe00:102-"toR1" 0
2001:db8:a:600::6/128 Remote OSPF3 18h57m53s 10
fe80::69ff:fe00:604-"toR6" 100
2001:db8:a:601::1/128 Remote BGP 00h57m44s 170
fe80::69ff:fe00:604-"toR6" 0
2001:db8:24::/48 Local Local 05d22h20m 0
toR4 0
------------------------------------------------------------------------------
No. of Routes: 7
Flags: n = Number of times nexthop is repeated
B = BGP backup route available
L = LFA nexthop available
S = Sticky ECMP requested

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 137
Edge Router
Edge Customer
Router Network
Customer NetworkiBGP
iBGPExport
ExportPolicy
policy[cont.]
[cont.]
With the export policy, all routers within an AS can now ping to the IPv6 loopback addresses
(i.e.,Switch
customer networks)
to notes view! of the Edge routers.

A:BGP_Pod2_R2>config>router# ping 2001:db8:a:600::6

PING 2001:db8:a:600::6 56 data bytes
64 bytes from 2001:db8:a:600::6 icmp_seq=1 hlim=64 time=1.65ms.
64 bytes from 2001:db8:a:600::6 icmp_seq=2 hlim=64 time=1.57ms.
64 bytes from 2001:db8:a:600::6 icmp_seq=3 hlim=64 time=1.46ms.

13
8 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 138
Border Router eBGP using IPv6 Link Local

All the routers within as AS can now ping to the IPv6 loopback addresses from their Edge routers.
Develop an IPv6 eBGP connection so that the two ASes can reach each other’s loopback addresses (or
customer networks).

IPv6 automatically assigns the link local address to an IPv6 interface, which can be used for establishing
an eBPG connection.

Develop an IPv6 eBGP config on the Border routers by using the link local address and verify that the
IPv6 loopback addresses or customer networks at the Edge routers can be reached by the routers in
different ASes through the eBGP connection.

13
9 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 139
Border Router
Border eBGP
Router using
eBGP usingIPv6
IPv6Link
LinkLocal
Local[cont.]
[cont.]
Exercise 7.4:
IPv6Switch
eBGP:to notes view!

On each Border router, find its IPv6 link local address for the eBGP connection as follows:

A:BGP_Pod1_R1# show router interface "toR3"

==============================================================================
Interface Table (Router: Base)
==============================================================================
Interface-Name Adm Opr(v4/v6) Mode Port/SapId
IP-Address PfxState
------------------------------------------------------------------------------
toR3 Up Up/Up Network 1/1/1
10.1.3.1/27 n/a
2001:db8:13::1/48
14 PREFERRED
0 Nokia 2020
© Nokia Confidential
fe80::aaff:fe01:101/64 PREFERRED
------------------------------------------------------------------------------
Interfaces : 1
==============================================================================

A:BGP_Pod3_R3# show router interface "toR1"

==============================================================================
Interface Table (Router: Base)
==============================================================================
Interface-Name Adm Opr(v4/v6) Mode Port/SapId
IP-Address PfxState
------------------------------------------------------------------------------
toR1 Up Up/Up Network 1/1/1
10.1.3.3/27 n/a
2001:db8:13::3/48 PREFERRED
fe80::aaff:fe03:101/64 PREFERRED
------------------------------------------------------------------------------
Interfaces : 1
==============================================================================

Ping from R1 to R3 link local address is good and it is ready for eBGP setup.

A:BGP_Pod1_R1# ping fe80::aaff:fe03:101-toR3

PING fe80::aaff:fe03:101-"toR3" 56 data bytes
64 bytes from fe80::aaff:fe03:101-toR3 icmp_seq=1 hlim=64 time=6.45ms.
64 bytes from fe80::aaff:fe03:101-toR3 icmp_seq=2 hlim=64 time=2.45ms.
64 bytes from fe80::aaff:fe03:101-toR3 icmp_seq=3 hlim=64 time=2.15ms.
64 bytes from fe80::aaff:fe03:101-toR3 icmp_seq=4 hlim=64 time=2.38ms.
64 bytes from fe80::aaff:fe03:101-toR3 icmp_seq=5 hlim=64 time=2.49ms.

---- fe80::aaff:fe03:101 (toR3) PING Statistics ----

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 2.15ms, avg = 3.19ms, max = 6.45ms, stddev = 1.64ms

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 140
Border Router
Border eBGP
Router using
eBGP usingIPv6
IPv6Link
LinkLocal
Local[cont.]
[cont.]

Switch
A ping toR3
from notes view!
to R1 link local address is also good and it is ready for eBGP setup.

A:BGP_Pod3_R3# ping fe80::aaff:fe01:101-toR1

PING fe80::aaff:fe01:101-"toR1" 56 data bytes
64 bytes from fe80::aaff:fe01:101-toR1 icmp_seq=1 hlim=64 time=3.10ms.
64 bytes from fe80::aaff:fe01:101-toR1 icmp_seq=2 hlim=64 time=2.96ms.
64 bytes from fe80::aaff:fe01:101-toR1 icmp_seq=3 hlim=64 time=2.75ms.
64 bytes from fe80::aaff:fe01:101-toR1 icmp_seq=4 hlim=64 time=2.41ms.
64 bytes from fe80::aaff:fe01:101-toR1 icmp_seq=5 hlim=64 time=2.27ms.

---- fe80::aaff:fe01:101 (toR1) PING Statistics ----

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 2.27ms, avg = 2.70ms, max = 3.10ms, stddev = 0.315ms

14
On the Edge and Border routers, develop anNokiaIPv6
1 Nokia 2020
©
eBGP setup by using the IPv6 link local
Confidential

addresses of the remote end. Note that the R3 link local address is used in the R1 IPv6 eBGP
config below for neighbors.

A:BGP_Pod1_R1>config>router>bgp# info
----------------------------------------------
group "IPv6_eBGP"
family ipv6
loop-detect discard-route
peer-as 65200
neighbor fe80::aaff:fe03:101-"toR3"
exit

A:BGP_Pod2_R2>config>router>bgp# info
----------------------------------------------
group "IPv6_eBGP"
family ipv6
loop-detect discard-route
peer-as 65200
neighbor fe80::aaff:fe04:101-"toR4"
exit

A:BGP_Pod3_R3>config>router>bgp# info
----------------------------------------------
group "IPv6_eBGP"
family ipv6
loop-detect discard-route
peer-as 65100
neighbor fe80::aaff:fe01:101-"toR1"
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 141
Border Router eBGP using IPv6 Link Local [cont.]

A:BGP_Pod4_R4>config>router>bgp# info
----------------------------------------------
group "IPv6_eBGP"
family ipv6
loop-detect discard-route
peer-as 65100
neighbor fe80::aaff:fe02:101-"toR2"
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 142
Border Router
Border eBGP
Router using
eBGP usingIPv6
IPv6Link
LinkLocal
Local[cont.]
[cont.]
Verify the IPv6 eBGP neighbor status.
Switch to notes view!
A:BGP_Pod1_R1# show router bgp summary
==============================================================================
BGP Router ID:10.100.100.1 AS:65100 Local AS:65100
==============================================================================
BGP Admin State : Up BGP Oper State : Up
Total Peer Groups : 4 Total Peers : 8
<< ski p>>

==============================================================================
BGP Summary
==============================================================================
Legend : D - Dynamic Neighbor
==============================================================================
Neighbor
Description
14
3 Nokia 2020
© Nokia Confidential
AS PktRcvd InQ Up/Down State|Rcv/Act/Sent (Addr Family)
PktSent OutQ
------------------------------------------------------------------------------
10.1.3.3
BGP_Pod3_R3
65200 734 0 05h54m30s 4/4/8 (IPv4)
739 0
10.100.100.2
BGP_Pod2_R2
65100 281 0 02h16m06s 4/0/4 (IPv4)
282 0
10.100.100.5
BGP_Pod1_R5
65100 278 0 02h16m25s 2/2/4 (IPv4)
281 0
10.100.100.6
BGP_Pod2_R6
65100 278 0 02h16m25s 2/2/4 (IPv4)
281 0
2001:db8:a:200::2
65100 163 0 01h19m14s 2/0/2 (IPv6)
169 0
2001:db8:a:500::5
65100 168 0 01h21m33s 1/1/2 (IPv6)
169 0
2001:db8:a:600::6
65100 156 0 01h15m50s 1/1/2 (IPv6)
169 0
fe80::aaff:fe03:101-"toR3"
65200 20 0 00h07m29s 2/2/4 (IPv6)
28 0
------------------------------------------------------------------------------

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 143
Border Router
Border eBGP
Router using
eBGP usingIPv6
IPv6Link
LinkLocal
Local[cont.]
[cont.]
Verify that Edge routers can reach other AS’s IPv6 customer networks (loopback addresses).
Switch to notes view!
A:BGP_Pod1_R5# show router bgp routes ipv6
==============================================================================
BGP Router ID:10.100.100.5 AS:65100 Local AS:65100
==============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete

==============================================================================
BGP IPv6 Routes
==============================================================================
Flag Network LocalPref MED
Nexthop (Router) Path-Id Label
14 As-Path
4 Nokia 2020
© Nokia Confidential
------------------------------------------------------------------------------
u*>i 2001:db8:a:601::1/128 100 None
2001:db8:a:600::6 None 10
No As-Path -
u*>i 2001:db8:a:701::1/128 100 None
2001:db8:a:100::1 None 10
65200 -
*i 2001:db8:a:701::1/128 100 None
2001:db8:a:200::2 None 20
65200 -
u*>i 2001:db8:a:801::1/128 100 None
2001:db8:a:100::1 None 10
65200 -
*i 2001:db8:a:801::1/128 100 None
2001:db8:a:200::2 None 20
65200 -
------------------------------------------------------------------------------
Routes : 5

Ping between ASes’ customer networks is successful.

A:BGP_Pod1_R5# ping 2001:db8:a:801::1 source 2001:db8:a:501::1

PING 2001:db8:a:801::1 56 data bytes
64 bytes from 2001:db8:a:801::1 icmp_seq=1 hlim=61 time=6.64ms.
64 bytes from 2001:db8:a:801::1 icmp_seq=2 hlim=61 time=6.07ms.
64 bytes from 2001:db8:a:801::1 icmp_seq=3 hlim=61 time=5.13ms.
64 bytes from 2001:db8:a:801::1 icmp_seq=4 hlim=61 time=5.78ms.
64 bytes from 2001:db8:a:801::1 icmp_seq=5 hlim=61 time=5.49ms.

---- 2001:db8:a:801::1 PING Statistics ----

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 5.13ms, avg = 5.82ms, max = 6.64ms, stddev = 0.511ms

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 144
Wrap-up
In this module we have covered the following items:
• Configuration of the common IPv4 and IPv6 iBGP and eBGP setup on Nokia’s Service
Router, including:
̵ iBGP with next-hop-self setup for an Autonomous System (AS)
̵ eBGP setup across multiple Autonomous Systems (ASes)
̵ iBGP and eBPG import and export policies for traffic steering by using community, local
preference, and prefix list
̵ IPv6 eBGP using the IPv6 interface local link address
̵ Route Reflector and redundancy for iBGP scalability

14
5 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 145
14
6 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M05 Ed0 146
 EVPN

ER00198-V-2000 V0 - S05M06 Ed0

1 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 1
Learning Objectives
Upon completion of this module, you should be able to:
• Enhance VPLS network service into EVPN VXLAN service and use IP instead of MPLS
as the transport protocol to connect multiple layer 2 EVPNs together
• Set up MP-BGP supporting EVPN address family as EVPN VXLAN’s control plane
protocol
• Set up VXLAN as EVPN VXLAN’s data plane encapsulation protocols to form Virtual
Tunnel Endpoints (VTEPs) for interconnecting EVPN endpoints
• Debug MP-BGP supporting EVPN address family for EVPN MAC route exchange

2 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 2
 ToC Slide

Table of Contents

Lab Setup
Initial Lab Verification
MP-BGP (evpn) Control Plane
EVPN VXLAN Service
Debug EVPN VXLAN
Wrap-up

3 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 3
 Lab Setup

4 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 4
Initial Lab Condition

All routers are setup in ISIS Level 2 and routers R1 to R8 can ping to each others’ system addresses of 10.10.10.x/32.

A:R8# ping 10.10.10.5

PING 10.10.10.5 56 data bytes
64 bytes from 10.10.10.5: icmp_seq=1 ttl=62 time=3.35ms.
64 bytes from 10.10.10.5: icmp_seq=2 ttl=62 time=3.43ms.

Use VXLAN as the encapsulation protocol over an IP core network (R1 to R4) and thus all MPLS protocols such as RSVP-TE
and LDP are shutdown.
PC9 to PC12 have IP addresses 192.168.1.x/24 connected to the access port 1/1/5:0 of the Edge routers, R5 – R8. They
can ping to its own IP address but they cannot reach each other because the EVPN VXLAN has not yet setup.
[root@PC12 ~]# ping 192.168.1.12
PING 192.168.1.12 (192.168.1.12) 56(84) bytes of data.
64 bytes from 192.168.1.12: icmp_seq=1 ttl=64 time=0.044 ms
64 bytes from 192.168.1.12: icmp_seq=2 ttl=64 time=0.035 ms Ping to self is OK

[root@PC12 ~]# ping 192.168.1.5

PING 192.168.1.5 (192.168.1.5) 56(84) bytes of data.
From 192.168.1.12 icmp_seq=2 Destination Host Unreachable
Ping other PCs fail
From 192.168.1.12 icmp_seq=3 Destination Host Unreachable

5 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 5
 Router System Addresses and PC Interface
10.10.10.5/32 10.10.10.6/32
PC9 3ffe::1:505:505/128 3ffe::1:606:606/128 PC10

10.10.10.1/32 10.10.10.2/32
3ffe::1:101:101/128 3ffe::1:202:202/128

R5 R1 R2
eth1 192.168.1.9/24 R6 eth1 192.168.1.10/24

PC11 R7 R3 R4 R8 PC12
10.10.10.3/32 10.10.10.4/32
3ffe::1:303:303/128 3ffe::1:404:404/128

eth1 192.168.1.11/24 10.10.10.7/32 10.10.10.8/32 eth1 192.168.1.12/24

3ffe::1:707:707/128 3ffe::1:808:808/128

6 Nokia 2020
© Nokia Confidential

System Address – AS 65100

R1 – 10.10.10.1/32
R2 – 10.10.10.2/32
R5 – 10.10.10.5/32
R6 – 10.10.10.6/32
R3 – 10.10.10.3/32
R4 – 10.10.10.4/32
R7 – 10.10.10.7/32
R8 – 10.10.10.8/32

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 6
 Physical Port, ISIS Area and Level
PC9 AS 65100 PC10
ISIS Area 49.00 1/1/5
eth1
All routers ISIS Level 2
eth1
1/1/4 1/1/4
R5 R1 R2
R6
1/1/2
1/1/5 1/1/5

1/1/1 1/1/1

1/1/5 1/1/5
1/1/2

PC11 R3 R4 R8 PC12
1/1/4 1/1/4
1/1/5 1/1/5
eth1 eth1

R7

7 Nokia 2020
© Nokia Confidential

R1 to R4 are Border or Core routers

R5 to R8 are Edge routers

Each pair of students has one Border and one Edge routers.

R1, R2, R5 and R6 are in AS 65100

R3, R4, R7 and R8 are in AS 65200

OSPF is used in each AS for router connectivity.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 7
 EVPN VXLAN 1000 and Student Pods
Goal - All PCs can ping with each other over EVPN VXLAN using VNI 1000.
PC9 PC10
Pod1 Pod2
ISIS area 49.02

R5 R1 R2 R6

EVPN-VXLAN
VNI = 1000

PC11 R3 R4 R8 PC12

Pod3 Pod4
ISIS area 49.03 ISIS area 49.04
R7
8 Nokia 2020
© Nokia Confidential

Student1 and student2 – BGP_Pod1

Student3 and student4 – BGP_Pod2

Student5 and student6 – BGP_Pod3

Student7 and student8 – BGP_Pod4

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 8
Student Lab Assignment

Group Border/Core Router Edge Router AS

Student1 R1 R5
Student2 10.10.10.1/32 10.10.10.5/32
(Pod1)

Student3 R2 R6
Student4 10.10.10.2/32 10.10.10.6/32 65100
(Pod2)

Student5 R3 R7
Student6 10.10.10.3/32 10.10.10.7/32
(Pod3)
Student7 R4 R8
Student8 10.10.10.4/32 10.10.10.8/32
(Pod4)

9 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 9
Lab Preparation

Ensure PC9 to PC12 have the following IP addresses for their eth1 interfaces:
• PC9’s eth1 – 192.168.1.9/24
• PC10’s eth1 – 192.168.1.10/24
• PC11’s eth1 – 192.168.1.11/24
• PC12’s eth1 – 192.168.1.12/24

On the PC, use the command, ifconfig eth1 192.168.1.x/24 to set the IP address, if necessary.

10Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 10
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y).

Initial rollback config file’s comment – EVPN VXLAN – Initial.

• /admin rollback revert X

Final rollback config file’s comment – EVPN VXLAN – Final.

To compare current config with the final lab answer:

• /admin rollback compare active-cfg to Y

11Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 11
 Initial Lab Verification

12Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 12
Introduction and Lab Objective

The objective of this lab is to:

• Familiarize with the initial EVPN VXLAN lab setup

13Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 13
Exercise - IGP Config and Verification

Each group login to their Edge routers (e.g., R5 to R8) and invoke the following commands
to verify the ISIS configuration and explain the results:
• /config router isis
• show router isis adjacency
• show router route-table
• ping 10.10.10.X
̵ X can be 1 to 8

14Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 14
Answer - IGP Config and Verification

A:R8>config>router>isis# info
All routers are in ISIS Level 2 domain and they can reach each others’ ----------------------------------------------
system addresses. level-capability level-2
area-id 49.04
level 2
A:R8>config>router>isis# ping 10.10.10.5
wide-metrics-only
PING 10.10.10.5 56 data bytes
exit
64 bytes from 10.10.10.5: icmp_seq=1 ttl=61 time=3.86ms.
interface "system"
64 bytes from 10.10.10.5: icmp_seq=2 ttl=61 time=4.04ms.
no shutdown
64 bytes from 10.10.10.5: icmp_seq=3 ttl=61 time=5.83ms.
exit
interface "toR4"
Each Edge router has only one physical link to the core network: interface-type point-to-point
no shutdown
• R5 can reach the core network via R1 only. exit
no shutdown

A:R5>config>router>isis# show router isis adjacency

===============================================================================
Rtr Base ISIS Instance 0 Adjacency
===============================================================================
System ID Usage State Hold Interface MT-ID
-------------------------------------------------------------------------------
R1 L1L2 Up 24 toR1 0
-------------------------------------------------------------------------------
Adjacencies : 1

15Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 15
 MP-BGP (evpn) Control Plane

16Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 16
Exercise – MP-BGP (evpn) Setup

In EVPN, endpoints’ MAC addresses are learnt via MP-BGP (evpn) message exchange instead of ARP. Each
pair of students config their Edge routers to use MP-BGP (evpn) for endpoints’ MAC address discovery.

Create an MP-iBGP group called EVPN to support evpn address family:

• config router bgp group EVPN
• config router bgp internal
• config router bgp family evpn
Specify all Edge routers as BGP neighbors for exchanging endpoints’ MAC addresses:
• config router bgp neighbor x.x.x.x

Verify and examine the MP-iBGP (evpn) setup on the Edge routers:
• show router bgp neighbor
• show router bgp route evpn mac

17Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 17
Answer – MP-iBGP (evpn) Setup

All Edge routers have MP-iBGP neighbors to all other Edge routers for EVPN endpoints’ MAC addresses discovery.
A:R5>config>router>bgp# info A:R6>config>router>bgp# info
---------------------------------------------- ----------------------------------------------
group "EVPN" group "EVPN"
family evpn family evpn
type internal type internal
neighbor 10.10.10.6 neighbor 10.10.10.5
exit exit
neighbor 10.10.10.7 neighbor 10.10.10.7
exit exit
neighbor 10.10.10.8 neighbor 10.10.10.8
exit exit
exit exit
no shutdown no shutdown

A:R7>config>router>bgp# info A:R8>config>router>bgp# info

---------------------------------------------- ----------------------------------------------
group "EVPN" group "EVPN"
family evpn family evpn
type internal type internal
neighbor 10.10.10.5 neighbor 10.10.10.5
exit exit
neighbor 10.10.10.6 neighbor 10.10.10.6
exit exit
neighbor 10.10.10.8 neighbor 10.10.10.7
exit exit
exit exit
no shutdown no shutdown
18Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 18
Answer – MP-iBGP (evpn) Setup [cont.]
A:R7>config>router>bgp# show router bgp summary
===============================================================================
BGP Router ID:10.10.10.7 AS:65100 Local AS:65100
All MP-iBGP (evpn) neighbors are UP. ===============================================================================
BGP Admin State : Up BGP Oper State : Up
Total Peer Groups : 1 Total Peers : 3
Total VPN Peer Groups : 0 Total VPN Peers : 0
Total BGP Paths : 29 Total Path Memory : 7784
<< skip >>
Total Link State Rem Rts: 0 Total Link State Rem Act Rts: 0

===============================================================================
BGP Summary
===============================================================================
Legend : D - Dynamic Neighbor
===============================================================================
Neighbor
Description
AS PktRcvd InQ Up/Down State|Rcv/Act/Sent (Addr Family)
PktSent OutQ
-------------------------------------------------------------------------------
10.10.10.5
65100 90 0 00h01m09s 0/0/2 (Evpn)
14 0
10.10.10.6
65100 90 0 00h01m09s 2/2/2 (Evpn)
14 0
10.10.10.8
65100 88 0 00h01m09s 0/0/2 (Evpn)
14 0
19Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 19
Answer – MP-iBGP (evpn) Setup [cont.]

There is no MAC address learnt from EVPN’s endpoints as we have not yet setup EVPN VXLAN and thus the PCs connected
to port 1/1/5 of the Edge routers cannot be learnt or discovered.

A:R8# show router bgp routes evpn mac

===============================================================================
BGP Router ID:10.10.10.8 AS:65100 Local AS:65100
===============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete

===============================================================================
BGP EVPN MAC Routes
===============================================================================
Flag Route Dist. MacAddr ESI
Tag Mac Mobility Label1
Ip Address
NextHop
-------------------------------------------------------------------------------
No Matching Entries Found.

20Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 20
 EVPN VXLAN Service

21Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 21
Exercise – EVPN VXLAN Setup

EVPN VXLAN is based on VPLS CLI constructs. Each pair of students provision their Edge routers with
VPLS 1000 as follows:
VXLAN ID (VNI) = 1001
• config vpls 1000 vxlan vni 1 instance 1 create
router-distinguisher = 65100:1000
router-target = target:65100:1000
Enable bgp-evpn and vxlan for VPLS 1000.
• config vpls 1000 bgp-evpn vxlan no shutdown
Use sap 1/1/5:0, which is connected to PCX.

Verify the EVPN setup and explain the results by:

• show service id 1000 base
• show router bgp route evpn mac

22Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 22
Answer – EVPN VXLAN Setup

Edge routers R5 to R8 have the VPLS 1000 enhanced with VXLAN operations as follows:

A:R5# configure service

A:R5>config>service# info
----------------------------------------------
vpls 1000 name "1000" customer 1 create
vxlan instance 1 vni 1001 create
exit
bgp
route-distinguisher 65100:1000
route-target export target:65100:1000 import target:65100:1000
exit
bgp-evpn
vxlan bgp 1 vxlan-instance 1
no shutdown
exit
exit
stp
shutdown
exit
sap 1/1/5:0 create
no shutdown
exit
no shutdown
exit
----------------------------------------------
23Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 23
Answer – EVPN VXLAN Setup [cont.]
A:R5# show service id 1000 base

===============================================================================
VPLS or EVPN VXLAN 1000 is UP. Service Basic Information
===============================================================================
Service Id : 1000 Vpn Id : 0
Service Type : VPLS
MACSec enabled : no
Name : 1000
Description : (Not Specified)
Customer Id : 1 Creation Origin : manual
Last Status Change: 07/01/2020 08:15:08
Last Mgmt Change : 07/01/2020 08:15:08
Etree Mode : Disabled
Admin State : Up Oper State : Up
MTU : 1514
SAP Count : 1 SDP Bind Count : 0
Snd Flush on Fail : Disabled Host Conn Verify : Disabled
SHCV pol IPv4 : None
Propagate MacFlush: Disabled Per Svc Hashing : Disabled
Allow IP Intf Bind: Disabled
Fwd-IPv4-Mcast-To*: Disabled Fwd-IPv6-Mcast-To*: Disabled
Mcast IPv6 scope : mac-based
Def. Gateway IP : None
Def. Gateway MAC : None
Temp Flood Time : Disabled Temp Flood : Inactive
Temp Flood Chg Cnt: 0
SPI load-balance : Disabled
TEID load-balance : Disabled
Src Tep IP : N/A
Vxlan ECMP : Disabled
MPLS ECMP : Disabled

24Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 24
Answer – EVPN VXLAN Setup [cont.]

VPLS or EVPN VXLAN 1000 is UP. VSD Domain : <none>

-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:1/1/5:0 q-tag 1518 1518 Up Up

25Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 25
Exercise – EVPN VXLAN Verification

On the PC, ping to all other PCs connected to the Edge routers. It should be successful through the
EVPN 1000 supporting VXLAN.
• ping 192.168.1.X
̵ X can be 9, 10, 11, or 12

Verify the IP and MAC address learnt over EVPN 1000:

• show router bgp route evpn mac
• show service vxlan
• show service id 1000 base
• show service vxlan
• show router bgp routes evpn mac

Verify the MAC addresses learnt on EVPN 1000 are the MAC addresses of the PCs:
• On the PC, use the command ifconfig eth1 to verify the PC MAC address.

26Nokia 2020
© Nokia Confidential

• ifconfig eth1 192.168.1.9/24 (for PC9)

• ifconfig eth1 192.168.1.10/24 (for PC10)
• ifconfig eth1 192.168.1.11/24 (for PC11)
• ifconfig eth1 192.168.1.12/24 (for PC12)

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 26
Answer – EVPN Verification

Each PC can ping to other PCs on the Edge routers through EVPN 1000 using VNI 1001.

[root@PC9 ~]# ping 192.168.1.10

PING 192.168.1.10 (192.168.1.10) 56(84) bytes of data.
64 bytes from 192.168.1.10: icmp_seq=1 ttl=64 time=5.69 ms
64 bytes from 192.168.1.10: icmp_seq=2 ttl=64 time=5.25 ms

[root@PC9 ~]# ping 192.168.1.11

PING 192.168.1.11 (192.168.1.11) 56(84) bytes of data.
64 bytes from 192.168.1.11: icmp_seq=1 ttl=64 time=7.85 ms
64 bytes from 192.168.1.11: icmp_seq=2 ttl=64 time=4.62 ms

[root@PC9 ~]# ping 192.168.1.12

PING 192.168.1.12 (192.168.1.12) 56(84) bytes of data.
64 bytes from 192.168.1.12: icmp_seq=1 ttl=64 time=7.48 ms
64 bytes from 192.168.1.12: icmp_seq=2 ttl=64 time=2.88 ms

27Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 27
Answer – EVPN Verification [cont.]

R5 learns one only MAC address (i.e., PC’s MAC address) from each Edge Router’s VXLAN Tunnel Endpoint (VTEP).
VTEP receives VXLAN frames that encapsulates overlay IP address (e.g., 192.168.1.X) and payload, and acts as a tunnel
endpoint using the underlay IP address (e.g., 10.10.10.X) to route the VXLAN encapsulated frame.

A:R5# show service id 1000 vxlan

===============================================================================
VPLS VXLAN, Vxlan Instance: 1, VNI: 1001
===============================================================================
Creation Origin: manual
Assisted-Replication: none
RestProtSrcMacAct: none

===============================================================================
VPLS VXLAN service Network Specifics
===============================================================================
-------------------------------------------------------------------------------
Ing Net QoS Policy: none
Ingress FP QGrp : (none) Ing FP QGrp Inst : (none)
VTEP security : disabled MAC Learning : disabled
MAC Aging : disabled Discard Unknown Source : disabled
MAC address limit : 0
===============================================================================

28Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 28
Answer – EVPN Verification [cont.]

VTEPs of VPLS 1000 located on remote Edge routers or PCs.

A:R5# show service vxlan

===============================================================================
VXLAN Tunnel Endpoints (VTEPs)
===============================================================================
VTEP Address Number of Egress VNIs Oper
State
-------------------------------------------------------------------------------
10.10.10.6 1 Up
10.10.10.7 1 Up
10.10.10.8 1 Up
-------------------------------------------------------------------------------
Number of VTEPs: 3

A:R5# show service vxlan 10.10.10.6

===============================================================================
VXLAN Tunnel Endpoint: 10.10.10.6
===============================================================================
Egress VNI Service Id Oper State
-------------------------------------------------------------------------------
1001 1000 Up

29Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 29
Answer – EVPN Verification [cont.]
A:R5>config>service# show router bgp routes evpn mac
===============================================================================
BGP Router ID:10.10.10.5 AS:65100 Local AS:65100
===============================================================================
The endpoints’ (PCs )MAC addresses learnt Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
by each Edge router over EVPN 1000. l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete

===============================================================================
BGP EVPN MAC Routes
===============================================================================
Flag Route Dist. MacAddr ESI
Tag Mac Mobility Label1
Ip Address
NextHop
-------------------------------------------------------------------------------
u*>i 65100:1000 02:00:a8:00:ca:01 ESI-0
0 Seq:0 VNI 1001
n/a
10.10.10.6

u*>i 65100:1000 02:00:a8:00:cb:01 ESI-0

0 Seq:0 VNI 1001
n/a
10.10.10.7

u*>i 65100:1000 02:00:a8:00:cc:01 ESI-0

0 Seq:0 VNI 1001
n/a
MAC address learnt from R8’s EVPN 1000 10.10.10.8

-------------------------------------------------------------------------------
[root@PC12 ~]# ip addr
eth1:
link/ether 02:00:a8:00:cc:01 brd ff:ff:ff:ff:ff:ff

30Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 30
Answer – EVPN Verification [cont.]

The MAC addresses learnt from VPLS or EVPN VXLAN 1000 endpoints.

A:R5# show service id 1000 fdb vxlan vni 1001

===============================================================================
Forwarding Database, Service 1000
===============================================================================
ServId MAC Source-Identifier Type Last Change
Transport:Tnl-Id Age
-------------------------------------------------------------------------------
1000 02:00:a8:00:ca:01 vxlan-1: Evpn 07/01/20 08:57:33
10.10.10.6:1001
1000 02:00:a8:00:cb:01 vxlan-1: Evpn 07/01/20 08:57:44
10.10.10.7:1001
1000 02:00:a8:00:cc:01 vxlan-1: Evpn 07/01/20 08:57:34
10.10.10.8:1001
-------------------------------------------------------------------------------
No. of Entries: 3
-------------------------------------------------------------------------------
Legend: L=Learned O=Oam P=Protected-MAC C=Conditional S=Static Lf=Leaf
===============================================================================

31Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 31
 Debug EVPN VXLAN

32Nokia 2020
© Nokia Confidential

Color legend in this lab guide:

*A:PExx>config>
Configuration display
-----------------------

*A:PExx# show bof

Show commands
=======================

>> Incoming OSPF packet Debug commands

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 32
Exercise – MP-iBGP EVPN Debug

PCs can ping to other PCs over EVPN 1000 because MP-iBGP exchanges EVPN’s MAC endpoints (i.e., VPLS endpoints’ MAC
and IP addresses).

To show MP-iBGP EVPN MAC route exchange, on the Edge router, config a log and debug BGP update packets as follows:
• config log log-id 6
• from debug to session
• /debug router bgp update neighbor 10.10.10.X
• show router bgp routes evpn mac

If there is no BGP EVPN routes due to inactivity timeout, generate some ping traffic among the PCs.

33Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 33
Answer – BGP EVPN Debug

Create the debug log: A:R8>config>log# log-id 6

A:R8>config>log>log-id# info
----------------------------------------------
from debug-trace
to session
no shutdown

A:R8>config>log>log-id# debug router bgp update neighbor 10.10.10.5

Debug BGP Update messages: A:R8#

3 2020/07/01 09:15:11.143 UTC MINOR: DEBUG #2001 Base Peer 1: 10.10.10.5
If there is no BGP EVPN routes due "Peer 1: 10.10.10.5: UPDATE
to inactivity timeout, generate Peer 1: 10.10.10.5 - Received BGP UPDATE:
Withdrawn Length = 0
some ping traffic among the PCs. Total Path Attr Length = 88
Flag: 0x90 Type: 14 Len: 44 Multiprotocol Reachable NLRI:
Address Family EVPN
NextHop len 4 NextHop 10.10.10.5
Type: EVPN-MAC Len: 33 RD: 65100:1000 ESI: ESI-0, tag: 0, mac len: 48 ma
c: 02:00:a8:00:c9:01, IP len: 0, IP: NULL, label1: 1001
Flag: 0x40 Type: 1 Len: 1 Origin: 0
Flag: 0x40 Type: 2 Len: 0 AS Path:
Flag: 0x80 Type: 4 Len: 4 MED: 0
Flag: 0x40 Type: 5 Len: 4 Local Preference: 100
Flag: 0xc0 Type: 16 Len: 16 Extended Community:
target:65100:1000
bgp-tunnel-encap:VXLAN
"

34Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 34
Answer – BGP EVPN Debug [cont.]

A:R8#

4 2020/07/01 09:15:35.669 UTC MINOR: DEBUG #2001 Base Peer 1: 10.10.10.5

"Peer 1: 10.10.10.5: UPDATE
Peer 1: 10.10.10.5 - Send BGP UPDATE:
Withdrawn Length = 0
Total Path Attr Length = 88
Flag: 0x90 Type: 14 Len: 44 Multiprotocol Reachable NLRI:
Address Family EVPN
NextHop len 4 NextHop 10.10.10.8
Type: EVPN-MAC Len: 33 RD: 65100:1000 ESI: ESI-0, tag: 0, mac len: 48 ma
c: 02:00:a8:00:cc:01, IP len: 0, IP: NULL, label1: 1001
Flag: 0x40 Type: 1 Len: 1 Origin: 0
Flag: 0x40 Type: 2 Len: 0 AS Path:
Flag: 0x80 Type: 4 Len: 4 MED: 0
Flag: 0x40 Type: 5 Len: 4 Local Preference: 100
Flag: 0xc0 Type: 16 Len: 16 Extended Community:
target:65100:1000
bgp-tunnel-encap:VXLAN
"

35Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 35
Answer – BGP EVPN Debug [cont.]

R8 learns the below MAC route from R5:

A:R8# show router bgp routes evpn mac
===============================================================================
BGP Router ID:10.10.10.8 AS:65100 Local AS:65100
===============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
l - leaked, x - stale, > - best, b - backup, p - purge
Origin codes : i - IGP, e - EGP, ? - incomplete

===============================================================================
BGP EVPN MAC Routes
===============================================================================
Flag Route Dist. MacAddr ESI
Tag Mac Mobility Label1
Ip Address
NextHop
-------------------------------------------------------------------------------
u*>i 65100:1000 02:00:a8:00:c9:01 ESI-0
0 Seq:0 VNI 1001
n/a
10.10.10.5

-------------------------------------------------------------------------------
Routes : 1

36Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 36
Wrap-up
In this module we have covered the following items:
• Enhance VPLS network service into EVPN VXLAN service and use IP instead of MPLS
as the transport protocol to connect multiple layer 2 EVPNs together
• Set up MP-BGP supporting EVPN address family as EVPN VXLAN’s control plane
protocol
• Set up VXLAN as EVPN VXLAN’s data plane encapsulation protocols to form Virtual
Tunnel Endpoints (VTEPs) for interconnecting EVPN endpoints
• Debug MP-BGP supporting EVPN address family for EVPN MAC route exchange

37Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 37
38Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M06 Ed0 38
 Segment Routing

ER00198-V-2000 V0 - S05M07 Ed0

1 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 1
Learning Objectives
Upon completion of this module, you should be able to:
• Define SRGB, allocate Prefix-SIDs
• Enable SR context within IGP, and ISIS
• Define Prefix-SID index range & offset label value (aka ‘start-label’)
• User assigns a Prefix-SID index or label to the prefix representing the node
(Node-SID)
• Configure SR tunnel table preference value
• Create and verify SR SDPs for network services
• Understand Loop-Free Alternate (LFA)

2 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 2
 ToC Slide

Table of Contents

Lab Setup
Initial Lab Verification
Segment Routing Setup
Segment Routing and LFA Verification
Wrap-up

3 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 3
 Lab Setup

4 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 4
Initial Lab Condition

All routers are in ISIS Level 2.

RSVP-TE and LDP are not setup as Segment Routing (SR) will be used to signal MPLS transport tunnels.

Edge routers R5-R8 and R6-R7 have SDP configured but since MPLS transport signaling, sr-isis is not yet configured, the
SDPs are down.

A:R5>config>service>sdp$ info A:R5>config>service>sdp$ show service sdp

------------------------------
far-end 10.10.10.8 ============================================================================
sr-isis Services: Service Destination Points
keep-alive ============================================================================
shutdown SdpId AdmMTU OprMTU Far End Adm Opr Del LSP Sig
exit ----------------------------------------------------------------------------
no shutdown 8 0 8678 10.10.10.8 Up Down MPLS TLDP
----------------------------------------------------------------------------
Number of SDPs : 1
----------------------------------------------------------------------------
Legend: R = RSVP, L = LDP, B = BGP, M = MPLS-TP, n/a = Not Applicable
I = SR-ISIS, O = SR-OSPF, T = SR-TE, F = FPE

5 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 5
 Router System Addresses
10.10.10.5/32 10.10.10.6/32
3ffe::1:505:505/128 3ffe::1:606:606/128

10.10.10.1/32 10.10.10.2/32
R5 3ffe::1:101:101/128 3ffe::1:202:202/128 R6

R1 R2

R3 R4

10.10.10.3/32 10.10.10.4/32
R7 3ffe::1:303:303/128 3ffe::1:404:404/128 R8

10.10.10.7/32 10.10.10.8/32
3ffe::1:707:707/128 3ffe::1:808:808/128
6 Nokia 2020
© Nokia Confidential

System Address – AS 65100

R1 – 10.10.10.1/32
R2 – 10.10.10.2/32
R5 – 10.10.10.5/32
R6 – 10.10.10.6/32
R3 – 10.10.10.3/32
R4 – 10.10.10.4/32
R7 – 10.10.10.7/32
R8 – 10.10.10.8/32

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 6
AS and Physical Port
AS 65100
1/1/2

1/1/4 1/1/4
R5 R1 R2
R6
1/1/2
1/1/5 1/1/5

1/1/1 1/1/1

1/1/5 1/1/5
1/1/2

R7 R3 R4 R8
1/1/4 1/1/4

1/1/2

7 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 7
ISIS Areas and Student Pods

Pod1 Pod2
ISIS area 49.01 ISIS area 49.02

R5 R1 R2
R6

SR signaled MPLS Transport

Tunnel (sr-isis)

R7 R3 R4 R8

Pod3 Pod4
ISIS area 49.03 ISIS area 49.04

8 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 8
Student Lab Assignment
Group Border/Core Router Edge Router AS

Student1 R1 R5
Student2 10.10.10.1/32 10.10.10.5/32
(Pod1) 3ffe::1:101:101/128 3ffe::1:505:505/128

Student3 R2 R6
Student4 10.10.10.2/32 10.10.10.6/32
(Pod2) 3ffe::1:202:202/128 3ffe::1:606:606/128
65100

Student5 R3 R7
Student6 10.10.10.3/32 10.10.10.7/32
(Pod3) 3ffe::1:303:303/128 3ffe::1:707:707/128
Student7 R4 R8
Student8 10.10.10.4/32 10.10.10.8/32
(Pod4) 3ffe::1:404:404/128 3ffe::1:808:808/128

9 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 9
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y).

Initial rollback config file’s comment - Segment Routing – Initial.

• /admin rollback revert X

Final rollback config file’s comment – Segment Routing – Final.

To compare current config with the final lab answer:

• /admin rollback compare active-cfg to Y

10Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 10
 Initial Lab Verification

11Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 11
Introduction and Lab Objective

The objective of this lab is to:

• Familiar with the initial SR lab setup

12Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 12
Exercise - IGP Config and Verification

Each group login to their Edge routers (e.g., R5 to R8) and invoke the following commands to verify the
ISIS configuration and explain the results.
• /config router isis
• show router isis adjacency
• show router isis prefix-sids
• show router route-table
• ping 10.10.10.X

13Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 13
Answer - IGP Config and Verification

All routers are in ISIS Level 2 domain and they can reach each other.

A:R8>config>router>isis# info A:R8>config>router>isis# ping 10.10.10.5

---------------------------------------------- PING 10.10.10.5 56 data bytes
64 bytes from 10.10.10.5: icmp_seq=1 ttl=61 time=3.86ms.
level-capability level-2
64 bytes from 10.10.10.5: icmp_seq=2 ttl=61 time=4.04ms.
area-id 49.04 64 bytes from 10.10.10.5: icmp_seq=3 ttl=61 time=5.83ms.
level 2
wide-metrics-only
exit
interface "system"
no shutdown
exit
interface "toR7"
interface-type point-to-point
no shutdown
exit
interface "toR4"
interface-type point-to-point
no shutdown
exit
no shutdown

14Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 14
Answer - IGP Config and Verification [cont.]

Each Edge router has two physical links to the core network.
• R5 can reach the core network via R1 or R6.

A:R5# show router isis adjacency

===============================================================================
Rtr Base ISIS Instance 0 Adjacency
===============================================================================
System ID Usage State Hold Interface MT-ID
-------------------------------------------------------------------------------
R6 L2 Up 21 toR6 0
R1 L2 Up 21 toR1 0
-------------------------------------------------------------------------------
Adjacencies : 2

15Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 15
Answer - IGP Config and Verification [cont.]

There is no SID found as we have not yet configured Segment Routing.

A:R5# show router isis prefix-sids

===============================================================================
Rtr Base ISIS Instance 0 Prefix/SID Table
===============================================================================
Prefix SID Lvl/Typ SRMS AdvRtr
MT Flags
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================

16Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 16
Exercise – SDP Tunnel Config and Verification

Each group login to their Edge routers (e.g., R5 to R8) and invoke the following commands to verify the SDP (i.e., MPLS
Transport tunnel) configuration and explain the results:
• /config service sdp X
- Which MPLS transport signaling protocol is used in the SDP config?
• show service sdp
• oam sdp-ping sr-isis X resp-sdp Y

17Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 17
Answer – SDP Tunnel Config and Verification

There is no MPLS Transport Tunnel signaling protocol such as LDP, RSVP-TE or SR-ISIS and thus the SDP tunnel is down.
A:R5>config>service# sdp 8 A:R5# /configure router ldp
A:R5>config>service>sdp# info A:R5>config>router>ldp# info
---------------------------------------------- ----------------------------------------------
far-end 10.10.10.8 interface-parameters
keep-alive exit
shutdown targeted-session
exit exit
no shutdown no shutdown

Segment Routing (FR) does not rely on LDP but LDP should not be shutdown as SR needs TLDP to signal the Service
Tunnels.
A:R5>config>service>sdp# show service sdp

============================================================================
Services: Service Destination Points
============================================================================
SdpId AdmMTU OprMTU Far End Adm Opr Del LSP Sig
----------------------------------------------------------------------------
8 0 0 10.10.10.8 Up Down MPLS TLDP
----------------------------------------------------------------------------
Number of SDPs : 1
----------------------------------------------------------------------------
Legend: R = RSVP, L = LDP, B = BGP, M = MPLS-TP, n/a = Not Applicable
I = SR-ISIS, O = SR-OSPF, T = SR-TE, F = FPE

18Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 18
Answer – SDP Tunnel Config and Verification [cont.]

Since the SDP tunnel is down due to lack of MPLS Transport Tunnel signaling protocol, sdp-ping using sr-isis is not
successful.

A:R5# oam sdp-ping 8 resp-sdp 5

Request Result: Not Sent - Original Sdp Id Down

19Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 19
 Segment Routing Setup

20Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 20
Exercise – ISIS Segment Routing Setup

In Lab 1, SDP is down as we have not yet set sr-isis to signal the tunnels.
Each pair of students login to their Border & Edge routers to configure SR:
• Initialize SRGB with start label 519000 and support 5000 sids.
̵ /config router mpls-labels sr-labels start 519000 end 524000
̵ /config router isis segment-routing prefix-sid-range start-label 519000 max-index 5000
̵ show router mpls-labels label-range

• Router number is the SR SID index (e.g., R5’s SR index is 5). Together with the SR start label or segment, each router in
SR domain has a globally unqiue Segment ID (sid).
̵ /config router isis interface system ipv4-node-sid index X

• Enable ISIS loopfree-alternate and traffic engineering:

̵ /config router isis loopfree-alternate
̵ /config router isis traffic-engineering

• Verify that ISIS can distribute sids for segment routing:

̵ show router isis prefix-sids

21Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 21
Exercise – ISIS Segment Routing Setup [cont.]

• Enable SDP to use sr-isis to signal MPLS transport tunnel instead of LDP or RSVP-TE and verify that the SDP tunnels are
up.
̵ /config service sdp X sr-isis
̵ show service sdp
̵ oam sdp-ping X resp-sdp Y
̵ oam lsp-ping sr-isis prefix 10.10.10.X/32

22Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 22
 Answer – Segment Routing ISIS and MPLS Setup

SR index uses router number. For example, R5 will have ipv4-node-side index 5.

A:R5>config>router# info A:R5>config>router>isis# info

---------------------------------------------- ----------------------------------------------
mpls-labels level-capability level-2
sr-labels start 519000 end 524000 area-id 49.01
exit traffic-engineering
advertise-router-capability as
loopfree-alternate
level 2
wide-metrics-only
exit
interface "system"
ipv4-node-sid index 5
no shutdown
exit
interface "toR6"
interface-type point-to-point
no shutdown
exit
interface "toR1"
interface-type point-to-point
no shutdown
exit
segment-routing
prefix-sid-range start-label 519000 max-index 5000
no shutdown
exit
no shutdown
----------------------------------------------
23Nokia 2020
© Nokia Confidential

Similarly, configure other Edge & Border nodes in respective groups.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 23
 Answer – Segment or MPLS Label Range

Prefix-SID range forms the Segment Routing Global Database (SRGB).

A:R8# show router mpls-labels label-range

============================================================================
Label Ranges
============================================================================
Label Type Start Label End Label Aging Available Total
----------------------------------------------------------------------------
Static 32 18431 - 18400 18400
Dynamic 18432 524287 0 500850 505856
Seg-Route 519000 524000 - 0 5001

When using indexing, Prefix-SID = Start-Label + SID Index.

• E.g., for R2, its SID is 519000 + 2 = 519002

24Nokia 2020
© Nokia Confidential

• Global: Start-label is equal to lowest label value in the SRGB and max-index is equal to the
range size of the SRGB.
• Per-instance: The SRGB is partitioned into non-overlapping sub-ranges using different start-
label values and index-range size.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 24
Answer – Verify ISIS Segment Routing Config

Routers’ sids are successfully distributed via ISIS.

A:R5# show router isis prefix-sids

===============================================================================
Rtr Base ISIS Instance 0 Prefix/SID Table
===============================================================================
Prefix SID Lvl/Typ SRMS AdvRtr
MT Flags
-------------------------------------------------------------------------------
10.10.10.1/32 1 2/Int. N R1
0 NnP
10.10.10.2/32 2 2/Int. N R2
0 NnP
10.10.10.3/32 3 2/Int. N R3
0 NnP
10.10.10.4/32 4 2/Int. N R4
0 NnP
10.10.10.5/32 5 2/Int. N R5
0 NnP SRMS : Y/N = prefix SID advertised by SR Mapping Server (Y)
10.10.10.6/32 6 2/Int. N R6 or not (N)
0 NnP S = SRMS prefix SID is selected to be programmed
10.10.10.7/32 7 2/Int. N R7 Flags: R = Re-advertisement
0 NnP N = Node-SID
10.10.10.8/32 8 2/Int. N R8 nP = no penultimate hop POP
0 NnP E = Explicit-Null
------------------------------------------------------------------------------- V = Prefix-SID carries a value
No. of Prefix/SIDs: 8 (8 unique) L = value/index has local significance
------------------------------------------------------------------------------- ==============================================================

25Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 25
Answer – Verify ISIS Segment Routing Config [cont.]
A:R8# show router isis capabilities level 2

==============================================
Rtr Base ISIS Instance 0 Capabilities
==============================================

Displaying Level 2 capabilities

----------------------------------------------
LSP ID : R1.00-00
Router Cap : 10.10.10.1, D:0, S:0
TE Node Cap : B E M P
SR Cap: IPv4 MPLS-IPv6
SRGB Base:519000, Range:5001
SR Alg: metric based SPF
Node MSD Cap: BMI : 12 ERLD : 15

LSP ID : R2.00-00
Router Cap : 10.10.10.2, D:0, S:0
TE Node Cap : B E M P
SR Cap: IPv4 MPLS-IPv6
SRGB Base:519000, Range:5001
SR Alg: metric based SPF
Node MSD Cap: BMI : 12 ERLD : 15

LSP ID : R3.00-00
Router Cap : 10.10.10.3, D:0, S:0
TE Node Cap : B E M P
SR Cap: IPv4 MPLS-IPv6
SRGB Base:519000, Range:5001
SR Alg: metric based SPF
Node MSD Cap: BMI : 12 ERLD : 15

26Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 26
Answer – Verify ISIS Segment Routing Config [cont.]
LSP ID : R4.00-00
Router Cap : 10.10.10.4, D:0, S:0
TE Node Cap : B E M P
SR Cap: IPv4 MPLS-IPv6
SRGB Base:519000, Range:5001
SR Alg: metric based SPF
Node MSD Cap: BMI : 12 ERLD : 15
LSP ID : R5.00-00
Router Cap : 10.10.10.5, D:0, S:0
TE Node Cap : B E M P
SR Cap: IPv4 MPLS-IPv6
SRGB Base:519000, Range:5001
SR Alg: metric based SPF
Node MSD Cap: BMI : 12 ERLD : 15

LSP ID : R6.00-00
Router Cap : 10.10.10.6, D:0, S:0
TE Node Cap : B E M P
SR Cap: IPv4 MPLS-IPv6
SRGB Base:519000, Range:5001
SR Alg: metric based SPF
Node MSD Cap: BMI : 12 ERLD : 15 LSP ID : R8.00-00
Router Cap : 10.10.10.8, D:0, S:0
LSP ID : R7.00-00 TE Node Cap : B E M P
Router Cap : 10.10.10.7, D:0, S:0 SR Cap: IPv4 MPLS-IPv6
TE Node Cap : B E M P SRGB Base:519000, Range:5001
SR Cap: IPv4 MPLS-IPv6 SR Alg: metric based SPF
SRGB Base:519000, Range:5001 Node MSD Cap: BMI : 12 ERLD : 15
SR Alg: metric based SPF
Node MSD Cap: BMI : 12 ERLD : 15 Level (2) Capability Count : 8
========================================

27Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 27
Answer – Verify ISIS Segment Routing Config [cont.]
A:R8# show router isis database R5.00-00 detail

===============================================================================
Rtr Base ISIS Instance 0 Database (detail)
===============================================================================

Displaying Level 1 database

-------------------------------------------------------------------------------
Level (1) LSP Count : 0

Displaying Level 2 database

-------------------------------------------------------------------------------
LSP ID : R5.00-00 Level : L2
Sequence : 0x37 Checksum : 0xcf5d Lifetime : 1158
Version : 1 Pkt Type : 20 Pkt Ver : 1
Attributes: L1L2 Max Area : 3 Alloc Len : 191
SYS ID : 0100.1001.0005 SysID Len : 6 Used Len : 191

TLVs :
Area Addresses:
Area Address : (2) 49.01
Supp Protocols:
Protocols : IPv4
IS-Hostname : R5
Router ID :
Router ID : 10.10.10.5
Router Cap : 10.10.10.5, D:0, S:0
TE Node Cap : B E M P
SR Cap: IPv4 MPLS-IPv6
SRGB Base:519000, Range:5001
SR Alg: metric based SPF
Node MSD Cap: BMI : 12 ERLD : 15

28Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 28
Answer – Verify ISIS Segment Routing Config [cont.]

I/F Addresses :
I/F Address : 10.1.5.5
I/F Address : 10.5.6.5
I/F Address : 10.10.10.5
TE IS Nbrs :
Nbr : R1.00
Default Metric : 10
Sub TLV Len : 19
IF Addr : 10.1.5.5
Nbr IP : 10.1.5.1
Adj-SID: Flags:v4VL Weight:0 Label:524283

29Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 29
Answer – Verify ISIS Segment Routing Config [cont.]

TE IS Nbrs :
Nbr : R6.00
Default Metric : 10
Sub TLV Len : 19
IF Addr : 10.5.6.5
Nbr IP : 10.5.6.6
Adj-SID: Flags:v4VL Weight:0 Label:524284
TE IP Reach :
Default Metric : 10
Control Info: , prefLen 28
Prefix : 10.1.5.0
Default Metric : 10
Control Info: , prefLen 28
Prefix : 10.5.6.0
Default Metric : 0
Control Info: S, prefLen 32
Prefix : 10.10.10.5
Sub TLV :
Prefix-SID Index:5, Algo:0, Flags:NnP

Level (2) LSP Count : 1

------------------------------------------------------------

30Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 30
Answer – Verify ISIS Segment Routing Config [cont.]

Control Info : D = Prefix Leaked Down

S = Sub-TLVs Present
Attribute Flags : N = Node Flag
R = Re-advertisement Flag
X = External Prefix Flag
E = Entropy Label Capability (ELC) Flag
Adj-SID Flags : v4/v6 = IPv4 or IPv6 Address-Family
B = Backup Flag
V = Adj-SID carries a value
L = value/index has local significance
S = Set of Adjacencies
P = Persistently allocated
Prefix-SID Flags : R = Re-advertisement Flag
N = Node-SID Flag
nP = no penultimate hop POP
E = Explicit-Null Flag
V = Prefix-SID carries a value
L = value/index has local significance
Lbl-Binding Flags: v4/v6 = IPv4 or IPv6 Address-Family
M = Mirror Context Flag
S = SID/Label Binding flooding
D = Prefix Leaked Down
A = Attached Flag
===============================================================================

31Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 31
Answer – Verify ISIS Segment Routing Config [cont.]

Enable SDP to use ISIS segment routing to signal MPLS transport tunnels.
A:R5>config>service# info
----------------------------------------------
sdp 8 mpls create
far-end 10.10.10.8
sr-isis
keep-alive
shutdown
exit
no shutdown
exit
----------------------------------------------
A:R5>config>service# show service sdp
With sr-isis signaling setup, SDPs are now up. ============================================================================
Services: Service Destination Points
============================================================================
SdpId AdmMTU OprMTU Far End Adm Opr Del LSP Sig
----------------------------------------------------------------------------
8 0 8682 10.10.10.8 Up Up MPLS I TLDP
----------------------------------------------------------------------------
Number of SDPs : 1
----------------------------------------------------------------------------
Legend: R = RSVP, L = LDP, B = BGP, M = MPLS-TP, n/a = Not Applicable
I = SR-ISIS, O = SR-OSPF, T = SR-TE, F = FPE

Note that TLDP is used for service tunnel signaling and thus LDP config of the service routers cannot be shutdown.

32Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 32
Answer – Verify MPLS Transport Tunnel

MPLS transport tunnels using sr-isis as the signaling protocol are up.

A:R8# oam lsp-ping sr-isis prefix 10.10.10.5/32

LSP-PING 10.10.10.5/32: 80 bytes MPLS payload
Seq=1, send from intf toR4, reply from 10.10.10.5
udp-data-len=32 ttl=255 rtt=6.61ms rc=3 (EgressRtr)

---- LSP 10.10.10.5/32 PING Statistics ----

1 packets sent, 1 packets received, 0.00% packet loss
round-trip min = 6.61ms, avg = 6.61ms, max = 6.61ms, stddev = 0.000ms

A:R8# oam lsp-ping sr-isis prefix 10.10.10.6/32

LSP-PING 10.10.10.6/32: 80 bytes MPLS payload
Seq=1, send from intf toR4, reply from 10.10.10.6
udp-data-len=32 ttl=255 rtt=4.81ms rc=3 (EgressRtr)

---- LSP 10.10.10.6/32 PING Statistics ----

1 packets sent, 1 packets received, 0.00% packet loss
round-trip min = 4.81ms, avg = 4.81ms, max = 4.81ms, stddev = 0.000ms

33Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 33
Answer – Verify SDP Segment Routing

SDP can now use sr-isis to establish MPLS transport tunnel to its far-end Edge router.

A:R8# oam sdp-ping 5 resp-sdp 8

--------------------------------------------------------------------
Actual IP Address - Local : 10.10.10.8
Expected Peer IP - Remote : 10.10.10.8
Actual IP Address - Remote : 10.10.10.5
Expected Peer IP - Local : 10.10.10.5
IP Address Mismatch : No
--------------------------------------------------------------------
Err SDP-ID Info Local Remote
--------------------------------------------------
SDP-ID: 5 8
Administrative State: Up Up
Operative State: Up Up
Path MTU: 8682 N/A
Response SDP Used: Yes
IP Interface State: Up
Forwarding Class be be
Profile In Out

Request Result: Sent - Reply Received

RTT: 5.26(ms)

34Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 34
Answer – Verify SDP Segment Routing [cont.]

The command oam sdp-ping 5 resp-sdp 8 uses the segment ID or MPLS labels we specified in the ISIS config
previously.
• prefix-sid-range start-label 519000 max-index 5000
• ipv4-node-sid index 5

Instructor log on to the hypervisor that hosts the 8 7750 vSIMs (R1 to R8) to use tcpdump to capture the MPLS packet
between Edge and Core routers to illustrate the Segment ID (i.e., MPLS transport label).
• vnet26 is the Ethernet Bridge (i.e., network link) that connects R8 and R4.
[root@vsim69 ~]# tcpdump -i vnet62 mpls -vvv
tcpdump: WARNING: vnet62: no IPv4 address assigned
tcpdump: listening on vnet62, link-type EN10MB (Ethernet), capture size
65535 bytes
00:32:42.248671 MPLS (label 519005, exp 0, ttl 255)
(label 1 (router alert), exp 0, [S], ttl 1)
00:32:42.253547 MPLS (label 519008, exp 0, ttl 252)
(label 1 (router alert), exp 0, [S], ttl 1)

• R5’s sid or MPLS transport label = 519005

• R8’s sid or MPLS transport label = 519008

35Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 35
Answer – Verify SDP Segment Routing [cont.]

You can verify the same by utilizing the tools dump command.

A:R8# tools dump router segment-routing tunnel

==============================================================================
Legend: (B) - Backup Next-hop for Fast Re-Route
(D) - Duplicate
label stack is ordered from top-most to bottom-most
==============================================================================
-----------------------------------------------------------------------------+
Prefix
Sid-Type Fwd-Type In-Label Prot-Inst
Next Hop(s) Out-Label(s) Interface/
Tunnel-ID
-----------------------------------------------------------------------------+
10.10.10.1
Node Orig/Transit 519001 ISIS-0
10.4.8.4 519001 toR4
(B)10.7.8.7 519001 toR7
10.10.10.2
Node Orig/Transit 519002 ISIS-0
10.4.8.4 519002 toR4
10.10.10.3
Node Orig/Transit 519003 ISIS-0
10.4.8.4 519003 toR4
(B)10.7.8.7 519003 toR7
10.10.10.4
Node Orig/Transit 519004 ISIS-0
10.4.8.4 519004 toR4
10.10.10.5
Node Orig/Transit 519005 ISIS-0
10.4.8.4 519005 toR4
(B)10.7.8.7 519005 toR7
10.10.10.6
Node Orig/Transit 519006 ISIS-0
10.4.8.4 519006 toR4
10.10.10.7
Node Orig/Transit 519007 ISIS-0
10.7.8.7 519007 toR7
10.10.10.8
Node Terminating 519008 ISIS-0
10.4.8.4
Adjacency Transit 524283 ISIS-0
10.4.8.4 3 toR4
10.7.8.7
Adjacency Transit 524284 ISIS-0
10.7.8.7 3 toR7
-----------------------------------------------------------------------------+
No. of Entries: 10
-----------------------------------------------------------------------------+

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 36
Answer – Verify
Answer SDP
– Verify Segment
SDP SegmentRouting
Routing[cont.]
[cont.]
You can verify the same by utilizing the tools dump command.
Switch to notes view!
A:R5# tools dump router segment-routing tunnel
==============================================================================
Legend: (B) - Backup Next-hop for Fast Re-Route
(D) - Duplicate
label stack is ordered from top-most to bottom-most
==============================================================================
-----------------------------------------------------------------------------+
Prefix
Sid-Type Fwd-Type In-Label Prot-Inst
Next Hop(s) Out-Label(s) Interface/
Tunnel-ID
-----------------------------------------------------------------------------+
10.10.10.1
Node Orig/Transit 519001 ISIS-0
10.1.5.1 519001 toR1
37Nokia 2020
© Nokia Confidential
10.10.10.2
Node Orig/Transit 519002 ISIS-0
10.1.5.1 519002 toR1
10.10.10.3
Node Orig/Transit 519003 ISIS-0
10.1.5.1 519003 toR1
10.10.10.4
Node Orig/Transit 519004 ISIS-0
10.1.5.1 519004 toR1
10.10.10.5
Node Terminating 519005 ISIS-0
10.10.10.6
Node Orig/Transit 519006 ISIS-0
10.5.6.6 519006 toR6
10.10.10.7
Node Orig/Transit 519007 ISIS-0
10.1.5.1 519007 toR1
10.10.10.8
Node Orig/Transit 519008 ISIS-0
10.1.5.1 519008 toR1
10.1.5.1
Adjacency Transit 524283 ISIS-0
10.1.5.1 3 toR1
10.5.6.6
Adjacency Transit 524284 ISIS-0
10.5.6.6 3 toR6
-----------------------------------------------------------------------------+
No. of Entries: 10
-----------------------------------------------------------------------------+

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 37
 Segment Routing and LFA
Verification

38Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 38
Exercise – Loop-Free Alternate

Explain what is Loop-Free Alternate (LFA) in MPLS.

Examine Edge router’s forwarding table using the following commands and explain why some
destinations have LFA but some do not.
• show router fp-tunnel-table 1
• show router tunnel-table
• show router tunnel-table 10.10.10.X/32 detail
̵ X is the far-end router

39Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 39
Answer – Loop-Free Alternate (LFA)

LFA is a node other than the primary neighbor. The backup routes (repair paths) are precomputed and
installed in the router as the backup for the primary paths.

Traffic is redirected to an LFA after a network failure before IGP convergence (can take seconds) is
completed to achieve
< 50ms failure downtime.

LFA makes the forwarding decision without any knowledge of the failure and thus it must neither use a
failed element nor use a protecting node to forward traffic (i.e., an LFA must not cause loops).

40Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 40
Answer – Loop-Free Alternate (LFA) [cont.]
A:R8# show router fp-tunnel-table 1
============================================================================
IPv4 Tunnel Table Display
For R8 to R5, it uses segment or MPLS label Legend:
519005, which is the shortest path via R4 B - FRR Backup
============================================================================
(10.4.8.4) to R5. Destination Protocol Tunnel-ID
Lbl
• A TE path will contain more segments or MPLS NextHop Intf/Tunnel
labels for a given destination. ----------------------------------------------------------------------------
<< skip >>
10.10.10.2/32 SR-ISIS-0 -
519002
10.4.8.4 1/1/4
10.10.10.3/32 SR-ISIS-0 -
519003
10.4.8.4 1/1/4
519003
A LFA via R7 (10.7.8.7) is pre-computed 10.7.8.7(B)
10.10.10.4/32 SR-ISIS-0
1/1/2
-
and installed as a backup. 519004
10.4.8.4 1/1/4
10.10.10.5/32 SR-ISIS-0 -
519005
For R8 to R6, there is no LFA as failover 10.4.8.4
519005
Has LFA 1/1/4

traffic from R8 to R7 will loopback to R8 10.7.8.7(B) 1/1/2

10.10.10.6/32 SR-ISIS-0 -
and use the failed R8-R4 link. 519006 Do not has LFA
10.4.8.4 1/1/4
----------------------------------------------------------------------------
Total Entries : 9

41Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 41
Answer – Tunnel-Table

Each router in SR domain maintains a full mesh segment or MPLS tunnels to the remote destinations.
A:R8# show router tunnel-table

===============================================================================
IPv4 Tunnel Table (Router: Base)
===============================================================================
Destination Owner Encap TunnelId Pref Nexthop Metric
Color
-------------------------------------------------------------------------------
10.4.8.4/32 isis (0) MPLS 524290 11 10.4.8.4 0
10.7.8.7/32 isis (0) MPLS 524289 11 10.7.8.7 0
10.10.10.1/32 [L] isis (0) MPLS 524293 11 10.4.8.4 30
10.10.10.2/32 isis (0) MPLS 524294 11 10.4.8.4 20
10.10.10.3/32 [L] isis (0) MPLS 524295 11 10.4.8.4 20
10.10.10.4/32 isis (0) MPLS 524292 11 10.4.8.4 10
10.10.10.5/32 sdp MPLS 5 5 10.10.10.5 0
10.10.10.5/32 [L] isis (0) MPLS 524296 11 10.4.8.4 40
10.10.10.6/32 isis (0) MPLS 524297 11 10.4.8.4 30
10.10.10.7/32 isis (0) MPLS 524291 11 10.7.8.7 10
-------------------------------------------------------------------------------
Flags: B = BGP or MPLS backup hop available
L = Loop-Free Alternate (LFA) hop available
E = Inactive best-external BGP route
k = RIB-API or Forwarding Policy backup hop
===============================================================================

42Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 42
Answer – Tunnel-Table and Tunnel Preference [cont.]
Sr-isis tunnel has preference 11, which has lower priority than tunnels setup by SDP (5), RSVP-TE (7) and LDP (9). If sr-isis
tunnels are used where other higher preference tunnels existed, use the following command to increase SR tunnel
preference.
• /configure router isis segment-routing tunnel-table-pref 6
A:R8# show router tunnel-table 10.10.10.5/32 detail

===============================================================================
Tunnel Table (Router: Base)
===============================================================================
Destination : 10.10.10.5/32
NextHop : 10.10.10.5
Tunnel Flags : (Not Specified)
Age : 00h39m10s
CBF Classes : (Not Specified)
Owner : sdp Encap : MPLS
Tunnel ID : 5 Preference : 5
Tunnel Label : - Tunnel Metric : 0
Tunnel MTU : 8682 Max Label Stack : 1
-------------------------------------------------------------------------------
Destination : 10.10.10.5/32 [L]
NextHop : 10.4.8.4
Tunnel Flags : has-lfa entropy-label-capable
Age : 00h39m10s
CBF Classes : (Not Specified)
Owner : isis (0) Encap : MPLS
Tunnel ID : 524296 Preference : 11
Tunnel Label : 519005 Tunnel Metric : 40
Tunnel MTU : 8686 Max Label Stack : 1
-------------------------------------------------------------------------------
Number of tunnel-table entries : 2
Number of tunnel-table entries with LFA : 1
===============================================================================

43Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 43
Wrap-up
In this module we have covered the following items:
• Define SRGB, allocate Prefix-SIDs
• Enable SR context within IGP, and ISIS
• Define Prefix-SID index range & offset label value (aka ‘start-label’)
• User assigns a Prefix-SID index or label to the prefix representing the node (Node-
SID)
• Configure SR tunnel table preference value
• Create and verify SR SDPs for network services
• Understand Loop-Free Alternate (LFA)

44Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 44
45Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S05M07 Ed0 45
 QoS

ER00198-V-2000 V0 - S06M01 Ed0

1 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 1
Learning Objectives
Upon completion of this module, you should be able to:
• Configure QoS Classification and Marking
- Create a SAP-ingress and SAP-ingress policy to specify IP criteria for marking traffic,
create queues and assign forwarding classes to queues
- Create Network and Network queue policy’s to consistently mark and queue traffic
transiting the end to end QoS network
- Verify that the SAP policy and network policies have been properly configured and
applied
• Configure QoS using policers instead of queues
- Configure and apply a scheduler policy
- Change the SAP-ingress policy to specify the parent scheduler for each queue & the
parameters with which it will compete for bandwidth
- Verify that the scheduler policy has been properly configured and applied
• Configure and verify hierarchical scheduling

2 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 2
 ToC Slide

Table of Contents

Lab- QoS Classification and Marking

Lab- Policing vs Queuing
Lab- Default vs. Hierarchical Scheduling
Wrap-up

3 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 3
 Lab- QoS Classification and
Marking

4 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 4
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y).

Initial rollback config file’s comment - Prerequsite for QOS.

• /admin rollback revert X

Final rollback config file’s comment - Sap-Ingress-QoS-policy

To compare current config with the final lab answer:

• /admin rollback compare active-cfg to Y

5 Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 5
 Choices of QoS Lab

• Objective:
- Configure QoS Classification and Marking.
192.168.5.9/24 192.168.5.10/24
4
PC9 R5 R1 R6 PC10
1/1/5:7 1/1/5 1/1/6 eth1
eth1 1/1/4 1/1/7 1/1/5:7
CE PE P PE CE2

• Exercise:
- Configure the SAP-ingress policy each queue and the parameters with which it will compete for bandwidth
- Verify that the SAP policy has been properly configured and applied.

192.168.5.11/24 192.168.5.12/24
PC11 R7 R3 R8 PC12
1/1/5:7 1/1/5 1/1/6 eth1
eth1 1/1/4 1/1/7 1/1/5:7
CE PE P PE CE2

6 Nokia 2020
© Nokia Confidential

Objective:
Students will learn that there are several stages in QoS-aware packet processing, including
classification, buffer acceptance/rejection, queuing, scheduling, policing, as well as marking and
re-marking. Correspondingly, there are different types of policies, aimed at implementing the
packet processing required at each one of those stages. Students will configure and verify
Quality of Service policies.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 6
 A Brief Note on QoS

Forwarding Class (FC)

PE P PE
Service N/w N/w N/w N/w Service
Ingress Egress Egress Egress Egress Ingress

Data flow
queue policer

7 Nokia 2020
© Nokia Confidential

When a packet arrives at a router, it needs to be classified as belonging to a forwarding class

(FC), regardless of whether it arrives via a SAP or via a network interface. The FC is an internal
attribute that will determine how the packet is treated during the time it remains in the router.
When the packet leaves the router, however, the FC is removed from it and, if needed, the
packet can be marked or re-marked with known values in one or more of its headers to maintain
consistent treatment throughout the network.
It is also important to mention that a packet is processed twice within each router, either by a
queue or by a policer: once as it enters the router and once more after it goes across the switch
fabric to the port that will be used to forward the packet to the next network element. The
ingress port will be an access port if the packet enters through a SAP or it will be a network port
if this router is not the ingress PE. Similarly, the egress port will be a network port if this router is
not yet the egress PE router or it will be an access port if this router is the egress PE router and
the packet will exit the service provider network through a SAP.
For these reasons, classification happens on ingress SAPs and ingress network interfaces, and
queues need to be created on SAP ingress, on network egress, on network ingress and on SAP
egress points. In this lab, we will learn how the different parameters in QoS policies control the
classification, queuing and marking that need to take place at all these points.
It is important to mention that there are default policies for the network side of a router (the
one coming from or going to other service provider routers) that may suit the customer
requirements for the packets to be properly treated from end to end, as long as the SAP-
Ingress and SAP-Egress policies are properly configured, according to the customer needs. For
this lab students will create and apply non-default SAP-Ingress/Egress, Network and Network-
Queue policies.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 7
 QoS Classification and Marking Policies
configure qos copy network 1 10 configure qos copy network 1 10
configure qos network 10 configure qos network 10
… …
configure router interface "toRX" qos 10 configure router interface "toRX" qos 10

configure qos copy network-queue default NQ1 configure qos copy network-queue default NQ1
configure qos network-queue NQ1 configure qos network-queue NQ1
… …
configure port 1/1/X ethernet network queue-policy NQ1 configure port 1/1/X ethernet network queue-policy NQ1
configure card 1 fp 1 ingress network queue-policy "NQ1 configure card 1 fp 1 ingress network queue-policy "NQ1

configure qos configure qos

• sap-ingress=10 • sap-egress=10

configure service configure service

• Epipe=1 • Epipe 1
• sap 1/1/5:7 • sap 1/1/5:7
• ingress qos 10 • egress qos 10
PE P PE
Service N/w N/w N/w N/w Service
Ingress Egress Egress Egress Egress Ingress
R5 R1 R6
Data flow

8 Nokia 2020
© Nokia Confidential

QoS Planning

Source Forwarding Class Queue Exp Classification

Ping EF 6 6 ICMP

Video1 H2 5 5 UDP pt 1234

Video2 AF 4 4 UDP pt 5678

SFTP L2 3 3 TCP

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 8
 Creating and Applying a SAP-Ingress QoS Policy

Service Ingress QoS policy “SAP-Ingress”

Defines traffic classification and marking
Switch
Policing Q’s buffering/scheduling Fabric
Determines Packet profile In/out

PE P PE
Service N/w N/w N/w N/w Service
Ingress Egress Egress Egress Egress Ingress

R5 R1 R6
Data flow

9 Nokia 2020
© Nokia Confidential

In this lab, the students will learn how to configure the different components of a SAP-Ingress
QoS policy. A SAP-Ingress QoS policy establishes the following packet-processing criteria:
Classifies each packet as belonging to a forwarding class, based on user-defined criteria:
• Assigns high or low priority status to each packet, which in turn specifies if the packet has a
low or high dropping precedence.
• It can create traffic queues, defining:
- Type (expedited, best-effort, auto-expedited)
- Mode (priority, profile)
- Allocated buffer size (committed and maximum)
- Rate (committed and maximum) at which stored packets will exit the queue.
• Alternatively or additionally, it can create traffic policers, defining:
- Rate (committed and maximum) at which packets will be forwarded
• Assigns forwarding classes to queues and/or policers
• Marks or re-marks packets, if needed.
Each group will create on their PE router (R5-R8) a SAP-Ingress QoS policy with a policy Id equal
to 10. In it, packets will be classified into different FCs based on the following criteria:
• If the protocol running on top of IP is ICMP, the packet will be considered as ping traffic and
classified as Expedited Forwarding (EF).
• If the transport protocol is UDP and the destination port number is 1234, the packet will be
considered part of a video download and classified as High-2 (H2).
• If the transport protocol is UDP and the destination port number is 5678, the packet will be
considered part of an additional video download and classified as Assured Forwarding (AF).
• Lastly, if the transport protocol is TCP, the packet will be considered part of an FTP
transaction and classified as Low-2 (L2).
• All other traffic, if any, will be treated as Best Effort (BE).

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 9
Creating and
Creating Applying
and a SAP-Ingress
Applying a SAP-IngressQoS
QoSPolicy
Policy[cont.]
[cont.]
These classification rules can be configured on the PE routers using the following commands.
Switch to notes view!
*A:R5# configure qos sap-ingress 10 create
*A:R5>…description "Ping EF Q6 Video1 H2 Q5 Video2 AF Q4 & FTP L2 Q3"
*A:R5>config>qos>sap-ingress# ip-criteria entry 10 create
*A:R5>config>qos>sap-ingress>ip-criteria>entry# description "Ping"
*A:R5>config>qos>sap-ingress>ip-criteria>entry# match protocol "icmp"
*A:R5>config>qos>sap-ingress>ip-criteria>entry>match# back
*A:R5>config>qos>sap-ingress>ip-criteria>entry# action fc ef
*A:R5>config>qos>sap-ingress>ip-criteria>entry# back
*A:R5>config>qos>sap-ingress>ip-criteria# back

*A:R5>config>qos>sap-ingress# ip-criteria entry 20 create

*A:R5>config>qos>sap-ingress>ip-criteria>entry# description "Video1"
*A:R5>...>ip-criteria>entry# match protocol "udp" dst-port eq 1234
*A:R5>config>qos>sap-ingress>ip-criteria>entry# action fc h2
*A:R5>config>qos>sap-ingress>ip-criteria>entry# back
*A:R5>config>qos>sap-ingress>ip-criteria# back
10Nokia 2020
© Nokia Confidential
*A:R5>config>qos>sap-ingress# ip-criteria entry 30 create
*A:R5>config>qos>sap-ingress>ip-criteria>entry# description " Video2"
*A:R5>…>sap-ingress>ip-criteria>entry# match protocol "udp" dst-port eq 5678
*A:R5>config>qos>sap-ingress>ip-criteria>entry# action fc af
*A:R5>config>qos>sap-ingress>ip-criteria>entry# back
*A:R5>config>qos>sap-ingress>ip-criteria# back

*A:R5>config>qos>sap-ingress# ip-criteria entry 40 create

*A:R5>config>qos>sap-ingress>ip-criteria>entry# description "FTP"
*A:R5>config>qos>sap-ingress>ip-criteria>entry# match protocol "tcp"
*A:R5>config>qos>sap-ingress>ip-criteria>entry>match# back
*A:R5>config>qos>sap-ingress>ip-criteria>entry# action fc l2
*A:R5>config>qos>sap-ingress>ip-criteria>entry# exit all

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 10
Creating and
Creating Applying
and a SAP-Ingress
Applying a SAP-IngressQoS
QoSPolicy
Policy[cont.]
[cont.]
These classification rules can be configured PE routers using the following commands.
Please note
Switch tosap-ingress
notes view! commands will need to be executed on all PE routers, R5 is provided
as an example.

*A:R5# configure qos sap-ingress 10

*A:R5>config>qos>sap-ingress# info
----------------------------------------------
queue 1 create
exit
queue 11 multipoint create
exit
ip-criteria
entry 10 create
description "Ping"
match protocol icmp
exit
action fc "ef"
exit
11Nokia 2020
© Nokia Confidential
entry 20 create
description "VLC1"
match protocol udp
dst-port eq 1234
exit
action fc "h2"
exit
entry 30 create
description "VLC2"
match protocol udp
dst-port eq 5678
exit
action fc "af"
exit
entry 40 create
description "FTP"
match protocol tcp
exit
action fc "l2"
exit
exit
----------------------------------------------

To properly process the packets, different queues and/or polices need to be created so that
independent resources are assigned to the different traffic flows. When a SAP-Ingress QoS
policy is created, two queues are created by default: queue 1 for unicast packets and queue 11
for multipoint packets (those that need to be replicated onto more than one output).
For this lab, each group will create 4 more queues within the same SAP-Ingress QoS policy,
each one to store packets from a different traffic flow.
Queue 3, which will be assigned to FTP traffic, will have a committed rate of 2 Mbps (CIR), and
the forwarding rate can go up to 7 Mbps (PIR) to accommodate packet bursts.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 11
Creating and
Creating Applying
and a SAP-Ingress
Applying a SAP-IngressQoS
QoSPolicy
Policy[cont.]
[cont.]
Queues 4 and 5, which will be assigned to video traffic, will each have a committed rate of 500
Kbps (CIR),toand
Switch a peak
notes view!information rate (PIR) of 2.5 Mbps to accommodate packet bursts.
These queues will use a non-default burst-limit value of 120,000 bytes. In general, highly
bursty traffic that can tolerate some delay needs a large burst-limit to reduce the probability
of packets being dropped.
Lastly, Queue 6, which will be assigned to Ping traffic, will have a committed rate of 150 Kbps
(CIR), and a peak information rate (PIR) also of 150 Kbps.
All queues will use default values for the committed and maximum buffer size. The commands
needed to create these queues are shown below.

*A:R5# configure qos sap-ingress 10

*A:R5>config>qos>sap-ingress# queue 6 create
*A:R5>config>qos>sap-ingress>queue# rate 150 cir 150
*A:R5>config>qos>sap-ingress>queue# back

*A:R5>config>qos>sap-ingress# queue 5 create

12Nokia 2020
© Nokia Confidential
*A:R5>config>qos>sap-ingress>queue# rate 2500 cir 500
*A:R5>config>qos>sap-ingress>queue# burst-limit 120000 bytes
*A:R5>config>qos>sap-ingress>queue# back

*A:R5>config>qos>sap-ingress# queue 4 create

*A:R5>config>qos>sap-ingress>queue# rate 2500 cir 500
*A:R5>config>qos>sap-ingress>queue# burst-limit 120000 bytes
*A:R5>config>qos>sap-ingress>queue# back

*A:R5>config>qos>sap-ingress# queue 3 create

*A:R5>config>qos>sap-ingress>queue# rate 7000 cir 2000
*A:R5>config>qos>sap-ingress>queue# back
*A:R5>config>qos>sap-ingress# exit all
... Output omitted ...

*A:R5>config>qos>sap-ingress# info
----------------------------------------------
... Output omitted ...
queue 3 create
rate 7000 cir 2000
exit
queue 4 create
rate 2500 cir 500
burst-limit 120000 bytes
exit
queue 5 create
rate 2500 cir 500
burst-limit 120000 bytes
exit
queue 6 create
rate 150 cir 150
... Output omitted ...
----------------------------------------------

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 12
Creating and
Creating Applying
and a SAP-Ingress
Applying a SAP-IngressQoS
QoSPolicy
Policy[cont.]
[cont.]
As the final step to configure the SAP-Ingress QoS policy, FCs need to be mapped to the
corresponding queues.
Switch to notes view!The commands needed for this are shown below. All FCs not explicitly
mapped will use either queue 1 or queue 11, depending on whether they correspond to unicast
or multipoint traffic, respectively.

*A:R5# configure qos sap-ingress 10

*A:R5>config>qos>sap-ingress# fc "af" create queue 4
*A:R5>config>qos>sap-ingress# fc "ef" create queue 6
*A:R5>config>qos>sap-ingress# fc "h2" create queue 5
*A:R5>config>qos>sap-ingress# fc "l2" create queue 3

*A:R5>config>qos>sap-ingress# info
fc "af" create
queue 4
exit
13Nokia 2020
© fc "ef" create Nokia Confidential
queue 6
exit
fc "h2" create
queue 5
exit
fc "l2" create
queue 3
exit
... Output omitted ...

Once the SAP-Ingress policy is complete, it can be applied to the Epipe SAPs on the PE routers.
The Epipe configuration then changes as follows. Only PE1 (R5) is shown as an example,
perform the same on remaining nodes.

*A:R5# configure service epipe 1

*A:R5# sap 1/1/5 ingress qos 10
*A:R5# config>service# info
… output omitted …
epipe 1 name "1" customer 1 create
sap 1/1/5:7 create
ingress
qos 10
exit
no shutdown
exit
spoke-sdp 6:1 create
no shutdown
exit
no shutdown
exit
… output omitted …
----------------------------------------------

To clear the statistics collected on the queues, students will issue the following command on
their respective PE router.

# clear service statistics sap 1/1/5:7 counters

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 13
Verification of SAP-Ingress QoS Policy
Verification of SAP-Ingress QoS Policy
To verify that the QoS policy has been properly created and applied, the following command can be
used on each PE:
Switch to notes view!
*A:R5# show service id 1 sap 1/1/5:7 stats
==============================================================================
Service Access Points(SAP)
==============================================================================
Service Id : 1
SAP : 1/1/5:7 Encap : null
Description : (Not Specified)
Admin State : Up Oper State : Up
... Output omitted ...
------------------------------------------------------------------------------
Sap per Queue stats
------------------------------------------------------------------------------
Packets Octets
Ingress Queue 1 (Unicast) (Priority)
Off. HiPrio : 0 0
Off. LowPrio : 0 0
Dro. HiPrio
14Nokia
© 2020 : 0 Nokia Confidential 0
Dro. LowPrio : 0 0
For. InProf : 0 0
For. OutProf : 0 0

Ingress Queue 3 (Unicast) (Priority)

Off. HiPrio : 0 0
Off. LowPrio : 0 0
Dro. HiPrio : 0 0
Dro. LowPrio : 0 0
For. InProf : 0 0
For. OutProf : 0 0

Ingress Queue 4 (Unicast) (Priority)

Off. HiPrio : 0 0
Off. LowPrio : 0 0
Dro. HiPrio : 0 0
Dro. LowPrio : 0 0
For. InProf : 0 0
For. OutProf : 0 0

Ingress Queue 5 (Unicast) (Priority)

Off. HiPrio : 0 0
Off. LowPrio : 0 0
Dro. HiPrio : 0 0
Dro. LowPrio : 0 0
For. InProf : 0 0
For. OutProf : 0 0

Ingress Queue 6 (Unicast) (Priority)

Off. HiPrio : 0 0
Off. LowPrio : 0 0
Dro. HiPrio : 0 0
Dro. LowPrio : 0 0
For. InProf : 0 0
For. OutProf : 0 0

Egress Queue 1
For. In/InplusProf : 0 0
For. Out/ExcProf : 0 0
Dro. In/InplusProf : 0 0
Dro. Out/ExcProf : 0 0

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 14
Verification of SAP-Ingress QoS Policy [cont.]
Verification of SAP-Ingress QoS Policy [cont.]

The previous output shows that the queues have been created, associated with the relevant SAP, and
thatSwitch to notes
no packets haveview!
been stored in them yet. Observe that the statistics include the number of
packets (and the corresponding octets) that are being offered, dropped and forwarded for each
existing queue. Notice also that there are separate counters for packets that have been forwarded as
in-profile and as out-of-profile.

15Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 15
 Creating and Applying Network-egress QoS Polices

Network Policies:
Network-Queue Policies:
• Applied at Ingress and Egress Interface
• Applied to egress ports and Ingress MDA’s (ingress FP for vSR)
• Ingress defines (dot1p dscp lsp-exp)
• Creates Q’s (unicast/multipoint)
to FC marking
• Assign queue type (expedite|best-effort|auto-expedite)
• Egress defines FC to (dot1p dscp
• Set Rate (CIR and PIR) CBS MBS
lsp-exp) marking in/out profile and Switch Assigns forwarding class to queue mapping
remarking Fabric

PE P PE
Service N/w N/w N/w N/w Service
Ingress Egress Egress Egress Egress Ingress

R5 R1 R6
Data flow

16Nokia 2020
© Nokia Confidential

In this lab, the students will learn how to configure Network-Queue and Network QoS policies
and how they are applied to a Network Egress point.
Network-Queue QoS policy
The queues and policers created in the SAP-Ingress policy, described in the previous lab, are
used to process packets on arrival from the customer site, as they wait before having a chance
to go through the router’s switch fabric to the egress port.
A Network-Queue policy, in contrast, when applied to a network port, creates queues that will
be used to process packets after they have crossed the switch fabric and right before they
leave the router towards the next router in the service provider network. The Network-Queue
QoS policy is also in charge of mapping forwarding classes to the queues it has created. Note
that, by the time a packet arrives at the egress network port, it has already been classified as
belonging to one of the forwarding classes, so there is no need to classify packets at this point.
As mentioned above, there are default policies for the network side of a router (the one
pointing to other service provider routers) that are in general enough for the packets to be
properly treated from end to end. Regarding the FCs that are relevant for this lab (EF, H2, AF
and L2), the default Network-Queue QoS policy creates the queues and does the FC-to-queue
mapping shown in the following screen capture.
According to this default policy, for instance, L2 packets are stored in queues 2 and 10,
depending on whether they are unicast or multipoint packets. These queues have 3% and 1%
respectively of the port buffer space reserved (CBS) and they can potentially use up to 50% of
the port buffer space, based on competition (MBS). The amount of bandwidth committed to
forward these packets is 25% and 5% respectively (CIR) but, if not used by other FCs of the
same priority level of higher, these packets can use the entire port capacity to be transmitted
(PIR = 100%).
The parameters corresponding to the other forwarding classes (AF, H2 and EF) can be
interpreted similarly.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 16
Displaying Default Network-egress QoS Policies
Displaying Default Network-egress QoS Policies
*A:R1>configure qos network-queue "default"
*A:R1>config>qos>network-queue#info
Switch to notes view! detail
----------------------------------------------
description "Default network queue QoS policy.
... Output omitted ...
queue 2 auto-expedite create
no port-parent
no avg-frame-overhead
rate 100 cir 25 fir 0
adaptation-rule pir closest cir closest fir closest
mbs 50
cbs 3
... Output omitted ...
queue 10 multipoint auto-expedite create
queue 10 multipoint auto-expedite create
no port-parent
no avg-frame-overhead
rate 100 cir 5 fir 0
adaptation-rule pir closest cir closest fir closest
17Nokia 2020
© mbs 50 Nokia Confidential
cbs 1
... Output omitted ...
fc l2 create
multicast-queue 10
queue 2
egress-hsmda
queue 2
exit
exit
... Output omitted ...
*A:R1>config>qos>network-queue# info detail | match cir
rate 100 cir 0 fir 0
adaptation-rule pir closest cir closest fir closest
rate 100 cir 25 fir 0
adaptation-rule pir closest cir closest fir closest
rate 100 cir 25 fir 0
adaptation-rule pir closest cir closest fir closest
rate 100 cir 25 fir 0
adaptation-rule pir closest cir closest fir closest
rate 100 cir 100 fir 0
... Output omitted ...
#-----------------------------------------------------------

Note that overbooking (sum of CIR values for the different queues exceeding 100%) is allowed.
The consequences of overbooking, depending on whether single-tier or hierarchical scheduling
is being used, will be explained in the scheduling section.
It is possible to create a new policy to do things differently, either to create new queues with
different parameters or to change the mapping between FCs and queues, consistent with the
specific service level agreement (SLA) that the provider has with the customer.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 17
Displaying Default Network-egress QoS Policies [cont.]
Displaying Default Network-egress QoS Policies [cont.]
*A:R1>configure qos network 1 egress
*A:R1>config>qos>network>egress#
Switch to notes view! info detail
----------------------------------------------
no remarking
fc af
dscp-in-profile af11
dscp-out-profile af12
lsp-exp-in-profile 3
lsp-exp-out-profile 2
dot1p-in-profile 2
dot1p-out-profile 2
no de-mark
no port-redirect-group
exit
... Output omitted ...
fc ef
dscp-in-profile ef
dscp-out-profile ef
lsp-exp-in-profile 5
18Nokia 2020
© lsp-exp-out-profile 5
Nokia Confidential
dot1p-in-profile 5
dot1p-out-profile 5
no de-mark
no port-redirect-group
... Output omitted ...
fc h2
dscp-in-profile af41
dscp-out-profile af42
lsp-exp-in-profile 4
lsp-exp-out-profile 4
dot1p-in-profile 4
dot1p-out-profile 4
no de-mark
no port-redirect-group
exit
... Output omitted ...
fc l2
dscp-in-profile cs1
dscp-out-profile cs1
lsp-exp-in-profile 1
lsp-exp-out-profile 1
dot1p-in-profile 1
dot1p-out-profile 1
no de-mark
no port-redirect-group
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 18
Configuration of Network-queue QoS Policies
Configuration of Network-queue QoS Policies
Students will create on their team’s routers a new Network-Queue policy by copying the default policy.
TheSwitch
name oftothe policy
notes will be “NQ1” and the FC-to-queue mapping will be modified as shown in the
view!
following screen capture. The commands that need to be issued on all routers are the following.
Note: Network-queue policies are applied to egress ports and ingress MDAs (ingress FP on simulators).
Network-queue policies Create queues (unicast or multipoint) assign queue-type (expedite|best-
effort|auto-expedite) set rate % (CIR PIR) Queue parameters (CBS MBS HPO) and assign FC to queue
mapping.

*A:R5>configure qos copy network-queue default NQ1

*A:R5>configure qos network-queue "NQ1"
*A:R5>…# description "Ping-EF-Q6 Video1-H2-Q5 Video2-AF-Q4 FTP-L2-Q3"
*A:R5>config>qos>network-queue# fc af queue 4
*A:R5>config>qos>network-queue# fc l2 queue 3
*A:R5>config>qos>network-queue# info detail | match "fc af" post-lines 100
----------------------------------------------
description "Ping-EF-Q6 Video1-H2-Q5 Video2-AF-Q4 FTP-L2-Q3"
... Output omitted ...
19Nokia 2020
© fc af create Nokia Confidential

multicast-queue 11
queue 3
egress-hsmda
queue 3
exit
exit
... Output omitted ...
fc ef create
multicast-queue 14
queue 6
egress-hsmda
queue 6
exit
exit
... Output omitted ...
fc h2 create
multicast-queue 13
queue 5
egress-hsmda
queue 5
exit
exit
... Output omitted ...
fc l2 create
multicast-queue 10
queue 3
egress-hsmda
queue 2
exit
exit
fc nc create
multicast-queue 16
queue 8
egress-hsmda
queue 8
exit
exit
----------------------------------------------

Note: The default forwarding class value for Queues 5 and 6 do not require changing.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 19
Configuration of Network-queue QoS Policies [cont.]
Configuration of Network-queue QoS Policies [cont.]
Once the Network-Queue QoS policy has been created, it must be applied to all of the epipe’s network
ports and ingress
Switch MDAs
to notes view!(ingress FP on simulators) for consistent treatment of packets throughout the
entire service provider network. An example of the commands (R5) that need to be issued on all
routers network ports to apply the Network-Queue QoS policy are shown below.
*A:R5# configure port 1/1/4 ethernet network queue-policy "NQ1
To verify that the policy has been properly configured and applied, the students can use for instance
the following command, which displays the network-egress queues with their parameters (CBS, MBS,
CIR, PIR and HPO) and the FC mappings, corresponding to the port that connects P2 to P3.

*A:R5# show pools 1/1/4 network-egress

==============================================================================
Pool Information
==============================================================================
Port : 1/1/4
Application : Net-Egr Pool Name : default
CLI Config. Resv CBS : Sum
...©20Nokia
Output2020
omitted ... Nokia Confidential

==============================================================================
Queue : 3 Net=l2 Port=1/1/4
==============================================================================
FC Map : l2 af
... Output omitted ...
==============================================================================
Queue : 5 Net=h2 Port=1/1/4
==============================================================================
FC Map : h2
... Output omitted ...
==============================================================================
Queue : 6 Net=ef Port=1/1/4
==============================================================================
FC Map : ef
Admin PIR : 1000000 Oper PIR : Max
Admin CIR : 1000000 Oper CIR : Max
Admin MBS : 40320 KB Oper MBS : 40320 KB
High-Plus Drop T*: 40320 KB High Drop Tail : 40320 KB
Low Drop Tail : 35520 KB Exceed Drop Tail : 36480 KB
CBS : 4800 KB Depth : 0
==============================================================================
Queue : 7 Net=h1 Port=1/1/4
==============================================================================
... Output omitted ...
==============================================================================
Queue : 8 Net=nc Port=1/1/4
==============================================================================
... Output omitted ...
==============================================================================

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 20
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y).

Initial rollback config file’s comment - Sap-Ingress-QoS-policy

• /admin rollback revert X

Final rollback config file’s comment - Network-QoS-policies

To compare current config with the final lab answer:

• /admin rollback compare active-cfg to Y

21Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 21
Network QoS Policy
Network QoS Policy
After a packet has been waiting in one of the network-egress queues, as described in the
previous
Switchlab, it will be
to notes transmitted towards the next service provider router. The last
view!
processing that takes place before the packet leaves the router is that it can be marked (or
re-marked). That is, based on the packet’s forwarding class and profile, one or more fields in its
headers can be set (or changed) to specific values to give the next router enough information
to properly classify the packet on ingress. That is the role of the egress portion of a Network
QoS policy when it is applied to a network IP interface.
The default Network QoS policy does the following marking/re-marking on egress, regarding
the FCs that we are interested in (EF, H2, AF, and L2). If the packet entered the router via a
network interface, it will not be re-marked. If the packet entered the router via a SAP, however,
the IP DSCP field, the MPLS EXP bits, and the Priority bits in the IEEE 802.1p header (the same
one used for VLAN tags) will be set to values consistent with the packet’s FC and profile.

*A:R1>config>qos# info detail | match "network 1" post-lines 200

#--------------------------------------------------
22Nokia 2020
© Nokia Confidential
echo "QoS Policy Configuration"
#--------------------------------------------------
... Output omitted ...
network 1 create
description "Default network QoS policy."
scope template
ingress
default-action fc be profile out
... Output omitted ...
egress
no remarking
fc af
dscp-in-profile af11
dscp-out-profile af12
lsp-exp-in-profile 3
lsp-exp-out-profile 2
dot1p-in-profile 2
... Output omitted ...
fc ef
dscp-in-profile ef
dscp-out-profile ef
lsp-exp-in-profile 5
lsp-exp-out-profile 5
dot1p-in-profile 5
exit
... Output omitted ...
fc h2
dscp-in-profile af41
dscp-out-profile af42
lsp-exp-in-profile 4
lsp-exp-out-profile 4
dot1p-in-profile 4
dot1p-out-profile 4

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 22
Network QoS Policy [cont.]
Network QoS Policy [cont.]
As you can see, it is possible to mark packets using the DSCP field within the IP header, the
EXPSwitch
field within theview!
to notes MPLS header, or using the Dot1p field within the Ethernet header with
VLAN tags. For this lab, students will create a new Network QoS policy to do custom
marking/re-marking using only the EXP field.

Students will create on their group’s routers a new Network QoS policy by copying the default
policy (policy Id equal to 1). The new policy will have a policy Id of 10 and the marking will be
modified as shown in the following:

*A:R1# configure qos copy network 1 10

*A:R1# configure qos network 10
*A:R1>config>qos>network# description "Ping-EF-Q6; VLC1-H2-Q5; VLC2-AF-Q4;
FTP-L2-Q3"
*A:R1>config>qos>network# egress fc ef lsp-exp-in-profile 6
*A:R1>config>qos>network# egress fc ef lsp-exp-out-profile 6
*A:R1>config>qos>network# egress fc h2 lsp-exp-in-profile 5
*A:R1>config>qos>network#
23Nokia 2020
© egress fc Nokia
h2 Confidential
lsp-exp-out-profile 5
*A:R1>config>qos>network# egress fc af lsp-exp-in-profile 4
*A:R1>config>qos>network# egress fc af lsp-exp-out-profile 4
*A:R1>config>qos>network# egress fc l2 lsp-exp-in-profile 3
*A:R1>config>qos>network# egress fc l2 lsp-exp-out-profile 3
*A:R1>config>qos>network# info
----------------------------------------------
description "Ping-EF-Q6; VLC1-H2-Q5; VLC2-AF-Q4; FTP-L2-Q3"
... Output omitted ...
egress
fc af
lsp-exp-in-profile 4
lsp-exp-out-profile 4
exit
fc ef
lsp-exp-in-profile 6
lsp-exp-out-profile 6
exit
fc h2
lsp-exp-in-profile 5
lsp-exp-out-profile 5
exit
fc l2
lsp-exp-in-profile 3
lsp-exp-out-profile 3
exit
exit
----------------------------------------------

Once the Network QoS policy has been created on all routers, it needs to be applied to all of
the network IP interfaces for consistent treatment of packets throughout the entire service
provider network. The command that needs to be issued on all routers to apply the Network
QoS policy is shown below:

*A:R5# configure router interface "toR1" qos 10

*A:R1# configure router interface "toR5" qos 10

*A:R1# configure router interface "toR6" qos 10

*A:R6# configure router interface "toR1" qos 10

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 23
 Creating and Applying Network-egress QoS Polices

Network Policies:
Network-Queue Policies:
• Applied at Ingress and Egress Interface
• Applied to egress ports and Ingress MDA’s (ingress FP for vSR)
• Ingress defines (dot1p dscp lsp-exp)
• Creates Q’s (unicast/multipoint)
to FC marking
• Assign queue type (expedite|best-effort|auto-expedite)
• Egress defines FC to (dot1p dscp
• Set Rate (CIR and PIR) CBS MBS
lsp-exp) marking in/out profile and Switch Assigns forwarding class to queue mapping
remarking Fabric

PE P PE
Service N/w N/w N/w N/w Service
Ingress Egress Egress Egress Egress Ingress

R5 R1 R6
Data flow

24Nokia 2020
© Nokia Confidential

We have mentioned before that a packet can arrive at a router either via a SAP or via a network
interface. If it arrives via a SAP, we already configured a SAP-ingress policy to process the
packet. In this section we will create a policy that will classify packets as they enter a router via a
network interface.
In the previous lab we analyzed how to configure the egress part of a Network QoS policy
(marking/re-marking). In this lab we will learn how to configure the ingress part of a Network
QoS policy (classification).
The default Network QoS policy does the following classification on ingress, regarding the EXP
bits in the MPLS header, which is what we will use to mark our packets, as explained in the
previous section.

*A:R1>config>qos# info detail

... Output omitted ...
network 1 create
description "Default network QoS policy."
ingress
lsp-exp 0 fc be profile out
lsp-exp 1 fc l2 profile in
lsp-exp 2 fc af profile out
lsp-exp 3 fc af profile in
lsp-exp 4 fc h2 profile in
lsp-exp 5 fc ef profile in
lsp-exp 6 fc h1 profile in
lsp-exp 7 fc nc profile in

It can be seen that these classification rules associate packets to an FC and profile that are
consistent with those that the packet would have before leaving the previous router if the
default QoS policy were used. Since we modified the marking of packets on egress, we need to
modify the way packets will be classified on ingress when they carry the markings we selected
for them.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 24
Network QoS Policy [cont.]
Network QoS Policy [cont.]
*A:R1# configure qos copy network 1 10
*A:R1#
Switch configure qos network 10
to notes view!
*A:R1>config>qos>network# description "Ping-EF-Q6; VLC1-H2-Q5; VLC2-AF-Q4;
FTP-L2-Q3"
*A:R1>config>qos>network# ingress lsp-exp 6 fc ef profile in
*A:R1>config>qos>network# ingress lsp-exp 5 fc h2 profile in
*A:R1>config>qos>network# ingress lsp-exp 4 fc af profile in
*A:R1>config>qos>network# ingress lsp-exp 3 fc l2 profile in
*A:R1>config>qos>network# info
----------------------------------------------
description "Ping-EF-Q6; VLC1-H2-Q5; VLC2-AF-Q4; FTP-L2-Q3"
... Output omitted ...
ingress
... Output omitted ...
dscp af43 fc h2 profile out
lsp-exp 0 fc be profile out
lsp-exp 1 fc l2 profile in
lsp-exp 2 fc af profile out
lsp-exp 3 fc l2 profile in
25Nokia 2020
© lsp-exp 4 fc af profile in
Nokia Confidential
lsp-exp 5 fc h2 profile in
lsp-exp 6 fc ef profile in
lsp-exp 7 fc nc profile in
----------------------------------------------

Once the Network QoS policy has been created on all routers, it needs to be applied to all of
the network IP interfaces for consistent treatment of packets throughout the entire service
provider network. An example of the command that needs to be issued on all routers to apply
the Network QoS policy is shown below:

As far as applying these rules, they become active when the Network QoS policy is applied to
the network interfaces. That was done in the previous exercise when we issued the following
commands on all routers. Both the egress and ingress rules become active at the same time.

*A:R5# configure router interface "toR1" qos 10

*A:R1# configure router interface "toR5" qos 10

*A:R1# configure router interface "toR6" qos 10

*A:R6# configure router interface "toR1" qos 10

Note: The common practice is to configure both Egress and Ingress rules in the Network QoS
policy first, and then to apply the policy to the network interfaces. In this exercise, Egress and
Ingress rules were configured separately to emphasize that they take effect at different
packet-processing stages and on different network points.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 25
Network QoS Policy [cont.]
Network QoS Policy [cont.]
When a packet enters a router via a network interface, after it has been classified it needs to
be processed by a queue
Switch to notes view! or a policer and wait for an opportunity to go through the switch
fabric towards the corresponding egress port. Different queues and/or policers need to be
created and the different FCs need to be mapped to the queues. That is the role of a
Network-Queue QoS policy when it is applied to an MDA or FP in vSIM. The queues created by
the policy and the corresponding FC-queue mapping apply to all of the network ports that
belong to the relevant MDA.
Again, the SR OS provides enough flexibility to configure a Network-Queue QoS policy to be
applied on egress and a different one to be applied on ingress. However, to create a
homogeneous packet processing environment, we will use on ingress (applied to MDAs or FP’s)
the same policy we used on egress before (applied to network ports). Namely, the Network-
Queue policy called “NQ1” created in a previous lab.

Therefore, since in our lab setup all network ports correspond to MDA 1/1, the command that
needs to be issued on all routers to apply the ingress Network-Queue QoS policy is the
26Nokia 2020
© Nokia Confidential
following.

RX# configure card 1 mda 1 network ingress queue-policy "NQ1“

For vSIM use

RX# configure card 1 fp 1 ingress network queue-policy "NQ1"

Note: Since the same Network-Queue QoS policy is applied on ingress and egress, similar
queues and FC-queue mappings apply on both directions. However, one set of queues is
created to store packets on ingress and a separate set of queues is created to store packets
on egress.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 26
Network QoS Policy [cont.]
Network QoS Policy [cont.]
*A:R5# show pools 1 fp 1 network-ingress
==============================================================================
Switch to notes view!
Pool Information
==============================================================================
Port : 1/1/4
Application : Net-Egr Pool Name : default
CLI Config. Resv CBS : Sum
Resv CBS Step : 0% Resv CBS Max : 0%
Amber Alarm Threshold: 0% Red Alarm Threshold : 0%
... Output omitted ...
==============================================================================
Queue : 3 Net=l2 Port=1/1/4
==============================================================================
FC Map : l2
... Output omitted ...
==============================================================================
Queue : 4 Net=af Port=1/1/4
==============================================================================
FC Map : af l1
...©27Nokia
Output2020 omitted ... Nokia Confidential
==============================================================================
Queue : 5 Net=h2 Port=1/1/4
==============================================================================
FC Map : h2
Dest Tap : not-applicable Dest FP : not-applicable
Admin PIR : 10000000 Oper PIR : Max
Admin CIR : 10000000 Oper CIR : Max
Admin MBS : 80640 KB Oper MBS : 80640 KB
High-Plus Drop T*: 80640 KB High Drop Tail : 80640 KB
Low Drop Tail : 71040 KB Exceed Drop Tail : 72960 KB
CBS : 15840 KB Depth : 0
Slope : not-applicable
==============================================================================
Queue : 6 Net=ef Port=1/1/4
==============================================================================
... Output omitted ...

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 27
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y).

Initial rollback config file’s comment - Network-QoS-policies

• /admin rollback revert X

Final rollback config file’s comment - SAP-Egress-QoS-policy

To compare current config with the final lab answer:

• /admin rollback compare active-cfg to Y

28Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 28
 Creating and Applying a SAP-egress QoS Policy

Switch
Fabric Service Egress QoS policy “SAP-Egress”
Defines queue parameters
Maps FC to egress Q’s

PE P PE
Service N/w N/w N/w N/w Service
Ingress Egress Egress Egress Egress Ingress

R5 R1 R6
Data flow

29Nokia 2020
© Nokia Confidential

In this lab, the students will learn how to configure the different components of a SAP-Egress
QoS policy. A SAP-Egress QoS policy establishes the following packet-processing criteria:
• It can create traffic queues, defining:
- Type (expedited, best-effort, auto-expedited)
- Mode (priority, profile)
- Allocated buffer size (committed and maximum)
- Rate (committed and maximum) at which stored packets will exit the queue
• Alternatively or additionally, it can create traffic policers, defining:
- Rate (committed and maximum) at which packets will be forwarded
• Assigns forwarding classes to queues
• Packet re-marking, if needed.
Note that, by the time a packet arrives at the egress SAP, it has already been classified as
belonging to one of the forwarding classes, so (although possible) there is no need to classify
packets at this point.
Each team will create on their respective P router a SAP-Egress QoS policy with a policy Id equal
to 10. By default, the policy includes queue 1, whose parameters are chosen to store BE
packets. Note that there is no need to create multipoint queues in a SAP-Egress QoS policy,
since all packets affected by it will exit the router through the same SAP.

For this lab, each group will create four additional queues within the same SAP-Egress QoS
policy, each one to store packets from a different traffic flow. The parameters associated with
these queues will be the same as the ones discussed before for the SAP-Ingress QoS policy.
After creating these queues, each FC will be mapped to its corresponding queue.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 29
Creating a SAP-egress QoS Policy
Creating a SAP-egress QoS Policy
The commands needed to create this SAP-Egress QoS policy are shown below:
Switch to notes view!
*A:R6# configure qos sap-egress 10 create
*A:R6…$ description "Ping EF Q6 Video1 H2 Q5 Video2 AF Q4 & FTP L2 Q3"
*A:R6>config>qos>sap-egress$ queue 6 create
*A:R6>config>qos>sap-egress>queue$ rate 150 cir 150
*A:R6>config>qos>sap-egress>queue$ back
*A:R6>config>qos>sap-egress$ queue 5 create
*A:R6>config>qos>sap-egress>queue$ rate 2500 cir 500
*A:R6>config>qos>sap-egress>queue$ burst-limit 120000 bytes
*A:R6>config>qos>sap-egress>queue$ back
*A:R6>config>qos>sap-egress$ queue 4 create
*A:R6>config>qos>sap-egress>queue$ rate 2500 cir 500
*A:R6>config>qos>sap-egress>queue$ burst-limit 120000 bytes
*A:R6>config>qos>sap-egress>queue$ back
*A:R6>config>qos>sap-egress$ queue 3 create
*A:R6>config>qos>sap-egress>queue$ rate 7000 cir 2000
*A:R6>config>qos>sap-egress>queue$ back
*A:R6>config>qos>sap-egress#
30Nokia 2020
©
fc af create queue 4
Nokia Confidential
*A:R6>config>qos>sap-egress# fc ef create queue 6
*A:R6>config>qos>sap-egress# fc h2 create queue 5
*A:R6>config>qos>sap-egress# fc l2 create queue 3
*A:R6>config>qos>sap-egress# exit all

The commands needed to create this SAP-Egress QoS policy are shown below:

*A:R6# configure qos sap-egress 10 create

*A:R6>config>qos>sap-egress$ info
----------------------------------------------
queue 1 create
exit
queue 3 create
rate 7000 cir 2000
exit
queue 4 create
rate 2500 cir 500
burst-limit 120000 bytes
exit
queue 5 create
rate 2500 cir 500
exit
queue 6 create
rate 150 cir 150
exit
fc af create
queue 4
exit
fc ef create
queue 6
exit
fc h2 create
queue 5
exit
fc l2 create
queue 3
exit
----------------------------------------------

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 30
Creating a SAP-egress QoS Policy [cont.]
Creating a SAP-egress QoS Policy [cont.]
Once the SAP-Egress policy is complete, it can be applied to the Epipe SAP. The Epipe
configuration then view!
Switch to notes changes as follows. Only R1 is shown as an example:

*A:R6# configure service epipe 1 sap 1/1/5:7 egress qos 10

*A:R6# configure service epipe 1
*A:R6>config>service>epipe# info
----------------------------------------------
sap 1/1/5:7 create
ingress
qos 10
exit
no shutdown
exit
spoke-sdp 5:1 create
no shutdown
exit
no shutdown
31Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 31
 Verify QoS Classification and Marking Policies

configure router interface "toRX" configure router interface "toRX“

info info
configure qos network 10 configure qos network 10 ingress
info info
configure port 1/1/X ethernet network configure card 1 fp 1 ingress network
info info
configure qos network-queue NQ1 configure qos network-queue NQ1
info info

configure qos configure qos

• sap-ingress=10 • sap-egress=10

configure service configure service

• Epipe=1 • Epipe 1
• sap 1/1/5:7 • sap 1/1/5:7
• ingress qos 10 • egress qos 10
PE P PE
Service N/w N/w N/w N/w Service
Ingress Egress Egress Egress Egress Ingress

R5 R1 R6
Data flow

32Nokia 2020
© Nokia Confidential

QoS Planning

Source Forwarding Class Queue Exp Clasification

Ping EF 6 6 ICMP

Video1 H25 5 5 UDP pt 1234

Video2 AF 4 4 UDP pt 5678

SFTP L2 3 3 TCP

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 32
Verify QoS Classification and Marking Policies [cont.]
Verify QoS Classification and Marking Policies [cont.]
Use the following commands to verify the sap-ingress policy has been applied on the PE
e-pipe service.
Switch to notes view!

*A:R5# configure service epipe 1 sap 1/1/5:7 ingress

*A:R5>config>service>epipe>sap>ingress# info
----------------------------------------------
qos 10
----------------------------------------------
*A:R5# configure qos sap-ingress 10
*A:R5>config>qos>sap-ingress# info
----------------------------------------------
description "Ping EF Q6 Video1 H2 Q5 Video2 AF Q4 & FTP L2 Q3"
queue 1 create
exit
queue 3 create
rate 7000 cir 2000
exit
queue 4 create
33Nokia 2020
© rate 2500 cir 500 Nokia Confidential

burst-limit 120000 bytes

... Output omitted ...
ip-criteria
entry 10 create
description "Ping"
match protocol icmp
exit
action fc "ef"
exit
entry 20 create
description "Video1"
match protocol udp
dst-port eq 1234
exit
action fc "h2"
exit
entry 30 create
description " Video2"
match protocol udp
dst-port eq 5678
exit
action fc "af"
exit
entry 40 create
description "FTP"
match protocol tcp
exit
action fc "l2"
exit
exit

This output shows that the sap-ingress policy has been created, associated with the relevant
SAP.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 33
Verify QoS Classification and Marking Policies [cont.]
Verify QoS Classification and Marking Policies [cont.]
Use the following commands to verify the network and network-queue policy have been
applied onto
Switch the ingress
notes view!PE router. (R5, R6, R7, R8)

*A:R5# configure router interface toR1

*A:R5>config>router>if# info
----------------------------------------------
address 10.1.5.5/28
port 1/1/4
ipv6
address 2001:db8:15::1:5:5/64
exit
qos 10
no shutdown
----------------------------------------------

*A:R5# configure qos network 10 egress

*A:R5> config>qos>network>egress# info
----------------------------------------------
34Nokia 2020
© fc af Nokia Confidential

lsp-exp-in-profile 4
lsp-exp-out-profile 4
exit
fc ef
lsp-exp-in-profile 6
lsp-exp-out-profile 6
exit
fc h2
lsp-exp-in-profile 5
lsp-exp-out-profile 5
exit
fc l2
lsp-exp-in-profile 3
lsp-exp-out-profile 3
exit
----------------------------------------------
*A:R5# configure port 1/1/4 ethernet network
*A:R5>config>port>ethernet>network# info
----------------------------------------------
queue-policy "NQ1"
----------------------------------------------
*A:R5# configure qos network-queue "NQ1"
*A:R5>config>qos>network-queue# info
----------------------------------------------
description " Ping-EF-Q6; Video1-H2-Q5; Video2-AF-Q4; FTP-L2-Q3"
... Output omitted ...

This output shows that the network and network-queue policy has been applied to the port
and interface of the PE router.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 34
Verify QoS Classification and Marking Policies [cont.]
Verify QoS Classification and Marking Policies [cont.]
Use the following commands to verify the network and network-queue policy have been
applied onto
Switch the ingress
notes view!P router.

*A:R1# configure router interface "toR5"

*A:R1>config>router>if# info
----------------------------------------------
address 10.1.5.1/28
port 1/1/5
ipv6
address 2001:db8:15::1:5:1/64
exit
qos 10
no shutdown
----------------------------------------------
*A:R1# configure qos network 10 ingress
*A:R1>config>qos>network>ingress# info
----------------------------------------------
description "Ping-EF-Q6; Video1-H2-Q5; Video2-AF-Q4; FTP-L2-Q3"
35Nokia 2020
© ingress Nokia Confidential

dscp be fc be profile out

dscp ef fc ef profile in
dscp cs1 fc l2 profile in
... Output omitted ...
*A:R1# configure card 1 fp 1 ingress network
*A:R1>config>card>fp>ingress>network# info
----------------------------------------------
queue-policy "NQ1"
----------------------------------------------

*A:R1>configure qos network-queue NQ1

*A:R1>config>qos>network-queue# info
----------------------------------------------
description " Ping-EF-Q6; Video1-H2-Q5; Video2-AF-Q4; FTP-L2-Q3"
queue 1 create
... Output omitted ...

This output shows that the network and network-queue policy has been applied to the port
and interface of the ingress P router.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 35
Verify QoS Classification and Marking Policies [cont.]
Verify QoS Classification and Marking Policies [cont.]
Use the following commands to verify the network and network-queue policy have been
applied onto
Switch the ingress
notes view!P router.

*A:R1# configure router interface "toR6"

*A:R1>config>router>if# info
----------------------------------------------
address 10.1.6.1/28
port 1/1/7
ipv6
address 2001:db8:16::1:6:1/64
exit
qos 10
no shutdown
----------------------------------------------
*A:R1# configure qos network 10 egress
*A:R1>config>qos>network>ingress# info
----------------------------------------------
fc af
36Nokia 2020
© lsp-exp-in-profile 4
Nokia Confidential

lsp-exp-out-profile 4
exit
fc ef
lsp-exp-in-profile 6
lsp-exp-out-profile 6
exit
fc h2
lsp-exp-in-profile 5
lsp-exp-out-profile 5
exit
fc l2
lsp-exp-in-profile 3
lsp-exp-out-profile 3
exit

*A:R1# configure port 1/1/7 ethernet network

*A:R1>config>port>ethernet>network# info
----------------------------------------------
queue-policy NQ1
----------------------------------------------
*A:R1>config>qos>network-queue# info
----------------------------------------------
description " Ping-EF-Q6; Video1-H2-Q5; Video2-AF-Q4; FTP-L2-Q3"
queue 1 create
... Output omitted ...

This output shows that the network and network-queue policy has been applied to the egress
interface and port of the egress P router.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 36
Verify QoS Classification and Marking Policies [cont.]
Verify QoS Classification and Marking Policies [cont.]
Use the following commands to verify the network and network-queue policy have been
applied onto
Switch the egress
notes PE router.
view!

*A:R6# configure router interface toR1

*A:R6>config>router>if# info
----------------------------------------------
address 10.1.6.6/28
port 1/1/6
ipv6
address 2001:db8:16::1:6:6/64
exit
qos 10
no shutdown
----------------------------------------------

*A:R6# configure qos network 10 ingress

*A:R6> config>qos>network>ingress# info
----------------------------------------------
...©37Nokia
Output2020 omitted ... Nokia Confidential

lsp-exp 2 fc af profile out

lsp-exp 3 fc l2 profile in
lsp-exp 4 fc af profile in
lsp-exp 5 fc h2 profile in
lsp-exp 6 fc ef profile in
lsp-exp 7 fc nc profile in
----------------------------------------------
*A:R6# configure port 1/1/6 ethernet network
*A:R6>config>port>ethernet>network# info
----------------------------------------------
queue-policy "NQ1"
----------------------------------------------
*A:R6# configure qos network-queue "NQ1"
*A:R6>config>qos>network-queue# info
----------------------------------------------
description " Ping-EF-Q6; Video1-H2-Q5; Video2-AF-Q4; FTP-L2-Q3"
... Output omitted ...

This output shows that the network and network-queue policy has been applied to the
interface and port of the egress PE router.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 37
Verify QoS Classification and Marking Policies [cont.]
Verify QoS Classification and Marking Policies [cont.]
Use the following commands to verify the sap-egress policy has been applied on the e-pipe
service.
Switch to notes view!

*A:R6# configure service epipe 1 sap 1/1/5:7 egress

*A:R6>config>service>epipe>sap>ingress# info
----------------------------------------------
qos 10
----------------------------------------------
*A:R6# configure qos sap-egress 10
*A:R6>config>qos>sap-ingress# info
----------------------------------------------
description "Ping EF Q6 Video1 H2 Q5 Video2 AF Q4 & FTP L2 Q3"
queue 1 create
exit
queue 3 create
rate 7000 cir 2000
exit
queue 4 create
38Nokia 2020
© rate 2500 cir 500 Nokia Confidential

burst-limit 120000 bytes

... Output omitted ...
queue 6 create
rate 150 cir 150
exit
fc af create
queue 4
exit
fc ef create
queue 6
exit
fc h2 create
queue 5
exit
fc l2 create
queue 3
exit

This output shows that the sap-egress policy has been created, associated with the relevant
egress SAP.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 38
Verification of Traffic Classification, Queuing, and Marking
Verification of Traffic Classification, Queuing, and Marking
In this lab, students will start generating traffic corresponding to each different stream (Ping,
SFTP IPERF-1
Switch and IPERF-2),
to notes view! one at a time.
Please Note: The instructor may need to change the vPC9 and vPC11 address to match the
diagram below.
Each pair of students configure their PCs (PC9 to PC12) with virtual interfaces as follows:

#PC9
ip link add link eth1 name eth1.7 type vlan proto 802.1Q id 7
ip addr add 192.168.5.9/24 dev eth1.7 #sap 1/1/5:7
ip link set eth1.7 up

#PC10
ip link add link eth1 name eth1.7 type vlan proto 802.1Q id 7
ip addr add 192.168.5.10/24 dev eth1.7 #sap 1/1/5:7
ip link set eth1.7 up

#PC11
39Nokia 2020
© Nokia Confidential

ip link add link eth1 name eth1.7 type vlan proto 802.1Q id 7
ip addr add 192.168.5.11/24 dev eth1.7 #sap 1/1/5:7
ip link set eth1.7 up

#PC12
ip link add link eth1 name eth1.7 type vlan proto 802.1Q id 7
ip addr add 192.168.5.12/24 dev eth1.7 #sap 1/1/5:7
ip link set eth1.7 up

[root@pc9 ~]# ping 192.168.5.10

PING 192.168.5.10 (192.168.5.10) 56(84) bytes of data.
64 bytes from 192.168.5.10: icmp_seq=1 ttl=64 time=4.00 ms
64 bytes from 192.168.5.10: icmp_seq=2 ttl=64 time=3.36 ms

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 39
Verification of Traffic Classification, Queuing, and Marking [cont.]
Verification of Traffic Classification, Queuing, and Marking [cont.]
Students will issue the following command on their respective routers in order to clear the
statistics
Switchcollected on the SAP statistics.
to notes view!

*A:R5# clear service statistics sap 1/1/5:7 counters

After a few seconds, students will display the SAP statistics using the following command.

*A:R5# show service id 1 sap 1/1/5:7 stats

Analyze the statistics corresponding to the ingress queues, which include the number of
packets (and the corresponding octets) that are being offered, forwarded and dropped for
each existing queue. Verify that traffic is properly classified and queued by making sure that
the counters for the queue that is expected to receive the traffic being generated are
increasing. The example below shows a situation where only Ping traffic is being generated so
far, which is expected to be stored in queue 6.
40Nokia 2020
© Nokia Confidential

*A:R5# clear service statistics sap 1/1/5:7 all

*A:R5# show service id 1 sap 1/1/5:7 stats | match "Ingress Queue 6" post-
lines 5

Ingress Queue 6 (Unicast) (Priority)

Off. HiPrio : 0 0
Off. LowPrio : 16 1632
Dro. HiPrio : 0 0
Dro. LowPrio : 0 0
For. InProf : 0 0
For. OutProf : 20 2040

*A:R5# clear port 1/1/4 statistics

*A:R5# show port 1/1/4 detail
Egress Queue 6 Packets Octets
In/Inplus Prof fwded : 0 0
In/Inplus Prof dropped: 0 0
Out/Exc Prof fwded : 4 496
Out/Exc Prof dropped : 0 0
Egress Queue 7 Packets Octets

*A:R1# clear port 1/1/5 statistics

*A:R1# show port 1/1/5 detail | match "Ingress Queue 6" post-lines 4

Ingress Queue 6 Packets Octets

In Profile forwarded : 14 1736
In Profile dropped : 0 0
Out Profile forwarded : 0 0
Out Profile dropped : 0 0
Ingress Queue 7 Packets Octets

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 40
Verification of Traffic Classification, Queuing, and Marking [cont.]
Verification of Traffic Classification, Queuing, and Marking [cont.]
*A:R1# clear port 1/1/7 statistics
*A:R1# show
Switch portview!
to notes 1/1/7 detail | match "Egress Queue 6" post-lines 4

Egress Queue 6 Packets Octets

In/Inplus Prof fwded : 3 372
In/Inplus Prof dropped: 0 0
Out/Exc Prof fwded : 0 0
Out/Exc Prof dropped : 0 0

*A:R6# clear port 1/1/6 statistics

*A:R6# show port 1/1/6 detail | match "Ingress Queue 6" post-lines 4

Ingress Queue 6 Packets Octets

In Profile forwarded : 2 248
In Profile dropped : 0 0
Out Profile forwarded : 0 0
Out Profile dropped : 0 0
Ingress Queue 7 Packets Octets

*A:R6# clear service statistics sap Nokia

41Nokia 2020
© 1/1/5:7
Confidential all
*A:R6# show service id 1 sap 1/1/5:7 stats | match "Egress Queue 6" post-lines
5
Egress Queue 6
For. In/InplusProf : 2 204
For. Out/ExcProf : 0 0
Dro. In/InplusProf : 0 0
Dro. Out/ExcProf : 0 0

==============================================================================
Stop the ping using <CTL>-C
…
64 bytes from 192.168.5.10: icmp_seq=2 ttl=64 time=3.33 ms
^C
--- 192.168.5.10 ping statistics ---

Start the Iperf traffic simulating Video1 and using the same commands analyze the statistics
corresponding to the Video1 traffic.

[root@pc9 ~]# iperf -u -c 192.168.5.10 -b 1M -t 3000 -i 1 -l 1470 -p 1234

------------------------------------------------------------
Client connecting to 192.168.5.10, UDP port 1234
Sending 1470 byte datagrams, IPG target: 11215.21 us (kalman adjust)
UDP buffer size: 208 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.5.9 port 52804 connected with 192.168.5.10 port 1234
[ ID] Interval Transfer Bandwidth
[ 3] 0.0- 1.0 sec 131 KBytes 1.07 Mbits/sec
[ 3] 1.0- 2.0 sec 128 KBytes 1.05 Mbits/sec

[root@PC10 ~]# iperf -s -u -p 1234

------------------------------------------------------------
Server listening on UDP port 1234
Receiving 1470 byte datagrams
UDP buffer size: 208 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.5.10 port 1234 connected with 192.168.5.9 port 33111

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 41
Verification of Traffic Classification, Queuing, and Marking [cont.]
Verification of Traffic Classification, Queuing, and Marking [cont.]
Start the Iperf traffic simulating Video2 and using the same commands analyze the statistics
corresponding to the
Switch to notes Video2 traffic.
view!

[root@pc9 ~]# iperf -u -c 192.168.5.10 -b 1M -t 3000 -i 1 -l 1470 -p 5678

------------------------------------------------------------
Client connecting to 192.168.5.10, UDP port 5678
Sending 1470 byte datagrams, IPG target: 11215.21 us (kalman adjust)
UDP buffer size: 208 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.5.9 port 60432 connected with 192.168.5.10 port 5678
[ ID] Interval Transfer Bandwidth
[ 3] 0.0- 1.0 sec 131 KBytes 1.07 Mbits/sec
[ 3] 1.0- 2.0 sec 128 KBytes 1.05 Mbits/sec

[root@PC10 ~]# iperf -s -u -p 5678

------------------------------------------------------------
Server listening on UDP port 5678
42Nokia 2020
© Nokia Confidential
Receiving 1470 byte datagrams
UDP buffer size: 208 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.5.10 port 5678 connected with 192.168.5.9 port 60432

Start the SFTP traffic and using the same commands analyze the statistics corresponding to
the SFTP traffic.
Note: The instructor may need to create a file to sFTP between the vPCs, an example is
provided for vPC9 below.

Create a Big File to DFTP from vPC10

[root@pc9 ~]# cd /root
[root@pc9 ~]# dd if=/dev/zero of=BigFile count=10240 bs=10240
10240+0 records in
10240+0 records out
104857600 bytes (105 MB) copied, 0.983877 s, 107 MB/s

[root@PC10 ~]# sftp 192.168.5.9

########################################################################
# Notice: The use of this system is restricted to users who have been #
# authorized by Nokia. Except where prohibited by law, Nokia may #
# monitor, record and audit all system activities. Any unauthorized #
# use of this system, or use in violation of Nokia's policies and #
# applicable law, could result in Company disciplinary actions and/or #
# criminal and civil penalties. #
########################################################################
root@192.168.5.9's password: root
Connected to 192.168.5.9.
sftp> get BigFile
Fetching /root/BigFile to BigFile
/root/BigFile 12% 12MB 351.6KB/s 04:15
ETA

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 42
 Lab- Policing vs Queuing

43Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 43
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y).

Initial rollback config file’s comment - SAP-Egress-QoS-policy

• /admin rollback revert X

Final rollback config file’s comment - SAP-Ingress-QoS-Policer

To compare current config with the final lab answer:

• /admin rollback compare active-cfg to Y

44Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 44
 Lab Design

• Objective:
- Configure hierarchical BW allocation using H-QoS scheduling.
192.168.5.9/24 192.168.5.10/24
PC9 R5 R1 R6 4 PC10
1/1/5:7 1/1/5 1/1/6 eth1
eth1 1/1/4 1/1/7 1/1/5:7
CE PE P PE CE2

• Exercise:
- Change the SAP-ingress policy to specify the parent scheduler for each queue & the parameters with which it will
compete for bandwidth
- Verify that the scheduler policy has been properly configured and applied.
192.168.5.11/24 192.168.5.12/24

PC11 R7 R3 R8 PC12
1/1/5:7 1/1/5 1/1/6 eth1
eth1 1/1/4 1/1/7 1/1/5:7
CE PE P PE CE2

45Nokia 2020
© Nokia Confidential

Objective:
In this lab, students will learn how to create SAP-Ingress QoS policies that include policers
instead of queues to process the incoming packets.
Copy the existing SAP-Ingress QoS policy 10 into a new one with an Id of 20.
R5-R8# configure qos copy sap-ingress 10 20
Create within policy 20 four policers with the same Ids and rate parameters as the queues
previously created as part of policy 10.

R5-R8#configure qos sap-ingress 20 policer 3 create rate 7000 cir 2000

R5-R8#configure qos sap-ingress 20 policer 4 create rate 2500 cir 500
R5-R8#configure qos sap-ingress 20 policer 5 create rate 2500 cir 500
R5-R8#configure qos sap-ingress 20 policer 6 create rate 150 cir 150
R5-R8#configure qos sap-ingress 20
R5-R8>config>qos>sap-ingress#info
----------------------------------------------
... Output omitted ...
policer 3 create
rate 7000 cir 2000
exit
policer 4 create
rate 2500 cir 500
exit
policer 5 create
rate 2500 cir 500
exit
policer 6 create
rate 150 cir 150
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 45
Creating and Applying a SAP-ingress QoS Policer
Creating and Applying a SAP-ingress QoS Policer
Map the forwarding classes to the corresponding policers, instead of the queues. The
commands
Switch toneeded for this are shown below.
notes view!

R5-R8# configure qos sap-ingress 20 fc "l2" create policer 3

R5-R8# configure qos sap-ingress 20 fc "af" create policer 4
R5-R8# configure qos sap-ingress 20 fc "h2" create policer 5
R5-R8# configure qos sap-ingress 20 fc "ef" create policer 6
R5-R8# configure qos sap-ingress 20

R5-R8>config>qos>sap-ingress# info
----------------------------------------------
... Output omitted ...
fc "l2" create
policer 3
exit
fc "af" create
policer 4
exit
46Nokia 2020
© fc "h2" create Nokia Confidential

policer 5
exit
fc "ef" create
policer 6
exit

Once SAP-Ingress policy 20 is complete, apply it to the Epipe SAPs on all four CE routers. The
Epipe configuration then changes as follows.

*A:R5# configure service epipe 1 sap 1/1/5:7 ingress qos 20

*A:R5# configure service epipe 1
*A:R1>config>service>epipe# info
----------------------------------------------
sap 1/1/5:7 create
ingress
qos 20
exit
egress
qos 10
exit
no shutdown
exit
spoke-sdp 6:1 create
no shutdown
exit
no shutdown
----------------------------------------------

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 46
Verifying a SAP-ingress QoS Policer
Verifying a SAP-ingress QoS Policer
Clear the statistics collected on the queues by issuing the following command on the P router.
Switch to notes view!
R5# clear service statistics sap 1/1/5:7 counters

Verify that the QoS policy has been properly created and applied by issuing the following
command. The example only shows PE2.

*A:R5# show service id 1 sap 1/1/5:7 stats | match Policer post-lines 20

Sap per Policer stats

------------------------------------------------------------------------------
Packets Octets

Ingress Policer 3 (Stats mode: minimal)

Off. All : 0 0
Dro. All : 0 0
47Nokia 2020
For.
©
All : 0 Nokia Confidential
0

Ingress Policer 4 (Stats mode: minimal)

Off. All : 0 0
Dro. All : 0 0
For. All : 0 0

Ingress Policer 5 (Stats mode: minimal)

Off. All : 0 0
Dro. All : 0 0
For. All : 0 0

Ingress Policer 6 (Stats mode: minimal)

Off. All : 0 0
Dro. All : 0 0
For. All : 0 0
==============================================================================

The previous output shows that the policers have been created, associated with the relevant
SAP, and that no packets have been processed by them yet. Observe that the statistics include
the number of packets (and the corresponding octets) that are being offered, dropped and
forwarded for each existing policer.
Observe as well that, even though the queues are still part of SAP-Ingress QoS policy 20, they
do not physically exist since none of the forwarding classes have been mapped to them.
In general, packets processed by a policer will experience a smaller delay than those processed
by a queue, but it may be at the cost of an increased probability of being dropped. The reason
for this is the fact that policers do not have a buffer where packets can wait for an opportunity
to be forwarded.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 47
Verifying a SAP-ingress QoS Policer [cont.]
Verifying a SAP-ingress QoS Policer [cont.]
In this lab, start generating traffic corresponding to two of the four different streams
discussed
Switch toabove
notes(Ping,
view!Telnet instead of SFTP), one at a time.

[root@pc9 ~]# ping 192.168.5.10

Students will issue the following command on their respective P router in order to clear again
the statistics collected on the SAP queues.

*A:R5# clear service statistics sap 1/1/5:7 counters

After a few seconds, students will display the SAP statistics using the following command. Use
the service Id that corresponds to your group (100, 200, 300 or 400).

*A:R5# show service id 1 sap 1/1/5:7Nokia

48Nokia 2020
© stats
Confidential

Analyze the statistics corresponding to the ingress queues, which include the number of
packets (and the corresponding octets) that are being offered, forwarded and dropped for
each existing queue. Verify that traffic is properly classified and queued by making sure that
the counters for the queue that is expected to receive the traffic being generated are
increasing. The example below shows a situation where Ping and Telnet traffic is being
generated.

*A:R5# show service id 1 sap 1/1/5:7 stats | match Policer post-lines 20

Sap per Policer stats

------------------------------------------------------------------------------
Packets Octets

Ingress Policer 3 (Stats mode: minimal)

Off. All : 0 0
Dro. All : 0 0
For. All : 0 0

Ingress Policer 4 (Stats mode: minimal)

Off. All : 0 0
Dro. All : 0 0
For. All : 0 0

Ingress Policer 5 (Stats mode: minimal)

Off. All : 0 0
Dro. All : 0 0
For. All : 0 0

Ingress Policer 6 (Stats mode: minimal)

Off. All : 6 612
Dro. All : 0 0
For. All : 6 612
==============================================================================

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 48
Verifying a SAP-ingress QoS Policer [cont.]
Verifying a SAP-ingress QoS Policer [cont.]
Stop the ping using CTL-C.
Switch to notes view!
64 bytes from 192.168.5.10: icmp_seq=2 ttl=64 time=3.33 ms
^C
--- 192.168.5.10 ping statistics ---
…

Start the Iperf traffic simulating Video1 and using the same commands analyze the statistics
corresponding to the Video1 traffic.

[root@pc9 ~]# iperf -u -c 192.168.5.10 -b 1M -t 3000 -i 1 -l 1470 -p 1234

------------------------------------------------------------
Client connecting to 192.168.5.10, UDP port 1234
Sending 1470 byte datagrams, IPG target: 11215.21 us (kalman adjust)
UDP buffer size: 208 KByte (default)
------------------------------------------------------------
[ ©49
3]Nokia local
2020 192.168.5.9 port 40988 connected
Nokia Confidential with 192.168.5.10 port 1234
[ ID] Interval Transfer Bandwidth
[ 3] 0.0- 1.0 sec 131 KBytes 1.07 Mbits/sec
[ 3] 1.0- 2.0 sec 128 KBytes 1.05 Mbits/sec

[root@PC10 ~]# iperf -s -u -p 1234

------------------------------------------------------------
Server listening on UDP port 1234
Receiving 1470 byte datagrams
UDP buffer size: 208 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.5.10 port 1234 connected with 192.168.5.9 port 55656

*A:R5# clear service statistics sap 1/1/5:7 counters

After a few seconds, students will display the SAP statistics using the following command. Use
the service Id that corresponds to your group (100, 200, 300 or 400).

*A:R5# show service id 1 sap 1/1/5:7 stats | match Policer post-lines 20

------------------------------------------------------------------------------
Packets Octets

Ingress Policer 3 (Stats mode: minimal)

Off. All : 0 0
Dro. All : 0 0
For. All : 0 0

Ingress Policer 4 (Stats mode: minimal)

Off. All : 0 0
Dro. All : 0 0
For. All : 0 0

Ingress Policer 5 (Stats mode: minimal)

Off. All : 769 1165804
Dro. All : 0 0
For. All : 769 1165804

Ingress Policer 6 (Stats mode: minimal)

Off. All : 0 0
Dro. All : 0 0
For. All : 0 0

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 49
Verifying a SAP-ingress QoS Policer [cont.]
Verifying a SAP-ingress QoS Policer [cont.]
Start the Iperf traffic simulating Video2 and using the same commands analyze the statistics
corresponding to the
Switch to notes Video2 traffic.
view!

[root@pc9 ~]# iperf -u -c 192.168.5.10 -b 1M -t 3000 -i 1 -l 1470 -p 5678

------------------------------------------------------------
Client connecting to 192.168.5.10, UDP port 5678
Sending 1470 byte datagrams, IPG target: 11215.21 us (kalman adjust)
UDP buffer size: 208 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.5.9 port 38342 connected with 192.168.5.10 port 5678
[ ID] Interval Transfer Bandwidth
[ 3] 0.0- 1.0 sec 131 KBytes 1.07 Mbits/sec
[ 3] 1.0- 2.0 sec 128 KBytes 1.05 Mbits/sec

[root@PC10 ~]# iperf -s -u -p 5678

------------------------------------------------------------
Server listening on UDP port 5678
50Nokia 2020
© Nokia Confidential
Receiving 1470 byte datagrams
UDP buffer size: 208 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.5.10 port 5678 connected with 192.168.5.9 port 53752

A:R5# clear service statistics sap 1/1/5:7 counters

A:R5# show service id 1 sap "1/1/5:7" stats | match Policer post-lines 20

Sap per Policer stats

------------------------------------------------------------------------------
Packets Octets

Ingress Policer 3 (Stats mode: minimal)

Off. All : 0 0
Dro. All : 0 0
For. All : 0 0

Ingress Policer 4 (Stats mode: minimal)

Off. All : 907 1375012
Dro. All : 0 0
For. All : 907 1375012

Ingress Policer 5 (Stats mode: minimal)

Off. All : 0 0
Dro. All : 0 0
For. All : 0 0

Ingress Policer 6 (Stats mode: minimal)

Off. All : 0 0
Dro. All : 0 0
For. All : 0 0
===========================================================

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 50
Verifying a SAP-ingress QoS Policer [cont.]
Verifying a SAP-ingress QoS Policer [cont.]
Start the SFTP traffic and using the same commands analyze the statistics corresponding to
theSwitch
SFTP traffic.
to notes view!

[root@pc9 ~]# sftp 192.168.5.10

########################################################################
# Notice: The use of this system is restricted to users who have been #
# authorized by Nokia. Except where prohibited by law, Nokia may #
# monitor, record and audit all system activities. Any unauthorized #
# use of this system, or use in violation of Nokia's policies and #
# applicable law, could result in Company disciplinary actions and/or #
# criminal and civil penalties. #
########################################################################
root@192.168.5.10's password: root
Connected to 192.168.5.10.
sftp> get BigFile
Fetching /root/BigFile to BigFile
/root/BigFile 31% 32MB 346.4KB/s 03:21 ETA
51Nokia 2020
© Nokia Confidential

A:R5# clear service statistics sap 1/1/5:7 counters

A:R5# show service id 1 sap "1/1/5:7" stats | match Policer post-lines 20

------------------------------------------------------------------------------
Packets Octets

Ingress Policer 3 (Stats mode: minimal)

Off. All : 1446 111096
Dro. All : 0 0
For. All : 1446 111096

Ingress Policer 4 (Stats mode: minimal)

Off. All : 0 0
Dro. All : 0 0
For. All : 0 0

Ingress Policer 5 (Stats mode: minimal)

Off. All : 0 0
Dro. All : 0 0
For. All : 0 0

Ingress Policer 6 (Stats mode: minimal)

Off. All : 0 0
Dro. All : 0 0
For. All : 0 0
===========================================================

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 51
 Lab - Default vs. Hierarchical
Scheduling

52Nokia 2020
© Nokia Confidential

Scheduling is associated with the process of deciding how and when packets will exit a queue.
Each queue is visited periodically by a scheduler to decide which of the buffered packets are to
be forwarded immediately, either in or out of profile, and which ones need to continue waiting.
Queues will participate in what is called default scheduling, unless they are explicitly configured
to be part of a hierarchical bandwidth distribution arrangement.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 52
Initial and Final Lab Rollback Config

Use the command show system rollback to identify each rollback config’s index
number (X, and Y).

Initial rollback config file’s comment - SAP-Ingress-QoS-Policer

• /admin rollback revert X

Final rollback config file’s comment - H-QoS

To compare current config with the final lab answer:

• /admin rollback compare active-cfg to Y

53Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 53
 Lab Design

• Objective:
- Configure hierarchical BW allocation using policers in place of queues.
192.168.5.9/24 192.168.5.10/24
4
PC9 R5 R1 R6 PC10
1/1/5:7 1/1/5 1/1/6 eth1
eth1 1/1/4 1/1/7 1/1/5:7
CE PE P PE CE2

• Exercise:
- Change the SAP-ingress policy to specify the parent scheduler for each queue & the parameters with which it will
compete for bandwidth
- Verify that the scheduler policy has been properly configured and applied.
192.168.5.11/24 192.168.5.12/24
PC11 R7 R3 R8 PC12
1/1/5:7 1/1/5 1/1/6 eth1
eth1 1/1/4 1/1/7 1/1/5:7
CE PE P PE CE2

54Nokia 2020
© Nokia Confidential

Objective:
In this lab, students will learn how to create SAP-Ingress QoS policies that include policers
instead of queues to process the incoming packets.
Copy the existing SAP-Ingress QoS policy 10 into a new one with an Id of 30.
R5-R8# configure qos copy sap-ingress 10 30
Create within policy 30 four policers with the same Ids and rate parameters as the queues
previously created as part of policy 10.

R5-R8#configure qos sap-ingress 30 policer 3 create rate 7000 cir 2000

R5-R8#configure qos sap-ingress 30 policer 4 create rate 2500 cir 500
R5-R8#configure qos sap-ingress 30 policer 5 create rate 2500 cir 500
R5-R8#configure qos sap-ingress 30 policer 6 create rate 150 cir 150
R5-R8#configure qos sap-ingress 30
R5-R8>config>qos>sap-ingress#info
----------------------------------------------
... Output omitted ...
policer 3 create
rate 7000 cir 2000
exit
policer 4 create
rate 2500 cir 500
exit
policer 5 create
rate 2500 cir 500
exit
policer 6 create
rate 150 cir 150
exit

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 54
Default Scheduling
Default Scheduling
Forwarding classes NC, H1, EF, and H2 are considered expedited, whereas forwarding classes
L1, AF,
Switch L2, toand BE are
notes considered best-effort. A queue’s type can be configured as expedite,
view!
best effort or auto-expedite (default). If a queue is auto-expedite, it will be considered
expedite if all of the forwarding classes mapped to it are expedited; otherwise, it will be
considered best effort.
For any given queue, a packet on egress will be considered in or out of profile depending on
whether servicing it implies remaining under the queue’s CIR (Committed Information Rate) or
exceeding it, respectively.
Default scheduling is based on the queue’s type (expedited or best-effort) and the profile (in
or out) of the packet at the head of the queue:
• The first service loop includes expedited queues with in-profile packets at their heads
• The second loop includes best-effort queues with in-profile packets at their heads
• The third service loop includes expedited queues with out-of-profile packets at their heads
• The fourth loop includes best-effort queues with out-of-profile packets at their heads
With this in mind, and given the classification assigned to the different types of traffic being
generated
55Nokia 2020
©
in this course: Nokia Confidential

• Ping and video packets arriving at the service SAPs will be forwarded first (up to their
respective CIR rates) because they are put in expedited queues,
• They will be followed by the other video and TCP packets (up to their respective CIR rates)
because they are put in best-effort queues,
• Out-of-profile packets will be serviced next, following a similar sequence as in-profile
packets.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 55
Hierarchical Scheduling
Hierarchical Scheduling
If we wanted to give a higher priority to some customers over others (perhaps because they
are Switch
willing to
to notes
pay a view!
premium for a better service), at the same time that service differentiation
is maintained between video packets versus FTP and other data packets, we need to create a
hierarchical structure.
Students will configure on each PE router a hierarchical scheduler policy called “HQoS1”. This
policy will include a tier-1 scheduler called “root” and two tier-2 schedulers, one called “gold”
and the other one called “silver”. Both the gold and the silver schedulers will have the root
scheduler as their parent. The in-profile and out-of-profile priority levels (cir-level and level,
respectively) will be set to 6 for the gold scheduler and to 4 for the silver scheduler. The in-
profile and out-of-profile weight values (cir-weight and weight, respectively) will be set to 50
for both schedulers. Also, their PIR will be set to the maximum port rate and their CIR will be
set to the sum of their children CIR values.
The configuration commands needed to create such a hierarchical scheduler structure are
shown below.
56Nokia 2020
© Nokia Confidential

*A:R5>config>qos# info
----------------------------------------------
... Output omitted ...
scheduler-policy "HQoS1" create
tier 1
scheduler "root" create
description "Scheduler sharing bandwidth among all
customers"
exit
exit
tier 2
scheduler "gold" create
description "Scheduler for customers paying premium"
parent "root" level 6 weight 50 cir-level 6 cir-weight 50
exit
scheduler "silver" create
description "Scheduler for customers not paying premium"
parent "root" level 4 weight 50 cir-level 4 cir-weight 50
exit
exit
exit

By having different priority levels, both for in-profile and out-of-profile packets, children of the
gold scheduler will have a higher priority to use bandwidth, meaning that children of the silver
scheduler will only be able to forward in-profile packets when there are no backlogged in-
profile “golden” queues. The same applies for out-of-profile packets.
This hierarchy needs to be applied to the queues previously created in the SAP-Ingress QoS
policy 10. Students will select the gold scheduler as the parent for their queues. Additionally:
• EF packets (queue 6) will be given a priority level of 8 (highest) and a default weight of 1,
both for in-profile and out-of-profile packets,
• AF packets (queue 5) will be given a priority level of 5 (lower) and a weight of 4, both for in-
profile and out-of-profile packets,
• L1 packets (queue 4) will be given a priority level of 5 (same as above) and a default weight
of 1, both for in-profile and out-of-profile packets,
• Finally, L2 packets (queue 3) will be given a priority level of 1 (lowest) and a default weight of
1, both for in-profile and out-of-profile packets.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 56
Hierarchical Scheduling [cont.]
Hierarchical Scheduling [cont.]
The changes needed on the SAP-Ingress policy are shown below.
Switch to notes view!
*A:R5# configure qos sap-ingress 30
*A:R5>config>qos>sap-ingress# info
----------------------------------------------
queue 1 create
exit
queue 3 create
parent "gold" cir-level 1
rate 7000 cir 2000
exit
queue 4 create
parent "gold" level 5 cir-level 5
rate 2500 cir 500
burst-limit 120000 bytes
exit
queue 5 create
parent "gold" level 5 weight 4 cir-level 5 cir-weight 4
57Nokia 2020
©
rate 2500 cir 500 Nokia Confidential
burst-limit 120000 bytes
exit
queue 6 create
parent "gold" level 8 cir-level 8
rate 150 cir 150
exit
... Output omitted ...

After these policies have been completed, students will change back the SAP to using SAP-
Ingress QoS policy 30. An additional configuration command is needed to indicate the SAP
which scheduler-policy to use to find out who the parents of its queues are.

*A:R5# configure service epipe 1

*A:R5>config>service>epipe# info
----------------------------------------------
sap 1/1/5:7 create
ingress
scheduler-policy "HQoS1"
qos 20
exit
egress
scheduler-policy "HQoS1"
qos 10
exit
no shutdown
exit
spoke-sdp 6:1 create
no shutdown
exit
no shutdown
----------------------------------------------

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 57
Verification of Hierarchical Scheduling
Verification of Hierarchical Scheduling
The following command can be issued to verify that the scheduler policy has been properly
configured
Switch toand applied.
notes view!

*A:R5# show qos scheduler-hierarchy sap 1/1/5:7 ingress detail

…

Root (Ing)
| slot(1)
|--(S) : root
| | AdminPIR:max AdminCIR:3150(sum)
| | Limit Unused Bandwidth: disabled
| |
| |
| | [Withi

+n CIR Level 0 Weight 0]

| | Assigned:0 Offered:0
| | Consumed:0
| ©58Nokia
| 2020 Nokia Confidential

| | [Above CIR Level 0 Weight 0]

| | Assigned:0 Offered:0
| | Consumed:0
| |
| |
| | TotalConsumed:0
| | OperPIR:max
| |
| | [As Parent]
| | Rate:max
| | ConsumedByChildren:0
| |
| |
| |--(S) : gold
| | | AdminPIR:max AdminCIR:3150(sum)
| | | Parent Limit Unused Bandwidth: not-found
| | |
| | |
| | | [Within CIR Level 6 Weight 50]
| | | Assigned:3150 Offered:0
| | | Consumed:0
| | |
| | | [Above CIR Level 6 Weight 50]
| | | Assigned:max Offered:0
| | | Consumed:0
| | |
| | |
| | | TotalConsumed:0
| | | OperPIR:max
| | |
| | | [As Parent]
| | | Rate:max
| | | ConsumedByChildren:0

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 58
Verification of Hierarchical Scheduling
Verification of Hierarchical Scheduling [cont.]
| | (Q) : 1->1/1/5->6 1-1
| Switch
| |to notes
| AdminPIR:150
view! AdminCIR:150
| | | | Parent Limit Unused Bandwidth: not-found
| | | | CBS:7680 B
| | | | MBS:67200 B
| | | | Depth:0 B
| | | | HighPlus Drop Tail:67200 B
| | | | High Drop Tail:67200 B
| | | | Low Drop Tail:60480 B
| | | | Exceed Drop Tail:53760 B
| | | |
| | | | [Within CIR Level 8 Weight 1]
| | | | Assigned:150 Offered:0
| | | | Consumed:0
| | | |
| | | | [Above CIR Level 8 Weight 1]
| | | | Assigned:150 Offered:0
| | | | Consumed:0
| | | |
| ©59Nokia
| 2020| | TotalConsumed:0 Nokia Confidential
| | | | OperPIR:150 OperCIR:150
| | | | OperFIR:0
| | | |
| | | | PktByteOffset:add 0*
| | | | OnTheWireRates:false
| | | | ATMOnTheWireRates:false
| | | | LastMileOnTheWireRates:false
... Output omitted ...
| |
| |--(S) : silver
| | | AdminPIR:max AdminCIR:0(sum)
| | | Parent Limit Unused Bandwidth: not-found
| | |
| | | [Within CIR Level 4 Weight 50]
| | | Assigned:0 Offered:0
| | | Consumed:0
| | |
| | | [Above CIR Level 4 Weight 50]
| | | Assigned:max Offered:0
| | | Consumed:0
| | |
| | | TotalConsumed:0
| | | OperPIR:max
| | |
| | | [As Parent]
| | | Rate:max
| | | ConsumedByChildren:0

In the screen capture above, each scheduler is identified by an (S) and its name. Similarly, each
queue is identified by a (Q) and by specifying the service and the SAP it belongs to, plus the
queue ID. For instance, 1->1/1/5->6 identifies queue 6 corresponding to SAP 1/1/5 of service 1.
The priority level and weight values are displayed for each scheduler and queue within square
brackets.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 59
Verification of Hierarchical Scheduling [cont.]
Verification of Hierarchical Scheduling [cont.]
Additionally, there are different values being displayed for each scheduler and queue:
AdminSwitch CIR/PIR: Specifies
to notes view! the configured value of CIR/PIR.
Assigned CIR/PIR: Specifies the CIR/PIR rate that accounts for transmission opportunities
granted by a parent scheduler to one of its members, which may have been used or not
depending on whether or not there are packets waiting to be forwarded.
Consumed CIR/PIR: Specifies the PIR/CIR rate that accounts for transmission opportunities
granted by a parent scheduler to one of its members and actually used by this member.
Offered CIR/PIR: Specifies the offered load of a given member.
Assigned, consumed and offered values will change dynamically as the traffic generated by
customers fluctuates, and as bandwidth is redistributed from queues that are not using up
their bandwidth to queues that require it and vice versa.
From the previous outputs, we can see that queues have in fact been organized in the desired
hierarchical structure.
The instructor will generate traffic corresponding to all flows. Wait a few seconds and issue the
previous command again and observe how the assigned, consumed and offered values
60Nokia 2020
© Nokia Confidential
change.
Note that all queues have been parented by the gold scheduler in this example. If a new SAP
were to be created on the same port, and if its queues were parented by the silver scheduler,
then they would have a lower precedence to use bandwidth since they would compete, as a
group, with a lower priority versus these queues that belong to the gold scheduler.
In that hierarchical structure, however, priorities and weights within each parent scheduler
would be maintained, meaning that Ping traffic would still have a higher priority that Video
traffic, and Video would still have a higher priority than FTP traffic.
If there is overbooking (sum of CIR values for the different queues exceeding the router’s
forwarding capacity) in a hierarchical scheduling environment, since bandwidth is allocated in a
weighted fair queuing fashion, queues with the same parent sharing the same priority level will
get an amount of bandwidth proportional to their weight, up to their CIR. As an example,
queue 5 would get four times as much bandwidth as queue 4.
An important remark is that, if a queue is not associated with a parent scheduler, it will be
considered orphaned. For that reason, it will be serviced with a lower priority than any
parented queue. In other words, an orphaned queue will be serviced only if there is bandwidth
left over after exhaustively serving all queues that do have a parent scheduler.

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 60
Wrap-up
In this module we have covered the following items:
• Configured QoS Classification and Marking
- Created a SAP-ingress and SAP-ingress policy to specify IP criteria for marking traffic,
create queues and assign forwarding classes to queues
- Created Network and Network queue policy’s to consistently mark and queue traffic
transiting the end to end QoS network
- Verified that the SAP policy and network policies have been properly configured and
applied
• Configured QoS using policers instead of queues
- Configured and apply a scheduler policy
- Changed the SAP-ingress policy to specify the parent scheduler for each queue & the
parameters with which it will compete for bandwidth
- Verified that the scheduler policy has been properly configured and applied
• Configured and verified hierarchical scheduling

61Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 61
62Nokia 2020
© Nokia Confidential

COPYRIGHT © 2020 Nokia. CONFIDENTIAL.

ER00198-V-2000 V0 - S06M01 Ed0 62
This training was brought to you by NokiaEDU.

Please follow the link to learn more at the Nokia Learning Store:

https://learningstore.nokia.com/

Follow us on social media:

LinkedIn: https://www.linkedin.com/company/nokia
Facebook: https://www.facebook.com/nokia/
Glassdoor: https://www.glassdoor.com/nokia
Twitter: https://twitter.com/nokia
Youtube: https://www.youtube.com/user/nokia
© Nokia