IPv6 address allocation

I've got a best practices question.
We're planning our transition to IPv6. We've gone to ARIN and aquired a /48 for the company. My question is about the best way to manage that space.
Our company already has one a second office location (which is international) in addition to our corporate offices. I expect we will have more within the next couple of years. I can allocate pieces of our /48 to these locations (trying to plan careful to support route aggregation) or I can have each of our international locations get their own /48 from their respective registries.
What's the intent about the best way to handle this?
Thx
Patrick

Hi Patrick,
before jumping to provide an answer I would like you to consider the nature of the network you are building and whether or not you will be using own dedicated links or using the Internet as transmission infrastructure.
In the first case you own provider independent IPv6 addressing could be a good idea if you run BGP. This also would allow you to be multihomed in different countries and could also become a transit AS.
But if you only are forwarding own traffic and have a couple of connection in different countries with stable and reputable ISPs maybe the only thing you need is provider assigned space for each location and you do not even need to run BGP only an IGP to prevent your internal traffic from spilling on the Internet. This would prevent rerouting of traffico from a different link to a network with a failed ISP connection.
You might also consider provider independent address space assigned by RIR in the country where you have your subsidiaries and use BGP to advertise the whole address space to the entire world and achieve redundancy.
Fact is more parameters are needed to answer you question:
Are you running BGP now (do you have an AS number)
Are you (or willing to be) a transit network
Are you looking for multihoming (in a single RIR area or multiple)
How much money are investing to obtain resilience and reliability.
I hope this question will help you better define your problem
Cheers
Fabio

Similar Messages

IPv6 Addressing Point to Point Links in the enterprise

For an enterprise, it doesn't seem to make sense to use Global addressing for point to point, transit-only links and loopbacks.
Link-local only addressing breaks debugging tools like traceroute, DNS, etc.
Is Unique Local the correct choice for this?
I've searched quite a bit and I've not found a lot of discussion about scope selection for point to point links. Some RFCs such as 6164 imply Global scope vs Unique Local scope usage is a preference. Most discussions of point to point addressing focus on bit length. I'm assuming this means design concerns are agnostic toward scope selection.
Is anyone aware of documentation I've missed or have any recommendations in this area?
If ULA was the correct choice, address hierarchy might look like this:
DataNetwork1 -- Router1 -- ULA.1.1 -- Link -- ULA1.2 -- Agg Router -- Core
DataNetwork2 -- Router2 -- ULA.2.1 -- Link -- ULA2.2 -- Agg Router /
DataNetwork3 -- Router3 -- ULA.3.1 -- Link -- ULA3.2 -- Agg Router /
The network core would have summarized entries for DataNetwork[1|2|3] and ULA[1|2|3]. IE, there would be a Global hierarchy and a ULA hierarchy.

Scott,
Let me break this down into some categories for you.
Address selection:
I believe that best practice is to use Global Unicast Addressing everywhere (coupled with a proper security policy at your edge). ULA was a compromise for Site Local never being properly defined and whilst it can be used in the same way as GUA I don't believe it is worth it. Irrespective of what you use (GUA or ULA), subject to your security and routing policy traceroute will work from both ends (e.g. you tracing out, someone tracing in)
Address masking:
The general rule of thumb is that you allocate /64s to eveything and then mask down to the appropriate mask for the function you are expecting (P.S. Forget everything you learnt about IPv4 address conservation). If you are using /127 masks then in theory every p2p link in your network is either a 0 (::) or a 1 (::1)
e.g.
traceroute HostB:
1     2001:1234:abcd:1::1
2     2001:1234:abcd:2::1
3     2001:1234:abcd:3::1
4     2001::4:10
The only exception to this is loopbacks, you can sequentially allocate /128s from the same /64 block
NOTE: /127 support is recent and may not be supported by some vendors, in this case use /126 masking (same as you would use /30s in IPv4)
If you have a /48 ( a normal enterise allocation) or larger then this should not be an issue ( you have access to 65536 x /64s) the only reason you would consider ULA for infrastructure numbering is because you have a small IPv6 pool. I would still argue you should get more IPv6 addresses than use ULA.
I hope this helps
Cheers

IPv6 Address Management and Security Questions

I'm trying to draft an IPv6-based version of our location's current routing configuration in anticipation of when our ISP will finally roll it out, and address management has been giving me the biggest headache - ironic, considering IPv6 was supposed to simplify address allocation.
My first config draft was made assuming that I would be getting a static /56 or /60 prefix from the ISP, and I was just going to insert the prefix into my DHCP pools and there would be no issues. That was before reading around and discovering that some ISPs are considering prefix delegation (PD) for both residential and business accounts instead of static blocks. Now I have questions about how to stick as close to the current IPv4 configuration as possible.
For the PD scenario, what I am looking at now are two addresses ranges for each network - a ULA /120 space that I want to control using stateful DHCPv6, and the global space which can be /64 and auto-configured. That way there will be a "private" address space for internal routing in the event of a prefix change or an extended outage. But I'm not sure how the config should look for such a scenario. What I have drafted so far is this:
ipv6 dhcp pool DHCP6_INTERNAL
address prefix FDAB::1:0/120
domain-name whatever.net
dns-server FDAB::1:1
ipv6 dhcp pool DHCP6_DMZ-WIFI
address prefix FDAB::2:0/120
domain-name guest.whatever.net
dns-server FDAB::2:1
interface GigabitEthernet0
description WAN-LINK
ipv6 enable
ipv6 address dhcp
no ipv6 unreachables
no ipv6 redirects
ipv6 flow ingress
ipv6 flow egress
ipv6 virtual-reassembly in
ipv6 nd autoconfig default-route
ipv6 dhcp client pd hint ::/56
ipv6 dhcp client pd ISP-PREFIX
zone-member security OUTSIDE
speed auto
duplex auto
no cdp enable
interface FastEthernet8.1
description VLAN_1-INTERNAL
encapsulation dot1Q 1 native
ipv6 enable
ipv6 address FDAB::1:1/120
ipv6 address ISP-PREFIX ::1:0:0:0:1/64
ipv6 flow ingress
ipv6 flow egress
ipv6 virtual-reassembly in
zone-member security INSIDE
ip tcp adjust-mss 1300
ipv6 dhcp server DHCP6_INTERNAL
ipv6 nd managed-config-flag
ipv6 nd other-config-flag
interface FastEthernet8.2
description VLAN_2-DMZ-WIFI
encapsulation dot1Q 2
ipv6 enable
ipv6 address FDAB::2:1/120
ipv6 address ISP-PREFIX ::2:0:0:0:1/64
ipv6 flow ingress
ipv6 flow egress
ipv6 virtual-reassembly in
zone-member security DMZ
ip tcp adjust-mss 1300
ipv6 dhcp server DHCP6_DMZ-WIFI
ipv6 nd managed-config-flag
ipv6 nd other-config-flag
Will this config work? By which I mean: will the DHCPv6 servers provide ULA addresses, and will SLAAC work for global address allocation? If not, what needs to be changed?
Also, another question. I found a few references to a prefix name (the "ISP-PREFIX") which can be used as part of a static IPv6 address on an interface, which is a good idea in case the prefix changes. But that brings up another concern - if the prefix changes, that will invalidate ACLs referencing the global addresses using the previous prefix. Is there anything similar to the prefix name string that can be used in ACLs to keep this from occurring?

DHCPv6-PD is not necessarily dynamic the same way as DHCP was with the public IPv4 addresses in the IPv4 world.
While the outside network (PPPoE, DHCPv6, anything) might be truly dynamic and changing with possibly every login session, the DHCPv6 delegated prefix might be tied to your login credentials or DHCPv6 client's DUID after the first connection. A bit like a DHCP lease reservation.
If that is the case, there is some possibility that your ISP will run reverse route injection, and will always route your "fixed" prefix to the currently active dynamic "outside" address.
Talk to your ISP and have them confirm that, once the PD'd /48 or /56 is initially assigned, it won't change, and that the same prefix will be delegated every time. Then you can treat it as if it were fully static, and you won't have to go down the ULA path.
I contacted one of our local ISPs, and they're doing it exactly that way: PPPoE for IPv4 and IPv6 (fully dynamic), and DHCPv6-PD with the /48 tied to the PPPoE login credentials. I might change to that ISP sooner or later.
With my current ISP, my IPv6 access is 6RD based. I get a /60, with my current public ipv4 address (by DHCP) embedded into those 60 bits. Readressing is bound to happen sooner or later, and it happens every so often, and it breaks my IPv6 ACLs.
I'm also looking for a way to write IPv6 ACLs with wildcard bits, not prefix/mask, so I can use them with ZBFW. So far, no sign of it.
A few more comments:
ULA addressing:
It may look tempting, plausible and intuitive to use dual global and ULA addressing.
I started this way as well. However, it turns out that Windows 7 has (had?) some issues with proper source address selection. The "longest common prefix" rule never seemed to work properly. In some cases, it would pick the global address to talk to ULA hosts, or stubbornly insist to use the ULA address to talk to an IPv6 internet host. It was a frustrating experience. Be sure to test this to the full extent (and back, and again and then some more) with every operating system you intend to use.
Using /120:
Be sure to test this as well, and very thoroughly. Subnet masks longer than /64 are sometimes called "uncharted territory" in IPv6. Longer subnet masks will break SLAAC, and there may be (embedded) devices that will not react benevolently to a subnet mask other than /64, or simply lack support for DHCPv6.
adjust-mss
I see you have "ip tcp adjust-mss 1300". While PMTUd may be mandatory with IPv6, I found it being broken already :-( . "ipv6 tcp adjust-mss .... " is now a separate command since IOS 15.4(1). I would suggest considering it, depending with your experience with PMTUd on IPv6.

IPv6 Address management

Hi,
we are at the stage where we are now looking to begin implementing IPv6 in the network. Not wanting to rush into this and end up with something unmanageable, our initial consideration is address management. Due to the large number of address' we are looking for advice on address management software, which seems to be a little thin on the ground.
So the question is, how are those people who are already using v6 managing their address allocations and what software is the most useable and popular? Value for money is also a consideration, any advice most welcome,
Thanks
Toby

Hi,
we are at the stage where we are now looking to begin implementing IPv6 in the network. Not wanting to rush into this and end up with something unmanageable, our initial consideration is address management. Due to the large number of address' we are looking for advice on address management software, which seems to be a little thin on the ground.
So the question is, how are those people who are already using v6 managing their address allocations and what software is the most useable and popular? Value for money is also a consideration, any advice most welcome,
Thanks
Toby

IPv6 Address in Internal Enterprise

Hello All,
I was looking at a Pilot deploment of IPv6 in our Labs.
I was little confused with rgards to what should I use as IPv6 address on Internal Network Infrastructure and hosts.
This is when I jumped across BRKRST-2301 where Shanon McFarland gives some idea on use of IPv6 in the internal.
So what it said is:
1. ULA Only -- Not recommended as NAT 66 solution does not exist <-- Can I use NPT Solution. But it would require same no. of GUA as well.
2. ULA + Global -- More problems with DNS, DHCP and SAS <-- Is this really that difficult ?
3. Global Only -- Recommended but security folks are not ready.     <-- I could even not convince some R&S folks for this!!! Even though I am convinced.
Apart from this, if i use a GUA which is not allocated to anyone internally & then NPT it while going outside.
I would like to know your thoughts and what would you recommend to do.
Maulik

Hi,
Reading many such things I think having GUA to end Hosts is best bet and that is what many people recommend to do.
I'm a bit confused since you say that all hosts will have 4 addresses but ULA must be used internally.
How will you dictate to every server and PC that they will only use their ULA addresses and ignore their global addresses for all internal communications? How will you monitor that this is actaully happening?
          <-- SAS should be used for this. Please refer this RFC and the problem statement it gives for SAS. But I am not sure every OS out there has implemented it correctly.
http://tools.ietf.org/html/rfc5220#page-12
You also state that all GUA addresses will be advertised to the Internet but these devices are not be reachable from the Internet. However you have just advertised these addresses to the Internet. I'm puzzled as to how you can achieve both conflicting requirements.
          <-- By this I actually meant that on all Infrastructure links and loopbacks of Routers we will use ULA, only end hosts will be given GUA and this GUA will be advertised into the routing protocol (exterior) for reachability. Both GUA and ULA in IGP. Advantage of this is that infrastructure network devices will not be reachable from Internet whatsoever.
I have had bad experiences with SP's in the past. Therefore I would not trust my IPv6 Security policy to them.
          <-- I agree, applying policies should be done at enterprise end must never trust SP.
For NAT 66, yes i am aware that it is still not available in major implementations, but some LB do that. So just was giving a thought.
http://tools.ietf.org/html/rfc6296
So I was just giving a thought:
1. To allocate ULA to Infrastructure Links and network devices.
2. Provide only GUA to end hosts. I too feel that should be the best approach.
Let me know on the 1st point. Thanks.

IPv6 address questions

I'm having trouble understanding IPv6 addresses. In IPv4 the CIDR slash notation means what subnet the address is in. But a /48 in IPv6 does not mean subnet. I have no idea what it means. For instance I've seen the address 2001:0:1:5::1/64, and I have no idea what the /64 means. Can someone explain it?
Link local address: it's not enough to put an FE80 to identify this kind of address, but for some reason, they decided to put FFFE in the middle of the ipv6 address. What were they thinking? Why do they need to identify this kind of address TWICE within the address, AND why couldn't they put the FFFE at the end or the beginning, but instead they put it right in the middle? WTF?
3 types of addresses? What why? with that many bits in an address there's no reason to have 3 of them. Theres enough for everyone.
Illogical allocation of bits. A global ip address reserves the last 64 bits for the host ip. This is equivalent to 18 quintillion hosts on ONE SUBNET! YEAH RIGHT! There's no way that's even remotely logical, feasible, or practical. The more I look at IPv6 notation, the more I think my 5th grader could have come up with a better design.
Also, why didn't they adopt the OSI model of addressing, like in ISIS. That has more than enough addresses for everyone.
Obviously i'm missing the point completely on IPv6. It sounds like the most unthoughtful pile of rubbish ever conceived. So can someone please direct me to a place or explain what the thought process was when creating this new addressing scheme?
bonus points: what happened to ipv5, and what was ipv1,ipv2,ipv3? I think the inventor should have called it IPv2000, because he really went overboard.

Hi Richee,
ISPs generally give ipv6 addresses to companies with /48 prefix length.
The company receiving this can create its own subnets within the /48 and /64 range.
The last 64 for bits of the address are generally used to insert the mac-address of the local interface when using stateless auto-configuration, but you can use it for subnetting as well, if you configure your addresses manually.
For the other questions I think this link could give you more info:
http://www.cisco.com/en/US/tech/tk872/tsd_technology_support_protocol_home.html
And one more little addition:
Nothing is perfect in this universe. Everything can be considered good or bad, it is just a question of viewpoint.
Try to look at ipv6 from both viewpoints. You will have surprises.
Cheers:
Istvan

Understanding IPv6 Address from RIR

Hi Folks,
I am very new to IPv6 and having some question need you guys advices as we are planning to integrate IPv6 to our existing network environment.
RIR allocated 2300:1480::/32 to us, but they said the assignment windows is 2300:1480::/48.
So what is the actual subnet to us? we don't quite understand the address assignment. How about 33-47 bits, it is belong to me or belong to RIR?
(Actual IPv6 address has been removed/modified)
Sent from Cisco Technical Support iPhone App

Hi Sean,
Further clarification with APNIC, this is their reply....
Does it meant, bit /33-47 is my main subnet And /48-/63 id customer's subnet and /64 is interface id or host in generally?
+++++
For your own infrastructure, you can assign the IP as per your
requirement. For your customers, you can only assign up to /48. If you
need to assign more then /48 to your customers, you need to submit your
APNIC second opinion request.
+++++
Sent from Cisco Technical Support iPhone App

Connect to server using IPv6 address in afp URL

I'm not sure whether this is the correct forum for this question, but does anyone know whether I can specify an IPv6 address in the "Connect to Server" dialog?
I've setup IPv6 over direct-wired ethernet between my MBP and Mini. Using ping6, I can ping one from the other (but only when I specify -I en0)
I've tried the following URLs:
afp://[fe80::0216:cbff:dead:beef]
afp://[fe80::0216:cbff:dead:beef%en0]
I think the problem might be because I don't have an IPv6 router between the two hosts.
Thanks.
MacBook Pro 15 2.0GHz Mac OS X (10.4.8) mini 1.83GHz

I have the same problem and for me it extends to everything from SSH to HTTP. I think that mac has a bug in it networking. I can't get it to work on any mac I've tried. Can your mini connect to your laptop?
I've been googling for 3 days and can't find any solution.
MBP Mac OS X (10.4.9)

Can't get ipv6 address assigned correctly.

I use NetworkManager and dhclient for auto-configuration but it has some weird problems.
When I boot up my laptop, I only have chance to get access to ipv6 network, when I fail, I tried to delete the connection in Network Management Settings, and then added a new profile, disable and then enable the network again. Sometimes it works well, but sometimes it failed to auto-config.
If I use the command:
$ ip -6 rout
then I'll get the following message:
unreachable fe80::/64 dev lo proto kernel metric 256 error -101
fe80::/64 dev wlan0 proto kernel metric 256
default via fe80::2e0:2ff:fe54:59 dev wlan0 proto static metric 1
every time the default gateway is configured well, sometimes the address the address is missed , and if I do the following:
$ ping6 -I wlan0 -c 4 fe80::2e0:2ff:fe54:59
It responses normally.
PING fe80::2e0:2ff:fe54:59(fe80::2e0:2ff:fe54:59) from fe80::1034:56ff:fe78:9124 wlan0: 56 data bytes
64 bytes from fe80::2e0:2ff:fe54:59: icmp_seq=1 ttl=64 time=5.32 ms
64 bytes from fe80::2e0:2ff:fe54:59: icmp_seq=2 ttl=64 time=6.64 ms
64 bytes from fe80::2e0:2ff:fe54:59: icmp_seq=3 ttl=64 time=10.6 ms
64 bytes from fe80::2e0:2ff:fe54:59: icmp_seq=4 ttl=64 time=3.60 ms
--- fe80::2e0:2ff:fe54:59 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 3.603/6.546/10.617/2.587 ms
do the following:
$ ip -6 addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
inet6 2001:250:4400:d000::161/128 scope global
valid_lft forever preferred_lft forever
inet6 fe80::1034:56ff:fe78:9124/64 scope link
valid_lft forever preferred_lft forever
I found I just sometimes can get the ipv6 address start with 2001:
If the address is assigned, then:
$ ping6 ipv6.google.com
PING ipv6.google.com(ipv6.google.com) 56 data bytes
^C
--- ipv6.google.com ping statistics ---
11 packets transmitted, 0 received, 100% packet loss, time 10008ms
response nothing!
Then I switch into Windows 7, if something like above happened, then I managed to set the MAC address to a random value such as 12-34-56-78-91-23, soon, the problem will be corrected, I'll get a new ipv6 address assigned by DHCPv6 server. If I switch back to arch, set the MAC address in NetworkManager, it didn't have function at most time, and the ipv6 address even won't change!
Can anyone help me with this problem?
by the way, I never get ipv6 address when I use dhcpcd.

bernarcher wrote:
Hello and welcome to the forums heliumhgy.
Just in case you are wondering where your post has been gone: The moderators board received this message from you:
I dont need tunnel to access to ipv6, My univ use dual-stack to get both ipv4 and v6 work around all campus.
This is because you inadvertently used the "Report" link. But don't worry this happens rather often.
Just cause I caught the glimpse of re-blabla, and mistaken it as reply
Last edited by heliumhgy (2012-11-29 03:16:11)

Is it normal?(NetworkManager applet's strange output & 3 IPv6 address)

1) label ppp0 appears in NetworkManager applet every time when I up vpn-connection
2) Also something strange with enp5s0. Output of "ip addr":
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 10:bf:48:20:61:a4 brd ff:ff:ff:ff:ff:ff
inet 10.0.122.144/8 brd 10.255.255.255 scope global dynamic enp5s0
valid_lft 9283sec preferred_lft 9283sec
inet6 2002:5be2:8e63:b:12bf:48ff:fe20:61a4/64 scope global noprefixroute dynamic
valid_lft 2592003sec preferred_lft 604803sec
inet6 fec0::b:12bf:48ff:fe20:61a4/64 scope site noprefixroute dynamic
valid_lft 2592003sec preferred_lft 604803sec
inet6 fe80::12bf:48ff:fe20:61a4/64 scope link
valid_lft forever preferred_lft forever
3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 00:08:ca:67:17:e9 brd ff:ff:ff:ff:ff:ff
9: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1400 qdisc pfifo_fast state UNKNOWN group default qlen 3
link/ppp
inet 91.226.141.81 peer 1.1.1.1/32 scope global ppp0
valid_lft forever preferred_lft forever
inet 91.226.141.81/32 brd 91.226.141.81 scope global ppp0
valid_lft forever preferred_lft forever
Is it normal that this interface has three IPv6 addresses?

Hi,
We are hitting the software bug and the bug ID is CSCsz56711
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsz56711
The issue is related to PCI componenet on the AP hardware and log that points to that is..
bsnInitRcbSlot: slot 0 has venus radio(UNSUPPORT)
The Replacement is the resolution and please contact your reseller or partner and if ur are the partner then RMA ids the resolution..
Lemme know if this answered ur question and please dont forget to rate the usefull posts!!
Regards
Surendra

Regarding the ipv6 address handling

Hi,
Are there any built-in functions in pl/sql for handling ipv6 addresses?
The functions similar to inet_ntop and inet_pton in c++ are available in pl/sql?

The closest I get to it is maybe dbms_network_acl_utility
http://download.oracle.com/docs/cd/E11882_01/appdev.112/e16760/d_networkacl_utl.htm#ARPLS67249
Subprogram Description
CONTAINS_HOST Function
Determines if the given host is equal to or contained in the given host, domain, or subnet
DOMAIN_LEVEL Function
Returns the domain level of the given host name, domain, or subnet
DOMAINS Function
For a given host, this function returns the domains whose ACL assigned is used to determine if a user has the privilege to access the given host or not.
EQUALS_HOST Function
Determines if the two given hosts, domains, or subnets are equal

How to verify if an IPV6 address entered in a textbox is valid ?

Hi,
How to verify if an IPV6 address entered in a text box is valid. I have a swing application. Until now we used only IPV4 address and we had a gui component with only four entries, which checked if the number entered is <= 255, so the user had to enter a correct address. Now with IPV6 there are IPV6 addresses, IPV4 mapped addresses, IPV6 zero compressed addresses and leading zeroes dropped kinds. We cannot supply a fix gui component.
So if I provide a textcomponent which accepts strings - how do i check if the ip addresses entered by the user is valid. Can I use INET6Address to do this ? is there a way ?
Thanks.

InetAddress.getByName(String host)
If it returns an Inet6Address without throwing an exception, I guess that would work.

IP phone not getting IPv6 address

Hi guys,
I am having trouble with receiving IPv6 address from my 2811 CME router that has been configured as a DHCPv6. Could you please help me what is wrong with my configuration below? Thank you.
Router#sh run
Building configuration...
Current configuration : 2327 bytes
! Last configuration change at 22:52:14 UTC Mon Feb 17 2014
version 15.1
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname Router
boot-start-marker
boot-end-marker
no aaa new-model
dot11 syslog
ip source-route
no ip cef
no ip domain lookup
ipv6 unicast-routing
ipv6 cef
ipv6 dhcp pool VOICE
address prefix 2001::/64
vendor-specific 9
suboption 1 address 2001::1
suboption 2 ascii "IP-Phone"
multilink bundle-name authenticated
voice-card 0
crypto pki token default removal timeout 0
license udi pid CISCO2811 sn FHK1213F0HN
redundancy
interface FastEthernet0/0
bandwidth 50
no ip address
duplex auto
speed auto
interface FastEthernet0/0.10
encapsulation dot1Q 10
ipv6 address 2001::1/64
ipv6 enable
ipv6 nd other-config-flag
ipv6 dhcp server VOICE
interface FastEthernet0/1
bandwidth 50
no ip address
duplex auto
speed auto
ip forward-protocol nd
no ip http server
no ip http secure-server
tftp-server flash:SCCP41.9-3-1SR2-1S.loads
tftp-server flash:cnu41.9-3-1ES13.sbn
tftp-server flash:cvm41sccp.9-3-1ES13.sbn
tftp-server flash:dsp41.9-3-1ES13.sbn
tftp-server flash:jar41sccp.9-3-1ES13.sbn
tftp-server flash:term41.default.loads
tftp-server flash:apps41.9-3-1ES13.sbn
tftp-server flash:mk-sccp.jar alias English_United_States/mk-sccp.jar
tftp-server flash:g3-tones.xml alias United_States/g3-tones.xml
control-plane
mgcp profile default
telephony-service
protocol mode dual-stack preference ipv6
max-ephones 5
max-dn 5
ip source-address 2001::1
cnf-file location flash:
load 7941 SCCP41.9-3-1SR2-1S.loads
max-conferences 8 gain -6
transfer-system full-consult
create cnf-files version-stamp Jan 01 2002 00:00:00
ephone-dn 1
number 1000
ephone-dn 2
number 2000
ephone-dn 3
number 7000
ephone 1
device-security-mode none
mac-address 0017.9406.FD55
type 7941
button 1:1
ephone 2
device-security-mode none
mac-address 0016.46F5.F08E
button 1:2
ephone 3
device-security-mode none
mac-address 0017.941D.BE05
type 7941
button 1:3
line con 0
logging synchronous
line aux 0
line vty 0 4
login
transport input all
scheduler allocate 20000 1000
end

Duplicate posts.
Go here: https://supportforums.cisco.com/thread/2267863

Port_based address Allocation

hi,
Can Port_based address Allocation is possible in cisco switch if possible kindly tell the switch model or any cisco / third party software reqiure.
pls help......

Hi All,We have a Cisco 897VAG-LTE and a 867VAE-K9.We need to enable DHCP on the router and assign an IP address to fa0/1 using the configuration below. A mac address reservation will not work as we will be swapping out the embedded device when repairs are required.Our supplier is using a C897VAMG-LTE-GA-K9 with c800-universalk9-mz.SPA.154-3.M1 software. They say the configuration is not working on their test router.At what level of IOS is this command supported; IPBase, Universal, Adv Ip Services? Cisco white papers do not specify this.How best do I approach this situation?Textip dhcp use subscriber-id client-idip dhcp subscriber-id interface-nameip dhcp excluded-address 10.36.1.1 10.36.1.20!ip dhcp pool DHCP-POOL network 10.36.1.0 255.255.255.0 default-router 10.36.1.254 reserved-only address 10.36.1.253 client-id "Fa0/1" ascii
This topic first appeared in the Spiceworks Community

Why do the connected devices to the router have the smae IPV6 address?

Hi,
Now I meet the issue
The operation steps on router (WRVS4400N):
1.Set the IP mode as Dual-stack IP and then save
2.Disable the IPV4 DHCP server
3.Use other deivces to connect the router.
The connected devices have the same IP address(2005:123:456:789::1),I am confused,why is it?
please help.
Thanks!

Hello,
The WRVS4400N is in fact assigning IPv6 addresses to all the devices connected to it, but the WRVS4400N does not show a table with the IPv6 addresses assigned to each device connected, it only shows the IPv4 addresses and the respective MAC address for each device. The IPv6 of the WRVS4400N is an aggregetable global unicast IPv6 address (See the image below)
If you go to Setup > LAN you will see that you cannot modify the prefix of the IPv6 address, all you can modify is the postifx and prefix length field (As you can see in the image below).
For more information about these fields and general IPv6 configuration, please refer to the article IPv6 Configuration on WRVS4400N Wireless-N Gigabit Security Routers
The only way you have to see the IPv6 address assigned to each device connected to the WRVS4400N is to check on each device the IPv6 address assigned. The WRVS4400N does not provide this information. You can see from the below picture the IPv6 address assigned to my computer. As you can see, the WRVS4400N assign the the computer the prefix 2002:c0a8::/6. Then you can see the actual IPv6 address which is 2002:c0a8:0:b182:e6a:9b0e:cdcf.
As you can see, the initial part (The prefix) remains the same, since these are the first 64 bits of the whole IPv6 address. The other 64 bits of the IPv6 address represents the interface ID, that is, the device that is connected to the WRVS4400N.
I hope you find this information helpful. If you have further questions, don't hesitate to ask.
Alejandro Moncada
SBCD Engineer
[email protected]

IPv6 address allocation

Similar Messages

Maybe you are looking for