On Wed, Aug 3, 2011 at 10:51 AM, Mark Tinka <[email protected]> wrote: > On Wednesday, August 03, 2011 11:40:26 AM tim tiriche wrote: > >> Do you normally run mult itopology or single topology for >> isis when deploying dual stack? >> Any recommendations and why chose one over the other. > > We're a multi-topology house, and turn it on by default with > every new device we add to the network. > > It's very useful because the reality is that when operators > are turning up v6 across the network, there is a period > through which the IS-IS topologies are not congruent, i.e., > one is v4 while another v4 + v6. > > Because of this, single topology on one side and multi- > topology on another won't work. Similarly, dual-stack on one > side and v4 only on the other side won't work either. > > This is especially important in multi-vendor environments, > where Cisco IOS, for example, do not enable both IS-ISv6 > when IS-IS is enabled; this is unlike Junos, which enables > both IS-IS for v4 and v6 when IS-IS is enabled. > > Unless you plan to shutdown your entire network, configure > dual-stack everywhere and then boot it all back up at once, > go MT :-). It certainly won't hurt. > >> For MPLS TE, do you create additional lsp's for v6 or >> just do 6PE? > > We just got dual-stack, and avoid 6PE altogether.
Thanks. Does, that mean if you had full mesh RSVP lsp you added the same for v6? If you had ldp running, you ran two instances one for v4 and one for v6? > > Mark. > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
