Solved: HSRP CONFIGURATION ERROR

brijendrasaini · ‎08-30-2017

DEAR TEAM,

WHEN I CONFIGURE HSRP EVERYTHING IS OK BUT WHEN I CONNECT R1 TO R2 AND R1 TO SWITCH2 THEN COMMINICATION STOP.

WHEN I REMOVE BOTH THE LINK THEN AGAIN EVERY THING IS OK

PASSWORD PACKET TRACER IS cisco when asked

hsrp ip 172.16.32.3 group number 10

please do needul so that i am able to confiure the same with both link.

Please rename the file hsrp.pkt

Regards

Brijendra

Predrag Jovic · ‎08-31-2017

Now if you don't configure the priority, both devices will be working as active

Not really, if priority on all devices is the same (for example default 100) devices will use IP addresses as a tie breaker, device with highest IP address will become active router, other devices become standby routers.

Typically, split brain situation, where both devices act as active routers is when routers do not receive hrsp hellos from its neighbors.

In the first configuration (hsrp.pkt) there problem is/was

R1

interface Vlan50
mac-address 00d0.ff33.8a01
ip address 172.16.32.2 255.255.0.0
standby 10 ip 172.16.32.1

R2

interface Vlan50
mac-address 0001.43ca.8601
ip address 172.16.32.1 255.255.0.0
standby 10 ip 172.16.32.3

Different standby IP addresses configured for the same HSRP group, and standby address on one of ther devices is the same as interface address on other device.

In lab hsrp.pkt I am getting warning about native VLAN mismatch. Native VLAN mismatch can lead to network loops. Please resolve that issue in your lab.

View solution in original post

Julio E. Moisa · ‎08-30-2017

Hi,

Can you paste the configuration on a notepad? Im not able to ready the file.

Thank you

:-)

>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

brijendrasaini · ‎08-30-2017

r1

Switch>en

Switch>enable

Password:

Switch#show run

Building configuration...

Current configuration : 1511 bytes

!

version 12.2

no service timestamps log datetime msec

no service timestamps debug datetime msec

service password-encryption

!

hostname Switch

!

enable secret 5 $1$mERr$hx5rVt7rPNoS4wqbXKX7m0

!

spanning-tree mode pvst

!

interface FastEthernet0/1

switchport access vlan 50

switchport mode access

!

interface FastEthernet0/2

switchport access vlan 50

switchport mode access

!

interface FastEthernet0/3

switchport access vlan 50

switchport mode access

!

interface FastEthernet0/4

!

interface FastEthernet0/5

!

interface FastEthernet0/6

!

interface FastEthernet0/7

!

interface FastEthernet0/8

!

interface FastEthernet0/9

!

interface FastEthernet0/10

!

interface FastEthernet0/11

!

interface FastEthernet0/12

!

interface FastEthernet0/13

!

interface FastEthernet0/14

!

interface FastEthernet0/15

!

interface FastEthernet0/16

!

interface FastEthernet0/17

!

interface FastEthernet0/18

!

interface FastEthernet0/19

!

interface FastEthernet0/20

!

interface FastEthernet0/21

!

interface FastEthernet0/22

!

interface FastEthernet0/23

!

interface FastEthernet0/24

!

interface GigabitEthernet0/1

!

interface GigabitEthernet0/2

!

interface Vlan1

no ip address

shutdown

!

interface Vlan50

ip address 172.16.32.1 255.255.0.0

standby version 2

standby 10 ip 172.16.32.3

!

ip classless

!

ip flow-export version 9

!

line con 0

exec-timeout 0 20

password 7 0822455D0A16

logging synchronous

!

line aux 0

!

line vty 0 4

password 7 0822455D0A16

login

!

end

r2

Current configuration : 1324 bytes

!

version 12.2

no service timestamps log datetime msec

no service timestamps debug datetime msec

no service password-encryption

!

hostname Switch

!

spanning-tree mode pvst

!

interface FastEthernet0/1

switchport access vlan 50

switchport mode access

!

interface FastEthernet0/2

switchport access vlan 50

switchport mode access

!

interface FastEthernet0/3

!

interface FastEthernet0/4

!

interface FastEthernet0/5

!

interface FastEthernet0/6

!

interface FastEthernet0/7

!

interface FastEthernet0/8

!

interface FastEthernet0/9

!

interface FastEthernet0/10

!

interface FastEthernet0/11

!

interface FastEthernet0/12

!

interface FastEthernet0/13

!

interface FastEthernet0/14

!

interface FastEthernet0/15

!

interface FastEthernet0/16

!

interface FastEthernet0/17

!

interface FastEthernet0/18

!

interface FastEthernet0/19

!

interface FastEthernet0/20

!

interface FastEthernet0/21

!

interface FastEthernet0/22

!

interface FastEthernet0/23

!

interface FastEthernet0/24

!

interface GigabitEthernet0/1

!

interface GigabitEthernet0/2

!

interface Vlan1

no ip address

shutdown

!

interface Vlan50

ip address 172.16.32.2 255.255.0.0

standby version 2

standby 10 ip 172.16.32.3

!

ip classless

!

ip flow-export version 9

!

line con 0

!

line aux 0

!

line vty 0 4

login

!

end

Julio E. Moisa · ‎08-30-2017

Hi

I assume the switches are interconnected through an uplink and the ports assigned to the vlan 50.

Now I see the following on the DHCP configuration, it should be:

interface Vlan50
ip address 172.16.32.1 255.255.0.0
standby version 2
standby 10 ip 172.16.32.3
standby 10 preempt
standby 10 priority 105

interface Vlan50
ip address 172.16.32.2 255.255.0.0
standby version 2
standby 10 ip 172.16.32.3
standby 10 preempt

By default the HSRP priority is 100, a higher priority is always preferred to be the active device and the other device will be the standby. Now if you don't configure the priority, both devices will be working as active, you can see that through: show standby vlan 50.

So you need to assign a device as active to enable the redundancy. If the device active fails, the standby will take the active role, now imagine the previous active device is up again, the preempt command will be in charge to remove the active status to the current device and assign the role back to the primary device (the previous active)

Hope it is useful

:-)

>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

brijendrasaini · ‎08-31-2017

hi julio,

What happen actual when i connect the switch from another switch and from router r1 to switch 2 then whole network jam.

That i ment to say in packet tracer all port link blink immediatlety.

I do not congifure switch direct connect without any configuration.

brijendrasaini · ‎08-31-2017

Dear Julio,

This is the structure when i connect the switch that start network jam or might be loop.

Predrag Jovic · ‎08-31-2017

Predrag Jovic · ‎08-31-2017

Now if you don't configure the priority, both devices will be working as active

Not really, if priority on all devices is the same (for example default 100) devices will use IP addresses as a tie breaker, device with highest IP address will become active router, other devices become standby routers.

Typically, split brain situation, where both devices act as active routers is when routers do not receive hrsp hellos from its neighbors.

In the first configuration (hsrp.pkt) there problem is/was

R1

interface Vlan50
mac-address 00d0.ff33.8a01
ip address 172.16.32.2 255.255.0.0
standby 10 ip 172.16.32.1

R2

interface Vlan50
mac-address 0001.43ca.8601
ip address 172.16.32.1 255.255.0.0
standby 10 ip 172.16.32.3

Different standby IP addresses configured for the same HSRP group, and standby address on one of ther devices is the same as interface address on other device.

In lab hsrp.pkt I am getting warning about native VLAN mismatch. Native VLAN mismatch can lead to network loops. Please resolve that issue in your lab.

brijendrasaini · ‎09-01-2017

Dear Predrag,

issue in vlan,as i correct it all things are working fine thanks a lot.

Regards

Brij

Predrag Jovic · ‎09-01-2017

I am glad to hear it. You're welcome.