PNC-DUP (PNC Duplication)
Issue 1 May 2002
8-1295555-233-143
find no problems with the bus, then it is either the port board or the EAA. It
may be simpler to replace the port board than to request a PNC
interchange. However, if it is not clear which port board may be at fault, or
maintenance is being performed remotely, verify that the EAA is not at fault
by executing a PNC interchange. If the interchange solves the problem,
then the EAA is faulty. If the problem persists after the interchange, but
TDM bus maintenance finds no problem, then the port board is faulty.
Error Log Entries
Whenever a PNC interchange takes place, an error is logged against PNC-DUP
with a code that conveys information about the cause of the interchange and
which PNC became active. There are no alarms associated with PNC-DUP
errors, but there should be an alarm against the PNC component that drove the
interchange. There are no PNC-DUP test sequences, but status pnc will provide
information regarding the status of the PNCs. The information given in the
following tables will help to identify areas of the Alarm Log to be investigated to
find the source the problem.
Error Code
Aux
Data Error Code
Aux
Data
00000 (a) None 20200 – 20263 (s)
1
10000 – 10063 (b)
1
1. The Aux Data indicates which PNC became active after the PNC interchange: “0” denotes
PNC-A; “1” denotes PNC-B.
20300 – 20363 (t)
1
10100 – 10163 (c)
1
20400 – 20463 (u)
1
10200 – 10263 (d)
1
20500 – 20563 (v)
1
10300 – 10363 (e)
1
20601 – 20664 (w)
1
10400 – 10463 (f)
1
20701 – 20764 (x)
1
10500 – 10563 (g)
1
21000 – 21063 (y)
1
10601 – 10664 (h)
1
21100 – 21163 (z)
1
10701 – 10764 (i)
1
21200 – 21263 (aa)
1
11000 – 11063 (j)
1
21300 – 21363 (ab)
1
11100 – 11163 (k)
1
21400 – 21463 (ac)
1
11200 – 11263 (l)
1
21601 – 21664 (ad)
1
11300 – 11363 (m)
1
21701 – 21764 (ae)
1
11400 – 11463 (n)
1
51000 (af)
1
11601 – 11664 (o)
1
52000 (ag)
1
11701 – 11764 (p)
1
53000 (ah)
1
20000 – 20063 (q)
1
60801 (ai)
1
20100 – 20163 (r)
1
60800 (aj)
1
To Next Page
Loading...
