- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
05-18-2022 01:09 PM
Is there any PA published document for the node paths and entries in the configuration file? And how do you tell if something is a path or an entry in the config? It seems extremely painful to try and figure out an xpath to pull the data you want. Searching the forums and KB has some hints, but no over arching config format information.
For instance... i want to pull the routing table config for comparison between firewalls (because you can't sort or export the routing table in the GUI). So you have to dig thru the entire config (because there is no tab/path complete) and eventually figure out you want the "/devices/localhost.localdomain/network/virtual-router/default/routing-table" xpath.... But that doesn't work, because apparently some of those are entries, not paths, but there is no way to know that in the config file itself. So you finally come up with a command through trial and error:
show config running xpath "devices/entry[@name='localhost.localdomain']/network/virtual-router/entry[@name='default']/routing-table"
Surely there is an easier way?
05-18-2022 02:05 PM
I can't say I've ever seen this documented anywhere, its been more of something that you just kind of pick up on as you work with the platform more.
You can download the configuration file itself and have an IDE like VisualStudio Code that will actually parse the XML for you and list everything out. That or just having a good look at the structure of the configuration file itself would probably be faster than trial and error.
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!