2
Management
41
The
restore
will
be
successful;
however,
the
processors
use
different
logical
names
for
their
Ethernet
interfaces.
For
example,
the
interface
sfp1
on
the
DPB1
processor
corresponds
to
the
sfp4
interface
on
the
DPB2
processor.
The
restored
configuration
will
continue
to
use
original
interface
names
such
as
sfp1
after
the
restore,
but
these
will
no
longer
match
the
interface
text
labels
on
the
module’s
exterior.
This
interface
renaming
can
cause
confusion
and
should
therefore
be
avoided.
Restoring the default configuration
A
special
case
for
using
the
backup
command
for
restoring
a
configuration
is:
Device:/>
backup
‐
reset
This
restores
the
default
configuration
for
the
security
gateway.
The
following
points
should
be
noted
about
a
reset:
•
Since
the
default
configuration
will
be
restored,
the
‐
reset
option
should
be
issued
only
from
an
SSH
client
that
is
connected
to
the
default
management
interface
using
the
default
management
IP
address,
or
from
a
console
that
is
connected
to
the
RS232
serial
console
interface.
Otherwise,
the
connection
to
the
CLI
will
be
lost
after
the
command
is
issued.
•
The
current
SEG
configuration
will
be
lost
after
a
reset
and
cannot
be
recovered.
For
this
reason,
this
command
option
should
be
used
with
caution.
To
remind
the
administrator
that
the
command
is
irreversible,
a
prompt
appears
to
ask
if
the
SEG
should
proceed:
Device:/>
backup
‐
reset
This
will
reset
the
current
configuration
to
the
system's
default
configuration
and
reboot
the
system.
This
change
is
not
reversible.
Are
you
sure
you
want
to
continue?
[yes/no]:
yes
Resetting
configuration
to
system
default...
Reset
configuration
to
default
successful.
Restarting
the
SGW:done.
In
CLI
scripts,
the
‐
force
option
must
be
used
with
‐
reset
:
Device:/>
backup
‐
reset
‐
force
This
is
necessary
since
a
script
cannot
respond
to
the
prompt.
