I just installed waas in version 4.2.1 and got a weird ping result. On the core wae I enabled the management interface as gig1/0 (10.0.0.1) and the gigi 2/0 just for wccp with the router (192.168.0.1) and the default gateway on the same subnet as the management interface. When I do a ping to the management interface of the waas from a remote location I get this duplicate pings, when I perform a trace route this does not happen. Is this an expected behavior?
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
64 bytes from 10.0.0.1: icmp_seq=1 ttl=58 time=18.8 ms
64 bytes from 10.0.0.1: icmp_seq=1 ttl=58 time=20.9 ms (DUP!)
64 bytes from 10.0.0.1: icmp_seq=2 ttl=58 time=17.9 ms
64 bytes from 10.0.0.1: icmp_seq=2 ttl=58 time=19.6 ms (DUP!)
This document will provide screenshots to outline the steps to setup
TACACS+ configuration to ACI and also the configuration required on
Cisco ACS server. Please find the official Cisco guide for configuring
TACACS+ Authentication to ACI:
Is it supported or NOT supported? It's a frequently asked question.
Before APIC, release 2.3(1f), transit routing was not supported within a
single L3Out profile. In APIC, release 2.3(1f) and later, you can
configure transit routing with a single L3Out pr...
Cisco Documents are usually accurate, but when it came to the document
on Cisco APIC Signature-Based Transactions it was slightly off the mark.
This document is for those novices to API like me who cant seem to
figure out how to go about performing signat...