Nd6 Delete - Zte ZXR10 Command Manual

Syntax
Description
Instructions
Example
Related
Commands
Purpose
Command Modes
Syntax
Syntax
Description
<ipv6-address>
<hardware-address>
This command is supported after the platform version 4.6.02.
The nd6 add command is used to create a static entry in the
neighbor cache list. As the interface address is also added into the
neighbor cache list in local system, the nd6 add command can
not overwrite the address of local interface.
The entry labeled "static" in the neighbor cache list indicates that it
is valid for ever, and its status is "reachable". The priority of static
entries is higher than that of dynamic ones. That is, if there is a
dynamic neighbor cache entry with the same address, this com-
mand will overwrite the static entry. Contrarily, dynamic entries
learned through the neighbor discovery protocol cannot be added
successfully if there is such entry.
This example describes how to add a static neighbor cache entry
on the fei_3/1 interface, with the destination address 4ffe::2, and
hardware address 00:01:00:02:00:03.
ZXR10(config)#int fei_3/1
ZXR10(config-if)#nd6 add 4ffe::2 0001.0002.0003
show nd6 cache
clear nd cache

nd6 delete

nd6 delete

Use this command to delete an entry in the neighbor cache list
in the interface configuration mode. The entry can be static or
dynamic.
Interface configuration
nd6 delete <ipv6-address>
<ipv6-address>
Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 IPv6 Basic Protocols
Destination address in the neighbor cache
list. It follows RFC2373, It is represented by
breaking it up into eight 16–bit segments.
Each segment is separated by colons. The
simplified format supported by RFC2373 can
be adopted
Hardware address corresponding to the
destination address in the neighbor cache
list. It is the 48-bit value in the format
of XXXX.XXXX.XXXX. It is represented by
breaking it up into 3 16–bit segments. Each
segment is separated by dots
Destination address in the neighbor cache
list. It follows RFC2373, It is represented by
breaking it up into eight 16–bit segments.
Each segment is separated by colons. The
simplified format supported by RFC2373 can
be adopted.
27