I have a 81c with a superloop disabling itself (FHW000) What would be the best way of determing if it is the NET card or Controller card? VER. 3621 REL. 4  

Replace one then the other if the first doesn't fix it.  Probably the nt8d04.

Roger that, my only problem is down time with 216 users and no maintenance window.

Thanks though.

had a shelf that would not come up at all before, had to pop each IPE card (except Xpec) till I found the bad one on the shelf....

might not apply to your problem

__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius

Just making sure, in ld 97 superloop 68 is controller 6. Is controller card 6 in the ipe cabinet which has 68 0 or 68 1 or is it somewhere less obvious? Its a remote site. Trying to gather all I can before I go there.   

The controller is in the ipe remote shelf.  When you look at the controller's faceplate it wil flash the number unless it is down.  If you are replacing the network card both shelves will be down.  I would start with the controller in this case.

I beleive there is one in 68 0 and 68 1. Can one controller take out the whole supl or does that info. point more to a network card?
The error code BERR600 indicates NCB 0 2 LOOP 68  at address 0x9120 in Group 2.

Ok so 68 0 is controller 3 (flashes c0 and 03) 68 1 is controller 6 (flashes c0 and 06)duh!. Still not sure if one controller will take out the whole supl. Cards on order will update after fix.

I appreciate you'lls help.

You have one controller per shelf. Swapping out the controller for shelf 0 will have no affect on shelf 1 and vice versa. Now replacing the superloop network card will take out both shelves.  

Like I said earlier, probably the nt8d04.  You can run a test in ld 39 that will look at every card in a designated network group ie. group 2 shelf 0.  TEST BKPL 2 0 would be the command.

Yes sir I'm with that. I was wondering though through all the err codes I've been searching, which one do I replace if the whole superloop is disabling at once?

If you know how to count the slots in the network group then the test bkpl is a nice tool.  The results are given as 0-31 pass/fail.  If 68 fails replace it.

Yes the entire superloop will be down, if you have a shelf 0 and a shelf 1 both will be down if in seperate shelves.

Thanks,

Buddy

Linked in Profile
http://www.linkedin.com/in/buddyhassell
 

Superloop card NTBD04 was replaced yesterday. Seems to have taken care of the entire supl disabling. Thanks for all the input on that. Can't seem to be able to stop the NPR504 errs though. After enabling/disabling/testing just about everything LD 32,34,38 and 46 has to offer still they come. Is there a way of deciphering what exactly is happening below?

  *   NPR504 09/05/12 12:26:01 168199366                                
OPRDATA: 001

*   NPR504 09/05/12 12:26:01 168199367                                
OPRDATA: 016

*   NPR504 09/05/12 12:26:01 168199368                                
OPRDATA: 017

*   NPR504 09/05/12 12:26:01 168199369                                
OPRDATA: 032

*   NPR504 09/05/12 12:26:01 168199370                                
OPRDATA: 033

*   NPR504 09/05/12 12:26:01 168199371                                
OPRDATA: 048

*   NPR504 09/05/12 12:26:01 168199372                                
OPRDATA: 049

*   NPR504 09/05/12 12:26:01 168199373                                
OPRDATA: 064

*   NPR504 09/05/12 12:26:01 168199374                                
OPRDATA: 065

*   NPR504 09/05/12 12:26:01 168199375                                
OPRDATA: 080

*   NPR504 09/05/12 12:26:01 168199376                                
OPRDATA: 081
 

That error references wrong commands in the conference/tds loads.  It's just rolling or are you entering something?

Yeah thats the thing. Its not coming from a keyboard.

That looks like it might be the history file.

The morning will be here soon enough. Will see what the nightly does do it. Out and thanks.

To no surprise, NPR504s are still there. History file problem does make sense, NPRs are all the same every time. Would this be possibly a INI fix or can something be done in one of the many existing lds?  

I would bet it will INI on its own if you dont schedule one soon.

To look ofr the time your routines run

ld 22

prt

ovly

look for todr

Thanks,

Buddy

Linked in Profile
http://www.linkedin.com/in/buddyhassell

you can try the HALT command from OVL000, but it won't fix the "stuck" midnight routine,

__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius

oops, thought you had a stuck midnight routine running.... sorry.

__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius

We have three 81c switches here and all of them are producing the *NPR504 msgs.
I only see them after a stat in load 32, they follow the loop status. Annoying more than anything but do want to get them cleaned up. The switches were all recently (six months) updated with the latest deplist.

Think I'll disable the packs and reseat all the cards on Monday. Thanks!!

just to clarify, are you saying that you are typing in STAT (and hitting enter) in LD 32? (to produce these messages)

or are these message just showing up on their own?

__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius

That is normal. Didn't know you were typing stat.

I can do a stat and enter in ld 32 and they are at the bottom.

LD 32
STAT

000 = XCT-TDMF LOOP
00 DSBL 00 BUSY
* NPR504 11/05/12 12:44:59 168200013
OPRDATA: 000

001 = XCT-CNFC LOOP
00 DSBL 00 BUSY
002 = MISP ( BRIL ) LOOP
00 DSBL 08 BUSY
004 = MISP ( BRIL ) LOOP
00 DSBL 08 BUSY
006 = MISP ( BRIL ) LOOP
00 DSBL 08 BUSY
008 = SUPER LOOP
000 DSBL 001 BUSY
012 = SUPER LOOP
000 DSBL 003 BUSY
016 = XCT-TDMF LOOP
00 DSBL 00 BUSY
017 = XCT-CNFC LOOP
00 DSBL 00 BUSY
018 = MISP ( BRIL ) LOOP
DSBL NOT RESPONDING
020 = MISP ( BRIL ) LOOP
00 DSBL 08 BUSY
022 = PRI TRK LOOP
00 DSBL 00 BUSY NPR301
023 = PRI TRK LOOP
00 DSBL 03 BUSY NPR301
024 = MISP ( BRIL ) LOOP
00 DSBL 08 BUSY
026 = MISP ( BRIL ) LOOP
00 DSBL 06 BUSY
028 = SUPER LOOP
000 DSBL 001 BUSY
032 = XCT-TDMF LOOP
00 DSBL 00 BUSY
033 = XCT-CNFC LOOP
00 DSBL 00 BUSY
034 = PRI TRK LOOP
00 DSBL 00 BUSY NPR301
035 = PRI TRK LOOP
00 DSBL 00 BUSY NPR301
036 = SUPER LOOP
000 DSBL 005 BUSY
046 = PRI TRK LOOP
00 DSBL 05 BUSY NPR301
047 = PRI TRK LOOP
00 DSBL 00 BUSY NPR301
048 = XCT-TDMF LOOP
00 DSBL 01 BUSY
049 = XCT-CNFC LOOP
00 DSBL 00 BUSY
050 = PRI TRK LOOP
00 DSBL 00 BUSY NPR301
051 = PRI TRK LOOP
00 DSBL 01 BUSY NPR301
052 = SUPER LOOP
000 DSBL 001 BUSY
062 = PRI TRK LOOP
00 DSBL 00 BUSY NPR301
063 = PRI TRK LOOP
00 DSBL 00 BUSY NPR301
064 = XCT-TDMF LOOP
00 DSBL 00 BUSY
065 = XCT-CNFC LOOP
00 DSBL 00 BUSY
066 = PRI TRK LOOP
00 DSBL 00 BUSY NPR301
067 = PRI TRK LOOP
00 DSBL 00 BUSY NPR301
068 = SUPER LOOP
000 DSBL 016 BUSY
078 = PRI TRK LOOP
00 DSBL 00 BUSY NPR301
079 = PRI TRK LOOP
00 DSBL 00 BUSY NPR301
080 = XCT-TDMF LOOP
00 DSBL 00 BUSY
081 = XCT-CNFC LOOP
00 DSBL 00 BUSY
082 = PRI TRK LOOP
00 DSBL 00 BUSY NPR301
083 = PRI TRK LOOP
00 DSBL 00 BUSY NPR301
084 = SUPER LOOP
000 DSBL 030 BUSY
.
* NPR504 11/05/12 12:44:59 168200014
OPRDATA: 001

* NPR504 11/05/12 12:44:59 168200015
OPRDATA: 016

* NPR504 11/05/12 12:44:59 168200016
OPRDATA: 017

* NPR504 11/05/12 12:44:59 168200017
OPRDATA: 032

* NPR504 11/05/12 12:44:59 168200018
OPRDATA: 033

* NPR504 11/05/12 12:44:59 168200019
OPRDATA: 048

* NPR504 11/05/12 12:44:59 168200020
OPRDATA: 049

* NPR504 11/05/12 12:44:59 168200021
OPRDATA: 064

* NPR504 11/05/12 12:44:59 168200022
OPRDATA: 065

* NPR504 11/05/12 12:44:59 168200023
OPRDATA: 080

* NPR504 11/05/12 12:44:59 168200024
OPRDATA: 081

Ok well, if that's normal nothing to worry about then. I'll just add that to the "can clear alarm and comes right back" list.