kseich at gmail
Apr 30, 2012, 12:33 PM
Post #3 of 4
Thank Scott, I will take a look at that. 32 might just be enough for what
Re: Handling redundancy between buildings.
[In reply to]
we want to accomplish.
On Mon, Apr 30, 2012 at 3:31 PM, Scott Voll <svoll.voip [at] gmail> wrote:
> run your 3750's in a HSRP setup. weight the one in the building to be
> primary for the vlan's in that building and do the oppisite in the other
> we do it here and it works pretty slick.
> Not knowing the size of your buildings.... it is possible to run out of
> HSRP instances. I think we topped our 3750E off at 32.
> Not sure what your looking at for total vlans.
> On Mon, Apr 30, 2012 at 12:08 PM, Kevin Seich <kseich [at] gmail> wrote:
>> We have 2 buildings on our Campus right next to each other. They are
>> connected by 10 Gb fiber pulls. Each building has it's own generator and
>> UPS. Each building has it's own ISP. We have an ASA 5520 failover pair,
>> one in each building. We have 2 - 3750x stacked in each building as a
>> core. We are currently a flat network, a /16. We are in the
>> design/brainstorming phase of segmenting this into vlans. We'd like to
>> take the burden off the ASA for routing and do all inter vlan routing on
>> the 3750s. From what we can see, you cannot treat the 3750s as a failover
>> pair, like the ASAs. What are our options in segmenting this?
>> 1 We can do all routing on the ASAs. This would achieve the same
>> redundancy we have now, but put the burden on the ASA for routing all
>> 2 Put the routing on the 3750 stack. This would essentially break our 2
>> buildings into separate networks, separate , non-overlapping vlans in each
>> building. reconfigure services to talk across the buildings and vlans.
>> 3 put in routers behind the ASAs that handle all the vlan routing. These
>> function in a failover pair. this keeps the redundancy we are looking for
>> but we are not utilizing the layer 3 capability that we paid for on the
>> Are there other options? What have you guys/girls done?
>> Looking for any other input you have just to spark the design creativity.
>> Thank you !
>> cisco-nsp mailing list cisco-nsp [at] puck
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
cisco-nsp mailing list cisco-nsp [at] puck
archive at http://puck.nether.net/pipermail/cisco-nsp/