CISCO 2950, very simple VLAN'ing

[poohbeer]

Got a Cisco 2950 and trying to use 802.1q to connect it's vlans with an extreme networks summit48. For now however just the basic setup on the cisco not connected to the summit48 with 2 vlans. See my problem and the config below.
I don't have any cisco experience so I might be doing something awfully stupid here but i cannot get it working.

Problem:

Switch(config)#int vlan 1000
Switch(config-if)#no shut
Switch(config-if)#
20:17:33: %LINK-3-UPDOWN: Interface Vlan1000, changed state to up
20:17:33: %LINK-5-CHANGED: Interface Vlan10, changed state to administratively down
20:17:34: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan10, changed state to down
Switch(config-if)#exit
Switch(config)#int vlan 10
Switch(config-if)#no shut
Switch(config-if)#
20:18:02: %LINK-3-UPDOWN: Interface Vlan10, changed state to up
20:18:03: %LINK-5-CHANGED: Interface Vlan1000, changed state to administratively down
20:18:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan10, changed state to up



configuration:

Current configuration : 2259 bytes
!
version 12.1
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname Switch
!
!
ip subnet-zero
vtp mode transparent
!
vlan 10
name akzo
!
vlan 1000
name switches
!
spanning-tree extend system-id
!
!
interface FastEthernet0/1
switchport access vlan 10
no ip address
!
interface FastEthernet0/2
switchport access vlan 10
no ip address
!
interface FastEthernet0/3
switchport access vlan 10
no ip address
!
interface FastEthernet0/4
switchport access vlan 10
no ip address
!
interface FastEthernet0/5
switchport access vlan 10
no ip address
!
interface FastEthernet0/6
switchport access vlan 10
no ip address
!
interface FastEthernet0/7
switchport access vlan 10
no ip address
!
interface FastEthernet0/8
switchport access vlan 10
no ip address
!
interface FastEthernet0/9
switchport access vlan 10
no ip address
!
interface FastEthernet0/10
switchport access vlan 10
no ip address
!
interface FastEthernet0/11
switchport access vlan 10
no ip address
!
interface FastEthernet0/12
switchport access vlan 10
no ip address
!
interface FastEthernet0/13
switchport access vlan 10
no ip address
!
interface FastEthernet0/14
switchport access vlan 10
no ip address
!
interface FastEthernet0/15
switchport access vlan 10
no ip address
!
interface FastEthernet0/16
switchport access vlan 10
no ip address
!
interface FastEthernet0/17
switchport access vlan 10
no ip address
!
interface FastEthernet0/18
switchport access vlan 10
no ip address
!
interface FastEthernet0/19
switchport access vlan 10
no ip address
!
interface FastEthernet0/20
switchport access vlan 10
no ip address
!
interface FastEthernet0/21
switchport access vlan 10
no ip address
!
interface FastEthernet0/22
switchport access vlan 10
no ip address
!
interface FastEthernet0/23
switchport access vlan 1000
no ip address
!
interface FastEthernet0/24
no ip address
!
interface GigabitEthernet0/1
no ip address
!
interface GigabitEthernet0/2
no ip address
!
interface Vlan1
no ip address
no ip route-cache
shutdown
!
interface Vlan10
no ip address
no ip route-cache
!
interface Vlan1000
no ip address
no ip route-cache
shutdown
!
ip http server
!
!
line con 0
line vty 5 15
!
end

 

[imported_netman]

I'm going to assume that the point of this is to have 2 active VLAN interfaces on the 2950? And when I say interfaces, I mean IP enabled interfaces (L3), not just a L2 VLAN.

Lets start with square 1: a 2950 is an access layer device and only supports (1) active L3, IP enable VLAN interface for management. The 2950 doesn't do routing, so the use of having 2 IP enabled VLANs would be pointless, they couldn't route between each other. You can only have 1 "ip default-gateway", which will route any management traffic back out the single active VLAN interface. Hope that all made sense..

So if your point is to create 2 VLAN interfaces (with IP's), like this:

conf t

interface vlan 1000
ip address 10.1.1.1 255.255.255.0
no shut


interface vlan 10
ip address 10.10.10.1 255.255.255.0
no shut

Then it won't work. You can't have 2 active IP's or VLAN intefaces on a 2950.

If having IP's enabled on the switches for these VLANs isn't important, and you only wanted to enable VLAN tagging (dot1q) for these vlans, so that just the machines assigned to these VLANs could reach each other, and not necessarily an IP of the switch.. then you need to just do this (add the vlans to the VLAN database):


Start by doing this:

show vlan brief

(does it show your vlan 1000 and 10), most new versions of IOS don't create a VLAN in the database when you try to bring up and interface. So you have to create the VLAN, then create the interface.

conf t

vlan 1000
name <description optional>

vlan 10
name <description optional>

That is all you need to properly create the VLANs, however then if you are going to trunk the 2950 to the extreme then you need to setup a trunk port too, to allow both vlans across. Versus an access port that will only allow 1 VLAN.

Any other questions I would be happy to help

 

[ScottMac]

ON the 2950 (an L2 switch), only one VLAN will show "UP" at a tie: the "administrative" or "natilve" VLAN.

The others are working, but you can only have one active IP address associsted with the switch (the Admin / Native).

Good Luck

Scott

 

[Agamar]

I have all of our switches (2950 and 3550) configured with 2 vlans. I use the "switchport access" command to put the ports into the vlan. Example:

!
interface FastEthernet0/19
switchport access vlan 180
no ip address
!
interface FastEthernet0/20
switchport access vlan 176
no ip address
!
interface Vlan176
no ip address
no ip route-cache
!
interface Vlan180
ip address 138.xxx.xxx.xxx 255.255.252.0
no ip route-cache
!
ip default-gateway 138.xxx.xxx.254
ip http server

 

[imported_netman]

Originally posted by: Agamar
I have all of our switches (2950 and 3550) configured with 2 vlans. I use the "switchport access" command to put the ports into the vlan. Example:

!
interface Vlan176
no ip address
no ip route-cache
!
interface Vlan180
ip address 138.xxx.xxx.xxx 255.255.252.0
no ip route-cache
!




The point being that you only have IP's (L3 interface) assigned to one interface. And, a 3550 is capable of being a multilayer switch (router) while the 2950 isn't.

 

[Cooky]

Correct me if I'm wrong, but I think OP just wants to connect the cat2950 w/ the Summit 48 switch so that vlans on one switch can communicate w/ the other.

I think what he needs to do is
1.set up VTP correctly so that VLAN information is shared among the switches. Right now the cat2950 is in Transparent mode.
2.creat a dot1q trunk w/ the other switch.

 

[imported_netman]

Cooky, that is almost what my first post says. Minus the fact that VTP is a Cisco proprietary protocol and can't share info with an Extreme switch.

1) I don't think it was intended to setup VLAN interfaces.. Just simple create the vlans.

conf t
vlan 1000
vlan 10
end

2) then setup a trunk to pass both vlans

 

[spidey07]

all you need to do is setup the VLANs with...

vlan 10
vlan 1000

Since your switch is in VTP transparent mode (as it should be) you now have two vlans created. Then as you've done use the "switchport mode access vlan xxx" to assign the ports to that vlan.

Then create the trunk port with..
ing f0/12 <----or whatever port your trunking with
switchport mode trunk
switchport trunk native vlan xxx
^^^^^the xxx is your native vlan and has to match on both sides of the trunk...this is the untagged traffic/vlan.

verify with....
show int f0/12 trunk
^^^^or whatever port is the trunk.


When you use the command "int vlan 10" you are creating a Switched Virtual Interface or SVI. This is a virtual interface used for routing between vlans on a layer 3 switch. On a layer2 switch there is really only one true SVI and that is the management VLAN which is used by the switch itself to communicate (telnet, webserver, snmp, logging, etc)

serch cisco.com for more. I'm sure there is a manual for the switch.

 

[Cooky]

netman - you did cover it already. I just didn't read it through. My bad.