{% load static %}

How do I handle Check disk size failed?

Method 1. Please open the EasySuite root directory and open NCEV100R019C00SPC601_v*_EasySuite_win32_x86\easysuite\easysuite\config\migrate_config.properties, and modify the SRC_MIGRATE_ROOT_PARTITION value to the new migration root directory. The directory requirements are as follows:

This configuration file is used to define the migration root path.

SRC_MIGRATE_ROOT_PARTITION is used to customize the migration root path for non-Windows sources.

The default root path is "/opt". If the space is insufficient, you can customize the path.

Pay attention to the following points when modifying the path:

1. For uTraffic, the root path can only be set to "/opt" or its subdirectory, for example, "/opt/backup".

2. To avoid conflicts, you are advised not to configure the root path to "/tmpfs", "/tmp", "/opt/sybase",

"/opt/oss", and "/etc/proc" paths that are being used by the EMS and system.

3. The multi-layer directory that does not exist cannot be configured. For example, if the /opt/backup directory exists in the environment, the multi-layer directory cannot be configured as /opt/backup/test1/test2.

4. The configured directory type cannot be a link.

5. The swap partition cannot be used.Check method:

Solaris OS: Run the "df -h" command to view the partition whose value in the "Filesystem" column is swap.

Linux OS: Run the "cat /etc/fstab" or "swapon -s" command to query the swap partition.

6. On Linux OS, the tmpfs partition is not allowed.

7. You are advised to use the root partition path with the largest available space, for example, "/opt/backup".

8. The customized path is an absolute path and can contain only letters, digits, and underscores (_). The length cannot exceed 51 characters.

9. For the new directory and its parent directory, the permission must be 755 and no requirement is posed on the owner group or the permission must be 750 and the owner group must be ossgroup.

10. The modification takes effect immediately without the need to restart the EasySuite client.However, the entire pre-migration source check needs to be performed again.

11. If the migration root paths of multiple source nodes are different, the configuration is as follows: {ip1}:{path1},{ip2}:{path2}. In the format, ip1 indicates the IP address of the first source node, and path1 indicates the migration root directory configured on the first source node.

Method 1. the following operations to clear the space of the source system U2000. Confirm with the customer about the clearance operation and clear data only after the customer agrees.

Clear the space: Obsolete files in the NE software library.

Procedure

  1. Log in to the U2000 client, choose Administration > NE Software Management > NE Software Library Management from the main menu.
  2. Select one or more files that can be deleted, right-click, and choose Delete from the shortcut menu. Alternatively, click Delete in the lower right corner of the window.

  3. If the following information is displayed, click Yes.

  4. A message is displayed, indicating that the deletion is successful. Click Details to confirm the deletion.

Clear the space: Delete the backup NE data files.

NE data files are used for NE disaster recovery. Before deleting NE data files, confirm with the customer. After the customer agrees, you are advised to back up the NE data files to another host and then delete them.

File path: /opt/backup/ftpboot/ftproot/dc/backup and /opt/backup/ftpboot/ftproot/dc/bak**.

Clear the space: U2000 dynamic files.

U2000 dynamic files are generated by scheduled tasks and database overflow dump during U2000 running. These files are generated in real time and become historical data over time. The number of files is large. These files are not read in the NCE environment and do not affect the running of NCE. They are backed up as historical data. If the space of the source U2000 is insufficient, you can delete some or all of the content in the following table after obtaining the customer's consent.

Table 1 U2000 dynamic file list and clearance suggestions

Module

Directory

File Usage

Clearance Rule

Remarks

Transport

/opt/oss/server/var/dump/PerfLog/

NE performance data

Retain the data of the latest one day according to the date when the files are generated.

If the number of files generated within one day is large, the file generation dates cannot be distinguished, or the customer requires that all data is retained, copy all the files to a server other than the U2000 or NCE server for backup, and delete the files from U2000. The backup files can be deleted one month later.

Transport

/opt/oss/server/var/PerfLog

NE performance data

Retain the data of the latest one day according to the date when the files are generated.

If the number of files generated within one day is large, the file generation dates cannot be distinguished, or the customer requires that all data is retained, copy all the files to a server other than the U2000 or NCE server for backup, and delete the files from U2000. The backup files can be deleted one month later.

Transport

/opt/oss/server/var/PerfFileData

NE performance data exported to the NBI

Delete the files after backup.

Copy all files to a server other than the U2000 or NCE server for backup and delete the files from U2000. The backup files can be deleted one month later.

Transport

/opt/oss/server/var/cache

Historical SDH and WDM performance data

Delete the files after backup.

Copy all files to a server other than the U2000 or NCE server for backup and delete the files from U2000. The backup files can be deleted one month later.

Transport

/opt/oss/server/var/dump/PerfFileData

NE performance data exported to uTraffic

Delete the files after backup.

Copy all files to a server other than the U2000 or NCE server for backup and delete the files from U2000. The backup files can be deleted one month later.

Transport

/opt/oss/server/nml/nmlsdh/report/

SDH resource report

Retain the files generated in the last two times.

   

Transport

/opt/oss/server/nml/nmlotn/report

WDM resource report

Retain the files generated in the last two times.

   

Transport

/opt/oss/server/nml/nmlotn/report/wdmtrail

WDM trail report

Retain the files generated in the last two times.

   

Transport

/opt/oss/server/var/dump/RTNLinkDump

Microwave link report

Retain the files generated in the last two times.

   

Transport

/opt/oss/server/var/dump/circuitpackmanuinfo

Board manufacturing information report

Retain the files generated in the last two times.

   

Transport

/opt/oss/server/var/snapshot

DCC view report

Retain the files generated in the last two times.

   

Transport

/opt/oss/server/script

U2000 script file

Retain the files generated in the last two times.

The number of U2000 script files is about twice the number of physical NEs managed by U2000. If the number of files exceeds 2000, you are advised to copy all files to a server other than the U2000 or NCE server and delete the files from U2000. After the migration is successful, use the script export function on NCE to export new scripts.

Transport

/opt/oss/server/var/dump/checkhealth

Network health check data

Retain the files generated in the last two times.

   

Transport

/opt/oss/server/etc/oss_cfg/trans/ason/Nml_ason_otn/optimize_history

WDM ASON optimization record

Retain the latest 10 files.

   

Transport

/opt/oss/server/etc/oss_cfg/trans/ason/Nml_ason_sdh/optimize_history

SDH ASON optimization record

Retain the latest 10 files.

   

Transport

/opt/oss/server/etc/oss_cfg/trans/ason/Nml_ason_otn/route_history

WDM ASON rerouting record

Retain the latest 10 files.

   

Transport

/opt/oss/server/etc/oss_cfg/trans/ason/Nml_ason_sdh/route_history

SDH ASON rerouting record

Retain the latest 10 files.

   

Inventory

/opt/oss/server/var/dump/inventoryDump

Inventory report

Retain the files generated in the last two times.

   

PMS

/opt/oss/server/var/dump/dataadmin/backup

Files dumped by PMS

Delete the files after backup.

This directory stores historical data files dumped by the PMS. If files exist in this directory on U2000, back up the files and then delete them.

Engineering

/opt/backup/dbbackup

Scheduled database backup files

Delete the files after backup.

This directory stores the scheduled database backup files. You can back up the files in the /opt/backup directory and then delete them. (The /opt/backup directory may be an independent partition.)

Engineering

/opt/backup/NMSbackup+timestamp

Backup files before the U2000 patch installation

Delete the files after backup.

This directory stores the scheduled database backup files. You can back up the files in the /opt/backup directory and then delete them. (The /opt/backup directory may be an independent partition.)

Engineering

/opt/backup/ftpboot/coldbackupdata

Database cold backup files

Delete the files after backup.

This directory stores the scheduled database backup files. You can back up the files in the /opt/backup directory and then delete them. (The /opt/backup directory may be an independent partition.)

Engineering

Under the /opt directory: OSpatch+timestamp, U2000 version+timestamp, patch+timestamp

Patch files

Delete the files after backup.

The files in the /opt directory are patch files. You can back up the files and then delete them.

IP

/opt/oss/server/common/ip/gcli/pnpscriptlogs

Script run log files

Delete the files after backup.