thread690-994837
This is a g3r v10
The errors are on multiple SNIs and point to SNC problem.
The visual indications on the SNCs are both have green leds lit stdy and slot 02E12 has steady yellow (active?) where the switch shows 02E10 as being active similar to mikeydidit's post from above thread.
"At one time (around V6 to V8), their was a problem with the switch node clocks. The switch would see the standby as active and the active as standby. The way to resolve was to "sta swi" and look at what the switch sees as the active clock. Then look at the cabinet itself, and see which one was active (yellow light on the active). If it is running on the board the switch sees as standby, pull the active SNC board and that would swap it to the right board. That is what it took to resolve this, and yes I had to do this quite a few times until I went on to later versions of software."
Mike Jones
LSUHSC
Before being on site and looking at the leds I had tried testing boards, busy and release 02E12 and set switch node clock which aborts and "try later".
There have been no service interruptions as yet and am a little nervous just pulling the board in 02E12 to force it to the one it thinks is active.
Would this cause a service outage?
Any thoughts or comments welcomed
Thanks
Les
This is a g3r v10
The errors are on multiple SNIs and point to SNC problem.
The visual indications on the SNCs are both have green leds lit stdy and slot 02E12 has steady yellow (active?) where the switch shows 02E10 as being active similar to mikeydidit's post from above thread.
"At one time (around V6 to V8), their was a problem with the switch node clocks. The switch would see the standby as active and the active as standby. The way to resolve was to "sta swi" and look at what the switch sees as the active clock. Then look at the cabinet itself, and see which one was active (yellow light on the active). If it is running on the board the switch sees as standby, pull the active SNC board and that would swap it to the right board. That is what it took to resolve this, and yes I had to do this quite a few times until I went on to later versions of software."
Mike Jones
LSUHSC
Before being on site and looking at the leds I had tried testing boards, busy and release 02E12 and set switch node clock which aborts and "try later".
There have been no service interruptions as yet and am a little nervous just pulling the board in 02E12 to force it to the one it thinks is active.
Would this cause a service outage?
Any thoughts or comments welcomed
Thanks
Les