04-24-2016 11:29 PM - edited 03-08-2019 05:29 AM
Dear Community
this will work.
Core 1
interface Vlan404
description XYZ
ip address 125.10.X.X 255.255.252.0
no ip redirects
no ip mroute-cache
standby preempt
standby 1 ip 125.10.X.X
end
interface Vlan100
description 10.208.X.X Produktion
ip address 10.208.X.X 255.255.252.0
no ip redirects
standby preempt
standby 1 ip 10.208.X.X
end
Core 2
interface Vlan404
description XYZ
ip address 125.10.X.X 255.255.252.0
no ip redirects
standby 1 ip 125.10.X.X
interface Vlan100
description XYZ
ip address 10.208.X.X 255.255.252.0
no ip redirects
standby 1 ip 10.208.X.X
end
Core 3
interface Vlan404
description XYZ
ip address 10.208.X.X 255.255.255.0
no ip redirects
shutdown
standby 104 ip 10.108.X.X
standby 104 priority 110
standby 104 preempt
standby 104 authentication md5 key-string 7 XXXXXXXXXXXXXXX
end
interface Vlan100
description XYZ
ip address 10.208.X.X 255.255.252.0
no ip redirects
shutdown
standby 100 ip 10.208.X.X
standby 100 priority 110
standby 100 preempt
standby 100 authentication md5 key-string 7 XXXXXXXXXXXXXXXXXXXXXXX
Core 4
interface Vlan404
description XYZ
ip address 10.208.X.X 255.255.255.0
no ip redirects
shutdown
standby 104 ip 10.108.X.X
standby 104 priority 90
standby 104 authentication md5 key-string 7 XXXXXXXXXXXXXXX
end
interface Vlan100
description XYZ
ip address 10.208.X.X 255.255.252.0
no ip redirects
shutdown
standby 100 ip 10.208.X.X
standby 100 priority 90
standby 100 authentication md5 key-string 7 XXXXXXXXXXXXXXXXXXXXXXX
No other solution, thanks.
Solved! Go to Solution.
05-04-2016 12:48 AM
hey was off last few days
Yes you would use an AD Administrative distance like below to specify which is used first the higher the AD is the less preferred route so it wont join the table until the other route is invalid , AD of 220 set for backup route
ip route 10.208.x.x 255.255.255.0 125.x.x.1
ip route 10.208.x.x 255.255.255.0 125.x.x.2 220
http://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/15986-admin-distance.html
04-25-2016 12:33 AM
If your going to use authentication I would put it under each vlan, I would also add preempt to each vlan interface , HSRP groups can have up to 6 routers so you can have 1 group instead of 2 but means only 1 active router at a time
This is a typo I presume its not in same subnet so wont work
interface Vlan404
description XYZ
ip address 10.208.X.X 255.255.255.0
no ip redirects
shutdown
standby 104 ip 10.108.X.X
The other option is to have them all in same GLBP group and load balance across each router so theres no routers sitting there waiting to become active
04-25-2016 01:41 AM
Hi Mark,
Thanks for your quick reply.
"If your going to use authentication I would put it under each vlan, I would therefore add to preempt each vlan interface" I understand.
I'm going to all the interface Add preemt.
To:
interface Vlan404
description XYZ
ip address 255.255.255.0 10.208.X.X
no ip redirects
shut down
standby 104 ip 10.108.X.X <<<< here I typed an error.
Correct:
interface Vlan404
description XYZ
ip address 255.255.255.0 10.208.X.X
no ip redirects
shut down
standby 104 ip 10.208.X.X
so I'm going all over the Vlan Int adden the authentication.
Did I understand you correctly.
Excuse me for my bad englich.
04-25-2016 02:13 AM
Hi
Yes so if using authentication I would apply it to each vlan interface so its consistent across the HSRP groups , it is an optional command but if your using it on one vlan i would put it on the other vlans too
Its best practice to have preempt on each router not just the active router
1 Add pre-empt to each vlan interface
2 If using authentication use it on each vlan
04-25-2016 04:23 AM
Hi Mark,
Have you well understood, the conversion is on Thursday.
I will later give a feedback, thanks in advance.
05-01-2016 11:15 PM
Hi Mark,
the transition is complete.
However, I had to leave the interface on the Core1 and Core2.
Because the internal routing did not work.
Now I have such a result with which I disagree.
I have two gateway for a network.
ip route 10.208.x.x 255.255.255.0 125.x.x.1 ( Core1)
ip route 10.208.x.x 255.255.255.0 125.x.x.2 ( Core2)
how can I assign my prio to the interface 125.x.x.1.
and only when the link is gone to the 125.x.x.2 10
I Do it with metric or with distanc?
I think of HSRP is but in a month which, until then I have to so rule.
The network is s very complex and can maintenance work always ca be made in a month.
with best thanks.
05-04-2016 12:48 AM
hey was off last few days
Yes you would use an AD Administrative distance like below to specify which is used first the higher the AD is the less preferred route so it wont join the table until the other route is invalid , AD of 220 set for backup route
ip route 10.208.x.x 255.255.255.0 125.x.x.1
ip route 10.208.x.x 255.255.255.0 125.x.x.2 220
http://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/15986-admin-distance.html
05-04-2016 04:00 AM
HI Mark,
I have a current similar set up. I have two routers and L3 catalyst switch.
Plan to have redundancy using hsrp creating 2 standby groups on two routers but have one group of vlan has the primary route to R1 and others to R2.
L3 switch has intervlan routing and management vlan as well.
from L3 switch : static ip route for a certan vlan to use gateway IP address on a svi of standby grp 1 (r1) and static Ip route for another vlan use gateway IP address on a svi standby group 2(r2). route doesn't work.
it works only if I have default route configures ip route 0.0.0.0 0.0.0.0 10.xxx
how would I be able to make it work what I intended to.. I have tried the static route from the routers layer as well.
05-04-2016 04:10 AM
Hi
have you made the 2 groups active either side ? , can you post the HSRP config of both sides and any other relevant config and il take a look
another option is GLBP and load balance across both routers with just 1 group
05-04-2016 04:17 AM
Standby group 1 ( 10.x.x.1) is active on r1 and standby group 2 (10.x.x.2) is active on r2.
I just wanted to have a specific vlan to have primary route to one r1 and other vlans to have primary route to r2
so glbp is probably not an option.
05-04-2016 06:02 AM
That sounds as if you have design side setup correct without seeing any configs I cant really make much assumptions what could be wrong , maybe the client end have the wrong vip set , statics could be wrong etc hard to know without seeing anything
Heres a couple of docs based on what your trying to achieve
https://cciethebeginning.wordpress.com/2008/08/27/mhsrp-and-load-sharing/
http://www.cisco.com/c/en/us/support/docs/ip/hot-standby-router-protocol-hsrp/13781-7.html
05-04-2016 04:54 AM
Hi Mark,
holiday is good, be offline is better;-)
Super, hate me read something, but I wanted to make sure about your info.
I see that this issue is very much in demand.
Get it so up until I get the opportunity for an HSRP
I thank you for your support, all good now.
Mustafa
05-02-2016 01:42 AM
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
Hi Mark,
the transition is complete.
However, I had to leave the interface on the Core1 and Core2.
Because the internal routing did not work.
Now I have such a result with which I disagree.
I have two gateway for a network.
ip route 10.208.x.x 255.255.255.0 125.x.x.1 ( Core1)
ip route 10.208.x.x 255.255.255.0 125.x.x.2 ( Core2)
how can I assign my prio to the interface 125.x.x.1.
and only when the link is gone to the 125.x.x.2 10
I Do it with metric or with distanc?
I think of HSRP is but in a month which, until then I have to so rule.
The network is s very complex and can maintenance work always ca be made in a month.
with best thanks.