Procurve 3500 - Can not be switch IP address and route gateway at the same time.

[KoreyB]

I am trying to configure a Procurve 3500yl-48G switch with multiple VLANs and routing for use in our wireless deployment.  I am unable to add the routes for the specific VLAN's and keep getting the following message, "172.20.210.1 can not be switch IP address and route gateway at the same time.".  Here is the config on the switch. 

Running configuration:

; J8693A Configuration Editor; Created on release #K.14.41

hostname "XX-CORE-XX"
time timezone 480
fastboot
console inactivity-timer 5
module 1 type J86yyA
module 2 type J86xxA
interface 1
   broadcast-limit 30
exit
interface 2
   broadcast-limit 30
exit
interface 3
   broadcast-limit 30
exit
interface 4
   broadcast-limit 30
exit
interface 5
   broadcast-limit 30
exit
interface 6
   broadcast-limit 30
exit
interface 7
   broadcast-limit 30
exit
interface 8
   broadcast-limit 30
exit
interface 9
   broadcast-limit 30
exit
interface 10
   broadcast-limit 30
exit
interface 11
   broadcast-limit 30
exit
interface 12
   broadcast-limit 30
exit
interface 13
   broadcast-limit 30
exit
interface 14
   broadcast-limit 30
exit
interface 15
   broadcast-limit 30
exit
interface 16
   broadcast-limit 30
exit
interface 17
   broadcast-limit 30
exit
interface 18
   broadcast-limit 30
exit
interface 19
   broadcast-limit 30
exit
interface 20
   broadcast-limit 30
exit
interface 21
   broadcast-limit 30
exit
interface 22
   broadcast-limit 30
exit
interface 23
   broadcast-limit 30
exit
interface 24
   broadcast-limit 30
exit
interface 25
   broadcast-limit 30
exit
interface 26
   broadcast-limit 30
exit
interface 27
   broadcast-limit 30
exit
interface 28
   broadcast-limit 30
exit
interface 29
   broadcast-limit 30
exit
interface 30
   broadcast-limit 30
exit
interface 31
   broadcast-limit 30
exit
interface 32
   broadcast-limit 30
exit
interface 33
   broadcast-limit 30
exit
interface 34
   broadcast-limit 30
exit
interface 35
   broadcast-limit 30
exit
interface 36
   broadcast-limit 30
exit
interface 37
   broadcast-limit 30
exit
interface 38
   broadcast-limit 30
exit
interface 39
   broadcast-limit 30
exit
interface 40
   broadcast-limit 30
exit
interface 41
   broadcast-limit 30
exit
interface 42
   broadcast-limit 30
exit
interface 43
   broadcast-limit 30
exit
interface 44
   broadcast-limit 30
exit
interface 45
   broadcast-limit 30
exit
interface 46
   broadcast-limit 30
exit
interface 47
   broadcast-limit 30
exit
interface 48
   broadcast-limit 30
exit
ip default-gateway 172.20.1.254
ip routing
vlan 1
   name "DEFAULT_VLAN"
   untagged 14,16,18,20,22,24,43-47
   ip address dhcp-bootp
   tagged 1
   no untagged 2-13,15,17,19,21,23,25-42,48
   exit
vlan 2
   name "Data"
   untagged 1,3,5,7,9,11,13,15,17,19,21,23,25-42
   ip address 172.20.1.30 255.255.128.0
   tagged 8
   exit
vlan 10
   name "W-Manage"
   untagged 2,4,6,10,12
   ip address 172.20.210.1 255.255.255.0
   tagged 1,8
   exit
vlan 12
   name "W-Secure"
   untagged 48
   ip address 172.20.212.1 255.255.255.0
   tagged 1,8
   exit

web-management ssl
ip route 0.0.0.0 0.0.0.0 172.20.1.254
ip route 172.16.0.0 255.255.0.0 172.20.1.254

no autorun

The routes I am trying to add are:

ip route 172.20.210.0 255.255.255.0 172.20.210.1

ip route 172.20.212.0 255.255.255.0 172.20.212.1

These routes are required to pass the traffic form our wireless lan to the rest of the network. 

[Fredrik Lönnman]

I can't see why you need the routes at all? The 172.20.210.0/24 and 172.20.212.0/24 networks will be in the routing table as "connected" since they are configured on vlan 10 and 12.

Your route statement doesnt make sense, you cant say that the network 172.20.210.0/24 is at gateway 172.20.210.1, because its the same net.

[KoreyB]

I do show the networks as connected but I cannot see the host at 172.20.1.1 from the wireless client.  When I do a tracert it dies at the client gateway 172.20.212.1.  I can however ping the wireless client from the HP switch. 

Any ideas as to why this is not working.  This is a Cisco wireless deployment using a wireless lan controller. 

[paulgear]

Sounds to me like you don't have any route back to 172.20.212.1 from 172.20.1.1. Does it know that it needs to go through the switch to get to 172.20.212.0/24, or does it just have 172.20.1.254 as its default gateway?

Assuming that's the problem, depending on your network topology, a route to 172.20.212.0/24 on 172.20.1.254 might be enough to get you by, or a dynamic routing protocol such as OSPF may be a better option.