Catalyst 9800 on Hyper v issue

[guidov2]

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

[Mark Elsen]

 - Carefully review installation guidelines, and needed resources from the document below; also pay attention to the section Configuring Tagged ports :

   https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/9800-cloud/installation/b-c9800-cl-install-guide/b-c9800-cl-install-guide_chapter_01011.html

 M.

[guidov2]

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 ?

[Mark Elsen]

 - Also check and or lookup compatibility between 9800-virtual version being installed and hyper v version currently in place.

 M.

[guidov2]

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

[guidov2]

sorry for typo

16.12.02s not 6.12.02s

[Rich R]

I can't see any compatibility matrix either. Presume you've checked the Hardware and VM Requirements and Network Connectivity Issues sections in https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/9800-cloud/installation/b-c9800-cl-install-guide/troubleshooting.html
There's a bit of info on vNICs and switches at https://www.cisco.com/c/en/us/products/collateral/wireless/catalyst-9800-cl-wireless-controller-cloud/nb-06-cat9800-cl-cloud-wirel-data-sheet-ctp-en.html#Features

[Mark Elsen · Accepted solution]

 Ref : https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/16-12/release-notes/rn-16-12x-9800.html#id_114714

 It seems that if you look at the Supported Hardware hardware section that Hyper-V is not listed, whilst in 

 https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-1/release-notes/rn-17-1-9800.html#id_114714

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)

[Rich R]

Well spotted - I didn't check the release notes - duh! 🙂

[roberto pargalia]

Thank You Marce,

I have the same problem too.

we check !

Roberto

[guidov2]

Thank you 

this explain the issue

[guidov2]

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

[Mark Elsen]

 - 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.

[Mark Elsen]

 - 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.

[guidov2]

Thanks