Ok all, we are at our wits end on this one. We have installed a fiber remote at a college that will not run clean. This is an 81C on Release 25. Below are the errors we take periodically:
% XMI000 92 : OIF: switched to prim
% XMI000 92 : OIF: no active link
% XMI000 92 : OIF: switched to prim
% XMI000 92 : OIF: no active link
% XMI000 92 : OIF: switched to prim
So far we haven’t developed any sort of pattern as to when these errors occur. Currently I'm on a theory of them only occurring when Core 1 and Clock 1 are active so I have locked in Core 0 and Clock 0 until they reappear. The only time we have been able to keep it up and clean is when we take the remote cabinet to the switchroom and direct connect it to the network card. That automatically makes you think “Ahh, the fiber is bad”. Well, now we aren’t so sure. Below are the steps we have taken to try to get this remote running clean:
1. We have replaced the network card, controller card, and both EOI boards on each end twice.
2. We have replaced the fiber jumpers on each end.
3. We have moved the network card from the left slot of Loop 92 to the right slot. (there are no more Superloops left without moving some cards around)
4. We have replaced the power supply in the remote cabinet
5. We have had the fiber cable contractors come out and test the fiber and they assure us it is clean and gave us the readings from the test equipment.
6. We moved the remote cabinet to another building that has an existing fiber remote that has always run clean. The new remote cabinet took errors in that building as well over that fiber
7. As stated above, we have taken the remote cabinet to the switchroom and direct connected it to the network card. It hasn’t given errors in this setup but now we aren’t sure we left it there long enough.
Have any of you seen these errors before? Based on the steps we have taken, do any of you have any other ideas?
War Eagle!
Lions Baseball '09!
% XMI000 92 : OIF: switched to prim
% XMI000 92 : OIF: no active link
% XMI000 92 : OIF: switched to prim
% XMI000 92 : OIF: no active link
% XMI000 92 : OIF: switched to prim
So far we haven’t developed any sort of pattern as to when these errors occur. Currently I'm on a theory of them only occurring when Core 1 and Clock 1 are active so I have locked in Core 0 and Clock 0 until they reappear. The only time we have been able to keep it up and clean is when we take the remote cabinet to the switchroom and direct connect it to the network card. That automatically makes you think “Ahh, the fiber is bad”. Well, now we aren’t so sure. Below are the steps we have taken to try to get this remote running clean:
1. We have replaced the network card, controller card, and both EOI boards on each end twice.
2. We have replaced the fiber jumpers on each end.
3. We have moved the network card from the left slot of Loop 92 to the right slot. (there are no more Superloops left without moving some cards around)
4. We have replaced the power supply in the remote cabinet
5. We have had the fiber cable contractors come out and test the fiber and they assure us it is clean and gave us the readings from the test equipment.
6. We moved the remote cabinet to another building that has an existing fiber remote that has always run clean. The new remote cabinet took errors in that building as well over that fiber
7. As stated above, we have taken the remote cabinet to the switchroom and direct connected it to the network card. It hasn’t given errors in this setup but now we aren’t sure we left it there long enough.
Have any of you seen these errors before? Based on the steps we have taken, do any of you have any other ideas?
War Eagle!
Lions Baseball '09!