 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
6 messages in net.nether.puck.cisco-nsp[c-nsp] Re: Strange error on Cat65 MSFC| From | Sent On | Attachments |
|---|---|---|
| Jason Koh | Jan 18, 2005 10:42 pm | |
| Michael K. Smith | Jan 19, 2005 12:47 am | |
| Jason Koh | Jan 19, 2005 1:01 am | |
| John Neiberger | Jan 19, 2005 10:31 am | |
| MADMAN | Jan 19, 2005 11:20 am | |
| Jason Koh | Jan 19, 2005 8:06 pm |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | [c-nsp] Re: Strange error on Cat65 MSFC | Actions... |
|---|---|---|
| From: | MADMAN (davi...@qwest.com) | |
| Date: | Jan 19, 2005 11:20:59 am | |
| List: | net.nether.puck.cisco-nsp | |
CCO doesn't say much on this except open a TAC case:
ERROR MESSAGE NOTIFICATIONS (if any)
%MSFC2-3-MISTRAL_BAD_PAK (x1): Possibly un-encapsulated packet passed to Mistral: int [chars], type [int], stat [hex], flags [hex], size [dec], offset [dec], total [int]
Explanation: A packet that is badly encapsulated has been received from the process level.
Recommended Action: Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information
Though I seem to recall this error and it was a line card fault though I think we tried replacing the sup/MSFC first.
Dave
Jason Koh wrote:
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
_______________________________________________ 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/
-- David Madland CCIE# 2016 Sr. Network Engineer Qwest Communications 612-664-3367
"Emotion should reflect reason not guide it"