3
Addressing
56
EthernetInterface and EthernetDevice object types
In
the
SEG
there
are
two
types
of
configuration
objects
that
are
used
to
manage
Ethernet
interface
operation:
EthernetInterface
and
EthernetDevice
.
The
EthernetInterface
object
is
used
to
configure
the
logical
properties
of
Ethernet
operation
such
as
IP
address.
The
EthernetDevice
object
is
used
to
specify
low
level,
driver
‐
related
properties
such
as
link
‐
speed
and
duplex.
The
following
section
covers
the
EthernetInterface
object
type.
Ethernet interface properties
The
principal
properties
for
an
EthernetInterface
object
are:
•
Interface
name
The
names
of
the
Ethernet
interfaces
are
predefined
by
the
system,
and
are
mapped
to
the
names
of
the
physical
ports.
For
example,
a
system
with
a
wan
port
will
have
an
Ethernet
interface
named
wan
.
The
names
of
the
Ethernet
interfaces
can
be
changed
to
better
reflect
their
usage.
For
example,
if
an
interface
named
dmz
is
connected
to
a
wireless
LAN,
you
might
change
the
interface
name
to
wireless
.
For
maintenance
and
troubleshooting,
it
is
recommended
to
tag
the
corresponding
physical
port
with
the
new
name.
•
IP
addresses
Each
Ethernet
interface
is
required
to
have
an
Interface
IP
Address
.
The
interface
IP
address
is
used
as
the
primary
address
for
communicating
with
the
system
through
the
specific
Ethernet
interface.
More
than
one
IP
address
can
be
allocated
to
an
Ethernet
interface.
SEG
IPAddress
objects
are
usually
used
to
define
the
IP
addresses
of
Ethernet
interfaces.
Those
objects
are
normally
auto
‐
generated
by
the
system.
For
more
information,
see
Auto
‐
generated
address
objects
on
page
65
.
When
the
SEG
is
first
started,
all
unconfigured
Ethernet
interfaces
will
be
assigned
default
addresses
from
the
localhost
subnetwork
(
127.0.0.0/8
).
•
MTU
This
determines
the
maximum
size
of
packets
in
bytes
that
can
be
sent
on
this
interface.
By
default,
the
interface
uses
the
maximum
size
supported.
•
HACritical/Sync
For
HA
cluster
nodes,
it
is
important
to
identify
those
interfaces
that
are
critical
and
those
that
are
sync
interfaces.
This
is
explained
further
in
High
Availability
on
page
157
.
