Troubleshooting IPv4 only DSL modem disconnect in dual-stack environment

Available Languages

Download Options

  • PDF     (3.4 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (74.5 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (68.7 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:September 15, 2016
Document ID:200691

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Introduction

This document describes a solution to recover DSL modems, IPv4 only in dual-stack environement, disconnected while it terminates on ASR1000 series router.

Problem

DSL modems disconnected were due to missing PPP keep-lives after enabled IPv6(IPv6CP) on LNS device.

ASR1000 as LNS is constantly sending out IPv6CP messages to CPE device. This is the behaviour as per RFC 1661. It tries to negotiate with its peer; if the peer cannot understand IPv6CP. The peer should send PROTREJ, which LNS will not try to negotiate IPV6CP.

Such constant IPv6CP messages can cause legacy IPv4-only modems to stop sending keep-alives to the LNS, resulting in session disconnection.

Solution

You can stop the constant IPv6CP messages via the following configuration on Virtual-Template interface.

  1. ppp ncp passive ipv6cp

# LNS will negotiate ipv6 only if initiated by client.

Alternative option:

  1. ppp ncp override local  

#This command tracks attributes received in authorization from RADIUS, verify the permitted Network Control Program (NCP), reject the current NCP negotiation, and override the local dual-stack configuration

TAC Authored

Contributed by Cisco Engineers

  • Frederick Kam
    Cisco TAC Engineer

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products