OSPF not advertising network associated with Loopback interface - Page 2

m.tapping · ‎05-20-2004

Following router/IOS/WAN upgrade OSPF is not advertising the subnet associated with the Loopback interface. It does however advertise the actual Loopback interface address. The subnet associated with the Loopback interface is used for NAT translations.

System image file is "flash:c2600-is-mz.122-23.bin"

interface Loopback0

ip address 172.18.33.1 255.255.255.0

!

interface FastEthernet0/0

ip address 192.168.3.2 255.255.255.0 secondary

ip address 172.16.10.101 255.255.248.0

ip access-group 110 in

no ip redirects

ip nat inside

speed 10

half-duplex

no cdp enable

!

interface BRI0/0

no ip address

ip nat outside

encapsulation ppp

no ip mroute-cache

dialer rotary-group 1

isdn switch-type basic-net3

no fair-queue

no cdp enable

!

interface ATM1/0

description *** 2Mbps CellStream ***

bandwidth 2048

no ip address

no ip mroute-cache

logging event subif-link-status

no atm ilmi-keepalive

scrambling-payload

impedance 120-ohm

!

interface ATM1/0.1 point-to-point

bandwidth 1024

ip address 172.31.5.70 255.255.255.252

ip nat outside

pvc Risley 1/32

vbr-nrt 1024 1024 64000

oam-pvc manage

encapsulation aal5snap

!

interface ATM1/0.2 point-to-point

bandwidth 1024

ip address 172.29.1.58 255.255.255.252

ip nat outside

pvc SunGard 1/34

vbr-nrt 1024 1024 64000

oam-pvc manage

encapsulation aal5snap

!

interface ATM1/1

no ip address

shutdown

no atm ilmi-keepalive

scrambling-payload

impedance 120-ohm

!

interface ATM1/2

no ip address

shutdown

no atm ilmi-keepalive

scrambling-payload

impedance 120-ohm

!

interface ATM1/3

no ip address

shutdown

no atm ilmi-keepalive

scrambling-payload

impedance 120-ohm

!

interface Dialer1

bandwidth 1

ip address 172.18.48.17 255.255.255.0

ip nat outside

encapsulation ppp

dialer in-band

dialer idle-timeout 300

dialer map ip 172.18.48.1 name foxrtr-ris03 broadcast *****830874

dialer hold-queue 10

dialer-group 1

no fair-queue

no cdp enable

ppp authentication chap

!

router ospf 100

log-adjacency-changes

redistribute connected metric-type 1 subnets

redistribute static

passive-interface FastEthernet0/0

network 172.18.33.0 0.0.0.255 area 0

network 172.18.48.0 0.0.0.255 area 0

network 172.29.1.0 0.0.0.255 area 0

network 172.31.5.0 0.0.0.255 area 0

distribute-list 2 out

!

ip nat pool pj 172.18.33.20 172.18.33.254 netmask 255.255.255.0

ip nat inside source list 1 pool pj

ip nat inside source static 172.16.9.86 172.18.33.14

ip nat inside source static 172.16.8.247 172.18.33.13

ip nat inside source static 172.16.9.97 172.18.33.5

ip nat inside source static 172.16.9.28 172.18.33.4

ip nat inside source static 172.16.9.132 172.18.33.11

ip nat inside source static 172.16.13.24 172.18.33.2

ip nat inside source static 172.16.9.77 172.18.33.7

ip nat inside source static 172.16.9.53 172.18.33.3

ip nat inside source static 172.16.8.75 172.18.33.9

ip nat inside source static 172.16.18.3 172.18.33.12

ip nat inside source static 172.16.9.71 172.18.33.6

ip classless

ip route 0.0.0.0 0.0.0.0 172.18.48.1 150

ip http server

!

access-list 1 permit 192.168.1.0 0.0.0.255

access-list 1 permit 192.168.2.0 0.0.0.255

access-list 1 permit 192.168.3.0 0.0.0.255

access-list 1 permit 192.168.5.0 0.0.0.255

access-list 1 permit 172.16.0.0 0.0.255.255

access-list 2 deny 192.168.3.0

access-list 2 deny 172.16.8.0

access-list 2 deny 172.16.0.0

access-list 2 permit any

m.tapping · ‎05-26-2004

My current OSPF neighbour is across subinterface ATM1/0.1, this is correct.

Neighbor ID Pri State Dead Time Address Interface

172.18.48.1 1 FULL/ - 00:00:38 172.31.5.69 ATM1/0.1

I can see that Router Link State advertisiements are being generated locally and propogated into the backbone, however the underlying stub network isn't even when redistributing 'Connected'.

I hope I haven't misinterpreted what the OSPF protocol will do and I have other working examples where the stub network associated with the Loopback interface are advertised.

I've attached the output from "show ip ospf interface", note that I have reverted the network type for the Loopback interface.

Dialer1 is up, line protocol is up (spoofing)

Internet Address 172.18.48.17/24, Area 0

Process ID 100, Router ID 172.18.33.1, Network Type POINT_TO_POINT, Cost: 65535

Transmit Delay is 1 sec, State POINT_TO_POINT,

Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5

No Hellos (Passive interface)

Index 2/2, flood queue length 0

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

Last flood scan length is 1, maximum is 1

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)

ATM1/0.1 is up, line protocol is up

Internet Address 172.31.5.70/30, Area 0

Process ID 100, Router ID 172.18.33.1, Network Type POINT_TO_POINT, Cost: 97

Transmit Delay is 1 sec, State POINT_TO_POINT,

Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5

Hello due in 00:00:06

Index 4/4, flood queue length 0

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

Last flood scan length is 1, maximum is 40

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

Neighbor Count is 1, Adjacent neighbor count is 1

Adjacent with neighbor 172.18.48.1

Suppress hello for 0 neighbor(s)

ATM1/0.2 is down, line protocol is down

Internet Address 172.29.1.58/30, Area 0

Process ID 100, Router ID 172.18.33.1, Network Type POINT_TO_POINT, Cost: 97

Transmit Delay is 1 sec, State DOWN,

Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5

Loopback0 is up, line protocol is up

Internet Address 172.18.33.1/24, Area 0

Process ID 100, Router ID 172.18.33.1, Network Type LOOPBACK, Cost: 1

Loopback interface is treated as a stub Host

foxrtr-tvbc02#

I will be trying your recommendation of using another IP subnet on the loopback tonight.

ziutek · ‎05-26-2004

Did changing the ospf network type not work? From the outpuit of the sho ip ospf ne command I see that you are still advertising only the loopback as a host route, and not as a full network. Add the ?ip ospf net point-to-p" command under the loopback interface, and the issue clear ip ospf proc. the take a look at the sh ip opsg int again, and see if the changes show up making loopback0 a point-to-point network.

Joe

olorunloba · ‎05-26-2004

Funny question, because I guess you must have done it already.

Have you tried to do a clear ip route * ?

This is after specifying the loopback as a point to point.

m.tapping · ‎05-26-2004

not specifically although this would have been taken care of by virtue of the number of reloads I've performed.