Lucent Technologies 5ESS-2000, Инструкции по эксплуатации и техническому обслуживанию

Страница: 123 / 1421

update in the 5ESS-2000 switch.
If all software updates in the active log have been made official and memory space used by the old version of the
replaced functions has been reclaimed, the history of these software updates may be stored in the archive log to
conserve disk space. Subsequently, these histories may be printed on the MCC printer by typing ``9104,backlog''.
The updates shown in Figures 5-6 and 5-7 are in a temporary state. The most important status flag is the
INSTALLED flag. An administrative module initialization can cause temporary updates in the administrative module
to be removed. Consequently, the INSTALLED flag is reset and is cleared from the software update history after
completion of the initialization. An administrative module initialization does not affect temporary updates installed in
switch modules. The history of a software update which updates switch modules is global to all switch modules.
Therefore, any interface module initialization does not cause the INSTALLED flag to be reset for a temporary switch
module update.
The process type is described more explicitly by using the correct process types (see Figures 5-6 and 5-7 ). An
OFC flag is added to the history entry after the update is made official. For a function replacement, an AUDT flag is
added to the history after memory space used by the version of the replaced function(s) is reclaimed. If the
reclamation of memory space fails, an AUDABT flag is added to the history entry instead. The AUDABT flag is set
only when the reclamation of non-AM updates fails.
A file replacement may be verified by checking the time stamp and file size on the target file at the directory where
the original file is located. When a function replacement is installed, the new address of the function is printed on the
printer. The new address may be used to establish a breakpoint to detect when the replacement function is called.
If an update is targeted for multiple switch modules, two pieces of information are available to verify that the update
is in all of the target modules. The first piece of information is the UPD Module Report. This report is generated and
printed on the MCC printer automatically after a temporary update has been successfully applied, but one or more
modules did not receive the update. The report identifies all modules which received the update and all modules
which did not receive the update. If all modules received the update, the report is not printed.
The other piece of information is available on MCC Page 1800 (Figure 5-8 ). Box 10 is called UPDBACKOUT. This
indicator shows whether or not recently applied SM program updates are currently loaded or backed out.
Both MCC Pages 1850 and 1851 (Figures 5-9 and 5-10 ) are added for communication module processor
(CMP) inhibit and recovery control. Box 10 is called UPDBACKOUT. If the selected module
should have the update,
the box will be lighted.
Menu Page 1950 also provides the ability to detect update inconsistencies in the system. Poke 9200 (VERIFY
INCONSISTENCY) provides this capability. For example, if a temporary update is booted out of the administrative
module as a result of an initialization and if a switch module is isolated when an update is installed in all switch
modules, an update inconsistency occurs. In this case, the isolated module does not receive the update. The use of
poke 9200 generates the report shown in Figure 5-11 .
Poke 9300 (RECOVER FORWARD) may be used from menu Page 1950 to reapply all temporary updates in an
inconsistent state. Poke 9400 (RECOVER BACKWARD) removes the temporary updates, starting from the last one
in the system. If there is no inconsistency, a message will print to the ROP. Both pokes automatically determine the
starting and ending points of the software update sequence so that a recovery process can be performed.
As the number of software updates installed in the system increases, disk space used by the history files grows.
When all software updates have been made official and memory space used by the old version of the functions is
reclaimed, most software update history can be saved in an archive file in a condensed format. This can be done by
entering the
UPD:REDUCE command manually. There is no corresponding poke on the 1950 page.
On menu Page 1950, poke 9600 may be used in clear disk space occupied by the software updates after the
software update is made official. An automatic check is made to verify that the specified software update was made
235-105-210 October 1999
Copyright © 1999 Page 15