Guest

Preview Tool

Cisco Bug: CSCuo53813 - Validate IPSec Ping results blank when ESP packets are sent.

Last Modified

Jul 03, 2017

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

10.5(1.98300.9)

Description (partial)

Symptom:
Pre-condition : If FIPS is enabled and valid IP Sec policies exist.
In OS Administration > Services > Ping, if you select Validate Ping, there will be no evidence that the ping has occurred. A wireshark will show that ESP packets are exchanged between select nodes (with IPSec Policies)

Conditions:
FIPS enabled. Valid IP Sec policies exist.

Related Community Discussions

CUCM-IPSEC Policy Failure between CUCM and MGCP-GWY
CUCM 10.5(2) IPSEC security policy between ISR-G2 (15.5) MGCP GWY establishes ISAKMP SA, but fails to establish IPSEC SA's.  IPSEC policy matches on CUCM and GWY.  IKE PHASE 1 Main Mode is successful. I get all 6 MM messages on sniffer trace and a "show crypto isakmp sa" shows QM_IDLE Active. IKE Phase 2 Fails.  Sniffer shows IKE Phase 1 completing and IKE Phase 2 not completing.  I reduced the IPsec Sec. Parms from AES 256, sha-256 and DH Group 5 down to 3des and Sha1 and Group 2.  I was able to ...
Latest activity: Mar 08, 2017
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.