Lab Getting out to ISP

[leinad427]

So I have the following lab setup and I am having an issue getting the Core/Dis Switch to ping the ISP router. I've attached an image of the lab and below is the output for the router and cor/dis switch.

I have ospf enabled on both R1 and Core and I have a static route from R1 to the ISP and can ping from R1 to the ISP but not from the core. Is there any way to do this? 

R1

========================

Building configuration...

Current configuration : 1187 bytes
!
version 12.3
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R1
!
boot-start-marker
boot-end-marker
!
!
memory-size iomem 5
no aaa new-model
ip subnet-zero
no ip icmp rate-limit unreachable
ip cef
ip tcp synwait-time 5
!
!
!
!
no ip domain lookup
ip ips po max-events 100
no ftp-server write-enable
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface FastEthernet0/0
ip address 10.0.1.4 255.255.255.248
duplex auto
speed auto
!
interface Serial0/0
ip address 172.0.1.1 255.255.255.252
clockrate 2000000
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/1
no ip address
shutdown
clockrate 2000000
!
router ospf 1
router-id 1.1.1.1
log-adjacency-changes
network 10.0.1.0 0.0.0.255 area 1
network 172.0.1.0 0.0.0.255 area 1
!
ip classless
ip route 0.0.0.0 0.0.0.0 Serial0/0
!
!
no ip http server
no ip http secure-server
!
no cdp log mismatch duplex
!
!
!
!
control-plane
!
!
!
!
!
!
!
!
!
line con 0
exec-timeout 0 0
privilege level 15
logging synchronous
line aux 0
exec-timeout 0 0
privilege level 15
logging synchronous
line vty 0 4
login
!
!
end

=================================

Core/DIS

================================

Building configuration...

Current configuration : 3128 bytes
!
! Last configuration change at 21:07:44 UTC Wed Jan 10 2018
!
version 15.2
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
service compress-config
!
hostname Switch
!
boot-start-marker
boot-end-marker
!
!
!
no aaa new-model
!
!
!
!
!
!
!
!
ip cef
no ipv6 cef
!
!
!
spanning-tree mode rapid-pvst
spanning-tree extend system-id
!
vlan internal allocation policy ascending
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface GigabitEthernet0/0
switchport trunk encapsulation dot1q
switchport trunk native vlan 110
switchport mode trunk
media-type rj45
negotiation auto
!
interface GigabitEthernet0/1
switchport trunk encapsulation dot1q
switchport trunk native vlan 110
switchport mode trunk
media-type rj45
negotiation auto
!
interface GigabitEthernet0/2
switchport trunk encapsulation dot1q
switchport trunk native vlan 110
switchport mode trunk
media-type rj45
negotiation auto
!
interface GigabitEthernet0/3
media-type rj45
negotiation auto
!
interface Vlan110
ip address 10.0.1.1 255.255.255.248
!
router ospf 1
router-id 2.2.2.2
network 10.0.1.0 0.0.0.255 area 1
!
ip forward-protocol nd
!
no ip http server
no ip http secure-server
!
!
!
!
!
!
control-plane
!
banner exec ^C
**************************************************************************
* IOSv is strictly limited to use for evaluation, demonstration and IOS *
* education. IOSv is provided as-is and is not supported by Cisco's *
* Technical Advisory Center. Any use or disclosure, in whole or in part, *
* of the IOSv Software or Documentation to any third party for any *
* purposes is expressly prohibited except as otherwise authorized by *
* Cisco in writing. *
**************************************************************************^C
banner incoming ^C
**************************************************************************
* IOSv is strictly limited to use for evaluation, demonstration and IOS *
* education. IOSv is provided as-is and is not supported by Cisco's *
* Technical Advisory Center. Any use or disclosure, in whole or in part, *
* of the IOSv Software or Documentation to any third party for any *
* purposes is expressly prohibited except as otherwise authorized by *
* Cisco in writing. *
**************************************************************************^C
banner login ^C
**************************************************************************
* IOSv is strictly limited to use for evaluation, demonstration and IOS *
* education. IOSv is provided as-is and is not supported by Cisco's *
* Technical Advisory Center. Any use or disclosure, in whole or in part, *
* of the IOSv Software or Documentation to any third party for any *
* purposes is expressly prohibited except as otherwise authorized by *
* Cisco in writing. *
**************************************************************************^C
!
line con 0
line aux 0
line vty 0 4
!
!
end

[Mark Malone · Accepted solution]

Hi
in ospf there should always be an area 0 for the backbone , but for a lab to redistribute the default route into other routers in same area try under the ospf process r1 add default-information originate

Doc extract
There are two ways to advertise a default route into a normal area. The first is to advertise 0.0.0.0 into the OSPF domain, provided the advertising router already has a default route. The second is to advertise 0.0.0.0 regardless of whether the advertising router already has a default route. The second method can be accomplished by adding the keyword always to the default-information originate command.

[leinad427]

just like magic, thanks that solve the issue. I was trying to add a static route from the core to the R1 {facepalm}

[paul driver]

Hello

As the isp and all your rtrs are in the same area 1 then you should only need to make a few amendments.

R1
no ip route 0.0.0.0 0.0.0.0 Serial0/0
ip route 0.0.0.0 0.0.0.0 Serial0/0 172.0.1.2

interface fa0/0

ip ospf 1 priority 200 ( as this is an ospf broadcast link its preferable to make this the DR of the core/dis rtrs)

router ospf 1

default-information originate always

As for the core/dis rtr they will revive a default route from rtr1 so they will be able to reach the isp. prefixes

ISP rtr

The isp in return would be filtering any default route being advertised to it and accept any other prefixes you send it to which will be originating fro the core/dis rtrs via their own network statements
.(NOTE:- the below config is not required if the default is originating from the ISP rtr instead of rtr1)

ip prefix-list nodefault seq 5 deny 0.0.0.0/0
ip prefix-list nodefault seq 10 permit 0.0.0.0/0 le 32

router ospf 1
distribute-list prefix nodefault in Serial0/0

res
Paul