About Software and Database Files
is contained in the standby area until a different file version is installed in the standby
area. The standby software files and database files can be activated individually.
The file area is an intermediate storage area located on a RAM disk (RDISK) on the NCU,
and is cleared on reboot. It is used to download software and database files from external
servers to the NE, and to upload backup database files to external servers.
Files can be downloaded and uploaded by using file transfer protocol (FTP) or secure
copy protocol (SCP). Like SSH, SCP uses secure socket layer (SSL) technology. NEs
with a first generation NCU are not capable of providing FTP or SCP server functionality,
for example, when serving the role of GNE for other NEs. Second generation NCUs can
act as an FTP or SCP servers, as they contain a stronger processor with sufficient
random-access memory (RAM). For more information about which NCUs are of first
generation or second generation, refer to “NCU Troubleshooting” on p.509.
Database backup files can alternatively be stored in a file area on the SCU, and restored
from this area on the SCU. This requires an SCU-II, an SCU-S, or an SCU with hardware
revision 2.01 or higher.
Software and Database Compatibility
The NE software and database that will be activated on an NE must be compatible.
When a software update is performed using a valid update path, the database version is
compatible. Otherwise, the database may not support the software functionality, or vice
versa. This may affect services.
To prevent a database from making service affecting (SA) changes to the installed
modules, the NCU detects when it is inserted into a new network element, as well as
when a new Compact Flash (CF) has been inserted. It then switches to an auxiliary
database. This auxiliary database functions as a security mechanism, in which the
equipment settings are not altered by it. It will therefore not have an impact on a running
system. The auxiliary database uses the default IP address, and thus management
contact with the NE will be lost. You will have to be on site, and reconnect to the NE
using a serial connection, to restore contact. Refer to the FSP 3000R7 Provisioning and
Operations Manual for guidelines on fixing the problem.
Software Update and Switchback
During activation of a software release, the first step taken by the system is to preserve
the former software database. This is done by copying the former database to the active
area and migrating its format to the new software version. The format update is
necessary for the database to match the features of the new software version. In
addition, the first time a software release is activated, the former software database is
copied to the standby area.
If you update a protected NCU, the standby NCU will be updated automatically during the
activation of the software release on the active NCU.
Figure 39 illustrates a software update scenario. An NEoperating with software release
8.1.0 is updated to software release 8.3.2. Since the user chose to keep the current
database during software activation, the previous database was migrated to the software
release 8.3.2 format. This database is labeled 8.3.2a.
604 FSP 3000R7 Maintenance and Troubleshooting Manual - Product Release 16.2 - Document Issue A
To Next Page
Loading...