Dell Force10

OSPF Configuration
Module 8

Objectives

Review OSPF Protocol

Implement OSPF in FTOS
Identify Basic Configuration
Commands
Perform Graceful Restart
Comparisons with Cisco
Troubleshooting Overview

8-2

OSPF Review
OSPF Autonomous System
OSPF AREA 0
LSDB-A0
-------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---

DR

BDR

OSPF AREA 1
(NSSA)

Network 10

ODR

LSDB-A1
-------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---

DR
ODR

Network 20
BDR

BGP
Autonomous
System

ODR

LSDB-A2
-------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---

OSPF AREA 2

OSPF AREA 3 (STUB)

LSDB-A3
-------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---

8-3

OSPF Concepts
Link State Database (LSDB)

Router ID

Area
Backbone (Area 0)
Normal
Stub

Hello Packets

Stub no summaries

Link State Advertisements

Types 1,2,3,4,5,7,9

Not So Stubby

Link State Updates

NSSA no summaries
Router Types
Internal Router
Area Border Router (ABR)
Autonomous System Boundary
Router (ASBR)
Virtual Links

8-4

Form adjacencies (Hellos)

Maintain adjacencies (keepalives)

Interface States
Designated Router (DR )
Backup Designated Router (BDR)
Other Designated Router (DR
other)

Link State Advertisement (LSA)

Are transmitted by every OSPF router when neighbor adjacency is
established
LSAs vary according to Link State Types and router function/s
Describes a routers local piece of the routing topology that it is responsible
for
A routers self-originating LSA is re-transmitted every 30 minutes
even in the absence of any change, in the event the LSA information may
have been lost or corrupted in a neighbor routers tables.
Stored in the routers link state database (LSDB)

8-5

Whats in an OSPF Network? - LSA

Overview
LSA
Type

What is it?

What will see it?

What sends
it?

Link State ID
Field Entry

What does it provide?

Router-LSA

All OSPF Routers

within an Area

All Routers

Originating
Routers ID

A Routers Links
(Neighbor Info.)

Network-LSA

All OSPF Routers

within an Area

Designated
Routers

DRs Router
Interface (IP
Address)

Information of Networks
present in an Area (all
routers attached to that
network)

Summary-LSA
(IP Network)

All OSPF Routers in

the AS

ABR

IP Network
Address of the
Network being
advertised

IP Networks from other

Areas in the AS

Summary LSA
(ASBRs)

All OSPF Routers in

the AS

ABR

Router ID of
ASBR
connected to
an External AS

Existence of ASBRs

AS External
LSA

All OSPF Routers in

the AS except those
in STUB or NSSA
Areas

ASBR or the
ABRs in an
NSSA

External AS IP
Network
Address

Reachable networks that

are external to the AS

NSSA External
LSA

All OSPF Routers in

an NSSA Area

ABRs in an
NSSA

External AS IP
Network
Address

Reachable networks that

are external to the AS

8-6

OSPF Implementation in FTOS

Up to 32 OSPF instances runs in RP1
Supported LSA types: 1-5,7,9
Supported Protocol Features (FCS)
Stub and Not-So-Stubby Areas
Does FTOS support Totally Stubby and Totally Not-So-Stubby Areas?
Virtual Links
MD5 authentication
Route redistribution
Graceful restart (RFC 3623)
Authentication change wait time
Scales up to 1,000 neighbors and 10,000 routes (8,000 external and
2,000 internal)

8-7

Basic OSPF Configuration Steps

1. Configure an IP address on an interface
2. Enable OSPF process
Force10(conf)# router ospf process-id
3. Specify network and the area it belongs in
Force10(conf-router_ospf)# network ip-address standardmask area area-id

4.

Configure Router ID (optional)

Force10(conf-router_ospf)# Router-ID 4-octet-number

5.

Configure stub areas from the ROUTER OSPF mode (optional)

Force10(conf-router_ospf)# area area-id nssa|stub [nosummary]

6. Configure any other process parameters from the ROUTER OSPF mode
(optional)
Force10(conf-router_ospf)# passive-interface {default |
interface}

8-8

Confidential

Interface Specific OSPF

Configuration Commands
Configure OSPF interface parameters from the INTERFACE mode
Force10(conf-gi-x/y)# ip ospf auth-change-wait-time
seconds
Force10(conf-gi-x/y)# ip ospf authentication-key key
Force10(conf-gi-x/y)# ip ospf message-digest-key keyid
md5 key
Force10(conf-gi-x/y)# ip ospf cost cost
Force10(conf-gi-x/y)# ip ospf priority number
Force10(conf-gi-x/y)# ip ospf dead-interval seconds
Force10(conf-gi-x/y)# ip ospf hello-interval seconds
Force10(conf-gi-x/y)# ip ospf retransmit-interval seconds
Force10(conf-gi-x/y)# ip ospf transmit-delay seconds

8-9

OSPF Authentication Options

FTOS supports 2 types of OSPF authentication
Simple
MD5

Authentication Time Change

Enables period after password is changed
Router accepts both the old and new password to maintain adjacency
ip ospf auth-change-wait-time 100
interface GigabitEthernet 1/4
ip address 192.168.250.2/24
ip ospf auth-change-wait-time 100
ip ospf authentication-key 7 387a7f2df5969da4
no shutdown

Simple Authentication

MD5 Authentication
interface GigabitEthernet 0/4
ip address 192.168.250.1/24
ip ospf auth-change-wait-time 100
ip ospf message-digest-key 1 md5 7 387a7f2df5969da4
no shutdown

8-10

OSPF Graceful Restart Feature

Graceful restart or non-stop forwarding
Database synchronization maintained between neighbors during failover
Accomplished by not re-issuing the LSAs
Need to announce grace period for hitless feature during failover
Neighbors keep the same state of the failover router, during the grace
period
Common shutdown procedures are not performed on the failover router

Link State Database state are maintained on other routers.

Forwarding Information Base tables will be up to date on the failover router
Failover router will continue normal operation after graceful restart
S-Series supports helper role only

8-11

Tools to Verify OSPF

Show ip ospf neighbor
Show ip ospf database
Show ip ospf route
Show interface

Show protocols
Debug IP OSPF event
Debug IP OSPF packet
Ping

8-12

OSPF Neighbor Command

Use the show <ip ospf neighbor> command to verify neighbors in
the same or remote areas have formed
Neighbors in the Full state are exchanging database updates

A0(conf)# do show ip ospf neighbor

Neighbor ID
192.168.1.11
192.168.1.12
192.168.2.10
192.168.3.10

Pri
1
1
1
1

State
Dead Time
FULL/BDR 00:00:39
FULL/BDR 00:00:35
FULL/DR
00:00:38
FULL/BDR 00:00:36

Address
Interface
10.11.1.11 Gi 0/1
10.11.2.12 Gi 0/2
10.12.12.20 Gi 0/12
10.13.13.30 Gi 0/13

Area
1
1
0
0

8-13

OSPF Database Command

Issue the command <show ip ospf database> command to view
the Link State Database where LSAs are used to popular the database

A1(conf-router_ospf-1)# do show ip ospf database

OSPF Router with ID (192.168.1.11) (Process ID 1)
Router (Area 1)
Link ID
192.168.1.10
192.168.1.11
192.168.1.12

ADV Router
192.168.1.10
192.168.1.11
192.168.1.12

Age
919
929
916

Seq#
Checksum Link count
0x8000000c 0xa4a2
3
0x8000000a 0xc965
3
0x80000009 0x31f7
3

Network (Area 1)
Link ID
10.11.1.10
10.11.2.10
10.11.12.11

8-14

ADV Router
192.168.1.10
192.168.1.10
192.168.1.11

Age
997
919
929

Seq#
0x80000003
0x80000003
0x80000003

Checksum
0x7860
0x7b5b
0x07c2

OSPF Routes
Step 9
Issue the command <show ip route>
Observe which routes are being learned via OSPF.

A1(conf-router_ospf-1)# do show ip route

Codes: C - connected, S - static, R - RIP,
B - BGP, IN - internal BGP, EX - external BGP,LO - Locally
Originated,
O - OSPF, IA - OSPF inter area, N1 - OSPF NSSA external type 1,
N2 - OSPF NSSA external type 2, E1 - OSPF external type 1,
E2 - OSPF external type 2, i - IS-IS, L1 - IS-IS level-1,
L2 - IS-IS level-2, IA - IS-IS inter area, * - candidate
default,
> - non-active route, + - summary route
Gateway of last resort is not set
Destination
----------C 10.11.1.0/24
O 10.11.2.0/24

Gateway
Dist/Metric
----------------Direct, Gi 0/1
0/0
via 10.11.1.10, Gi 0/1
110/2
via 10.11.12.12, Gi 0/12
C 10.11.12.0/24
Direct, Gi 0/12
0/0
O 192.168.1.10/32 via 10.11.1.10, Gi 0/1
110/2
C 192.168.1.11/32 Direct, Lo 0
0/0
O 192.168.1.12/32 via 10.11.12.12, Gi 0/12 110/2

Last Change
----------01:06:51
00:55:34
01:05:23
00:56:44
01:07:37
00:55:34

8-15

OSPF Show Commands

Force10# show ip ospf interface gigabitethernet 3/5

GigabitEthernet 3/5 is up, line protocol is up

Internet Address 3.3.3.1/24, Area 0
Process ID 1, Router ID 100.1.1.1, Network Type BROADCAST, Cost: 1
Transmit Delay is 1 sec, State BDR, Priority 1
Designated Router (ID) 192.168.1.1, Interface address 3.3.3.2
Backup Designated Router (ID) 100.1.1.1, Interface address 3.3.3.1
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
Hello due in 00:00:10
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 192.168.1.1 (Designated Router)
Force10# show ip os neighbor
Neighbor ID
Pri
State
192.168.1.1
1
FULL/DR

Dead Time Address

00:00:33 3.3.3.2

Interface Area
Gi 3/5
0

Force10# show ip ospf virtual-links

Virtual Link to router 192.168.253.24 is up
Transit area 10.10.10.10, Cost of using 11
Transmit Delay is 1 sec, State UP
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5

8-16

OSPF Neighbor State Changes

Force10# debug ip ospf event
13:19:20 : OSPF(1:00):
Nbr. rid:192.168.1.1 in aid:0 intf:Gi 3/5
13:19:20 : OSPF(1:00):
Nbr. rid:192.168.1.1 in aid:0 intf:Gi 3/5
13:19:20 : OSPF(1:00):
Nbr. rid:192.168.1.1 in aid:0 intf:Gi 3/5
13:19:21 : OSPF(1:00):
Nbr. rid:192.168.1.1 in aid:0 intf:Gi 3/5
EXSTART
13:19:21 : OSPF(1:00):
Elect. aid:0 intf:Gi 3/5
Elect DR 3.3.3.2, BDR 3.3.3.1
13:19:25 : OSPF(1:00):
Nbr. rid:192.168.1.1 in aid:0 intf:Gi 3/5
13:19:25 : OSPF(1:00):
Nbr. rid:192.168.1.1 in aid:0 intf:Gi 3/5
EXCHANGE
13:19:25 : OSPF(1:00):
Nbr. rid:192.168.1.1 in aid:0 intf:Gi 3/5
LOADING
13:19:26 : OSPF(1:00):
Nbr. rid:192.168.1.1 in aid:0 intf:Gi 3/5
FULL

Neighbor state change from NULL to DOWN

Neighbor state change from DOWN to INIT
Neighbor state change from INIT to 2WAY
Neighbor state change from 2WAY to

We are SLAVE
Neighbor state change from EXSTART to
Neighbor state change from EXCHANGE to
Neighbor state change from LOADING to

8-17

OSPF Troubleshooting
Force10# debug ip ospf packet
OSPF packet debugging is on
13:15:30 : OSPF(1:00):
Xmt. v:2 t:1(HELLO) l:48 rid:100.1.1.1
aid:0 chk:0x89e5 aut:0 auk: keyid:0 to:Gi 3/5 dst:224.0.0.5
netmask:255.255.255.0 pri:1 N-, MC-, E+, T-,
hi:10 di:40 dr:3.3.3.2 bdr:3.3.3.1
Nbr: 192.168.1.1
13:15:33 : OSPF(1:00):
Rcv. v:2 t:1(HELLO) l:48 rid:192.168.1.1
aid:0 chk:0x89e5 aut:0 auk: keyid:0 from:Gi 3/5
netmask:255.255.255.0 pri:1 N-, MC-, E+, T-,
hi:10 di:40 dr:3.3.3.2 bdr:3.3.3.1
Nbr: 100.1.1.1
Force10# debug ip ospf spf
OSPF spf debugging is on
Force10OSPF(1:00): HEADLINE: del_vx_rte. pfx:172.16.0.0 mask:255.255.255.0 Nh:192.168.254.1
OSPF(1:00): HEADLINE: ospfAddRoute. pfx:172.16.0.0 mask:255.255.255.0 Nh1:192.168.254.1
OSPF(1:00): HEADLINE:
type:3(STNET) level:1 aid:0.0.0.0 #Nh:1 cost:2 cost2:0 tag:0
OSPF(1:00): HEADLINE: add_vx_rte. pfx:172.16.0.0 mask:255.255.255.0 Nh:192.168.254.1

8-18

OSPF Troubleshooting
OSPF process not active on router
Valid interface
OSPF adjacency not established with DR/BDR
Verify ip address and subnet configuration on the interface matches the
neighbors configuration
Verify physical connectivity to the network
Verify if OSPF authentication is used on the neighboring router, that the
authentication type and keys match on the two routers
Verify MTU matches on the two routers interfaces
On Ethernet interface, is OSPF configured as broadcast?
Are there any access-lists on the interface that drop OSPF protocol
packets? OSPF hello packets have a destination address of 224.0.0.5
Verify router is in correct area type (stub, nssa)

8-19

Routes in LSDB, not Injected in Routing

Table
Frequently because the advertising router is not reachable in OSPF
Verify there is no network type mismatch between the local and
remote interfaces

Verify IP addresses match, between the local and remote interfaces

Verify the subnet configured on the local and remote interfaces
match
Verify forwarding address is not learned via an external route

8-20

Confidential

OSPF Routes not Injected into the LSDB

Use OSPF Debug to decipher OSPF packets received by the router.
%OSPF-4-ERRRCV error message indicates that an OSPF router has received
an invalid OSPF packet. This can be caused by
OSPF area mismatch
OSPF not enabled in the interface
Invalid type
Bad link-state update advertisement count
Bad link-state update length

8-21

Module
Summary

In this module we learned:

Review OSPF Protocol
Implement OSPF in FTOS
Identify Basic Configuration
Commands
Perform Graceful Restart
Comparisons with Cisco
Troubleshooting Overview

8-22