You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Added extra options to do the steps in PowerShell
Added a section to specify the VLAN config in case the monitored traffic comes from different VLAN(s) then the Hyper-V host sits in.
Removed line "In the Hardware list, under the Network Adapter drop-down list, select Hardware Acceleration and clear the Virtual Machine Queue option for the monitoring network interface." as it was not reflected in the PowerShell version and I don't believe it is needed.
|**vSwitch_Span**|Newly added SPAN virtual switch name |
45
+
|**Ethernet**|Physical adapter name |
46
+
47
+
Reference: [Create and configure a virtual switch with Hyper-V](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/get-started/create-a-virtual-switch-for-hyper-v-virtual-machines?tabs=powershell#create-a-virtual-switch)
48
+
49
+
### Create a new virtual switch with Hyper-V Manager
34
50
35
51
1. Open the Virtual Switch Manager.
36
52
@@ -84,15 +100,23 @@ If you use PowerShell, define the name of the newly added adapter hardware as `M
84
100
85
101
:::image type="content" source="../media/tutorial-install-components/vswitch-span.png" alt-text="Screenshot of selecting the following options on the virtual switch screen.":::
86
102
87
-
1. In the **Hardware** list, under the **Network Adapter** drop-down list, select **Hardware Acceleration** and clear the **Virtual Machine Queue** option for the monitoring network interface.
88
-
89
103
1. In the **Hardware** list, under the **Network Adapter** drop-down list, select **Advanced Features**. Under the **Port Mirroring** section, select **Destination** as the mirroring mode for the new virtual interface.
90
104
91
105
:::image type="content" source="../media/tutorial-install-components/destination.png" alt-text="Screenshot of the selections needed to configure mirroring mode.":::
92
106
93
107
1. Select **OK**.
94
108
95
-
## Turn on Microsoft NDIS capture extensions
109
+
## Turn on Microsoft NDIS capture extensions with PowerShell
110
+
111
+
Turn on support for [Microsoft NDIS Capture Extensions](/windows-hardware/drivers/network/capturing-extensions) for the virtual switch you'd [created earlier](#configure-a-traffic-mirroring-port-with-hyper-v).
112
+
113
+
**To enable Microsoft NDIS capture extensions for your new virtual switch**:
## Turn on Microsoft NDIS capture extensions with Hyper-V Manager
96
120
97
121
Turn on support for [Microsoft NDIS Capture Extensions](/windows-hardware/drivers/network/capturing-extensions) for the virtual switch you'd [created earlier](#configure-a-traffic-mirroring-port-with-hyper-v).
98
122
@@ -139,6 +163,24 @@ Get-VMSwitchExtensionPortFeature -FeatureName "Ethernet Switch Port Security Set
139
163
|--|--|
140
164
|**vSwitch_Span**| Newly added SPAN virtual switch name |
141
165
166
+
## Configure VLAN settings for the Monitor adapter (if needed)
167
+
168
+
In case the HYper-V server would sit in a diffeernt VLAN than the VLAN from which the mirrored traffic comes, the Monitor adapter must be set to accpet traffic from the mirrored VLANs
169
+
170
+
Use below PowerShell command to enable the Monitor adapter to accept traffic from the monitored traffic from different VLANs:
0 commit comments