2
Management
28
Listing scripts
The
script
command
without
any
parameters
lists
all
the
scripts
currently
available
and
indicates
the
size
of
each
script
as
well
as
the
type
of
memory
where
it
resides
(residence
in
non
‐
volatile
memory
is
indicated
by
the
word
“Disk”
in
the
Memory
column).
Device:/>
script
Name
Storage
Size
(bytes)
‐‐‐‐‐‐‐‐‐‐‐‐‐‐ ‐‐‐‐‐‐‐‐‐‐‐‐ ‐‐‐‐‐‐‐‐‐‐‐‐‐‐
my_script.sgs
RAM
8
my_script2.sgs
Disk
10
To
list
the
content
of
a
specific
uploaded
script
file,
for
example,
my_script.sgs
,
the
command
would
be:
Device:/>
script
‐
show
‐
name=my_script.sgs
Creating scripts automatically
When
the
same
configuration
objects
needs
to
be
copied
between
multiple
SEGs,
one
way
to
do
this
with
the
CLI
is
to
create
a
script
file
that
creates
the
required
objects
and
then
upload
to
and
run
the
same
script
on
each
device.
If
a
SEG
installation
already
has
the
objects
configured
that
need
to
be
copied,
running
the
script
‐
create
command
on
that
installation
provides
a
way
to
automatically
create
the
required
script
file.
This
script
file
can
then
be
downloaded
to
the
local
management
workstation
and
then
uploaded
to
and
executed
on
other
SEGs
to
duplicate
the
objects.
For
example,
suppose
the
requirement
is
to
create
the
same
set
of
IPAddress
objects
on
several
SEGs
that
already
exist
on
a
single
security
gateway.
The
administrator
would
connect
to
the
single
gateway
with
the
CLI
and
issue
the
command:
Device:/>
script
‐
create
Address
IPAddress
‐
name
new_script.sgs
This
creates
a
script
file
called
new_script_sgs
that
contains
all
the
CLI
commands
necessary
to
create
all
IPAddress
objects
in
that
gateway’s
configuration.
The
created
file’s
contents
might,
for
example,
be:
add
IPAddress
sfp1_ip
Address=10.6.60.10
add
IPAddress
sfp1_net
Address=10.6.60.0/24
add
IPAddress
sfp1_br
Address=10.6.60.255
add
IPAddress
sfp1_dns1
Address=141.1.1.1
"
"
"