I know failover for my content rules works without having the corresponding VIP defined as a "redundant-vip" under the client-facing VRRP group in the circuit configuration section. (failover works because my upstream gateway/firewall has a static route for my VIP via my CSS redundant interface IP).
The question is: will ASR work if my content rule VIPs are not within the IP subnets defined on my CSS circuits/VLANs?
For example, our gateway/firewall has a static route for my VIP (192.168.1.100) via 172.20.30.254 (VR on my CSS):
!********************* GLOBAL *********************
Have you tested this in your lab? What I found out is:
This kind of set up (VIP is outside of client circuit) will work with redundancy, but not ASR, means not session failover. Since session failover needs redundant-index, which in terms needs vip been associated with a VRID, but you can't, since it is outside of client circuit subnet:
add service web1
add service web2
vip address 192.168.30.100
when I tried to active this rule:
%% VIP address needs to be associated with a virtual router.
When tried to associate this vip to a VR:
css-lab1(config-circuit-ip[VLAN902-188.8.131.52])# ip redundant-vip 102 192.168.30.100
%% Address outside of allowed range.
Gilles, any way to around this problem? or if you want to use ASR, vip must be on the client circuit?
The unmanaged mode is also known as Network only switching, which is introduced in Brazos release. It adds the flexibility for customer to use only network automation for service appliance.
If a device is configured a...
Usually, we can access ESXi Shell by pressing Alt+F1 from ESXi DCUI (Direct Console User Interface).
But on HyperFlex system, it just shows black window.
This is expected behavior because HyperFlex redirects ESXi Shell output to SoL...
Configuring an Export Policy Using the GUI
This procedure explains how to configure an Export policy using the APIC GUI. Follow these steps to trigger a backup of your data:
On the menu bar, choose Admi...