03-05-2012 11:43 AM
on 4.1.3 - When doing a commit covering multiple vsys's fails, the system will not specify which vsys caused the error. Can anyone please give any advice on why it is doing this. We are doing this directly from the Firewall device directly and not from Panorama.
We get this problem with any commit error. It doesn't really matter what it is. Just create a couple of vsys's. Have one that works correctly and another that has errors. Do a full commit and it won't tell you which vsys is having problems. You can figure it out by systematically choosing which vsys to exclude from the commit and when it works you know at that point the vsys you didn't select is the one with the error. While this method works for a 2 or 3 vsys it is not scalable.
Any advice on what is causing this would be great.
03-05-2012 11:58 AM
Did you click on the "commit all failed" link under Panorama > Managed Devices to check for any errors?
This should explain which VSYS is having the issue.
03-05-2012 11:58 AM
Did you click on the "commit all failed" link under Panorama > Managed Devices to check for any errors?
This should explain which VSYS is having the issue.
03-05-2012 01:09 PM
It shows the same thing under managed devices. Does not show what vsys failed or what exactly failed.
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!
