Preview Tool

Cisco Bug: CSCvu36573 - Opflex connection failing for Hyper-v hosts on multipod setups

Last Modified

Sep 02, 2020

Products (1)

  • Cisco Application Policy Infrastructure Controller (APIC)

Known Affected Releases

4.2(4i) 4.2(4k) 4.2(4o) 5.0(1k)

Description (partial)

When a multi-pod environment is deployed in a non-home pod, the hyper-v servers cannot establish a successful connection to the leaf switch, and the opflexODev and OpflexIDEp objects are not created on the leaf switch. This results in a traffic outage, as the on-demand EPGs will be removed from the setup.

Hyper-v hosts connected to the non-home pod subnet will not resolve the anycast IP address to the proper subnet, which causes leaf discovery to fail. In a failure scenario, the following logs will be seen:

Hyper-V VTEP IP is allocated to subnet and it is trying to wrongly reach to leaf anycast IP of instead of and will result in failure.

05/01/2020 10:43:57-20072-26||DiscoverSwitchSettings||  Discovered VTEP address is Macaddress is 112233445566 vTepNetworkName: vEthernet (VNET_apicinfra) VtepSubnetMask
05/01/2020 10:43:58-20072-26||GetSwitchPropertyOpaqueData|| VMMDOM: Domain CTRLR: SCVMM HOSTORIP: AnyCAST: NonEnglish: 1
05/01/2020 10:43:58-20072-26||DiscoverSwitchSettings|| CtrlrName:SCVMM, DomainName:Domain, SCVMM_LeafAnycastAddr:, MPodAnyCastAddr
05/01/2020 10:43:58-20072-26||SendRequest|| Querying Leaf URL
05/01/2020 10:44:03-20072-26||SendRequestWithCert|| Exception Message : The operation has timed out
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.