I do not see any ports set for VLAN 2.  Once you have a port set up with access mode VLAN 2 it should change the status.

It is like not having the other end of the cable plugged into a physical port.

Example for access mode:

console# configure

console(config)# interface ethernet xxx

console(config-if)# switchport mode access

console(config-if)# switchport access vlan xxx

console(config-if)# end

If you are trunking you would need to use the General Mode on the 62XX.

console# configure

console(config)# interface ethernet xxx

console(config-if)# switchport mode general

console(config-if)# switchport general allowed vlan add 100 tagged

console(config-if)# switchport general allowed vlan add 101 untagged

console(config-if)# end

Hope this helps,

Keep us updated if you can

Thanks for the response. My thinking is obviously not clear yet. I was hoping to configure a machine (and VLAN membership) based on the machine's IP address rather than specifying a port (your xxx would be 1/g10?). I realize the original VLAN spec works on layer 2 but, in my reading, I thought I came across something that said I could assign a machine (regardless of port)  to a VLAN based on the machine's IP address.  

sorry, can't really help but while reading some things come to my mind:

you write you are using a private class C network

>ip address 192.139.238.79

this is NOT a private network, it belongs to a company in Canada. Besides this, classfull networks are obsolete since 20 years :)  [1] [2]

We did have the same thing here, and changed it thoughout the whole company. years ago but still find sometimes

the old IP in configs :)

>finding devices that won't work with anything other than /24

I'm just curious, did you ever stumble across such a device?

[1] en.wikipedia.org/.../Classless_Inter-Domain_Routing

[2] en.wikipedia.org/.../Private_network

Thilo

correction - second line should be "VLAN 10" not "VLAN 2"

Do you have 192.168.3.1 set as the default gateway on the workstation?

A default route is a path for the router that states where to send all traffic that has no other specifically defined routes in the routing table.

console(config)# ip route 11.0.0.0 255.255.255.0 10.0.0.5   (syntax = "ip route 'dest network' and 'mask' 'next-hop' and address 'metric'")

console(config)# exit

console# show ip route

Route Codes: R - RIP Derived, O - OSPF Derived, C - Connected, S - Static B - BGP Derived, IA - OSPF Inter Area E1 - OSPF External Type 1, E2 - OSPF External Type 2 N1 - OSPF NSSA External Type 1, N2 - OSPF NSSA External Type 2

C                 10.0.0.0/24 [0/0] directly connected, vlan 10

S                 11.0.0.0/24 [1/0] via 10.0.0.5, vlan 10

Thanks for your help.

Now I have two ports set for VLAN 2 with computers plugged into those ports. Static IPs set 192.168.3.3 and 192.168.3.5. I can ping between them. I can't get to or from any devices on VLAN 1.

Here is my config now:

!Current Configuration:

!System Description "PowerConnect 6248, 3.3.3.3, VxWorks 6.5"

!System Software Version 3.3.3.3

!Cut-through mode is configured as disabled

!

configure

vlan database

vlan 10,20

vlan routing 10 1

vlan association subnet 192.168.3.0 255.255.255.0 10

exit

hostname "curetes"

sntp broadcast client enable

sntp server 192.139.238.68

stack

member 1 2

member 2 2

member 3 2

member 4 2

exit

ip address 192.139.238.79 255.255.255.0

ip default-gateway 192.139.238.27

ip domain-name mydomain.com

ip name-server 192.139.238.33

ip routing

interface vlan 10

routing

ip address 192.168.3.1 255.255.255.0

ip netdirbcast

exit

username "admin" password XXXXXXXXXXXXX level 15 encrypted

!

interface ethernet 1/g23

switchport access vlan 10

exit

!

interface ethernet 1/g25

switchport access vlan 10

exit

exit

My computer on 192.168.3.3 is in VLAN 10. It can't ARP 192.168.3.1. Shouldn't the switch respond to the ARP?

What does the default route on the switch really do?

We have always simply configured the default route on our devices to be our firewall interface - with the firewall and all devices are on VLAN 1.

Thanks in advance.

Don

Could many of my problems be related to the fact that, with the exception of these two computers in VLAN 10, all my other systems are in VLAN 1?

I do have 192.168.3.1 set as the default route on the computer. The switch never answers the computer's ARP request for the MAC for that IP - I'm snooping the computer's interface with wireshark.

I can arp/ping the other computer on the VLAN which is at 192.168.3.5.

On Dell layer 3 switches (except 6024), the management vlan cannot be routed.  By default, the management vlan is 1.  If you want to route vlan 1, you need to change the management vlan to something else and then you will be able enable routing on vlan 1.  You can manage the switch via a routing interface also.

console> enable

console# config

console (config)# vlan database

console (config-vlan)# vlan 99

console(config-vlan)# exit

console (config)# ip address vlan 99

console (config)# interface vlan 1

console (config-if-vlan1)# routing

It should are you able to ping the workstation 192.168.3.3 from the switch?

You might do a traceroute to see the path.  If you have VLAN 10 set up with ip address 192.168.3.1.  Then have an interface set up with switchport access to vlan 10 with an ip in the same subnet and the gateway of 192.168.3.1.  You should be able to reach that without any routing set up on the switch.

Done.

Now, as a routing interface, should

interface vlan 10

routing

ip address 192.168.3.1 255.255.255.0

ip netdirbcast

exit

shouldn't the switch answer an arp on 192.168.3.1?

I can now ping 192.168.3.3 from the switch. Yay!

The interface answers my ARPs on the computer at 192.168.3.3.

I put the management interface on VLAN 99 at IP 192.168.4.2. just to get it out of the way.

I tried to configure a route as you describe above.

ip route 192.168.3.0 255.255.255.0 192.139.238.27

No luck. Error was

The static route will not take effect until a routing interface

belonging to the same subnet as the next hop IP is created and activated.

hmm. maybe something is up on the interface.. sure enough:

show ip interface vlan 10

produced the line:

Routing Interface Status....................... Down

hmm. why not redo the commands?

curetes(config)#interface vlan 10

curetes(config-if-vlan10)#routing

curetes(config-if-vlan10)#exit

curetes(config)#ip routing

curetes(config)#exit

curetes#show ip interface vlan 10

Routing Interface Status....................... Up

Now the Routing interface is UP and the switch answers my ARPS on the 192.168.3.x network.

Packets route from 192.168.3.x to 192.139.238.x but not the other way

curetes#show ip route

Route Codes: R - RIP Derived, O - OSPF Derived, C - Connected, S - Static

      B - BGP Derived, IA - OSPF Inter Area

      E1 - OSPF External Type 1, E2 - OSPF External Type 2

      N1 - OSPF NSSA External Type 1, N2 - OSPF NSSA External Type 2

C      192.139.238.0/24 [0/1] directly connected,   vlan 1

C      192.168.3.0/24 [0/1] directly connected,   vlan 10

I tried to figure out your routing commands as you outlined in your post of 06-05-2012 12:50 PM but it would not accept it. Would you be so kind as to repeat it again with my networks? switch interfaces are at 192.168.3.1 and 192.139.238.79.

Thank you so much.

Yea, I've seen all the error messages when I have tried to get this to work :

curetes(config)#ip route 192.168.3.0 255.255.255.0 192.139.238.79

The specified Static Route Next Hop Router Address is invalid.

I'm trying to route between two vlans on the same switch.

"Packets route from 192.168.3.x to 192.139.238.x but not the other way"

That sounds like you need a route on the 192.139.238.x router/gateway.  The route is going out but not coming back.  Therefore the upstream router needs a route something like:

192.168.3.0 255.255.255.0 (interface coming out of 192.139.238.x or next hop address)