-
Title
Using the Second NIC on the K2000 -
Description
The way you can configure and utilize the second network port on the K2000 depends on the version of your K2000.
-
Resolution
K2000 version 3.3 and earlier
Prior to version 3.4, the K2000 could only use the first NIC to communicate. The second (or third or fourth) NICs did not act as failover or load balancing for the K2000. There is no way to configure this, or to split traffic types (PXE, DHCP, imaging) between the NICs.
K2000 version 3.4 and later
Beginning with K2000 version 3.4, you are able to utilize the second NIC on a physical K2000 to directly connect to a NAS device for external storage. More information on enabling external storage can be found on our K2000 Storage TechNote article.
K2000 version 3.5 and later
In addition to external storage, you are able to utilize the second NIC on a physical K2000 for link aggregation in version 3.5. When link aggregation is enabled, the second port cannot be explicitly used for offboard-storage configuration.
By default, link aggregation is not enabled on the K2000 appliance. The K2000 requires that your switch is capable of a LACP (802.3ad) connection. Before you enable link aggregation, set your switch to actively negotiate LACP. See your switch vendor's documentation for details. Passive negotiation mode does not work. If your switch is set to operate in passive mode, the switch cannot negotiate the K2000 LACP connection. For an example of a Cisco switch configuration running the IOS operating system set to active mode, view the online FreeBSD Handbook. All interfaces in each EtherChannel must be the same speed and duplex.