NS & NA  Work like ARP , DAD , when first host comes up it sends ICMPv6-ND (NS) and check for

DAD
, it if not received any response then it will advertise its address to ff02::1 by NA. (FF02::1  like
255.255.255.255 in Ipv4)
Ipv4 ARP is event driven , means router should ask for that …. But Ipv6 is unsolicitated.
Solitation is FF02::1:FF <Ipv4 add>
RS & RA  works like dhcp ,these messages, to learn the prefix, prefix length, and default
router.

Ip ipv4 first packet will be unreachable due to ARP but in case of ipv6 it won’t bcz address table is
populated when ipv6 is configured using DAD/icmpv6
IPv6 migration guide & IPv6 planning and designing : --

A combination of both native IPv4 and IPv6, better known as dual stack, if the WAN network supports IPv6, then
dual stack is again the recommend option. If not, then the solution is to use tunnels to connect the IPv6 islands over
IPv4.
Does your current hardware and infrastructure (routers, switches, load balancers, DNS, etc.) support IPv6?
if the intended deployment is new (no existing networks or equipment), you may want to consider an IPv6-only
deployment strategy. However, if the intended deployment augments an existing IPv4 network, then IPv4 and IPv6
coexistence must be assumed at the outset, and likely for many years.

1. Discovery  business requirements for the migration, including timing, as well as external considerations such as
regional address availability and government compliance.
2. Assessment  an organization lays out its technical requirements and determines how to best deploy the technology
with goals of minimizing disruption, facilitating troubleshooting, and containing implementation costs. various
deployment options, such as dual-stack or hybrid models.
3. Planning and Design 
 Dual-Stack Model :- In the dual-stack model, desktops, the campus, hosts within the data center, and any
connectivity to the outside world are both IPv4 and IPv6 enabled in most cases. Planning includes migration of
routers and switches to IPv6-capable Cisco IOS® Software releases and in some cases IPv6-capable hardware.

4) Developing a Detailed Design :- The detailed design includes the IPv6 addressing plan; physical connectivity
considerations, including WAN links and wireless LANs; creating and managing VLANs and their associated protocols; and
the routing infrastructure to include provider connectivity, high availability, multicast (if required), quality of service,
manageability, scalability, and performance.
Security
Security is a crucial consideration in IPv6 migration. IPv6 is not an update of IPv4 but an entirely new suite of
protocols, raising new security challenges. Because of these unknown risks, organizations should adequately
resource for such areas as firewall and intrusion prevention device readiness and IT expertise to properly identify
and remedy threats.

5) Implementation :- The final stage of the planning process is to develop a plan for implementation and
testing.
6) Optimization
Once you have deployed IPv6, your work has just begun. The adoption process is a closed loop that offers
opportunities for continual feedback and optimization.

Transition :-
– Dual Stack mechanisms :- Depending on the scale, a dual-stack approach
can also be the most expensive and time-consuming to deploy, especially
when considering all possible systems. It can potentially require new
hardware or changes to existing hardware, considerable planning, a
welldefined rollout plan, and a skilled operations staff.

– Translation Mechanisms :- to allow IPv6 only devices to

communicate with IPv4 only devices
– Tunnelling Mechanisms :- Encapsulation of IPv6 packets within IPv4
packets and vice versa which means it can also be used for IPv4
connections over IPv6 native networks. E.g
– IPv6 tunneling encapsulates IPv6 packets within IPv4 packets and uses
the existing IPv4 core to allow IPv6 end systems (islands) to communicate
without the need to upgrade the intermediate IPv4 infrastructure between
them.
– Configured (Static) - tunnel mode ipv6ip, GRE
– Automatic
6to4 (RFC 3056)  site2site
ISATAP  intra-site host2host
Teredo end to end and it works behind nat also.
–
– 1) DNS server
1) 6to4 address  IPv4 encapsulated in IPv6 or IPv6 encapsulated in
IPv4 (2002:border-router-IPv4-address::/48. IPv6 prefix that is
reserved for 6to4 use )
tunnel mode ipv6ip 6to4 command tells R1 to look to the 2nd/3rd
octets to find the destination IPv4 address,
IPv4 Anycast Address
IPv6 192.88.99.1
Native Network IPv4
Internet

6to4
6to4 relay
router
router
(gateway)
6to4 client
Tunnels
through IPv4
IPv4 address
V4ADDR
IPv6 address 6to4
2002:V4ADDR::1 router
IPv6 Host (gateway)
6to4 client
6to4 subnet
IPv6 Addresses:
An IPv6 IGP is not needed, because the router finds the destination IPv4 address on the
other end of the tunnel embedded in the destination IPv6 address in the received packet.
IPv6 addresses are not in the same subnet as the other routers’ tunnel interfaces.
I have to use static route.

Destination IPv6 Address: Destination IPv4 Address Destination IPv6 Address:

V6ADDR 192.88.99.1 V6ADDR

IPv6 Packet IPv4 Header Encapsulated IPv6 Packet IPv6 Packet

6to4 6to4
router relay
(gateway) router
6to4 host Native IPv6 host
IPv6 address V6ADDR
2002:V4ADDR-A::25
IPv4 Internet IPv6 Internet

IPv4 address Well known IPv4 address

V4ADDR-A or
IPv6 address the Anycast address
2002:V4ADDR-A::1 192.88.99.1

Destination IPv6 Address: Destination IPv4 Address Destination IPv6 Address:

2002:V4ADDR-A::25 V4ADDR-A 2002:V4ADDR-A::25

IPv6 Packet IPv4 Header Encapsulated IPv6 Packet IPv6 Packet

S ta r t w ith IP v 4 A d d r e s s

1 9 2 .0 .2 .7 5

Is c o n v e r te d to h e x C 0 0 0 :0 2 4 B
fo r m

6 to 4 h a s its o w n
2 0 0 2 ::/1 6 a s s ig n e d a d d r e s s b lo c k

P r e - p e n d e d to th e h e x
2 0 0 2 ::/1 6 & C 0 0 0 :0 2 4 B
c o n v e r te d v 4 a d d r e s s

Y ie ld is a g lo b a l- s c o p e d r o u ta b le
2 0 0 2 :C 0 0 0 :0 2 4 B ::/4 8 IP v 6 p r e fix

– 2) ISATAP  Intra Site automatic Tunnel Addressing Protocol -- The node

(A.B.C.D)v4 gets the (FE80::5EFE:AB:CD)v6 Link Local address
– ISATAP is a mechanism with minimal configuration required
– ISATAP is ideal when there are relatively few, relatively scattered
individual nodes that need service
–
– 192.0.2.100 IPv4 Address

–
– Is converted to hex C000:0264
form
–
– 0000:5EFE
And pre-pended with the
ISATAP 32-bit link-local suffix
–
– ::0000:5EFE:C000:0264
–
– The link-local prefix merges with
– FE80::/10
the network identifier to create the

– ISATAP IPv6 link-local address

– FE80::0000:5EFE:C000:0264
 – The router adds 0000:5EFE as quartets 5 and 6 amd 7&8 will be IPv4
address.
– tunnel mode ipv6ip isatap
–
–
–
–
–

–
–
– 3) Teredo  If host behind NAT . Encapsulates the IPv6 packets within
UDP v4 packets to bypass the problem of NAT in many cases restricting
protocol 41 (IP encapsulated) packets. Teredo is complex, so
performance will suffer – may consider as last resort
–
IPv4 Header UDP Header Encapsulated IPv6 Packet

Potential Issue with Tunnelling 

 MTU fragmentation
 ICMPv4 error handling
 Filtering protocol 41
 NAT (Network Address Translation)

A General Transition Roadmap for an enterprise or educational network

• Network Design v
• Implementation of a mixed IPv4/IPv6 environment
• Gradual transition of non-critical systems to IPv6
Allows the evaluation of the operation and stability of the network devices and
non-critical systems under IPv6
Develops the transition procedures
Disseminates the usages of transition mechanisms (tunnels, gateways, etc.) for
communications between exclusive IPv6 areas
• Transition of all systems to IPv6
•

. IPv4 address space such as Classless Inter-Domain Routing (CIDR), RFC 1918
addresses, and Network Address Translation (NAT), which have extended the
availability of IPv4 addressing at much lower costs and technical requirements than
those associated with converting or adopting IPv6.
. select the most appropriate option—both as a transition strategy and as a long-term
IPv6 strategy.

NAT-PT  if one end Is ipv4 and other end is IPv6

How many ways I can assigned IPv6 address to interfaces

 1) Manual
2) Using eig-64
3) Using automatic  RS & RA -- stateless
4) Using DHCP  statefull

 TO configure ipv6 on switch  by default switch does not allocate memory for
ipv6 so we have to enable …. Sdm prefer dial-ipv4-and-ipv6 and save and reload

OSPFv3 LSA’s :-
Router LSAs (Type 1)—
Network LSAs (Type 2)—
Interarea-prefix LSAs for ABRs (Type 3)—
Interarea-router LSAs for ASBRs (Type 4)—
Autonomous system external LSAs (Type 5)—
Link LSAs (Type 8)—
Intra-Area-Prefix LSAs (Type 9)—

IN IPv6 redistribution ,, connected links won’t get redistribute bydefault.

Node-Local Scope
FF01:0:0:0:0:0:0:1 224.0.0.1 All-nodes address
FF01:0:0:0:0:0:0:2 224.0.0.2 All-routers address
Link-Local Scope
FF02:0:0:0:0:0:0:1 224.0.0.1 All-nodes address
FF02:0:0:0:0:0:0:2 224.0.0.2 All-routers address
FF02:0:0:0:0:0:0:5 224.0.0.5 OSPF IGP
FF02:0:0:0:0:0:0:6 224.0.0.6 OSPF IGP designated routers
FF02:0:0:0:0:0:0:9 224.0.0.9 RIP routers
FF02:0:0:0:0:0:0:D 224.0.0.13 All PIM routers
Site-Local Scope
FF05:0:0:0:0:0:0:2 224.0.0.2 All-routers address
Any Valid Scope
FF0X:0:0:0:0:0:0:101 224.0.1.1 Network Time
Protocol (NTP)
FF0X:0:0:0:0:0:0:127 224.0.1.39 cisco-rp-announce
FF0X:0:0:0:0:0:0:128 224.0.1.40 cisco-rp-discovery
Extension Headers :-
1) TCP header
2) AUTH
3) ESP
4) Fragmentation
5) HOP by Hop option
6) Destination option
7) routing

IPv6 minimum MTU of 1280 bytes.

ICMPv6  ICMPv6 is integral to IPv6. Error reporting, MTU path discovery and neighbor
discovery.

A significant difference between IPv4 and IPv6 is that ..only originating nodes can
fragment packets; So originating nodes must either use Path MTU Discovery (PMD) to
find the lowest MTU along a path to the destination, or never produce packets larger
than 1280 bytes.
ICMPv6-ND: Sending NS for FE80::C803:9FF:FED4:1C on FastEthernet1/0
ICMPv6-ND: DAD: FE80::C803:9FF:FED4:1C is unique.
ICMPv6-ND: Sending NA for FE80::C803:9FF:FED4:1C on FastEthernet1/0
ICMPv6-ND: Address FE80::C803:9FF:FED4:1C/10 is up on FastEthernet1/0
ICMPv6-ND: Sending RS on FastEthernet1/0
ICMPv6-ND: Received RA from FE80::C801:5FF:FE84:38 on FastEthernet1/0
ICMPv6-ND: Sending NS for 2001:CCCC::C803:9FF:FED4:1C on FastEthernet1/0
ICMPv6-ND: Autoconfiguring 2001:CCCC::C803:9FF:FED4:1C on FastEthernet1/0

ICMPv6-ND: DAD: 2001:CCCC::C803:9FF:FED4:1C is unique.

ICMPv6-ND: Sending NA for 2001:CCCC::C803:9FF:FED4:1C on FastEthernet1/0
ICMPv6-ND: Address 2001:CCCC::C803:9FF:FED4:1C/64 is up on FastEthernet1/0

Q  I have configured only IPv6 address on interfaces and configured ospfv3 how it will
work - it won’t work bcz ospf router-id either we have to define manual or at least one
interface should have ipv4 address.

RIPng  up to four RIP processes are supported. Each process must use a unique
UDP port number. A single process can use the default value, 521.
OSPFv3 router IDs, area IDs, and LSA link state IDs are still expressed using 32 bits.
Multiple OSPFv3 protocol processes can run on a single link.

The IPv6 version of the redistribute command takes only routes learned from an IGP but
by default does not take connected routes on interfaces enabled for that IGP. Redistribution
takes routes from the IP routing table.Address won’t be redistributed is
link local addresses
■ local routes
■ connected routes
  BSNL Range :- 2001:4490::/30
Divided into Mobile,Multiplay,FTTH,CDMA,NGN,3G,WiMax,MPLS CORE

FTTH & WimaX ,MPLS  Full /36 Block

MOBILE 3G  The country is divided into 4 zones. Therefore /38 address block will be
reserved for each zone. Of this /38 block one /39 will be for post paid and the other /39
for prepaid service.
MULTIPLAY  Therefore /42 address block for every BNG.
CDMA  160 MSCs are. Therefore /44 address block for every MSC. Out of this /45 for
post paid & /45 for prepaid services.
NGN  /41 address block for every circle.

CHECk :-
1) Newly for ipv6 only
2) Ipv4 is existed and want to migrate to ipv6 .

PLAN :-
a) Map out strategy for IPv6 migration including consideration of the following
Developing a Detailed Design :- The detailed design includes the IPv6 addressing plan; physical connectivity
considerations,

i) Application migration or upgrades

ii) Networking/router migrations or upgrades

iii) Selection of transition technologies from tunneling, translation and/or dual-stack

approaches and planning corresponding DNS impacts

iv) Selection of IPv6 device configuration strategy, e.g., stateless autoconfiguration,

 stateful configuration or hybrid

b) Consider timeframe requirements, if any, analyze dependencies across affected elements

and determine budgeting requirements to derive a migration plan.
Execution :-
Completion :-
As planned, complete the transition with decommissioning of IPv4 space or planned coexistence of
IPv4-IPv6 address space. This can be done as portions of your network fully
migrate or as a final decommissioning step across the network.

b) You may want to leave IPv4 protocol operational throughout, or on portions of your
network, depending on requirements to service external hosts that may be IPv4-only
based on internal policies.