Export (0) Print
Expand All

Get-NetEventVmSwitch

Windows Server 2012 R2 and Windows 8.1

Updated: October 17, 2013

Applies To: Windows 8.1, Windows PowerShell 4.0, Windows Server 2012 R2

Get-NetEventVmSwitch

Gets Hyper-V virtual switches from a provider.

Syntax

Parameter Set: ByName
Get-NetEventVmSwitch [[-Name] <String[]> ] [-AsJob] [-CimSession <CimSession[]> ] [-ShowInstalled] [-ThrottleLimit <Int32> ] [ <CommonParameters>]

Parameter Set: ByProviderOfTarget
Get-NetEventVmSwitch [-AsJob] [-AssociatedPacketCaptureProvider <CimInstance> ] [-CimSession <CimSession[]> ] [-ShowInstalled] [-ThrottleLimit <Int32> ] [ <CommonParameters>]




Detailed Description

The Get-NetEventVmSwitch cmdlet gets Hyper-V virtual switches from a Remote Packet Capture provider. This cmdlet returns a list of Hyper-V virtual switches that you configured as filters on a Remote Packet Capture provider.

The protocol stack uses multiple layers to transmit, receive, and process network traffic as packets. The provider logs network traffic as Event Tracing for Windows (ETW) events.

Parameters

-AsJob

Runs the cmdlet as a background job. Use this parameter to run commands that take a long time to complete. The cmdlet immediately returns an object that represents the job and then displays the command prompt. You can continue to work in the session while the job completes. To manage the job, use the *-Job cmdlets. To get the job results, use the Receive-Job cmdlet. For more information about Windows PowerShell® background jobs, see about_Jobs.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-AssociatedPacketCaptureProvider<CimInstance>

Specifies the associated packet capture provider as a CIM object. To obtain the packet capture provider, use the Get-NetEventPacketCaptureProvider cmdlet.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

True (ByValue)

Accept Wildcard Characters?

false

-CimSession<CimSession[]>

Runs the cmdlet in a remote session or on a remote computer. Enter a computer name or a session object, such as the output of a New-CimSession or Get-CimSession cmdlet. The default is the current session on the local computer.


Aliases

Session

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Name<String[]>

Specifies an array of Hyper-V virtual switches.


Aliases

none

Required?

false

Position?

1

Default Value

none

Accept Pipeline Input?

True (ByPropertyName)

Accept Wildcard Characters?

false

-ShowInstalled

Indicates that the cmdlet displays all network adapters that are installed on the computer.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-ThrottleLimit<Int32>

Specifies the maximum number of concurrent operations that can be established to run the cmdlet. If this parameter is omitted or a value of 0 is entered, then Windows PowerShell® calculates an optimum throttle limit for the cmdlet based on the number of CIM cmdlets that are running on the computer. The throttle limit applies only to the current cmdlet, not to the session or to the computer.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

<CommonParameters>

This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see    about_CommonParameters.

Inputs

The input type is the type of the objects that you can pipe to the cmdlet.

Outputs

The output type is the type of the objects that the cmdlet emits.

Examples

Example 1: Get a Hyper-V virtual switch from a provider

This example gets a Hyper-V virtual switch from the Remote Packet Capture provider for a network session. After you complete these commands to configure the network session, you can start and stop the event and packet capture for the network session by using the Start-NetEventSession and Stop-NetEventSession cmdlets.

The first command uses the New-NetEventSession cmdlet to create a network session named NESession01.

The second command uses the Add-NetEventPacketCaptureProvider cmdlet to add a Remote Packet Capture provider for the session named NESession01.

The third command uses the Add-NetEventVmSwitch cmdlet to add the Hyper-V virtual switch named Network Adapter 2 - Virtual Switch as a filter on the Remote Packet Capture provider.

The fourth command uses the Add-NetEventVmSwitch cmdlet to add the Hyper-V virtual switch named Network Adapter 4 - Virtual Switch as a filter on the Remote Packet Capture provider.

The fifth command gets the Hyper-V virtual switch named Network Adapter 2 - Virtual Switch from the provider.


PS C:\> New-NetEventSession -Name "NESession01"
PS C:\> Add-NetEventPacketCaptureProvider -SessionName "NESession01"
PS C:\> Add-NetEventVMSwitch -Name “Network Adapter 2 - Virtual Switch"
PS C:\> Add-NetEventVMSwitch -Name “Network Adapter 4 - Virtual Switch"
PS C:\> Get-NetEventVMSwitch -Name "Network Adapter 2 - Virtual Switch"

Related topics

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft