9
High Availability
163
Setting interface IP addresses
Each
interface
on
both
the
master
and
slave
units
has
two
IP
addresses
associated
with
it:
1.
The
shared
IP
address
The
shared
IP
address
is
the
address
that
is
used
during
general
operation
of
the
HA
cluster
and
is
the
address
used
in
constructing
configuration
security
policies.
It
is
always
the
same
for
each
of
the
interfaces
in
a
matching
pair
on
master
and
slave.
If
the
interface
sfp1
is
to
have
the
shared
IPv4
address
10.6.12.1,
the
CLI
command
to
set
this
is:
Device:/>
set
Interface
EthernetInterface
sfp1
IPaddress=10.6.12.1
This
command
is
repeated
for
both
the
master
and
slave.
2.
The
private
IP
address
A
private
IPv4
address
is
also
assigned
to
each
interface
but
it
is
not
the
same
for
a
pair
of
interfaces.
Each
interface
gets
a
unique
address
so
that
it
is
possible
to
connect
to
a
specific
interface
on
a
specific
node
in
the
cluster.
Connection
to
this
address
could
be
for
the
purpose
of
SEG
management
or
to
ping
the
interface.
For
allocating
the
private
IP,
each
interface
has
two
properties
associated
with
it:
PrivateIP:0
and
PrivateIP:1
.
PrivateIP:0
is
the
private
IPv4
address
of
the
master
interface
in
an
interface
pair
and
PrivateIP:1
is
the
private
address
of
the
corresponding
slave
interface
in
a
pair.
For
example,
if
10.6.12.10
is
the
private
IPv4
address
of
the
interface
sfp1
on
the
master
and
10.6.12.11
is
the
private
IP
of
interface
sfp1
on
the
slave,
the
following
command
should
be
issued:
Device:/>
set
Interface
EthernetInterface
sfp1
PrivateIP:0=10.6.12.10
PrivateIP:1=10.6.12.11
This
command
is
repeated
for
both
the
master
and
slave
and
can
be
combined
with
the
command
for
setting
the
shared
IPv4
address.
As
seen
in
this
example,
it
is
usual
to
use
private
and
shared
IPv4
addresses
from
the
same
network.
It
may
seem
redundant
that
the
private
IP
of
both
master
and
slave
are
set
on
both
cluster
nodes.
However,
like
other
elements
of
a
configuration,
these
private
IPv4
addresses
are
mirrored
between
master
and
slave.
If
a
management
interface
is
connected
to
the
master
and
the
private
address
PrivateIP:1
for
the
slave
is
changed
only
on
the
master,
it
allows
the
address
to
be
automatically
copied
over
to
the
slave's
configuration.
All
interfaces
in
a
cluster
will
require
a
shared
IP
but
it
is
not
necessary
that
every
interface
has
a
private
IP.
The
private
IP
is
used
for
SSH
management
access
as
a
source
IP
for
log
messages
and
to
allow
pinging
of
the
interface
on
one
node
in
the
cluster.