VLAN question (making a port a member of more than one VLAN)

I think you can make a port a member of more than one VLAN with the multiport command right?
Let's say you have 3 VLANs on your switch.
VLAN1 (default)

If I assign port number 5 to be part of VLAN2 and VLAN3, can I choose what IP address to assign the computer plugged into port number 5? I'm assuming I can assign it an IP of either VLAN2 or VLAN3 addressing scheme?

Who is Participating?

Improve company productivity with a Business Account.Sign Up

Dr-IPConnect With a Mentor Commented:
If what you are trying to do is have a server with a native IP addresses on multiple VLAN’s to reduce the traffic across the router between VLAN’s, I have a better way of doing that. What I do is set the port on the switch for 802.1Q trunking, and then configure the NIC on the server for trunking and VLAN’s. Not all NIC’s can do it, but most NIC’s that come in servers have drivers and software that can.

When you are done, to the OS it will appear to it that the server has multiple NIC’s, each of which can be configured individually. Just make sure you get the correct address on the virtual NIC to match the VLAN it’s set to and it should work like a champ.    
NicBreyConnect With a Mentor Commented:
Only trunk ports can be assigned to more than one vlan. On the other side you will either have another trunk port on a different switch, or a router interface with sub-interfaces for each vlan's ip range.

Access ports can be configured with only one vlan
Don JohnstonConnect With a Mentor InstructorCommented:
The multiport command will allow you to make a port a member of more than one vlan but Cisco does not recommend its use. I also read a while back that the command would be removed from the IOS at some point. I haven't tried the command lately so I don't know if it's still available.

Another thing to keep in mind is that if you configure one port with the multi command you will not be able to configure trunking on any other port.

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

lrmooreConnect With a Mentor Commented:
You can use the Private VLAN concept to put a port into more than one VLAN

I'm not sure that is what you are wanting to know? What switch are you using?
dissolvedAuthor Commented:
Thanks Nick.
Don:  Thanks. At home I'm running a 2920 catalyst w/enterprise.  There are 3 vlans on the switch and everything is working great. Port 24 is trunked to a 2600 router.

Port 3 is an access port, as well as a multi port. And my trunk link still works on port 24. Is this possible?

Here is  a sh run
spanning-tree vlan 1 hello-time 10
spanning-tree vlan 3 hello-time 10
ip subnet-zero
interface FastEthernet0/1
port security max-mac-count 1
interface FastEthernet0/2
switchport multi vlan 1,3
interface FastEthernet0/3
switchport access vlan 3
switchport multi vlan 1,3
interface FastEthernet0/4
switchport access vlan 2

Cut off the rest  
dissolvedAuthor Commented:
lrmoore:  At work we are using 2980g switches (connected via fiber) and they all connect to the core (catalyst 4000).

Also, I read in a CCNA book...that you can make a server part of 2 vlans. That way clients dont have to cross a layer 3 device to reach it.  This doesnt make sense to me . Are you supposed to put two nics in the server (one on each vlan). Or are you supposed to use the multi vlan command?

I will check out that link you provided
PennGwynConnect With a Mentor Commented:
> Also, I read in a CCNA book...that you can make a server part of 2 vlans. That way clients dont have to cross a layer 3
> device to reach it.  This doesnt make sense to me . Are you supposed to put two nics in the server (one on each vlan). Or
> are you supposed to use the multi vlan command?

Most people put two NICs in the server, or a trunk-capable NIC, or something like an ATM interface.  I've never seen anyone use multi for this; to use it on a server, you'd need a NIC/OS that allows secondary IP addresses since you want it to be reachable on the various VLANs.

dissolvedAuthor Commented:
You know what penngwyn. I think you're right. A special nic is required to do this in your server. I have to go back into my book to see. Thanks
Not necessarily. Windows will let you assign up to 5 IP addresses to most any NIC and they do not have to be in the same subnet at all...
dissolvedAuthor Commented:
thanks guys. Thanks DR ip
dissolvedAuthor Commented:
Is this why servers ship with several network cards built in???  A few of our servers at work have more than one network card.  Is it for this purpose for connecting each interface to different networks?

Also, supposedly Dell's new server has a couple nics on board and you can assign both nics the same IP (they are viewed as one physical interface).  What advantage does this have?

There are many reasons a second NIC can be handy, and since it’s so cheep to do on the manufacturing level, a lot of servers come with two now days. For the small office, you can hook one up to your DLS line and the other one to the local LAN, and use it for internet connection sharing and as a firewall for the clients. Or as I have seen done, use one to connect to the internet for web severing, and the second one to a private LAN for management purposes. Also on a heavily loaded server, you can do load sharing across the two cards if you have a switch that supports it, effectively doubling throughput for what was once a fraction of the cost of going gigabit, but as we all know gigabit switch prices have fallen though the floor lately. So you might start seeing secondary NIC’s being dropped on a lot of servers, or as I have seen on a few, get one gigabit copper, and a 10-100. Besides that, when you trunk a gigabit interface, it’s like having 10 100 meg adaptors, so the need for a second one kind of goes out the door so long as you have a switch that supports trunking and VLAN’s.    

First, you have to use ‘switchport mode multi’ for the multi vlan option to work.

Second, it's only the 2900XL/3500XL series switches that support that type of configuration.  You'll be without that option on any of the other switches.  In fact, the XL series switches let you get away with a lot of things that the others don’t.  Therefore it’s bad practice to lock yourself into a specific switch type.

Third, it's a cleaner solution to have more NIC's, but you can use a single nic.  If you are using a single NIC, make sure that you specific default gateways for each of those IP's that you assign to the single NIC.  Otherwise you will have unpredictable results.  Not to mention security impacts, where most people are starting to use RPF as a way to stop spoofing...

RE comment from Trevens

I may get shot down in flames here, but my undertanding is that you only specify 1 default gateway, and add routes to the server routing table for the other Vlans.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.