In the 8.3+ software levels user dont need any NAT configuration between 2 interfaces if he/she dont need to specifically NAT something.
If you have a Dynamic PAT configuration from "inside" to "mpls" that contains the networks behind "inside" as the source address then in this situation you would need another NAT configuration to enable communication from the "mpls" to "inside". (to enable bidirectional connection forming that is)
If there is no NAT configuration between "inside" and "mpls" at the moment then you wont need any NAT configuration. You will just have to make sure the traffic is allowed in the interface ACL. If your have equal "security-level" between the interfaces then you will have to make sure you have "same-security-traffic permit inter-interface" also configured.
In 8.3 version nat statement depends on object. You need to create object for the source ip as well nat ip and call the object in nat statement.
I am new to ISE and after going through some of documentation I am having problems getting this specific setup to work. The version of ISE is 2.4 and it doesn't have any cumulative patches installed.
The context for the situa...
We are trying to remove all AAA configuration from an ASR9k. No matter how we try to remove we are getting commit failed. Does anyone know if there are specific steps required to remove AAA? We have removed all dependencies on AAA, so we...
For Version 12.5 on SSL Cert-Config is written:"TLSv1.0 and TLSv1.1 cannot be enabled simultaneously, but both can be enabled for use with TLSv1.2." What does it mean?TLSv1.2 + v1.1 + v1.0 enabled is NOT ok?butTLSv1.2 + v1.1 OR TLSv1.2 + v1.0 is ok?&...
Hi guys, I am having a strange issue....I really hope that you can help me with... We have a site-to-site tunnel with out BGP running up against Azure.... It works no issue here, but after 10-11 days the connections drops... I can see that the t...