RE: ip vrf ... mdt data

100 %

Shaughn Smith
CCIE #23962 (SP)

-----Original Message-----
From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of Rick Mur
Sent: Monday, April 20, 2009 3:21 PM
To: Rich Collins
Cc: ccielab_at_groupstudy.com
Subject: Re: ip vrf ... mdt data

The 'mdt default' is enough to get all data you need in to the tunnel. If
you want to do some loadbalancing on the multicast traffic you can set a
threshold (kbps) and specify a range of multicast addresses to use so you
can do all kinds of freaky things with :-)

But for the CCIE lab, I wouldn't bother about the 'mdt data' command if it's
not asked for. If they want you to configure it the question will be clear
about it, something like: If multicast traffic gets over 100Kbps it should
be sent to 239.0.1.0/24. Otherwise stick to the 'mdt default'.

Rick Mur
CCIE #21946 (R&S)
CCNP, CCIP, JNCIA-ER, MCSE
rick_at_rickmur.com

On Mon, 20 Apr 2009 08:07:48 -0400
  Rich Collins <nilsi2002_at_gmail.com> wrote:
  Hello,
  
  I'm trying to understand the "mdt data.." with Multicast
Distribution
  Tree setups.
  
  I've seen examples with just mdt default configured and some with the
  mdt data multicast group range defined additionally.
  
  What should indicate that mdt data should be defined and if not clear
  is it "over configuration" to define mdt data? If so is threshold 1
a
  safe bet?
  
  Thanks
  Rich
  
  
  Blogs and organic groups at http://www.ccie.net
  
  _______________________________________________________________________
  Subscription information may be found at:
  http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Mon Apr 20 2009 - 15:56:41 ART