Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

err4286 12

Status
Not open for further replies.

westcoaster

Technical User
Sep 26, 2002
218
CA
err4286 12
Message count on the loop exceeds the threshold value.

Action: refer to any OVD messages previously printed, and check the hardware for defects that generate an overload condition. Rearrange the tn's to another location or they may be disabled. Reconfigure the loop.

..............................................................
I am having a problem (opt11c rls 21) where cards 13, 14, 15, and 16 are disabling them selfs. the only way to get them working again is to ini the switch and enable the cards in ld 32. If I don't do the ini the cards show idle but the sets don't work. I am not able to do an idu on those sets either.

Would this err have anything to do with my problem?
 
Hi,

when the cards do not enable, what is the status of the fibre link??

Do you have any other cards in the cabinet, and do they work fine?


Marc D.

If Bill Gates had a nickel for every time Windows crashed... Oh wait, he does...
 
there are cards in slots 11, 12, and 17. they work fine. I had replaced the fibre cord and the fibre receiver in the expansion cabnet. made no diffrence. when the cards would be down npr0000(ld 32 program identifier) and npr0003(illegal command) constantly scrolling on the screen of the terminal.
It appears like I have stablised the problem for now. I deleted several tn's that were programmed but had no sets installed. I also removed all midnight routines as well as the software audit. it appears the cards were going down every three hours. I was able to have them run all last night without a problem.
we are in the process of upgrading the MM 12 to call pilot and the switch software to succession. what has started all this is when I loaded the callpilot migration utility onto the MM.(courtesy down the MM ld 48 dis aml 9 follow the directions to turn the tape on before powering up, only to find the MM will not boot of the tape in this manner. Jack around a bunch more, call tech support and find I need to turn the tape drive on after powering on the MM and enabling the aml link) we have done nothing to the switch, nor have we installed the callpilot yet.
Oh, so much to relate..., so little time and space. (i'm not a fast typer)
 
You upgraded the switch to succession from what release? If you upgraded from below 25, did you replace the software daughterboard on the SSC? Releases below 25 have a 40 Mb daughterboard (24 sometimes have a 48Mb), but you need a 48Mb with Succession.

Do you have a third cabinet?? And do you use a single or dual fibre daughterboard on the ssc?


Marc D.

If Bill Gates had a nickel for every time Windows crashed... Oh wait, he does...
 
The switch hasn't been upgraded yet. the only thing that has happened so far is, the callpilot to MM tool has been uploaded to the MM and the customer info has been migrated to tape.

no third cabnet. only the main and an expansion
there is only a single fibre daughter board.

to do the sucession upgrade there is an upgraded daughterboard and a pcmcia.
 
so far it appears to be running just fine...
couple of thoughts....

1. it's saturday and the switch is slow, the cpu has time to process whatever is ailing it as it doesn't have to deal with the other calls.

2. one of the users sets has corrupt data on it, user pushes a button and... (user not working saturday)

3. The software audit didn't like the tn's that were programmed but didn't have sets installed. and/or there was something corrupt with one of them.

I come from a norstar background the opt 11 is a diffrent animal...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top