Guest

Preview Tool

Cisco Bug: CSCur16793 - xlate per-session commands are not synchronized

Last Modified

Sep 13, 2019

Products (1)

  • Cisco ASA 5500-X Series Firewalls

Known Affected Releases

9.0(4.24) 9.1(5.12)

Description (partial)

Symptom:
xlate per-session  are not synchronized between active/standby failover units.
This is an example.

[active unit]
ciscoasa/admin/act(config)# show run xlate

[standby unit]
ciscoasa/admin/stby(config)# show run xlate
xlate per-session deny tcp any4 any4
xlate per-session deny tcp any4 any6
xlate per-session deny tcp any6 any4
xlate per-session deny tcp any6 any6
xlate per-session deny udp any4 any4 eq domain
xlate per-session deny udp any4 any6 eq domain
xlate per-session deny udp any6 any4 eq domain
xlate per-session deny udp any6 any6 eq domain

Conditions:
This issue occurs only that multi context mode and failover is enabled when there is no startup-config in standby unit.

-----
ciscoasa# show mode
Security context mode: multiple
ciscoasa# sh startup-config
No Configuration
-----
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.