Fwd: [f-nsp] Cisco 3550 to FESX424

[Mike Allen]

Missed the list last time with this.  Anyway, more thoughts on tagged vs.
untagged, it should help you Brendan.

---------- Forwarded message ----------
From: Mike Allen <mkallen at gmail.com>
Date: Dec 7, 2005 9:03 AM
Subject: Re: [f-nsp] Cisco 3550 to FESX424
To: Tine Hutchison <foundry-nsp at well-duh.net>

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

switchport trunk encapsulation dot1q

 switchport mode trunk
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

switchport access vlan 4

 switchport mode access
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.

Mike

 On 12/6/05, Tine Hutchison <foundry-nsp at well-duh.net> wrote:
>
> Two things to know that will probably get you most of the way there.
>
> 1) VLAN assignment is handled in the vlan config and not the interface
> config.
> 2) vlan interfaces are created in the vlan config and are called 've'
> virtual
> ethernet.
>
> i.e.
> vlan 4
> spanning-tree 802-1w
> tagged e 4
> router-interface ve 22
>
> interface ve 4
> port-name cust 4
> ip address 1.2.3.4/30
> ip access-group 123 in
> ...
> ...
>
> I don't use any sort of traffic policing, so I'm not sure how you'd do
> that.
>
> You should know in advance that the FESX doesn't do outbound ACLs and
> never
> will.  You don't have any ACLs in your example, but it is something to
> be aware
> of.
>
> Tine
>
> Quoting Brendan Mannella <bmannella at g3tech.net>:
>
> > Hello,
> >
> >
> >
> > I have been reading the list for a while now and finally decided to
> purchase
> > a FESX424-PREM to replace my Cisco 3550-EMI.
> >
> >
> >
> > I am having a hard figuring out how to convert my Cisco config into a
> > Foundry Config.
> >
> >
> >
> > interface FastEthernet0/22
> >
> > description Uplink to Cust Colo Switch
> >
> > switchport access vlan 4
> >
> > switchport mode access
> >
> > service-policy input 1Mbit-in
> >
> > service-policy output 1Mbit-out
> >
> > !
> >
> > interface FastEthernet0/23
> >
> > description Uplink to L2 Dedicated Server switch
> >
> > switchport trunk encapsulation dot1q
> >
> > switchport mode trunk
> >
> > !
> >
> > interface FastEthernet0/24
> >
> > description Uplink to L2 Dedicated Server Switch.
> >
> > switchport trunk encapsulation dot1q
> >
> > switchport mode trunk
> >
> >
> >
> >
> >
> > Routed Interface config on Cisco, and I have all the L2 Vlans configured
> via
> > vland command.
> >
> >
> >
> > interface Vlan7
> >
> > description Cust 1
> >
> > ip address 111.111.111.111  255.255.255.248
> >
> > !
> >
> > interface Vlan8
> >
> > description Cust 2
> >
> > ip address 222.222.222.222 255.255.255.252
> >
> > !
> >
> > interface Vlan9
> >
> > description Cust 3
> >
> > ip address 333.333.333.333 255.255.255.248
> >
> >
> >
> >
> >
> > Can some post a converted Foundry config just to give me a idea.
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Brendan
> >
> >
>
>
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20051207/0f9bf1ca/attachment.html>