[c-nsp] Re: Strange error on Cat65 MSFC

Jason Koh kohtohshyr at pacific.net.sg
Wed Jan 19 01:01:42 EST 2005


I can't find anything in the CCO as well. I wanted to open a TAC case but I don't have a contract agreement with Cisco.

> 
> From: "Michael K. Smith" <mksmith at noanet.net>
> Date: Wed 19/01/2005 1:46 PM GMT+08:00
> To: Jason Koh <kohtohshyr at pacific.net.sg>, 
>         Marty Adkins <adkins at netcraftsmen.net>,  <cisco-nsp at puck.nether.net>
> Subject: Re: [c-nsp] Re: Strange error on Cat65 MSFC
> 
> On 1/18/05 7:42 PM, "Jason Koh" <kohtohshyr at pacific.net.sg> wrote:
> 
> > Oh dear, silly me, forgot to attach it.
> > 
> > Jan 19 11:39:51.362 SGT: %MSFC2-3-MISTRAL_BAD_PAK: Possibly un-encapsulated
> > packet passed to Mistral: int Vlan119, type 103, stat 0x210048, flags 0x0,
> > size 77, offset 58, total 2747320927
> > -Traceback= 4029DBBC 40203954 4010AF98 40922A50 40922AD8 40922C7C 40231DFC
> > 40231DE8
> > 
> PIM?  Is someone (or you) running multicast on that particular VLAN?  All of
> the Cisco stuff related to MISTRAL errors recommends a TAC case, as does a
> Traceback under any circumstances.
> 
> Anyone care to share what the MISTRAL ASIC is and or does?  I did the usual
> poking and prodding around CCO but can't find an architectural reference for
> that particular ASIC.
> 
> Mike
> 
> 

Jason Koh
Senior Network Engineer
Pacific Internet Ltd



More information about the cisco-nsp mailing list