ProCurve 3500 - one static route lost

[cenk sasmaztin]

all the same my advice

directly connect 100.0 network your core switch with vlan

switch learn all vlan subnet address (directly connected address)and know one default gateway address

switch see when packet go to other network quickly learn destination

so unreachable directly network this address

192.168.3.0
172.19.4.0
172.19.6.0
new 192.168.100.0>

go to default gateway address for any network any subnet information

this config provide very fast and free of problem routing

[68k]

Thanks for your answer!

> some times destination address 100.0
> network paket go to 3.254 device very
> normal because you say to switch > destination ip any mask go 3.254 however
> 192.168.100.0 or 150.0 network in this
> address so switch fristly see any any
> route rule in routing table

> your switch see rouing table fristly frist
> rule 0.0.0.0 0.0.0.0 192.168.3.254

If I may say that: I don't believe that the switch (the routing engine) is working this way. Then a static route wouldn't make sense at all. OK, the any/any route is always the first one in the table shown by sh ip route. But this comes from the sorting and doesn't reflect the order of the routing decision. IMHO of course. But any other behavior would be nonsense. In such case I never had a chance that a static route could become active. Would you agree?


> 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

See above, IMHO that's not normal.

> please test
> change ip route command sorting

I tried it and it doesn't change anything. As expected by me. If it would change the behavior, then with every new static route I had to care about the sorting of the entries in the routing table. This cannot be ...

> directly connect 100.0 network your core
> switch with vlan

As I already wrote: I cannot connect this link directly to the switch for several reasons. But all in all I believe, that's not the problem as such. The switch has to correctly handle static routes. And he has to use and respect them _before_ the any/any route. Like every other router would do.

Thanks and kind regards.