Note<\/b> Today I am concluding my series about working with network adapters. One of the cool things about the Windows platform is all the ways that are possible to obtain networking statistical information. There are NetStat, Netsh, performance counters, and the Get-NetworkStatistics<\/b> function from the NetAdapter<\/b> Windows PowerShell module. All of these methods can be used inside the Windows PowerShell console or from within the Windows PowerShell ISE.<\/p>\n Using Netsh to obtain network statistics is easy and powerful. For example, to show IP statistics, I use the following command:<\/p>\n netsh interface ipv4 show ipstats<\/p>\n A sample output from this command is shown in the image that follows:<\/p>\n To use Netsh to show TCP statistics, I use the command shown here:<\/p>\n netsh interface ipv4 show tcpstats<\/p>\n The command and the output from the command are shown here:<\/p>\n One of the cool things about using Netsh from within Windows PowerShell is that I have the power of Windows PowerShell at my fingertips. Rather than going back and forth to find stuff, I can pipe the results from a command to the Select-String<\/b> cmdlet.<\/p>\n For example, if I am interested in how many commands are available to show statistics, I use the following command because I noticed that each of the commands contains the letters stats<\/b>:<\/p>\n netsh interface ipv4 show | Select-String "stats"<\/p>\n The output from the command is shown here:<\/p>\n PS C:\\> netsh interface ipv4 show | Select-String "stats"<\/p>\n show icmpstats – Displays ICMP statistics.<\/p>\n show ipstats – Displays IP statistics.<\/p>\n show tcpstats – Displays TCP statistics.<\/p>\n show udpstats – Displays UDP statistics.<\/p>\n In addition to the IPV4 interface, I can also work with the IPV6 interface and obtain similar statistics. Here is the command that I used to obtain that information:<\/p>\n PS C:\\> netsh interface ipv6 show | Select-String "stats"<\/p>\n show ipstats – Displays IP statistics.<\/p>\n show tcpstats – Displays TCP statistics.<\/p>\n show udpstats – Displays UDP statistics.<\/p>\n In addition to using the Select-String<\/b> cmdlet to parse the output from the Netsh Help, I can use it to hone in on specific information from the statistics. For example, the following command retrieves IPv6 interface IP stats:<\/p>\n netsh interface ipv6 show ipstats<\/p>\n I can hone in on the output and look for errors by piping the results to the Select-String<\/b> cmdlet and choosing errors<\/b>. This command is shown here.<\/p>\n netsh interface ipv6 show ipstats | Select-String errors<\/p>\n In the image that follows, I first show the command to retrieve the IPV6 IP statistics. Next I show the output from the command. Then I filter the output to only errors by using the Select-String<\/b> cmdlet. Lastly, I show the output from the filtered string.<\/p>\n The NetStat command has been in the Windows world for a long time. It provides a quick snapshot of connections from local ports to remote ports in addition to the protocol and the state of those connections.<\/p>\n It takes a couple of minutes to run, and as a result, it makes sense to store the results of NetStat into a variable. I can then examine the information several times if I want to without having to wait to gather the information additional times. Here is an example of running the NetStat<\/b> command and storing the results in a variable:<\/p>\n $net = NetStat<\/p>\n To display the information in an unfiltered fashion, I simply type $net<\/b> at the Windows PowerShell prompt, and it displays all of the information that it gathered:<\/p>\n $net<\/p>\n The command to run NetStat<\/b>, store the results in a variable, and examine the contents of the $net<\/b> variable are shown in the following image:<\/p>\n The real power, however, comes in using Windows PowerShell to parse the text output to find specific information. For example, the previous output shows multiple connections in various connected states. I can easily parse the output and find only the connections that are Established<\/b>. The command I use is:<\/p>\n $net | select-string "Established"<\/p>\n The command and the output from the command are shown in the following image:<\/p>\n Interestingly enough, I can also use Netsh to report on TCP connections. The command is shown here:<\/p>\n netsh interface ipv4 show tcpconnections<\/p>\n The output from the command, as shown in the image that follows, is a bit different than that received from NetStat<\/b>:<\/p>\n To easily collect performance counter information, I need to know the performance counter set names. To do this, I use the Get-Counter<\/b> cmdlet, and I choose all of the ListSets<\/b>. I then like to sort on the CounterSetName<\/b> property, and then select only that property. The following command retrieves the available list sets:<\/p>\n Get-Counter -ListSet * |<\/p>\n Sort-Object CounterSetName |<\/p>\n Select-Object CounterSetName<\/p>\n If I pipe the output to the Out-GridView<\/b> cmdlet, I can easily filter the list to find the list sets I want to use. This command is shown here:<\/p>\n Get-Counter -ListSet * |<\/p>\n Sort-Object CounterSetName |<\/p>\n Select-Object CounterSetName |<\/p>\n Out-GridView<\/p>\n The resulting Out-GridView<\/b> pane makes it easy to filter for different values. For example, the image that follows filters for IP:<\/p>\n When I have the CounterSetName<\/b> value that want to query, it is a simple matter of plugging it into Get-Counter<\/b> to first obtain the paths, as shown here:<\/p>\n $paths = (Get-Counter -ListSet ipv4).paths<\/p>\n Next, I use the paths with the Get-Counter<\/b> cmdlet to retrieve a single instance of the IPv4 performance information:<\/p>\n Get-Counter -Counter $paths<\/p>\n The commands and the output from the commands are shown in the following image:<\/p>\n If I want to monitor a counter set for a period of time, I use the –SampleInterval<\/b> property and the –MaxSamples <\/b>parameter. In this way, I can specify how long I want the counter collection to run. An example of this technique is shown here:<\/p>\n Get-Counter -Counter $paths -SampleInterval 60 -MaxSamples 60<\/p>\n If I want to monitor continuously, until I type Ctrl+C<\/b> to break the command, I use the –Continuous<\/b> parameter and the –SampleInterval<\/b> parameter. An example of this command is shown here:<\/p>\n Get-Counter -Counter $paths -SampleInterval 30 -Continuous<\/p>\n The easiest way to gather network adapter statistics is to use the Get-NetAdapterStatistics<\/b> function from the NetAdapter<\/b> module. It provides a quick overview of the sent and received packets. An example of the command is shown here:<\/p>\n Get-NetAdapterStatistics<\/p>\n The command and a sample output are shown in the image that follows:<\/p>\n If I want to work with a specific network adapter, I can use the name of the adapter; or for more flexibility, I can pipe the results from the Get-NetAdapter<\/b> function. This technique is shown here:<\/p>\n Get-NetAdapter -ifIndex 12 | Get-NetAdapterStatistics<\/p>\n The Get-NetAdapterStatistics<\/b> function returns more than only the bytes sent and received. To find the additional information, I like to pipe the results to the Format-List<\/b> cmdlet. An example of this technique is shown here:<\/p>\n Get-NetAdapter -ifIndex 12 | Get-NetAdapterStatistics | format-list *<\/p>\n The command,and the output associated with the command are shown in the following image:<\/p>\n This concludes Network Adapter Week. Join me tomorrow when I will talk about mobile devices, Active Sync, and Exchange. It is cool stuff that you do not want to miss.<\/p>\n I invite you to follow me on Twitter<\/a> and Facebook<\/a>. If you have any questions, send email to me at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n Ed Wilson, Microsoft Scripting Guy<\/b> <\/p>\n","protected":false},"excerpt":{"rendered":" Summary: Microsoft Scripting Guy, Ed Wilson, talks about various ways to gather network statistics by using Windows PowerShell. Microsoft Scripting Guy, Ed Wilson, is here. Hey, it is nearly the weekend! This means we are one week closer to Windows PowerShell Saturday #007… PowerShell Saturday #007 will be held in Charlotte, North Carolina on February […]<\/p>\n","protected":false},"author":596,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[37,60,3,298,45],"class_list":["post-2198","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-networking","tag-performance","tag-scripting-guy","tag-tcpip","tag-windows-powershell"],"acf":[],"blog_post_summary":" Summary: Microsoft Scripting Guy, Ed Wilson, talks about various ways to gather network statistics by using Windows PowerShell. Microsoft Scripting Guy, Ed Wilson, is here. Hey, it is nearly the weekend! This means we are one week closer to Windows PowerShell Saturday #007… PowerShell Saturday #007 will be held in Charlotte, North Carolina on February […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/2198","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/596"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=2198"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/2198\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=2198"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=2198"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=2198"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
You may want to refer to the earlier posts to catch up on the series:<\/p>\n\n
Netsh<\/h2>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/HSG-1-17-14-01.png\" "\\"Image")
<\/a><\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/HSG-1-17-14-02.png\" "\\"Image")
<\/a><\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/HSG-1-17-14-03.png\" "\\"Image")
<\/a><\/p>\nNetStat<\/h2>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/HSG-1-17-14-04.png\" "\\"Image")
<\/a><\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/HSG-1-17-14-05.png\" "\\"Image")
<\/a><\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/HSG-1-17-14-06.png\" "\\"Image")
<\/a><\/p>\nPerformance counters<\/h2>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/HSG-1-17-14-07.png\" "\\"Image")
<\/a><\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/HSG-1-17-14-08.png\" "\\"Image")
<\/a><\/p>\nUsing Get-NetAdapterStatistics<\/h2>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/HSG-1-17-14-09.png\" "\\"Image")
<\/a><\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/HSG-1-17-14-10.png\" "\\"Image")
<\/a><\/p>\n