cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
430
Views
0
Helpful
1
Replies

6to4 anycast crashing 1812 router regularly

chrohmann
Level 1
Level 1

Hello,

I setup IPv6 anycast (client) (RFC 3068) on my 1812 router. The router is using a pppoe dialer 1 via vlan 10 (FTTB-network that uses VLANs between vdsl-modem and IAD).

Here you go with the config:

--- cut ---

interface FastEthernet2

description WAN-link (VDSL Modem)

switchport mode trunk

interface Vlan1

ip address 192.168.xxx.254 255.255.255.0

ip nat inside

ip virtual-reassembly

ipv6 address localnet ::1:0:0:0:1/64

ipv6 nd prefix default 180 120

ipv6 nd ra interval 10

!

interface Vlan10

no ip address

pppoe enable group global

pppoe-client dial-pool-number 1

!

ipv6 unicast-routing

ipv6 general-prefix localnet 6to4 Dialer1

ipv6 inspect name ipv6inspect tcp

ipv6 inspect name ipv6inspect udp

ipv6 inspect name ipv6inspect icmp

multilink bundle-name authenticated

vpdn enable

interface Tunnel64

description IPv6 6to4 tunnel

no ip address

no ip redirects

ipv6 enable

ipv6 traffic-filter no-ipv6-inbound in

ipv6 mtu 1472

ipv6 inspect ipv6inspect out

tunnel source Dialer1

tunnel mode ipv6ip 6to4

tunnel path-mtu-discovery

!

interface Dialer1

ip ddns update hostname HOSTNAME.dyndns.org

ip ddns update DynDNS

ip address negotiated

no ip redirects

no ip proxy-arp

ip mtu 1452

ip nat outside

ip virtual-reassembly

encapsulation ppp

ip route-cache flow

ip tcp adjust-mss 1452

dialer pool 1

dialer vpdn

dialer-group 1

no cdp enable

ppp authentication pap callin

ppp pap sent-username <A HREF="mailto:<A HREF="mailto:USERNAME@PROVIDER.TLD">USERNAME@PROVIDER.TLD</A>"><A HREF="mailto:USERNAME@PROVIDER.TLD">USERNAME@PROVIDER.TLD</A></A> password 0 PASSWORD

ppp ipcp dns request

!

no ip forward-protocol nd

ip route 0.0.0.0 0.0.0.0 Dialer1

ip nat inside source list 1 interface Dialer1 overload

ipv6 route ::/0 2002:C058:6301::

ipv6 access-list no-ipv6-inbound

deny ipv6 any any

--- cut ---

The thing is that everything just works just as expected. IPv6 RA (router solicitations) just appear after the tunnnel 64 is up and IPv6 internet can be used. After a while (I guess when the dialer needs to redial) this appears in the log:

--- cut ---

%DIALER-6-UNBIND: Interface Vi2 unbound from profile Di1

%LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down

%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down

%LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel64, changed state to down

%DIALER-6-BIND: Interface Vi2 bound to profile Di1

%LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up

%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up

%LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel64, changed state to up

%IP-3-DESTHOST: src=xx.xx.xx.xx, dst=0.0.0.0, NULL desthost -Process= "IPv6 IDB", ipl= 4, pid= 210, -Traceback= 0x808D0CE4 0x80CCD37C 0x80CCF1A4 0x80CCF964 0x80CCF9BC 0x81726BFC 0x80065370 0x81F253F4 0x81F26DC4 0x81E2FB84 0x81E063C8 0x81E0664C 0x81DF88A8 0x81DF8CD0 0x81DFE514 0x81DFBB00

%IP-3-DESTHOST: src=xx.xx.xxx.xx, dst=0.0.0.0, NULL desthost -Process= "IPv6 IDB", ipl= 4, pid= 210, -Traceback= 0x808D0CE4 0x80CCD37C 0x80CCF1A4 0x80CCF964 0x80CCF9BC 0x81726BFC 0x80065370 0x81F253F4 0x81F26DC4 0x81E2FB84 0x81E063C8 0x81E0664C 0x81DF88A8 0x81DF8CD0 0x81DFE514 0x81DFBB00

%IP-3-DESTHOST: src=xx.xx.xx.xx, dst=0.0.0.0, NULL desthost -Process= "MLD", ipl= 4, pid= 212, -Traceback= 0x808D0CE4 0x80CCD37C 0x80CCF1A4 0x80CCF964 0x80CCF9BC 0x81726BFC 0x80065370 0x81F253F4 0x81F26DC4 0x81E2FB84 0x81E063C8 0x81E08728 0x81E30A2C 0x81E10CD4 0x81E10D84 0x81E1064C

%IP-3-DESTHOST: src=xx.xx.xx.xx, dst=0.0.0.0, NULL desthost -Process= "MLD", ipl= 4, pid= 212, -Traceback= 0x808D0CE4 0x80CCD37C 0x80CCF1A4 0x80CCF964 0x80CCF9BC 0x81726BFC 0x80065370 0x81F253F4 0x81F26DC4 0x81E2FB84 0x81E063C8 0x81E08728 0x81E30A2C 0x81E10CD4 0x81E10D84 0x81E1064C

--- cut ---

Those entries are there everytime the dialer goes down and up again. The only way to gain connectivity back it by booting the router.

IOS: c181x-advipservicesk9-mz.124-11.XW9.bin

1 Reply 1

Laurent Aubert
Cisco Employee
Cisco Employee

Hi,

Only the TAC will be able to analyse those logs and help you to find out the root cause of this issue.

HTH

Laurent.

Review Cisco Networking products for a $25 gift card