Solved: OSPF in NBMA network

feroz syed · ‎06-05-2013

Hi,

I am running ospf in hub and spoke scenario all frame maps are active and can ping each other, now problem is can’t see any ospf neighbor relations with other routers all three routers are in same subnet and in same area and also checked the hello and dead timer are equal.

kcnajaf · ‎06-05-2013

Hi Feroz,

I hope you are missing neighbor command on R1.

router ospf 1

neighbor 172.12.123.2

neighbor 172.12.123.3

Hope that helps

Regards

Najaf

Please rate when applicable or helpful !!!

View solution in original post

Jose Jara · ‎06-05-2013

Hi Feroz,

you have different options in NBMA. However, if the network type is non-broadcast, it's mandatory to use neighbor statements as the communication is unicast. The use of priority 0 is to prevent that spokes will not participate in the DR/BDR election process.

Other option is to use point-to-multipoint network ospf network type. Here, you do not need to change priority because there is no DR/BDR and also you do not need neighbor statements. However, you need to add the broadcast keyword in the frame map statements between the Hub and Spokes as the communication is multicast - 224.0.0.5.

Hope this helps,

Jose.

View solution in original post

Akash Agrawal · ‎06-05-2013

Hi Feroz,

You need to ensure that router is sending hellos or not, If it is sending hello other device is accepting it or not.

"show ip ospf interface " can tell you if you are sending hello out of this interface or not.

for NBMA network , you need to define neighbor with command "neighbor under ospf process

Router1# show ip ospf interface ethernet 0
Ethernet0 is up, line protocol is up 
  Internet Address 10.10.10.1/24, Area 0 
  Process ID 1, Router ID 192.168.45.1, Network Type BROADCAST, Cost: 10
  Transmit Delay is 1 sec, State BDR, Priority 1 
  Designated Router (ID) 172.16.10.1, Interface address 10.10.10.2
  Backup Designated router (ID) 192.168.45.1, Interface address 10.10.10.1
  Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
    Hello due in 00:00:06                           <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
  Index 1/1, flood queue length 0
  Next 0x0(0)/0x0(0)
  Last flood scan length is 2, maximum is 2
  Last flood scan time is 0 msec, maximum is 4 msec
  Neighbor Count is 1, Adjacent neighbor count is 1 
    Adjacent with neighbor 172.16.10.1  (Designated Router)
  Suppress hello for 0 neighbor(s)

CCO link to configure OSPF over NBMA networks.

http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a008009470d.shtml

feroz syed · ‎06-05-2013

R1#sh ip ospf int

Loopback1 is up, line protocol is up

Internet Address 192.168.100.1/24, Area 0

Process ID 1, Router ID 192.168.100.1, Network Type LOOPBACK, Cost: 1

Loopback interface is treated as a stub Host

Serial1/0 is up, line protocol is up

Internet Address 172.12.123.1/24, Area 10

Process ID 1, Router ID 192.168.100.1, Network Type NON_BROADCAST, Cost: 64

Transmit Delay is 1 sec, State DR, Priority 1

Designated Router (ID) 192.168.100.1, Interface address 172.12.123.1

No backup designated router on this network

Timer intervals configured, Hello 30, Dead 120, Wait 120, Retransmit 5

oob-resync timeout 120

Hello due in 00:00:19

Supports Link-local Signaling (LLS)

Cisco NSF helper support enabled

IETF NSF helper support enabled

Index 1/2, flood queue length 0

Next 0x0(0)/0x0(0)

Last flood scan length is 0, maximum is 0

Last flood scan time is 0 msec, maximum is 0 msec

Neighbor Count is 0, Adjacent neighbor count is 0

Suppress hello for 0 neighbor(s)

R2#sh ip ospf int

Loopback1 is up, line protocol is up

Internet Address 192.168.100.2/24, Area 0

Process ID 1, Router ID 192.168.100.2, Network Type LOOPBACK, Cost: 1

Loopback interface is treated as a stub Host

Serial1/2 is up, line protocol is up

Internet Address 172.12.123.2/24, Area 10

Process ID 1, Router ID 192.168.100.2, Network Type NON_BROADCAST, Cost: 64

Transmit Delay is 1 sec, State DR, Priority 1

Designated Router (ID) 192.168.100.2, Interface address 172.12.123.2

No backup designated router on this network

Timer intervals configured, Hello 30, Dead 120, Wait 120, Retransmit 5

oob-resync timeout 120

Hello due in 00:00:17

Supports Link-local Signaling (LLS)

Cisco NSF helper support enabled

IETF NSF helper support enabled

Index 1/2, flood queue length 0

Next 0x0(0)/0x0(0)

Last flood scan length is 0, maximum is 0

Last flood scan time is 0 msec, maximum is 0 msec

Neighbor Count is 0, Adjacent neighbor count is 0

Suppress hello for 0 neighbor(s)

R3#sh ip ospf int

Loopback1 is up, line protocol is up

Internet Address 192.168.100.3/24, Area 0

Process ID 1, Router ID 192.168.100.3, Network Type LOOPBACK, Cost: 1

Loopback interface is treated as a stub Host

Serial1/3 is up, line protocol is up

Internet Address 172.12.123.3/24, Area 10

Process ID 1, Router ID 192.168.100.3, Network Type NON_BROADCAST, Cost: 64

Transmit Delay is 1 sec, State DR, Priority 1

Designated Router (ID) 192.168.100.3, Interface address 172.12.123.3

No backup designated router on this network

Timer intervals configured, Hello 30, Dead 120, Wait 120, Retransmit 5

oob-resync timeout 120

Hello due in 00:00:00

Supports Link-local Signaling (LLS)

Cisco NSF helper support enabled

IETF NSF helper support enabled

Index 1/2, flood queue length 0

Next 0x0(0)/0x0(0)

Last flood scan length is 0, maximum is 0

Last flood scan time is 0 msec, maximum is 0 msec

Neighbor Count is 0, Adjacent neighbor count is 0

Suppress hello for 0 neighbor(s)

R1#sh ip ospf int
Loopback1 is up, line protocol is up
Internet Address 192.168.100.1/24, Area 0
Process ID 1, Router ID 192.168.100.1, Network Type LOOPBACK, Cost: 1
Loopback interface is treated as a stub Host
Serial1/0 is up, line protocol is up
Internet Address 172.12.123.1/24, Area 10
Process ID 1, Router ID 192.168.100.1, Network Type NON_BROADCAST, Cost: 64
Transmit Delay is 1 sec, State DR, Priority 1
Designated Router (ID) 192.168.100.1, Interface address 172.12.123.1
No backup designated router on this network
Timer intervals configured, Hello 30, Dead 120, Wait 120, Retransmit 5
oob-resync timeout 120
Hello due in 00:00:19
Supports Link-local Signaling (LLS)
Cisco NSF helper support enabled
IETF NSF helper support enabled
Index 1/2, flood queue length 0
Next 0x0(0)/0x0(0)
Last flood scan length is 0, maximum is 0
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 0, Adjacent neighbor count is 0
Suppress hello for 0 neighbor(s)

R2#sh ip ospf int
Loopback1 is up, line protocol is up
Internet Address 192.168.100.2/24, Area 0
Process ID 1, Router ID 192.168.100.2, Network Type LOOPBACK, Cost: 1
Loopback interface is treated as a stub Host
Serial1/2 is up, line protocol is up
Internet Address 172.12.123.2/24, Area 10
Process ID 1, Router ID 192.168.100.2, Network Type NON_BROADCAST, Cost: 64
Transmit Delay is 1 sec, State DR, Priority 1
Designated Router (ID) 192.168.100.2, Interface address 172.12.123.2
No backup designated router on this network
Timer intervals configured, Hello 30, Dead 120, Wait 120, Retransmit 5
oob-resync timeout 120
Hello due in 00:00:17
Supports Link-local Signaling (LLS)
Cisco NSF helper support enabled
IETF NSF helper support enabled
Index 1/2, flood queue length 0
Next 0x0(0)/0x0(0)
Last flood scan length is 0, maximum is 0
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 0, Adjacent neighbor count is 0
Suppress hello for 0 neighbor(s)

R3#sh ip ospf int
Loopback1 is up, line protocol is up
Internet Address 192.168.100.3/24, Area 0
Process ID 1, Router ID 192.168.100.3, Network Type LOOPBACK, Cost: 1
Loopback interface is treated as a stub Host
Serial1/3 is up, line protocol is up
Internet Address 172.12.123.3/24, Area 10
Process ID 1, Router ID 192.168.100.3, Network Type NON_BROADCAST, Cost: 64
Transmit Delay is 1 sec, State DR, Priority 1
Designated Router (ID) 192.168.100.3, Interface address 172.12.123.3
No backup designated router on this network
Timer intervals configured, Hello 30, Dead 120, Wait 120, Retransmit 5
oob-resync timeout 120
Hello due in 00:00:00
Supports Link-local Signaling (LLS)
Cisco NSF helper support enabled
IETF NSF helper support enabled
Index 1/2, flood queue length 0
Next 0x0(0)/0x0(0)
Last flood scan length is 0, maximum is 0
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 0, Adjacent neighbor count is 0
Suppress hello for 0 neighbor(s)

Akash Agrawal · ‎06-05-2013

Hi Feroz,

Please share OSPF configuration for all 3 routers. You can also run "debug ip ospf adj" to collect more logs.

Regards,

Akash

Jose Jara · ‎06-05-2013

If layer 2 it's fine as you said and you have configured the neighbor statements as Akash said, then configure priority 255 in the Hub - R1, priority 0 in the spokes, then clear ip ospf process and it should work.

Best Regards,

Jose.

feroz syed · ‎06-05-2013

R3#debug ip ospf adj

OSPF adjacency events debugging is on

R3#cle

R3#clear ip os

R3#clear ip ospf pr

R3#clear ip ospf process

Reset ALL OSPF processes? [no]: y

R3#

*Jun 5 11:54:23.415: OSPF: Interface Loopback1 going Down

*Jun 5 11:54:23.415: OSPF: 192.168.100.3 address 192.168.100.3 on Loopback1 is dead, state DOWN

*Jun 5 11:54:23.455: OSPF: Interface Serial1/3 going Down

*Jun 5 11:54:23.455: OSPF: 192.168.100.3 address 172.12.123.3 on Serial1/3 is dead, state DOWN

*Jun 5 11:54:23.455: OSPF: Neighbor change Event on interface Serial1/3

*Jun 5 11:54:23.459: OSPF: DR/BDR election on Serial1/3

*Jun 5 11:54:23.459: OSPF: Elect BDR 0.0.0.0

*Jun 5 11:54:23.459: OSPF: Elect DR 0.0.0.0

*Jun 5 11:54:23.459: OSPF: Elect BDR 0.0.0.0

*Jun 5 11:54:23.459: OSPF: Elect DR 0.0.0.0

*Jun 5 11:54:23.459: DR: none BDR: none

R3#

*Jun 5 11:54:23.463: OSPF: Flush network LSA immediately

*Jun 5 11:54:23.463: OSPF: Remember old DR 192.168.100.3 (id)

*Jun 5 11:54:23.547: OSPF: Interface Loopback1 going Up

*Jun 5 11:54:23.547: OSPF: Interface Serial1/3 going Up

*Jun 5 11:54:23.915: OSPF: Build router LSA for area 0, router ID 192.168.100.3, seq 0x80000001, process 1

*Jun 5 11:54:23.963: OSPF: We are not DR to build Net Lsa for interface Serial1/3

*Jun 5 11:54:23.963: OSPF: Build router LSA for area 10, router ID 192.168.100.3, seq 0x80000001, process 1R3#debug ip ospf adj
OSPF adjacency events debugging is on
R3#cle
R3#clear ip os
R3#clear ip ospf pr
R3#clear ip ospf process
Reset ALL OSPF processes? [no]: y
R3#
*Jun 5 11:54:23.415: OSPF: Interface Loopback1 going Down
*Jun 5 11:54:23.415: OSPF: 192.168.100.3 address 192.168.100.3 on Loopback1 is dead, state DOWN
*Jun 5 11:54:23.455: OSPF: Interface Serial1/3 going Down
*Jun 5 11:54:23.455: OSPF: 192.168.100.3 address 172.12.123.3 on Serial1/3 is dead, state DOWN
*Jun 5 11:54:23.455: OSPF: Neighbor change Event on interface Serial1/3
*Jun 5 11:54:23.459: OSPF: DR/BDR election on Serial1/3
*Jun 5 11:54:23.459: OSPF: Elect BDR 0.0.0.0
*Jun 5 11:54:23.459: OSPF: Elect DR 0.0.0.0
*Jun 5 11:54:23.459: OSPF: Elect BDR 0.0.0.0
*Jun 5 11:54:23.459: OSPF: Elect DR 0.0.0.0
*Jun 5 11:54:23.459: DR: none BDR: none
R3#
*Jun 5 11:54:23.463: OSPF: Flush network LSA immediately
*Jun 5 11:54:23.463: OSPF: Remember old DR 192.168.100.3 (id)
*Jun 5 11:54:23.547: OSPF: Interface Loopback1 going Up
*Jun 5 11:54:23.547: OSPF: Interface Serial1/3 going Up
*Jun 5 11:54:23.915: OSPF: Build router LSA for area 0, router ID 192.168.100.3, seq 0x80000001, process 1
*Jun 5 11:54:23.963: OSPF: We are not DR to build Net Lsa for interface Serial1/3
*Jun 5 11:54:23.963: OSPF: Build router LSA for area 10, router ID 192.168.100.3, seq 0x80000001, process 1

cadet alain · ‎06-05-2013

Hi,

Post your configs and make sure you configured the static neighbours on the hub and the OSPF priority to zero on the spokes interfaces.

Regards

Alain

Don't forget to rate helpful posts.

feroz syed · ‎06-05-2013

It would be helpful if you explain me why we need to change priority on spoke routers.

!

interface Loopback1

ip address 192.168.100.1 255.255.255.0

!

interface FastEthernet0/0

no ip address

shutdown

duplex half

!

interface Serial1/0

ip address 172.12.123.1 255.255.255.0

encapsulation frame-relay IETF

serial restart-delay 0

frame-relay map ip 172.12.123.3 103

frame-relay map ip 172.12.123.2 102

no frame-relay inverse-arp

!

interface Serial1/1

no ip address

shutdown

serial restart-delay 0

!

interface Serial1/2

no ip address

shutdown

serial restart-delay 0

!

interface Serial1/3

no ip address

shutdown

serial restart-delay 0

!

router ospf 1

log-adjacency-changes

network 172.12.123.0 0.0.0.255 area 10

network 192.168.100.0 0.0.0.255 area 0

interface Loopback1

ip address 192.168.100.2 255.255.255.0

!

interface FastEthernet0/0

no ip address

shutdown

duplex half

!

interface Serial1/0

no ip address

shutdown

serial restart-delay 0

!

interface Serial1/1

no ip address

shutdown

serial restart-delay 0

!

interface Serial1/2

ip address 172.12.123.2 255.255.255.0

encapsulation frame-relay

serial restart-delay 0

frame-relay map ip 172.12.123.3 201

frame-relay map ip 172.12.123.1 201

no frame-relay inverse-arp

!

interface Serial1/3

no ip address

shutdown

serial restart-delay 0

!

interface FastEthernet2/0

no ip address

shutdown

duplex auto

speed auto

!

interface FastEthernet2/1

no ip address

shutdown

duplex auto

speed auto

!

router ospf 1

log-adjacency-changes

network 172.12.123.0 0.0.0.255 area 10

network 192.168.100.0 0.0.0.255 area 0

!

interface Loopback1

ip address 192.168.100.3 255.255.255.0

!

interface FastEthernet0/0

no ip address

shutdown

duplex half

!

interface Serial1/0

no ip address

shutdown

serial restart-delay 0

!

interface Serial1/1

no ip address

shutdown

serial restart-delay 0

!

interface Serial1/2

no ip address

shutdown

serial restart-delay 0

!

interface Serial1/3

ip address 172.12.123.3 255.255.255.0

encapsulation frame-relay

serial restart-delay 0

frame-relay map ip 172.12.123.2 301

frame-relay map ip 172.12.123.1 301

no frame-relay inverse-arp

!

interface FastEthernet2/0

no ip address

shutdown

duplex auto

speed auto

!

interface FastEthernet2/1

no ip address

shutdown

duplex auto

speed auto

!

router ospf 1

log-adjacency-changes

network 172.12.123.0 0.0.0.255 area 10

network 192.168.100.0 0.0.0.255 area 0

!
interface Loopback1
ip address 192.168.100.1 255.255.255.0
!
interface FastEthernet0/0
no ip address
shutdown
duplex half
!
interface Serial1/0
ip address 172.12.123.1 255.255.255.0
encapsulation frame-relay IETF
serial restart-delay 0
frame-relay map ip 172.12.123.3 103
frame-relay map ip 172.12.123.2 102
no frame-relay inverse-arp
!
interface Serial1/1
no ip address
shutdown
serial restart-delay 0
!
interface Serial1/2
no ip address
shutdown
serial restart-delay 0
!
interface Serial1/3
no ip address
shutdown
serial restart-delay 0
!
router ospf 1
log-adjacency-changes
network 172.12.123.0 0.0.0.255 area 10
network 192.168.100.0 0.0.0.255 area 0

Router 2

interface Loopback1
ip address 192.168.100.2 255.255.255.0
!
interface FastEthernet0/0
no ip address
shutdown
duplex half
!
interface Serial1/0
no ip address
shutdown
serial restart-delay 0
!
interface Serial1/1
no ip address
shutdown
serial restart-delay 0
!
interface Serial1/2
ip address 172.12.123.2 255.255.255.0
encapsulation frame-relay
serial restart-delay 0
frame-relay map ip 172.12.123.3 201
frame-relay map ip 172.12.123.1 201
no frame-relay inverse-arp
!
interface Serial1/3
no ip address
shutdown
serial restart-delay 0
!
interface FastEthernet2/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet2/1
no ip address
shutdown
duplex auto
speed auto
!
router ospf 1
log-adjacency-changes
network 172.12.123.0 0.0.0.255 area 10
network 192.168.100.0 0.0.0.255 area 0
!

Router 3

interface Loopback1
ip address 192.168.100.3 255.255.255.0
!
interface FastEthernet0/0
no ip address
shutdown
duplex half
!
interface Serial1/0
no ip address
shutdown
serial restart-delay 0
!
interface Serial1/1
no ip address
shutdown
serial restart-delay 0
!
interface Serial1/2
no ip address
shutdown
serial restart-delay 0
!
interface Serial1/3
ip address 172.12.123.3 255.255.255.0
encapsulation frame-relay
serial restart-delay 0
frame-relay map ip 172.12.123.2 301
frame-relay map ip 172.12.123.1 301
no frame-relay inverse-arp
!
interface FastEthernet2/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet2/1
no ip address
shutdown
duplex auto
speed auto
!
router ospf 1
log-adjacency-changes
network 172.12.123.0 0.0.0.255 area 10
network 192.168.100.0 0.0.0.255 area 0

kcnajaf · ‎06-05-2013

Hi Feroz,

I hope you are missing neighbor command on R1.

router ospf 1

neighbor 172.12.123.2

neighbor 172.12.123.3

Hope that helps

Regards

Najaf

Please rate when applicable or helpful !!!

Jose Jara · ‎06-05-2013

As the network type is non-broadcast, a DR is needed for the database synchronization. The spokes must synchronize their databases with the Hub, which must be the DR. The spokes do not have direct communication between them, so they could not sync their databases.

I would hardcode the router-id as well and configure the neighbor statements as they are missing in the config.

Hope this helps,

Jose.

kcnajaf · ‎06-05-2013

HI Feroz,

From your debug output it looks like your loopback interface is going down (very strange:-). Router would be using the loopback address as the router id for the OSPF process.

If you have necessary configuration as adviced in previous post by other experts and if you ensure your interface remains up up i think that should fix the issue.

Hope that helps

Regards

Najaf

Please rate when applicable or helpful !!!

feroz syed · ‎06-05-2013

So when OSPF running in nbma network it's mandatory to execute "neighbour cmd " and making priority 0 on spoke routers .
Sent from Cisco Technical Support iPhone App

Jose Jara · ‎06-05-2013

Hi Feroz,

you have different options in NBMA. However, if the network type is non-broadcast, it's mandatory to use neighbor statements as the communication is unicast. The use of priority 0 is to prevent that spokes will not participate in the DR/BDR election process.

Other option is to use point-to-multipoint network ospf network type. Here, you do not need to change priority because there is no DR/BDR and also you do not need neighbor statements. However, you need to add the broadcast keyword in the frame map statements between the Hub and Spokes as the communication is multicast - 224.0.0.5.

Hope this helps,

Jose.