topic Re: VSX in Firewall and Security Management

VSX

fatalXerror — Mon, 09 Dec 2019 12:03:32 GMT

Hi Guys,

Is it normal in VSX CLI that even if I go into a VS then I do "show configuration", it always shows me the VS0?

How can I do a "show configuration" per each VS? I am running R80.20.

Thanks

Re: VSX

Sigbjorn — Mon, 09 Dec 2019 12:26:40 GMT

You need to use set virtual-system <vs id> before running clish commands.

Re: VSX

fatalXerror — Mon, 09 Dec 2019 12:37:39 GMT

Hi @Sigbjorn , I tried that way already but it gives me the VS0 configuration.

Re: VSX

Sigbjorn — Mon, 09 Dec 2019 12:41:15 GMT

Well, it depends on what you are looking for.

It will for example always show you all interfaces, and the common settings of the vsx itself. But you can view VS specific routes by setting the virtual-system first.

Is there any information in particular you're looking for?

Re: VSX

fatalXerror — Mon, 09 Dec 2019 12:47:43 GMT

Hi @Sigbjorn ,

I am looking for all configuration related to a particular VS.

For example, I want to know the interfaces, routes, and other configurations associated to VS1 itself and not the others. Is that possible?

Like in Cisco ASA multiple context, if I go inside the context then I do show run, it will just show me the configuration related to that context.

Thanks

Re: VSX

Sigbjorn — Mon, 09 Dec 2019 12:51:33 GMT

You won't find all that information with a simple clish command in VSX.

Try vsx_provisioning_tool -o "show vd name <vs name>" from the management server.

Re: VSX

fatalXerror — Mon, 09 Dec 2019 12:59:28 GMT

Hi @Sigbjorn , thanks for the feedback.

I see, noted on that.

This command, will show the configuration for s specific VS?

Thanks

Re: VSX

Brian_Deutmeyer — Mon, 09 Dec 2019 14:25:34 GMT

If you do a 'set-virtual system X', then 'show configuration', that will show you all configuration related to that virtual system that isn't interface related. If you have any dynamic routing configured, DHCP relay, etc. that will show there. You can see the interfaces associated with a VS by doing 'ifconfig' in expert mode (vsenv X; ifconfig).