Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

Example: Configuring IPv6 Interfaces and Enabling Neighbor Discovery

This example shows how to configure the router to send IPv6 neighbor discovery messages.

Requirements

In this example, no special configuration beyond device initialization is required.

Overview

In this example, all of the interfaces in the sample topology are configured with IPv6 addresses. If you plan to extend IPv6 functionality into your LAN, datacenter, or customer networks, you might want to use Stateless Address Auto-Configuration (SLAAC) and that means configuring router advertisements. SLAAC is an IPv6 protocol that provides some similar functionality to DHCP in IPv4. Using SLAAC, network hosts can autoconfigure a globally unique IPv6 address based on the prefix provided by a nearby router in a router advertisement. This removes the need to explicitly configure every interface in a given section of the network. Router advertisement messages are disabled by default, and you must enable them to take advantage of SLAAC.

To configure the router to send router advertisement messages, you must include at least the following statements in the configuration. All other router advertisement configuration statements are optional.

protocols {router-advertisement {interface interface-name {prefix prefix;}}}

To configure neighbor discovery, include the following statements. You configure router advertisement on a per-interface basis.

protocols {router-advertisement {interface interface-name {current-hop-limit number;default-lifetime seconds;(link-mtu | no-link-mtu);(managed-configuration | no-managed-configuration);max-advertisement-interval seconds;min-advertisement-interval seconds;(other-stateful-configuration | no-other-stateful-configuration);prefix prefix {(autonomous | no-autonomous);(on-link | no-on-link);preferred-lifetime seconds;valid-lifetime seconds;}reachable-time milliseconds;retransmit-timer milliseconds;virtual-router-only;}traceoptions {file filename <files number> <size maximum-file-size> <world-readable | no-world-readable>;flag flag;}}}

Figure 1 shows a simplified sample topology.

Figure 1: ICMP Router Discovery Topology

ICMP Router Discovery Topology

This example shows how to make sure that all of the IPv6 hosts attached to the subnets in the sample topology can auto-configure a local EUI-64 address.

CLI Quick Configuration shows the configuration for all of the devices in Figure 1. Step-by-Step Procedure describes the steps on Device R1.

Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.

Device R1

set interfaces fe-1/2/0 unit 1 description to-P2set interfaces fe-1/2/0 unit 1 family inet6 address 2001:db8:0:1::/64 eui-64set interfaces fe-1/2/1 unit 5 description to-P4set interfaces fe-1/2/1 unit 5 family inet6 address 2001:db8:0:5::/64 eui-64set interfaces fe-1/2/2 unit 9 description to-P3set interfaces fe-1/2/2 unit 9 family inet6 address 2001:db8:0:9::/64 eui-64set interfaces lo0 unit 1 family inet6 address 2001:db8::1/128set protocols router-advertisement interface fe-1/2/0.1 prefix 2001:db8:0:1::/64set protocols router-advertisement interface fe-1/2/1.5 prefix 2001:db8:0:5::/64set protocols router-advertisement interface fe-1/2/2.9 prefix 2001:db8:0:9::/64

Device R2

set interfaces fe-1/2/0 unit 2 description to-P1set interfaces fe-1/2/0 unit 2 family inet6 address 2001:db8:0:1::/64 eui-64set interfaces fe-1/2/1 unit 14 description to-P3set interfaces fe-1/2/1 unit 14 family inet6 address 2001:db8:0:14::/64 eui-64set interfaces fe-1/2/2 unit 21 description to-P4set interfaces fe-1/2/2 unit 21 family inet6 address 2001:db8:0:21::/64 eui-64set interfaces lo0 unit 2 family inet6 address 2001:db8::2/128set protocols router-advertisement interface fe-1/2/0.2 prefix 2001:db8:0:1::/64set protocols router-advertisement interface fe-1/2/1.14 prefix 2001:db8:0:14::/64set protocols router-advertisement interface fe-1/2/2.21 prefix 2001:db8:0:21::/64

Device R3

set interfaces fe-1/2/0 unit 10 description to-P1set interfaces fe-1/2/0 unit 10 family inet6 address 2001:db8:0:9::/64 eui-64set interfaces fe-1/2/1 unit 13 description to-P2set interfaces fe-1/2/1 unit 13 family inet6 address 2001:db8:0:14::/64 eui-64set interfaces fe-1/2/2 unit 17 description to-P4set interfaces fe-1/2/2 unit 17 family inet6 address 2001:db8:0:17::/64 eui-64set interfaces lo0 unit 3 family inet6 address 2001:db8::3/128set protocols router-advertisement interface fe-1/2/0.10 prefix 2001:db8:0:9::/64set protocols router-advertisement interface fe-1/2/1.13 prefix 2001:db8:0:14::/64set protocols router-advertisement interface fe-1/2/2.17 prefix 2001:db8:0:17::/64

Device R4

set interfaces fe-1/2/0 unit 6 description to-P1set interfaces fe-1/2/0 unit 6 family inet6 address 2001:db8:0:5::/64 eui-64set interfaces fe-1/2/1 unit 18 description to-P3set interfaces fe-1/2/1 unit 18 family inet6 address 2001:db8:0:17::/64 eui-64set interfaces fe-1/2/2 unit 22 description to-P2set interfaces fe-1/2/2 unit 22 family inet6 address 2001:db8:0:21::/64 eui-64set interfaces lo0 unit 4 family inet6 address 2001:db8::4/128set protocols router-advertisement interface fe-1/2/0.6 prefix 2001:db8:0:5::/64set protocols router-advertisement interface fe-1/2/1.18 prefix 2001:db8:0:17::/64set protocols router-advertisement interface fe-1/2/2.22 prefix 2001:db8:0:21::/64

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode in the Junos OS CLI User Guide .

To configure a IPv6 neighbor discovery:

  1. Configure the network interfaces.

    This example shows multiple loopback interface addresses to simulate attached networks.

    [edit interfaces]user@R1# set fe-1/2/0 unit 1 description to-P2user@R1# set fe-1/2/0 unit 1 family inet6 address 2001:db8:0:1::/64 eui-64
    user@R1# set fe-1/2/1 unit 5 description to-P4user@R1# set fe-1/2/1 unit 5 family inet6 address 2001:db8:0:5::/64 eui-64
    user@R1# set fe-1/2/2 unit 9 description to-P3user@R1# set fe-1/2/2 unit 9 family inet6 address 2001:db8:0:9::/64 eui-64
    user@R1# set lo0 unit 1 family inet6 address 2001:db8::1/128
  2. Enable neighbor discovery.
    [edit protocols router-advertisement]user@R1# set interface fe-1/2/0.1 prefix 2001:db8:0:1::/64user@R1# set interface fe-1/2/1.5 prefix 2001:db8:0:5::/64user@R1# set interface fe-1/2/2.9 prefix 2001:db8:0:9::/64

Results

From configuration mode, confirm your configuration by entering the show interfaces and show protocols commands. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

user@R1# show interfacesfe-1/2/0 {unit 1 {description to-P2;family inet6 {address 2001:db8:0:1::/64 {eui-64;}}}}fe-1/2/1 {unit 5 {description to-P4;family inet6 {address 2001:db8:0:5::/64 {eui-64;}}}}fe-1/2/2 {unit 9 {description to-P3;family inet6 {address 2001:db8:0:9::/64 {eui-64;}}}}lo0 {unit 1 {family inet6 {address 2001:db8::1/128;}}}
user@R1# show protocolsrouter-advertisement {interface fe-1/2/0.1 {prefix 2001:db8:0:1::/64;}interface fe-1/2/1.5 {prefix 2001:db8:0:5::/64;}interface fe-1/2/2.9 {prefix 2001:db8:0:9::/64;}}

If you are done configuring the device, enter commit from configuration mode.

Verification

To confirm that the configuration is working properly, perform this task:

Checking the Interfaces

Purpose

Verify that the interfaces are up, and view the assigned EUI-64 addresses.

Action

From operational mode, enter the show interfaces terse command.

user@R1> show interfaces terse
Interface               Admin Link Proto    Local                 Remote
fe-1/2/0               
fe-1/2/0.1              up    up   inet6    2001:db8:0:1:2a0:a514:0:14c/64
                                            fe80::2a0:a514:0:14c/64
fe-1/2/1.5              up    up   inet6    2001:db8:0:5:2a0:a514:0:54c/64
                                            fe80::2a0:a514:0:54c/64
fe-1/2/2.9              up    up   inet6    2001:db8:0:9:2a0:a514:0:94c/64
                                            fe80::2a0:a514:0:94c/64
lo0                    
lo0.1                   up    up   inet6    2001:db8::1     
                                            fe80::2a0:a50f:fc56:14c

Meaning

The output shows that all interfaces are configured with the IPv6 (inet6) address family. Each IPv6-enabled interface has two IPv6 addresses; one link-local address, and one global address. The global addresses match those shown in Figure 1. Junos OS automatically creates a link-local address for any interface that is enabled for IPv6 operation. All link-local addresses begin with the fe80::/64 prefix. The host portion of the address is a full 64 bits long and matches the link-local interface identifier. When an interface address is configured using the eui-64 statement, its interface identifier matches the interface identifier of the link-local address. This is because link-local addresses are coded according to the EUI-64 specification.

Pinging the Interfaces

Purpose

Verify connectivity between the directly connected interfaces.

Action

  1. Determine the remote router’s IPv6 interface address.

    On Device R2, run the show interfaces terse command for the interface that is directly connected to Device R1, and copy the global address into the capture buffer of your terminal emulator.

    user@R2> show interfaces fe-1/2/0.2 terse
    Interface               Admin Link Proto    Local                 Remote
fe-1/2/0.2              up    up   inet6    2001:db8:0:1:2a0:a514:0:24c/64
                                            fe80::2a0:a514:0:24c/64
  2. On Device R1, run the ping command, using the global address that you copied.
    user@R1> ping 2001:db8:0:1:2a0:a514:0:24c
    PING6(56=40+8+8 bytes) 2001:db8:0:1:2a0:a514:0:14c --> 2001:db8:0:1:2a0:a514:0:24c
16 bytes from 2001:db8:0:1:2a0:a514:0:24c, icmp_seq=0 hlim=64 time=20.412 ms
16 bytes from 2001:db8:0:1:2a0:a514:0:24c, icmp_seq=1 hlim=64 time=18.897 ms
16 bytes from 2001:db8:0:1:2a0:a514:0:24c, icmp_seq=2 hlim=64 time=1.389 ms

Meaning

Junos OS uses the same ping command for both IPv4 and IPv6 testing. The lack of any interior gateway protocol (IGP) in the network limits the ping testing to directly-connected neighbors. Repeat the ping test for other directly connected neighbors.

Checking the IPv6 Neighbor Cache

Purpose

Display information about the IPv6 neighbors.

After conducting ping testing, you can find an entries for interface addresses in the IPv6 neighbor cache.

Action

From operational mode, enter the show ipv6 neighbors command.

user@R1> show ipv6 neighbors
IPv6 Address                 Linklayer Address  State       Exp Rtr Secure Interface
2001:db8:0:1:2a0:a514:0:24c  00:05:85:8f:c8:bd  stale       546 yes no      fe-1/2/0.1  
fe80::2a0:a514:0:24c         00:05:85:8f:c8:bd  stale       258 yes no      fe-1/2/0.1  
fe80::2a0:a514:0:64c         00:05:85:8f:c8:bd  stale       111 yes no      fe-1/2/1.5  
fe80::2a0:a514:0:a4c         00:05:85:8f:c8:bd  stale       327 yes no      fe-1/2/2.9

Meaning

In IPv6, the Address Resolution Protocol (ARP) has been replaced by the Neighbor Discovery Protocol (NDP). The IPv4 command show arp is replaced by the IPv6 command show ipv6 neighbors. The key pieces of information displayed by this command are the IP address, the MAC (Link Layer) address, and the interface.

Verifying IPv6 Router Advertisements

Purpose

Confirm that devices can be added to the network using SLAAC by ensuring that router advertisements are working properly.

Action

From operational mode, enter the show ipv6 router-advertisement command.

user@R1> show ipv6 router-advertisement
Interface: fe-1/2/0.1
  Advertisements sent: 37, last sent 00:01:41 ago
  Solicits received: 0
  Advertisements received: 38
  Advertisement from fe80::2a0:a514:0:24c, heard 00:05:46 ago
    Managed: 0
    Other configuration: 0
    Reachable time: 0 ms
    Default lifetime: 1800 sec
    Retransmit timer: 0 ms
    Current hop limit: 64
    Prefix: 2001:db8:0:1::/64
      Valid lifetime: 2592000 sec
      Preferred lifetime: 604800 sec
      On link: 1
      Autonomous: 1
Interface: fe-1/2/1.5
  Advertisements sent: 36, last sent 00:05:49 ago
  Solicits received: 0
  Advertisements received: 37
  Advertisement from fe80::2a0:a514:0:64c, heard 00:00:54 ago
    Managed: 0
    Other configuration: 0
    Reachable time: 0 ms
    Default lifetime: 1800 sec
    Retransmit timer: 0 ms
    Current hop limit: 64
    Prefix: 2001:db8:0:5::/64
      Valid lifetime: 2592000 sec
      Preferred lifetime: 604800 sec
      On link: 1
      Autonomous: 1
Interface: fe-1/2/2.9
  Advertisements sent: 36, last sent 00:01:37 ago
  Solicits received: 0
  Advertisements received: 38
  Advertisement from fe80::2a0:a514:0:a4c, heard 00:01:00 ago
    Managed: 0
    Other configuration: 0
    Reachable time: 0 ms
    Default lifetime: 1800 sec
    Retransmit timer: 0 ms
    Current hop limit: 64
    Prefix: 2001:db8:0:9::/64
      Valid lifetime: 2592000 sec
      Preferred lifetime: 604800 sec
      On link: 1
      Autonomous: 1

Meaning

The output shows that router advertisements are being sent and received on Device R1’s interfaces, indicating that both Device R1 and its directly connected neighbors are configured to generate router-advertisements.

Tracing Neighbor Discovery Events

Purpose

Perform additional validation by tracing router advertisements.

Action

  1. Configure trace operations.
    [edit protocols router-advertisement traceoptions]user@R1# set file ipv6-nd-traceuser@R1# set traceoptions flag alluser@R1# commit
  2. Run the show log command.
    user@R1> show log ipv6-nd-trace
    Mar 29 14:07:16 trace_on: Tracing to "/var/log/P1/ipv6-nd-trace" started
Mar 29 14:07:16.287229 background dispatch running job ipv6_ra_delete_interface_config_job for task Router-Advertisement
Mar 29 14:07:16.287452 task_job_delete: delete background job ipv6_ra_delete_interface_config_job for task Router-Advertisement
Mar 29 14:07:16.287505 background dispatch completed job ipv6_ra_delete_interface_config_job for task Router-Advertisement
Mar 29 14:07:16.288288 ipv6_ra_iflchange(Router-Advertisement): ifl 0xb904378 ifl fe-1/2/2.9 104 change 0, intf 0xba140d8
Mar 29 14:07:16.288450 ipv6_ra_iflchange(Router-Advertisement): ifl 0xb904250 ifl fe-1/2/0.1 85 change 0, intf 0xba14000
Mar 29 14:07:16.288656 ipv6_ra_iflchange(Router-Advertisement): ifl 0xb9044a0 ifl fe-1/2/1.5 80 change 0, intf 0xba1406c
Mar 29 14:07:16.289293 ipv6_ra_ifachange(Router-Advertisement): ifa 0xba002bc fe80::2a0:a514:0:54c ifl fe-1/2/1.5 80 change 0, intf 0xba1406c
Mar 29 14:07:16.289358 -- nochange/add
Mar 29 14:07:16.289624 ipv6_ra_ifachange(Router-Advertisement): ifa 0xba00230 2001:db8:0:5:2a0:a514:0:54c ifl fe-1/2/1.5 80 change 0, intf 0xba1406c
Mar 29 14:07:16.289682 -- nochange/add
Mar 29 14:07:16.289950 ipv6_ra_ifachange(Router-Advertisement): ifa 0xba001a4 fe80::2a0:a514:0:14c ifl fe-1/2/0.1 85 change 0, intf 0xba14000
Mar 29 14:07:16.290009 -- nochange/add
Mar 29 14:07:16.290302 ipv6_ra_ifachange(Router-Advertisement): ifa 0xba00118 2001:db8:0:1:2a0:a514:0:14c ifl fe-1/2/0.1 85 change 0, intf 0xba14000
Mar 29 14:07:16.290365 -- nochange/add
Mar 29 14:07:16.290634 ipv6_ra_ifachange(Router-Advertisement): ifa 0xba003d4 fe80::2a0:a514:0:94c ifl fe-1/2/2.9 104 change 0, intf 0xba140d8
Mar 29 14:07:16.290694 -- nochange/add
Mar 29 14:07:16.290958 ipv6_ra_ifachange(Router-Advertisement): ifa 0xba00348 2001:db8:0:9:2a0:a514:0:94c ifl fe-1/2/2.9 104 change 0, intf 0xba140d8
Mar 29 14:07:16.291017 -- nochange/add
Mar 29 14:07:20.808516 task_job_create_foreground: create job ipv6 ra for task Router-Advertisement
Mar 29 14:07:20.808921 foreground dispatch running job ipv6 ra for task Router-Advertisement
Mar 29 14:07:20.809027 ipv6_ra_send_advertisement: sending advertisement for ifl 104 to ff02::1
Mar 29 14:07:20.809087 (4810916) sending advertisement for ifl 104
Mar 29 14:07:20.809170  ifa 0xba00348 2001:db8:0:9:2a0:a514:0:94c/64
Mar 29 14:07:20.809539  --> sent 56 bytes
Mar 29 14:07:20.809660 task_timer_reset: reset Router-Advertisement_ipv6ra
Mar 29 14:07:20.809725 task_timer_set_oneshot_latest: timer Router-Advertisement_ipv6ra interval set to 7:07
Mar 29 14:07:20.809772 foreground dispatch completed job ipv6 ra for task Router-Advertisement
 

Related Documentation

 

Published: 2012-06-13

Supported Platforms

 

Related Documentation

 

Published: 2012-06-13

Previous Page Next Page