Version 6.2.3 Known Issues
Bug ID |
Headline |
---|---|
SF Cli - "inside" or "outside" interface capture not giving all options |
|
Firepower Management Center does not support userPrincipalName attribute for login with ISE 2.2+ |
|
Core in Firepower Management Center Perl |
|
Using the match keyword in capture command causes IPv6 traffic to be ignored in capture |
|
Small number of TLS connections can fail after TLS inspection in Hardware Mode is overloaded |
|
With SSL inspection in software mode, a few TLS connections fail to close in a timely manner |
|
SSL errors on session resume when server IP address changes - HW mode |
|
Firepower Threat Defense show tech-support command output broken on 2100 from CLISH CLI |
|
With SSL inspection enabled, TLS traffic throughput can drop following high-availability failover |
|
Deployment Failed-Snort Restart Failure- APPLY_APP_CONFIG_APPLICATION_FAILURE SignalAppConfigFailed |
|
Deployment failure due to Snort failed to restart PDTS Handle was NULL |
|
Decrypted connections fail when SSLv2 is supported but a higher version is negotiated |
|
Some indicators may stay pending when consuming TAXII feeds in parallel |
|
Firepower Device Management fails on 2100 (6.2.3-51 (PortChannel)) |
|
Unable to delete certificate objects if there were previous used at ISE even it was deleted |
|
Routed Threat Defense allows Transparent Configuration, but traffic fails (6.2.3-66) on KVM only |
|
Firepower Threat Defense virtual on ESXi Firstboot config does not sync hostname correctly with FQHN |
|
Firepower 2110 dropping connections |
|
With SSL inspection in hardware mode and Malware protection, secure file transfers occasionally fail |
|
CNP has been enabled in Firepower Management Center where it usage Satellite server for license |
|
Same groups from different AD not downloaded |
|
FMC backup restore fails if it contains files/directories with future timestamps |