[c-nsp] GSR12008 Error
Chris Lane
clane1875 at gmail.com
Wed Sep 10 17:12:35 EDT 2008
I think its safe to say its the LC. Issue is resolved with LC removed. Site
is remote across country, i will get a maintenance window and get more info
in the near future.
Regards,
Chris
On Wed, Sep 10, 2008 at 5:00 PM, Leonardo Gama Souza <
leonardo.souza at nec.com.br> wrote:
> You can try to insert that LC into another slot and collect those
> commands if the issue come back.
>
>
> ------------------------------
> *De:* Chris Lane [mailto:clane1875 at gmail.com]
> *Enviada:* qua 10/9/2008 17:44
>
> *Para:* Leonardo Gama Souza
> *Cc:* cisco-nsp at puck.nether.net
> *Assunto:* Re: [c-nsp] GSR12008 Error
>
> Darn, problem for me is i removed the 8 port FastE card that was causing
> all the grief last night because it kept reloading. I removed the one
> connection i had in LC and LC still continued to bounce. Here is the
> output anyways.
>
> -----------------------------------------
>
>
>
> On Wed, Sep 10, 2008 at 4:33 PM, Leonardo Gama Souza <
> leonardo.souza at nec.com.br> wrote:
>
>> The same command.
>> execute-on all show controller fia
>>
>> Rgds.
>>
>> ------------------------------
>> *De:* Chris Lane [mailto:clane1875 at gmail.com]
>> *Enviada:* qua 10/9/2008 17:34
>> *Para:* Leonardo Gama Souza
>>
>> *Assunto:* Re: [c-nsp] GSR12008 Error
>>
>> You didn't add command ~
>> Thanks
>>
>> On Wed, Sep 10, 2008 at 4:23 PM, Leonardo Gama Souza <
>> leonardo.souza at nec.com.br> wrote:
>>
>>> Oh. I forgot one thing.
>>> You must issue this command on all LC as well.
>>>
>>>
>>> ------------------------------
>>> *De:* Chris Lane [mailto:clane1875 at gmail.com]
>>> *Enviada:* qua 10/9/2008 17:25
>>> *Para:* Leonardo Gama Souza
>>> *Cc:* cisco-nsp at puck.nether.net
>>> *Assunto:* Re: [c-nsp] GSR12008 Error
>>>
>>> No errors as you can see.
>>> cr.la1.ca#sh <http://cr.la1.ca/#sh> controller fia
>>> Fabric configuration: 2.4Gbps bandwidth, redundant fabric
>>> Master Scheduler: Slot 17 Backup Scheduler: Slot 16
>>>
>>> From Fabric FIA Errors
>>> -----------------------
>>> redund fifo parity 0 redund overflow 0 cell drops 0
>>>
>>> crc32 lkup parity 0 cell parity 0 crc32 0
>>>
>>> Switch cards present 0x001F Slots 16 17 18 19 20
>>> Switch cards monitored 0x001F Slots 16 17 18 19 20
>>> Slot: 16 17 18 19 20
>>> Name: csc0 csc1 sfc0 sfc1 sfc2
>>> -------- -------- -------- -------- --------
>>> los 0 0 0 0 0
>>> state Off Off Off Off Off
>>> crc16 0 0 0 0 0
>>>
>>> To Fabric FIA Errors
>>> -----------------------
>>> sca not pres 0 req error 0 uni fifo overflow 0
>>>
>>> grant parity 0 multi req 0 uni fifo undrflow 0
>>>
>>> cntrl parity 0 uni req 0 crc32 lkup parity 0
>>>
>>> multi fifo 0 empty dst req 0 handshake error 0
>>> On Wed, Sep 10, 2008 at 4:10 PM, Leonardo Gama Souza <
>>> leonardo.souza at nec.com.br> wrote:
>>>
>>>> Hi,
>>>>
>>>> Look for errors in "show controller fia".
>>>> Maybe the LC was badly seated...
>>>> Maybe you have a bad SFC...
>>>> There are a lot of possibilities.
>>>>
>>>> Cheers,
>>>> Leonardo Gama.
>>>>
>>>> ------------------------------
>>>> *De:* cisco-nsp-bounces at puck.nether.net em nome de Chris Lane
>>>> *Enviada:* qua 10/9/2008 15:58
>>>> *Para:* cisco-nsp at puck.nether.net
>>>> *Assunto:* [c-nsp] GSR12008 Error
>>>>
>>>> All,
>>>>
>>>> GSR question, appears Cisco finally got around to updating the IOS train
>>>> on
>>>> 12.0.32.S – we have been running S8 for a while but S11 just came out
>>>> and it
>>>> appears to have many new features! One of my routers is running
>>>> 12.0.32.S6 –
>>>> its been so for 2years. I had a bad 8 port FastE lc a while back so I
>>>> replaced just recently with a known good lc tested in the lab, So I
>>>> sent it
>>>> to replace the failed one ~ after 2 days I started getting these
>>>> errors.
>>>>
>>>> %FABRIC-3-ERR_HANDLE:
>>>>
>>>> %RP-3-FABRIC_UNI
>>>>
>>>> %FIA-3-HALT
>>>>
>>>> L%LC-6-BMACMDRPLY
>>>>
>>>>
>>>>
>>>> >From what I gather this is the RP is having trouble communicating with
>>>> the
>>>> LC. One of these errors suggests upgrading IOS ~ but S6 to S8 isn't
>>>> that
>>>> big of a deal and couldn't possibly be the culprit could it? Is this RP
>>>> related? And if so I could easily flip to the backup RP.
>>>>
>>>> Any suggestions would be super appreciative.
>>>>
>>>> --
>>>> //CL
>>>> _______________________________________________
>>>> 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/
>>>>
>>>>
>>>
>>>
>>> --
>>> //CL
>>>
>>
>>
>>
>> --
>> //CL
>>
>
>
>
> --
> //CL
>
--
//CL
More information about the cisco-nsp
mailing list