HSRP issue

[Sir Asvald]

So I'm working on lab on packet tracer, I've assigned all the standby configs and all that. I'm having an issue where I'm getting this message every few seconds

%IP-4-DUPADDR: Duplicate address 192.168.1.1 on FastEthernet0/1, sourced by 0000.0C07.AC00

%IP-4-DUPADDR: Duplicate address 192.168.1.1 on FastEthernet0/1, sourced by 0000.0C07.AC00

%IP-4-DUPADDR: Duplicate address 192.168.1.1 on FastEthernet0/1, sourced by 0000.0C07.AC00

 

I'll upload the file if anyone want's to look at it. 

HSRP2.pkt

[Lurick]

Can you post a snippet of just the VLAN/HSRP configs for one VLAN?

[Sir Asvald]

17 minutes ago, Lurick said:

Can you post a snippet of just the VLAN/HSRP configs for one VLAN?

There are no VLANs? 

 

 

[Sir Asvald]

NVM got it working. 

[Lurick]

2 minutes ago, Abdul201588 said:

There are no VLANs? 

 

 

Ah, so you're doing it on two interfaces. So used to doing HSRP on vlan interfaces  

 

What IP addresses are you using on the interfaces?

Do you have both sides in the same HSRP group?

[Sir Asvald]

6 minutes ago, Lurick said:

Ah, so you're doing it on two interfaces. So used to doing HSRP on vlan interfaces  

 

What IP addresses are you using on the interfaces?

Do you have both sides in the same HSRP group?

I was following this guide.

 

Btw I've created a DHCP server on "R1" and I'm not get any ip addresses, would it work if i used ip helper address?

 

[Lurick]

Just now, Abdul201588 said:

I was following this guide.

 

Btw I've created a DHCP server on "R1" and I'm not get any ip addresses, would it work if i used ip helper address?

 

 

Yah, if the DHCP server isn't locally connected you need to use IP Helper

[Sir Asvald]

1 minute ago, Lurick said:

 

Yah, if the DHCP server isn't locally connected you need to use IP Helper

R1 is configured to give out IPs. So if the interface went down, how would it work?

[Lurick]

Just now, Abdul201588 said:

R1 is configured to give out IPs. So if the interface went down, how would it work?

IPs wouldn't get handed out if there isn't another path or another server  

[Sir Asvald]

2 minutes ago, Lurick said:

IPs wouldn't get handed out if there isn't another path or another server  

Okay Here's the diagram. 

 

If the interface F0/1 on R1 went down. How would I get the IPs. 

[Lurick]

Just now, Abdul201588 said:

Okay Here's the diagram. 

 

If the interface F0/1 on R1 went down. How would I get the IPs. 

It should go out Fa0/1 on S1 instead of Fa0/24 and then over and up

[Sir Asvald]

2 minutes ago, Lurick said:

It should go out Fa0/1 on S1 instead of Fa0/24 and then over and up

Mistake. I meant F0/0. Sorry  

 

EDIT: Talking about the router on the left. 

[Lurick]

Just now, Abdul201588 said:

Mistake. I meant F0/0. Sorry  

Ah, then it would just go out Fa0/24 on S1 and up. So long as the link between the two switches doesn't go down along with a link to the router you're still good.

[Sir Asvald]

4 minutes ago, Lurick said:

Ah, then it would just go out Fa0/24 on S1 and up. So long as the link between the two switches doesn't go down along with a link to the router you're still good.

I got it working. I setup DHCP on the secondary router.  same config. 

 

Thanks for the help.

[NZLaurence]

On the Cisco dhcp isn't tied to the physical interface, its tied to the IP subnet of the helper interface.

 

When an router receives a request for an IP from a dhcp client it will try to match it to an "ip dhcp pool" with a network statement that matches the subnet of the interface that first received the request.

 

E.g. if Router1 receives a request on Fa0/1 which has an IP of 192.168.1.1/24 it will look for a IP pool with a "network 192.168.1.0/24" statement.

 

If the same router then has a IP helper set to point to Router2 and then receives a request on the same interface (fa0/1 192.168.1.1/24) it will forward that request to router2 and router2 will look for an IP pool with a "network 192.168.1.0/24" statement even if there are no interfaces configured on router2 in that subnet.

 

Using this your requests will follow standard layer3 routes to get between thee two routers. This means that if there is redundant links between the two router using rip it will follow the routes.

 

Protip, use loopback addresses injected into your dynamic routing protocol to give the router2 an address that never goes down so that no matter which link has issues its always reachable.

 

Sorry for formatting, sent from a tiny screen with an imagery keyboard.