Configuring Dynamic Routing

• This module will offer an introduction to configuring IS-IS on the Nokia

(fmr. Alcatel-Lucent) Service Router platform. This module will also
introduce BFD, routing policies, and debugging.

• This module assumes the reader is familiar with router interfaces, and the
overall concept of link-state protocols.

• RFC 1142: OSI IS-IS Intra-domain Routing Protocol -

https://tools.ietf.org/html/rfc1142

• RFC 5880: Bidirectional Forwarding Detection (BFD) -

https://tools.ietf.org/html/rfc5880
 Goals
• Debugging
• Observe IS-IS adjacencies forming via debug
• Observe LSPDUs via debug
• Routing policy
• Allow direct (Local) routes to be redistributed into IS-IS
• Apply to IS-IS as an export policy
• IGP (IS-IS)
• Configure the global router-id on each SR. The router-id will match the “system” address.
• Configure all Service Routers/Intermediate Systems with an Area-ID of 49.00
• Configure all Service Routers/Intermediate Systems to be Level 2 Only.
• Configure each router interface participating in IS-IS as a circuit of the ‘point-to-point’ type.
• Configure a wide metric of 5000 on each router interface participating in IS-IS.
• Configure MD5 authentication, using the key “my-isis-key”
• Enable IPv4 BFD
• BFD
• Configure BFD on all router interfaces participating in IS-IS.
• Configure BFD with a transmit-interval of 100, a receive-interval of 100, and a multiplier of 3
• Alter BFD’s default parameters to force the SFM (or CPM) to manage sessions: type cpm-np
 Debugging

configure log file-id 66 Creates the log file (66) for debugs.

description “File for log-id 66” The file’s description.

location cf3: Instructs the SR to save this in root (cf3:).

rollover 60 retention 24 Log rolls over every 60m, kept for 24h.

/configure log log-id 66 Creates the event handler destination (66).

description “Log for protocol debugs” The log’s description.

from debug-trace Capture data from any debug commands.

to file 66 Place the captured data in file 66.

/show log log-id 66 Display the contents of log-id 66.

 Routing Policies
• Allow routes to be controlled according to specifically defined criteria.
• Routes can be allowed or denied based on various parameters:
• Destination IP
• Protocol
• Packet size
• Community list
• Routing policies can reference prefix-lists.
• The goal of our routing policy:
• Redistribute directly-connected (Local) routes into IS-IS.
 Routing Policies

configure router policy-options begin Enters ‘edit’ mode via the CLI.

policy-statement “EXPORT-DIRECT-ROUTES” The name of our routing policy.

default-action reject The default-action for this policy.

entry 1 The specific entry in this policy.

from protocol direct ‘from’ directly-connected (Local) interfaces.
to protocol isis ‘to’ protocol IS-IS.

action accept The action for this entry.

/configure router policy-options commit Commit changes made to this policy.
 Dynamic Routing
• An IGP (Interior Gateway Protocol) is used to exchange routing
information within a routing domain.

• Service Providers typically use a Link State IGP to achieve internal

route redistribution within their routing domain.

• Learning routes dynamically will allow N1 to reach N6, even though

they aren’t directly-connected.
 IS-IS
Area-ID: 49.00 N6
N1
Level 2 Only
N2 N5

BFD BFD

BFD

N3 N4
 BFD
• BFD – Bi-directional Forwarding Detection.
• Asynchronous protocol

• Establishes a lightweight session between systems to detect link

failure.

• BFD messages are processed by the IOMs, by-default.

• BFD sessions are configured on router interfaces, and enabled within

the desired protocol.
 IS-IS adjacency Without BFD

Link failure
N1 SW1 SW2 N6

No link state changes are detected for
at least 27 seconds; N1 believes the
adjacency is UP and forwards traffic
into a blackhole until the Hold Time
expires.
No link state changes are detected for
at least 27 seconds; N6 believes the
adjacency is UP and forwards traffic
into a blackhole until the Hold Time
expires.

IS-IS adjacency
 IS-IS adjacency,
BFD session
With BFD

Link failure
N1 SW1 SW2 N6

BFD tears down the adjacency in <1
second due to the protocol not
receiving Control Messages from the
far-end. N1 updates its LSDB, and
floods that update to its adjacent
neighbors.
BFD tears down the adjacency in <1
second due to the protocol not
receiving Control Messages from the
far-end. N6 updates its LSDB, and
floods that update to its adjacent
neighbors.

IS-IS adjacency,
BFD session
 Goals
• Debugging
• Observe IS-IS adjacencies forming via debug
• Observe LSPDUs via debug
• Routing policy
• Allow direct (Local) routes to be redistributed into IS-IS
• Apply to IS-IS as an export policy
• IGP (IS-IS)
• Configure the global router-id on each SR. The router-id will match the “system” address.
• Configure all Service Routers/Intermediate Systems with an Area-ID of 49.00
• Configure all Service Routers/Intermediate Systems to be Level 2 Only.
• Configure each router interface participating in IS-IS as a circuit of the ‘point-to-point’ type.
• Configure a wide metric of 5000 on each router interface participating in IS-IS.
• Configure MD5 authentication, using the key “my-isis-key”
• Enable IPv4 BFD
• BFD
• Configure BFD on all router interfaces participating in IS-IS.
• Configure BFD with a transmit-interval of 100, a receive-interval of 100, and a multiplier of 3
• Alter BFD’s default parameters to force the SFM (or CPM) to manage sessions: type cpm-np