Table of Contents
Advertisement
Changing the Multihoming Property to Strict (CLI)
Virtual Network Interface Cards (VNICs) - VNICs allow single or aggregated
■
Ethernet datalinks to be split into multiple virtual (Ethernet) datalinks. VNICs can
be optionally tagged with VLAN IDs, and can allow physical network port sharing
in a cluster. Step-by-step instructions can be found in
Networking" on page 214
Note -
The IEEE802.3ad (link aggregation) standard does not explicitly support aggregations across
multiple switches, but some vendors provide multi-switch support via proprietary extensions. If
a switch configured with those extensions conforms to the IEEE standard and the extensions are
transparent to the end-nodes, its use is supported with the appliance. If an issue is encountered,
Oracle support may require it to be reproduced on a single-switch configuration.
The following datalink settings are available:
TABLE 13
Property
Name
Speed
Duplex
VLAN
VLAN ID
VNIC
MTU
80
Oracle ZFS Storage Appliance Administration Guide, Release OS8.6.x • September 2016
below.
VNIC-based and VLAN-based datalinks cannot share the same VLAN ID.
Datalink Settings
"Clustering Considerations for
Description
Use the defined custom name. For example: "internal",
"external", "adminnet", etc.
Use the defined speed. Valid values are auto, 10, 100,
1000 and 10000, representing autonegotiation, forced
10Mbit/sec, forced 100Mbit/sec, forced 1Gbit/sec and
forced 10Gbit/sec. Speed and duplex must be either both
forced to specific values or both set to autonegotiate. Not
all networking devices support forcing to all possible
speed/duplex combinations. Disabling autonegotiation
is strongly discouraged. However, if the switch has
autonegotiation disabled, it may be necessary to force
speed (and duplex) to ensure the datalink runs at the
expected speed and duplex.
Use the defined transmission direction. Valid CLI values
are auto, half, and full, representing autonegotiation,
half- and full-duplex respectively. Speed and duplex
must be either both forced to specific values or both set
to autonegotiate.
Use VLAN headers.
Use the defined VLAN identifier; optional for VNICs.
Use a VNIC.
Use the defined maximum transmission unit (MTU)
size. The default MTU is 1500 bytes. Specify a lower
MTU (minimum 1280) to leave packet headroom (for
example, for tunneling protocols). Specify a larger MTU
(maximum 9000) to improve network performance.
All systems and switches on the same LAN must be
configured with the chosen MTU. After the MTU value
Advertisement
Table of Contents
