What are the disadvantages of configuring ip address on WAAS Inline interface?
Hi - currently, waas is running in Inline mode and waas-g0/0 is the primary interface for management traffic.
I am thinking to move the ip address on waas-g0/0 to the Inline interface. I know it is supported & can be done.
However, before to do that I would like to get your thoughts of what are the disadvantages of doing this?
The reason being is that waas-g0/0 port is connected to a cisco switch which is located "behind" the waas appliance, so if the switch or swtich port goes down, our NMS system will receive a waas went down alarm message which is not true, actually, the waas is up but the waas-g0/0 managment port that connected to the switch is down and this creates lot of confusiion.
It makes more sense to move the managment ip address to Inline interface as this will tell us the "true" state of the waas.
One major disadvantage is that if you, for some reason, wants to disable the inline interface, e.g. to stop optimization temporarily, you will loose connectivity to the WAAS box itself ... and thus you cannot enable it again.
Besides this, I think that if you loose the switchport or the entire switch, the inlineinterface and the interface on the router will go down as well ... and you'll gain nothing.
At least this is the way the inline adapter are supposed to work, because of the internal relay.
Topology & Design:
Two ACI fabrics
Stretching VLANs using OTV
Both fabrics are advertising BD subnets into same routing domain
Some BDs(or say VLANs) are stretched, but some are not.
Endpoints can move betwee...
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
Topology &Design:Traffic flow within same fabric:Endpoint moves to Fabric-2Bounce Entry Times OutTraffic Black-holedSummarySolutionAppendix:
In the Previous articles of ACI Automation, we are using Postman/Newman a...