Procedures. The appendices in this IP relating to retrofit are high level outlines and
are intended only as a supplement to the retrofit manual.
2.12.6 Software Release Update
A software release update is performed to transition from one software release text
load to another. To perform a software release update, see 235-106-20X (whereX=the
document number associated to the applicable software release), 5ESS Switch
Software Release Update Procedures.
2.12.7 Software Update
2.12.7.1 Software Update Download
Software Updates (SUs) on the ASM can automatically be sent to the Host and the
DRMs in the Switching Complex using the tool dsdownload. Separate directories are
provided for the Host and each DRM’s SUs. These directories are
/app/su/download/3B and /app/su/download/VCDX. SUs are sent to the Host
Administrative Module (AM) over the DCI link, and to the DRMs via the Switching
Complex data and transmission network. On the Host AM and DRMs, the SUs are
placed in /etc/bwm.
Note: To download TMP or Unofficial Craft SUs, (refer to procedure - Handling
5ESS TMP and Unofficial CRAFT SUs in the ASM User’s Guide.)
After an SU has been successfully sent to the Host and all DRMs in the Switching
Complex, it is deleted from the ASM disk.
Note: SFID 320, “Feature Deployment on ASM,” must be active on the Host and
each DRM for the files to be automatically sent.
2.12.7.2 Software Update Automation
Once an SU has been sent to the /etc/bwm directories, the SU can be applied by
either using a cut-through to each Host/DRM and manually applying the SU or using
SU Automation to automatically apply the SU to the Host and all DRMs in the
Switching Complex.
This feature can only be used for SU installation on the Host and all the DRMs in the
complex together. If SU installation on only the Host or a subset of DRMs is desired,
then it must be done via a cut-through to each Host/DRM’s MCC.
An SU can be scheduled for automatic installation across the Switching Complex only
if the Host and all DRMs are on the same release and SU level. If not, attempts to
schedule an SU for automatic installation will be rejected.
SU automation commands are sent to the Switching Complex by writing them to a file
(referred to as an "automation command file" or "command file") and placing the file in
the ASM directory /app/su/automation/autocmd/. The command file will be
automatically sent to the Host and all active DRMs. After the file has been sent, it is
moved to the directory /app/su/automation/sent.
Note: The user is responsible for verifying the form and syntax of SU Automation
command files. If invalid SU Automation commands are included in a command file,
they will simply not be processed and no error output will appear.
On the Host and each DRM, the commands in the file are executed as if they were
inputs to the 1941 page on the MCC. The changes to the state of SU automation are
recorded in a results file on the ASM. If any error conditions occur, such as a
communications failure between the ASM and the Host or a DRM, it will also be
235-200-150
Feburary 2007
5ESS
®
SWITCH DISTINCTIVE REMOTE MODULE
Issue 3.00O Page 2-63
To Next Page
Loading...