new partner?

partners[@]IT-PlayGround.net

created for you

read, share

E-mail us:

hello[@]IT-PlayGround.net

Why join the elite?


1. Great team members – friendly, open minded for new challenges.
2. Knowledge and experience sharing at an excellent level by all.
3. Social events organized with the great team members in Blagoevgrad and or Sofia.
4. Discount codes provided by the partners.
5. LinkedIn recommendations after some time
6. More to come. Stay tuned. ;)

contact us: hello[@]IT-PlayGround.Net
  • Home
  • Blog
  • Administrator
  • Powershell and cmd commands, how to stop specific networking technologies, that are incompatible with nic teaming

Blog

This is a blog about different types of software development and windows system administration tricks, tuts and other helpful stuff.

Powershell and cmd commands, how to stop specific networking technologies, that are incompatible with nic teaming

NOTE:

1) Further below you will see how we can deactivate all forms of TCP Offload, as well as Trimming (which is not even a network technology but is related to various types of Windows Cluster issues) Below you can find how to deactivate the VMQ and RSS as well.

2) Last but not least there is a way to check out the MTU size of the adapters --- This is a known problem when the MTU size is 1514 instead of 1500.

Additional NOTES: RSS and VMQ are compatible with NIC teaming, but they should be configured additionally to work fine with it. There exist some network card drivers and firmware that doesn't allow proper RSS and VMQ usage, therefore it is needed to deactivate them as well, just in case.

It is good to know that NO HARM at all is caused by it, practically (higher CPU usage could be the case, which wasn't ever observed).  Please also note that RSS and VMQ are useful only when used for 10 Gb or above NICs.

1) suspect network and storage technologies CMD: Chimney, Task Offload, RSS, as well as TRIM operations.

Please note to run them in a cmd.exe or PowerShell with administrator privileges

netsh int tcp set global chimney=disabled
netsh interface ipv4 set global taskoffload = disabled
netsh interface ipv6 set global taskoffload = disabled
netsh int tcp set global rss=disabled
fsutil behavior set disabledeletenotify 1

Please note that the first five are global network settings. The sixth one is a storage / file system that deactivates the TRIM and UNMAP operations. TRIM operations are not found only by the SSD plates but they are default standard active operations of each NTFS partitions and volumes by 2012 and 2012 R2.

PowerShell with an example where possible

Checksum Offload

Get-NetAdapterChecksumOffload

List all network adapters, where the Technology is active. Remember the names, with the commands below. P.S. You can view all adapters, including the obscured with the -IncludeHidden parameter, so

Get-NetAdapterChecksumOffload –IncludeHidden Disable-NetAdapterEncapsulatedPacketTaskOffload –Name 'Adapter1' (remove the name of the command Namen if that doesn't list any. Check the syntax, if there are still any so please go to the next step) P.S. The name of the adapter should be selected as 'Adapter1'.

Please do this for all active adapters Encapsulated Packet Task Offload

Get-NetAdapterEncapsulatedPacketTaskOffload

List all network adapters where the Technology is active. Remember the names with the below commands to manually deactivate them Disable-NetAdapterEncapsulatedPacketTaskOffload –Name 'Adapter1' (the name of the above command. If this doesn't have any values check the syntax, if it still doesn't then please go to the next step)

For active Adapters configure in that way VMQ, Virtual Queue Get-NetAdapterVmq

List all network adapters where the Technology is active. Remember the names with the below commands to manually deactivate them Disable-NetAdapterVmq –Name 'MgtNIC3_MGT' (the name of the above command. If this doesn't have any values check the syntax, if it still doesn't then please go to the next step)
For active Adapters configure in that way VMQ VLAN Filter Get-Netadapteradvancedproperty |where {$_.RegistryKeyword –eq "*VMQVlanFiltering"} List all network adapters where the Technology is active. Remember the names with the below commands to manually deactivate them Set-Netadapteradvancedproperty –Name 'MgtNIC6_CSV' –RegistryKeyword "*VMQVlanFiltering" –DisplayValue "Disabled" For active Adapters configure in that way TCP Large Send Offload. Get-NetAdapterLso Listet alle Netzwerkadapter, bei denen die o.g. Technologie aktiv ist. Die Namen merken, mit den unten stehenden Kommandos manuell deaktivieren. Disable-NetAdapterLso –Name 'MgtNIC3_MGT' (die Namen aus dem o.g. Kommando entnehmen, falls dieses keine Werte aufgewiesen hat, Syntax prüfen, falls immer noch -bitte weiter zum nächsten Schritt) For active Adapters configure in that way

2) suspect defect network drivers – incorrect MTU size Check whether the MTU size is displayed properly - there are known problems with Broadcom network adapters, but not only there. Influence: The incorrectly displayed MTU value results in sporadic network disturbances, especially at higher load, thus also possible with simultaneous backup of several VMs. However, this does not result in regular network interruptions, so the error is usually hidden To check this, you can use PowerShell

Get-NetAdapterAdvancedProperty |where {$_.displayname -eq "jumbo packet"}
Or Get-NetAdapterAdvancedProperty |where {$_.displayname -eq "jumbo mtu"}
Or Get-NetAdapterAdvancedProperty Or using the CMD for IPv4: netsh int ipv4 show int
And for IPv6: netsh int ipv6 show int

The MTU size should not have a value of 1514, but the default configured value should be 1500. If for example a value of 1514 (Or other slightly different values of 1500, which no administrator has set manually), then this can be corrected with network card driver updates or by doing so manually using the cmd.exe:

netsh interface ipv4 set subinterface 10 mtu=1500 store=persistent
netsh interface ipv4 set subinterface 12 mtu=1500 store=persistent
netsh interface ipv4 set subinterface 25 mtu=1500 store=persistent
netsh interface ipv4 set subinterface 40 mtu=1500 store=persistent etc.

P.S. The subinterface index (10, 12, 25, 40, etc.) Command netsh int ipv4 show int (the column "Idx", meaning the adapter number) and refers to the index of the adapter that has the MTU value of 1514.
How to upgrade and downgrade the integration servi...
The curious incident of missing system restore poi...

Related Posts

Sign up for our newsletter to get the latest news

About the project

IT-PlayGround.NET logo

a Personal IT PlayGround project developed over the years.

Powered by:  www.sslavkov.eu

Social media: