Brocade BigIron RX Series Configuration Guide - Manual (Page 1268)

1190 BigIron RX Series Configuration Guide
53-1002484-04
Configuring static neighbor entries
44
Configuring static neighbor entries
In some special cases, a neighbor cannot be reached using the neighbor discovery feature. In this
situation, you can add a static entry to the IPv6 neighbor discovery cache, which causes a neighbor
to be reachable at all times without using neighbor discovery. (A static entry in the IPv6 neighbor
discovery cache functions like a static ARP entry in IPv4.)
For example, to add a static entry for a neighbor with the IPv6 address 3001:ffe0:2678:47b and
link-layer address 0004.6a2b.8641 that is reachable through Ethernet interface 3/1, enter the
following command.
BigIron RX(config)# ipv6 neighbor 3001:ffe0: :2678:47b ethernet 3/1
0004.6a2b.8641
Syntax: [no] ipv6 neighbor <ipv6-address> ethernet <port> | ve <ve-number> [ethernet <port>]
<link-layer-address>
The <ipv6-address> parameter specifies the address of the neighbor.
The ethernet | ve parameter specifies the interface through which to reach a neighbor. If you
specify an Ethernet interface, specify the port number of the Ethernet interface. If you specify a VE,
specify the VE number and then the Ethernet port numbers associated with the VE. The link-layer
address is a 48-bit hardware address of the neighbor.
If you attempt to add an entry that already exists in the neighbor discovery cache, the software
changes the already existing entry to a static entry.
To remove a static IPv6 entry from the IPv6 neighbor discovery cache, use the no form of this
command.
Limiting the number of hops an IPv6 packet can traverse
By default, the maximum number of hops an IPv6 packet can traverse is 64. You can change this
value to between 1 – 255 hops. For example, to change the maximum number of hops to 70, you
can enter the following command.
BigIron RX(config)# ipv6 hop-limit 70
Syntax: [no] ipv6 hop-limit <number>
The number of hops can be from 1 – 255.
QoS for IPv6 traffic
Configuring QoS for IPv6 traffic is generally the same as it is for IPv4 traffic. The QoS policies you
configure on the Brocade device apply to both incoming IPv6 and IPv4 traffic. ACLs can be used to
perform QoS for IPv6 traffic:
• dscp
• fragments
• priority-force
• priority-mapping
• source routing