<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>take a read through this: http://community.brocade.com/docs/DOC-1848<br><br><br><div><div id="SkyDrivePlaceholder"></div>> From: fligor@illinois.edu<br>> Date: Tue, 9 Oct 2012 13:56:23 -0500<br>> To: eric@fusionity.com<br>> CC: foundry-nsp@puck.nether.net<br>> Subject: Re: [f-nsp] Tagged Ports<br>> <br>> <br>> On Oct 9, 2012, at 12:22, Eric Chen <eric@fusionity.com> wrote:<br>> <br>> > We're just a bit confused on this vs Cisco terminology. Apologies for the trouble<br>> <br>> "tagged" on Foundry/Brocade is "trunked" on Cisco<br>> <br>> in Foundry you put the port tagging info under the VLAN command. In Cisco you put switchport trunk under the Port, and list the allowed VLANs per port. switching back and forth between the two flavors of devices can be a tad confusing at first.<br>> <br>> The cisco equivalent to what is Richard described below on a Foundry would be<br>> <br>> interface GigabitEthernet1/1<br>> switchport access vlan 2<br>> <br>> interface GigabitEthernet1/2<br>> switchport access vlan 3<br>> <br>> interface GigabitEthernet2/1<br>> switchport<br>> switchport trunk encapsulation dot1q<br>> switchport trunk allowed vlan 2,3<br>> switchport mode trunk<br>> <br>> <br>> <br>> Hope this helps,<br>> <br>> -debbie<br>> <br>> <br>> > <br>> > Best,<br>> > Eric<br>> > <br>> > On 10 Oct, 2012, at 1:08 AM, Richard Laager <rlaager@wiktel.com> wrote:<br>> > <br>> >> The questions you're asking suggest you're new to the entire concept of<br>> >> VLANs. IMHO, this isn't really the mailing list to help with that.<br>> >> Perhaps there's someone internally there (since your domain suggests<br>> >> you're a web host) that can provide some more in-depth mentoring.<br>> >> <br>> >> As for the syntax of things, here's an example of a tagged port (e 2/1)<br>> >> with two VLANs, and two ports (e 1/1 & e 1/2) untagged on VLANs 2 and 3,<br>> >> respectively. From this example, you should be able to see how to build<br>> >> whatever you need.<br>> >> <br>> >> vlan 2<br>> >> tagged ethernet 2/1<br>> >> untagged ethernet 1/1<br>> >> <br>> >> vlan 3<br>> >> tagged ethernet 2/1<br>> >> untagged ethernet 1/2<br>> >> <br>> >> -- <br>> >> Richard<br>> > <br>> > _______________________________________________<br>> > foundry-nsp mailing list<br>> > foundry-nsp@puck.nether.net<br>> > http://puck.nether.net/mailman/listinfo/foundry-nsp<br>> <br>> -- <br>> -debbie<br>> Debbie Fligor, n9dn Lead Network Engineer, CITES, Univ. of Il<br>> email: fligor@illinois.edu <http://www.uiuc.edu/ph/www/fligor><br>> "Every keystroke can be monitored. And the computers never forget."<br>> <br>> <br>> _______________________________________________<br>> foundry-nsp mailing list<br>> foundry-nsp@puck.nether.net<br>> http://puck.nether.net/mailman/listinfo/foundry-nsp<br></div> </div></body>
</html>