Router Log：%NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14) 的Error Message

異常 Log：
Sep 14 05:37:05.692 TWN: %AAA-3-BADSERVERTYPEERROR: Cannot process accounting server type radius (UNKNOWN)
Sep 14 05:37:05.708 TWN: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di1
Sep 14 05:37:05.712 TWN: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
Sep 14 05:37:06.688 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down
Sep 14 05:37:06.692 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel471, changed state to down
Sep 14 05:37:27.980 TWN: %DIALER-6-BIND: Interface Vi2 bound to profile Di1
Sep 14 05:37:27.984 TWN: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
Sep 14 05:37:29.692 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up
Sep 14 05:37:29.736 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel471, changed state to up
Sep 14 05:37:32.344 TWN: %NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14)
Sep 14 06:17:29.770 TWN: %NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14)
Sep 14 06:57:29.779 TWN: %NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14)
Sep 17 05:21:28.664 TWN: %AAA-3-BADSERVERTYPEERROR: Cannot process accounting server type radius (UNKNOWN)
Sep 17 05:21:28.684 TWN: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di1
Sep 17 05:21:28.688 TWN: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
Sep 17 05:21:29.664 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down
Sep 17 05:21:29.668 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel471, changed state to down
Sep 17 05:21:50.956 TWN: %DIALER-6-BIND: Interface Vi2 bound to profile Di1
Sep 17 05:21:50.960 TWN: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
Sep 17 05:21:52.312 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up
Sep 17 05:21:52.408 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel471, changed state to up
Sep 17 05:21:55.216 TWN: %NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14)
Sep 17 06:01:52.413 TWN: %NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14)
Sep 17 06:41:52.443 TWN: %NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14)
Sep 20 05:23:51.348 TWN: %AAA-3-BADSERVERTYPEERROR: Cannot process accounting server type radius (UNKNOWN)
Sep 20 05:23:51.368 TWN: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di1
Sep 20 05:23:51.372 TWN: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
Sep 20 05:23:52.348 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down
Sep 20 05:23:52.348 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel471, changed state to down
Sep 20 05:24:13.640 TWN: %DIALER-6-BIND: Interface Vi2 bound to profile Di1
Sep 20 05:24:13.644 TWN: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
Sep 20 05:24:15.076 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up
Sep 20 05:24:15.124 TWN: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel471, changed state to up
Sep 20 05:24:17.904 TWN: %NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14)
Sep 20 06:04:15.158 TWN: %NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14)
Sep 20 06:44:15.168 TWN: %NHRP-3-PAKREPLY: Receive Registration Reply packet with error - unique address registered already(14)
[點擊此處縮放]

Client 端是使用浮動 IP 來做 PPPOE，每三天更換一次 Public IP

撥接介面：
Dialer1 is up, line protocol is up (spoofing)
Hardware is Unknown
Internet address is ********
MTU 1492 bytes, BW 56 Kbit/sec, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, loopback not set
Keepalive set (10 sec)
DTR is pulsed for 1 seconds on reset
Interface is bound to Vi2
Last input never, output never, output hang never
Last clearing of "show interface" counters 1w6d
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/0/16 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
Available Bandwidth 42 kilobits/sec
30 second input rate 0 bits/sec, 0 packets/sec
30 second output rate 0 bits/sec, 0 packets/sec
302042 packets input, 17189948 bytes
113534 packets output, 1680424 bytes
Bound to:
Virtual-Access2 is up, line protocol is up
Hardware is Virtual Access interface
MTU 1492 bytes, BW 56 Kbit/sec, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 9/255
Encapsulation PPP, LCP Open
Listen: CDPCP
Open: IPCP
PPPoE vaccess, cloned from Dialer1
Vaccess status 0x44, loopback not set
Keepalive set (10 sec)
Interface is bound to Di1 (Encapsulation PPP)
Last input 00:00:00, output never, output hang never
Last clearing of "show interface" counters 17:19:17
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 2000 bits/sec, 4 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
22421 packets input, 1441224 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
6237 packets output, 101996 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
[點擊此處縮放]

設定值：
!
interface Dialer1
mtu 1492
ip address negotiated
encapsulation ppp
load-interval 30
dialer pool 1
dialer watch-group 1
dialer-group 1
ppp authentication pap chap callin
ppp chap hostname ********
ppp chap password ********
ppp pap sent-username ******** password ********
!
[點擊此處縮放]

在Cisco Support Community 找到了一篇關於此問題解決方法供參考

---------- 下列轉至 Cisco Support Community ----------

( 點選標題 Link 可直接連至原頁面 )
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

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.
[點擊此處縮放]