ProCurve 3500 - one static route lost

[68k]

Hi,

we have some ProCurve switches with some (4) VLANs. The VLANs all are tagged and available on all the switches. One of these switches is a 3500, which has routing enabled. Besides the routing between all the vlans he also has two static routes:

ip route 0.0.0.0 0.0.0.0 192.168.3.254
ip route 192.168.100.0 255.255.255.0 192.168.150.1

192.168.150.1 is the address of a router to a separate network segment (192.168.100.0/24). 192.168.150/24 is a separate VLAN for only the 3500 and this router (transfer network).

So far so good. But sometimes, hosts (from the other vlans) which are sending packets to the network 192.168.100.0, cannot communicate with targets there and vice versa. All the hosts connected to the ProCurve switches have the 3500 as there default gateway, the hosts in the 192.168.100 network "their" router of course. A quite simple structure.

If all is running fine, then the packets from the hosts are routed over the 3500, as expected. I verified this with traceroute.

If the pings are timing out, then a traceroute on the sending hosts shows, that the first hop is 192.168.3.254 (the default gateway of the 3500 itself). If after some minutes all is working fine again, then a traceroute shows the correct routing path via the 3500 -> vlan (192.168.150.0) ...

It seems, that for whatever reason sometimes the routing of the packets to network 192.168.100.0 is wrong? But if so, why? Do I have a firmware problem? The switch is currently running K.13.09. Or did I oversee something other? BTW, this happens to all the hosts. It's not limited to a special machine.

It would be nice, if someone could help me.

Thanks and regards

[cenk sasmaztin]

please send me sh tech print

[68k]

Here it comes.

Thanks!

[cenk sasmaztin]

hi
where are 192.168.100.0 network
your local site or wide area site

[68k]

Hi,

it's on our local site. WAN is behind the 192.168.3.245.

Thank you!

[cenk sasmaztin]

you say to switch
any destination ip, any destination mask go to 192.168.3.254 gateway

after repead you say switch
if go to 192.168.100.0 network 255.255.255.0 mask go to 192.168.150.1 gateway

all route packet fristly go 192.168.3.254 gateway so if packet include destination ip 192.168.100.0 address fristly 192.168.3.254 gateway after go 192.168.150.1 gateway
this is problem....

if 192.168.100.0 network in your local network change vlan 4 ip address
vlan 4 ip address 192.168.100.1 and all 100.0 network client make default gateway address 192.168.100.1

you can use only one static route
for internet connection all vlan
ip route 0.0.0.0 0.0.0.0 192.168.3.254
must be ip routing enable on switch
now all vlan routing between and all vlan go to internet site

ip routing
vlan 1
name "VLAN_SEG1"
untagged 1-12,15-21
ip address 192.168.3.250 255.255.255.0
tagged 23,24,Trk1
no untagged 22
exit
vlan 2
name "VLAN_SEG2"
ip address 172.19.4.250 255.255.254.0
tagged 23,24,Trk1
exit
vlan 3
name "VLAN_SEG3"
ip address 172.19.6.250 255.255.254.0
tagged 23,24,Trk1
exit
vlan 4
name "VLAN_SEG4"
untagged 22
ip address 192.168.100.1 255.255.255.0
exit
ip route 0.0.0.0 0.0.0.0 192.168.3.254
*****************************************
make config internet router for ip routing your internet router ip address 192.168.3.254
write static route on internet router
192.168.0.0 255.255.0.0 192.168.3.250
172.19.0.0 255.255.0.0 192.168.3.250

[68k]

> you say to switch
> any destination ip, any destination mask go to 192.168.3.254 gateway

Yes, any unknown destination should be routed via 192.168.3.254

> after repead you say switch
> if go to 192.168.100.0 network 255.255.255.0 mask go to
> 192.168.150.1 gateway

Yes, with this static route I want the switch that all packets for 192.168.100.0/24 has to be routed via 192.168.150.1. According to the documentation I think, this is the right way. Or am I wrong?

> all route packet fristly go 192.168.3.254
> gateway so if packet include destination ip
> 192.168.100.0 address fristly 192.168.3.254
> gateway after go 192.168.150.1 gateway
> this is problem....

I'm not sure if I understand correctly. Do you mean, that all the packets with a destination in 192.168.100.0/24 first go to 192.168.3.254, even if a static route for the 192.168.100.0/24 network exists? Is it that what you say? If yes, why should this be so? If a static route exists, then the switch should not send any packet matching this route to the gateway for "0.0.0.0/0.0.0.0-packets".

Or am I wrong with this assumption? Or did I have misunderstood?


> if 192.168.100.0 network in your local network change vlan 4 ip address
> vlan 4 ip address 192.168.100.1 and all 100.0 network client make
> default gateway address 192.168.100.1

Maybe my earlier reply confused a little bit. This 192.168.100.0/24 network is "local", as it's used in a separate building in our company. We have to go there via router (192.168.150.1). It's in contrast to "real" WAN connections we're also using (behind the 192.168.3.254).

> you can use only one static route
> for internet connection all vlan
> ip route 0.0.0.0 0.0.0.0 192.168.3.254
> must be ip routing enable on switch
> now all vlan routing between and all vlan go to internet site

To be honest - I don't understand. ;-)

As I said above: Currently I have two static routes (and I hope I understand the routing concepts of the PC switches correctly):

No. 1): for the 192.168.100.0/24 network
No. 2): for "the rest/all the others" 0.0.0.0 (means NOT the VLANs and NOT the 192.168.100.0)

Is my assumption correct? Is this possible with 3500 switch? I think yes, as for some minutes it works as expected. And after a time of (for example) 20 minutes or so, the routing doesn't work anymore and from the sender's perspective all packets are routed to 192.168.3.254. It looks, like the static route no. 1) isn't active in this moment.

> vlan 4
> name "VLAN_SEG4"
> untagged 22
> ip address 192.168.100.1 255.255.255.0
> exit

As I wrote above: This isn't possible. The word "local site" in my earlier reply was misleading I fear. I have to use the transfer network 192.168.150.0 and go via router to 192.168.100.0. From the 3500's point of view I would say, the 192.168.100.0 network and all non-VLAN-networks (0.0.0.0) all are WAN.

My main problem is: Sometimes all is working as it should, sometimes not. Until now I couldn't find out why. But I'm quite sure, that it has to do with the 3500 switch. In case of NOT reaching the 192.168.100.0 network, he still shows the right static routes but seems to doesn't act accordingly. And I think, that's not correct. And myabe therefore I should upgrade to the latest firmware first ...?

Do you understand my thoughts and what I've written?

Thank you very much for your help!

[cenk sasmaztin]

not any frimware problem for routing

if you want free of problem routig working on switch must be right routing config.

you say********************
(If the pings are timing out, then a traceroute on the sending hosts shows, that the first hop is 192.168.3.254 (the default gateway of the 3500 itself). If after some minutes all is working fine again, then a traceroute shows the correct routing path via the 3500 -> vlan (192.168.150.0) ...)

some times destination address 100.0 network paket go to 3.254 device very normal
because you say to switch

[cenk sasmaztin]

when switch or/and router send ethernet packet other network see routing table

your switch see rouing table fristly frist rule 0.0.0.0 0.0.0.0 192.168.3.254

ip route 0.0.0.0 0.0.0.0 192.168.3.254
ip route 192.168.100.0 255.255.255.0 192.168.150.1

have 100.0 destination packet go to 3.254 subnet very normal

[cenk sasmaztin]

please test
change ip route command sorting

Running configuration:

; J8692A Configuration Editor; Created on release #K.13.09

hostname "LOC01"
snmp-server contact "IT"
max-vlans 253
time timezone 60
time daylight-time-rule Middle-Europe-and-Portugal
fastboot
web-management ssl
module 1 type J86xxA
trunk 13-14 Trk1 LACP
ip routing
ip directed-broadcast
no ip source-route
ip udp-bcast-forward
timesync sntp
sntp unicast
snmp-server community "xxxxx" Unrestricted
snmp-server community "xxxxx" Operator
vlan 1
name "VLAN_SEG1"
untagged 1-12,15-21
ip address 192.168.3.250 255.255.255.0
tagged 23,24,Trk1
no untagged 22
exit
vlan 2
name "VLAN_SEG2"
ip address 172.19.4.250 255.255.254.0
tagged 23,24,Trk1
exit
vlan 3
name "VLAN_SEG3"
ip address 172.19.6.250 255.255.254.0
tagged 23,24,Trk1
exit
vlan 4
name "VLAN_SEG4"
untagged 22
ip address 192.168.150.2 255.255.255.0
exit
fault-finder bad-driver sensitivity high
fault-finder bad-transceiver sensitivity high
fault-finder bad-cable sensitivity high
fault-finder too-long-cable sensitivity high
fault-finder over-bandwidth sensitivity high
fault-finder broadcast-storm sensitivity high
fault-finder loss-of-link sensitivity high
fault-finder duplex-mismatch-HDx sensitivity high
fault-finder duplex-mismatch-FDx sensitivity high
no ip icmp redirects
sntp server priority 1 192.168.3.1
ip ssh filetransfer
ip route 192.168.100.0 255.255.255.0 192.168.150.1 ********(frist ip route)
ip route 0.0.0.0 0.0.0.0 192.168.3.254*****(second ip route)
spanning-tree
spanning-tree Trk1 priority 4
spanning-tree priority 1 force-version RSTP-operation
no tftp client
no tftp server
no tftp6 client
no tftp6 server