Unable to pass traffic on the Dynamic Multipoint VPN tunnel with the "%NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14)" error message

[TCC_2]

Core issue

If the spoke router is configured with the dynamic IP address, the cached nonbroadcast, multiaccess (NBMA) with the Next Hop Resolution Protocol (NHRP) address on the hub does not match to a new dynamic NBMA address with the NHRP address. If this happens, the %NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14) error message appears on the spoke router.

Resolution

In order to resolve this issue, configure the ip nhrp registration no-unique command on the spoke router.

If the unique flag is set in the NHRP registration request packet, a Next Hop Server (NHS) must reject any registration attempts for the same private address that uses a different NBMA address. If a client receives a new IP address, for example on Dynamic Host Configuration Protocol (DHCP), and tries to register before the cache entry on the NHS times out, the NHS must reject it.

If you configure the ip nhrp registration no-unique command, the unique flag is not set, and the NHS can override the old registration information.

This command is useful in an environment where client IP addresses can change frequently such as a dial environment.

[mohammed asif suleman]

Thank you very much for the superb soln.

[ashish.sehgal1]

I applied the command, unfortunaetely still getting the same error :(

*Mar 1 01:35:00.343: %NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14)

[hachemirafik]

You should add also the command ip nhrp registration timeout with a low value in seconds at the spoke router to remove the obsolete registration quickly