25.06.2013 Views

CLI Guide - WatchGuard Technologies

CLI Guide - WatchGuard Technologies

CLI Guide - WatchGuard Technologies

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Arguments<br />

None.<br />

Example<br />

WG(admin)#exit<br />

Getting started with the <strong>WatchGuard</strong> <strong>CLI</strong><br />

top command<br />

WG(admin)#top<br />

Effect<br />

Immediately returns to the top level of the<br />

<strong>WatchGuard</strong> <strong>CLI</strong> (the “WG#” prompt) from<br />

whatever level of <strong>CLI</strong> you are using.<br />

Arguments<br />

None.<br />

Example<br />

WG(admin)#top<br />

# As a result, the WG# prompt is displayed.<br />

Using keywords<br />

The <strong>CLI</strong> provides keywords such as enable, disable, and<br />

no that perform specific functions with system parameters.<br />

For example, enable and disable are used to enable and<br />

disable existing configurations such as policy schedules<br />

and system QoS settings. The following example shows an<br />

existing schedule configuration named “24_7_Schedule”<br />

being enabled:<br />

WG(config)#schedule 24_7_Schedule<br />

enable<br />

The keyword no functions as a simple “on/off” switch for<br />

configuration components, as shown in the following<br />

example:<br />

WG(config)#denial_of_service no -<br />

pingofdeath<br />

<strong>WatchGuard</strong> Command Line Interface <strong>Guide</strong> 15

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!