03-25-2020 12:53 AM - edited 07-05-2021 11:53 AM
Hello,
Strange issue with Catalyst 9800 hosted on Hyper v:
Interfaces doesn't work in switch port mode:
if interfaces are configured in switchport mode (access or trunk) it seem there is no transmission to the outside.
In routing mode it works correctly.
Already installed on other VM (not Hyper v) without issue.
from WLC we can see the arp table is populated .. but other devices cannot see its mac address and there is no entry in apr table.
with FIA packet trace we can see
Drop with reason 493.
in attach screenshot of packet capture
Solved! Go to Solution.
03-26-2020 02:56 AM
It seems that if you look at the Supported Hardware hardware section that Hyper-V is not listed, whilst in
Supported Hardware section it is mentioned that you need (see tabled output below). This implies that your version does not yet support Hyper-V and that you will need 17.1.x at least to start with.
Microsoft Hyper-V |
Windows Server 2016 (Version 1607) with Hyper-V Manager (Version 10.0.14393) |
03-25-2020 01:55 AM
- Carefully review installation guidelines, and needed resources from the document below; also pay attention to the section Configuring Tagged ports :
M.
03-25-2020 02:34 AM
Hello,
reviewed few time the installation guidelines.
tagged ports configured in powershell as the example:
Get-VMNetworkAdapter -VMName <C9800-name>
for trunk port:
Set-VMNetworkAdapterVlan -VMName “C9800” -VMNetworkAdapterName Eth1 -Trunk -AllowedVlanIdList “1-4000” -NativeVlanId 0
for access port (management):
-VMName “C9800” -VMNetworkAdapterName Eth0 -Untagged
Any other ideas ?
03-25-2020 03:51 AM
- Also check and or lookup compatibility between 9800-virtual version being installed and hyper v version currently in place.
M.
03-25-2020 09:43 AM
Hello,
I cannot find the compatibility matrix for Hyper v with 9800 version.
9800 version is 6.12.02s
do you have any link for this ?
Thanks and regards
Guido
03-25-2020 09:44 AM
sorry for typo
16.12.02s not 6.12.02s
03-26-2020 02:44 AM
03-26-2020 02:56 AM
It seems that if you look at the Supported Hardware hardware section that Hyper-V is not listed, whilst in
Supported Hardware section it is mentioned that you need (see tabled output below). This implies that your version does not yet support Hyper-V and that you will need 17.1.x at least to start with.
Microsoft Hyper-V |
Windows Server 2016 (Version 1607) with Hyper-V Manager (Version 10.0.14393) |
03-26-2020 03:00 AM
03-26-2020 03:07 AM
Thank You Marce,
I have the same problem too.
we check !
Roberto
03-26-2020 03:12 AM
Thank you
this explain the issue
03-26-2020 08:04 AM
I spoke too early.
it doesn't work also with 17.x train
Hosting machine is widows server 2019 1809 build 17763 v. Hyper v manager10.0.1763.1 (switch embedded teaming )
Issue is: from int g1 (routed mode) all works fine - g2 (trunk - native vlan 21).
it is like it receive packets but they are not sent
any vlan on trunk can see mac addresses on its vlan but other devices cannot see the 9800 mac
for example default gateway for each vlan does not see arp entri of vlan configured on 9800
thanks and regards
03-26-2020 08:13 AM
- As this is all fairly new from the controller-versioning side and the hyper-v support, you may want to take these issue up with Cisco TAC.
M.
03-26-2020 08:16 AM
- Also note that you are not using the exact specified hyper-v environment in terms of windows and hyper-v versions. This is tricky. Usually things are upwards compatible, but for specialized appliances this is not always true. They for instance need to be certified for later versions of windows and hyper-v. You need authoritative confirmation from TAC that it will work on your hyper-v environment.
M.
03-27-2020 09:43 AM
Thanks
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide