cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
712
Views
0
Helpful
3
Replies

HSRP Design question

Scott Brien
Beginner
Beginner

Hi,


I have recently undertaken a project for which i am to re-design our border network  for our customers and  infrastructure.

The design which i have in mind is as follows:

1) Customer WAN comes in on layer 2 on our customer agg switch  and terminates in their own VFW where they can access the infrastructure required

2) a /30 public address space is assigned with 1 address on the outside IF of the VFW and the other on our border router which is connected via a trunk to our core switches.

My issue here is how we are to configure redundancy between our 2 border routers which are geographically seperated over a L2 WAN.

The border routers are multihomed HSRP would need to be active standby not load sharing.

Any assistance/thoughts would be appreciated on this one.

Thanks,
Scott

3 Replies 3

darren.g
Contributor
Contributor

Scott Brien wrote:

Hi,


I have recently undertaken a project for which i am to re-design our border network  for our customers and  infrastructure.

The design which i have in mind is as follows:

1) Customer WAN comes in on layer 2 on our customer agg switch  and terminates in their own VFW where they can access the infrastructure required

2) a /30 public address space is assigned with 1 address on the outside IF of the VFW and the other on our border router which is connected via a trunk to our core switches.

My issue here is how we are to configure redundancy between our 2 border routers which are geographically seperated over a L2 WAN.

The border routers are multihomed HSRP would need to be active standby not load sharing.

Any assistance/thoughts would be appreciated on this one.

Thanks,
Scott

It's difficult to configure HSRP with only a /30 to play with - with two interfaces, you typically need a minimum of 3 addresses (one for each interface and one for the floating "virtual" node).

If you can get a /29 to play with on your edge connection, just configure HSRP normally and configure one router to preempt always - lower the priority so it always takes the "master" role, and configure it to preempt so if it does go down, it will always take the virtual address back as soon as it stabilises after boot/restart.

HSRP supposedly does not do load sharing by default, so you should be OK if you configure your "main" router with the highest priority and absolute rights to preempt the HSRP group.

Of course, if you can't get a /29 to play with, this gets more sticky. :-)

Off hand, I can't think of a way to make this work when you've only got one IP address to play with - not without manual intervention. You could configure the same IP detaisl on both edge routers and leave one interface shutdown (run them in a VLAN and use an SVI to traffic will pass across your layer 2 WAN), but I can't offer anything better than that - I'll watch to see if some other genius can. :-)

Cheers

Hi Darren,

My thoughts exactly, I initially designed this using EIGRP for the internal networks and BGP on the Border + HSRP.

But L2 right to the border just seemed a lot nicer.

We have the space to use /29 just whether or not we want to use that per customer.

I Suppose we could automate that manual work which you mentioned but I would prefer to just give an additional set of addresses and have redundancy/failover without our intervention.

Scott

Hi Scott

Is the VFW Gateway for the Customer LAN Users also ? Seems so to me.

From reading above I can visualise the network setup to be as below:

                                               WAN/ Internet        WAN/Internet

                                                     !                               !

                                                  BGR1                       BGR2   

                                                     !                                !

                                                    L2                             L2

                                                     !                                !

                                                           !                   !

                                                                 AGG_SW

                                                                       !

                                                            Outside_IF_VFW

                                                                       !

                                                                    VFW

                                                                       !

                                                                 LAN_GW

                                                                       !

                                                                 LAN_USRs

If the above setup is correct and we have a requirement of LAN_to_LAN communication between different Sites HSRP will not be a good solution in my opinion as It will invoke use of Static Routing along it which again is not good for big setups. For smaller setups we can survive though. Using HSRP in the LAN for the LAN_GW is fine as that's the best deal to cut for the LAN but using HSRP for WAN is an off. Rather we should look for routing protocols to achieve the required redundacny (A:S),load-balancing (A:A) or any other desired routing. BGP would be the best option and yes this would definotely invite you to incure another X /30 for the 2nd  BGR and anyways a X/29 is needed for the HSRP. So personally I would recommend to use Dynamic Routing Protocols over WAN rather than HSRP with Static Routing.

Hope this helps to provide some inputs on your design consideration.

Regards

Varma

Getting Started

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:

Recognize Your Peers