El contenido no se encuentra disponible en el idioma seleccionado. Estamos trabajando continuamente para agregar más idiomas. Gracias por su apoyo.

Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
On this page
Help Center/ Bare Metal Server/ User Guide/ Network/ Enhanced High-Speed Network/ Configuring an Enhanced High-Speed NIC (Windows Server)

Configuring an Enhanced High-Speed NIC (Windows Server)

Updated on 2022-09-16 GMT+08:00

This section uses Windows Server 2012 R2 Standard as an example to describe how to configure an enhanced high-speed network bond of a BMS.

NOTE:

The configuration methods of other Windows Server OSs are similar to that of Windows Server 2012 R2 Standard.

Add a NIC

  1. Log in to a Windows BMS.
  2. On the Windows PowerShell CLI of the BMS, run the following command to check the NIC information:

    Get-NetAdapter

    Information similar to the following is displayed.

    NOTE:

    eth0 and eth1 bear the VPC, and eth3 and eth4 bear the enhanced high-speed network bond. The following steps use eth2 and eth3 to configure the enhanced high-speed network.

  3. To improve the outbound traffic on the OS, perform the operations in Method 1. If there is no special requirement on traffic, perform the operations in Method 2.

    • Method 1: Use the switch standalone mode for the bond in the OS. The outbound traffic is distributed across all active NICs, and the inbound traffic is received through one of the NICs in the team.
    1. Run the following command to create a bond port group for the enhanced high-speed network:

      New-NetLbfoTeam -Name qinq -TeamMembers "eth2","eth3" -TeamingMode SwitchIndependent -LoadBalancingAlgorithm Dynamic -Confirm:$false

      NOTE:

      In the command, qinq is the name of the port group planned for the enhanced high-speed network, and eth2 and eth3 are the network devices that bear the enhanced high-speed network obtained in 2.

    2. Run the following command to query the network adapters:

      get-NetLbfoTeamMember

      Get-NetAdapter

    • Method 2: Use the active/standby mode for the bond in the OS.
    1. Run the following command to create a bond port group for the enhanced high-speed network:

      New-NetLbfoTeam -Name Team2 -TeamMembers "eth2","eth3" -TeamingMode SwitchIndependent -LoadBalancingAlgorithm IPAddresses -Confirm:$false

      NOTE:

      In the command, Team2 is the name of the port group planned for the enhanced high-speed network, and eth2 and eth3 are the network devices that bear the enhanced high-speed network obtained in 2.

    2. Run the following command to set a network port of port group Team2 created in 3.a to the standby port:

      Set-NetLbfoTeamMember -Name "eth3" -AdministrativeMode Standby -Confirm:$false

      NOTE:

      The port group configured for the enhanced high-speed network supports only the active/standby mode. eth3 is one of the ports of the port group. You can determine which port is configured as the standby port based on your planning.

      get-NetLbfoTeamMember

      Get-NetAdapter

  4. Run the following command to enter the Network Connections page:

    ncpa.cpl

    Then enter the following page.

  5. Configure the enhanced high-speed network.

    1. On the Network Connections page, double-click port group Team2 created in 3 to switch to the Team2 Status page.
    2. Click Next to switch to the Team2 Properties page.
    3. On the Networking tab page, double-click Internet Protocol Version 4 (TCP/IPv4) to switch to the Internet Protocol Version 4 (TCP/IPv4) Properties page.
    4. Select Use the following IP address, configure the IP address and subnet mask, and click OK.

      NOTE:

      If the IP address planned for the enhanced high-speed network does not conflict with the VPC network segment, you can plan the IP address as needed, only to ensure that BMSs communicating through the enhanced high-speed network are in the same network segment as the enhanced high-speed network.

  6. Perform the preceding operations to configure other BMSs.
  7. After all BMSs are configured, ping the IP address in the same network segment as the enhanced high-speed network of other BMSs from each BMS.

Delete a NIC

  1. Log in to a Windows BMS.
  2. On the Windows PowerShell CLI of the BMS, run the following command to query information about the bonded enhanced high-speed NICs to be deleted:

    Get-NetLbfoTeamNIC -Team Team2

  3. Run the following command to delete the bonded NICs:

    Remove-NetLbfoTeam -Name "Team2"

  4. Run the following commands to query the NIC information and verify that the NIC is deleted:

    Get-NetAdapter

Utilizamos cookies para mejorar nuestro sitio y tu experiencia. Al continuar navegando en nuestro sitio, tú aceptas nuestra política de cookies. Descubre más

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback