Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

address-range #17

Open
magfuentes opened this issue Feb 17, 2017 · 0 comments
Open

address-range #17

magfuentes opened this issue Feb 17, 2017 · 0 comments

Comments

@magfuentes
Copy link

Hi All,

My customer is running 12.1 and did the config as "old style" , please see below:

set security zones security-zone corporate-to-mgmt1 address-book address rimnet-addm-deployment-1 range-address 10.27.126.179 to 10.27.126.188
set security zones security-zone corporate-to-mgmt1 address-book address rimnet-addm-deployment-2 range-address 10.27.63.14 to 10.27.63.17
set security zones security-zone corporate-to-mgmt1 address-book address rimnet-addm-deployment-3 range-address 10.27.63.8 to 10.27.63.12

Then, the script was ignoring these lines and breaking the connection with the address-set, generating the following error:

address-set rimnet-addm-deployment {
##
## Warning: referenced address must be defined under address-book
## Warning: referenced address must be defined under address-book
##

Thus, I added in the "upgrade script file" a new "if case" in the template gen-upgrade-cfg to cover this situation:

                                } else if ( ./range-address ) {
                                                    <range-address> {
                                                            <name> ./range-address/name;
                                                            <to> {
                                                                if ( ./range-address/to/range-high ){    
                                                                  <range-high> ./range-address/to/range-high;
                                                                }
                                                            }
                                                    } 
                                            }
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant