We do a basic load balancing configuration for https. 3 servers. 1 is currently suspended. Today one of the servers in the content rule crashed. After it came up it showed a current 3100 connections?!?!?!? and fluctuated by a few up and down.... as time progressed.
The other server showed 20 connections. I had the server folks tell me how many active connects they had on the one that said 3000+ in the CSS and he said 3.
But 3000 connections? I don't think this server can handle 1000 concurrent connections.. hehe. Much less 3000.
Thanks for all this info on the flows. I did a sho flow at the time and only saw about 50 flows listed. I didn't know those other commands however. You can get a lot of information about the particular flow.... but if the current local connections value showed 3000+ shouldn't I have seen 3000+ flows when I did a show flows?
the show flow limit its output to the first 100 flows.
If the counter dropped by itself I still believe it was somehow connections for which the CSS didn't see the FIN or RESET. So they were kept alive even if on the server they had been removed. It does not mean the 3000 connections existed on the server at the same time.
I see... then what this may imply is that the server went down... and the CSS was still sending traffic to it? possibly?!?! Before it showed as 'dying'... and then once it was 'dead' it stopped trying to send traffic... leaving a bunch of 'half open' connections... hanging there.. ?
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...