<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The router should be able to do it pretty easily. We’ve got a
lot of those switches, and while I’m not routing between the subnets, I know that
it is a core functionality of them. My primary suggestion is to make sure you
talk to the correct people at dell. There Is a specific team of people that has
expertise in the higher end switches. Don’t accept dell’s typical front end
support guys.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Mark<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
nflug-bounces@nflug.org [mailto:nflug-bounces@nflug.org] <b>On Behalf Of </b>Richard
Hubbard<br>
<b>Sent:</b> Wednesday, July 09, 2008 10:28 AM<br>
<b>To:</b> nflug@nflug.org<br>
<b>Subject:</b> Re: [nflug] Routers switches and the urge to get very vocal
with aDell tech support rep<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>That's what we're trying now. Apparently, the tech support
guy that was working with us initially has been fired because he's and
idiot. <br>
<br>
The one we're working with now seems to have more active brain cells...<o:p></o:p></p>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<p class=MsoNormal><span style="font-family:comic sans
ms;">Richard Hubbard </span><br>
ATTO Technology Inc<o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>-----
Original Message ----<br>
From: Darin Perusich <Darin.Perusich@cognigencorp.com><br>
To: nflug@nflug.org<br>
Sent: Wednesday, July 9, 2008 9:10:34 AM<br>
Subject: Re: [nflug] Routers switches and the urge to get very vocal with a
Dell tech support rep<br>
<br>
If your switch ports are not tagged properly then traffic will not route <br>
across VLAN's. Also any downstream switches must also have the VLANS <br>
configured and uplink ports properly tagged as well. I'd start by <br>
getting two subnets talking to each other only on this layer3 switch <br>
before complicating it by adding downstream switches.<br>
<br>
Richard Hubbard wrote:<br>
> We were setting up vlans, but we could only get a particular subnet to <br>
> talk to itself. we had no ip packet forwarding in the layer 3 switch <br>
> between subnets...which is what a router is supposed to do.<br>
> <br>
> <br>
> <br>
> ----- Original Message ----<br>
> From: Darin Perusich <<a href="mailto:Darin.Perusich@cognigencorp.com">Darin.Perusich@cognigencorp.com</a>><br>
> To: <a href="mailto:nflug@nflug.org">nflug@nflug.org</a><br>
> Sent: Wednesday, July 9, 2008 8:25:30 AM<br>
> Subject: Re: [nflug] Routers switches and the urge to get very vocal <br>
> with a Dell tech support rep<br>
> <br>
> I'm not sure about Dell switchs but I need to configure VLAN's on my<br>
> 3com switches to segment the various subnets. Have you tried this?<br>
> <br>
<br>
<br>
-- <br>
Darin Perusich<br>
Unix Systems Administrator<br>
Cognigen Corporation<br>
395 Youngs Rd.<br>
Williamsville, NY 14221<br>
Phone: 716-633-3463<br>
Email: <a href="mailto:darinper@cognigencorp.com">darinper@cognigencorp.com</a><br>
_______________________________________________<br>
nflug mailing list<br>
<a href="mailto:nflug@nflug.org">nflug@nflug.org</a><br>
<a href="http://www.nflug.org/mailman/listinfo/nflug" target="_blank">http://www.nflug.org/mailman/listinfo/nflug</a><o:p></o:p></span></p>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Internal
Virus Database is out of date.<br>
Checked by AVG - http://www.avg.com<br>
Version: 8.0.136 / Virus Database: 270.4.5/1535 - Release Date: 7/4/2008 5:03
PM</span><o:p></o:p></p>
</div>
</body>
</html>