I've got an old HP Procurve 5400 series switch that's acting as our core switch for a network with inter-VLAN routing. Right now, the gigabit uplink to our firewall gets really saturated because we upload a lot of camera data to the cloud. To fix this, we're upgrading to a 10gb fiber uplink, but it seems like traffic isn't being routed out through this new link. Here's a quick breakdown of the situation:
- The old uplink is on VLAN 70, configured as:
- interface A1
- untagged vlan 70
- spanning-tree instance ist path-cost 20000
- spanning-tree root-guard
- exit
- The new uplink is configured the same way:
- interface F6
- untagged vlan 70
- spanning-tree instance ist path-cost 20000
- spanning-tree root-guard
- exit
I'm using an 8-port SFP+ module for F6 while A is a standard 24-port gigabit module. The strange part is, I can ping the internet directly from the switch using the new uplink, but client devices can't seem to send their traffic through. The IP routing table looks fine with the correct default gateway. I don't see anything in the logs indicating dropped traffic or STP problems. Has anyone dealt with something similar? I know this old switch might be limiting, but it's all we've got right now.
3 Answers
Have you disabled the A1 interface and tested again? It could be affecting the production environment if it’s still enabled but physically disconnected.
From what you’re describing, it sounds like STP might be blocking one of your interfaces. You should also consider looking into LACP for load balancing, but remember that all the link speeds and duplex settings need to match in a LAG. Since you're switching to the new link, just ensure only one is active at a time to avoid confusion.
You could also check if there are any policies set that might be affecting routing. Sometimes, policy-based routing can impact how traffic is handled, especially with old equipment.
We haven't disabled A1 yet, but it's physically disconnected because we need to connect F6.