04-25-2011 10:32 PM - edited 03-01-2019 05:26 PM
Have been banging my head against a wall after somehow losing the ability for prefix delegation after moving from an 877 -> 887.
"ipv6 dhcp" no longer works but documentation for the feature at http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-dhcp_ps10591_TSD_Products_Configuration_Guide_Chapter.html#wp1054045 shows it should still be there.
I assume that im configuring in the wrong order and that the command won't work without a specific configuration but no idea what so far.
Below is a quick example.
internets(config)#int di0
internets(config-if)#ipv6 dhcp
^
% Invalid input detected at '^' marker.
internets(config-if)#ipv6 ?
IPv6 interface subcommands:
address Configure IPv6 address on interface
cef Cisco Express Forwarding for IPv6
enable Enable IPv6 on interface
inspect Apply inspect name
mode Interface mode
mtu Set IPv6 Maximum Transmission Unit
nat Enable IPv6 NAT on interface
nd IPv6 interface Neighbor Discovery subcommands
policy Enable IPv6 policy routing
redirects Enable sending of ICMP Redirect messages
rip Configure RIP routing protocol
traffic-filter Access control list for packets
unnumbered Preferred interface for source address selection
unreachables Enable sending of ICMP Unreachable messages
verify Enable per packet validation
virtual-reassembly IPv6 Enable Virtual Fragment Reassembly
Solved! Go to Solution.
04-26-2011 05:31 AM
The problem may be related to which feature licenses are activated on the box.
Check the result of the command "show license feature" and check whether datak9 is enabled.
If it is not, this would certainly cause you a problem like this.
Cheers, Gustavo
04-26-2011 10:04 AM
Sorry for that...
In such cases, removing the "partner" string from the URL may solve the problem...
Could you please try to access http://www.cisco.com/en/US/docs/routers/access/sw_activation/SA_on_ISR.html and see if it works?
Cheers, Gustavo
04-26-2011 12:49 AM
Hi,
I suppose you want this interface to be a dhcpv6 client, then the command is ipv6 address dhcp as per the link you provided.
What exactly do you want to achieve on this router: dhcpv6 server or client?
Regards.
Alain.
04-26-2011 08:48 AM
I want it to configure it as a dhcp client, correct.
The attached document mentions "ipv6 address dhcp" but nothing about delegation of a prefix and does not support rapid-commit.
In regards to the licensing the output is shown below.
internets#sh license feature
Feature name Enforcement Evaluation Subscription Enabled
advipservices yes yes no no
advsecurity yes yes no yes
advsecurity_npe no no no no
ios-ips-update yes yes yes no
WAAS_Express yes yes no no
SSL_VPN yes yes no no
Cellular_WAN yes yes no no
04-26-2011 09:20 AM
Fature navigator indicates that the feature is supported.
I still think this problem is related to feature set / technology pack not being enabled.
Get an evaluation license for advanced ip services and enable it on your router. I would bet that it will work after this.
If this is the problem, you'd have to buy a permanent license to use it longer than the evaluation period.
For more information, visit the page http://www.cisco.com/en/US/partner/docs/routers/access/sw_activation/SA_on_ISR.html
Cheers, Gustavo
04-26-2011 10:00 AM
This leads into a program I've had before with the Cisco site, getting a login with the correct permissions.
Got no idea where to start with that and my current login doesn't have permission to get to that page or the page to request an evaluation license.
04-26-2011 10:04 AM
Sorry for that...
In such cases, removing the "partner" string from the URL may solve the problem...
Could you please try to access http://www.cisco.com/en/US/docs/routers/access/sw_activation/SA_on_ISR.html and see if it works?
Cheers, Gustavo
04-26-2011 11:01 AM
I enabled advipservices and reloaded the router and the command is now available.
Connection is not working in dual stack but that's another issue altogether, thanks for the very helpful and detailed answers guys.
04-26-2011 11:11 AM
In a lab environment I've worked with recently I've used the configurations below:
interface GigabitEthernet0/0
no ip address
duplex auto
speed auto
!
interface GigabitEthernet0/0.1
encapsulation dot1Q 101
pppoe enable group global
pppoe-client dial-pool-number 1
!
interface GigabitEthernet0/1
description CONECTED TO W2K-2008
ip address 15.15.15.2 255.255.255.0
duplex auto
speed auto
ipv6 address PREFIX1 ::1:0:0:0:1/64
!
interface Dialer1
ip address negotiated
ip nat outside
ip virtual-reassembly
encapsulation ppp
dialer pool 1
dialer idle-timeout 0
dialer persistent
ipv6 address autoconfig default
ipv6 dhcp client pd PREFIX1
ppp chap hostname cisco
ppp chap password 0 cisco
ppp ipcp route default
WAN interface was gig0/0.1 (VLAN 101) and LAN interface was gig0/1.
HTH, Gustavo
04-26-2011 11:39 AM
Looks like the problem is that the same prefix is trying to be assigned to the router as well as to the LAN.
Apr 26 18:33:32.671: %IPV6_ADDRESS-3-ADDRESS_CFG: 2001:44B8:7395:CA20::1/64 can not be configured on Vlan1, 2001:44B8:7395:CA20::1/64 is in use on ATM0
04-26-2011 11:54 AM
What is the configuration of ATM0?
Did you check what are you receiving from DHCP-PD with debug commands (debug ipv6 dhcp)?
Did you also check what are you receiving in ra messages with debug commands (debug ipv6 nd)?
Cheers, Gustavo
04-26-2011 08:16 PM
ATM configuration
interface ATM0
description --- ADSL ---
no ip address
no atm ilmi-keepalive
ipv6 address NODE-PD ::1/64
ipv6 enable
pvc 8/35
tx-ring-limit 3
encapsulation aal5snap
protocol ppp dialer
dialer pool-member 1
This is the output from debugging on na and DHCP
Apr 27 03:09:06.339: ICMPv6-ND: Create Static Neighbour FE80::226:99FF:FE61:4b00 on Dialer0
Apr 27 03:09:06.339: ICMPv6-ND: DELETE -> REACH: FE80::226:99FF:FE61:4b00
Apr 27 03:09:07.219: IPv6 DHCP: Sending SOLICIT to FF02::1:2 on Dialer0
Apr 27 03:09:07.243: IPv6 DHCP: Received REPLY from FE80::226:99FF:FE61:4b00 on Dialer0
Apr 27 03:09:07.243: IPv6 DHCP: Adding server FE80::226:99FF:FE61:4b00
Apr 27 03:09:07.243: IPv6 DHCP: Processing options
Apr 27 03:09:07.243: IPv6 DHCP: Adding prefix 2001:44B8:7395:bb20::/60 to NODE-PD
Apr 27 03:09:07.243: IPv6-Addrmgr-ND: DAD request for 2001:44B8:7395:bb20::1 on ATM0
Apr 27 03:09:07.243: IPv6-Addrmgr-ND: DAD: 2001:44B8:7395:bb20::1 is unique.
Apr 27 03:09:07.243: %IPV6_ADDRESS-3-ADDRESS_CFG: 2001:44B8:7395:bb20::1/64 can not be configured on Vlan1, 2001:44B8:7395:bb20::1/64 is in use on ATM0
Apr 27 03:09:07.243: IPv6 DHCP: T1 set to expire in 1800 seconds
Apr 27 03:09:07.243: IPv6 DHCP: T2 set to expire in 2880 seconds
Apr 27 03:09:07.243: IPv6 DHCP: Configuring DNS server 2001:44B8:1::6
Apr 27 03:09:07.243: IPv6 DHCP: Configuring DNS server 2001:44B8:2::6
Apr 27 03:09:07.243: IPv6 DHCP: Configuring domain name
Apr 27 03:09:07.243: IPv6 DHCP: Client provided option DOMAIN-LIST (len 0) is invalid
Apr 27 03:09:07.243: IPv6 DHCP: DHCPv6 changes state from SOLICIT to OPEN (REPLY_RECEIVED) on Dialer0
Apr 27 03:09:08.403: ICMPv6-ND: Sending RS on Dialer0
Apr 27 03:09:08.431: ICMPv6-ND: Received RA from FE80::226:99FF:FE61:4b00 on Dialer0
Apr 27 03:09:08.431: ICMPv6-ND: Selected new default router FE80::226:99FF:FE61:4b00 on Dialer0
Apr 27 03:09:08.431: ICMPv6-ND: Installed default to FE80::226:99FF:FE61:4b00 on Dialer0
Apr 27 03:09:08.431: IPv6-Addrmgr-ND: DAD request for 2001:44B8:66:8638:5A8D:9FF:FEA4:8CC8 on Dialer0
Apr 27 03:09:08.431: ICMPv6-ND: Sending NS for 2001:44B8:66:8638:5A8D:9FF:FEA4:8FC8 on Dialer0
Apr 27 03:09:08.431: ICMPv6-ND: Autoconfiguring 2001:44B8:66:8638:5A8D:9FF:FEA4:8FC8 on Dialer0
Apr 27 03:09:08.431: ICMPv6-ND: Allocate ND config on Dialer0
Apr 27 03:09:08.431: ICMPv6-ND: O bit set; checking stateless DHCP
Apr 27 03:09:09.431: IPv6-Addrmgr-ND: DAD: 2001:44B8:66:8638:5A8D:9FF:FEA4:8FC8 is unique.
Apr 27 03:09:09.431: ICMPv6-ND: Sending NA for 2001:44B8:66:8638:5A8D:9FF:FEA4:8FC8 on Dialer0
Apr 27 03:11:32.387: ICMPv6-ND: Request to send RA for FE80::5A8D:9FF:FEA4:8FC8
Apr 27 03:11:32.387: ICMPv6-ND: Sending RA from FE80::5A8D:9FF:FEA4:8FC8 to FF02::1 on Vlan1
Apr 27 03:11:32.387: ICMPv6-ND: MTU = 1500
04-27-2011 02:56 PM
Interfaces vlan1 and ATM0 have the same ipv6 address configuration...
ipv6 address NODE-PD ::1/64
You've received 2001:44B8:7395:bb20::/60 as delegated prefix and you can break it down among interfaces at your router...
Apr 27 03:09:07.243: IPv6 DHCP: Adding prefix 2001:44B8:7395:bb20::/60 to NODE-PD
You can break it into 16 separate /64 prefixes and assign it to the interfaces...
The first one is being assigned to ATM0:
Apr 27 03:09:07.243: IPv6-Addrmgr-ND: DAD request for 2001:44B8:7395:bb20::1 on ATM0
You can set the next one to vlan1 with the command below:
int vlan1
ipv6 addr NODE-PD 1:0:0:0:1/64
Cheers, Gustavo
04-28-2011 10:48 AM
I talked to one of the guys I work with who has a bit of Cisco knowledge about how our IPv6 network operates and he suggested removing the IPv6 information from the atm0 interface.
Now online with dual stack with no issues!
Thanks to all involved for their detailed feedback on this it's been a great help since I have really only been learning by myself previously.
One more client online for World IPv6 day
04-26-2011 05:31 AM
The problem may be related to which feature licenses are activated on the box.
Check the result of the command "show license feature" and check whether datak9 is enabled.
If it is not, this would certainly cause you a problem like this.
Cheers, Gustavo
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide