Preview Tool

Cisco Bug: CSCvt38095 - TLS Gateway FQDN is not getting resolved / tunnel does not get established post ME reboot

Last Modified

Jul 28, 2020

Products (1)

  • Cisco Mobility Express for Aironet Access Points

Known Affected Releases


Description (partial)

After initial TLS configuration, the secure tunnel status ip UP. But after saving and reloading the ME, the tunnel never comes up. It starts to work when we click on Apply button in the TLS configuration GUI or disable and enable again from CLI. The issue is happening only when TLSGW is FQDN and happening when it is IP address.

TLSGW is configured with FQDN and DNS network option is configured with 'default' and not manual server ip
Bug details contain sensitive information and therefore require a 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.