5304xl routing issues

[David Davis_12]

I have 5304xl switch that routes for a period of time then quits and then works again later. Sometimes I am unable to reach/ping between vlans or I am unable to reach/ping the firewall. Even stranger is that I have been on the web interface of the switch <5304> on the diagnostics page, from a client PC on vlan 10 and tried to ping a mail server on vlan 10, ip 10.10.10.14, and the firewall trusted interface 10.10.10.1. Both ping tests failed. Also the PC <10.10.10.57> I was accessing the switch from could not ping the same ips either, yet mail flow continued to work Here is an example setup I have used.
On my firewall I have the return routes for my vlans as:
10.10.20.0/24 10.10.10.2
10.10.30.0/24 10.10.10.2
10.10.40.0/24 10.10.10.2
The trusted inerface ip on the firewall is 10.10.10.1/24
On the switch I have the following:
> config# ip routing
> config# vlan 10
> config# name "infotech"
> config# ip address 10.10.10.2/24
> config# untagged a1-a7
> config# tagged a15,a16
> config# exit
> config# vlan 20
> config# name "test"
> config# ip address 10.10.20.1/24
> config# untagged b1-b7
> config# tagged a15,a16
> config# ip helper-address 10.10.10.12
> config# exit
> config# vlan 30
> config# name "test"
> config# ip address 10.10.30.1/24
> config# untagged b8-b15
> config# tagged a15,a16
> config# ip helper-address 10.10.10.12
> config# exit
> config# ip route 0.0.0.0 0.0.0.0 10.10.10.1
> config# write mem
This is my "core" switch. All other switches are used only at layer 2.
I also have a 2848 setup as follows.
> config# vlan 10
> config# untagged 1-8
> config# tagged 47,48
> config# ip heler-address 10.10.10.12
> config# exit
> config# vlan 20
> config# untagged 9-18
> config# tagged 47,48
> config# ip helper-address 10.10.10.12
> config# exit
> config# vlan 30
> config# untagged 19-25
> config# tagged 47,48
> config# ip helper-address 10.10.10.12
> config# exit
> config# write mem

Any ideas on what's going wrong or what may be wrong with my setup?
Thanks!

[Jeff Brownell · Accepted solution]

David,

I certainly can not see issue from the data provided. A topology map and show techs as well as proof that the problem is with the core switch/router (sniffer traces) would be a good start. Make sure your code is up to date on all applicable switches. Have you opened a support call on this? I would recommend you do so with the requested data if a firmware upgrade doesnt help...

-Jeff

[David Davis_12]

Jeff, I have placed a support call, actually got the chassis replaced, sent in several sh techs. Also the latest firmware. Nothing yet. Tech support has been trying. Something like 10+ hours talking to them now. BTW, I have used a different cables, even a standby firewall. No change.

[Jeff Brownell]

David,
Give me the case id you are working with support on this issue. I will read the history and offer assistance through the support avenue (if all right with you).
-Jeff

[David Davis_12]

I have changed out the modules and it appears the problems have cleared up. Don't know, but it's all working now.

[Ralph Bean_2]

David, may I ask what module types you swapped in/out?

Thanks,
Ralph

[David Davis_12]

I have too 5304xl switches. One I am using as a core switch with routing enabled. The other 5304xl as a layer 2 switch. I swapped out the modules between the switches and haven't had any issues till today. The switch I am using as a layer 2 locked up. It won't get past it's post. I've just finished calling it in to HP. The replacement chassis should be here tommorrow. It's locked up tight. I'm guessing the firmware is corrupted. I'll find tommorrow.