Hello Nimal - you can use redundant interfaces with 802.1q and have link from fw1 to sw1 and sw2 and vice versa
so fw1 active interface is connected to switch 1 and standby interface connect to switch 2, fw2 active interface to switch 2 and standby interface to switch 1, this way if fw1 and sw2 fail, fw2 standby interface becomes active to switch 1 hope this helps -christian On Wed, Jun 25, 2008 at 8:20 PM, Nimal David Sirimanne <[EMAIL PROTECTED]> wrote: > Hello, > > We;'re trying to setup a network with 2 Cisco ASA (5510) and 2 Cisco 2950 > switches. In event that any firewall kaputs, the other will take over (we > havent decided on active/active or active/standby configuration yet). Also, > all the servers on the internal network are performing "network teaming" , > so even if one switch dies, traffic will pass through other traffic > > FW1 -- SW1 --| > | | FW2 -- SW2 --| > > My question is, what if for some freak reason FW1 AND SW2 dies > simultaneously. In this scenario, network is totally down unless we do some > manual recabling. I understand that this might never ever happen, but i > would like to see how i can plan for this, because this network is to be > deployed in a remote location, where there might not be any IT people around > to assist. > > Appreciate any advise, or ideas on this. Thanks! > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
