Unsolved

This post is more than 5 years old

3 Posts

17538

January 25th, 2014 06:00

vlan support on s50v layer 3 mode

Hello all, first post here,

I have recently inherited 2 s50v switches. my first issue I ran into was that all many of the commands found in command line references (8.4.x in my case) are just non existent. after pouring through forums and manuals I thought maybe it has the SFTOS but the show version doesn't matchup to SFTOS.

so my first question is there somewhere documented what the s50v have and don't have from the standard cli feature list.

My next question is having to do with adding tagged vlan support to our uplink port which is 48 at the moment. I understand that since it has an ip address its placed in Layer-3 mode. but for the life of me I cant find in the manuals how to all other vlans tags to pass through it.

in standard FTOS from the manual you would apply an ip to a virtual nic for management instead of being force to apply it to the physical address 48. 

so is there a command to allow for vlans on management interface , if not what are my options

thanks in advance

118 Posts

January 25th, 2014 07:00

Couple of comments here. 

Force10 S50v is a POE cable gigabit switch with 10Gb uplink and stacking capabilities. It supports both layer2 and layer3 feature sets. 

If you assign a PORT into layer 3 mode- you are designating it a routing port, and VLAN participation would not be applicable. If you create a VLAN interface and assign an IP address to it, then it becomes an inter-VLAN router - and the physical ports would have membership in one or more VLANs. 

So if you want to do an uplink - you would either create a port channel first (to support multiple physical ports as the uplink) and then set the membership from the VLAN

ie: 

vlan 1

untagged 48

vlan 2 

tagged 48

vlan 3

tagged 48

If you are in a mixed Cisco environment and want to pass-thru vtp to switches on either side of the Force10 - then you would need to lookup hybrid ports. 

For force10 software updates you need to request an account on support.force10networks.com

S50v - FTOS 8.4.2 is the current version. SFTOS would be 2.5.3.7.

3 Posts

January 25th, 2014 07:00

Thanks for the quick reply Michael,

but im still somewhat confused. I understand up to "an inter vlan router ". at this point I get that this would allow ports that are members of vlan1 and vlan2 to communicate with each other.

but not sure about port channels (i.e. relationship and configuration)

also when you write "tagged 48" confuses me because if a port is in layer3 mode (which 48 is) you cant tag it so im not sure how I would apply that part. you mention 'set the membership to the vlan' but it seems that there's a middle step I would have to do to port 48 to be able to tag it first.

my goal is simply to have tagged vlan2(#) packets from say port 3 to get out of the switch over the wire that's connected to port 48 which is the management ip interface so its locked to layer3. most switches I work with you add the mgmt. ip to a virtual nic not necessarily a physical port. but it seems like even though we have version 8.4.2 we don't have that capability on this switch.

I will investigate hybrid ports and port channel, but if you know of somewhere where I could get a step by step guide to allowing tagged packets to pass-through an interface with the management ip that would be awesome. on a side note yes there is various makes of switches in the network.

thanks again

118 Posts

January 25th, 2014 20:00

I had to grab a book on the S50V to double check the presence of a fixed management port - (s4810 have those); it does NOT have an ethernet management port - so you can remove the IP address from port 48, and put it in switchport mode so that you can configure VLANs and such to achieve the behavior you want. You would put the management ip for the switch on the vlan interface (whatever tag number that VLAN is in your environment). 

eg: 

config t

int vlan 22

untagged 48 

ip address  

Yes - you will need to be serial consoled into the switch to do this without losing connectivity. 

You can not pass vlan information over layer 3 (router) ports - VLANs are layer 2 entities.

0 events found

No Events found!

Top