[c-nsp] GSR 12008 GRP ISSUES
Eninja
eninja at gmail.com
Wed Jul 22 05:12:00 EDT 2009
Chris,
Quick walk through... The Secondary RP ToFab FIA reports that it is
having difficulty accessing the fabric and thus IPC fails (since it
travels via the fabric), secondary is unable to therefore initiate and
respond to active-secondary keepalives, Active RP unsuccessfully
attempts to reset it via the MBUS and then marks it dead via the
MBUS-6-DEADSCDY.
You should reinsert it to see if a reseat clears the problem before an
RMA.
Eninja
On Jul 21, 2009, at 10:12 PM, Chris Lane <clane1875 at gmail.com> wrote:
> Slot0 we think has a defective GRP, we removed and errors are gone.
> I have a
> new GRP being shipped for tomorrow.
> Thanks
>
> On Tue, Jul 21, 2009 at 5:07 PM, Aaron <dudepron at gmail.com> wrote:
>
>> Looks like a fabric problem.
>>
>>
>> On Tue, Jul 21, 2009 at 14:34, Chris Lane <clane1875 at gmail.com>
>> wrote:
>>
>>> All,
>>> I have a GSR 12008 with 2 GRP-B route processors. Running
>>> gsr-k4p-mz.120-32.S11.bin
>>>
>>> My GRP failed over about 45 minutes ago to the backup in Slot1
>>> from Slot0.
>>> I keep getting this in my logs.
>>> SEC 0:00:00:06: %MBUS-6-FIA_CONFIG: Switch Cards 0x1F (bit mask);
>>> Primary
>>> Clock CSC_1
>>> SEC 0:00:00:07: %FIA-3-HALT: To Fabric
>>> SEC 0:00:00:07: %FIA-3-PARITYERR: To Fabric parity error was
>>> detected.
>>> Request parity error interrupt = 0x4.
>>> SEC 0:00:00:07: %FIA-3-HALT: To Fabric
>>> SEC 0:00:00:07: %FIA-3-HALT: To Fabric
>>> SEC 0:00:00:07: %RP-3-FABRIC_UNI: Unicast send timed out (1)
>>> SEC 0:00:00:13: %RP-3-FABRIC_UNI: Unicast send timed out (1)
>>> SEC 0:00:00:23: %RP-3-FABRIC_UNI: Unicast send timed out (1)
>>> SEC 0:00:00:37: %IPC-5-REGPORTFAIL: Registering Control Port
>>> Id=0x1000003
>>> timeout=0x6
>>> -Traceback= 501F6650 505A3B90 505A3F4C 505A40D8 5059FCCC 502A02D8
>>> 502A02C4
>>> SEC 0:00:00:44: %RP-3-FABRIC_UNI: Unicast send timed out (1)
>>> SEC 0:00:01:08: %IPC-5-REGPORTFAIL: Registering Control Port
>>> Id=0x1000003
>>> timeout=0x6
>>> -Traceback= 501F6650 505A3B90 505A3BD8 502A02D8 502A02C4
>>> SEC 0:00:01:15: %RP-3-FABRIC_UNI: Unicast send timed out (1)
>>> SEC 0:00:01:39: %IPC-5-REGPORTFAIL: Registering Control Port
>>> Id=0x1000003
>>> timeout=0x6
>>> -Traceback= 501F6650 505A3B90 505A3BD8 502A02D8 502A02C4
>>> SEC 0:00:01:56: %RP-3-FABRIC_UNI: Unicast send timed out (1)
>>> SEC 0:00:02:10: %IPC-5-REGPORTFAIL: Registering Control Port
>>> Id=0x1000003
>>> timeout=0x6
>>> -Traceback= 501F6650 505A3B90 505A3BD8 502A02D8 502A02C4
>>> SEC 0:00:02:41: %IPC-5-REGPORTFAIL: Registering Control Port
>>> Id=0x1000003
>>> timeout=0x6
>>> -Traceback= 501F6650 505A3B90 505A3BD8 502A02D8 502A02C4
>>> SEC 0:00:02:48: %RP-3-FABRIC_UNI: Unicast send timed out (1)
>>> SEC 0:00:03:12: %IPC-5-REGPORTFAIL: Registering Control Port
>>> Id=0x1000003
>>> timeout=0x6
>>> -Traceback= 501F6650 505A3B90 505A3BD8 502A02D8 502A02C4
>>> SEC 0:00:03:43: %IPC-5-REGPORTFAIL: Registering Control Port
>>> Id=0x1000003
>>> timeout=0x6
>>> -Traceback= 501F6650 505A3B90 505A3BD8 502A02D8 502A02C4
>>> SEC 0:00:03:50: %RP-3-FABRIC_UNI: Unicast send timed out (1)
>>> SEC 0:00:04:14: %IPC-5-REGPORTFAIL: Registering Control Port
>>> Id=0x1000003
>>> timeout=0x6
>>> -Traceback= 501F6650 505A3B90 505A3BD8 502A02D8 502A02C4
>>> SEC 0:00:04:45: %IPC-5-REGPORTFAIL: Registering Control Port
>>> Id=0x1000003
>>> timeout=0x6
>>> -Traceback= 501F6650 505A3B90 505A3BD8 502A02D8 502A02C4
>>> SEC 0:00:05:02: %RP-3-FABRIC_UNI: Unicast send timed out (1)
>>> Jul 21 12:27:01.258 EDT: %RP-3-ERROR: Timed out while initializing
>>> IPC to
>>> standby RP in slot 0
>>> Jul 21 12:28:02.070 EDT: %MBUS-6-DEADSCDY: Standby RP in slot 0
>>> timed out,
>>> reset
>>>
>>>
>>> Is this because SLOT0 is hung, trying to become primary again yet
>>> not
>>> communicating with SLOT1 the active RP?
>>> SLOT 0 (RP/LC 0 ): Route Processor
>>> MAIN: type 19, 800-2427-03 rev F0
>>> Deviation: D070866
>>> HW config: 0x00 SW key: 00-00-00
>>> PCA: 73-2170-08 rev E0 ver 5
>>> Design Release 1.5 S/N SAD0745027R
>>> MBUS: MBUS Agent (1) 73-2146-07 rev B0 dev 0
>>> HW version 1.2 S/N CAT073504X3
>>> Test hist: 0x00 RMA#: 00-00-00 RMA hist: 0x00
>>> DIAG: Test count: 0x00000000 Test results: 0x00000000
>>> FRU: Linecard/Module: GRP-B=
>>> Route Memory: MEM-GRP-512=
>>> MBUS Agent Software version 2.68 (RAM) (ROM version is 3.47)
>>> ROM Monitor version 2.2
>>> Primary clock is CSC 1
>>> Board State is Route Processor Powered ( RP RDY ) *********
>>> SHOULDN'T
>>> THIS SAY STANDBY (STBY RP )
>>> Insertion time: 42w1d (00:56:55 ago)
>>> DRAM size: 536870912 bytes
>>>
>>>
>>> SLOT 1 (RP/LC 1 ): Route Processor
>>> MAIN: type 19, 800-2427-03 rev F0
>>> Deviation: 0
>>> HW config: 0x00 SW key: 00-00-00
>>> PCA: 73-2170-08 rev E0 ver 5
>>> Design Release 1.5 S/N SAD072000C3
>>> MBUS: MBUS Agent (1) 73-2146-07 rev B0 dev 0
>>> HW version 1.2 S/N CAT07100SFN
>>> Test hist: 0x00 RMA#: 00-00-00 RMA hist: 0x00
>>> DIAG: Test count: 0x00000000 Test results: 0x00000000
>>> FRU: Linecard/Module: GRP-B=
>>> Route Memory: MEM-GRP-512=
>>> MBUS Agent Software version 2.68 (RAM) (ROM version is 3.47)
>>> ROM Monitor version 2.2
>>> Primary clock is CSC 1
>>> Board State is IOS Running ACTIVE (ACTV RP )
>>> Insertion time: 42w1d (00:56:55 ago)
>>> DRAM size: 536870912 bytes
>>>
>>>
>>>
>>> Any help, suggestions greatly appreciated
>>>
>>> Chris
>>>
>>> --
>>> //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
> _______________________________________________
> 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/
More information about the cisco-nsp
mailing list