VRRP question

How come when I configure VRRP on my vlans, I can no longer reach them? For ex. I have 2 switches, one Core an other Backup. Both configured with SVI's. I configure VRRP per vlan with the following syntex:

CORE 1
int vl 1
ip add 192.168.1.1
vrrp 1 ip 192.168.1.1

BACKUP
int vl 1
ip add 192.168.1.2
vrrp 1 ip 192.168.1.1

After the above config, I cannot reach the vlans from hosts at all. Any ideas? What am I doing wrong? Both switches are connected as a trunk
LVL 3
Shark AttackNetwork adminAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Don JohnstonInstructorCommented:
When you say "cannot reach the vlans from hosts", what do you mean?  Which VLAN is this host on and what VLAN is it trying to reach?

I'm assuming that everything works fine without the VRRP config?

Do you have VRRP configured on the other VLANs?
0
NetExpert Network Solutions Pte LtdTechnical SpecialistCommented:
Your Vlan interface ip address and VRRP address should not be same ... Check your core 1 vlan config
0
Shark AttackNetwork adminAuthor Commented:
I have VRRP configured on all vlans the same way. Without VRRP I get instant reply back. With VRRP I don't. For ex. I have a vlan 5 below

Core:
Int vl 5
ip 10.153.0.1
vrrp 1 ip 10.153.0.1

BACKUP
int vl 5
ip 10.153.0.2
vrrp 1 ip 10.153.0.1

I have a host on the vlan with an IP 10.153.0.15. When I ping 10.153.0.1,  or .2 I get no reply back. When I remove VRRP configs, I get back the connection.
0
Cloud Class® Course: C++ 11 Fundamentals

This course will introduce you to C++ 11 and teach you about syntax fundamentals.

NetExpert Network Solutions Pte LtdTechnical SpecialistCommented:
Zack,

Check your core vlan 5 configuration... Vlan interface IP address should be different than VRRP IP address

Change the core switch config like below

Vlan 5
IP address 10.153.0.3
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Shark AttackNetwork adminAuthor Commented:
by the way I  created the scenario in GNS3, are my configs correct? This could be GNS3 issue i guess but I am going ti implement VRRP to my network and wanted to see if I can give it a try in GNS3 first
0
Shark AttackNetwork adminAuthor Commented:
NetExper: I am using VRRP which enables me to use the same Ip address of the interface as a virtual interface. Thats the reason why I'm going with VRRP and not HSRP
0
Don JohnstonInstructorCommented:
Okay.

I'm guessing that you have fallen into the trap created by a statement in some Cisco documents which reads:

Because the virtual router uses the IP address of the physical Ethernet interface
and they show the physical IP address being the same as the virtual IP address.

As previously stated, this is incorrect. So if you change to something like:

CORE 1
int vl 1
 ip add 192.168.1.3
 vrrp 1 ip 192.168.1.1

Open in new window


BACKUP
int vl 1
 ip add 192.168.1.2
 vrrp 1 ip 192.168.1.1

Open in new window


That should get VRRP working.  Not sure if that's what is causing your connectivity issue though.  But it does need to be fixed.
0
Shark AttackNetwork adminAuthor Commented:
It worked when I made the change.

So, I cannot use the same IP as a SVI for VRRP IP? What If I had physical interface and used that as an IP of the VRRP? Would this also be an issue?
0
Don JohnstonInstructorCommented:
Yes.  You do not use the same IP address for the virtual router as you do for the interface. Regardless of whether it's a physical interface or SVI.
0
Shark AttackNetwork adminAuthor Commented:
OK, well that changes everything, might as well use HSRP.

Let me as you one more question. When I configured HSRP first on each of the vlans, and I drop the primary vlan, The backup switch goes to ACTIVE but the hosts don't re-direct to the virtual IP. For ex. I have "no ip routing" on the host with ip default-gateway pointing to the virtual HSRP address but when I do traceroute, it still shows the actual IP of the interface vlan. I can ping the virtual IP though, so not sure why this is happening. I also have ip sla configured but only for the vlan thats a native vlan on the trunk. Do I need to make ipsla with tracking for all vlans in this case for it to work?
0
Don JohnstonInstructorCommented:
Let me as you one more question. When I configured HSRP first on each of the vlans, and I drop the primary vlan,
What do you mean by "drop the VLAN"?
when I do traceroute, it still shows the actual IP of the interface vlan.
Correct. The router will respond to the traceroute with its own address.
0
Shark AttackNetwork adminAuthor Commented:
looks like it's working now, dont know about the new GNS3. It's pretty buggy. I have to reset the ASA at least 5 times before all interfaces work.

Thank you all for you help!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Switches / Hubs

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.