wg-multicast - Re: PIM-5-REG_ENCAP_INVALID?
Subject: All things related to multicast
List archive
- From: Gordon Rogier <>
- To:
- Subject: Re: PIM-5-REG_ENCAP_INVALID?
- Date: Mon, 13 Nov 2000 11:24:12 -0600 (CST)
jeff, beat me to the CSCdr49641 bug id. note, this is fixed in 12.1(5).
it really is not a problem in the Cisco, only a reaction to the JUNOS
and/or network across the wide area.
--*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*--
Gordon Rogier
Network Engineer 785-864-0381wk 785-550-4468 cell
Great Plains Network 785-864-9330 FAX
On Mon, 13 Nov 2000, Jeff Olenchek wrote:
> Anybody know what this means?
>
> Nov 10 12:06:16.950 EST: %PIM-5-REG_ENCAP_INVALID: Bad register from
> 128.59.0.231 for (160.39.128.207, 224.77.18.18). Trace = 450005D4 91970000
> 4110C2C
> -Process= "PIM Process", ipl= 0, pid= 99
>
> This is logged on my RP (7507 running 12.1(3.3)). The sender is a PC
> running Ghost. The source of the register is a 6509 running Cosmos
> 12.0(7)XE1.
>
> I'm also seeing some other clutter in the log on the RP which I
> mentioned at the WG meeting in Atlanta:
>
> Nov 12 05:35:07.612 EST: %PIM-5-SA_ENCAP_INVALID: Bad SA from RP
> 141.142.12.1 for (141.142.4.9, 224.0.1.84). Trace = 45000056 48670000
> E110000
> -Process= "MSDP Process", ipl= 0, pid= 107
> Nov 13 02:47:26.192 EST: %PIM-5-SA_ENCAP_INVALID: Bad SA from RP
> 193.190.197.253 for (69.0.0.178, 16.0.0.0). Trace = 2020 E53796D0
> 8FA90169
> -Process= "MSDP Process", ipl= 0, pid= 107
> Nov 13 07:54:40.460 EST: %PIM-5-SA_ENCAP_INVALID: Bad SA from RP
> 147.102.255.3 for (0.0.32.32, 229.55.150.208). Trace = 2020 E53796D0
> 9366620F
> -Process= "MSDP Process", ipl= 0, pid= 107
>
> TIA.
> /a
>
> Maybe this is bug CSCdr49641
>
> Release Notes
>
> A Cisco router that is running Cisco IOS Release
> 12.0(10)S and that receives
> a large packet that was fragmented before receipt may
> display the following
> error message at the rendezvous point of a multicast
> network that is running
> Protocol Independent Multicast (PIM) sparse mode:
> %PIM-5-REG_ENCAP_INVALID: Bad register from for (,
> ). Trace = ....
> ...
>
> jeff
>
>
- PIM-5-REG_ENCAP_INVALID?, Alan Crosswell, 11/13/2000
- Re: PIM-5-REG_ENCAP_INVALID?, Matthew Davy, 11/13/2000
- <Possible follow-up(s)>
- Re: PIM-5-REG_ENCAP_INVALID?, Jeff Olenchek, 11/13/2000
- Re: PIM-5-REG_ENCAP_INVALID?, Gordon Rogier, 11/13/2000
- Re: PIM-5-REG_ENCAP_INVALID?, Alan Crosswell, 11/13/2000
Archive powered by MHonArc 2.6.16.