Upgrade FOXMAN-UN database from R17A to R18
For an upgrade from R17A to R18, the procedure is considering that the DIRAC database must be upgraded from R17A to R18. Follow the steps below:
1 Perform a force poll on all network elements on your existing (old) FOXMAN-UN server.
The network should be as stable and alarm free as possible. Take note of the following:
− Any present alarms and unmanaged network element.
− Anything in invalid state on NP, ESM or ENP.
2 Create a backup of the NEM database on your existing (old) FOXMAN-UN server.
3 Create a backup of the following files from the folder “/opt/nem/etc” on your existing (old) FOXMAN-UN server:
/opt/nem/etc/iptranslate.conf
/opt/nem/etc/firewall.conf
Create a backup of the following files if they are present:
/opt/nem/etc/cst1_license.xml
/opt/nem/etc/npfotool_crossconnect.csv
/opt/nem/etc/npfotool_termination.csv
/opt/nem/etc/npfotool_trailhierarchy.csv
4 Restore the backed-up files from /opt/nem/etc on the new FOXMAN-UN R18 RHEL 9.6 server.
5 Restore the backed-up NEM database on the new FOXMAN-UN R18 RHEL 9.6 server.
Some general information on the database upgrade is given in [1KHW002414] User Manual “FOXMAN-UN under Linux”.
6 Start FOXMAN-UN services by executing nemstart.
Please note:
In networks with 1000 or more NEs, the initialization of the NMS can take between 20 and 30 minutes. The system is not fully operational during this time.
7 Once the FOXMAN-UN services are running, log in to FOXMAN-UN and check the NEM Browser, Networking Package (NP), Ethernet Security Manager (ESM) and Ethernet Networking Package (ENP). Refer to the following table for the status:
Item | Status |
|---|---|
NEM Browser | All network elements are manageable and are alarm free.1 |
NP | The status matches the one on the server of the previous release. |
ESM | All Crypto Engines have the Communication Status “Manageable”. Note that it may take some time until this status is shown. |
ESM | The port mappings are present. |
ENP | All encrypted tunnels have the Encryption Status “Valid” and the Status “Deployed Valid”. |
ENP | VPLS, VPWS, Pseudo Wire, Link, NE and Service Profile are in the same state as on the server of the previous release. Some services may be “Unaligned”. |
1 On a customer network there might be alarms or unmanageable network elements present before the upgrade. The alarm and network element situation on the new R18 server should match the situation on the server of the previous release.
All network elements still run the ESW of the old system release (R17A) but are now managed by FOXMAN-UN R18.
8 MPLS Service migration: MPLS services without control word (if there are any) must be migrated to services with control word. Control word shall be migrated before upgrading the nodes, else there is a risk to lose packets due to time stamping non PTP packets on SENC1 or EPEX1 units. It is recommended to do this step even if you currently do not operate SENC1 or EPEX1 units.
Therefore, execute the script “Set PW Control Word” from the FOXMAN-UN - R18 “NEM Desktop - System - Remote Executor...”. Execute the script service by service, node by node or network-wide, as preferred.
9 Upgrade FOX61x network elements ESW to R18. For details see section Upgrade via FOXMAN-UN (ESW Distribution Wizard).
10 If any services appear invalid or unaligned after the NE ESW upgrade has been successfully terminated, execute the steps in section Post-upgrade steps.
11 If your setup includes Foreign Objects (FO), follow the instructions given in section Foreign Object (FO) Upgrade to R18.
12 Once the new system is stable, disconnect or uninstall the old FOXMAN-UN.