OSPF /HSRP Backup link for router

[leinad427]

I have the follwoing topology.. I cant get the redundant link between R1 to IOS-L2-2 to work nor can I get R2 to IOS-L2-1 to work. If I put a link betweeen the two switches everything works but if I remove it everything goes down. What could the issue be I thought I need to config the backup ports as a backup under the router interface config

[Julio E. Moisa]

Hi

Could you please share the configuration? 

Thank you in advance. 

[leinad427]

thisa is the config for R1: I had a backup port on F0/0 of F0/1 but removed it

Building configuration...

Current configuration : 1162 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R1
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
no ip icmp rate-limit unreachable
ip cef
!
!
!
!
no ip domain lookup
ip auth-proxy max-nodata-conns 3
ip admission max-nodata-conns 3
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
ip tcp synwait-time 5
!
!
!
!
!
interface FastEthernet0/0
ip address 172.0.1.2 255.255.255.0
duplex auto
speed auto
standby 1 ip 172.0.1.1
standby 1 priority 120
standby 1 preempt
!
interface Serial0/0
no ip address
shutdown
clock rate 2000000
!
interface FastEthernet0/1
no ip address
duplex auto
speed auto
!
interface Serial0/1
no ip address
shutdown
clock rate 2000000
!
interface FastEthernet1/0
no ip address
shutdown
duplex auto
speed auto
!
ip forward-protocol nd
!
!
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

[leinad427]

This is for IOS-L2-1:

Building configuration...

Current configuration : 3298 bytes
!
! Last configuration change at 05:24:15 UTC Sat Sep 23 2017
!
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
media-type rj45
negotiation auto
!
interface GigabitEthernet0/1
media-type rj45
negotiation auto
!
interface GigabitEthernet0/2
media-type rj45
negotiation auto
!
interface GigabitEthernet0/3
media-type rj45
negotiation auto
!
interface GigabitEthernet1/0
media-type rj45
negotiation auto
!
interface GigabitEthernet1/1
media-type rj45
negotiation auto
!
interface GigabitEthernet1/2
media-type rj45
negotiation auto
!
interface GigabitEthernet1/3
media-type rj45
negotiation auto
!
interface GigabitEthernet2/0
media-type rj45
negotiation auto
!
interface GigabitEthernet2/1
media-type rj45
negotiation auto
!
interface GigabitEthernet2/2
media-type rj45
negotiation auto
!
interface GigabitEthernet2/3
media-type rj45
negotiation auto
!
interface Vlan1
ip address 172.0.1.4 255.255.255.0
!
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

[Meheretab Mengistu]

Hi,

You have two routers with HSRP redundancy, right?
The main purpose of the redundancy is to failover when there is an outage in one link. If fa0/0 on R1 is DOWN, you want to failover to R2; and it should work. Because you have IP address configured on R2 and it is used as a gateway. However, your current setup will not work unless you have redundant link connecting the two switches. Since there is IP address configured on one part of the link and there is no IP address on the other link (fa0/1) and as it is not working as a switch, you could not make it work.

HTH,
Meheretab

[leinad427]

thanks so just to clarify there is no way to get R1 f0/1 to avtivate as a backup in case f0/0 fails the only way to get it work is to put a link between both switches this way R2 f0/0 activates right

[Meheretab Mengistu]

From practical point of view, you will normally configure a port on each router and add redundant link between the switches.
If you want to configure the way you choose for lab purpose, you will need to think of the way to put the two ports (fa0/0 and fa0/1) in to the same subnet so that they could share the same DHCP server and same IP address.

HTH,
Meheretab

[Julio E. Moisa]

Hi

Thank you for the configuration.

What I see is, you are using the VLAN 1 to interconnect the HSRP peers, now you should see if the HSRP peers are talking to define who is the master and who is the standby, you can use the following command:

show standby vlan 1 on both routers.

If everything is ok, R1 should be the active and R2 the standby. 

Now If R1 is down all the traffic from IOS-L2L1 should be redirected to R2 the same for the IOS-L2-2's traffic. 

If you are going to define who will be spanning tree root for the vlan 1 you can set up a link between both switches in order to have redundancy for the access switches. 

:-)