Routing problem with 5400zl

[Hugo Sousa]

Hello,

I'm having a problem with a ProCurve 5400zl.
i have ip routing enabled, 3 vlans.

Config:
; J8697A Configuration Editor; Created on release #K.13.25

hostname "HCF-SW1"
snmp-server contact "Andre Sousa"
snmp-server location "Bastidor 3"
time daylight-time-rule Middle-Europe-and-Portugal
module 1 type J8702A
module 2 type J8702A
module 3 type J8706A
module 4 type J8707A
trunk D1-D2 Trk1 LACP
trunk C1-C2 Trk2 LACP
trunk C3-C4 Trk3 LACP
trunk C5-C6 Trk4 LACP
trunk C7-C8 Trk5 LACP
trunk C9-C10 Trk6 LACP
ip routing
timesync sntp
sntp unicast
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
untagged A1,C15-C24,D3-D4
qos priority 0
ip address 192.168.1.200 255.255.255.0
tagged C11-C14,Trk1-Trk6
no untagged A2-A24,B1-B24
exit
vlan 2
name "VLAN2"
untagged A2-A24,B1-B24
qos priority 0
ip address 192.168.2.200 255.255.255.0
tagged C11-C14,Trk1-Trk6
exit
vlan 100
name "VOIP"
qos priority 6
ip address 172.1.1.254 255.255.255.0
tagged C11-C14,Trk1-Trk6
exit
sntp server priority 1 192.168.2.3
ip route 0.0.0.0 0.0.0.0 192.168.2.1
ip dns server-address priority 1 195.22.0.136
no ip ssh
spanning-tree
spanning-tree Trk1 priority 4
spanning-tree Trk2 priority 4
spanning-tree Trk3 priority 4
spanning-tree Trk4 priority 4
spanning-tree Trk5 priority 4
spanning-tree Trk6 priority 4
spanning-tree priority 1 force-version RSTP-operation
no autorun
password manager

All work fine when I configure routing and route 0.0.0.0 0.0.0.0 192.168.2.1

After a while routing stops.
I can no longer ping IPs from vlan 2 to vlan 1.
For instance I can ping 192.168.2.200 (ip address for VLAN 2 on 5400, but cannot ping 192.168.1.200)

Can anyone give some help with this issue.

Thanks,
Hugo Sousa

[cenk sasmaztin]

hiHugo
please you send me sh tech print

[Hugo Sousa]

Hello Cenk.

Today I was able to do some more testing.
I tried to boot with firmware version K12.57.
Made a fresh config but the results were even worst, with version K12.57 the 5400 didn't even made routing between VLANs.

Then I booted again with version K13.25.
Fresh config again, routing working just fine.
Made some testes, everything looked perfect.
Unfortunately it only worked for about 15 or 20 minutes, after that... no routing, no access to console (with telnet or http).

So here's the show tech, as you asked.
Thanks for your support.

[André Beck]

Hugo,

> Fresh config again, routing working just
> fine. Made some testes, everything looked
> perfect. Unfortunately it only worked for
> about 15 or 20 minutes, after that... no
> routing, no access to console (with telnet
> or http).

There's either a defective module in that chassis or the chassis itself is broken. I've seen such things more than once, it's always been either a module or the chassis. I'd start trying to isolate the faulty module, but if that's not possible, persuade HP to send you all parts for replacement. Then swap all the modules and only as a last resort, swap the chassis.

HTH,
Andre.