Troubleshooting HP-UX IPSec

Troubleshooting Scenarios

Symptoms

Output from the ipsec_report -sadcommand does not show IPSec/QM SAs and the audit log contains Quick Mode processing failed or QM negotiation timeout error messages.

Solution

Run ipsec_policy to determine the IPSec policy that HP-UX IPSec is using, or execute the ipsec_report -cacheand ipsec_report -hostcommands.

Check the transform list and lifetimes. Check the audit file.

Additional Information

If the ISAKMP/MM SA negotiation succeeded but the IPSec/QM SA negotiation failed, you will probably not see any ISAKMP/MM SAs in the output of the ipsec_report -madcommand. This is because the HP-UX IPSec IKE daemon tears down an ISAKMP/MM SA if an IPSec/QM SA negotiation fails. To be sure that the ISAKMP/MM negotiation succeeded and that IKE actually attempted to negotiate the IPSec/QM SA, look for Quick Mode processing failed or QM negotiation timeout error messages in the audit file. A QM negotiation timeout error usually indicates that the remote system did not agree with the IPSec/QM SA proposal and chose not to respond.

Check which IPSec policy is being used with the ipsec_policy command. Check the IPSec policy configurations for mismatches.

Manual Keys Fail

Problem

Manual keys do not work.

Symptoms

Link errors (unable to connect) and timeouts. The output from the ipsec_report -sadcommand shows the SAs, but attempts to exchange data with the remote system fail.

178

Chapter 5