Re: TCP connections effect in case of waas failure
Cisco WAAS utilizes standards-based TCP optimizations to remove TCP as a barrier to application performance over the WAN. By initiating a TCP Proxy after autodiscovery, communicating nodes experience LAN-like TCP behavior through local acknowledgement and TCP handling. As such, when the network goes down the TCP proxy has the ability to mask the disconnect for a short time, but after that all TCP connection will reset and clients will try to re-establish a connection.
-During transient disconnects (up to 95 seconds), the WAAS Edge maintains data in its buffers and retries the transmission to the WAAS Core upon network re-connect.
- When the WAAS Edge switches to "disconnected mode", its services change to "no service" and the buffered data is lost. Further file operations will fail and the Client will be alerted that the server is disconnected. Open documents can be "saved as" on another drive
-If the accessed file server was configured for "Disconnected Mode" CIFS clients will be able to continue to browse the cache directory and read fully cached files on an WAAS Edge
In addition with Windows on WAAS providing local window services (dns, authentication) user can access local file shares on WAVE
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...