Missed the list last time with this. Anyway, more thoughts on tagged vs. untagged, it should help you Brendan.<br><br>---------- Forwarded message ----------<br><span class="gmail_quote">From: <b class="gmail_sendername">
Mike Allen</b> <<a href="mailto:mkallen@gmail.com">mkallen@gmail.com</a>><br>Date: Dec 7, 2005 9:03 AM<br>Subject: Re: [f-nsp] Cisco 3550 to FESX424<br>To: Tine Hutchison <<a href="mailto:foundry-nsp@well-duh.net">
foundry-nsp@well-duh.net</a>><br><br></span>
<div>One important tip I can offer, that catches most new people making the transition from Cisco, you cannot create a ve/router interface without first having ports assigned into the vlan. It gets everybody the first time, the error message is kind of non-specific........Also, a little about tagged vs. untagged. Tagged means you expect to see, and will send, an
802.1q tag on every packet on an interface. Any untagged traffic rcvd on that interface will be dropped. Tagged maps </div><span class="q">
<div> </div>
<div><font size="2">switchport trunk encapsulation dot1q</font> </div>
<p><font face="Arial"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> switchport mode trunk</span></font></p></span>
<div>Tag ports typically go to other switches. Untagged means you don't expect, nor will you tag any packets with an 802.1q tag on that interface. Likewise, any tagged traffic will be dropped. (Before anyone says it, yes, dual mode will get around both of these general rules). Untagged would be where you plug in any workstations/servers/pc's. Untagged roughly maps to
</div><span class="q">
<div> </div>
<div><font size="2">switchport access vlan 4</font> </div>
<p><font face="Arial"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> switchport mode access</span></font></p></span>
<div>One last thing to note. On Foundry switches, you must specify which vlans are on what would be a 'cisco trunk', by tagging those ports into each vlan. Best of luck.</div><span class="sg">
<div> </div>
<div>Mike<br> </div></span>
<div><span class="e" id="q_108062d098040c19_6">
<div><span class="gmail_quote">On 12/6/05, <b class="gmail_sendername">Tine Hutchison</b> <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:foundry-nsp@well-duh.net" target="_blank">foundry-nsp@well-duh.net
</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Two things to know that will probably get you most of the way there.<br><br>1) VLAN assignment is handled in the vlan config and not the interface config.
<br>2) vlan interfaces are created in the vlan config and are called 've' virtual<br>ethernet.<br><br>i.e.<br>vlan 4<br>spanning-tree 802-1w<br>tagged e 4<br>router-interface ve 22<br><br>interface ve 4<br>port-name cust 4
<br>ip address <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://1.2.3.4/30" target="_blank">1.2.3.4/30</a><br>ip access-group 123 in<br>...<br>...<br><br>I don't use any sort of traffic policing, so I'm not sure how you'd do that.
<br><br>You should know in advance that the FESX doesn't do outbound ACLs and never <br>will. You don't have any ACLs in your example, but it is something to<br>be aware<br>of.<br><br>Tine<br><br>Quoting Brendan Mannella <
<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:bmannella@g3tech.net" target="_blank">bmannella@g3tech.net</a>>:<br><br>> Hello, <br>><br>><br>><br>> I have been reading the list for a while now and finally decided to purchase
<br>> a FESX424-PREM to replace my Cisco 3550-EMI.<br>><br>><br>><br>> I am having a hard figuring out how to convert my Cisco config into a <br>> Foundry Config.<br>><br>><br>><br>> interface FastEthernet0/22
<br>><br>> description Uplink to Cust Colo Switch<br>><br>> switchport access vlan 4<br>><br>> switchport mode access<br>><br>> service-policy input 1Mbit-in<br>><br>> service-policy output 1Mbit-out
<br>><br>> !<br>><br>> interface FastEthernet0/23<br>><br>> description Uplink to L2 Dedicated Server switch<br>> <br>> switchport trunk encapsulation dot1q<br>><br>> switchport mode trunk<br>
><br>> !<br>><br>> interface FastEthernet0/24<br>><br>> description Uplink to L2 Dedicated Server Switch.<br>><br>> switchport trunk encapsulation dot1q<br>><br>> switchport mode trunk<br>>
<br>><br>><br>><br>><br>> Routed Interface config on Cisco, and I have all the L2 Vlans configured via<br>> vland command. <br>><br>><br>><br>> interface Vlan7<br>><br>> description Cust 1
<br>><br>> ip address <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://111.111.111.111/" target="_blank">111.111.111.111</a> <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://255.255.255.248/" target="_blank">
255.255.255.248</a><br>><br>> !<br>><br>> interface Vlan8<br>><br>> description Cust 2<br>><br>> ip address <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://222.222.222.222/" target="_blank">
222.222.222.222</a> <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://255.255.255.252/" target="_blank">255.255.255.252</a><br>> <br>> !<br>><br>> interface Vlan9<br>><br>> description Cust 3
<br>><br>> ip address 333.333.333.333 <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://255.255.255.248/" target="_blank">255.255.255.248</a><br>><br>><br>><br>><br>><br>> Can some post a converted Foundry config just to give me a idea.
<br>><br>><br>><br>> Thanks,<br>><br>><br>><br>> Brendan<br>><br>><br><br><br><br>_______________________________________________<br>foundry-nsp mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:foundry-nsp@puck.nether.net" target="_blank">
foundry-nsp@puck.nether.net</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a>
<br></blockquote></div><br></span></div>