[c-nsp] network design question

Wed Sep 6 16:35:13 EDT 2006

Though, the mac used isn't virtual, it's the first physical mac address
available from ethN. 

Steve

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Scott Granados
Sent: Wednesday, September 06, 2006 1:13 PM
To: Robert D. Holtz - Lists; Cisco-NSP Mailing List
Subject: Re: [c-nsp] network design question

We're using Broadcom nics although linux loads intel drivers so I can
dig in to that side of things.

Thanks for the pointers.

G. Scott Granados
Sr. Network Operations Specialist
OFFICE: 415-946-2112 EXT. 222
CELL: 408-569-4017
URL: http://www.jeteye.com

-----Original Message-----
From: Robert D. Holtz - Lists [mailto:robert.d.holtz at gmail.com] 
Sent: Wednesday, September 06, 2006 12:39 PM
To: Scott Granados; 'Cisco-NSP Mailing List'
Subject: RE: [c-nsp] network design question

You can team up the NICs.

If the NICs you do have don't support teaming then it may be worth the
investment to get some that do.  Most likely they do ... this is getting
pretty common.  You may have to dig a little but I have found the
teaming
software available for the Broadcom chipset and *nix.

This will set up a virtual MAC (VMAC) address on the machine and the two
real MAC addresses become "invisible" to the outside world.  You then
associate the IP address with VMAC.

This has the added benefit of load balancing when both connections are
running.

The switch side would have HSRP running as one possible option.

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Scott Granados
Sent: Wednesday, September 06, 2006 2:11 PM
To: Cisco-NSP Mailing List
Subject: [c-nsp] network design question

Hi, I'm looking for some pointers on what technology or methods to use
here.

I'm designing a new network for my company and have run in to a problem
which I'm sure a solution exists to address but I didn't know where to
start.  I have two core switches (4506's) each with supervisor 4's
(wsx4515) and each has 3 wsx4548 cards installed making a total of 144
ports each.  Now, much of our architecture has several servers so for
example, we might have 4 application servers.  My plan was to place 2 on
switch a and two on switch b so if either switch fails, I only lose part
of my application serving ability.  However, suppose we have a master
mysql server but it's only attached to switch a.  If switch a dies then
the entire application dies as there is no path for data.  My servers
all have 2 gig NIC's.  Would it be possible to attach the mysql master
to both A and B and use some method that allows either card to be
reached by the same IP.  Clearly, having two ips would be simple but our
application does not have a means to connect to more than one DB.  Is
there a clean way that say switch A dies so then nic A no longer
functions so nic B takes the remaining traffic left on switch B headed
for the same ip of the database master?  What are people using for fail
over in the event of switch failures?

Thanks

G. Scott Granados

Sr. Network Operations Specialist

OFFICE: 415-946-2112 EXT. 222

CELL: 408-569-4017

URL: http://www.jeteye.com

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/