OPERATIONAL DEFECT DATABASE
...
...
When the interface IP is included in the object, as a part of the subnet object, the FMC doesn't report an error when using this object as part of the translated source or the destination network. it's getting accepted and saved, however the deployment will fail since the object contains an IP that overlap with the interface IP
Destination Interface IP is included in the subnet that is part of the object group. adding this object group as a translated source or destination network
exclude the IP address of the interface from the object group, or any entry that overlaps with the Interface IP. In case you want to Nat the Source Network ip to the same ip address as that of Destination Interface address, then use 'Interface' as the option in the UI rather than using it as a Network or Network Group Object.
When using the interface IP as a host object, where the object contains only one IP which is the interface IP, an error pops up when saving with the following details "Translated Source or Original Destination network IP address cannot overlap with Interface Ip address" However, this is not the case when the interface IP is included in range or subnet, configuration is getting saved and there are no error messages
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
