MDT Data on NX-OS 5.2

Answered Question
Sep 22nd, 2011

Hi everyone,

I´m trying to assign specific Customer-Multicast-Groups to an explicit MDT Data-Group via route-map which is configured on each mdt data-group.

Config looks like this

!

ip access-list High

10 permit ip any host 239.3.0.1/32

!

ip access-list Medium

10 permit ip any host 239.5.0.1/32

!

route-map High permit 10

match ip address High

!

route map Medium permit 10

match ip address Medium

!

vrf context Blue

mdt data 232.10.1.0/24 threshold 10 route-map High

mdt data 232.10.2.0/24 threshold 10 route-map Medium

!

My goal is, to have all multicast for 239.3.0.1 in 232.10.1.0/24 and all multicast for 239.5.0.1 in 232.10.2.0/24.

Right now, both customer-address are getting assigend to 232.10.2.0.

Any ideas?

I have this problem too.
0 votes
Correct Answer by tthankap about 2 years 6 months ago

Hello Dirk,

I can see that the route-map definition is not correct . The route-map must have 'match ip multicast group <>' for multicast control-plane filtering. Since the route-maps didn't have this match command and since route-maps are permit by default, only first route-map was getting selected ('Medium' was first route-map internally in mvpn).

Please modify the route-map config as follows:

route-map High permit 10

match ip multicast group 239.3.0.1/32

!

route map Medium permit 10

match ip multicast group 239.5.0.1/32

and let me know the results ..

  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 5 (1 ratings)
tthankap Mon, 09/26/2011 - 22:05

Hello Dirk ,

Is this a partial config that you are showing ? I dont see the default MDT defind?

I am guessing that you have all these features enabled too

feature bgp

feature pim

feature mvpn

feature mpls l3vpn

feature tunnel

feature mpls ldp

Inculde these o/p

show ip pim mdt

show mvpn mdt route

show ip pim mdt receive & send

Dirk Woellhaf Tue, 09/27/2011 - 00:17

Hi,

it is just a partial config. The "tunnel"-feature is not enabled by now.

here are the requested outputs:

S2# show ip pim mdt vrf Blue

MVPN Status Information for VRF "Blue" : MTI(mti8) Up

  Default MDT group 232.1.1.1 (Mode - SSM)

    Configured MTU: 1376 bytes, Actual MTU: 1376 bytes

    Configured tunnel source interface: loopback10

    Default BGP tunnel source interface: loopback10

    PIM Hello Interval: 30000 milliseconds

    PIM JP Interval: 60 seconds

    Data MDT Join Interval: 60 seconds

    Data MDT Switchover Interval: 3 seconds

    Data MDT Holddown Interval: 60 seconds

    Data MDT Timeout Interval: 240 seconds

    MDT Source address: 119.16.20.213 (iod loopback10)

    BGP RD: 192.16.20.213:100 (set)

    Data MDT Send Join Count: 6664

    Data MDT Received Join Count: 22201

     Data MDT: 232.10.2.0/24 threshold: 10 kbps route-map: Medium

     Data MDT: 232.10.1.0/24 threshold: 10 kbps route-map: High

S2# sh mvpn mdt route

MVPN MDT(Global) Route information for VRF "Blue":

(192.8.20.11, 232.1.1.1) [Refcount: 0]

(192.8.20.12, 232.1.1.1) [Refcount: 0]

(192.8.20.212, 232.1.1.1) [Refcount: 0]

(192.8.20.212, 232.10.2.0) [Refcount: 1]

(192.8.20.222, 232.1.1.1) [Refcount: 0]

(192.8.20.222, 232.10.2.0) [Refcount: 1]

(192.16.20.13, 232.1.1.1) [Refcount: 0]

(192.16.20.14, 232.1.1.1) [Refcount: 0]

(192.16.20.213, 232.1.1.1) [Refcount: 0]

(192.16.20.213, 232.10.2.0) [Refcount: 1]

(192.16.20.223, 232.1.1.1) [Refcount: 0]

S2# sh ip pim mdt send vrf Blue

MDT Data Groups Send List for vrf: Blue

C-Source        C-Group         MDT Source      MDT Group       Uptime   

192.168.224.1   239.3.0.1       192.16.20.213   232.10.2.0      4d19h   

S2# sh ip pim mdt rec vrf Blue

MDT Data Groups Received List for vrf: Blue

C-Source        C-Group         MDT Source      MDT Group       Uptime   

192.168.36.1    239.5.0.1       192.8.20.212    232.10.2.0      4d18h    

192.168.36.1    239.5.0.1       192.8.20.222    232.10.2.0      4d18h    

192.168.224.1   239.3.0.1       192.16.20.223   232.10.2.0      4d19h

Correct Answer
tthankap Tue, 09/27/2011 - 13:14

Hello Dirk,

I can see that the route-map definition is not correct . The route-map must have 'match ip multicast group <>' for multicast control-plane filtering. Since the route-maps didn't have this match command and since route-maps are permit by default, only first route-map was getting selected ('Medium' was first route-map internally in mvpn).

Please modify the route-map config as follows:

route-map High permit 10

match ip multicast group 239.3.0.1/32

!

route map Medium permit 10

match ip multicast group 239.5.0.1/32

and let me know the results ..

Actions

Login or Register to take actions

This Discussion

Posted September 22, 2011 at 6:54 AM
Stats:
Replies:4 Avg. Rating:5
Views:946 Votes:0
Shares:0

Related Content

Discussions Leaderboard