I have 2 server behind a CSS one is a windows and the other one is a Solaris, both of them given the same service through the same content, and both in the same source-nat-group, both servers need to do traceroute to the internet, the windows one send traceroute using icmp and solaris uses UDP, I can do traceroute from windows box using icmp through de CSS but I can't do traceroute from Solaris box using UDP.
I have found this info:
Traceroute is not quite so straight forward. Different platforms perform traceroute in different manners (UDP, ICMP, and so on), and it is not the port number alone which signifies that something is a traceroute packet.
The CSS does not setup flows for ICMP packets at all. The check for a traceroute packet says to not setup a flow if the following conditions exist:
1. Protocol is UDP.
2. The source port is less than 32769.
3. The destination port is less than 33434.
4. The UDP data length is less than 20.
5. There is 1 byte sequence number in UDP portion.
6. There is 1 byte original TTL.
If all these conditions are true, you will not setup a flow for this packet.
but even ICMP doesn't setup a flow the traceroute works fine, but doesn't work it traceroute use UDP as for Solaris.
Ping to the internet works fine from both servers.
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...