Nokia (Alcatel-Lucent) OSPF Configuration Tutorial

Nokia (Alcatel-Lucent) OSPF configuration tutorial | Networking in a Service Provider ...
Página 1 de 31
Nokia (Alcatel-Lucent) OSPF configuration tutorial
T
he purpose of this post is to cover basic OSPF configuration steps and commands. Intended
readers are engineers with basic OSPF knowledge who want to know how to configure OSPF
on Alcatel-Lucent Service Routers (7750-SR, 7705-SR, 7210-SR). All the examples are valid for
TiMOS-B-12.0.R8 both/i386 ALCATEL SR 7750 Copyright (c) 2000-2015 Alcatel-Lucent. software.
SINGLE-AREA OSPF
Basic OSPF protocol configuration in a single area consists of the next steps:
• Enable OSPF globally

• Configure router with OSPF Router ID
• Configure backbone OSPF Area 0
• Include interfaces in Area 0
I will guide you through basic OSPF configuration steps referring to this topology:
http://noshut.ru/2015/06/alcatel-lucent-ospf-configuration-tutorial/ 09/01/2018
Nokia (Alcatel-Lucent) OSPF configuration tutorial | Networking in a Service Provider ... Página 2 de 31
Enabling OSPF and Router ID

To enable OSPF on a router simply issue configure router ospf command. This will start OSPF
process #0 on a router. If you would like to run another separate OSPF process on the same router,
use configure router ospf <N> , where <N> is a decimal number of the OSPF process.
To operate properly OSPF routers should have unique Router ID, which is a 32-bit identifier. Router
ID selection process goes like this (in priority order):
• configured globally for a router router-id value

• configured system interface IPv4 address value
• the last 32 bits of the chassis MAC address
1 # configuring router-id explicitly

2 *A:R1# configure router router-id
3 - no router-id
4 - router-id <ip-address>
5
6 <ip-address> : a.b.c.d
7
8 *A:R1# configure router router-id 2.2.2.2
To check Router ID currently value in use and OSPF admin/oper status issue the command show
router ospf status
1 *A:R1# show router ospf status

2
3 ===============================================================================
4 OSPFv2 (0) Status
5 ===============================================================================
6 OSPF Cfg Router Id : 0.0.0.0
7 OSPF Oper Router Id : 1.1.1.1 # Router ID inherited from System IPv4 address
8 OSPF Version : 2
9 OSPF Admin Status : Enabled # OSPF administratively enabled
10 OSPF Oper Status : Enabled # OSPF is operating
11 <output omitted>
Configuring Backbone Area

To configure OSPF area you should use command area in OSPF configuration context:
1 A:R1>config>router>ospf# area
2 - area <area-id>
3 - no area <area-id>
4
5 <area-id> : <ip-address> | [0..4294967295]
Area ID value could be entered as decimal, like area 0 or in dotted-decimal format like area
0.0.0.0 .
It is common practice to use one composite command to enable OSPF process and to configure
OSPF area instead of two separate commands:
1 # This command will enable OSPF process (it is disabled by default) and configure Area 0 on this router.
2
3 A:R1# configure router ospf area 0
To check all the configured areas on a router use show router ospf area
1 A:R1# show router ospf area

2
3 ==================================================================
4 OSPFv2 (0) all areas
5 ==================================================================
6 Area Id Type SPF Runs LSA Count LSA Cksum Sum
7 ------------------------------------------------------------------
8 0.0.0.0 Standard 2 1 0xcaf7
9 ------------------------------------------------------------------
10 No. of OSPF Areas: 1
11 ==================================================================
Configuring OSPF interfaces

Once backbone area is configured its time to add some interfaces to it with interface
<interface_name> command.
1 # Entering to OSPF Area 0 configuration context

2 *A:R1# configure router ospf area 0
3
4 # Adding system interface to OSPF process
5 *A:R1>config>router>ospf>area# interface "system"
6 *A:R1>config>router>ospf>area>if$ back
7
8 # Adding interface toR2 and configuring it with point-to-point type
9 # By default, ethernet interfaces use Broadcast interface type
10 *A:R1>config>router>ospf>area# interface "toR2"
11 *A:R1>config>router>ospf>area>if$ interface-type point-to-point
12 *A:R1>config>router>ospf>area>if$ back
13 *A:R1>config>router>ospf>area# back
14
15 # This configuration steps effectively lead us to this OSPF configuration for router R1
16 *A:R1>config>router>ospf# info
17 ----------------------------------------------
18 area 0.0.0.0
19 interface "system"
20 no shutdown
21 exit
22 interface "toR2"
23 interface-type point-to-point
24 no shutdown
25 exit
26 exit
27 no shutdown
28 ----------------------------------------------
To check that OSPF interfaces was configured properly and are operating use this show command:
1 *A:R1# show router ospf interface

2
3 ===============================================================================
4 OSPFv2 (0) all interfaces
5 ===============================================================================
6 If Name Area Id Designated Rtr Bkup Desig Rtr Adm Oper
7 -------------------------------------------------------------------------------
8 system 0.0.0.0 1.1.1.1 0.0.0.0 Up DR
9 toR2 0.0.0.0 0.0.0.0 0.0.0.0 Up PToP
10 -------------------------------------------------------------------------------
11 No. of OSPF Interfaces: 2
12 ===============================================================================
Repeat the same configuration steps by including all the interfaces to OSPF Area 0 to the other
backbone routers R2-R3-R4 and you will end up with fully configured OSPF Backbone Area. Finally
its time to check that our routers established neighboring relationships:
1 A:R1# show router ospf neighbor

2
3 ===============================================================================
4 OSPFv2 (0) all neighbors
5 ===============================================================================
6 Interface-Name Rtr Id State Pri RetxQ TTL
7 Area-Id
8 -------------------------------------------------------------------------------
9 toR2 2.2.2.2 Full 1 0 33
10 0.0.0.0
11 toR3 3.3.3.3 Full 1 0 39
12 0.0.0.0
13 -------------------------------------------------------------------------------
14 No. of Neighbors: 2
15 ===============================================================================
One of the most used OSPF verification commands is show router ospf database . This
command shows all the Links State Advertisements (LSA) and helps the engineer to troubleshoot
OSPF-related issues.
1 A:R1# show router ospf database

2
3 ===============================================================================
4 OSPFv2 (0) Link State Database (Type : All)
5 ===============================================================================
6 Type Area Id Link State Id Adv Rtr Id Age Sequence Cksum
7 -------------------------------------------------------------------------------
8 Router 0.0.0.0 1.1.1.1 1.1.1.1 873 0x8000000b 0x4dd5
9 Router 0.0.0.0 2.2.2.2 2.2.2.2 561 0x80000006 0x1c2b
10 Router 0.0.0.0 3.3.3.3 3.3.3.3 879 0x80000008 0x6d94
11 Router 0.0.0.0 4.4.4.4 4.4.4.4 1588 0x80000005 0x94ec
12 -------------------------------------------------------------------------------
13 No. of LSAs: 4
14 ===============================================================================
15
16
17 ### additional OSPF database show commands ###
18
20 - database [type {router|network|summary|asbr-summary|external|nssa|all}]
21 [area <area-id>] [adv-router <router-id>] [<link-state-id>] [detail]
22
23 <router|network|su*> : KEYWORDS - specify database type
24 <area-id> : ip-address - a.b.c.d
25 area - [0..4294967295]
26 <router-id> : a.b.c.d
27 <link-state-id> : a.b.c.d
28 <detail> : keyword - displays detailed information
MU LTI-AREA OSPF
Basic Multi-area OSPF configuration is straightforward as well. I added two more routers to
previous topology acting as core routers in two new areas: Area 1 and Area 2.
sorry fellows, I mistyped port numbers for R5-R1 and R6 -R2 pairs, it should be 1/1/4. Though this
wont affect the course of this topic in anyway
W e will start by configuring Area 1 on routers R5 and R1. Every command is from the previous
section, so you wouldn’ t face any problems.
R5 R1 (ABR)
1 # Creating Area 1 on R5 and adding "system" and "toR1" interfaces

2
4 *A:R5>config>router>ospf>area$ interface "toR1" interface-type point-to-point
5 *A:R5>config>router>ospf>area$ interface "system"
6
7
8 # Verifying created Area 1 and its interfaces
9
11
12 ===============================================================================
14 ===============================================================================
16 -------------------------------------------------------------------------------
17 system 0.0.0.1 5.5.5.5 0.0.0.0 Up DR
18 toR1 0.0.0.1 0.0.0.0 0.0.0.0 Up PToP
19 -------------------------------------------------------------------------------
21 ===============================================================================
Adding one more Area (besides backbone Area 0) on R1 makes it Area Border Router. So R1 will
form and maintain another neighbor relationships with R5 in Area 1. W e will check if its true:
on R5 on R1
1 *A:R5# show router ospf neighbor

2
3 ===============================================================================
5 ===============================================================================
7 Area-Id
8 -------------------------------------------------------------------------------
9 toR1 1.1.1.1 Full 1 0 33
10 0.0.0.1
11 -------------------------------------------------------------------------------
13 ===============================================================================
I repeated same configuration steps on R6 : added it to Area 2 and neighbored with R2.
Examining Multi-area LSDB

Since we configured multi-area OSPF we should expect to see some new LSA in our Link State
Database:
on R1 (ABR) on R5

2
3 ===============================================================================
5 ===============================================================================
7 -------------------------------------------------------------------------------
8 Router 0.0.0.0 1.1.1.1 1.1.1.1 550 0x80000007 0x58cd
9 Router 0.0.0.0 2.2.2.2 2.2.2.2 668 0x80000006 0xaf65
10 Router 0.0.0.0 3.3.3.3 3.3.3.3 193 0x80000006 0x7192
11 Router 0.0.0.0 4.4.4.4 4.4.4.4 732 0x80000007 0xa34d
12 Summary 0.0.0.0 5.5.5.5 1.1.1.1 773 0x80000002 0x508f
13 Summary 0.0.0.0 10.1.5.0 1.1.1.1 1091 0x80000002 0x7172
14 Summary 0.0.0.0 6.6.6.6 2.2.2.2 519 0x80000002 0x4d3
15 Summary 0.0.0.0 10.2.6.0 2.2.2.2 724 0x80000002 0x3ca1
16 Router 0.0.0.1 1.1.1.1 1.1.1.1 830 0x80000004 0x50ea
17 Router 0.0.0.1 5.5.5.5 5.5.5.5 171 0x80000005 0x47bb
18 Summary 0.0.0.1 1.1.1.1 1.1.1.1 660 0x80000002 0x1d37
19 Summary 0.0.0.1 2.2.2.2 1.1.1.1 183 0x80000002 0xda11
20 Summary 0.0.0.1 3.3.3.3 1.1.1.1 122 0x80000002 0xac3b
21 Summary 0.0.0.1 4.4.4.4 1.1.1.1 318 0x80000002 0x6a15
22 Summary 0.0.0.1 6.6.6.6 1.1.1.1 207 0x80000002 0xe69
23 Summary 0.0.0.1 10.1.2.0 1.1.1.1 377 0x80000003 0x9055
24 Summary 0.0.0.1 10.1.3.0 1.1.1.1 262 0x80000003 0x855f
25 Summary 0.0.0.1 10.2.4.0 1.1.1.1 1039 0x80000003 0x5a24
26 Summary 0.0.0.1 10.2.6.0 1.1.1.1 864 0x80000002 0x4637
27 Summary 0.0.0.1 10.3.4.0 1.1.1.1 1056 0x80000003 0x4e2f
28 -------------------------------------------------------------------------------
29 No. of LSAs: 20
30 ===============================================================================
Aha, R1 as being an ABR lists all LSA’ s for both Area 0 and Area 1. Moreover, R1 lists Type 3
Summary LSA from Area 0 to Area 1 and vice versa, from Area 1 to Area 0.
R5 has only Area 1’ s LSA’ s, since R5 lives in j ust one Area – Area 1.
V erifying OSPF routes propagation

To ensure that OSPF routes was transferred between OSPF lets check it by issuing a set of
commands on both R5 and R1:
on R1 (ABR) on R5
Nokia (Alcatel-Lucent) OSPF configuration tutorial | Networking in a Service Provid... Página 10 de 31
1 # Checking routes that have been received via OSPF

2
3 *A:R1# show router route-table protocol ospf
4
5 ===============================================================================
6 Route Table (Router: Base)
7 ===============================================================================
8 Dest Prefix[Flags] Type Proto Age Pref
9 Next Hop[Interface Name] Metric
10 -------------------------------------------------------------------------------
11 2.2.2.2/32 Remote OSPF 03h01m17s 10
Since we configured all routers in our topology we can try to run ping between R6 and R5:
1 A:R6# ping 5.5.5.5

2 PING 5.5.5.5 56 data bytes
3 64 bytes from 5.5.5.5: icmp_seq=1 ttl=62 time=11.7ms.
OSPF ROU TE SU MMARIZ ATION
So far we configured multi-area OSPF topology with three Areas. And one of the reasons to
implement multi-area OSPF topology is the ability to perform manual summariz ation. In this section
we will configure OSPF route summariz ation between Area 0 and Area 1.
To get a range of IP addresses which we will summariz e later we will add 3 loopback interfaces to
R3 router and include them in OSPF Area 0:
1 :R3# show router interface

2
3 ===============================================================================
4 Interface Table (Router: Base)
5 ===============================================================================
6 Interface-Name Adm Opr(v4/v6) Mode Port/SapId
7 IP-Address PfxState
8 -------------------------------------------------------------------------------
9 lo1 Up Up/-- Network loopback
10 192.168.3.1/32 n/a
12 192.168.3.2/32 n/a
14 192.168.3.3/32 n/a
15 <output omitted>
16
17
18
20
21 ===============================================================================
23 ===============================================================================
25 -------------------------------------------------------------------------------
26 system 0.0.0.0 3.3.3.3 0.0.0.0 Up DR
27 toR1 0.0.0.0 0.0.0.0 0.0.0.0 Up PToP
28 toR4 0.0.0.0 0.0.0.0 0.0.0.0 Up PToP
29 lo1 0.0.0.0 3.3.3.3 0.0.0.0 Up DR
30 lo2 0.0.0.0 3.3.3.3 0.0.0.0 Up DR
31 lo3 0.0.0.0 3.3.3.3 0.0.0.0 Up DR
32 -------------------------------------------------------------------------------
34 ===============================================================================
Since we added these interfaces to OSPF we see them coming to R5 router as Type 3 Network
Summary LSA. And these routes make their way to routing table.

2
3 ===============================================================================
5 ===============================================================================
7 -------------------------------------------------------------------------------
8 Router 0.0.0.1 1.1.1.1 1.1.1.1 531 0x80000005 0x4eeb
9 Router 0.0.0.1 5.5.5.5 5.5.5.5 43 0x80000006 0x45bc
10 Summary 0.0.0.1 1.1.1.1 1.1.1.1 496 0x80000003 0x1b38
11 Summary 0.0.0.1 2.2.2.2 1.1.1.1 1898 0x80000002 0xda11
12 Summary 0.0.0.1 3.3.3.3 1.1.1.1 225 0x80000003 0xaa3c
13 Summary 0.0.0.1 4.4.4.4 1.1.1.1 463 0x80000003 0x6816
14 Summary 0.0.0.1 6.6.6.6 1.1.1.1 373 0x80000003 0xc6a
15 Summary 0.0.0.1 10.1.2.0 1.1.1.1 323 0x80000004 0x8e56
16 Summary 0.0.0.1 10.1.3.0 1.1.1.1 32 0x80000004 0x8360
17 Summary 0.0.0.1 10.2.4.0 1.1.1.1 513 0x80000004 0x5825
18 Summary 0.0.0.1 10.2.6.0 1.1.1.1 1089 0x80000003 0x4438
19 Summary 0.0.0.1 10.3.4.0 1.1.1.1 1188 0x80000004 0x4c30
20 Summary 0.0.0.1 192.168.3.1 1.1.1.1 566 0x80000001 0x5c2b
21 Summary 0.0.0.1 192.168.3.2 1.1.1.1 560 0x80000001 0x5234
22 Summary 0.0.0.1 192.168.3.3 1.1.1.1 554 0x80000001 0x483d
23 -------------------------------------------------------------------------------
24 No. of LSAs: 15
25 ===============================================================================
26
27
28 A:R5# show router route-table
29
30 ===============================================================================
32 ===============================================================================
35 -------------------------------------------------------------------------------
36 <<ouput omitted>>
W e will configure route summariz ation on Area Border Router (R1), so it will advertise only one
summary route 192.168.3.0/30 instead of three specific routes.
Configuration steps:

2 A:R1>config>router>ospf>area# area-range 192.168.3.0/30
Pay attention, that summariz ation command area-range must be applied in the context of the
area being summariz ed. Since we are summariz ing routes from area 0 to area 1 then we using this
command in area 0 configuration context. By default, adding command area-range
<prefix>/<length> will actually place command area-range <prefix>/<length> advertise in the
configuration, meaning that ABR will advertise this prefix. Counterpart statement not-advertise is
used for route suppression and will be discussed in a detail in next section.
Pay attention: route summariz ation procedure automatically places black-hole route in R1’ s route-
table.
1 *A:R1# show router route-table 192.168.3.0/24 longer

2
3 ===============================================================================
5 ===============================================================================
8 -------------------------------------------------------------------------------
9 192.168.3.0/30 Blackh* OSPF 00h32m52s 255
10 Black Hole 100
11 192.168.3.1/32 Remote OSPF 00h53m58s 10
12 10.1.3.3 100
13 192.168.3.2/32 Remote OSPF 00h53m52s 10
14 10.1.3.3 100
15 192.168.3.3/32 Remote OSPF 00h53m47s 10
16 10.1.3.3 100
17 -------------------------------------------------------------------------------
18 No. of Routes: 4
Lets see what has changed at R5. R5’ s LSDB now has j ust one Type 3 Summary LSA regarding
network 192.168.3.0/30 and has no LSA’ s for specific networks:

2
3 ===============================================================================
5 ===============================================================================
7 -------------------------------------------------------------------------------
8 Router 0.0.0.1 1.1.1.1 1.1.1.1 1234 0x80000005 0x4eeb
9 Router 0.0.0.1 5.5.5.5 5.5.5.5 746 0x80000006 0x45bc
10 Summary 0.0.0.1 1.1.1.1 1.1.1.1 1199 0x80000003 0x1b38
11 Summary 0.0.0.1 2.2.2.2 1.1.1.1 658 0x80000003 0xd812
12 Summary 0.0.0.1 3.3.3.3 1.1.1.1 928 0x80000003 0xaa3c
13 Summary 0.0.0.1 4.4.4.4 1.1.1.1 1166 0x80000003 0x6816
14 Summary 0.0.0.1 6.6.6.6 1.1.1.1 1076 0x80000003 0xc6a
15 Summary 0.0.0.1 10.1.2.0 1.1.1.1 1026 0x80000004 0x8e56
16 Summary 0.0.0.1 10.1.3.0 1.1.1.1 735 0x80000004 0x8360
17 Summary 0.0.0.1 10.2.4.0 1.1.1.1 1216 0x80000004 0x5825
18 Summary 0.0.0.1 10.2.6.0 1.1.1.1 420 0x80000004 0x4239
19 Summary 0.0.0.1 10.3.4.0 1.1.1.1 340 0x80000005 0x4a31
20 Summary 0.0.0.1 192.168.3.0 1.1.1.1 4 0x80000001 0x5437
21 -------------------------------------------------------------------------------
V erifying that IP connectivity works for summariz ed route:
1 A:R5# ping 192.168.3.3

OSPF ROU TE FILTERING ON ABR
Y ou can filter unwanted routes on ABR’ s with the same command area-range adding the key
not-advertise .
For example lets take a look at R6 ’ s route table which contains specific routes to R3’ s loopback
addresses. These addresses is advertising by R2 since it is acting as ABR and advertises all the
routes it has in its routing table.
1 A:R6# show router route-table 192.168.3.0/24 longer

2
3 ===============================================================================
5 ===============================================================================
8 -------------------------------------------------------------------------------
9 192.168.3.1/32 Remote OSPF 01h21m48s 10
10 10.2.6.2 300
11 192.168.3.2/32 Remote OSPF 01h21m43s 10
12 10.2.6.2 300
13 192.168.3.3/32 Remote OSPF 01h21m37s 10
14 10.2.6.2 300
15 -------------------------------------------------------------------------------
16 No. of Routes: 3
If we want to prevent R2 from advertising some routes to its neighbor in Area 1 then we have to
make configuration steps in Area 0 context since we filter Area 0 routes:

2 A:R2>config>router>ospf>area# area-range 192.168.3.1/32 not-advertise
By doing this, we tell R2 to stop advertising Type 3 Summary LSA for prefix 192.168.3.1/32 . And
R6 ’ s route table immediately reflects this change by missing this specific route 192.168.3.1/32 :

2
3 ===============================================================================
5 ===============================================================================
8 -------------------------------------------------------------------------------
9 192.168.3.2/32 Remote OSPF 01h28m38s 10
10 10.2.6.2 300
11 192.168.3.3/32 Remote OSPF 01h28m32s 10
12 10.2.6.2 300
13 -------------------------------------------------------------------------------
14 No. of Routes: 2
Y ou can also use “ summary” prefix to filter a range of routes:
1 A:R2>config>router>ospf>area# area-range 192.168.3.0/30 not-advertise

2
3 # All loopback routes are filtered by R2
5
6 ===============================================================================
8 ===============================================================================
11 -------------------------------------------------------------------------------
12 -------------------------------------------------------------------------------
13 No. of Routes: 0
Note: Route filtering does not install any black-hole routes.
ASBR’ S AND OSPF ROU TE REDISTRIBU TION
Routes between different routing domains can me mutually exchanged. External routers can be
exported into OSPF and vice versa. The process of routes exchange is often called route
redistribution.
In this section we will redistribute routes added by means of loopback interfaces created on R5.
These routes are in R5’ s route table but are not advertising to OSPF neighbor, since these interfaces
are not included in OSPF process.
1 *A:R5# show router route-table 192.168.5.0/24 longer

2
3 ===============================================================================
5 ===============================================================================
8 -------------------------------------------------------------------------------
9 192.168.5.1/32 Local Local 00h00m14s 0
10 lo1 0
11 192.168.5.2/32 Local Local 00h00m09s 0
12 lo2 0
13 192.168.5.3/32 Local Local 00h00m05s 0
14 lo3 0
15 -------------------------------------------------------------------------------
16 No. of Routes: 3
17
18
19
21
22 ===============================================================================
24 ===============================================================================
26 -------------------------------------------------------------------------------
27 system 0.0.0.1 5.5.5.5 0.0.0.0 Up DR
28 toR1 0.0.0.1 0.0.0.0 0.0.0.0 Up PToP
29 -------------------------------------------------------------------------------
To redistribute these local routes to OSPF process a policy should be configured. Lets configure
policy with a name EXPORT Local Loopbacks :
1 *A:R5# configure router policy-options

2
3 # enter policy-options edit mode by using "begin" statement
4 *A:R5>config>router>policy-options# begin
5
6 # create prefix list to match desired routes
7 *A:R5>config>router>policy-options# prefix-list "Loopbacks_to_export"
8 *A:R5>config>router>policy-options>prefix-list$ prefix 192.168.5.0/24 longer
9 *A:R5>config>router>policy-options>prefix-list$ back
10
11 # create policy statement to export routes
12 *A:R5>config>router>policy-options# policy-statement "EXPORT Local Loopbacks"
13 *A:R5>config>router>policy-options>policy-statement$ entry 10
14 # apply prefix-list rule as a "from" statement
15 *A:R5>config>router>policy-options>policy-statement>entry$ from prefix-list "Loopbacks_to_export"
16 # narrow the use scope of this policy applying "to protocol ospf" statement
17 *A:R5>config>router>policy-options>policy-statement>entry$ to protocol ospf
18
19 # set accept action (default action is deny all)
20 *A:R5>config>router>policy-options>policy-statement>entry# action accept
21 *A:R5>config>router>policy-options>policy-statement>entry>action# back
22 *A:R5>config>router>policy-options>policy-statement>entry$ back
23 *A:R5>config>router>policy-options>policy-statement$ back
24
25 # type commit to apply changes
26 *A:R5>config>router>policy-options# commit
27
The next step is to configure R5 as an ASBR router and to apply created policy to OSPF process:
1 # it is necessary to issue command "asbr" to make a router an ASBR

2
3 *A:R5# configure router ospf
4 *A:R5>config>router>ospf# asbr
5 *A:R5>config>router>ospf# export "EXPORT Local Loopbacks"
V erifying redistributed routes propagation

Now these routes get exported to OSPF process on R5. Moreover, R5 is now configured as ASBR.
These changes allow other routers in OSPF domain to receive these routes via Type 4 ASBR
Summary LSA and Type 5 AS External LSA:
R5 R1 R3 R6
1 *A:R5# show router ospf database

2
3 ===============================================================================
5 ===============================================================================
7 -------------------------------------------------------------------------------
8 Router 0.0.0.1 1.1.1.1 1.1.1.1 1033 0x80000004 0x50ea
9 Router 0.0.0.1 5.5.5.5 5.5.5.5 1072 0x80000006 0x4bb4
10 Summary 0.0.0.1 1.1.1.1 1.1.1.1 706 0x80000004 0x1939
11 Summary 0.0.0.1 2.2.2.2 1.1.1.1 2226 0x80000002 0xda11
12 Summary 0.0.0.1 3.3.3.3 1.1.1.1 107 0x80000003 0xaa3c
13 Summary 0.0.0.1 4.4.4.4 1.1.1.1 929 0x80000003 0x6816
14 Summary 0.0.0.1 6.6.6.6 1.1.1.1 1879 0x80000002 0xe69
15 Summary 0.0.0.1 10.1.2.0 1.1.1.1 366 0x80000003 0x9055
16 Summary 0.0.0.1 10.1.3.0 1.1.1.1 472 0x80000003 0x855f
17 Summary 0.0.0.1 10.2.4.0 1.1.1.1 737 0x80000003 0x5a24
18 Summary 0.0.0.1 10.2.6.0 1.1.1.1 939 0x80000003 0x4438
19 Summary 0.0.0.1 10.3.4.0 1.1.1.1 442 0x80000003 0x4e2f
20 Summary 0.0.0.1 192.168.3.0 1.1.1.1 355 0x80000003 0x5039
21 AS Ext n/a 192.168.5.1 5.5.5.5 506 0x80000001 0x63ea
22 AS Ext n/a 192.168.5.2 5.5.5.5 506 0x80000001 0x59f3
23 AS Ext n/a 192.168.5.3 5.5.5.5 506 0x80000001 0x4ffc
24 -------------------------------------------------------------------------------
25 No. of LSAs: 16
26 ===============================================================================
OSPF STU B AREA
Stub areas are widely used since they help to optimiz e LSDB and routing tables of the routers. W e
will configure Area 2 as stub, this will tell ABR (R2) to not distribute any External routes and send a
default route instead into Area 2. To configure Area 2 as stub you need to configure all OSPF
routers inside this area:
1 # on R2 (ABR)
2 A:R2# configure router ospf
3 A:R2>config>router>ospf# area 2 stub
4
5
6 # on R6 (Area 2 router)
7 A:R6# configure router ospf area 2 stub
This “ before | after” comparison shows that after configuring Area 2’ s routers as stub R6 router no
longer receives ASBR Summary LSA and AS External LSA nor it has routes 19 2.16 8 .5.1-3/32.
Instead it has a new Summary LSA from ABR with the Link State ID 0.0.0.0 which means default
route.
R6 before stub area R6 after stub area

2
3 ===============================================================================
5 ===============================================================================
7 -------------------------------------------------------------------------------
8 Router 0.0.0.2 2.2.2.2 2.2.2.2 432 0x80000004 0x76b3
9 Router 0.0.0.2 6.6.6.6 6.6.6.6 1309 0x80000006 0xf9f2
10 Summary 0.0.0.2 1.1.1.1 2.2.2.2 535 0x80000003 0xe802
11 Summary 0.0.0.2 2.2.2.2 2.2.2.2 1098 0x80000004 0xcc7d
12 Summary 0.0.0.2 3.3.3.3 2.2.2.2 524 0x80000003 0x7806
13 Summary 0.0.0.2 4.4.4.4 2.2.2.2 1427 0x80000003 0x5e80
14 Summary 0.0.0.2 5.5.5.5 2.2.2.2 471 0x80000003 0x1c5a
15 Summary 0.0.0.2 10.1.2.0 2.2.2.2 661 0x80000003 0x726f
16 Summary 0.0.0.2 10.1.3.0 2.2.2.2 85 0x80000003 0x5329
17 Summary 0.0.0.2 10.1.5.0 2.2.2.2 200 0x80000003 0x3d3d
18 Summary 0.0.0.2 10.2.4.0 2.2.2.2 58 0x80000003 0x508e
19 Summary 0.0.0.2 10.3.4.0 2.2.2.2 549 0x80000003 0x3049
20 AS Summ 0.0.0.2 5.5.5.5 2.2.2.2 1460 0x80000001 0x1265
21 AS Ext n/a 192.168.5.1 5.5.5.5 899 0x80000001 0x63ea
22 AS Ext n/a 192.168.5.2 5.5.5.5 899 0x80000001 0x59f3
23 AS Ext n/a 192.168.5.3 5.5.5.5 899 0x80000001 0x4ffc
OSPF TOTALLY STU B AREA
ABR router participating in a Totally stub area blocks not only Type 4 ASBR Summary and Type 5 AS
External LSA but also Type 3 Summary LSA. This drastically reduces LSDB and route tables on Area
2 routers. As of this moment we have Area 2 configured as stub area, lets configure it to be totally
stub. To make Area 2 totally stub we need to configure j ust ABR (R2) with keyword no summaries
1 *A:R2# configure router ospf area 2 stub no summaries
Take a look at R6 ’ s LSDB and route table

2
3 ===============================================================================
5 ===============================================================================
7 -------------------------------------------------------------------------------
8 Router 0.0.0.2 2.2.2.2 2.2.2.2 482 0x80000004 0x9497
9 Router 0.0.0.2 6.6.6.6 6.6.6.6 518 0x80000004 0x1cd4
10 Summary 0.0.0.2 0.0.0.0 2.2.2.2 222 0x80000007 0x4b05
11 -------------------------------------------------------------------------------
12 No. of LSAs: 3
13 ===============================================================================
14
15
16
17
18 *A:R6# show router route-table
19
20 ===============================================================================
22 ===============================================================================
25 -------------------------------------------------------------------------------
26 0.0.0.0/0 Remote OSPF 00h02m16s 10
27 10.2.6.2 101
28 6.6.6.6/32 Local Local 02h11m29s 0
29 system 0
30 10.2.6.0/24 Local Local 02h11m07s 0
31 toR2 0
32 -------------------------------------------------------------------------------
33 No. of Routes: 3
Now Area 2 router R6 has only 3 LSA in its LSDB. All Type 3 Summary LSA for networks inside Area
0 was substituted by Summary default route from ABR (R2).
NOT SO STABBY AREA (NSSA)
There is a typo on the pic. No type4 lsa will be advertised in Area0 by R1. Only Type5
Not so stabby areas are basically stub areas with ASBR. It inherits the same rule of blocking Type 4
and Type 5 LSA and in order to distribute external routes from ASBR another LSA – Type 7 – is used.
W e will configure Area 1 to be NSSA by adding commands to R1 (ABR) at first:
1 # prior to configuring NSSA on R5 lets check that we have active neighbor - R1

2
3 A:R5# show router ospf neighbor
4
5 ===============================================================================
7 ===============================================================================
9 Area-Id
10 -------------------------------------------------------------------------------
11 toR1 1.1.1.1 Full 1 0 35
12 0.0.0.1
13 -------------------------------------------------------------------------------
15 ===============================================================================
16
17 #configuring Area 1 on R5 to NSSA state
18
19 A:R5# configure router ospf area 1 nssa
20
21
22 # Re-check neighbor status
23
24 *A:R5# show router ospf neighbor
25
26 ===============================================================================
As soon we configured Area 1 on R5 to be NSSA we lost R1 as neighbor. This is the effect of

mismatched Area type in OSPF H ello messages between two routers. Recall that R1 is maintaining
Area 1 as a basic area, and Area 1 on R5 was reconfigured to NSSA.
W e will fix neighboring by moving R1’ s Area 1 to NSSA operation as well:
1 A:R1# configure router ospf area 1 nssa

2
3
4 # Now check neighboring one more time
5
6 *A:R1# show router ospf neighbor "toR5"
7
8 ===============================================================================
9 OSPFv2 (0) neighbors for interface "toR5"
10 ===============================================================================
12 Area-Id
13 -------------------------------------------------------------------------------
14 toR5 5.5.5.5 Full 1 0 33
15 0.0.0.1
16 -------------------------------------------------------------------------------
Now when R1 and R5 are neighbors again lets see what has changed:
R5' s R5' s LSDB after NSSA

2
3 ===============================================================================
5 ===============================================================================
7 -------------------------------------------------------------------------------
8 Router 0.0.0.1 1.1.1.1 1.1.1.1 1911 0x80000004 0x50ea
9 Router 0.0.0.1 5.5.5.5 5.5.5.5 1690 0x80000006 0x4bb4
10 Summary 0.0.0.1 1.1.1.1 1.1.1.1 2160 0x80000004 0x1939
11 Summary 0.0.0.1 2.2.2.2 1.1.1.1 2145 0x80000003 0xd812
12 Summary 0.0.0.1 3.3.3.3 1.1.1.1 1697 0x80000003 0xaa3c
13 Summary 0.0.0.1 4.4.4.4 1.1.1.1 669 0x80000004 0x6617
14 Summary 0.0.0.1 6.6.6.6 1.1.1.1 1529 0x80000003 0xc6a
15 Summary 0.0.0.1 10.1.2.0 1.1.1.1 997 0x80000003 0x9055
16 Summary 0.0.0.1 10.1.3.0 1.1.1.1 142 0x80000004 0x8360
17 Summary 0.0.0.1 10.2.4.0 1.1.1.1 1824 0x80000003 0x5a24
18 Summary 0.0.0.1 10.2.6.0 1.1.1.1 2092 0x80000003 0x4438
19 Summary 0.0.0.1 10.3.4.0 1.1.1.1 459 0x80000004 0x4c30
20 Summary 0.0.0.1 192.168.3.0 1.1.1.1 1824 0x80000003 0x5039
21 AS Ext n/a 192.168.5.1 5.5.5.5 1369 0x80000003 0x5fec
22 AS Ext n/a 192.168.5.2 5.5.5.5 1491 0x80000003 0x55f5
23 AS Ext n/a 192.168.5.3 5.5.5.5 934 0x80000003 0x4bfe
24 -------------------------------------------------------------------------------
25 No. of LSAs: 16
26 ===============================================================================
As we see, all Type 5 AS External LSA was substituted by Type 7 NSSA LSA. And if we had any other
external routes we wouldnt see them in R5 database, since NSSA areas can not contain External
routes.
TOTALLY NSSA
There is a typo on the pic. No type4 lsa will be advertised in Area0 by R1. Only Type5
As with totally stubby areas, NSSA could be configured in a way that no Type 3 Summary LSA will
present in such area. Totally NSSA configuration adds two additional commands on ABR:
on R1 (ABR) on R5
1 *A:R1>config>router>ospf>area# info
2 ----------------------------------------------
3 nssa
4 exit
5 interface "toR5"
6 interface-type point-to-point
7 no shutdown
8 exit
9 ----------------------------------------------
10
11 # Configuring NSSA to be totally NSSA
12 *A:R1>config>router>ospf>area# nssa no summaries
ABR configured with Totally NSSA area filter Type 3 LSA as totally stubby area does. But notice one
maj or difference – there is no default route inj ected by ABR! This is the cause of ping failure to any
Area 0 address:
1 *A:R5# ping 4.4.4.4

3 No route to destination. Address: 4.4.4.4, Router: Base
To resolve this issue you should add another command to NSSA context:
1 *A:R1>config>router>ospf>area# nssa originate-default-route
This will cause R1 to inj ect Type 3 Summary LSA in Area 1:

2
3 ===============================================================================
5 ===============================================================================
7 -------------------------------------------------------------------------------
8 Router 0.0.0.1 1.1.1.1 1.1.1.1 1652 0x80000003 0xa685
9 Router 0.0.0.1 5.5.5.5 5.5.5.5 264 0x80000006 0x6998
10 Summary 0.0.0.1 0.0.0.0 1.1.1.1 53 0x80000001 0x75e4
11 NSSA 0.0.0.1 192.168.5.1 5.5.5.5 172 0x80000003 0xe34c
12 NSSA 0.0.0.1 192.168.5.2 5.5.5.5 1199 0x80000002 0xdb54
13 NSSA 0.0.0.1 192.168.5.3 5.5.5.5 1163 0x80000002 0xd15d
14 -------------------------------------------------------------------------------
15 No. of LSAs: 6
16 ===============================================================================
17
18
19 *A:R5# ping 4.4.4.4
DEBU GGING OSPF ADJ ACENCY ISSU ES
For two OSPF routers to become neighbors several parameters should be matched. And most of
them – are the parametes communicated via OSPF H ello messages. If you do not see the a neighbor
on the other side – there is a good chance that one of these parameters mismatch.
W hen you need to investigate what is the reason casing a neighboring relationships to break down
debug should help. I will show you some debug commands to help you understand how to
troubleshoot OSPF H ello mismatched parameters.
For some reason R1 lost its neighbor R5 in Area 1:
1 *A:R1# show router ospf neighbor "toR5"

2
3 ===============================================================================
4 OSPFv2 (0) neighbors for interface "toR5"
5 ===============================================================================
7 Area-Id
8 -------------------------------------------------------------------------------
9 -------------------------------------------------------------------------------
11 ===============================================================================
To see what is going wrong, lets create logging instance and capture H ello packets to analyz e
their content:
1 # Creating log #55

2 *A:R1# configure log log-id 55
3
4 # Configuring capture log messages from debug to memory
5 *A:R1>config>log>log-id$ from debug-trace
6 *A:R1>config>log>log-id$ to memory
7
8
9 # Specifying what "debug" should process. We are hunting OSPF Hello packets
10 # adding "detail" to see more verbose output
11
12 *A:R1# debug router ospf packet hello detail
Now we have log and debug configured, we could see log contents:
1 *A:R1# show log log-id 55

2
3 ===============================================================================
4 Event Log 55
5 ===============================================================================
6 Description : (Not Specified)
7 Memory Log contents [size=100 next event=22 (not wrapped)]
8
9 20 2015/01/01 03:11:31.28 UTC MINOR: DEBUG #2001 Base OSPFv2
10 "OSPFv2: PKT DROPPED
11 hello interval mismatch"
12
13 19 2015/01/01 03:11:31.28 UTC MINOR: DEBUG #2001 Base OSPFv2
14 "OSPFv2: PKT
15
16 >> Incoming OSPF packet on I/F toR5 area 0.0.0.1
17 OSPF Version : 2
18 Router Id : 5.5.5.5
19 Area Id : 0.0.0.1
20 Checksum : ec98
21 Auth Type : Null
22 Auth Key : 00 00 00 00 00 00 00 00
23 Packet Type : HELLO
24 Packet Length : 44
25
Now the problem is clear – incoming OSPF packet came in with H ello timer set to 5sec. And R1 tells
us that this value mismatches its configured H ello timer value.
This debug technique should indicate every discrepancy in OSPF values that should match, be it
authentication mismatch or area id mismatch.
And that is all for this moment. Should you have any questions – do not hesitate, comment form is
down below!
noshut# exit all
About Latest Posts
Roman Dodin
Network engineer at Nokia
Eagerness to learn multiplied by passion to share.

Y ou can reach me at LinkedIn
1 Comment noshut 
1 Login
 Recommend 1 ⤤ Share Sort by Oldest
Join the discussion…
LOG IN WITH OR SIGN UP WITH DISQUS ?
Name
nani • 10 months ago

Hello .. Thanks for writing wonderful article..
Can we use aggregate routes with OSPF, for eg on ASBR, can I write an aggregate
summary-only and redistribute it into OSPF with export policy.
It does work but I see both aggregate route and also specific routes via OSPF.
Am I missing something ?
1 • Reply • Share ›
NOSHUT
Nokia (Alcatel-Lucent) BGP configuration OSPF. Neighbors on a “point-to-

tutorial. Part 2 – … broadcast” network
• •
— amazing Roman !!, can't wait — Thanks, Dmitry, useful info!
for Part 3.
How to run Juniper vMX in UNetLab How to get rid of VNC and use telnet
• access for your Linux image?
— Here below some •
additional outputs :admin@P3# run show — Для 16.04 (and higher) етот метод
interfaces em2 | grep Current … не работает, там нужно всего лишь
поменять некоторые строки …
✉ Subscribe d Add Disqus to your siteAdd DisqusAdd Privacy

Nokia (Alcatel-Lucent) OSPF Configuration Tutorial

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Nokia (Alcatel-Lucent) OSPF Configuration Tutorial

Încărcat de

Drepturi de autor:

Formate disponibile

Nokia (Alcatel-Lucent) OSPF configuration tutorial | Networking in a Service Provider ...

Nokia (Alcatel-Lucent) OSPF configuration tutorial

• Enable OSPF globally

Enabling OSPF and Router ID

ID selection process goes like this (in priority order):

• configured globally for a router router-id value

1 # configuring router-id explicitly

router ospf status

1 *A:R1# show router ospf status

Configuring Backbone Area

1 A:R1# show router ospf area

Configuring OSPF interfaces

1 # Entering to OSPF Area 0 configuration context

1 *A:R1# show router ospf interface

1 A:R1# show router ospf neighbor

1 A:R1# show router ospf database

1 # Creating Area 1 on R5 and adding "system" and "toR1" interfaces

1 *A:R5# show router ospf neighbor

I repeated same configuration steps on R6 : added it to Area 2 and neighbored with R2.

Examining Multi-area LSDB

1 A:R1# show router ospf database

V erifying OSPF routes propagation

1 # Checking routes that have been received via OSPF

1 A:R6# ping 5.5.5.5

OSPF ROU TE SU MMARIZ ATION

R3 router and include them in OSPF Area 0:

1 :R3# show router interface

1 A:R5# show router ospf database

1 A:R1# configure router ospf area 0

1 *A:R1# show router route-table 192.168.3.0/24 longer

1 A:R5# show router ospf database

V erifying that IP connectivity works for summariz ed route:

1 A:R5# ping 192.168.3.3

OSPF ROU TE FILTERING ON ABR

1 A:R6# show router route-table 192.168.3.0/24 longer

1 A:R2# configure router ospf area 0

1 A:R6# show router route-table 192.168.3.0/24 longer

Y ou can also use “ summary” prefix to filter a range of routes:

1 A:R2>config>router>ospf>area# area-range 192.168.3.0/30 not-advertise

Note: Route filtering does not install any black-hole routes.

ASBR’ S AND OSPF ROU TE REDISTRIBU TION

1 *A:R5# show router route-table 192.168.5.0/24 longer

1 *A:R5# configure router policy-options

1 # it is necessary to issue command "asbr" to make a router an ASBR

V erifying redistributed routes propagation

1 *A:R5# show router ospf database

OSPF STU B AREA

R6 before stub area R6 after stub area

1 A:R6# show router ospf database

OSPF TOTALLY STU B AREA

1 *A:R2# configure router ospf area 2 stub no summaries

Take a look at R6 ’ s LSDB and route table

1 *A:R6# show router ospf database

NOT SO STABBY AREA (NSSA)

W e will configure Area 1 to be NSSA by adding commands to R1 (ABR) at first:

1 # prior to configuring NSSA on R5 lets check that we have active neighbor - R1

As soon we configured Area 1 on R5 to be NSSA we lost R1 as neighbor. This is the effect of

W e will fix neighboring by moving R1’ s Area 1 to NSSA operation as well:

1 A:R1# configure router ospf area 1 nssa

R5' s R5' s LSDB after NSSA

1 A:R5# show router ospf database

1 *A:R5# ping 4.4.4.4

1 *A:R1>config>router>ospf>area# nssa originate-default-route