HSRP issue both device active stats

Question

Here is the Diagram.

Ip address:

ISP:

[VIP]- 10.107.25.5
[R1] - 10.107.25.6
[R2] - 10.107.25.7

Me:

[VIP] - 10.107.25.10
[SW1] - 10.107.25.11
[SW2] - 10.107.25.12

Configuration on port:

SW1


    interface GigabitEthernet1/0/1
    description #Primary Link WTBB 1#
    no switchport
    ip address 10.107.25.11 255.255.255.248
    standby 30 ip 10.107.25.10
    standby 30 priority 110
    standby 30 preempt

SW2


    interface GigabitEthernet1/0/1
    description # Secondary Link WTBB 2#
    no switchport
    ip address 10.107.25.12 255.255.255.248
    standby 30 ip 10.107.25.10
    no standby 30 preempt

Notes: Interesting thing i can't ping from 10.107.25.11 to 10.107.25.12 I am not sure what is other side of ISP, As per document .11 should ping .12 so they can say hello to each other using L2 layer right?

This is what i did but i think its wrong way to configure HSRP

[SW1]

interface vlan3
ip address 10.107.25.11 255.255.255.248
standby 30 ip 10.107.25.10
standby 30 priority 110
standby 30 preempt 

interface GigabitEthernet1/0/1
switchport access allow vlan 3

[SW2]

interface vlan3
ip address 10.107.25.12 255.255.255.248
standby 30 ip 10.107.25.10
standby 30 priority 110
standby 30 preempt 

interface GigabitEthernet1/0/1
switchport access allow vlan 3

On Trunk interface i allowed Vlan3

Now i can ping from .11 to .12 ip address using vlan3 (L2) network. and HSRP is happy (active/standby).

But if i unplug cable on port G1/0/1 trying to mimic cable is cut and my VIP will failover. but problem is .11 and .12 is on vlan3 interface and they are UP no matter you cut the cable or not..

How do i solve this issue in above scenario?

Answer 1

Edited to reflect new information in the question:

Based on your multiple edits which finally give the whole picture (I hope), you can try something like this, but using the switch stacking capability in the alternative configuration will give you a better solution.

Your connection to the ISP will need to be on the same subnet as the ISP.

SW1:

track 3 interface GigabitEthernet1/0/1 line-protocol
!
interface GigabitEthernet1/0/1
 description #Primary Link WTBB 1#
 switchport
 switchport access vlan 3
 switchport mode access
 no shutdown
!
interface GigabitEthernet1/0/2
 description #Link to switch 2#
 switchport
 switchport access vlan 3
 switchport mode access
 no shutdown
!
interface Vlan3
 ip address 10.107.25.11 255.255.255.240
 standby 30 ip 10.107.25.10
 standby 30 priority 105
 standby 30 preempt
 standby 30 track 3 decrement 10
 no shutdown
!

SW2:

track 3 interface GigabitEthernet1/0/1 line-protocol
!
interface GigabitEthernet1/0/1
 description #Primary Link WTBB 2#
 switchport
 switchport access vlan 3
 switchport mode access
 no shutdown
!
interface GigabitEthernet1/0/2
 description #Link to switch 1#
 switchport
 switchport access vlan 3
 switchport mode access
 no shutdown
!
interface Vlan3
 ip address 10.107.25.12 255.255.255.240
 standby 30 ip 10.107.25.10
 standby 30 priority 100
 standby 30 preempt
 standby 30 track 3 decrement 10
 no shutdown
!

This allows the ISP HSRP to work since the ISP routers need to be able to talk to each other on the same VLAN so that the ISP HSRP works.

Alternate (stacked) Configuration:

SW1/2 stack:

interface GigabitEthernet1/0/1
 description #Primary Link WTBB 1#
 switchport
 switchport access vlan 3
 switchport mode access
 no shutdown
!
interface GigabitEthernet2/0/1
 description #Primary Link WTBB 2#
 switchport
 switchport access vlan 3
 switchport mode access
 no shutdown
!
interface Vlan3
 ip address 10.107.25.10 255.255.255.240
 no shutdown
!

This configuration gives you all the benefits of the two separate switches but solves your problem of having two separate switches with separate IP addresses. The stack is configured as a single switch and is managed as a single device. Besides the data sharing, the 3850s can also do power sharing so that if one of them loses power, the other can keep both switches running. You will also save precious public IP addresses.