[c-nsp] ip multicast boundary

[schilling]

Here is my multicast boundary:

ip access-list standard multicast-boundary
  deny 224.0.1.39
  deny 224.0.1.40
  deny 239.0.0.0 0.255.255.255
  permit any any

Please refer to

http://www.abilene.iu.edu/i2network/multicast-cookbook.html

schilling

On 6/20/07, Sergey Velikanov [Intelsoft] <sv at intelsoft.com> wrote:
>
> Hi
>
> command reference says about ip multicast boundary
>
> "Use this command to configure an administratively scoped boundary on an
> interface to filter multicast group addresses in the range defined by the
> access-list argument. A standard
> access list defines the range of addresses affected. When this command is
> configured, no multicast data packets are allowed to flow across the
> boundary from either direction.
> Restricting multicast data packet flow enables reuse of the same multicast
> group address in different administrative domains."
>
> so it should filter only multicast addresses, but when i apply this
> command on interface my msdp session goes down.
>
> access-list 80 remark Groups from DTV
> access-list 80 permit 224.1.0.0 0.0.7.255
>
> rk(config)#int vlan151
> rk(config-if)#ip multicast boundary 80
>
> some time ago
>
> %MSDP-5-PEER_UPDOWN: Session to peer 172.16.224.2 going down
> rk(config-if)#
> rk(config-if)#no ip multicast boundary 80
> rk(config-if)#
>
>
> %MSDP-5-PEER_UPDOWN: Session to peer 172.16.224.2 going up
>
> why ip multicast boundary filter tcp session with source & destination not
> in multicast range?
>
> Cisco IOS Software, C3560 Software (C3560-ADVIPSERVICESK9-M), Version 12.2(25)SED1,
> RELEASE SOFTWARE (fc1)
> Copyright (c) 1986-2005 by Cisco Systems, Inc.
> Compiled Tue 22-Nov-05 23:18 by yenanh
> Image text-base: 0x00003000, data-base: 0x01191EEC
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>