It has been suggested we configure an ACE with the VIPs not associated with a VLAN, By that I mean we have an inside and outside interface as normal (routed mode), but the VIP address is not associated with either interface - on a router it would be on a loopback.
A VIP is never associated to a VLAN, rather it is associated to a policy map.
Having said that, it is true that you can apply a policy map either to the global conf (i.e. ex 1 below)or to a specific VLAN (i.e. ex 2 below). When you apply it globally, then any request coming from any VLAN might hit the VIP. Otherwise if you apply it under a interface VLAN, only requests directed to the VIP and coming from those specific VLAN will hit the service policy.
Normally I can tell you that policy maps are applied under an interface VLAN. However depending on your set up, it might be worthy to apply them in the global.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...