Velocity Reviews

Velocity Reviews (http://www.velocityreviews.com/forums/index.php)
-   Cisco (http://www.velocityreviews.com/forums/f27-cisco.html)
-   -   Disable PIM Assert Process (http://www.velocityreviews.com/forums/t562613-disable-pim-assert-process.html)

philbo30 12-20-2007 03:24 PM

Disable PIM Assert Process
 
Does IOS 12.4 provide a mechanism to disable the PIM Assert Process?
If so, how?

philbo30 12-20-2007 04:00 PM

Re: Disable PIM Assert Process
 
On Dec 20, 10:24 am, philbo30 <masfe...@gmail.com> wrote:
> Does IOS 12.4 provide a mechanism to disable the PIM Assert Process?
> If so, how?


An alternative to disabling the PIM assert process might be to use an
ACL to block PIMv2 Type 5 messages in/out to 224.0.0.2. Any ideas on
how this ACL would look if it can be done?

philbo30 12-20-2007 04:06 PM

Re: Disable PIM Assert Process
 
On Dec 20, 11:00 am, philbo30 <masfe...@gmail.com> wrote:
> On Dec 20, 10:24 am, philbo30 <masfe...@gmail.com> wrote:
>
> > Does IOS 12.4 provide a mechanism to disable the PIM Assert Process?
> > If so, how?

>
> An alternative to disabling the PIM assert process might be to use an
> ACL to block PIMv2 Type 5 messages in/out to 224.0.0.2. Any ideas on
> how this ACL would look if it can be done?


Correction: 224.0.0.13 for PIMv2. 224.0.0.2 is PIMv1

pcmccollum@N0SPAMgmail.com 12-20-2007 09:35 PM

Re: Disable PIM Assert Process
 
On Dec 20, 8:06 am, philbo30 <masfe...@gmail.com> wrote:
> On Dec 20, 11:00 am, philbo30 <masfe...@gmail.com> wrote:
>
> > On Dec 20, 10:24 am, philbo30 <masfe...@gmail.com> wrote:

>
> > > Does IOS 12.4 provide a mechanism to disable the PIM Assert Process?
> > > If so, how?

>
> > An alternative to disabling the PIM assert process might be to use an
> > ACL to block PIMv2 Type 5 messages in/out to 224.0.0.2. Any ideas on
> > how this ACL would look if it can be done?

>
> Correction: 224.0.0.13 for PIMv2. 224.0.0.2 is PIMv1


I would recommend against blocking that multicast address as that
would handicap any PIM communication coming in that interface. I know
of no way to disable just the Assert messages in IOS.

neteng
http://blog.humanmodem.com

stephen 12-20-2007 10:39 PM

Re: Disable PIM Assert Process
 
"pcmccollum@N0SPAMgmail.com" <pcmccollum@gmail.com> wrote in message
news:4a0c76a5-5123-458b-be08-686afa4f89bf@d21g2000prf.googlegroups.com...
> On Dec 20, 8:06 am, philbo30 <masfe...@gmail.com> wrote:
> > On Dec 20, 11:00 am, philbo30 <masfe...@gmail.com> wrote:
> >
> > > On Dec 20, 10:24 am, philbo30 <masfe...@gmail.com> wrote:

> >
> > > > Does IOS 12.4 provide a mechanism to disable the PIM Assert Process?
> > > > If so, how?

> >
> > > An alternative to disabling the PIM assert process might be to use an
> > > ACL to block PIMv2 Type 5 messages in/out to 224.0.0.2. Any ideas on
> > > how this ACL would look if it can be done?

> >
> > Correction: 224.0.0.13 for PIMv2. 224.0.0.2 is PIMv1

>
> I would recommend against blocking that multicast address as that
> would handicap any PIM communication coming in that interface. I know
> of no way to disable just the Assert messages in IOS.


on a related problem - anyone know how to stop IOS sending out multicasts to
224.0.1.40 for the AutoRP function?

it bhaves OK with a pure IOS environment - but causes lots of "invalid RP
join" messages when it propagates to other PIM v2 / BSR type devices...
>
> neteng
> http://blog.humanmodem.com

--
Regards

stephen_hope@xyzworld.com - replace xyz with ntl



pcmccollum@N0SPAMgmail.com 12-20-2007 11:51 PM

Re: Disable PIM Assert Process
 
On Dec 20, 2:39 pm, "stephen" <stephen_h...@xyzworld.com> wrote:
> "pcmccol...@N0SPAMgmail.com" <pcmccol...@gmail.com> wrote in message
>
> news:4a0c76a5-5123-458b-be08-686afa4f89bf@d21g2000prf.googlegroups.com...
>
>
>
> > On Dec 20, 8:06 am, philbo30 <masfe...@gmail.com> wrote:
> > > On Dec 20, 11:00 am, philbo30 <masfe...@gmail.com> wrote:

>
> > > > On Dec 20, 10:24 am, philbo30 <masfe...@gmail.com> wrote:

>
> > > > > Does IOS 12.4 provide a mechanism to disable the PIM Assert Process?
> > > > > If so, how?

>
> > > > An alternative to disabling the PIM assert process might be to use an
> > > > ACL to block PIMv2 Type 5 messages in/out to 224.0.0.2. Any ideas on
> > > > how this ACL would look if it can be done?

>
> > > Correction: 224.0.0.13 for PIMv2. 224.0.0.2 is PIMv1

>
> > I would recommend against blocking that multicast address as that
> > would handicap any PIM communication coming in that interface. I know
> > of no way to disable just the Assert messages in IOS.

>
> on a related problem - anyone know how to stop IOS sending out multicasts to
> 224.0.1.40 for the AutoRP function?
>
> it bhaves OK with a pure IOS environment - but causes lots of "invalid RP
> join" messages when it propagates to other PIM v2 / BSR type devices...
>
> > neteng
> >http://blog.humanmodem.com

>
> --
> Regards
>
> stephen_h...@xyzworld.com - replace xyz with ntl


Stephen,

I think you'll need to implement the 'ip multicast boundary <acl#>
filter-autorp' command. It works as a bi-directional ACL to block auto-
rp traffic for the multicast groups in the ACL. Let's say you want to
stop the traffic from flowing through ethernet0/0:

ACL for all multicast groups:
access-list 1 permit 224.0.0.0. 15.255.255.255

interface e0/0
ip multicast boundary 1 filter-autorp

HTH,
neteng
http://blog.humanmodem.com

stephen 12-21-2007 08:35 AM

Re: Disable PIM Assert Process
 
"pcmccollum@N0SPAMgmail.com" <pcmccollum@gmail.com> wrote in message
news:c737ecc2-ba94-4fc1-9107-28da37dd69a1@a35g2000prf.googlegroups.com...
> On Dec 20, 2:39 pm, "stephen" <stephen_h...@xyzworld.com> wrote:
> > "pcmccol...@N0SPAMgmail.com" <pcmccol...@gmail.com> wrote in message
> >
> >

news:4a0c76a5-5123-458b-be08-686afa4f89bf@d21g2000prf.googlegroups.com...
> >
> >
> >
> > > On Dec 20, 8:06 am, philbo30 <masfe...@gmail.com> wrote:
> > > > On Dec 20, 11:00 am, philbo30 <masfe...@gmail.com> wrote:

> >
> > > > > On Dec 20, 10:24 am, philbo30 <masfe...@gmail.com> wrote:

> >
> > > > > > Does IOS 12.4 provide a mechanism to disable the PIM Assert

Process?
> > > > > > If so, how?

> >
> > > > > An alternative to disabling the PIM assert process might be to use

an
> > > > > ACL to block PIMv2 Type 5 messages in/out to 224.0.0.2. Any ideas

on
> > > > > how this ACL would look if it can be done?

> >
> > > > Correction: 224.0.0.13 for PIMv2. 224.0.0.2 is PIMv1

> >
> > > I would recommend against blocking that multicast address as that
> > > would handicap any PIM communication coming in that interface. I know
> > > of no way to disable just the Assert messages in IOS.

> >
> > on a related problem - anyone know how to stop IOS sending out

multicasts to
> > 224.0.1.40 for the AutoRP function?
> >
> > it bhaves OK with a pure IOS environment - but causes lots of "invalid

RP
> > join" messages when it propagates to other PIM v2 / BSR type devices...
> >
> > > neteng
> > >http://blog.humanmodem.com

> >
> > --
> > Regards
> >
> > stephen_h...@xyzworld.com - replace xyz with ntl

>
> Stephen,
>
> I think you'll need to implement the 'ip multicast boundary <acl#>
> filter-autorp' command. It works as a bi-directional ACL to block auto-
> rp traffic for the multicast groups in the ACL. Let's say you want to
> stop the traffic from flowing through ethernet0/0:
>
> ACL for all multicast groups:
> access-list 1 permit 224.0.0.0. 15.255.255.255
>
> interface e0/0
> ip multicast boundary 1 filter-autorp


OK - thanks for that - i will give it a try.
>
> HTH,
> neteng
> http://blog.humanmodem.com

--
Regards

stephen_hope@xyzworld.com - replace xyz with ntl




All times are GMT. The time now is 05:27 PM.

Powered by vBulletin®. Copyright ©2000 - 2013, vBulletin Solutions, Inc.
SEO by vBSEO ©2010, Crawlability, Inc.


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57