Upgraded core WAAS to 4.1.3b and edge device will not peer
I had a data center that had 2 WAE's running 4.0.1c and a single edge WAE running 4.1.3a. Everything ran fine. I upgraded the WAE's at the core to 4.1.3a this weekend and now the edge WAE that was already running 4.1.3a will not peer. WCCP is established locally. The core WAE's in the data center are peering with WAE's in another data center just fine. I am getting ZERO TFO connections on that edge WAE.
Re: Upgraded core WAAS to 4.1.3b and edge device will not peer
I found my WCCP had locked up on my 3750 switch. It showed the WAE connected when I did a "show ip wccp" but it also showed connected after disabling WCCP on the WAE. All is good now after resetting WCCP.
Why do you need native HA: The native HA feature allows two Cisco DCNM
appliances to run as active and standby applications, with their
embedded databases synchronized in real time. Therefore, when the active
DCNM is not functioning, the standby DCNM will...
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...