2
Management
29
The
file
new_script_sgs
can
then
be
downloaded
with
SCP
to
the
local
management
workstation
computer
and
then
uploaded
and
executed
on
the
other
SEGs.
The
end
result
is
that
all
units
will
have
the
same
IPAddress
objects
in
their
address
book.
Note:
In
the
created
script
example
above,
adding
an
IP
address
is
done
with
the
command:
add
IPAddress...
This
is
instead
of
the
usual
way
of
qualifying
the
object
with
its
group
name:
add
Address
IPAddress...
Both
are
valid
forms
of
the
command.
If
an
object
type
can
be
uniquely
identified
with
its
name,
its
object
category
does
not
need
to
be
specified.
This
is
always
the
case
with
automatically
‐
generated
scripts.
This
shortened
form
can
also
be
used
when
typing
the
entire
command
in
a
CLI
console,
although
tab
completion
will
always
include
the
object
category.
Objects excluded from script files
Certain
aspects
of
a
configuration
that
are
hardware
dependent
cannot
have
a
script
file
entry
created
when
using
the
‐
create
option.
This
is
true
when
the
CLI
node/object
type
in
the
script
‐
create
command
is
one
of:
•
COMPortDevice
•
EthernetDevice
These
node
types
are
skipped
when
the
script
file
is
created
and
the
SEG
displays
the
message:
No
objects
of
selected
category
or
type.
Commenting script files
Any
line
in
a
script
file
that
begins
with
the
#
character
is
treated
as
a
comment.
For
example:
#
The
following
line
defines
the
sfp1
IPv4
address
add
Address
IPAddress
sfp1_ip
Address=10.6.60.10
Scripts running other scripts
It
is
possible
for
one
script
to
run
another
script.
For
example,
the
script
my_script.sgs
could
contain
the
line:
"
"
script
‐
run
‐
name
my_script2.sgs
"
"
The
SEG
allows
the
script
file
my_script2.sgs
to
execute
another
script
file
and
so
on.
The
maximum
depth
of
this
script
nesting
is
5
levels.
