HP Procurve 4204vl Layer 3 switch routing problem

[Althorpe68]

Hi all, thanks in advance for your help. I have a Procurve 4204vl switch with four modules, (modules 1,3 & 4 are J8768A and module 2 is a J9033A). I have set up two new Vlans on the switch VLAN 2 (TELEPHONY) & VLAN 3 (SERVERS). We have a DHCP server on our network that hands out ip addresses. IP routing is enabled on the switch and I have 2 untagged ports assigned to each Vlan.

The problem I am having is that routing is not happening between the vlans. Here is the result of Show Run

module 1 type J8768A
module 3 type J8768A
module 4 type J8768A
module 2 type J9033A
ip default-gateway 192.168.20.167
ip routing
snmp-server community "public" Unrestricted
vlan 1
   name "DEFAULT_VLAN"
   untagged A1-A24,B1-B18,B21-B24,C1-C24,D1-D24
   ip address 192.168.20.2 255.255.255.0
   no untagged B19-B20
   ip igmp
   exit
vlan 2
   name "TELEPHONY"
   untagged B20
   ip address 10.20.1.254 255.255.0.0
   ip helper-address 192.168.20.209
   exit
vlan 3
   name "SERVERS"
   untagged B19
   ip address 10.21.1.254 255.255.0.0
   ip helper-address 192.168.20.209
   exit
qos type-of-service ip-precedence
stack join 00256196f040
spanning-tree
password manager

Ip address 192.168.20.2 is the address of the Switch. 192.168.20.209 is the address of our DHCP server.

Here is the result of the ip route command

                                              IP Route Entries

 Destination                 Gateway           VLAN     Type          Sub-Type      Metric     Dist.
 ------------------         ---------------           ----     ---------          ----------     ----------     -----
 10.20.0.0/16            TELEPHONY          2       connected                          0              0
 10.21.0.0/16            SERVERS              3       connected                          0              0
 127.0.0.0/8              reject                               static                                  0            250
 127.0.0.1/32            lo0                                   connected                          0              0
 192.168.20.0/24      DEFAULT_VLAN    1       connected                          0              0

I think the problem lies in the ip route table but I'm not sure what to put in to get the vlan's talking to each other. Clients on ports B19 or B20 can't get a DHCP address either.

Any ideas would be much appreciated.

Thanks in advance

[MarJ]

Did You configured corresponding DHCP address pool for 10.20.0.0/16 - TELEPHONY and 10.21.0.0/16 - SERVERS

 with proper gateways 10.20.1.254 and 10.21.1.254 on DHCP Server ?

[Althorpe68]

I believe I have, have a look I've attached some screenshots.

[paulgear]

Is the problem that you aren't getting DHCP IPs correctly, or that you can't ping 192.168.20.0/24 from 10.x.0.0/16?

If the former, try "dhcp-relay option 82 replace ip". If the latter i think it's far more likely that your end nodes have incorrect default gateways.

[Althorpe68]

Hi thanks for the reply, but there's something that I'm still missing. I have configured a laptop with an ip address of

ip address:    10.21.1.100

mask             255.255.0.0

Gateway       10.21.1.254

I cannot ping anything further than this. If I do a tracert I can only get as far as 10.21.1.254.

What did you mean exactly when you said the end nodes have incorrect default gateways? Can you provide an example of what would be a correct route for the procurve routers?

Many thanks for you help

[paulgear · Accepted solution]

End nodes means PCs, servers, printers, etc.  For example, the PC you set up has the correct default gateway, but what were you pinging on the other end?  Does it have the correct gateway settings?  If it's using another gateway (presumably you have some sort of router to connect to the Internet), does that gateway know the correct route to 10.21.0.0/16?  Routing is a bi-directional process, and you have to have both ends pointing at the right places to get connectivity - the reverse path is often neglected in troubleshooting.

[Althorpe68]

Well, as an example the servers on the 192 range are configured like so

ipaddress   192.168.20.200

Mask           255.255.255.0

Gateway     192.168.20.167

I am not sure how to configure a route to the 192 addresses and vice versa. I know you use the ip route command but not sure what it should be exactly. i.e. would

ip route 192.168.20.0 255.255.255.0 192.168.20.167

ip route 10.21.1.254 255.255.0.0 192.168.20.167

be correct. Or does the gateway need to be something else? I know I'm missing something and I'll kick myself when I've solved it but at the moment.....

Thanks for your help

[Althorpe68]

Got this sorted now there were a couple of things on the switch that needed to be unset so that the routing would work correctly.

Thanks for your help.

[Songpon44]

i have same your problem please tell me for config it