Cisco 2950 switch WS-C2950-24

The 2950 only supports one active vlan interface usually used for management.

Chris

As Chris said the 2950 only supports one active vlan interface but I'll add that you don't need to configure vlan 'interfaces' for the vlan itself to be active. You might create a trunk to another 'layer-3' switch/router that has the vlan interfaces configured and handles any intervlan switching/routing.

BernieM

Chris,

Excuse my lack of VLAN know-how, so does that mean the configured VLAN interfaces on the 2950 are purely for management and I can still have multiple VLANs setup and set the ports accordingly? If the answer to my previous question is YES, then the way the two VLANS will communicate is via an external router, correct?

Thanks Bernie. I did not see your post during my reply to Chris...

BV

The 2950 switch is layer 2 only. The VLAN interfaces are for assigning a management IP address to the switch but it allows you to put that IP address on whichever VLAN you desire. Based on its design, just assign one IP to one VLAN interface such as "interface VLAN 10".

When a VLAN does not have any ports assigned to it, the "interface VLAN" is in a down state because there are no ports assigned to it.

1 - Create each VLAN with the "vlan 10" and "vlan 100" commands. 2 - Assign every port to one or the other with commands like "interface FastEthernet0/1" and then "switchport access vlan 10". (repeat step 2 for all ethernet interfaces on the switch) 3 - Assign the management IP address for the switch to the "interface VLAN ??" depending on which VLAN that IP address goes to. 4 - Check your work with a "show vlan" and "show ip interface" command. The VLANS will show ports associated with them. The VLAN interfaces will be up.

Remember that on a switch like this, the "interface VLAN ??" is a virtual interface with a presence in a VLAN. Its only purpose is to put the assigned management IP address for the whole switch into one VLAN or another. The VLANs themselves are not represented by the VLAN interfaces, they are represented by a "show vlan" command. If you want to have multiple management IP addresses assigned, that is your choice. It is not a router so one IP address is all you need.

Thanks Scott for the clarity...

Your answer lead me to my next question. I have a spare Cisco 1720 router and was thinking of creating a trunk on port 24 of the Cisco

2950 switch and a VLAN subinterface on the FA interface of the 1720 router. I did a little googling about the creating VLAN subinterface on the 1720 and got mixed comments. Some said the 1720 does not support VLAN subinterface and other claimed it will with the right software feature set (IP plus). Any body have an authoritative answer on this feature of the Cisco 1720 router?

Thanks again...

BV

You have to have at least a 1721 to do 802.1q subinterfaces. As for the other discussion remember VLANS occur at L2, SVIs are at L3. As previously stated the SVI on a 2950 is for MGT purposes. The correct syntax for creating VLANs is either through VLAN DAT or global config. Cisco is moving away from VLAN DAT but it still does work.

from global -

vlan 100 name MGRS vlan 10 name RECEPTIONISTS

from vlan dat vlan 5 name cisco vlan 10 name catalyst exit

int fa1/0/1 switchport mode access switchport access vlan 5

int fa1/0/2 switchport mode access switchport access vlan 10

Thank you all...