ANTP0133E
PPRC REQUEST FAILED - PATH PROTOCOL MISMATCH

Explanation

A PPRC request specified FCP paths or WWNNs on the request, but the secondary LSS is connected to the specified primary LSS using ESCON® paths. Or the PPRC request specified ESCON paths or storage control serial numbers, but the secondary LSS is connected to the specified primary LSS using FCP paths. The request must be issued using the same protocol existing for the PPRC path when establishing new paths or deleting existing paths.

If you are trying to switch your path(s) in a LSS to LSS association from ESCON to FCP or vice versa and do not want to delete your PPRC pairs, you can use the procedure below. If you do not need to preserve your PPRC pairs, you can simply delete the pairs and existing paths and then establish new paths in the other protocol.
  1. Issue a CGROUP FREEZE command to the primary LSS. This will remove all of the ESCON paths and suspend all the PPRC pairs in the LSS to LSS association.
  2. Issue a CGROUP RUN command to allow Host application I/O to the primary volumes to resume.
  3. Issue the CESTPATH command using the applicable required parameters to re-establish the PPRC paths.
  4. Issue the CESTPAIR command with the MODE(RESYNC) option to re-establish the PPRC pairs.

System action

The request is rejected.

System programmer response

If you are issuing an establish path request to simply change which link addresses are to be used between the two LSSs without intending to change protocol, reissue the establish path request using the same protocol as used by the existing paths. If you are issuing a delete path request for existing paths, reissue the delete path request using the same protocol as used by the existing paths.

Source

Peer-to-peer remote copy (PPRC).

Parent topic: ANT messages