DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126 Issue 4
June 1999
Maintenance Object Repair Procedures
9-1506STBY-SPE (Standby SPE Maintenance)
9
b. Presenc e of th is error indic ates th at the st andby SPE has is b usied out.
When busied out, standby SPE’s health is kept at the level
partially
functional
and memory shadowing is kept off.
c. Error 103 indicates that a spontaneous interchang e has taken place. This
lower s the now standb y SPE’s sta te-of- health t o
partially functional
, raises
a MINO R alarm a gainst the stan dby SPE, a nd inv okes rec ent int erchan ge
mode (anti-thrashing). After one hour, or enter ing Test spe-standby long
or busyout spe-standby, the alarm clears, recent interchange mode is
lifted, and the standb y’s state of health assumes the appropriate value
(usually
functional
).
After a spont aneous SPE i nterch ange h as occ urred, the Alar m Log r etains
a reco rd of an y MAJOR ON -BOARD al arm ag ainst an SPE compo nent tha t
took place before the interc hange. This record is retained for three hours
and may indicate the c ause of the interchange when testing is not
possible or conc lusive. If handshake has not been restored (c heck with
status spe), rep lace t he alar med ci rcuit p ack o n the sta ndby SPE. If
handshake is up, and suc h an alarm is logged aga inst SW-CTL, replace
the standby MSSNET circuit pack. If hand shake is up, and such an alarm
is logged ag ainst one of the other SPE components, execute a test long
clear of the alarmed standby c omponent and follow repair instructions for
that maintenance object.
d. This error represents inhibiting of memory shadowing b y the standby SPE.
If this error occurs acc ompanied by error 514, then the standb y SPE has
reset, so wait 5 minutes for this condition to c lear. If the 257 error persists,
or did not occ ur with a 514, then how you proceed dep ends on whether
handshake is up. If handshak e is not up, deal with the handshake failure
problem (see the section
Resolving Handshake Failure
). If handshake is
up, look for errors or red LEDs indicti ng the standby packet-inter face
circuit pack or either of the duplication-interface c ircuit packs. If such
problems exist consult the ap propriate MO documentation. When no
PKTINT errors or alarms are present, the PKTINT may still be the cause of
the problem. Try reset packet-interface [a|b] to reset the standby PKTINT
and wait two minutes, after which shad owing should be turned on. If 257
continues to persist, with hand shake up, and no associated
packet-interface or d uplication-interface p roblems, escalate the problem.
e. This error indicates that shadowing could not b e turned on due to a
problem with the dup lication-interface hardware. Busyout spe-standby,
run test duplication-interface long, and consult the DUPINT section.
Once all tests of duplic ation-interface have passed, and all alarms against
it have cleared, release spe-standby and wait 10 minutes for normal
initialization to complete. If error 260 rec urs, escalate the problem.
f. This err or indi cates that the stand by SPE has b een res et. Wait 5 minute s
and then use "status spe" to see if the standby SPE is refreshed. If so,
ignore the 514 error. If not, or if 514 recurs freque ntly, then lock the
stand by SPE and proc eed to t rouble -shoot it with t he SPE-Down Interf ace.