How to Utilize NIC Teaming for Hyper-V VMs with VLAN in Windows Server 2016Broadcom NIC Teaming with Hyper-V R2Are there problems teaming the public network adapters on a Windows Server 2008 R2 failover cluster?How to configure teaming, teamed VLANs, and hyper-v?Hyper-v 2012 R2 Nic Teaming with VLAN'sConnection problems with Microsoft NIC teamingServer 2012 R2 Hyper-V Teaming with 1 Virtual Switch vs 2 Virtual SwitchesWhat are the best practices for NIC teaming in Server 2012 R2? Broadcom or Windows software?Hyper-V 2016 Teaming: 1 Gbps instead of 2 with Dynamic LACP?Hyper-V 2016 Server and NIC TeamingNIC teaming on hyper-v host or within each VM?
Why do games have consumables?
Philosophical question on logistic regression: why isn't the optimal threshold value trained?
A Note on N!
What is the philosophical significance of speech acts/implicature?
How can Republicans who favour free markets, consistently express anger when they don't like the outcome of that choice?
How to stop co-workers from teasing me because I know Russian?
If a planet has 3 moons, is it possible to have triple Full/New Moons at once?
Is there really no use for MD5 anymore?
Does a large simulator bay have standard public address announcements?
Aligning equation numbers vertically
Apply MapThread to all but one variable
Should the Death Curse affect an undead PC in the Tomb of Annihilation adventure?
How do I check if a string is entirely made of the same substring?
How to fry ground beef so it is well-browned
Re-entry to Germany after vacation using blue card
Pre-plastic human skin alternative
On The Origin of Dissonant Chords
Two field separators (colon and space) in awk
Mistake in years of experience in resume?
How could Tony Stark make this in Endgame?
How to have a sharp product image?
How to display Aura JS Errors Lightning Out
"You've called the wrong number" or "You called the wrong number"
How to write a column outside the braces in a matrix?
How to Utilize NIC Teaming for Hyper-V VMs with VLAN in Windows Server 2016
Broadcom NIC Teaming with Hyper-V R2Are there problems teaming the public network adapters on a Windows Server 2008 R2 failover cluster?How to configure teaming, teamed VLANs, and hyper-v?Hyper-v 2012 R2 Nic Teaming with VLAN'sConnection problems with Microsoft NIC teamingServer 2012 R2 Hyper-V Teaming with 1 Virtual Switch vs 2 Virtual SwitchesWhat are the best practices for NIC teaming in Server 2012 R2? Broadcom or Windows software?Hyper-V 2016 Teaming: 1 Gbps instead of 2 with Dynamic LACP?Hyper-V 2016 Server and NIC TeamingNIC teaming on hyper-v host or within each VM?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I have two Windows Server 2016 with Hyper-V installed. Each server has two ethernet adapters. And each Hyper-V has several VMs. My goal is VMs can communicate with each other if they fall into the same VLAN.
In order to make the network connection redundancy, I created the network teaming on the physical machine. The teaming is using "Switch Independent" with "Address Hash" options. On the Virtual Switch Manager, I created an external adapter by selecting the teamed adapter (Microsoft Network Adapter Multiplexor Driver).
Under each VM, I create a virtual adapter with VLAN tagged.
However, the VMs in the same VLAN cannot communicate with each other.
On the switch side, I have already configured trunk mode for all the ports connected with the physical machines.
If I remove the teaming, the VMs can communicate with VLAN tags. How to address this issue?
windows hyper-v vlan network-teaming
asked Sep 9 '18 at 5:38
NeilWangNeilWang
398
add a comment |
I have two Windows Server 2016 with Hyper-V installed. Each server has two ethernet adapters. And each Hyper-V has several VMs. My goal is VMs can communicate with each other if they fall into the same VLAN.
In order to make the network connection redundancy, I created the network teaming on the physical machine. The teaming is using "Switch Independent" with "Address Hash" options. On the Virtual Switch Manager, I created an external adapter by selecting the teamed adapter (Microsoft Network Adapter Multiplexor Driver).
Under each VM, I create a virtual adapter with VLAN tagged.
However, the VMs in the same VLAN cannot communicate with each other.
On the switch side, I have already configured trunk mode for all the ports connected with the physical machines.
If I remove the teaming, the VMs can communicate with VLAN tags. How to address this issue?
windows hyper-v vlan network-teaming
asked Sep 9 '18 at 5:38
NeilWangNeilWang
398
add a comment |
I have two Windows Server 2016 with Hyper-V installed. Each server has two ethernet adapters. And each Hyper-V has several VMs. My goal is VMs can communicate with each other if they fall into the same VLAN.
In order to make the network connection redundancy, I created the network teaming on the physical machine. The teaming is using "Switch Independent" with "Address Hash" options. On the Virtual Switch Manager, I created an external adapter by selecting the teamed adapter (Microsoft Network Adapter Multiplexor Driver).
Under each VM, I create a virtual adapter with VLAN tagged.
However, the VMs in the same VLAN cannot communicate with each other.
On the switch side, I have already configured trunk mode for all the ports connected with the physical machines.
If I remove the teaming, the VMs can communicate with VLAN tags. How to address this issue?
windows hyper-v vlan network-teaming
asked Sep 9 '18 at 5:38
NeilWangNeilWang
398
I have two Windows Server 2016 with Hyper-V installed. Each server has two ethernet adapters. And each Hyper-V has several VMs. My goal is VMs can communicate with each other if they fall into the same VLAN.
In order to make the network connection redundancy, I created the network teaming on the physical machine. The teaming is using "Switch Independent" with "Address Hash" options. On the Virtual Switch Manager, I created an external adapter by selecting the teamed adapter (Microsoft Network Adapter Multiplexor Driver).
Under each VM, I create a virtual adapter with VLAN tagged.
However, the VMs in the same VLAN cannot communicate with each other.
On the switch side, I have already configured trunk mode for all the ports connected with the physical machines.
If I remove the teaming, the VMs can communicate with VLAN tags. How to address this issue?
windows hyper-v vlan network-teaming
windows hyper-v vlan network-teaming
asked Sep 9 '18 at 5:38
NeilWangNeilWang
398
asked Sep 9 '18 at 5:38
NeilWangNeilWang
398
asked Sep 9 '18 at 5:38
NeilWangNeilWang
398
asked Sep 9 '18 at 5:38
NeilWangNeilWang
398
asked Sep 9 '18 at 5:38
NeilWangNeilWang
398
398
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
It's not entirely clear where your problem lies from your description. I'm uncertain about the "removing team" bit especially. If the VMs can communicate with each other when your virtual switch is Internal or Private, then the problem is not with Hyper-V.
If they can communicate with each other when you attach the virtual switch to only one unteamed adapter, then test using the other adapter instead. If one works but not the other, then it is likely a physical adapter or switch problem. If either works, but not both in a team, then it is likely a physical switch problem.
Check these points, even if you've already checked them. Problems like this are typically sourced back to something extremely minor and easy to overlook:
Physical Switch
- Ports are in trunk mode
- Ports are not in a port channel or LAG
- The desired VLAN is specifically allowed and/or marked as "Tagged"
- The ports do not use a numbered default VLAN, PVID, or have any numbered VLAN set as "Untagged"
Physical NICs
- NICs do not have any VLAN settings applied, check both firmware and drivers
Physical NIC Team
- You are using exactly one team interface and it is not assigned a numbered VLAN
Virtual adapters (Hyper-V Side)
- Virtual adapters have been assigned to the correct VLAN
- Virtual adapters are connected to the correct virtual switch
Virtual adapters (inside guest)
- Adapter has appropriate TCP/IP settings
- Firewall is not blocking the expected traffic
Troubleshooting
If you've done all of the above and it still doesn't work, then you likely have a physical problem somewhere.
- Disconnect the wire from one physical adapter and test
- Reconnect the initial wire and wait for stable connectivity (viewable in LBFOAdmin.exe or
Get-NetLbfoTeamMember). - Disconnect the second wire and test
answered Sep 10 '18 at 14:14
Eric SironEric Siron
764
Hi Eric, I tried several times but no luck. The switch ports are trunk and no aggregation is configured. I configured VLAN under virtual adapter(hyper-v). How can I get logs from the Cisco and Windows regards to the network traffic?
– NeilWang
Sep 12 '18 at 22:25
You did specifically set the switches to use 802.1q tagging and added the VLAN(s) to the trunk VLAN allowed list? Windows doesn't really log network traffic like you're looking for; Wireshark is probably a better tool. But this really sounds like you have a switch configuration problem. You can look at Cisco logs with "show log" but I'm not going to be much help on that topic.
– Eric Siron
Sep 13 '18 at 16:48
Yeah, I allowed all the VLANs through the ports and enabled the trunk by simply using the "switchport mode trunk" command. It gonna really hard for troubleshooting since I can't get the log from Windows and I have no idea about the Wireshark. I will try to find something might useful on Cisco logs. Thanks anyway.
– NeilWang
Sep 14 '18 at 22:13
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f930090%2fhow-to-utilize-nic-teaming-for-hyper-v-vms-with-vlan-in-windows-server-2016%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It's not entirely clear where your problem lies from your description. I'm uncertain about the "removing team" bit especially. If the VMs can communicate with each other when your virtual switch is Internal or Private, then the problem is not with Hyper-V.
If they can communicate with each other when you attach the virtual switch to only one unteamed adapter, then test using the other adapter instead. If one works but not the other, then it is likely a physical adapter or switch problem. If either works, but not both in a team, then it is likely a physical switch problem.
Check these points, even if you've already checked them. Problems like this are typically sourced back to something extremely minor and easy to overlook:
Physical Switch
- Ports are in trunk mode
- Ports are not in a port channel or LAG
- The desired VLAN is specifically allowed and/or marked as "Tagged"
- The ports do not use a numbered default VLAN, PVID, or have any numbered VLAN set as "Untagged"
Physical NICs
- NICs do not have any VLAN settings applied, check both firmware and drivers
Physical NIC Team
- You are using exactly one team interface and it is not assigned a numbered VLAN
Virtual adapters (Hyper-V Side)
- Virtual adapters have been assigned to the correct VLAN
- Virtual adapters are connected to the correct virtual switch
Virtual adapters (inside guest)
- Adapter has appropriate TCP/IP settings
- Firewall is not blocking the expected traffic
Troubleshooting
If you've done all of the above and it still doesn't work, then you likely have a physical problem somewhere.
- Disconnect the wire from one physical adapter and test
- Reconnect the initial wire and wait for stable connectivity (viewable in LBFOAdmin.exe or
Get-NetLbfoTeamMember). - Disconnect the second wire and test
answered Sep 10 '18 at 14:14
Eric SironEric Siron
764
Hi Eric, I tried several times but no luck. The switch ports are trunk and no aggregation is configured. I configured VLAN under virtual adapter(hyper-v). How can I get logs from the Cisco and Windows regards to the network traffic?
– NeilWang
Sep 12 '18 at 22:25
You did specifically set the switches to use 802.1q tagging and added the VLAN(s) to the trunk VLAN allowed list? Windows doesn't really log network traffic like you're looking for; Wireshark is probably a better tool. But this really sounds like you have a switch configuration problem. You can look at Cisco logs with "show log" but I'm not going to be much help on that topic.
– Eric Siron
Sep 13 '18 at 16:48
Yeah, I allowed all the VLANs through the ports and enabled the trunk by simply using the "switchport mode trunk" command. It gonna really hard for troubleshooting since I can't get the log from Windows and I have no idea about the Wireshark. I will try to find something might useful on Cisco logs. Thanks anyway.
– NeilWang
Sep 14 '18 at 22:13
add a comment |
It's not entirely clear where your problem lies from your description. I'm uncertain about the "removing team" bit especially. If the VMs can communicate with each other when your virtual switch is Internal or Private, then the problem is not with Hyper-V.
If they can communicate with each other when you attach the virtual switch to only one unteamed adapter, then test using the other adapter instead. If one works but not the other, then it is likely a physical adapter or switch problem. If either works, but not both in a team, then it is likely a physical switch problem.
Check these points, even if you've already checked them. Problems like this are typically sourced back to something extremely minor and easy to overlook:
Physical Switch
- Ports are in trunk mode
- Ports are not in a port channel or LAG
- The desired VLAN is specifically allowed and/or marked as "Tagged"
- The ports do not use a numbered default VLAN, PVID, or have any numbered VLAN set as "Untagged"
Physical NICs
- NICs do not have any VLAN settings applied, check both firmware and drivers
Physical NIC Team
- You are using exactly one team interface and it is not assigned a numbered VLAN
Virtual adapters (Hyper-V Side)
- Virtual adapters have been assigned to the correct VLAN
- Virtual adapters are connected to the correct virtual switch
Virtual adapters (inside guest)
- Adapter has appropriate TCP/IP settings
- Firewall is not blocking the expected traffic
Troubleshooting
If you've done all of the above and it still doesn't work, then you likely have a physical problem somewhere.
- Disconnect the wire from one physical adapter and test
- Reconnect the initial wire and wait for stable connectivity (viewable in LBFOAdmin.exe or
Get-NetLbfoTeamMember). - Disconnect the second wire and test
answered Sep 10 '18 at 14:14
Eric SironEric Siron
764
Hi Eric, I tried several times but no luck. The switch ports are trunk and no aggregation is configured. I configured VLAN under virtual adapter(hyper-v). How can I get logs from the Cisco and Windows regards to the network traffic?
– NeilWang
Sep 12 '18 at 22:25
You did specifically set the switches to use 802.1q tagging and added the VLAN(s) to the trunk VLAN allowed list? Windows doesn't really log network traffic like you're looking for; Wireshark is probably a better tool. But this really sounds like you have a switch configuration problem. You can look at Cisco logs with "show log" but I'm not going to be much help on that topic.
– Eric Siron
Sep 13 '18 at 16:48
Yeah, I allowed all the VLANs through the ports and enabled the trunk by simply using the "switchport mode trunk" command. It gonna really hard for troubleshooting since I can't get the log from Windows and I have no idea about the Wireshark. I will try to find something might useful on Cisco logs. Thanks anyway.
– NeilWang
Sep 14 '18 at 22:13
add a comment |
It's not entirely clear where your problem lies from your description. I'm uncertain about the "removing team" bit especially. If the VMs can communicate with each other when your virtual switch is Internal or Private, then the problem is not with Hyper-V.
If they can communicate with each other when you attach the virtual switch to only one unteamed adapter, then test using the other adapter instead. If one works but not the other, then it is likely a physical adapter or switch problem. If either works, but not both in a team, then it is likely a physical switch problem.
Check these points, even if you've already checked them. Problems like this are typically sourced back to something extremely minor and easy to overlook:
Physical Switch
- Ports are in trunk mode
- Ports are not in a port channel or LAG
- The desired VLAN is specifically allowed and/or marked as "Tagged"
- The ports do not use a numbered default VLAN, PVID, or have any numbered VLAN set as "Untagged"
Physical NICs
- NICs do not have any VLAN settings applied, check both firmware and drivers
Physical NIC Team
- You are using exactly one team interface and it is not assigned a numbered VLAN
Virtual adapters (Hyper-V Side)
- Virtual adapters have been assigned to the correct VLAN
- Virtual adapters are connected to the correct virtual switch
Virtual adapters (inside guest)
- Adapter has appropriate TCP/IP settings
- Firewall is not blocking the expected traffic
Troubleshooting
If you've done all of the above and it still doesn't work, then you likely have a physical problem somewhere.
- Disconnect the wire from one physical adapter and test
- Reconnect the initial wire and wait for stable connectivity (viewable in LBFOAdmin.exe or
Get-NetLbfoTeamMember). - Disconnect the second wire and test
answered Sep 10 '18 at 14:14
Eric SironEric Siron
764
It's not entirely clear where your problem lies from your description. I'm uncertain about the "removing team" bit especially. If the VMs can communicate with each other when your virtual switch is Internal or Private, then the problem is not with Hyper-V.
If they can communicate with each other when you attach the virtual switch to only one unteamed adapter, then test using the other adapter instead. If one works but not the other, then it is likely a physical adapter or switch problem. If either works, but not both in a team, then it is likely a physical switch problem.
Check these points, even if you've already checked them. Problems like this are typically sourced back to something extremely minor and easy to overlook:
Physical Switch
- Ports are in trunk mode
- Ports are not in a port channel or LAG
- The desired VLAN is specifically allowed and/or marked as "Tagged"
- The ports do not use a numbered default VLAN, PVID, or have any numbered VLAN set as "Untagged"
Physical NICs
- NICs do not have any VLAN settings applied, check both firmware and drivers
Physical NIC Team
- You are using exactly one team interface and it is not assigned a numbered VLAN
Virtual adapters (Hyper-V Side)
- Virtual adapters have been assigned to the correct VLAN
- Virtual adapters are connected to the correct virtual switch
Virtual adapters (inside guest)
- Adapter has appropriate TCP/IP settings
- Firewall is not blocking the expected traffic
Troubleshooting
If you've done all of the above and it still doesn't work, then you likely have a physical problem somewhere.
- Disconnect the wire from one physical adapter and test
- Reconnect the initial wire and wait for stable connectivity (viewable in LBFOAdmin.exe or
Get-NetLbfoTeamMember). - Disconnect the second wire and test
answered Sep 10 '18 at 14:14
Eric SironEric Siron
764
answered Sep 10 '18 at 14:14
Eric SironEric Siron
764
answered Sep 10 '18 at 14:14
Eric SironEric Siron
764
answered Sep 10 '18 at 14:14
Eric SironEric Siron
764
764
Hi Eric, I tried several times but no luck. The switch ports are trunk and no aggregation is configured. I configured VLAN under virtual adapter(hyper-v). How can I get logs from the Cisco and Windows regards to the network traffic?
– NeilWang
Sep 12 '18 at 22:25
You did specifically set the switches to use 802.1q tagging and added the VLAN(s) to the trunk VLAN allowed list? Windows doesn't really log network traffic like you're looking for; Wireshark is probably a better tool. But this really sounds like you have a switch configuration problem. You can look at Cisco logs with "show log" but I'm not going to be much help on that topic.
– Eric Siron
Sep 13 '18 at 16:48
Yeah, I allowed all the VLANs through the ports and enabled the trunk by simply using the "switchport mode trunk" command. It gonna really hard for troubleshooting since I can't get the log from Windows and I have no idea about the Wireshark. I will try to find something might useful on Cisco logs. Thanks anyway.
– NeilWang
Sep 14 '18 at 22:13
add a comment |
Hi Eric, I tried several times but no luck. The switch ports are trunk and no aggregation is configured. I configured VLAN under virtual adapter(hyper-v). How can I get logs from the Cisco and Windows regards to the network traffic?
– NeilWang
Sep 12 '18 at 22:25
You did specifically set the switches to use 802.1q tagging and added the VLAN(s) to the trunk VLAN allowed list? Windows doesn't really log network traffic like you're looking for; Wireshark is probably a better tool. But this really sounds like you have a switch configuration problem. You can look at Cisco logs with "show log" but I'm not going to be much help on that topic.
– Eric Siron
Sep 13 '18 at 16:48
Yeah, I allowed all the VLANs through the ports and enabled the trunk by simply using the "switchport mode trunk" command. It gonna really hard for troubleshooting since I can't get the log from Windows and I have no idea about the Wireshark. I will try to find something might useful on Cisco logs. Thanks anyway.
– NeilWang
Sep 14 '18 at 22:13
Hi Eric, I tried several times but no luck. The switch ports are trunk and no aggregation is configured. I configured VLAN under virtual adapter(hyper-v). How can I get logs from the Cisco and Windows regards to the network traffic?
– NeilWang
Sep 12 '18 at 22:25
Hi Eric, I tried several times but no luck. The switch ports are trunk and no aggregation is configured. I configured VLAN under virtual adapter(hyper-v). How can I get logs from the Cisco and Windows regards to the network traffic?
– NeilWang
Sep 12 '18 at 22:25
You did specifically set the switches to use 802.1q tagging and added the VLAN(s) to the trunk VLAN allowed list? Windows doesn't really log network traffic like you're looking for; Wireshark is probably a better tool. But this really sounds like you have a switch configuration problem. You can look at Cisco logs with "show log" but I'm not going to be much help on that topic.
– Eric Siron
Sep 13 '18 at 16:48
You did specifically set the switches to use 802.1q tagging and added the VLAN(s) to the trunk VLAN allowed list? Windows doesn't really log network traffic like you're looking for; Wireshark is probably a better tool. But this really sounds like you have a switch configuration problem. You can look at Cisco logs with "show log" but I'm not going to be much help on that topic.
– Eric Siron
Sep 13 '18 at 16:48
Yeah, I allowed all the VLANs through the ports and enabled the trunk by simply using the "switchport mode trunk" command. It gonna really hard for troubleshooting since I can't get the log from Windows and I have no idea about the Wireshark. I will try to find something might useful on Cisco logs. Thanks anyway.
– NeilWang
Sep 14 '18 at 22:13
Yeah, I allowed all the VLANs through the ports and enabled the trunk by simply using the "switchport mode trunk" command. It gonna really hard for troubleshooting since I can't get the log from Windows and I have no idea about the Wireshark. I will try to find something might useful on Cisco logs. Thanks anyway.
– NeilWang
Sep 14 '18 at 22:13
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f930090%2fhow-to-utilize-nic-teaming-for-hyper-v-vms-with-vlan-in-windows-server-2016%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
