oooooh ok you probably pushed everything through panorama then, in that case you can change the vsys in the template : panorama > templates > set the default vsys in the templates
I got it! It wasn't quite that easy because there were rules on vsys1 that had been pushed down and that needed cleaned up via xml, but this got me going in the right direction. Default vsys is in a few places that needed changed as well. But thank you!!!
oooooh ok you probably pushed everything through panorama then, in that case you can change the vsys in the template : panorama > templates > set the default vsys in the templates
I have Panorama as well if that matters.
I must not be understanding your first set of instructions correctly.
admin@01fw(active)# show | match vsys1
set vsys vsys1 application
set vsys vsys1 application-group
set vsys vsys1 zone
set vsys vsys1 service
set vsys vsys1 service-group
set vsys vsys1 schedule
set vsys vsys1 rulebase security rules
Pasted in this:
set vsys vsys2 application
set vsys vsys2 application-group
set vsys vsys2 zone
set vsys vsys2 service
set vsys vsys2 service-group
set vsys vsys2 schedule
set vsys vsys2 rulebase security rules
And got:
Invalid syntax.
For all of it.
How do i make the new vsys the default vsys?
There's a few methods. you could install the migration tool and export the config file, use the tool to move things to vsys2 and re-import the config
You could also use the cli set method:
> set cli config-output-format set
> configure
# show | match vsys1
capture all the 'vsys1' specific config and replace all the 'vsys1' with 'vsys2' and then paste the whole list of new set commands
you can then decide if you want to leave vsys1, r go an change all the 'set' to 'delete' in the vsys1 commands
or you could export the config file and let a xml editor loos eon it with a find/replace