Home

OneCommand NIC Teaming and VLAN Manager

1. ccceeeecceetttereeeeeeeetee 32 Restoring the NIC Teaming Configuration cccccccecteecseeeeeeeeeeeseenaees 32 Showing NIC Teaming and VLAN Contourations 33 SOWING EE 34 SNOW TO LEE 34 Showing VLAN Adatpters 35 Showing Free Adapters ccccccccceceeeeeseeneeeeeeeeeeeeeeeeeecaaeeeeeeeeseeeecsaeeeeeees 35 OneCommand NIC Teaming and VLAN Manager User Manual Page iii Table of Contents Showing Team or Adapter Details 36 Showing VLAN IDe nnne 37 Cre tee RR E Lu BE 37 Peleting a TS AM E 38 Addingia VEAN Reeeerrree ee ee eee ne eee eee 39 Deleting a EE 40 Appendix A Load Balancing Use Cases 00 ccceeceeeeeeeee eee eeeeceeeeeeeeeeeeeenaeeeeeeteee 41 Perceived POM MEO GG E 41 When to USC 2 eeeecece ccc eceeeeeeeeeeeeeaaaeeeeeeeeeeeeaaaaeeeeeeeeeeeaaaeeeeeeeeeeeesaaaaeeeeeeeeeesaaa 41 When Not to DEE 41 Destination ML ANEN 41 When to EE 41 When Not to Use ccc cece cece cece eee eeeeeeeeee eee eeeeaaaeeeeeeeeaaaaaaaeeeeeeeeeaaaaaeeeeseeeeees 41 Destination IP 42 Eeer ana tanaresstasahsectanetanaiasaiascianetsuuaananaredaaa tune 42 When Not to Use cece cece cee ee eee eeeeeeeeeeeeeeeeeeaaaaeeeeeeeeaaaaaaeeeeeeeeeeaaaaneeeeeeeeeess 42 OneCommand NIC Teaming and VLAN Manager User Manual Page iv gt G EMULEX Overview The Emulex OneCommand Network Interface Card NIC Teaming and Virtual Local Area Network VLAN manager provides the ability to team two or more NIC VNIC ports It also allows you to add o
2. on page 4 For team types other than failover select the Load Distributed By list and select from the following Perceived Port Load Selects the port with the least traffic load for the session Destination MAC Address Performs an XOR on the destination MAC address to determine which port should carry the load Destination IP Address Performs an XOR on the destination and source IP address to determine which port should carry the load OneCommand NIC Teaming and VLAN Manager User Manual Page 9 gt S EMULEX 6 When the team type selected is Failover choose an AutoFailback mode of Enabled or Disabled Note If you are creating a failover team when one already exists you must reboot the system before the newly created failover team is capable of failing over You can continue to create additional teams before rebooting however 7 The Available Network Adapters area lists adapters that are not members of any team or any VLAN bound adapter To add an adapter to the team select the adapter from the Available Network Adapters list and click Add The adapter appears in the Team Member Adapters list Repeat for each desired adapter in the team Note NICs shown as members of the same port by OneCommand Manager should not be included on the same team Note In Windows Server 2008 systems a down arrow represents a disabled adapter You cannot add a disabled adapter to a team A warning message is displayed if you
3. A group of unbound adapters working together and presented as a single adapter to applications e VLAN A Virtual LAN allows computers or virtual machines hypervisor guests to act as if they are connected by a private directly connected network You can assign VLANs to teams or individual adapters e VLAN Bound adapter A single adapter to which you assigned VLANs This adapter cannot be part of a team These are also called VLAN adapters e Available adapter An adapter that is not a member of a team and has no assigned VLANs This adapter is also called a free adapter OneCommand NIC Teaming and VLAN Manager User Manual Page 2 gt G EMULEX Failover FO A failover team consists of two members a primary and a secondary member Only one member is active at a time When a team is created the primary member is active and the secondary member is passive but only one member is active at a time When the primary team member disconnects due to link down link disabled or any other reason the failover mechanism selects the secondary team member which is in a link up state and traffic continues When a previously failed primary team member reports a link up state failback to the primary member occurs only if the team was created with Auto Failback enabled For teams created with AutoFailback disabled traffic will continue on the secondary adapter By default all the team members use the same MAC address the MAC address of the pri
4. Continued Hexadecimal Error Code Signed ansigned Decimal Description Decimal Value Value 0x8F000037 1895825353 2399141943 A reboot is needed for just made changes to take effect 0x8F000038 1895825352 2399141944 A reboot request is pending It is not safe to make NIC teaming configuration changes while the Windows operating system is in this state 0x8F000039 1895825351 2399141945 The OneCommand NIC Teaming and VLAN Manager cannot be uninstalled while teams or VLANs are defined The teams or VLANs must be deleted first 0x8F00003A 1895825350 2399141946 The team name is not unique 0x8F00003B 1895825349 2399141947 The command line interface cannot be found 0x8F00003C 1895825348 2399141948 The application is invoked without administrator privileges 0x8F00003D 1895825347 2399141949 The number of teams configured is already at the maximum allowed 0x8F00003E 1895825346 2399141950 The number of VLANs configured is already at the maximum allowed 0x8F00003F 1895825345 2399141951 A value on the command line cannot be converted to a numeric value Verify that values are correct 0x8F000040 1895825344 2399141952 VLANs cannot be assigned to this adapter because the adapter is a team member disabled or cannot be found 0x8F000041 1895825343 2399141953 One or more of the VLAN IDs are already in use by this adapter or team 0x8F000042 1895825342 2399141954 The adapter or team
5. Documents and Settings Adninistrator gt Figure 14 Network Connection information OneCommand NIC Teaming and VLAN Manager User Manual Page 19 gt S EMULEX Deleting Hyper V Teams When deleting a team that was configured in a virtual machine you must complete the following procedures 1 Remove the adapter from the virtual machine See Removing an Adapter from the Virtual Machine on page 20 2 Remove the team from the Virtual Network Manager See Deleting the Adapter from the Virtual Network Manager on page 22 3 Remove the team using the OneConnect NIC Teaming Manager See Removing the Team Using the OneConnect NIC Teaming Manager on page 23 4 Disable the Microsoft Virtual Network Switch Protocol for each adapter in the deleted team See Disabling the Microsoft Virtual Network Switch Protocol for an Adapter on page 23 Removing an Adapter from the Virtual Machine 1 Open Hyper V Manager 2 Ensure that the virtual machine is turned off 3 Inthe Results pane under Virtual Machines right click the name of the virtual machine and click Settings E Hyper V Manager Gla Fie Action View Window Help e e lzlelRles 23 Hyper V Manager Ga WIN U6H78R28TB3 Figure 15 Hyper V Manager Virtual Machines page OneCommand NIC Teaming and VLAN Manager User Manual Page 20 gt S EMULEX The Settings for the virtual machine page are displayed RA Settings for Nu of
6. EMULEX gt OneCommand NIC Teaming and LAN Manager Create Team x Create a unique Team Name and select a Team Type then use the controls below to add remove adapters Team Name Sue apple ue nee ab Team Type Failover FalBack Load Dart ed By Perceived Port Load Enabled C Disabled m Team Member Configuration Available Network Adapters Emulex OneConnect OCm11102 N X NIC TOE 8 Local Area Connection 11 Emulex OneConnect OCm11102 N X NIC TOE 7 Local Area Connection 10 Emulex OneConnect OCm11102 N X NIC TOE 6 Local Area Connection 9 Emulex OneConnect OCm11102 N X NIC TOE 5 Local Area Connection 8 Emulex OneConnect OCm11102 N X NIC TOE 4 Local Area Connection 7 Emulex OneConnect OCm11102 N X NIC TOE 3 Local Area Connection 6 Emulex OneConnect OCm11102 N X NIC TOE 2 Local Area Connection S Emulex OneConnect OCm11102 N X NIC TOE Local Area Connection 4 H Add Remove Team Member Adapters zeg Le Figure 2 OneCommand NIC Teaming and VLAN Manager Create Team dialog box 3 4 Enter a unique team name using up to 79 characters Choose a team type Valid options Failover For more information see Failover FO on page 3 Load balancing For more information see Smart Load Balancing SLB Team Load Balancing on page 3 LACP For more information see Switch Controlled Teaming Link Aggregation Control Protocol LACP
7. Properties page 4 Highlight the team virtual network 5 Click Remove and follow the prompts Removing the Team Using the OneConnect NIC Teaming Manager See Removing a Team on page 10 Disabling the Microsoft Virtual Network Switch Protocol for an Adapter Open the Network Connections window 2 Select the adapter that was a member of the removed team right click and select Properties from the context menu 3 The Network Adapter Properties dialog box opens OneCommand NIC Teaming and VLAN Manager User Manual Page 23 EMULEX d OO Local Area Connection 6 Properties EN Networking Connect using Emulex OneConnect 00m11102 N X NIC TOE This connection uses the following items Client for Microsoft Networks wv E QoS Packet Scheduler Ka A File and Printer Sharing for Microsoft Networks v Emulex OneConnect NIC Teaming and Multiple VLAN Microsoft Virtual Network Switch Protocol i Pia Internet Protocol Version 6 TCP IP v6 Install Uninstall Properties Internet Protocol Version A TCP IPv4 Description Allows your computer to access resources on a Microsoft network OK Cancel Figure 19 Network Adapter Properties dialog box 4 Clear the Microsoft Virtual Network Switch Protocol checkbox 5 Click OK to apply the new setting and close the Network Adapter Properties dialog box 6 Repeat this pr
8. VLAN id VLAN tag Number An optional parameter specifies the total number of VLANs to be deleted Valid values range from 1 to 4 Example C Program Files Emulex NIC Teaming gt OCTeamCmd exe delete vlan mylbteam 3 4 ULAN 3 deleted from mylbteam LAN 4 deleted from mylbteam ULAN 5 deleted from mylbteam LAN 6 deleted from mylbteam C Program Files Emulex NIC Teaming gt OCTeamCmd exe delete vlan nic6 166 2 ULAN 166 deleted from nich LAN 161 deleted from nic6 C Program Files Emulex NIC Teaming gt OCTeamCmd exe delete vlan ULAN 3 deleted from nich C Program Files Emulex NIC Teaming gt OneCommand NIC Teaming and VLAN Manager User Manual Page 40 gt G EMULEX APPENDIX A Load Balancing Use Cases Perceived Port Load This method automatically distributes TCP IP traffic across team member channels by examining traffic load history patterns When to Use Favorable types of traffic patterns for this balancing method include web traffic HTTP HTTPS and e mail traffic SMTP POP3 New TCP IP connections are assigned to the more lightly loaded member channel links to balance traffic loading across all members over time Only TCP IP traffic is balanced and distributed other non connection oriented traffic such as UDP IP and non IP traffic such as IPX SPX and others is assigned to a single default team member and is not balanced Once a connection is opened and assigned to a member link that TCP IP connection s traffic
9. are identified using the team name and network manager network connection name Parameters None OneCommand NIC Teaming and VLAN Manager User Manual Page 34 gt S EMULEX Example C NProgran PilcaNEnulex NIC Teaning gt docteamcnd show teams Device Manager Name Enulex OncConnect Teanfidapter 9 Hetwork Conn Device Nanc not available Connection Status not connected Tecan type Failover utonatic Failhack cnabled HAC ddross Link Speed Sand se Scnt Packcts Received enbers Enulex OneConnect OCe10102 F NIC TOE Local Area Connection 5 CPrioayui HP NC382i DP Multifunction Gigabit Server Adapter 3 Local Area Connection 3 wae ULANL3S 186 192 124 232 ULAN_34 189 192 122 239 Device Manager Name Enulex OncConnect Teanfidapter HL Nctwork Conn Device Nanc Local firca Connection 97 Connection Statuc connected IPv4 10 0 1 232 Tean type Load Balancing Hash type destnac HAC Addyvess 66 00 C9 9D A4 44 Link Speed 28 6 Gbps Packet Sent 42 Packets Received 169 Enulex OneConnect OCeiG192 F NIC TOE t4 Local rea Connection 8 Prinary gt Enulex OneConnect OCe18192 F NIC TOE 2 Local frea Connection 6 a OneConnect OCe1G8162 P NIC TOE 3 Local frea Connection Showing VLAN Adapters Syntax OCTeamCmd exe show vlanadapters Description This command shows all VLAN bound adapters and the VLANs assigned to them Adapters are identified using their name network manager network connection name
10. create team am nic4 nic6 Successfully created team myteam C Program Files Emulex NIC Teaming gt m Deleting a Team Caution Removing a team may take several minutes Prematurely cancelling this operation may result in partial removal of a team or VLAN which may lead to future teaming issues including system instability Note Do not remove a team or VLAN while they are carrying traffic If you do unpredictable results will occur Syntax delete team lt team id gt gt G EMULEX failow Description This command deletes a team from the system and deletes any VLANs assigned to the team Parameters Team id Team to be deleted Example C Program Files Emulex NIC Teaming gt OCTeamCmd exe delete team mylbteam Successfully deleted team mylbteam Program Files Emulex NIC Teaming gt OneCommand NIC Teaming and VLAN Manager User Manual Page 38 gt S EMULEX Adding a VLAN Syntax add vlan lt team id adapter id gt lt vlan id gt number Description This command assigns one or more VLANs to a team or an adapter You can only assign a VLAN to teams and Emulex adapters A VLAN is specified using the number to be assigned as the VLAN ID valid values range from 1 to 4094 If you specify a duplicate VLAN ID no VLANs that you request in the command are created You may assign a single team or adapter no more than 4 VLANs You can assign more than 1 VLAN by including the optional
11. gt lt EMULEX OneCommand NIC Teaming and VLAN Manager Version 2 6 Windows Server 2008 Windows Server 2008 R2 User Manual Emulex Connects P007631 01A Rev A Servers Storage and People gt G EMULEX A Copyright 2003 2012 Emulex All rights reserved worldwide No part of this document may be reproduced by any means or translated to any electronic medium without the prior written consent of Emulex Information furnished by Emulex is believed to be accurate and reliable However no responsibility is assumed by Emulex for its use or for any infringements of patents or other rights of third parties which may result from its use No license is granted by implication or otherwise under any patent copyright or related rights of Emulex Emulex the Emulex logo AutoPilot Installer AutoPilot Manager BlockGuard Connectivity Continuum Convergenomics Emulex Connect Emulex Secure EZPilot FibreSpy HBAnyware InSpeed LightPulse MultiPulse OneCommand OneConnect One Network One Company SBOD SLI and VEngine are trademarks of Emulex All other brand or product names referenced herein are trademarks or registered trademarks of their respective companies or organizations Emulex provides this manual as is without any warranty of any kind either expressed or implied including but not limited to the implied warranties of merchantability or fitness for a particular purpose Emulex may make improvements and changes to the
12. is never moved to a new link without regard to the out of balance level the overall team might be experiencing There must be a consistent stream of new TCP IP connections and typically a consistent stream of terminated TCP IP connections which have finished work for this traffic balancing method to perform well This type of process works well for servers that process a lot of small transactional operations that start and then end individual TCP IP connections for each transaction Some database protocols involve new connections for each query these also work well with this method When Not to Use Connections that are very long lived or which are not TCP IP based are a poor fit with this choice of balancing technique Examples of long lived connections are most TCP IP storage traffic such as NFS Unix Linux others CIFS Windows and iSCSI widespread usage Destination MAC This method is team member channel selection hashing based on the destination MAC address When to Use Use this method when the local system is the server and the server communicates through a NIC team to a switch and then to many other systems on the local subnet typically many client laptop or desktop systems To be effective the remote systems must be located on the same IP address subnet as the server team is located Use this method only when the server system communicates with many clients or other servers on the local subnet Only systems that are on t
13. ke pos You can use this setting to add devices to your virtual machine Boot From CO Select the devices you want to add and cick the Add button Virtual processors WD WE Controler 0 E WE Controller 1 __ sds Ana kas A network adapter requires drivers that are installed when you install integration re services in the quest operating system E SCSI Controler F Network Adapter Local Area Connection 2 Virtual N F coms None F come Nore Kl Diskette Orive Nore M ment I Name VetOne_Win2003 Z b e atve Serves Al services offered A Srapsher File Location C ProgranDsts Microsoft Windo DD Automatic Rat Action Restart previously runt Ze Automatic Rop Action Save Figure 11 Hyper V Manager Settings for a virtual machine page OneCommand NIC Teaming and VLAN Manager User Manual Page 17 d gt G EMULEX Note Figure 11 shows a network adapter To use a network adapter you may need to install integration services in the guest operating system 12 In the left pane select Add Hardware 13 In the right pane select a network adapter and click Add The Network Adapter page is displayed RA Settings for VirtOne isi xX betee woco Q Network Adapter T Add Hardware sk B10S Specify the configuration of the network adapter or remove the network adapter Book From CH Network 9 Morey fEmdex F sloverTeam One DI Processor fet 2 Virtua processors G Dynamic 5 MI e Controller 0 C State ee
14. more information OneCommand NIC Teaming and VLAN Manager User Manual Page 1 gt G EMULEX Supported Operating Systems The Windows NIC Teaming and VLAN Manager supports the following Windows Server 2008 operating systems e Windows Server 2008 x86 SP2 e Windows Server 2008 x64 SP2 e Windows Server 2008 x64 R2 e Windows Server 2008 x64 R2 SP1 e Windows Server 2008 x64 R2 with Hyper V e Windows Server 2008 x64 R2 SP1 with Hyper V Note Hyper V environments support failover teams only load balancing LACP and VLAN are not supported Why Teaming NIC teaming allows you to group multiple NICs as a single virtual device Depending on the teaming type one or more interfaces can be active When you combine multiple NICs this way the group is a team NIC teaming has several advantages e Increased bandwidth Two or more network interfaces are combined to share the load thus increasing bandwidth e Load balancing Link aggregation enables distribution of processing and communication across multiple links e Higher link availability Prevents a single link failure from disturbing traffic flow Teaming Types There are different types of teaming e Switch independent e Failover If configured for fault tolerance the system provides only failover e Smart load balancing If configured for load balancing failover is included e Switch dependent e Link Aggregation Control Protocol LACH Terminology e Team
15. number parameter The parameter specifies the total number of VLANs you wish to assign Valid values range from 1 to 4094 If there are already VLANs assigned to a team the maximum valid value of the number of VLANs to be assigned is reduced by the number of existing teams If you specify an invalid value the command is rejected without any other action being taken When you assign multiple VLANs the specified VLAN ID is used as the VLAN ID of the first VLAN That VLAN ID is then incremented to generate the VLAN ID for the next VLAN This process applies to each additional VLAN being assigned If any of the generated VLAN IDs are already in use or are outside the range of valid values the command is rejected without any other action being taken Parameters Team id If a VLAN is to be assigned to a team this is the team name Adapter id If a VLAN is to be assigned to an adapter this is the adapter alias VLAN id The number to be used as the VLAN tag Valid values range from 1 to 4094 Number An optional parameter specifies the total number of VLANs to be assigned Valid values range from 1 to 4 If there are already VLANs assigned to a team then the maximum valid value of the number of VLANs to be assigned is reduced by the number of existing teams If an invalid value is specified the command is rejected without any other action being taken Example C Program Files Emulex NIC Teaming gt OCTeamCmd exe add vlan mylbteam 3 4 nyl
16. used with CLI commands that use adapter id as a parameter Parameters None Example C Program Files Emulex NIC Teaming gt OCTeamCnd exe show aliases Alias nicS Device Manager Name Network Conn Device Alias nic4 Device Manager Name Network Conn Device Alias mnic6 Device Manager Name Network Conn Device Alias nici Emulex OneConnect 0Ce1G182 I Name Local Area Connection 7 Ee NIC TOE 2 NIC TOE OneConnect Connection mytean3 Emulex Name Local frea OneConnect Connection mytean3 Emulex Name Local Area STEE NIC TOE 2 Device Manager Name Network Conn Device Alias nic Device Manager Name Network Conn Device Alias nic2 Device Manager Name Network Conn Device Alias nic3 Device Manager Name Network Conn Device Alias nic8 Device Manager Name HP NC382i DP Multifunction Gigabit Server Name Local Area Connection do not team HP NC382i DP Multifunction Gigabit Server Name Local Area Connection 2 HP NC382i DP Multifunction Gigabit Server Name Local Area Connection 3 HP NC382i DP Multifunction Gigahit Server Name Local frea Connection 4 Emulex OneConnect O0Ce1 102 F NIC TOE Adapter Adapter 2 Adapter 3 Adapter 4 Network Conn Device Name Local Area Connection 5 Show Teams Syntax OCTeamCmd exe show teams Description This command lists all teams including their team type team members and assigned VLANs Teams
17. x vmi x Q O Network Adopter 7 Add Hardware A BIOS Specify the configuration of the network adapter or remove the network adapter Boot from CD Network E Memory Emulex Falloverteam_One gt 2048 MB sl P m MAC Address 1 Virtual processor Dynamic EI IDE Controller 0 Static Oe ne fe fs ee HD IDE Controller 1 OVO Drive Physical drive D I Enable spoofing of MAC addresses 5 SCSI Controler I Enable virtual LAN identification Network Adapter YLAN ID Local Area Connection 2 Wirtu The VLAN identifier specifies the virtual LAN that this virtual machine will use For all Network Adapter network communications through this network adapter Emulex_FaloverTeam_One Iess To remove the network adapter from this virtual machine click Remove Remove Use a legacy network adapter instead of this network adapter to perform a network based ion of the guest operating system or when integration Management services are not deet in the quest operating system 7 Name VMI 7 Integration Services All services offered e Snapshot Fie Location Combat D Automatic Start Action Restart previously running xl Kl Diskette Drive None Figure 16 Hyper V Manager Settings for a virtual machine page 4 Highlight the Team Network Adapter to be removed 5 Click Remove The Network adapter is removed from the virtual machine 6 Click OK to accept the changes and close the Settings page OneCommand NIC T
18. 0 Windows does not allow the file to open 0x8F00000D 1895825395 2399141901 The backup file has been corrupted 0x8F00000E 1895825394 2399141902 The number of NICs has changed since the backup was made 0x8F00000F 1895825393 2399141903 A different and unexpected NIC is found in the PCI slot 0x8F000010 1895825392 2399141904 A PCI slot does not contain the expected NIC 0x8F000011 1895825391 2399141905 Backup file creation failed 0x8F000012 1895825390 2399141906 Restoration failed 0x8F000013 1895825389 2399141907 No teams exist on the system 0x8F000014 1895825388 2399141908 There is an invalid number of command arguments 0x8F000015 1895825387 2399141909 Required data is not found on the command line 0x8F000016 1895825386 2399141910 The team type is not provided 0x8F000017 1895825385 2399141911 An invalid hash value is specified 0x8F000018 1895825384 2399141912 The provided number of members did not fall in the required range for the requested team type 0x8F000019 1895825383 2399141913 The adapter ID is invalid 0x8F00001A 1895825382 2399141914 The team ID is either missing or invalid 0x8F00001B 1895825381 2399141915 The team ID exceeds the maximum string length of 39 characters 0x8F00001C 1895825380 2399141916 The team ID adapter ID is invalid or missing 0x8F00001D 1895825379 2399141917 The team ID adapter ID is not found 0x8F00001E 1895825378 2399141918 The VLAN value or ID is invalid 0x8F00001F 1895
19. 1966 2399141967 Windows reports that some device configuration activity install uninstall enable disable is in progress NIC Teaming configuration changes cannot be made until that activity has completed A timeout occurred while waiting for Windows to complete the creation of a team The creation may have happened but it did not happen within 5 minutes 0x8F000050 1895825328 2399141968 A timeout occurred while waiting for Windows to complete the creation of a VLAN The creation may have happened but it did not happen within 5 minutes 0x8F000051 18958225327 2399141969 An adapter specified in a backup file could not be found on the system 0x8F000052 18958225326 2399141970 A team member is disabled Backups cannot be made while members are disabled 0x8F000053 1895825325 2399141971 Configuration changes cannot be made while OCM is running OneCommand NIC Teaming and VLAN Manager User Manual Page 30 The Command Reference Help Syntax OCTeamCmd exe help command gt G EMULEX Description The OCTeamCmd exe help command without any parameters or with the command line options of help h or lists the utility s version and all OCTeamCmd commands Parameters command The name of the CLI command Use this argument to show help for a specific command Example of help with no optional command on Administrat
20. 825377 2399141919 The hash value may be invalid or the internal structure may need to be updated 0x8F000020 1895825376 2399141920 The team type may be invalid or the internal structure may need to be updated 0x8F000021 1895825375 2399141921 Failure to retrieve the list of free adapters on the system 0x8F000022 1895825374 2399141922 Failure to retrieve the list of bound adapters on the system OneCommand NIC Teaming and VLAN Manager User Manual Page 27 gt S EMULEX Table 1 OneCommand NIC Teaming Driver and Command Line Utility Error Codes Continued OneCommand NIC Teaming and VLAN Manager User Manual g Signed Unsigned Decimal aor Hexadecimal Error Code Decimal Value Value Description 0x8F000023 1895825373 2399141923 Failed to retrieve the adapter alias list from the system 0x8F000024 1895825372 2399141924 Failed to create alias for one of the adapters 0x8F000025 1895825371 2399141925 Failed to create a team alias 0x8F000026 1895825370 2399141926 Failed to retrieve a team alias list 0x8F000027 1895825369 2399141927 Failed to read alias information from the registry 0x8F000028 1895825368 2399141928 The team name is not unique There is already a team or adapter with this name or alias 0x8F000029 1895825367 2399141929 lt Code Error gt The primary team is not set by the calling function 0x8F00002A 1895825366 2399141930 One of the
21. AN Manager Uninstaller and the OCTeamCmd utility cannot run at the same time 0x8F000003 1895825405 2399141891 The OneCommand NIC Teaming and VLAN Manager Update utility is running The OneCommand NIC Teaming and VLAN Manager Update utility and the OCTeamCmd utility cannot run at the same time 0x8F000004 1895825404 2399141892 Another copy of the OCTeamCmd utility is running only one can run at a time 0x8F000005 1895825403 2399141893 Initialization of Windows Common Controls failed 0x8F000006 1895825402 2399141894 The OneCommand NIC Teaming and VLAN Manager is not installed Presence of the driver is required for OCTeamCmd utility operation 0x8F000007 1895825401 2399141895 A file with this name already exists Backup files must have unique names 0x8F000008 1895825400 2399141896 The file cannot be found OneCommand NIC Teaming and VLAN Manager User Manual Page 26 gt S EMULEX Table 1 OneCommand NIC Teaming Driver and Command Line Utility Error Codes Continued Hexadecimal Error Code Signed Jnsigned Decimal Description Decimal Value Value 0x8F000009 1895825399 2399141897 There are too many arguments specified on the command line 0x8F00000A 1895825398 2399141898 The command is not recognized 0x8F00000B 1895825397 2399141899 The specified directory cannot be found 0x8F00000C 1895825396 239914190
22. C Teaming and VLAN Manager Do not use a previous version of the driver utilities to update the OneCommand NIC Teaming driver and NIC Teaming and VLAN Manager If you do unpredictable results will occur Note Do not update the NIC Teaming driver and NIC Teaming and VLAN Manager while H O traffic is running If you do unpredictable results will occur To update the NIC Teaming driver and the NIC Teaming and VLAN Manager while preserving the existing configuration including the IP address 1 From the Emulex website download the latest file named elxdrvr nic teaming lt version gt exe to your system 2 Double click the elxdrvr nic teaming lt version gt exe Uninstalling the OneCommand NIC Teaming Driver and the NIC Teaming and VLAN Manager To uninstall the NIC Teaming package 1 Use the Programs and Features Control Panel on all Windows Server 2008 operating systems WARNING Use the Emulex provided kit to uninstall the driver Do not use a previous version of the driver utilities to uninstall the OneCommand NIC Teaming driver and NIC Teaming and VLAN Manager If you do unpredictable results will occur Caution Uninstalling the NIC Teaming package will remove all existing teams and VLANs e For Windows Server 2008 amp Windows Server 2008 R2 select Start gt Control Panel gt Programs gt Uninstall a Program Starting the OneCommand NIC Teaming and VLAN Manager To start the OneCommand NIC Teaming
23. a vertical bar For example blue green red indicates that you may use blue green or red When selection from a list is mandatory the entire list is enclosed in angle brackets A list of optional items would be enclosed in curly brackets e Team id Where a team name is placed in a command e Adapter id Where an adapter alias is placed in a command e Adapter list Where a list of adapter aliases are placed in a command Aliases in a list are separated by one or more spaces e Network Manager Also known as the Network Connection Name e Hash Shows where a hashing algorithm is specified in a command For a list of supported hashing algorithms see Table 2 on page 38 e VLAN id This number represents the VLAN tag e VLAN alias The name that represents a VLAN that is automatically generated when a VLAN is created The name takes the form of VLan_n where nis the VLAN s VLAN id Error Codes Table 1 OneCommand NIC Teaming Driver and Command Line Utility Error Codes 3 Signed Unsigned Decimal oa Hexadecimal Error Code Decimal Value Value Description 0x00000000 0 No errors 0x8F000001 1895825407 2399141889 The OneCommand NIC Teaming and VLAN Manager is running The OneCommand NIC Teaming and VLAN Manager and the OCTeamCmd utility cannot run at the same time 0x8F000002 1895825406 2399141890 The OneCommand NIC Teaming and VLAN Manager Uninstaller is running The OneCommand NIC Teaming and VL
24. an delete team lt team id gt removes a team from the system ULAN Management Commands add vlan lt tean id adapter id gt lt vlan id gt lt nunber gt adds one or more ULANs to a team or an adapter delete vlan lt team id adapter id gt lt lt vlan id lt number gt gt i lt vlan alias gt gt removes one or more ULANs fron a team or an adapter c Program Files Enulex NIC Teaming Example of help with an optional command Program Files Emulex NIC Teaming gt OCTeamCmd exe help backup sage octeamcmd backup lt filename gt Creates a backup of the current NIC Teaming configuration in the specified file The specified file cannot already exist The file specification can include a directory path in addition to the filename If no directory path is specified the backup file will be placed in the current working directory Any specified directory path must exist and must be absolute or relative to the current working directory If either the directory path name or the filename contains spaces then the entire file specification must be enclosed in double quotes OneCommand NIC Teaming and VLAN Manager User Manual Page 31 gt S EMULEX Backing Up the NIC Teaming Configuration Syntax OCTeamCmd exe backup lt filename gt Description This command stores a backup of the current NIC teaming configuration in the specified file If the specified file exists the command returns an error You can include a d
25. and VLAN Manager click the OC NIC Teaming Manager from your desktop start menu OneCommand NIC Teaming and VLAN Manager User Manual Page 6 gt S EMULEX Using the OneCommand NIC Teaming and VLAN Manager Note For Windows Server 2008 x64 R2 and Windows Server 2008 x64 R2 with Hyper V TCP IP offload engine TOE technology is enabled Creating Configuring and Removing Teams A team of adapters functions as a single virtual network interface and appears the same as non teamed adapters to other network devices A protocol address such as an IP address is usually assigned to the physical adapter However when the OneCommand NIC Teaming and VLAN Manager is installed the protocol address is assigned to the team adapter and not to the physical adapters that make up the team Note Do not configure VLANs on adapters used with NIC teaming Note The NIC Teaming and VLAN Manager supports multi vendor teams Each team in a multi vendor environment must include at least one Emulex adapter e Emulex has tested the NIC Teaming and VLAN Manager with Intel x520 and Broadcom Netextreme II adapters Note NICs shown as members of the same port by OneCommand Manager should not be included on the same team Note SLB LACP and 802 3ad teams will not function properly using adapters with TCP offload enabled Disable these setting before creating teams Creating and Configuring a Team Caution Creating a team may ta
26. and alias Example C Program Files Emulex NIC Teaming gt 0OCTeamCmd exe show vlanadapters Alias nicS Device Manager Name Emulex OneConnect 0Ce1iG iG2 I NIC TOE Network Conn Device Name Local Area Connection 7 Connection Status connected Adapter type VLAN Bound MAC Address 60 68 C9 9D A4 6A Link Speed 18 8 Gbps Packet Sent 4578 Packets Received 295851 ULANs ULAN_3 169 254 28 197 Showing Free Adapters Syntax OCTeamCmd exe show freeadapters Description This command shows a listing of adapters that are not assigned to a team and do not have any assigned VLANs Adapters are identified using their name network manager network connection name and alias Parameters None OneCommand NIC Teaming and VLAN Manager User Manual Page 35 gt EMULEX Example C Program Files Emulex NIC Teaming gt octeamemd show freeadapters Alias nic8 Device Manager Name HP NC382i DP Multifunction Gigabit Server Adapter Network Conn Device Name Local Area Connection Connection Status connected Alias nic Device Manager Name HP NC382i DP Multifunction Gigabit Server Adapter 2 Network Conn Device Name Local Area Connection 2 Connection Status not connected Alias nic5S Device Manager Name HP NC382i DP Multifunction Gigabit Server Adapter 4 Network Conn Device Name Local Area Connection 4 Connection Status not connected Showing Team or Adapter Details Syntax show lt team id adapter id netwo
27. attempt to do so The Team Member Adapters area lists adapters that are members of the team 8 Click OK to return to OneCommand NIC Teaming and VLAN Manager dialog box Removing a Team To remove a team 1 From the Start menu click All Programs gt Emulex gt OneCommand Teaming and VLAN Manager to start the application The OneCommand NIC Teaming and VLAN Manager dialog box is displayed 2 Highlight the team that you want to remove Note In the Create Team dialog box expand the team that you are removing and note the names of the adapters This information is helpful in subsequent procedures such as Deleting Hyper V Teams OneCommand NIC Teaming and VLAN Manager User Manual Page 10 gt S EMULEX 2 OneCommand NIC Teaming and LAN Manager Utility File Help OneCommand NIC Teaming and VLAN Manager Teams and Available Adapters E Broadcom BCM57095 Netxtreme II GigE NDIS VBD Client 2 Local Area Connection 3 E O FailoverTeam_One Local Area Connection 8 ON Primary FailoyerTeam_One Emulex OneConnect OCm11102 N X NIC TOE Local Area Connection Secondary FailoverTeam_One Emulex OneConnect OCm11102 N X NIC TOE 2 Local Area Conne IBM USB Remote NDIS Network Device Local Area Connection Create Team Remove Team VLAN Show Config Exit Figure 3 OneCommand NIC Teaming and VLAN Manager Utility dialog box 3 Click Remove Team and follow the prompts Primary and Secondary Adapt
28. bteam nylbteam ULAN 5 added to mylbteam added to mylbteam C Program Files Emulex NIC Teaming gt OCTeamCmd exe add vlan nic6 166 2 ULAN 166 added to nich LAN i i added to nic6 C Program Files Emulex NIC Teaming gt OneCommand NIC Teaming and VLAN Manager User Manual Page 39 gt S EMULEX Deleting a VLAN Note Do not remove a team or VLAN while they are carrying traffic Doing so may produce unpredictable results Syntax delete vlan lt team id adapter id gt lt lt vlan id gt number gt Description This command deletes one or more VLANs from a team or an adapter You must specify the VLAN with its VLAN ID Additionally if the VLAN to be deleted belongs to a team you must specify the team and if the VLAN is assigned to an adapter you must specify the adapter id Optionally you can delete multiple VLANs by following the VLAN ID with the number of VLANs to be deleted If you are deleting multiple VLANs the specified VLAN ID is used as the VLAN ID of the first VLAN to delete The VLAN IDs of the other VLANs to be deleted must sequentially follow the VLAN ID of the first VLAN If any of these VLANs do not exist then no VLANs specified in the command are deleted Single VLANs may also be deleted by specifying their VLAN ID without the optional number of VLANs to delete Parameters Team id Team to which a VLAN to be deleted belongs Adapter id Adapter alias of the VLAN to be deleted from an adapter
29. d VLAN Manager Add Remove VLAN dialog box Figure 4 on page 12 select the adapter to remove from VLANs Configured area Note Do not remove a team or VLAN while they are carrying traffic unpredictable results may occur 2 Click Remove The adapter is removed 3 Click OK OneCommand NIC Teaming and VLAN Manager Configuration Display To view an adapter s current configuration 1 On the NIC Teaming and VLAN Manager dialog box Figure 1 on page 8 select an adapter and click Show Config The OneCommand NIC Teaming and VLAN Manager Configuration window is displayed This window is read only Figure 6 shows a failover team with the primary adapter active OneCommand NIC Teaming and VLAN Manager User Manual Page 13 gt OneCommand NIC Teaming and LAN Manager Configuration MAC Address 00 00 C9 56 06 86 Link Speed l 10 0 Gbps Connection Status Connected Primary active VLAN Enabled TCP Offload LO TOE m Team Properties Team Type FailOver Team Name Emulex TeamAdapter FO Team Manual Send Packets Receive Packets Figure 6 Teaming and VLAN Manager Configuration window Team Member States Each team member is in one of the following states as shown in the Connection Status field Connected The virtual adapter receives a connected status for the physical adapter Active The failover team member is being used as the active connection Disconnected When the virtual adapter receive
30. e file specification in quotes or double quotes Note When using the Restore command on Hyper V systems you must first delete any existing Hyper V virtual adapters that represent teams or VLANs See Deleting Hyper V Teams on page 20 for more information Once the restore process is complete you can re create the virtual adapters Once the restore operation is complete a restore report is generated Example fon Administrator Command Prompt c Program Files Enulex NIC Teaming gt octeanmcmd exe restore backup conf The NIC Teaming and ULAN configuration has been restored from file backup conf c vreated 1 26 2612 1 49 36 PM Please check c Program Files Emulex NIC Teanming Re storeRe port _26126126 135623 txt for more details c Program Files Enmulex NIC Teaming gt Showing NIC Teaming and VLAN Configurations Syntax OCTeamCmd exe show Description This command shows a summary of the overall NIC teaming and VLAN configurations Parameters None Example C Program Files Emulex NIC Teaming gt OCTeamCmd exe show Number of teams 2 LAN Bound Adapters 2 Available Adapters 2 C Program Files Emulex NIC Teaming gt OneCommand NIC Teaming and VLAN Manager User Manual Page 33 gt lt EMULEX Showing Aliases Syntax OCTeamCmd exe show aliases Description This command shows each adapters alias device manager name and network connection device name The aliases that are returned are
31. eaming and VLAN Manager 6 Uninstalling the OneCommand NIC Teaming Driver and the NIC Teaming and VLAN Manager 6 Starting the OneCommand NIC Teaming and VLAN Manager 6 Using the OneCommand NIC Teaming and VLAN Manager seses 7 Creating Configuring and Removing Teams 7 Creating and Configuring a Team 7 RemOVING a LOAM ec ccc cee et deeg een 10 Primary and Secondary Adapters ccccccccceeeeeeeeeeeeeeeeeeetcneeeeeeeseenaaaes 11 Removing an Adapter during Team Creation 11 Configuring a VLAN for an Adapter ceceecceeeeeeeee eee eeeccneeeeeeeeeeeeenaaeeeeenees 12 Removing a VLAN during VLAN Configuration eccceeeeeeeeeeeeeeeeeeees 13 OneCommand NIC Teaming and VLAN Manager Configuration Display 13 Using Teamed Adapters in Hvper NL 14 Exporting a Team Without a VLAN to a Virtual Machine ee 14 Deleting Hyper V Teams 20 Removing an Adapter from the Virtual Machine sec 20 Deleting the Adapter from the Virtual Network Manager sssssisssssessennenn 22 Removing the Team Using the OneConnect NIC Teaming Managev 23 Disabling the Microsoft Virtual Network Switch Protocol for an Adapter 23 OneCommand NIC Teaming Driver Command Line Interface 25 rodu UON ece a e EEEE ECEE EE EE 25 SYM RUNG Saa A aR 25 Error CGodes A 26 The Command Reference cccceeceeeeeecceeeeeeeeeeeeeeecceeeeeeeeeeeenccaeeeeeeeeenteed 31 FUP EE 31 Backing Up the NIC Teaming Configuration
32. eaming and VLAN Manager User Manual Page 21 d M p EMULEX m Deleting the Adapter from the Virtual Network Manager 1 Open Hyper V Manager and select the virtualization server in the console tree 2 Right click and select Virtual Network Manager from the context menu A Dupi he wtadi naea manage user tert rn Figure 17 Hyper V Manager menu OneCommand NIC Teaming and VLAN Manager User Manual Page 22 gt S EMULEX 3 The Virtual Network Manager opens Z3 Virtual Network Manager Bile ea amp _ Virtual Networks ro Neve virtual network ate Local Area Broadcom A Virtual Network Properties Connection 2 Virtual N Name mutex Failoverteam_One etxtreme Il Microsoft Virtual Switch aloverTeam_One FailoverTeam_One Notes amp Global Network Settings zl MAC Address Range x Connection type 00 1S SH 3F 93 00 te 00 15 SD 3 EE E Een What do you want to connect this network to External Faiovertest_One v Allow management operating system to share this network adapter Internal only Private virtual machine network Enable virtual LAN identification for management operating system MYLAN ID ifier specifies the virtual LAN that the management e all network communications through this netwo fect virtual machine networking La Cancel Sech Figure 18 Virtual Network Manager dialog box Virtual Network
33. eaming driver e NIC Teaming and VLAN Manager e NIC Teaming and VLAN Manager utilities 2 Navigate to the system directory to which you downloaded the file and double click the elxdrvr nic teaming lt version gt exe file Unattended Installation An unattended driver installation a quiet or silent installation requires no user input This is useful for performing an installation remotely from a command script or when you want to make sure a custom configuration is not changed by a user during installation Prerequisites Microsoft NET Framework 3 5 must be installed before you can install the OneCommand NIC Teaming driver and NIC Teaming and VLAN Manager If a Microsoft NET Framework version higher than 3 5 is already installed Microsoft NET Framework 3 5 must be installed as well Procedure To perform an unattended installation 1 From the Emulex website download the elxdrvr nic teaming lt version gt exe file to your system The kit is activated with the optional switch q or q2 The q switch displays progress reports The q2 switch does not display progress report OneCommand NIC Teaming and VLAN Manager User Manual Page 5 gt S EMULEX 2 Run the driver kit installer with the optional switch For example use the following command lxdrvr nic teaming lt version gt exe q2 Updating the OneCommand NIC Teaming Driver and the NIC Teaming and VLAN Manager WARNING Use the Emulex provided kit to update the NI
34. ers Note Every team must include at least one Emulex adapter as a primary adapter e To change the primary adapter of an existing team delete the team and recreate the team e To change the primary adapter while creating a team remove all adapters and add the first adapter that you would want to be the primary adapter Removing an Adapter during Team Creation To remove an adapter during team creation 1 On the OneCommand NIC Teaming and VLAN Manager Create Team dialog box Figure 2 on page 9 select the adapter to remove from Team Member Adapters area 2 Click Remove The adapter is removed from the Team Member Adapters area 3 Click OK to accept the changes and return to the OneCommand NIC Teaming and VLAN Manager dialog box 4 Click Exit to close the OneCommand NIC Teaming and VLAN Manager dialog box OneCommand NIC Teaming and VLAN Manager User Manual Page 11 gt G EMULEX Configuring a VLAN for an Adapter Note Configuring the VLAN at both the physical and team level may cause double tagging Note VLANs over multi vendor teams are not supported VLANs are only supported over teams consisting entirely of Emulex adapters Note If you use static IP addresses non DHCP you must assign IP addresses to any teams and VLANs that you create To configure a VLAN for a physical or team adapter 1 On the NIC Teaming and VLAN Manager dialog box Figure 1 on page 8 select the physical PNIC v
35. exe show nich Device Manager Name Emulex OneConnect 0Ce1 162 I NIC TOE Network Conn Device Name Local Area Connection 7 Connection Status connected Adapter type VLAN Bound MAC Address 06 60 C9 9D A4 6A Link Speed 186 86 Gbps Packet Sent 4566 Packets Received 294992 169 254 28 19 OneCommand NIC Teaming and VLAN Manager User Manual Page 36 gt G EMULEX Showing VLAN IDs Syntax show vlans lt team id adapter id gt Description This command shows a listing of VLAN IDs that are currently in use and those that are available for use Parameters Adapter id Adapter alias assigned by OCTeamCMD Team id The name assigned to a team when it is created Example C Program Files Emulex NIC Teaming gt OCTeamCmd exe show vlans nic5S Used ULAN IDs 3 Available ULAN IDs i 4 4094 C Program Files Emulex NIC Teaming gt OCTeamCmd exe show vlans mylbteam Used ULAN IDs r e r Available ULAN ID 1 2 7 4094 Creating a Team Caution Creating an adapter may take several minutes Prematurely cancelling this operation may result in partial removal of a team or VLAN which may lead to future teaming issues including system instability Note If you are creating a failover team when one already exists you must reboot the system before the newly created failover team is capable of failing over You can continue to create additional teams before rebooting however Syntax create team lt failover l
36. gns each adapter and team a Network Connection Name In most versions of Windows the name defaults to the form of Local Area Connection N To view the Network Connection Name from the desktop Select All Programs gt My Network Places 2 Right click on the adapter and click Properties The Network Connection Name is labeled by the operating system in a format similar to Local Area Connection N 3 You can rename these network connections with the tools provided by the operating system You can also use the Network Connection Name as an alias when identifying adapters or teams in OCTeamCmd commande If the name contains spaces enclose the entire name in double quotes Note Network Connection Names are not stored by the OCTeamCmd They are maintained by Windows Syntax Rules s Key words Key words determine which command to execute but do not specify any command parameters Keywords are shown in plain text e Mandatory items Angle brackets represent mandatory but variable items For example lt filename gt is a place in a command where you must supply a filename e Optional items Curly brackets represent optional items For example octeamcmd help command name shows that the help command can accept a command name as an optional parameter OneCommand NIC Teaming and VLAN Manager User Manual Page 25 gt S EMULEX e List of choices If a command parameter may be one of several items those items are separated by
37. has no VLANs assigned to it 0x8F000043 1895825341 2399141955 No VLAN bound adapters are defined 0x8F000044 1895825340 2399141956 VLANs cannot be added to team members 0x8F000045 1895825339 2399141957 An error occurred during application initialization 0x8F000046 1895825338 2399141958 An error occurred while cleaning the registry 0x8F000047 1895825337 2399141959 The adapter ID specified is invalid or already bound 0x8F000048 1895825336 2399141960 There are no teams or VLANs defined therefore a backup of the configuration cannot be made 0x8F000049 1895825335 2399141961 An application has locked Windows OneCommand NIC Teaming and VLAN Manager User Manual networking therefore teaming configuration changes cannot be made Page 29 gt S EMULEX Table 1 OneCommand NIC Teaming Driver and Command Line Utility Error Codes Continued Hexadecimal Error Code 0x8F00004A 0x8F00004B Signed Decimal Value 1895825334 1895825333 Unsigned Decimal Value 2399141962 2399141963 Description Exceeds the number of VLANs allowed Failed to find the alias for the required adapter 0x8F00004C 1895825332 2399141964 The same adapter was specified multiple times on the command line 0x8F00004D 1895825331 2399141965 Reboot the system after creating a failover team unless it is the first one on the system 0x8F00004E 0x8F00004F 1895825330 1895825329 239914
38. he local subnet have highly variant destination MAC addresses in Ethernet frames sent from the server system NIC team to those systems When Not to Use If the client laptop or desktop systems are located on different IP subnets and IP routing is required to reach them from the server this method is typically not a good fit When the Ethernet frames sent from the server system s NIC team to the IP router often a single gateway all have the same constant destination MAC address that of the IP router this method does not distribute traffic well When all of OneCommand NIC Teaming and VLAN Manager User Manual Page 41 gt G EMULEX the packets in all of the TCP IP have the same destination MAC address of the IP router they all hash to the same member individual link of the NIC team and all of the traffic has to travel on one link instead of being distributed to across many links Destination IP This method is team member channel selection hashing based on the destination IP address When to Use Use this method in these two situations e When a server communicates with many client systems or peer servers that are on the local IP subnet they have the same subnet as the server In this case the Destination IP address varies for each client and a good distribution of load based on varying IP addresses results between the server and the network switch e When the local server communicates with many client systems or peer
39. icast destination address The link aggregation control function determines which links may be aggregated It then binds the ports to an aggregator function in the system and monitors conditions to determine if a change in the aggregation group is required Link aggregation combines the individual capacity of multiple links to form a high performance virtual link The failure or replacement of a link in an LACP trunk does not cause loss of connectivity The traffic fails over to the remaining links in the trunk OneCommand NIC Teaming and VLAN Manager User Manual Page 4 gt S EMULEX Installing and Uninstalling the OneCommand NIC Teaming Driver and the NIC Teaming and VLAN Manager There are two ways to install the OneCommand NIC Teaming driver and the NIC Teaming and VLAN Manager e Attended installation using the GUI e Unattended installation using the command line Attended Installation Prerequisites The Microsoft NET Framework 3 5 must be installed before you can install the OneCommand NIC Teaming driver and the NIC Teaming and VLAN Manager If a Microsoft NET Framework version higher than 3 5 is already installed Microsoft NET Framework 3 5 must be installed as well Procedure To perform an attended installation 1 From the Emulex website download the elxdrvr nic teaming lt version gt exe to your system The installer is an executable file that self extracts and copies the following software onto your system e NIC T
40. ions Transmitted traffic through a router is load balanced and is based on the source and destination IP address and TCP UDP port number Since routers do not alter the source and destination IP address the load balancing algorithm works as intended Switch Controlled Teaming Link Aggregation Control Protocol LACP IEEE 802 3ad LACP is similar to link aggregation static mode except that it uses the LACP to negotiate the ports that make up the team The LACP must be enabled at both the server and the switch for the team to operate If LACP is not available at both ends of the link 802 3ad provides a manual aggregation that only requires both ends of the link to be in a link up state Because manual aggregation provides for the activation of a member link without performing the LACP message exchanges it is not as reliable and robust as an LACP negotiated link LACP automatically determines which member links can be aggregated and then aggregates them It provides for the controlled addition and removal of physical links for the link aggregation so that no frames are lost or duplicated The removal of aggregate link members is provided by the marker protocol that can be optionally enabled for LACP enabled aggregate links The link aggregation group advertises a single MAC address for all the ports in the team The MAC address of the team aggregator can be the MAC addresses of one of the NICs in the group The LACP and marker protocols use a mult
41. irectory path in addition to the filename If no directory path is specified the backup file is placed in the current working directory Any directory path that you specify must exist and must be absolute or relative to the current working directory If the directory path name or the file name contains spaces then you must enclose the entire file specification in quotes or double quotes In addition to the configuration information the server name of the machine that created the backup and the list of NIC adapters present are included in the backup data Backup files are saved as simple text files Note Backup files should not be edited or altered Use the backup option after a teaming configuration is complete or has changed Use the restore option when you want to e Replicate a server e Rebuild a server e Replace a failed adapter e Change a current configuration to a previous one Parameters filename The name of the backup file that is created Example Program Files Emulex NIC Teaming gt OCTeamCmd exe backup backup conf onfiguration backed up to file backup conf Proqram Files Emulex NIC Teamina gt _ Restoring the NIC Teaming Configuration Syntax OCTeamCmd exe restore lt filename gt Parameters filename The NIC Teaming and VLAN configuration is restored from this file that was created using the backup option Description This command replaces current NIC teaming configuration with the c
42. irtual VNIC or a team adapter in Available Adapters to which you want to add a VLAN 2 Click VLAN The Add Remove VLAN dialog appears gt OneCommand NIC Teaming and LAN Manager Add Remove YLAN x Adapter Emulex TeamAdapter FO Team Manual Configure VLAN VLAN ID VLAN Name Add LANs Configured VLAN Name IPyv4 v6 Address Remove OK Figure 4 Add Remove VLAN dialog box 3 Enter a VLAN ID Valid tag values are from 1 to 4094 The VLAN Name shows the VLAN Name in the format VLan_ lt VLAN ID gt Click Add to add the VLAN to the adapter You can create up to four VLANs for an adapter The VLANs Configured area shows the list of VLANs configured for the adapter 5 Click OK The VLAN is added to the list of configured VLANs Note Once a VLAN is added to a team the team adapter s connection is disabled The team adapter is marked with a down arrow in Windows Server 2008 OneCommand NIC Teaming and VLAN Manager User Manual Page 12 gt G EMULEX gt OneCommand NIC Teaming and LAN Manager Add Remove LAN Adapter Emulex TeamAdapter FO Team Manual r Configure LAN VLAN ID VLAN Name Add LANs Configured VLAN Name IPv4 v6 Address Van D FeB0 3cd1 8c3c cae4 8622 OK Figure 5 Configured VLANs Removing a VLAN during VLAN Configuration To remove a VLAN during VLAN configuration 1 On the OneCommand NIC Teaming an
43. ke several minutes Prematurely cancelling this operation may result in the partial creation or deletion of a team or VLAN Such an act may also lead to future teaming issues or even system instability Note If you use static IP addresses non DHCP you must assign IP addresses to any teams and VLANs that you create To create and configure a team 1 From the Start menu click All Programs gt Emulex gt OneCommand Teaming and VLAN Manager to start the application The OneCommand NIC Teaming and VLAN Manager dialog box is displayed OneCommand NIC Teaming and VLAN Manager User Manual Page 7 gt S EMULEX 2 OneCommand NIC Teaming and LAN Manager Utility File Help OneCommand NIC Teaming and VLAN Manager Teams and Available Adapters K Broadcom BCMS7095 Netxtreme II GigE NDIS VBD Client 2 Local Area Connection 3 FailoverTeam_One Local Area Connection 8 Primary FailoverTeam_One Emulex OneConnect OCm11102 N X NIC TOE Local Area Connection EK Secondary FailoverTeam_One Emulex OneConnect OCm11102 N X NIC TOE 2 Local Area Conne KS IBM USB Remote NDIS Network Device Local Area Connection Create Team Remove Team VLAN Show Config Exit Figure 1 OneCommand NIC Teaming and VLAN Manager dialog box 2 Click Create Team The OneCommand NIC Teaming and VLAN Manager Create Team dialog box is displayed OneCommand NIC Teaming and VLAN Manager User Manual Page 8 gt S
44. lient load balancing would be eliminated and could cause out of order frame delivery This receive load balancing scheme works as long as all clients and the teamed server are on the same subnet or broadcast domain OneCommand NIC Teaming and VLAN Manager User Manual Page 3 gt G EMULEX When the clients and the server are on different subnets and incoming traffic has to traverse a router the received traffic destined for the server is not load balanced The physical adapter that the intermediate driver has selected to carry the IP flow carries all of the traffic When the router needs to send a frame to the team IP address it broadcasts an ARP request if not in the ARP cache The server software stack generates an ARP reply with the team MAC address but the intermediate driver modifies the ARP reply and sends it over a particular physical adapter establishing the flow for that session over the particular physical adapter The reason is that ARP is not a routable protocol It does not have an IP header and therefore is not sent to the router or default gateway ARP is only a local subnet protocol In addition since the gratuitous ARP is not a broadcast packet the router does not process it and does not refresh its own ARP cache The only way that the router would process an ARP intended for another network device is if the router has proxy ARP enabled and the host has no default gateway This is very rare and not recommended for most applicat
45. mary team member Load Balancing Smart Load Balancing SLB Team Load Balancing Team load balancing provide both load balancing and fault tolerance Team load balancing works with any Ethernet switch and does not require any switch configuration The team advertises multiple MAC addresses and one or more IP addresses The virtual team adapter selects the team MAC address from the list of load balancing members When the server receives an address resolution protocol ARP request the software networking stack always sends an ARP reply with the team MAC address To begin the load balancing process the OneCommand NIC Teaming and VLAN Manager modifies this ARP reply by changing the source MAC address to match one of the physical adapters Load balancing enables both transmit and receive load balancing based on load balancing function to maintain in order delivery of frames Transmit load balancing is achieved by creating a hashing table using the hashing algorithm based on load distribution type When the virtual teaming adapter selects a physical adapter or port to carry all the frames to the destination the unique MAC address of the physical adapter is included in the frame and not the team MAC address This is required to comply with the IEEE 802 3 standard If two adapters transmit using the same MAC address a duplicate MAC address situation would occur that the switch could not handle Receive load balancing is achieved through an inte
46. ne or more VLANs over a team or over a NIC VNIC A VLAN is a network of computers that behave as if they are connected to the same wire even though they may actually be physically located on different segments of a Local Area Network LAN VLANs are configured through software rather than hardware which make them extremely flexible One advantage of a VLAN is that when a computer is physically moved to another location it can stay on the same VLAN without any hardware reconfiguration To increase throughput and bandwidth and to increase link availability you can configure multiple network interfaces on one or more ethernet ports to appear to the network as a single interface This is referred to as Network Interface Card NIC teaming or multi link trunking The Windows NIC Teaming and VLAN Manager supports e vNIC teaming e Switch controlled teaming Link Aggregation Control Protocol LACP e Switch independent teaming types e Failover FO e Smart load balancing SLB e TX RX load balancing e TCP IP load balancing e Non TCP IP TX load balancing e Media Access Control MAC address load balancing e Dynamic link aggregation e Auto Failback e Hashing e Perceived Port Load e Destination IP hashing e Destination MAC hashing DAMAC e Backup Restore of teaming configurations Note There are restrictions with using VLANs and universal multichannel UMC together and with using LACP and UMC together See the Windows driver manual for
47. ocedure for the remaining adapters that were members of the deleted team OneCommand NIC Teaming and VLAN Manager User Manual Page 24 gt S EMULEX OneCommand NIC Teaming Driver Command Line Interface Introduction The OneCommand NIC Teaming Driver 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 Note Do not configure VLANs on adapters used with NIC teaming 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 executed Network Connection Names Windows assi
48. onfiguration found in the specified backup file By replacing the current NIC teaming configuration with a backed up version you can Note The Restore command does not restore assigned IP addresses e Undo changes to the NIC configuration that you no longer want e Facilitate disaster recovery by restoring a NIC teaming configuration after reloading an operating system e Duplicate NIC teaming configurations on identical servers OneCommand NIC Teaming and VLAN Manager User Manual Page 32 gt S EMULEX To restore the NIC teaming configuration on the same or a duplicated server the server s current physical NIC configuration must be identical to the NIC configuration in the backup file If this condition is violated the restoration is terminated Note When restoring a NIC teaming configuration you must restore the configuration to the same adapter model in the same PCI slot number as the backed up system Note A system reboot is not required unless multiple failover teams were restored The CLI prompts you if this is the case The file specification can optionally include a directory path in addition to the filename If you do not specify a directory path the backup file is assumed to be located in the current working directory Any directory path that you specify must be absolute or relative to the current working directory If the directory path name or the file name contains spaces then you must enclose the entir
49. or Command Prompt c Program Files Enulex NIC Teaming gt octeancmd exe help OCTeamCnd version 7 2 6 118 Usage octeamcnd lt command gt lt parameters gt Help commands 7h displays this text 4 displays this text displays this text help displays this text help lt command displays help for the requested command Backup Restore Commands backup lt filename gt creates a file containing the current configuration restore lt filename gt replaces the current configuration with the one in the file Show Commands show displays the number of teams ULAN bound adapters and free adapters show lt team id adapter id i network connection nanme gt lt vlan_id gt displays detailed information about an adapter tean or ULAN show aliases displays each adapter s alias Network Connection Manager s device name and Device Manager s name show freeadapters displays a listing of the adapters that are not assigned to any teams and do not have ULANs assigned show teams displays a listing of the current teans and their details show versions Displays the versions of the various components show vlanadapters displays a listing of the ULAN bound adapters and the ULANs assigned to then show vlans lt team id adapter id gt displays the assigned and available ULAN ids for a team or an adapter Team Management Commands create team lt team type gt lt team name gt lt adapter list gt creates a te
50. product described in this manual at any time and without any notice Emulex assumes no responsibility for its use nor for any infringements of patents or other rights of third parties that may result Periodic changes are made to information contained herein although these changes will be incorporated into new editions of this manual Emulex disclaims any undertaking to give notice of such changes US patent notice is given for one or more of the following 6226680 6247060 6334153 6389479 6393487 6427171 6427173 6434620 6591302 6658480 6697868 6751665 6757746 6941386 6965941 6687758 7042898 7133940 7124205 7089326 6938092 6996070 Emulex 3333 Susan Street Costa Mesa CA 92626 OneCommand NIC Teaming and VLAN Manager User Manual Page ii Aa D Table of Contents gt lt EMULEX EE ENEE 1 Supported Operating Systems cccccceeeeeeeeeeeeeeccneeeeeeeeeeeeccaeeeeeeetesenceeeeeenees 2 WV ye Lull 2 ISHMINGIOOY cities ence cee eee 2 Se Ve EE 3 LOA Balancmg 3 Smart Load Balancing SLB Team Load Balancing eeeeeeeeeeees 3 Switch Controlled Teaming Link Aggregation Control Protocol LACP 4 Installing and Uninstalling the OneCommand NIC Teaming Driver and the NIC Teaming and VLAN Manager 5 Attended Installation EE 5 Ne IEN 5 Procedu O secs ch cet ecco 5 Wnattended Ms tallation E 5 Prore oU SIOS ninn e Een 5 Nee EE 5 Updating the OneCommand NIC Teaming Driver and the NIC T
51. rk connection name gt vlan id Description This command shows details about a team or an adapter Optionally to show information about a VLAN you must first specify an adapter or team and then specify the VLAN ID You may use a numeric value or a string to identify the VLAN Parameters Team id Team name Adapter id Adapter alias assigned by OCTeamCMD Network connection name network manager This name is not stored by OCTeamCMD This name is maintained by Windows Vlan id The number used as the VLAN tag Example z Progran Files Emulex n eaming 0OCleanCmd exe Device Manager Name Emulex OneConnect OCei i 2 F NIC TOE Network Conn Device Name Local Area Connection 5 Connection Status connected Tean mylhtean Team type Load Balancing Hash type destip Adapter Role Secondary Adapter Status Passive MAC Address BA 0A C9 9D A4 9A Link Speed 10 0 Gbps Packet Sent 146 Packets Received 1098 C Program Files Emulex NIC Teaming gt OCTeanCmd exe show mytean3 Device Manager Name nyteam3 Network Conn Device Name Local Area Connection 17 Connection Status connected Team type Failover Automatic Failback enabled MAC Address AA AA C9 9D A4 9C Link Speed 16 8 Gbps Packet Sent 155 Packets Received 788 Menhbers Emulex OneConnect O0CeiGiG 2 I NIC TOE 2 Local Area Connection H Emulex OneConnect O0Ce1G1G2 F NIC TOE 2 Local frea Connection 6 C Program Files Emulex NIC Teaming gt OCTeanCmd
52. rk page is displayed E S Virtual Network Manager BEE 5 Virtual Networks ZA New virtual network sty Local Area Connection 2 Virtual N A Emulex_FailoverTeam_One Fa overTeam_One eS f Connection type WT SE NEESS What do you want to connect this network to C Extena Fatoverteara_One D 7 Allow mansgemert operating system to share this network adapter Irkernal only Private virtual machine network IT Enable virtual LAN identification for management operating system VLAN ID The VLAN identifier specifies the vitus LAN that the management operating Remove Figure 9 New Virtual Network page without a VLAN 5 Enter the name of the new network Figure 9 shows Emulex_Failover_Team_One 6 Select the External radio button and select an Emulex adapter Select the Allow management operating system to share the network adapter check box Clear the Enable virtual LAN identification for management operating systems check box Click Apply Ensure that the virtual machine is turned off wo N a0 p On the Virtual Machines page select Settings OneCommand NIC Teaming and VLAN Manager User Manual Page 16 Ca A EMULEX a Fie Action View Window Hep e lzlelpler 23 Hyper V Manager a WIN U6sH78R 28783 Figure 10 Hyper V Manager Virtual Machines page The Settings for the virtual machine page are displayed HB Settings for VirtOne AS E Vote Wer x Q 7 Add Hardware
53. rmediate driver by sending gratuitous ARPs on a client by client basis using the unicast address of each client as the destination address of the ARP request also known as a directed ARP This is client load balancing and not traffic load balancing When the intermediate driver detects a significant load imbalance between the physical adapters in an LB team it generates gratuitous ARPs in an effort to redistribute incoming frames The intermediate driver does not answer ARP Requests only the software protocol stack provides the required ARP reply It is important to understand that receive load balancing is a function of the number of clients that are connecting to the server via the team interface Receive load balancing attempts to load balance incoming traffic for client machines across physical ports in the team It uses a modified gratuitous ARP to advertise a different MAC address for the team IP address in the sender physical and protocol address The gratuitous ARP is unicast with the MAC and IP address of a client machine in the target physical and protocol address respectively This causes the target client to refresh its ARP cache with a new MAC address map to the team IP address This has the potential to direct the received traffic to a different adapter than learned from the transmission Gratuitous ARPs are not broadcast because this would cause all clients to send their traffic to the same port As a result the benefits achieved through c
54. s the link down status indication through LACP or because you disable or remove the link it is disconnected Using Teamed Adapters in Hyper V Note TCP Offload does not occur in virtual machines Exporting a Team Without a VLAN to a Virtual Machine Hyper V must be installed to use Emulex teamed adapters in Hyper V To export a team without a VLAN to a virtual machine Create and install a VM In this example Windows Network Manager is used 1 2 Create a team using OneCommand NIC Teaming and VLAN Manager or OCTeamCmd 3 Open Hyper V Manager and select Virtual Network Manager Page 14 OneCommand NIC Teaming and VLAN Manager User Manual gt S EMULEX Figure 7 Hyper V Manager menu 4 The Create virtual network page is displayed Select External and click Add g Z Virtual Network Manager R Virtual Networks DA Create virtual network A Local Area Connection 2 Virtual N What type of vitusl network do you want to creste Brosdcom BCMS7O9S Netxtreme II S Global Network Setti G MAC Address Range 00 15 SD 4D C6 0 itema Private 00 to 00 15 50 4 _ Crestes a virtual network that binds to the physical network adspter so that virtual machines can access a physical network More abont creating virtual networks Figure 8 Hyper V Manager Create virtual network options OneCommand NIC Teaming and VLAN Manager User Manual Page 15 d gt G EMULEX The New Virtual Netwo
55. servers that are located on different IP subnets Non local different subnet or local IP addresses give a good distribution with this method when the IP addresses have good variation across the group IP address assignments are often not in the control of the administrator setting up a NIC team therefore the best way to guarantee a good distribution is when the group of client systems is large and there is good random variation in their IP address assignments When Not to Use This method is a poor fit when you have communication between only a few clients or peer servers and the server as there is insufficient variation in the set of destination IP addresses because there are few partners for IP traffic OneCommand NIC Teaming and VLAN Manager User Manual Page 42
56. ses EC Ve Controller 1 DvD Drive I Enable spoofing of MAC addresses EO SCSI Controler T Enable vitua LAN identification F Network Adapter CNS ID Local Ares Connection 2 Vrtu The VLAN identifier specifies the virtual LAN that this virtual machine wil use for all Ss Network Adapt network comenunications through this network adapter Emulex_FailoverTeam_One TZ Le 7 COM l p To remove the network adapter from this virtual machine dick Remove come Remove KH Distette Drive GP Use a legacy network adapter instead of this network adapter to perform a network based installation of the guest operating system or when integration amp Mana services are not installed in the quest operating system Name 7 Unkegration Services GR Snapshot File Location ColProgramDatalMicr ID Automatic Start Action Restart f pee nly runring xl Coox J c JI a Figure 12 Network Adapter page 14 Select the virtual network that you created and click Apply 15 Turn on and connect to the virtual machine 16 Verify the new network adapter From the desktop start menu click Control Panel gt Administrative Tools gt Computer Managerment gt Device Manager Select Network adapters in the right pane OneCommand NIC Teaming and VLAN Manager User Manual Page 18 gt S EMULEX Al Ele Action yew Window Hep 18 x e 0m2 uma S Computer Management Local gt E J System Tools 2 d Computer 3 il Event Viewer ze Di
57. sk drives E Shared Folders H E Display adapters Local Users and Groups 3 DVO CO ROM drives EN Performance Logs and Alert Ey Floppy disk controllers BA Device Manager e H Floppy disk drives a Storage o Gag Huan Interface Devices si SN Removable Storage Sy IDE ATAJATAPI controllers Disk Defragmenter o gt Keyboards Disk Management T Mice and other pointing devices si Ea Services and Applications BW Network adapters B Microsoft Vrtual Machine Bus Network Adapter E9 Microsoft Yrtual Machine Bus Network Adapter 3 wi Ports COM amp LPT oi SB Processors E d SCSI and RAID controllers e EI Sound video and game controlers ei d System devices Figure 13 Device Manager in the Computer Management window 17 Check the network connections From the command prompt enter lt ipconfig gt A new network connection adapter appears in the virtual machine Microsoft Windows Version 5 2 3790 CC Copyright 1985 2003 Microsoft Corp C Documents and Settings fdninistrator gt ipconfig Windows IP Configuration Ethernet adapter Local Area Connection Connection specific DNS Suffix lab enmulex com UP Hd e ee wee a e 10 192 76 61 Subnet Mask e e e 255 255 240 0 Default Gateway s s gt gt s 10 192 64 254 Ethernet adapter Local Area Connection 3 Connection specific DNS Suffix IP Addeass sis e een wal ee Subnet Mask Default Gateway s 23 1 100 64 255 0 0 0 C
58. t auto failback setting gt loadbalance lt hash gt 802 3ad lt hash gt LACP lt hash gt gt team name adapter list Description This command creates a team The team name is the name for the team that is to be created The name cannot exceed 80 characters and must be unique The adapters listed as part of the team may not be part of another team and may not have VLANs assigned to them The first adapter listed becomes the primary adapter this must be an Emulex adapter The number of allowable team members varies with team type Failover teams must have 2 members Load balancing teams must have from 2 to 8 members LACP and 802 3ad teams must have from 2 to 4 members The auto failback setting is only used for failover teams This setting specifies whether the team should automatically resume using the primary adapter once it becomes available again after the team has failed over to the secondary adapter A maximum of 4 teams can be created Use the abbreviated names from Table 2 when specifying the team type on Load Balancing LACP and 802 3ad teams from the command line OneCommand NIC Teaming and VLAN Manager User Manual Page 37 Table 2 Hash Algorithms Hash Algorithm Abbreviation Perceived adapter load percload Destination MAC destmac Destination IP destip Parameters Auto failback setting foenable or fodisabled Hash Hash algorithm Example C Program Files Emulex NIC Teaming gt OCTeamCmd exe
59. team members does not exist or does not have link 0x8F00002B 1895825365 2399141931 The primary adapter is not an Emulex adapter 0x8F00002C 1895825364 2399141932 The adapter s link is not enabled by the calling function 0x8F00002D 1895825363 2399141933 One of the team members is already bound and is not available for use by another team Ox8F00002E 1895825362 2399141934 The primary adapter is not set to active by the calling function Ox8F00002F 1895825361 2399141935 The secondary adapter in failover mode is not set to passive by the calling function 0x8F000030 1895825360 2399141936 The wrong number of members is set by the calling function 0x8F000031 1895825359 2399141937 The failover type provided to the create command is unknown 0x8F000032 1895825358 2399141938 Unable to determine whether an adapter is enabled or disabled 0x8F000033 1895825357 2399141939 An adapter is disabled 0x8F000034 1895825356 2399141940 An internal error is detected Check the debug log 0x8F000035 1895825355 2399141941 A timeout occurred while waiting for Windows to delete a team The deletion may have completed but it did not complete within five minutes 0x8F000036 1895825354 2399141942 A timeout occurred while waiting for Windows to delete a VLAN The deletion may have completed but it did not complete within five minutes Page 28 gt S EMULEX Table 1 OneCommand NIC Teaming Driver and Command Line Utility Error Codes

OneCommand NIC Teaming and VLAN Manager

Contents

Download Pdf Manuals

Related Search

Related Contents