- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
03-06-2024 07:41 AM
After creating the sub interface ae1.1416 and using the address 10.149.124.98/27, we are receiving the error below after adding the first usable address as the VIP with 10.149.124.97
Both palos are in an active/active pair
- We are able make the commit without using the VIP
- We can use another IP address in the subnet range as the VIP and commits are successful
- Firewall has been rebooted
- Completely removed the Sub interface/VIP, committed successful, then readded the sub interface/VIP and the commit fails
- This occurs on both primary and secondary firewalls
Any suggestions on what could be causing this issue?
03-06-2024 02:52 PM
The error generally relates to a memory allocation problem, but that doesn't really line up with simply adding a VIP pushing you over that line. I'd run 'debug dataplane show cfg-memstat statistics' and see what your VSYS allocation usage is. It's possible that this is pushing you over the edge, but it seems unlikely.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!