2
Management
20
Selecting object categories
With
some
categories,
it
is
necessary
to
first
choose
a
member
of
that
category
with
the
cc
(change
category
or
context)
command
before
individual
objects
can
be
manipulated.
This
is
the
case,
for
example,
with
routes.
There
can
be
more
than
one
routing
table,
so
when
adding
or
manipulating
a
route,
you
must
first
use
the
cc
command
to
identify
which
routing
table
you
are
interested
in.
Suppose
a
route
is
to
be
added
to
the
routing
table
main
.
The
first
command
would
be:
Device:/>
cc
RoutingTable
main
Device:/RoutingTable/main>
Notice
that
the
command
prompt
changes
to
indicate
the
current
category.
You
can
now
add
the
route:
Device:/RoutingTable/main>
add
Route
Interface=sfp1
Network=sfp1_net
Name=new_route1
To
deselect
the
category,
the
command
is
cc
on
its
own:
Device:/RoutingTable/main>
cc
Device:/>
The
categories
that
require
an
initial
cc
command
before
object
manipulation
have
a
“/”
character
following
their
names
when
displayed
by
a
show
command.
For
example:
RoutingTable/
.
Inserting into rule lists
Rule
lists
such
as
the
IP
rule
set
have
an
ordering
that
is
important.
With
the
add
command,
the
default
is
to
add
a
new
rule
to
the
end
of
a
list.
When
placement
at
a
particular
position
is
crucial,
the
add
command
can
include
the
Index=
property
as
an
option.
Inserting
at
the
first
position
in
a
list
is
specified
with
Index=1
in
an
add
command,
the
second
position
with
Index=2
and
so
on.
Referencing by name
You
can
optionally
name
some
objects
using
the
Name=
property
with
the
add
command.
An
object,
such
as
an
IP
rule,
will
always
have
an
Index
value
that
indicates
its
position
in
the
rule
list
but
can
optionally
be
allocated
a
name
as
well.
Subsequent
manipulation
of
such
a
rule
can
be
done
either
by
referring
to
it
by
its
index
(list
position)
or
by
using
its
assigned
name.
The
SEG
‐
100
Command
Line
Interface
Reference
lists
the
options
available
for
each
SEG
object,
including
Name=
and
Index=.
To
make
reading
configurations
easier,
it
is
strongly
advised
to
always
add
a
unique
name
to
important
objects
in
an
SEG
configuration.
For
example,
IP
rules
should
always
have
an
appropriate
name
specified
so
that
their
purpose
can
be
immediately
understood.
Using
duplicate
names
for
the
Name
option
is
allowed
but
not
recommended.