DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126 Issue 4
June 1999
Maintenance Object Repair Procedures
9-1504STBY-SPE (Standby SPE Maintenance)
9
no problems are revealed in the memor y long test sequence, b ut memory refresh
persists in failing with error 1281 error aux 1383, esc alate the problem.
Error code 1281 with auxiliary data 1381 ind icates that refresh of the
packet-interface d ual port RAM has failed. If this p ersists, one should look for
prob lems with e ithe r act ive SPE or stan dby SPE pac ket-i nter fac e boa rds. Follow
the procedures outlined in PKT-INT to fully test the active SPE’s Packet-interface.
Note t hat, s ince the s tand by SPE is not re fresh ed, o ne ca nnot exec ute th e lon g
demand test sequenc e on the standby Packet Interfac e. One can however
trigger a reset of that circu it pack. If the active PKT-INT passes all tests of the
long sequence and if the standby PKT-INT successfully resets, the p roblem
should clear. If error 1281 aux 1381 p ersists, escalate the problem .
Error code 1281 with auxiliary data 1380 in dicates that memory shado wing was
turned off during refresh and the refresh has therefore terminated in failure. This
situation should be treated as a shadowing failure and approached as described
in the section

Resolving Shadowing Failure

. If memory shadowing is restored , but
refresh again fails with code 1380, es calate attention to the problem.
One particular way memory o r PKT-INT refresh can be led to fail is by inserting
one of these circuit pac ks into its slot without powering d own the carrier. If this
happens, it may be nec essary to cycle p ower on the given carrier and let the
LMM run all tests of components on the c arrier to clear the probl em. If such an
SPE is in standby mode, reset spe-standby 4 would also cause the appropriate
initialization to occur. Always follow the l ock-and-power-d own approach to
replace circuit packs on the standby SPE.
Resolving Poor Health
It ca n hap pen t hat a stand by SPE i s pro perl y mai ntain ing h ands hake
communication, shadowing is on and the standb y is fully refreshed, but for some
reason the SOH of that standby SPE remains at a level other than
functional
.
For example, in a heavily loaded system, th e standby SOH may temporarily stay
at
not refreshed
, but eventually it should c lear. Once refresh completes, system
software begins an effort to improve the standby SOH from
not refreshed
to
functional
. This effort can be delayed , but within a few minutes one should see
the change. If one sees an ind efinite persistence of this health level, i n an
otherwise perfect stand by SPE, escalate the problem. This should be an
extremely rare event.
If the standby SOH Stays at
partially functional
, either the standby SPE is in

recent interchange mod e

or there is a major alarm against some criti cal standby
component (see the table ab ove). For the first case, verify the situation with
status spe and then clear the recen t interchange mode b y executing test
spe-standby long. Wait until at least the first four tests of the sequence
complete, then canc el out of the command. The standb y SOH should eventually
be raised to

functional.

In the second case, c heck the alarm log to see if there is
any ma jor al arm a gain st any com pone nt of t he sta ndb y SPE. If you fi nd on e, fi x