GTD5guru Tips

GTD5GURU will be discontinued at the end of 2023.

Starting January 1st, 2024, the gurus will no longer be available to assist you and this website will be taken offline.

UP ON OUR SOAPBOAX

Coming from the 'old days', we feel that the Central Office maintainer should be able to keep their switches clean and operating properly. Lack of training and guidance hinder this. A mentality also exists in some of you that you don't need to work on anything unless someone tells you to. There are some GTD-5's out there with virtually no alarms. If your DUMP STAT SYSA gives you more than 10 items, you have switch issues that need to be looked into. If you need a ticket, call Tier 1 or Tier 2 and ask them to create a ticket for you. Don't just ignore your problems.

MP won't run Active aka: SMA SYNDROME 0.032 MICROPROCESSOR FAILURE

A common problem that occurs in Microprocessors (MP) is that they may ATP and run all day INS.SBY but if they go active, they will kick out a SMA 0.032 MICROPROCESSOR FAILURE syndrome and recover. Sometimes it will just copy switch, recover the MP as ATP and return it INS.SBY. Other times it may take the MP to OOS.SYS. In almost all cases. if you PUT INS the MP, it will ATP and return to INS.SBY.

Every night just after midnight the switch runs routines which causes the ACTIVE copy of every processor to switch to the other side. So a faulty microprocessor card will go INS.ACT, take a SMA 0.032, recover and copy switch back to the other side. Sometimes this happens almost immediately, other times it may take hours to occur.

This is almost always caused by a bad microprocessor card. There are four different types of microprocessor cards FB-16280, FB-16281, FB-16581 & FB-16583. It may be easier to just go look at the card to see which type of spare card you will need.

The microprocessor card is the first double height card on the far left of the shelf. APC & TPC slot 14. TCU slot 11, RSU & RLU slot 5. Newer frames have different slot numbers, but it will be the first double height card on the far left of the shelf.

You can also roll the card with another processor that uses the same type of card and see if the problem follows the card. This is always good advice because "spare card" does not equal "good card". Before you spend the time tracking down a spare, rolling the card will make sure you are tracking down the card you need. Hey, it could be something else causing the problem, right?

BUNW OOS

The BUNW is the Base Unit Network. That means it is everything that PCM flows through. A BUNW diagnostic takes a long time because it is sending PCM from every FIU to every FIU and checking to make sure it gets there intact with no alarms. The BUNW also likes to go Out Of Service (OOS) due to problems it sees in any portion of the network. If software cannot specifically identify the cause, the BUNW is often taken OOS. When a network copy is trying to return INS, software checks that both copies are doing the same thing. If software detects that the two copies do not agree the BUNW goes OOS. That disagreement could be something as minor as a span alarm seen on one copy that is not seen on the other copy.

MXU OUTAGES Can they be degrown?

Decommissioned MXU's showing in OUTAGE. The first thing that YOU need to do is make sure all of the lines have been removed from the MXU. Sometimes stragglers are left behind in the database (even if there are no jumpers or no MXU exists.) If the database still has DN's pointing to the MXU, the MXU cannot be degrown.

EXAM EN.MXUx.*

Use the command above (replace the x with the MXU number) to see if any DN's remain assigned to the MXU. It is your responsibility to research any remaining DN's or delegate to your service office personnel. You need to get these DN's deleted from the MXU before anything further can be done.

Once the EXAM command shows RANGE PROCESSING COMPLETE all of the lines have been output. If no lines were identified, then the MXU can be degrown.

Send an email to support@GTD5Guru.com asking us to degrow your MXU and we will get er' done.

NOTE: Some MXU's have spare line switching (SPLN). This does not count as a DN assigned to the MXU. This will be removed when the MXU is degrown.

I@14:17:23 EXAM EN.MXU27.*

OK JOB 0037 ASSIGNED

R@14:17:24 EXMO113 JOB 0037 12/04/22 CLLISTXADS0

EN.MXU027.0000.00.000.00 UNAS SPLN TYPB

R@14:17:33 EXMO113 JOB 0037 12/04/22 CLLISTXADS0

RANGE PROCESSING COMPLETE

SPARE CARDS

Spare cards are spare. That doesn't mean they are good. When troubleshooting, spare cards are your enemy. It is best to roll cards between similar hardware to identify exactly which spare card you need to fix the trouble. Try to roll cards back to their original locations. If the spare fails differently than the original it is probably bad, Roll again to prove the spare is bad. Don't install multiple spares at a time.

OOS.TEMP means what?

When you see something OOS.TEMP it just means there is something else Out Of Service that is preventing this from being INS. Your challenge is to find out what is OOS.SYS or OOS.MM that is causing other things to be OOS.TEMP. The most common example of this is a network HID being OOS and causing everything else on that network copy to be OOS.TEMP. If an ACU or DCU goes OOS, all ACU, DCU, TSW, SSW, BUNW will all show OOS.TEMP. To find the cause for a network TEMP issue, use the command

DUMP STAT BNWA SOUR

There are similar commands that can show you why any light on the ACD Panel is lit. Got a light and you want to know why it is on, send us an email and tell us what light it is.

Page updated

Google Sites

Report abuse