Introduction, Adapter aliases and team identification – Dell Emulex Family of Adapters User Manual

Page 780

Advertising
background image

OneCommand NIC Teaming and VLAN Manager User Manual

P009415-01A Rev. A

5. OneCommand NIC Teaming Manager Command Line Interface

Introduction

780

5. OneCommand NIC Teaming Manager

Command Line Interface

Introduction

The OneCommand

NIC Teaming Manager Command Line Interface (OCTeamCmd)

is a companion to the OneCommand NIC Teaming and VLAN Manager. Use the

OCTeamCmd in scripted operations from within shell scripts or batch files.
Each time you run this application from the command line, a single operation is

performed. The first parameter of this command is the requested operation. When the

specified operation is completed, the command prompt is displayed. Some of the

OCTeamCmd commands require one or more additional parameters that specify the

nature of the command.
When creating or modifying teams and VLANs, changes to adapter names may not

completely propagate through the system until the system has been restarted. Before

the systems is restarted, the teams and VLANs will function properly, however some

operating system facilities may continue to use the adapter names before the change

was made.

Note: Do not configure VLANs on adapters used with NIC teaming.

Note: On Server Core systems, utilities such as SCONFIG and SYSTEMINFO identify

a network object with the Device Manager friendly name the object had at boot

time or when the object was created, whichever is most recent. As a result,

newly created teams and VLANs are identified generically until the system is

rebooted. Until a reboot, these utilities do not identify teams with their team

names nor do these utilities identify VLANs with their VLAN IDs. Likewise,

when deleting teams or removing adapters from teams, these utilities continue

to show such an adapter with its team member name until a reboot occurs. The

OCTeamCmd does show the correct name, even though these Server Core

utilities do not. Rebooting is not necessary for proper system operation.

However, if you manually assign IP addresses to teams and VLANs, you may

want to reboot as the IP address assignment is easier when the network objects

are properly identified.

Adapter Aliases and Team Identification

Adapters are identified within Windows by using the adapter name.
The OCTeamCmd also uses aliases to identify physical adapters. Adapter aliases are

assigned by the OCTeamCmd as adapters are discovered and take the form of “nicX”

where “X” is a unique integer. Adapter aliases, once assigned, exist for as long as the

adapter's GUID does not change. Any events that cause Windows to treat an existing

adapter as if it is newly installed, causes a new alias to be assigned to that adapter the

next time a OCTeamCmd command is run.

Advertising