Enable VLAN Routing in PowerConnect

Once you set up interfaces associated with the VANS you have created it should change the state of the VLAN interface.  It is similar with a routing interface when the other end of the connection is not configured and the state is down until both are set up and connected with a proper cable.

Here is a sample config for setting an interface for vlan access.

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 have connections between switches you would need a trunk/general mode to allow the VLAN traffic to traverse back and forth.  Depending on the switch model and whether you are connecting to a third party switch you can swap out general and trunk in the example below.

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.

Yes. I have these configurations done already. I enabled routing at the Vlan interface and global level

Do you have routing enabled globally and on each specific VLAN interface?

console(config)# ip routing

console(config)# interface vlan 2

console(config-if-vlan100)# ip address xxx.xxx.xxx.xxx /24

console(config-if-vlan100)# routing

console(config-if-vlan100)# exit

You would need to enter each VLAN to enable routing on the VLAN level.

Thanks Willy M,

I am more concerned with the reason(s) why all the vlan interfaces are all down. I have configured routing on the vlan interfaces and globally on the switch because it's layer three switch. My first post is my actual configuration status

Thanks!

You may also need to look at updating the firmware on the switch.  If you have a 62xx then you need to be at the latest firmware 3.3.3.3.

Download link for 3.3.3.3 firmware for the 62xx model:

www.dell.com/.../DriverFileFormats

It's very possible I am doing a lot of things wrong. I have several config text pasted in this post, please help diagnose what is wrong.

Numbers 1 screen shot :

lasw1#configure

lasw1(config)#ip route 172.16.0.1 255.255.192.0 192.168.2.231

The specified Static Route Address is invalid.

lasw1(config)#ip route 172.16.0.0 255.255.192.0 192.168.2.231

The specified Static Route Next Hop Router Address can't be in the same subnet a

s the service/network port.

lasw1(config)#

Number 2 screen shot ( Show IP interface Vlan 2)

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

Primary IP Address............................. 172.16.0.1/255.255.192.0

Routing Mode................................... Enable

Administrative Mode............................ Enable

Forward Net Directed Broadcasts................ Enable

Proxy ARP...................................... Enable

Local Proxy ARP................................ Disable

Active State................................... Inactive

MAC Address.................................... 5C26.0AF2.ECD6

Encapsulation Type............................. Ethernet

IP MTU......................................... 1500

Bandwidth...................................... 10000 kbps

Destination Unreachables....................... Enabled

ICMP Redirects................................. Enabled

Number 3 screen shot: Show Ip route

lasw1#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

Please help! I know the vlans are not routing yet because the interfaces are not enabled yet.

Use the ip route command in Global Configuration mode to configure a static route. Use the no form of the command to delete the static route. (syntax = "ip route 'dest network' and 'mask' 'next-hop' and address 'metric'")

lasw1(config)#ip route 172.16.0.1 255.255.192.0 192.168.2.231

The 255.255.192.0 /18 mask is making your network start at 172.16.0.0 and end at 172.16.63.255.  Giving you 16,382 hosts on the network.  So your next network would be 172.16.0.64.  If this is what you are intending then that is ok.  This is the reason you are getting the message “The specified Static Route Next Hop Router Address can't be in the same subnet as the service/network port.”

Here is a good Subnet calculator that can help with configuring.

www.subnet-calculator.com/subnet.php

Is 192.168.2.231 the ip of the interface on the connecting router(next hop)?

Referring to my earlier post if you do not have your VLAN’s set up on an interface for access or trunking then the Routing interface status will continue to be “Down”

Thanks again Willy M,

I made a mistake with the subnet layout. I have corrected that.

VLAN 1 : 172.16.0.0  (255.255.192.0) - 172.16.63.255 (255.255.192.0)

VLAN 2 : 172.168.64.0 (255.255.192.0) - 172.16.127.255 (255.255.192.0)

VLAN 3 : 172.168.128.0 (255.255.192.0 ) - 172.16.191.255 (255. 255.192.0 )

192.168.2.1 is the LAN IP address on our firewall (router).  But port 1 on the switch is connected to the LAN switch in the Subnet 192.168.2.XX

192.168.2.231 is the assigned IP address to lasw1. I can access the switch via a web browser on 192.168.2.231

Do i need a routable IP address to enable inter VLAN routing?  This is the error I have now after correcting the subnet layout mistake:

lasw1(config)#ip route 172.16.0.1 255.255.192.0 192.168.2.231

The specified Static Route Address is invalid.

lasw1(config)#

lasw1(config)#ip route 172.16.0.0 255.255.192.0 192.168.2.231

172.16.0.0 is the network ip

(syntax = "ip route 'dest network' and 'mask' 'next-hop' and address 'metric'")