Initialization and Recovery
555-233-143
3-8
Issue 1 May 2002
MultiVantage Application Resets
■
Single-Process Restart
The system automatically performs these restarts logs them in the ECS
logger. Occurrences of single-process restarts can be viewed applying
“
tail
” or “
grep
” to the log file from Linux command line.
■
‘‘Reset Level 1 (Warm Restart)’’ on page 3-9
■
‘‘Reset Level 2 (Cold-2 Restart)’’ on page 3-10
■
‘‘Reset Level 4 (MultiVantage Application Reload)’’ on page 3-11
When the system is powered up, or when it experiences a catastrophic fault that
interrupts its basic functions, it undergoes a reboot. In addition to reboot, there
are several less severe resets available for the system to recover from less
disrupting errors. The technician can also initiate these resets with a command.
!
CAUTION:
Multivantage application resets can have wide-ranging disruptive effects.
Unless you are familiar with resetting the system, follow normal escalation
procedures before attempting a demand reset.
NOTE:
If a reset fails to recover normal system operation, the firmware that controls
reset will escalate to the next higher level, up to reboot if necessary. Hot
restarts are not supported for S8700 Multi-Connect servers. An on-demand,
planned, or scheduled interchange results in a warm restart of the standby
server if it is in a refreshed state, or a reboot if it is not refreshed.
When a reset occurs (including an interchange), an error is logged against the
SYSTEM maintenance object (MO). The error code gives information about the
cause of the reset. Information about the reset is also logged in the initcauses
log. (See
‘‘display initcauses’’ on page 7-135
.)
EPNs can also undergo individual resets. These are described in:
■
‘‘reset ipserver-interface’’ on page 7-260
■
‘‘EXP-INTF (Expansion Interface Circuit Pack)’’ on page 8-762
■
‘‘EXP-PN (Expansion Port Network)’’ on page 8-821
For EPNs in high- and critical-reliability systems, IPSIs can also undergo
interchanges. These are described in:
■
‘‘IPSV-CTL (Ipserver Interface Control)’’ on page 8-950
For critical-reliability systems, PNC interchanges are described under
Summary of Contents for S8700 Series
Page 50: ...Maintenance Architecture 555 233 143 1 26 Issue 1 May 2002 ...
Page 74: ...Initialization and Recovery 555 233 143 3 12 Issue 1 May 2002 ...
Page 186: ...Alarms Errors and Troubleshooting 555 233 143 4 112 Issue 1 May 2002 ...
Page 232: ...Additional Maintenance Procedures 555 233 143 5 46 Issue 1 May 2002 ...
Page 635: ...status psa Issue 1 May 2002 7 379 555 233 143 status psa See status tti on page 7 406 ...
Page 722: ...Maintenance Commands 555 233 143 7 466 Issue 1 May 2002 ...