No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade
Knowledge Base

FAQ--Why the direct connected IPv6 address cannot ping under sub-interfaces

Publication Date:  2015-11-19  |   Views:  215  |   Downloads:  0  |   Author:  m00515467  |   Document ID:  EKB1000090118

Contents

Issue Description

Two AR1200 connected to each other directly with the same segment IPV6 address ,under the physical interfaces the PING test is successful, 

but under the sub-interfaces the PING test fail, The configurations are below:

in AR1:

interface GigabitEthernet0/0/1.200        

 dot1q termination vid 200

 ipv6 enable

 ipv6 address 3000::6AA8:28FF:FE4B:375E/64

 ipv6 address auto link-local

 ipv6 address auto global

in AR2:

interface GigabitEthernet0/0/1.200        

 dot1q termination vid 200

 ipv6 enable

 ipv6 address  3000::1/64

 ipv6 address auto link-local

 ipv6 address auto global

Solution

Under the sub-interface, add the command :ipv6 nd ns multicast-enable

A QinQ or a dot1q termination sub-interface on a routing device can send NS multicast packets to actively learn ND entries or respond to NS packets to passively learn ND entries.When a QinQ or a dot1q termination sub-interface needs to send multicast NS packets to learn ND entries but there is no corresponding ND entry, you need to run this command to enable a QinQ or a dot1q termination sub-interface to send NS multicast packets.