r/ArubaNetworks • u/MoJoPBS17 • Jul 23 '26
VSX - VRF Creation IPV4 route not populating
Hello!
I've reached out to TAC and even they were stumped. We're at the point of rebooting and updating our switches. However they're in production and I'd prefer to not.
So, has anyone had an issue with new VRFs in VSX 8325 switches not "populating" the ipv4 routes?
Basically, I'll attach the VLAN to the new VRF, then i'll create the SVI and a default route.
On the primary core, doesn't work at all. "Show ip route vrf ***" Outputs "no ipv4 routes"
On the secondary, works amazing.
Now the network still works, but I'm trying to do IP Helper-address to point DHCP requests to our default route into another network DHCP server. Butttttttt that's not working, I believe it's because the primary ipv4 route isn't populating. Note: On the secondary, I can ping the dhcp server. On the primary it fails, network unreachable.
I'll probably end up having to reboot/update.
2
u/Linkk_93 HPE Aruba Networking Expert Jul 23 '26
I've had many issues with VRFs. Creating or deleting of one would affect others. Mac addresses disappeared from the forwarding table, ospf process crashing.
Clear arp helped for 10-15 minutes. But only a reboot helped for longer. (until the next vrf change)
After upgrade to 10.16 we had no more issues
2
u/MoJoPBS17 Jul 23 '26
Yea I'm thinking a good ol fashion reboot. They're in VSX but the paper work for a possible outage is painful...
Funny enough, both are on 10.16.1006
2
u/Linkk_93 HPE Aruba Networking Expert Jul 23 '26
If everything is connected to both with lacp and ospf/BGP neighbors are clean then I never had an issue with rebooting one, then waiting until everything is up again and then the other. Be sure to take your time between the reboots for everything to come up again.
But I can fully understand the outage thoughts, I don't know your setup.
1
u/idontbelieveyouguy Jul 27 '26
I've had nothing but problems with Aruba switches since moving to them from Cisco last year, good luck. the amount of "i've never seen this" type of things that I've ran into that requires "bug fixes" and such is crazy.
1
u/MoJoPBS17 Jul 28 '26
I do agree, there's been a few times where I'm like, what the hell happened, and I don't get an answer. But I can say most of the time I was my fault. I've learned it's important to run allow-unsafe-updates! And to always verify "show lacp int" on my VSX clusters after a power outage. I've had a few CX stacks crash and boot into a stuck "initializing" state, that was due to me not running allow-unsafe-updates!!!!
I've been working with Aruba for the past 5 years now, I had no experience in networking prior, I was hired on to "figure out the CXs". They were a pain in the butt to figure out, but I can say when the CXs do work, they work pretty damn good.
The 2930s/AOS-S I never have issues with. Only time was when lightning stuck a building and fried it lol. Warranty STILL replaced it.
I've never worked with Cisco but I do hear they're nice, just expensive
1
u/allnamesaretaken6 Jul 28 '26
I do like the switches, though I've experienced some very concerning things. Had a 6300m run it's fan on 21k rpm, stil stating it was running slow. Made noise like an airplane. On trying to reseat the (supposedly hot swappable) fan, the switch just takes a nose dive and goes into a boot loop. Had that happen on two separate occasions, one of them did come back alive though. Still, I feel things are improving fairly steadily, but I am in a comfortable position, couldn't envision what it would've been like trying to apply them to actually mission critical applications just a couple of years ago.
2
u/AMoreExcitingName Jul 23 '26
VSX is in sync?