I have a strange problem trying to get VMWare VDI working with WAAS. The central site has a 6500 using WCCP to a core WAE. The remote site is connected via VPN and has an in-line WAE. The firewalls are running Inspect WAAS and all traffic is being optimised without problems.
You can see standard RDP traffic and HTTP traffic being optimised and CIFS is flying.
The VDI systems are using small WYSE terminals which have a two stage logon process. The first stage uses a secure HTTP connection to the VDI Broker (on IP address (x.x.152.10) to authenticate, which is does OK and the connection is displayed on the remote WAE (sh stats conn). The VDI broker then launches a VM using IP address x.x.152.65, which is obviously on the same subnet. BUT, the remote terminal cannot access the x.x.152.65 device from that site. You can access the VM x.x.152.65 from any other location in the network. Indeed, nobody from that site can access that VM. Whether they use a PC to RDP or use the VMWare client on the WYSE terminal.
If you remove the WAAS from the equation it works fine.
What's the difference? The VDI broker is on a different ESX server but they are on the same IP subnet. There is an IDS/IPS system in the core of the network that monitors traffic but i cannot see why this would matter.
Let me start by telling you that there is already a very nice document in the Cisco Community Forums which describes the procedure to upgrade the APIC CIMC. In case you came across this document before looking into the mentioned one, here is...
2020年7月14日 (初版)主な問題F3 ラインカードを利用した場合、Shared Policers の設定により通信レートを期待値に制御できません。CIR 値を 1048600 に設定し、以下一例となります。128 byte のペイロードのパケットが通過している場合の、egress port 側の sh int の出力：N7K(config)# sh int e1/1 | i i rate
Rate mode is dedicated
30 seconds input ...