Hi,
Congrats! If you have MPLS in your backbone, you can continue to use
IPv4 as the transport for your MPLS signaling. With this approach you
can run 6VPE and build a VPN for your inet6 traffic. This is a common
approach for "getting things going". All v6 stuff just rides across
MPLS and your core doesn't know the difference.
If you plan to carry inet6 routes in a non-ipvpn topology, you can get
your core "dual stack"; if you run OSPFv2 today you will need to
consider OSPFv3 or ISIS to carry IPv6 in your IGP.
You can have all your ipv4 configuration coexist with ipv6.
You can also use logical routers / virtual routers / etc, if you want
separation at that level.
Kind regards,
Truman
On 25/05/2009, at 10:32 PM, Matthias Gelbhardt wrote:
Hi!
Today we received our IPv6 prefix from RIPE. There are many projects
in the pipeline, so we would like to enable our network with IPv6
and would like to start new projects with default deployment in IPv6.
What would be the best practice to bring our backbone to IPv6? Would
one use a virtual router for this? Or is it doable to configure IPv6
in parallel to my other configuration? Do I have special memory
requirements for a virtual router, like a VM on VMware?
Regards,
Matthias
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
