All things related to multicast

[Jeff Olenchek <>]

        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