This is the documentation for the 20.10 version. Looking for the documentation of the latest version? Have a look here.
For directly connected networks which operate at layer 2, TNSR will attempt to locate neighboring hosts via Address Resolution Protocol (ARP) for IPv4 or Neighbor Discover Protocol (NDP) for IPv6. In this way, TNSR can discover the hardware MAC address to which a packet will be delivered in these networks.
Static neighbor entries can override this dynamic behavior so that a specified IPv4 or IPv6 address is always associated with the same MAC address.
The command to specify a static neighbor takes the following form:
tnsr(config)# neighbor <interface> <ip-address> <mac-address> [no-adj-route-table-entry]
The parameters for this command are:
The interface on which this static entry will be placed.
This interface must support layer 2 (L2) data. Neighbors cannot be configured on interfaces which only support layer 3 (L3), such as
The IPv4 or IPv6 address for the static neighbor entry.
The MAC address to associate with the given IP address.
Do not create an adjacency route table entry.
For example, to add a static entry to map
126.96.36.199 to a MAC address of
00:11:22:33:44:55 on the interface
GigabitEthernet3/0/0, run this
tnsr(config)# neighbor GigabitEthernet3/0/0 188.8.131.52 00:11:22:33:44:55
To see the current table of known IPv4 and IPv6 neighbors, use the
neighbor [interface <if-name>] command.
In other products, this information may be referred to as the ARP table or NDP table.
tnsr# show neighbor Interface S/D IP Address MAC Address --------------------- --- ------------ ----------------- GigabitEthernet0/14/0 D 203.0.113.1 00:90:0b:37:a3:24 GigabitEthernet0/14/0 D 203.0.113.14 00:0d:b9:33:0f:71 GigabitEthernet3/0/0 S 184.108.40.206 00:11:22:33:44:55 GigabitEthernet3/0/0 D 10.2.0.129 00:0c:29:4c:b3:9b
This output can optionally be filtered by interface name.
S/D column shows if the entry is static (
S) or dynamic (