Migrating from Foundry SuperX base layer 2 to Brocade MLXe-8

[aurfalien]

Hello,

I'm unsure if this is the correct forum to post on seeing that I'm talking about very old gear, so feel free to direct/correct me, etc...

I've about 6 Foundry SuperX chassis with various 1Gb and 10Gb modules and several of the Brocade 24 port 10Gb and 48 port 1Gb desktop switches sprinkled all over my facility.  I have these in a simple base layer 2 configuration with port based VLANs and lots and lots of trunks.  And I'd be thrilled to keep using them as I've a stock pile of spare parts to last a life time.  However I'm in need of 40Gb and got a real good deal on an MLXe-8.  Plus I've always enjoyed Foundry/Brocade and have a sort of brand loyalty going on.  On top of that I sure to like a chassis switch vs a desktop switch.

Amongst other things, it has 2x of the MR2-M management modules, a few 40Gb modules, couple of the 1Gb modules and some 100Gb modules and 3 of the high speed fabric modules.

Not sure if I can use the 100Gb but I digress, however I will be using the 40Gb for sure.

At any rate, I've been starting to read various manuals that I could find on this router as it doesn't seem to be just a switch and can't seem to find a way to make it easily do what I'd like.

All I really need it to do are;

Layer 2

Jumbo

Port based VLANs

I intend to keep as as it's a pretty awesome switch/router and am hoping that some one could get me started in the right direction.  I'm actually looking to grow into it eventually as it seems leaps and bounds above my SuperX's.

[aurfalien]

Is it possible when in after setting "no route-only" to assign the over all switch an IP address?  I currently have the management port set with an IP address which is how I'm managing it.

[Deep_Bakul_Bhoj · Accepted solution]

For basic layer 2 functionality, first enable switching. 
MLX#conf t
MLX(config)#no route-on
route-only Disable Layer 2 switching
https://extreme-networks.my.site.com/ExtrArticleDetail?an=000078239

For using the port as access port, use untagged option and for using the port as trunk use tagged option. 
#vlan 10
MLX(config-vlan-10)#untagged e 1/1

MLX#vlan 10
MLX(config-vlan-10)#tagged e 1/1

For mtu, you can set ip mtu on the interface but ethernet [l2] mtu is set globally. Please refer this article: https://extreme-networks.my.site.com/ExtrArticleDetail?an=000080640

[aurfalien]

Since you're here, I was curious as this is a general design question.  Would there be any advantages to implementing Layer 3 in a LAN, such as priority queueing etc...  And are IP based VLANs as secure as port based VLANs?  My MLXe-8 can do a lot of stuff so I might as well look into taking advantage of some added and cool features.  Although I'm a proponent of the KISS principal.

We're actually downsizing so I won't be needing all of those SuperX chassis and desktop switches and I've a few old Mellanox 40Gb switches that I'd like to retire as well.  I will instead use only my MLXe-8,  it has the module options and port density to do all I need.

[aurfalien]

Ah thank you!

The magic command is switchport mode.  This is great thank you.  I'm not used to so much power, this thing is a beast.  Thanks again for the reply.