-
Notifications
You must be signed in to change notification settings - Fork 221
[Bug]: Issue parsing F5 BigIP config file #287
Comments
Please add the entire F5 configuration, including all the info mentioned above; I won't try to tackle part of this problem without seeing what else may be broken in the config. |
Sorry for delay. The entire f5 configuration is over 25000 lines and has private info. I can upload a portion with a few lines. Cheers |
The main problem is the irule config that is not formated, it is free format config. |
Sanitize the private information and please email the file to me... [email protected]. I will be forced to close this if I can't get a complete config file. |
Hello @mpenning, Here is the config: The problem is after parsing ltm rule. Cheers |
This is fixed in ciscoconfparse2 version 0.5.0 FYI... several other things in the config-f5.txt do not parse correctly, but I will handle that as a different effort (which may require a dedicated parser). |
Contact Details
[email protected]
What happened?
I am using CiscoConfigParse to parse F5 BigIP configuration files, which work very well, but i have a bug, but i think the problem is how F5 config file write the config, i explain:
if a code block contains a "{" and after contains text WITHOUT a "}" in the same LINE, the parse do not work correctly.
if a code block contains text before a "}" and not a "{" in the same LINE, the parse do not work correctly.
Config sample1 that parse OK:
Config sample2 that parse with ERROR:
Config sample3 that parse with ERROR:
CiscoConfParse Version
Version 1.7.24
What Operating System are you using?
Linux - Debian, Ubuntu, CentOS, RHEL or others
What Python version(s) have this problem?
Python 3.9
Show us how to reproduce the problem. Please tell us if the problem is specific to certain inputs or situations.
Python tracebacks
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: