نحوه پیکربندی NIC Teaming در سرور HP Proliant با استفاده از HP NCU
HP Proliant Network Adapter Teaming (NIC Teaming) allows Server administrator to configure Network Adapter, Port, Network cable and switch level redundancy and fault tolerance. Server NIC Teaming will also allows Receive Load balancing and Transmit Load balancing. Once you configure NIC teaming on a server, the server connectivity will not be affected when one of the Network adapter fails, Network Cable disconnects or Switch failure happens.
To create NIC Teaming in Windows 2008/2003 Operating System, we need to use the HP Network Configuration Utility. HP Network Configuration Utility (HP NCU) is a very easy-to-use tool available for Windows Operating System. This utility is available for download at Driver & Download page of your HP Server (HP.com).
To configure NIC teaming on your Windows based HP Proliant Server, you need to download HP Network Configuration Utility (HP NCU). If you are using Windows 2012 Server Operating System on your HP Server, then you could not use HP Network Configuration Utility. We need to use the inbuilt network team software of Windows. Please install the latest version of Network card drivers before you install the HP Network Configuration Utility. In Linux, Teaming (NIC Bonding) function is already available and there is no HP tools which you need to use to configure it.
Different ways to open HP Network Configuration Utility:
HP NCU is used for Network Teaming and it has a easy to use graphical interface. Using NCU, you can create and dissolve NIC/Network teaming. If you have not installed NCU on your server, you need to download and install it from your HP Server driver download page. NCU is also included in HP Service Pack bundle. Once you download and install NCU, you need to launch the NCU to create a network team. So let let us see how to open Network Configuration Utility on your HP Server. You can open NCU in different ways.
1. Open HP NCU from System Tray:
Please check whether NCU is listed in System Tray, refer below said screen to understand better.
2. Open HP NCU from Run window:
Try searching/running the command cpqteam.exe at Start->Search or Windows Run menu as shown below. cpqteam is the name of the HP NCU executable program.
3. Open HP NCU from Network Properties:
Open Local Area Connection Properties on your Server, it will show HP Network Configuration Utility listed. Then select HP Network Configuration Utility and click on Properties. This should open NCU on your Server.
4. Open HP NCU from Program Files folder:
You could find the NCU program, I mean cpqteam.exe file in C:\Program Files\HP\NCU folder. If none of the above methods work for you, then you can try this step.
NOTE: If you are using Windows 2008 Core Editon, then you may have to open Command Prompt and CD to C:\Program Files\HP\NCU. Then run the command hpteam.cpl
By performing any of the above said methods, you can open HP NCU on your Server. As you can see from below provided screenshot, your Network Adapters will be listed in HP NCU. You can select multiple Network Adapters and click the Team button to form a network a teaming on your server.
HP NCU allows you to configure different types of Network Team, here are the few types of network team which can be configured using NCU.
- Network Fault Tolerance Only (NFT)
- Network Fault Tolerance Only with Preference Order
- Transmit Load Balancing with Fault Tolerance (TLB)
- Transmit Load Balancing with Fault Tolerance and Preference Order
- Switch-assisted Load Balancing with Fault Tolerance (SLB)
- 802.3ad Dynamic with Fault Tolerance
Network Fault Tolerance Only (NFT):
In NFT team, you can group two to eight NIC ports and it will act as one virtual network adapter. In NFT, only one NIC port will transmit and receive data and its called as primary NIC. Remaining adapters are non-primary and will not participate in receive and transmit of data. So
If you group 8 NICs and create a NFT Team, then only 1 NIC will transmit and receive data, remaining 7 NICs will be in standby mode. If the primary NIC fails, then next available NIC will be treated as Primary, and will continue the transmit and receive of data. NFT supports switch level redundancy by allowing the teamed ports to be connected to more than one switch in the same LAN
Network Fault Tolerance Only with Preference Order:
This mode is identical to NFT, however here you can select which NIC is Primary NIC. You can configure NIC Priority in HP Network Configuration Utility. This team type allows System Administrator to prioritize the order in which teamed ports should failover if any Network failure happens. This team supports switch level redundancy.
Transmit Load Balancing with Fault Tolerance (TLB):
TLB supports load balancing (transmit only). The primary NIC is responsible for receiving all traffic destined for the server, however remaining adapters will participate in transmission of data. Please note that Primary NIC will do both transmit and receive while rest of the NIC will perform only transmission of data. In simpler words, when TLB is configured, all NICs will transmit the data but only the primary NIC will do both transmit and receive operation.
If you group 8 NICs and create a TLB Team, then only 1 NIC will transmit and receive data, remaining 7 NICs will perform transmission of data. TLB supports switch level redundancy.
Transmit Load Balancing with Fault Tolerance and Preference Order:
This model is identical to TLB, however you can select which one is the Primary NIC. This option will help System Administrator to design network in such a way that one of the teamed NIC port is more preferred than other NIC port in the same team. This model also supports switch level redundancy.
Switch-assisted Load Balancing with Fault Tolerance (SLB):
SLB allows full transmit and receive load balancing. In this team, all the NICs will transmit and receive data hence you have both transmit and receive load balancing. So if you group 8 NICs and create a SLB Team, all the 8 NICs will transmit and receive data. However, SLB does not support Switch level redundancy as we have to connect all the teamed NIC ports to the same switch. Please note that SLB is not supported on all switches as it requires Ether Channel, MultiLink Trunking etc.
802.3ad Dynamic with Fault Tolerance
This team is identical to SLB except that the switch must support IEEE 802.3ad Link Aggregation Protocol (LACP). The main advantage of 802.3ad is that you do not have to manually configure your switch. 802.3ad does not support Switch level redundancy but allows full transmit and receive load balancing.
How to create Network Team using HP NCU:
Once you open NCU, you will find all the installed network cards are listed in it. As you can find from below provided screenshot, we have 4 NICs installed. Here, we will go ahead and team two Network cards in NFT mode. Later we will discuss how to assign IP address to the teamed NICs.
NOTE: HP NCU can be used as a Virtual switch or vSwitch. You can use the VLAN button on the NCU window and create multiple virtual Network Card interface in the Operating System.
1. The HP Network Configuration Utility Properties window will look like the one provided below.
2. Select 2 NICs by clicking on it and then click Team button.
3. HP Network Team #1 will be created as shown below.
4. Select HP Network Team #1 and click on Properties button to change team properties.
5. The Team Properties Window will open now.
6. Here you can select the type of NIC team you want to implement (See below screenshot).
7. Here, I will select NFT from the Team Type Selection drop down list.
8. Click OK once you selected the desired Team type.
9. Now you will be at below provided screen now. Click OK to close HP NCU.
10. You will receive confirmation window prompting you to save changes, Click Yes.
11. HP NCU will configure NIC teaming now, the screen may look like the one provided below.
12. This may take some time, once Teaming is done, below provided window will be shown.
13. Open HP NCU, you could find that HP Network Team is in Green color.
NOTE: Whenever you update NIC drivers on your HP Servers, ensure that you dissolve the existing NIC teaming before you do it. You will find Dissolve button in HP NCU window.
How to set Static IP address for Teamed Network Adapters:
As you have created NIC Teaming on your server, you may go ahead and assign a static IP to it Or you can leave the settings in default and your DHCP server will assign an IP automatically. You need to perform below provided steps only if you are setting any static IP for your NIC team. If you want to use DHCP, then you do not need to perform below said steps because your DHCP Server will automatically assigns new IP address to the Virtual NIC created by the teaming software.
To assign an IP, you need to open control panel window and open Network connection window. You will find a new network card with name “HP Network Team #1”. When we create a Network Team, this Virtual NIC will be created. To assign an IP for the Teamed NICs, we have to assign IP address for this Virtual NIC “HP Network Team #1”.
1. To set an IP address for HP Network Team #1, please open Network Connection window from Control Panel.
2. Right-click on Local Area Connection 5 and click on Properties.
3. Select Internet Protocol Version 4 (TCP/IP), and then click on Properties.
4. Select the option “Use the following IP address” and set a Static IP for the Teamed NICs now.
HP NCU can be used for fine tuning your Network Team. You could control various settings of the NICs using this wonderful utility. By the way, what do you think about my article? Were you able to team the NICs? Let us know.
- پیکربندی NIC Teaming در سرورهای HP Proliant
- نحوه اضافه و حذف VMnic uplink در VMware DvSwitch
- آشنایی با vSphere Distributed Switch
- کانفیگ کردن VMware vSPhere 5.5 Distributed Switch
- تخصیص یک LUN در دستگاه EMC Symmetrix VMAX
- آموزش VLAN سوییچ
- نحوه ایجاد vSphere Distributed Switch و Port Group
- ایجاد VMkernel Port برای iSCSI ، vMotion ، NFS و FT
- پیکربندی RAID در محیط Array Configuration Utility سرورهای HP
- بزرگترین چالش های مدیران در خصوص دیتاسنترها
- معایب مجازی سازی
- معماری HP 3PAR StoreServ