| 6.13. System management | ||
|---|---|---|
 | Chapter 6. Command language |  |
| 6.13. System management | ||
|---|---|---|
| | Chapter 6. Command language | |
In this section, the most frequently used commands about system management are shown.
With conf and conflog commands it's possible to copy, restore or save configuration and Log files. Below there's commands syntax:
[15:43:26] ABILIS_CPX:conflog ?BACKUP Copy configuration and log files to removable disk RESTORE Load configuration files from removable disk[15:43:26] ABILIS_CPX:conf ?BACKUP Copy configuration to removable disk GET Sends the configuration in memory to a remote site INFO Display/set configuration notes PUT Receives configuration from a remote site RELOAD Reload the configuration from a file RESTORE Alias of the CONFLOG RESTORE command SAVE Alias of the SAVE CONF command(s) VALIDATE Alias of the VALIDATE command
![[Tip]](../images/tip.png) | Tip |
|---|---|
Interesting chapter: Section 82.9, “How to copy files using a removable drive”. |
With file commands, it's possible to copy/delete a file or to transfer a file from and to Abilis CF/HD. Abilis supports XMODEM, XMODEM-1K, ZMODEM protocols for file transfer, from and to Abilis (use a terminal emulator which is compatible with the protocols mentioned above, to transfer files or system releases).
[15:43:26] ABILIS_CPX:file ?COPY Make a copy of a file DELETE Delete a file GET Send a file using XMODEM-1K or ZMODEM PUT Receive a file using XMODEM/XMODEM-1K or ZMODEM
With sys commands it's possible to manage Abilis CPX system software.
The following command displays the syntax:
[15:43:26] ABILIS_CPX:sys ?BMINSTALL Install Abilis Boot Manager BMVERIFY Verify Boot Manager on all mounted disks COMPACT Directory re-compacting operation COMPACTR Directory re-compacting operation, recursive COPY Make a copy of a file CREATE Create a directory DELETE Delete operations DIR List operations DISK Disk and Volume management DISPLAY Display operations GET Send a file using XMODEM-1K or ZMODEM PUT Receive a file using XMODEM/XMODEM-1K or ZMODEM SET Set operations UPDATE Receive a package or a new disk image and update the system
This command copies configuration and Log files
(DRIVERS.CFG, DRIVERS.BCK,
DHCP.BND, IKE.CNS,
CPX.LOG, CPX.DBG and
CPX.XCP) of the current version or of the specified
version to a removable disk.
The <version> string must correspond to an existing version directory in the form 'X.Y.Z' or 'X-Y-Z' or 'Y.Z' or 'Y-Z' or 'Y', where X, Y and Z are decimal digit [0 - 9] (E.g.: 8-5-1).
With the command conf backup it's possible to copy only configuration files.
[15:43:26] ABILIS_CPX:conflog backupTHE FOLLOWING REMOVABLE DISK DRIVES WERE FOUND: Drv Disk Label FS Free space Used space Total space ------------------------------------------------------------------------------- D: HD-16 VS FAT32 122828 MiB 81920 MiB 204748 MiB ------------------------------------------------------------------------------- T: HD-16 Bck FAT32 510476 MiB 32 KiB 510476 MiB ------------------------------------------------------------------------------- PLEASE ENTER THE DRIVE LETTER OF THE DISK DRIVE WHERE CONFIGURATION AND LOG FILES MUST BE COPIED (PRESS <ENTER> TO ABORT): T YOU ARE GOING TO BACKUP CONFIGURATION AND LOG FILES OF CURRENT VERSION TO 'T:\__Abilis_Cpx_Backup_And_Restore__'. PROCEED (N/Y)?y PROCEEDING WITH CONFIGURATION AND LOG FILES BACKUP... FILE 'DRIVERS.CFG'... SUCCESSFULLY COPIED. FILE 'DRIVERS.BCK'... SUCCESSFULLY COPIED. FILE 'CPX.LOG'... SUCCESSFULLY COPIED. FILE 'CPX.DBG'... SUCCESSFULLY COPIED. FILE 'CPX.XCP'... SUCCESSFULLY COPIED. FILE 'C:\APP\DHCP\DHCP.BND'... SUCCESSFULLY COPIED. FILE 'C:\APP\IKE\IKE.CNS'... SUCCESSFULLY COPIED. COMMAND COMPLETED
| Tip |
|---|---|
Interesting chapter: Section 82.9, “How to copy files using a removable drive”. |
These commands copy configuration files
(DRIVERS.CFG and DRIVERS.BCK)
from a removable disk to the current version or to the specified version
directory.
The <version> string must correspond to an existing version directory in the form 'X.Y.Z' or 'X-Y-Z' or 'Y.Z' or 'Y-Z' or 'Y', where X, Y and Z are decimal digit [0 - 9] (E.g.: 8-5-1).
[15:43:26] ABILIS_CPX:conflog restoreTHE FOLLOWING REMOVABLE DISK DRIVES WERE FOUND: Drv Disk Label FS Free space Used space Total space ------------------------------------------------------------------------------- D: HD-16 VS FAT32 122828 MiB 81920 MiB 204748 MiB ------------------------------------------------------------------------------- T: HD-16 Bck FAT32 510474 MiB 1 MiB 510476 MiB ------------------------------------------------------------------------------- PLEASE ENTER THE DRIVE LETTER OF THE DISK DRIVE FROM WHICH CONFIGURATION FILES MUST BE COPIED (PRESS <ENTER> TO ABORT): T YOU ARE GOING TO RESTORE CONFIGURATION FILES OF CURRENT VERSION FROM ''. PROCEED (N/Y)?y PROCEEDING WITH CONFIGURATION FILES RESTORE... FILE 'T:\__Abilis_Cpx_Backup_And_Restore__\DRIVERS.CFG'... SUCCESSFULLY COPIED. FILE 'T:\__Abilis_Cpx_Backup_And_Restore__\DRIVERS.BCK'... SUCCESSFULLY COPIED. COMMAND COMPLETED
| Tip |
|---|---|
Interesting chapter: Section 82.9, “How to copy files using a removable drive”. |
This command makes a copy of the “srcname” file into the specified “dtsname” path/file. The following command displays the syntax.
[15:43:26] ABILIS_CPX:file copy ?FILE COPY srcname dstname Make a copy of a file SYS COPY srcname dstname Make a copy of a file srcname Path or name of the source file to be copied. <Mandatory> When the file path is omitted the running version directory path is used. Spaces are allowed. Strings holding spaces must be written between quotation marks. (E.g.: "C:\APP\MY USERS\aaa.log") dstname Path or name of the target file. <Mandatory> When the file path is omitted the running version directory path is used. Spaces are allowed. Strings holding spaces must be written between quotation marks. (E.g.: A: or C:\4-3-1\ or Fdsp.bin or C:\4-3-2\drivers.cfg)
The “srcname” must be a file name. If the path is omitted the source file is assumed to be located in the current running version directory.
The “dstname” can either a path or a file name. If the path is omitted the destination directory is assumed to be the current running version directory.
Wildcards characters aren't accepted either in the source file name nor in the destination name.
File copies to root directory aren't allowed.
Log files (Cpx.log,
Cpx.dbg and Cpx.xcp) and
Cpx.rtb file cannot be overwritten.
This command deletes the specified file. The following command displays the syntax.
[15:43:26] ABILIS_CPX:file delete ?FILE DELETE filename Delete a file SYS DELETE FILE filename Delete a file filename Path or name of the file to be deleted. <Mandatory> When the file path is omitted the running version directory path is used. Spaces require double quotes (E.g. "C:\APP\MY DATA\aaa bbb.dat").
The “filename” must be a file name. If the path is omitted the source file is assumed to be located in the current running version directory.
Wildcards characters aren't accepted in the file name.
Files that are located in root directory can't be deleted.
File copies to root directory aren't allowed.
Configuration files, log files (Cpx.log,
Cpx.dbg and Cpx.xcp) and any
other system file cannot be deleted from the current running version
directory.
This command allows downloading files from the Abilis CPX. The following command displays the syntax.
[15:43:26] ABILIS_CPX:file get ?FILE GET [X] fname [<ver>] Send a file using XMODEM-1K FILE GET Z fname [<ver>] Send a file using ZMODEM SYS GET [X] fname [<ver>] Send a file using XMODEM-1K SYS GET Z fname [<ver>] Send a file using ZMODEM X or Z Select the X or Z MODEM protocol (by default XMODEM is used) XMODEM transfer is allowed only on files relative to the running version directory or to the specified '<ver>' version directory. ZMODEM transfer is allowed on any files. For file not relative either to the running version directory or to the '<ver>' version directory, the absolute file name is required i.e. including the full path. fname Name of the file to be sent <Mandatory> Spaces require double quotes (E.g. "C:\APP\MY DATA\aaa bbb.dat"). <ver> String corresponding to a version directory in <Optional> the form [x.y.z or x-y-z or y.z or y-z or y]. (E.g. 5.3.1 or 6-1-0 or 2189). Accepted only if 'fname' does not contain the full path.
The transfer procedure signals its availability to send the file with the message:
READY TO SEND FILE...
When the transfer is completed the following message is shown:
FILE TRANSFER ENDED, PRESS <ENTER> TO CONTINUE...
After pressing the Enter button, if the transfer was successful, the following message will be shown.
FILE TRANSFER SUCCESSFULLY COMPLETED
This command allows uploading files to the Abilis CPX. The following command displays the syntax:
[15:43:28] ABILIS_CPX:file put ?FILE PUT [X] fname [<ver>] Receive a file using XMODEM/XMODEM-1K FILE PUT Z fname [<ver>] Receive a file using ZMODEM SYS PUT [X] fname [<ver>] Receive a file using XMODEM/XMODEM-1K SYS PUT Z fname [<ver>] Receive a file using ZMODEM X or Z Select the X or Z MODEM protocol (by default XMODEM is used) XMODEM transfer is allowed only on files relative to the running version directory or to the specified '<ver>' version directory and only DRIVERS.CFG, DRIVERS.BCK, DHCP.BND, IKE.CNS files and mandatory fw files and optional USB devices and cards fw files are allowed. ZMODEM transfer is allowed on any files. For file not relative either to the running version directory or to the '<ver>' version directory, the absolute file name is required i.e. including the full path. fname Name of the file to be received <Mandatory> Spaces require double quotes (E.g. "C:\APP\MY DATA\aaa bbb.dat"). <ver> String corresponding to a version directory in <Optional> the form [x.y.z or x-y-z or y.z or y-z or y]. (E.g. 5.3.1 or 6-1-0 or 2189). Accepted only if 'fname' does not contain the full path
The transfer procedure signals its availability to receive the file by message:
READY TO RECEIVE FILE...
When the transfer is completed the following message is shown:
FILE TRANSFER ENDED, PRESS <ENTER> TO CONTINUE...
After pressing the Enter button, if the transfer was successful, the following message will be shown.
FILE TRANSFER SUCCESSFULLY COMPLETED
Once the file is received, it's submitted to a congruence control for checking its content validity. The User is informed through the message:
RECEIVED FILE 'namefile' CHECK IN PROGRESS...
If the file content isn't correct:
CHECK FAILED: FILE 'namefile' DELETED
If file content and version are correct:
CHECK PASSED
This command compacts the specified directory. It's useful when a lot of files have been deleted or renamed in a directory to reduce its size.
[15:01:49] ABILIS_CPX:sys compact ?SYS COMPACT <dir> [opt] Compact specified directory Allowed options: -R Recurse in sub-directories of the specified directory <Optional> [15:02:08] ABILIS_CPX:sys compact c:COMPACTING DIRECTORY 'c:' ... COMMAND EXECUTED, RECOVERED 2 SHORT DIRECTORY ENTRIES
![[Note]](../images/note.png) | Note |
|---|---|
This command copies all used directory entries to the start of the directory and zeros out all slack space. If the slack space is larger than one cluster, the slack space is freed, reducing the allocated size of a directory. |
To compact specified directory and sub-directories use "-R" option.
[15:03:10] ABILIS_CPX:sys compact c: -R
THIS OPERATION MAY TAKE FEW MINUTES AND LOCKS ACCESS TO DISK c:
PROCEED ANYWAY (N/Y)?y
COMPACTING DIRECTORY 'c:' AND ALL OF ITS SUBDIRECTORIES...
COMMAND EXECUTED, RECOVERED 0 SHORT DIRECTORY ENTRIESThis command creates a specified directory.
[16:41:48] ABILIS_CPX:sys create dir ?SYS CREATE DIR <dir> Creates a new directory (full path) If the parent directory doesn't exist it creates the full necessary path. [16:45:16] ABILIS_CPX:sys create dir C:\app\disa\msg\testCOMMAND EXECUTED
This command deletes a specified file.
[14:14:43] ABILIS_CPX:FILE DELETE filename Delete a file SYS DELETE FILE filename Delete a file filename Path or name of the file to be deleted. <Mandatory> When the file path is omitted the running version directory path is used. Spaces require double quotes (E.g. "C:\APP\MY DATA\aaa bbb.dat"). [15:22:12] ABILIS_CPX:sys delete file ?sys delete file C:\app\disa\msg\day\loopdial.wavFILE 'C:\app\disa\msg\day\loopdial.wav' IS GOING TO BE DELETED. PROCEED (N/Y)?y FILE 'C:\app\disa\msg\day\loopdial.wav' DELETED
This command deletes a specified directory.
[15:22:39] ABILIS_CPX:sys delete dir ?SYS DELETE DIR <dir> Delete the specified directory (full path) [15:24:51] ABILIS_CPX:sys delete dir c:\app\disa\msg\testYOU ARE GOING TO DELETE THE 'c:\app\disa\msg\test' DIRECTORY. PROCEED (N/Y)?y COMMAND EXECUTED
This command deletes the specified package file. Use sys
delete package <name of package> where <name of
package> must be the name of a package file located in
'C:\pkg' or an absolute package file name (the full
path is required).
[14:21:22] ABILIS_CPX:sys delete package test.pkg
YOU ARE GOING TO DELETE THE 'C:\PKG\TEST.PKG' PACKAGE FILE.
PROCEED (N/Y)?y
PACKAGE 'C:\PKG\TEST.PKG' DELETEDIt deletes the specified version directory.
[14:23:25] ABILIS_CPX:sys dir c:\Directory listing of C:\ LICENCE <DIR> 22/09/2015 11:27:44 7-9-16 <DIR> 22/09/2015 11:27:44 APP <DIR> 16/06/2015 14:26:10 PKG <DIR> 22/09/2015 15:14:54 LOG <DIR> 22/09/2015 15:14:54 USR <DIR> 22/09/2015 15:14:54 8-5-0 <DIR> 27/07/2017 07:19:18 8-3-9 <DIR> 04/11/2016 08:40:24 8-5-1 <DIR> 03/08/2017 07:19:40 8-4-6 <DIR> 14/07/2017 07:30:24 IO.SYS 125960 01/07/2003 12:30:04 MSDOS.SYS 99 11/12/2003 17:02:24 COMMAND.COM 94292 05/05/2003 22:22:00 BOOTSECT.RTT 512 22/09/2015 11:27:38 BM.RTA 284672 02/08/2017 09:58:46 BM.LOG 4096 03/08/2017 07:27:46 TIMECFG.DAT 30 26/03/2017 03:00:00 BM.CFG 107 03/08/2017 07:27:44 LASTRUN.DAT 512 21/08/2017 09:22:46 ETHMAC.DAT 256 13/07/2017 14:52:32 CPXRUN.CFG 80 03/08/2017 07:28:04 10 directory, 11 file (510,616 byte). Total 499 MiB, Used 96 MiB, Free 402 MiB. [14:23:42] ABILIS_CPX:sys delete version 7-9-16YOU ARE GOING TO DELETE THE 'C:\7-9-16' VERSION DIRECTORY. PROCEED (N/Y)?y VERSION 'C:\7-9-16' DELETED [14:24:23] ABILIS_CPX:sys dir c:\Directory listing of C:\ LICENCE <DIR> 22/09/2015 11:27:44 APP <DIR> 16/06/2015 14:26:10 PKG <DIR> 22/09/2015 15:14:54 LOG <DIR> 22/09/2015 15:14:54 USR <DIR> 22/09/2015 15:14:54 8-5-0 <DIR> 27/07/2017 07:19:18 8-3-9 <DIR> 04/11/2016 08:40:24 8-5-1 <DIR> 03/08/2017 07:19:40 8-4-6 <DIR> 14/07/2017 07:30:24 IO.SYS 125960 01/07/2003 12:30:04 MSDOS.SYS 99 11/12/2003 17:02:24 COMMAND.COM 94292 05/05/2003 22:22:00 BOOTSECT.RTT 512 22/09/2015 11:27:38 BM.RTA 284672 02/08/2017 09:58:46 BM.LOG 4096 03/08/2017 07:27:46 TIMECFG.DAT 30 26/03/2017 03:00:00 BM.CFG 107 03/08/2017 07:27:44 LASTRUN.DAT 512 21/08/2017 09:24:16 ETHMAC.DAT 256 13/07/2017 14:52:32 CPXRUN.CFG 80 03/08/2017 07:28:04 9 directory, 11 file (510,616 byte). Total 499 MiB, Used 83 MiB, Free 415 MiB.
These commands allow the elimination of obsolete versions or forgotten files or directories that are no longer used because they derive from no longer existing users.
[08:29:22] ABILIS_CPX:sys purge ?
ALL Performs all purges in sequence
USERS Purge directories and files of not existing users
VERSIONS Purge versions other than the current one
[08:29:32] ABILIS_CPX:SYS PURGE VERSIONS
This command deletes all versions/builds leaving only the current.
[14:28:13] ABILIS_CPX:sys purge versionsYOU ARE GOING TO KEEP ONLY CURRENT VERSION AND PURGE ALL THE OTHERS. PROCEED (N/Y)?y PURGE VERSIONS IN PROGRESS... DELETED '4727' BUILD DELETED '4715-8' BUILD DELETED '4703-18' BUILD DELETED '4726-98' BUILD DELETED '4715-10' BUILD DELETED '4715-11' BUILD DELETED '4703-23' BUILD COMMAND EXECUTED [14:29:39] ABILIS_CPX:sys display versionsList of available versions/builds: Version/Build directory Date Time ------------------------------------------------------------------------------- 8-11-0 29/03/2021 13:08:40 [14:31:10] ABILIS_CPX:
SYS PURGE USERS
This command deletes all working directories, Voice Mail directories and CTI Traffic analyzer files of no longer existing users.
[08:42:17] ABILIS_CPX:sys purge users
YOU ARE GOING TO PURGE ALL DIRECTORIES AND FILES OF NOT EXISTING USERs, IF ANY.
THIS OPERATION MAY TAKE SOME TIME.
PROCEED (N/Y)?y
PURGE USERS IN PROGRESS...
DELETED 'C:\APP\USERS\Utente1' DIRECTORY
DELETED 'C:\APP\USERS\Utente2' DIRECTORY
DELETED 'C:\APP\VM\USERS\Utente1' DIRECTORY
DELETED 'C:\APP\VM\USERS\Utente2' DIRECTORY
DELETED 'C:\APP\TRFA\CTI\USER\Utente1_DAY.DAT' FILE
DELETED 'C:\APP\TRFA\CTI\USER\Utente2_DAY.DAT' FILE
DELETED 'C:\APP\TRFA\CTI\USER\Utente1_WEEK.DAT' FILE
DELETED 'C:\APP\TRFA\CTI\USER\Utente2_WEEK.DAT' FILE
DELETED 'C:\APP\TRFA\CTI\USER\Utente1_MONTH.DAT' FILE
DELETED 'C:\APP\TRFA\CTI\USER\Utente2_MONTH.DAT' FILE
PURGE USERS STATISTICS:
- Users directories: 2
- VM Users directories: 2
- TRFA Cti user files: 6
- TRFA Cti History user files: 0
COMMAND EXECUTED
[08:44:02] ABILIS_CPX:SYS PURGE ALL
This command performs all purges in sequence, by first on versions and then on users.
This command makes possible the system software update in two ways:
By receiving from a remote source the package file holding the updated software and installing it on the CF/HD in a proper version directory.
The transfer procedure signals its availability to receive the package file by the following messages:
[18:01:32] ABILIS_CPX:sys update zSYSTEM UPDATE PROCEDURE PLEASE UPLOAD THE PACKAGE FILE. READY TO RECEIVE PACKAGE...
When the transfer is completed the following message is shown:
PACKAGE TRANSFER SUCCESSFULLY COMPLETED RECEIVED PACKAGE CHECK and EXTRACTION IN PROGRESS (8-9-0)... CHECK PASSED, EXTRACTION DONE. VERSION '8-9-0' SUCCESSFULLY INSTALLED.
If a package file already present in the 'C:\PKG' directory, installing it on the HD/CF in a proper version directory.
In this case the package file name specification is required by the User on the command line: sys update <package>. The <package> string must be the name of a package file located in 'C:\PKG' or an absolute package file name (i.e. The full path is required). If the specified package file isn't present, the message “FILE 'C:\PKG\<package> NOT FOUND” will be shown.
The procedure starts with a package integrity check. If the package passes the validation phase, the software extraction and installation take place.
[18:01:32] ABILIS_CPX:sys update 8-9-0 PACKAGE 'C:\PKG\8-9-0.PKG' CHECK and EXTRACTION IN PROGRESS (8-9-0)... CHECK PASSED, EXTRACTION DONE. VERSION '8-9-0' SUCCESSFULLY INSTALLED.
If the package verifications and extraction is successful, the package file is always deleted.
If the procedure fails for any reason, the package deletion takes place only after the User confirmation.
The list of currently available package files can be displayed by the command sys display packages; while a package file can be deleted by the command sys delete package.
Once a new software version is installed on the system, it can be set to be loaded at next system startup by the command sys set boot version. The list of the currently available versions can be displayed by the command sys display versions. Old versions, not longer useful, can be deleted by the command sys delete version.
| Tip |
|---|---|
Interesting chapter: Section 82.5, “How to remotely upgrade the Abilis firmware”. |
It makes possible an easy update of Abilis to newer versions.
The command requires a functional Internet connection to reach Abilis repository at support.abilis.net.
When new versions will be available the command will offer the most recent Abilis version for update, as well as the latest version of each minor version branch. You can then choose the version to install and whether and when to reboot.
[11:15:24] ABILIS_CPX:sys update auto ?
SYS UPDATE AUTO [-opt] Update system to the latest release available on
Abilis servers
Options:
-DELAY hh:mm Once updated, the system will reboot after the specified delay,
where 'hh' [0..2400], 'mm' [0..59].
Can be combined with -NOCALL -SAVE[CONF].
Alternative to -NOREBOOT.
-NOCALL Once updated, the system will reboot as soon as all CTI calls
are closed.
Can be combined with -DELAY -SAVE[CONF].
Alternative to -NOREBOOT.
Can be combined with -DELAY -NOCALL.
-SAVE[CONF] Before rebooting save configuration in both current and next
versions.
-NOREBOOT Once updated, the system will not reboot.
Alternative to all the other options.
[11:15:31] ABILIS_CPX:Following is a simulation of what may happen when a new version will available. The option -NOREBOOT is intentionally used for this simulation.
[11:48:23] ABILIS_CPX:sys update auto -norebootONCE UPDATED, THE SYSTEM WILL NOT SET NEXT VERSION AND IT WILL NOT REBOOT. DO YOU WANT TO PROCEED (N/Y)?y RETRIEVING http://support.abilis.net/downloads/cpx2k/releases.xml... CURRENT RUNNING VERSION IS '8-9-0'. LATEST AVAILABLE VERSION IS '8-9-1'. DO YOU WANT TO PROCEED (N/Y)?yRETRIEVING http://support.abilis.net/downloads/cpx2k/8.9/8.9.1/cpx-8.9.1-std-package.zip... CHECK and EXTRACTION IN PROGRESS (8-9-1)... CHECK PASSED, EXTRACTION DONE. VERSION '8-9-1' SUCCESSFULLY INSTALLED. C:\8-9-0\DRIVERS.CFG COPIED TO VERSION '8-9-1'. SYSTEM AUTO UPDATE COMPLETED [11:49:23] ABILIS_CPX:
If more minor or major versions will be available the command will show the latest of each minor version and will let you to choose.
[11:53:07] ABILIS_CPX:sys update auto -norebootONCE UPDATED, THE SYSTEM WILL REBOOT IMMEDIATELY. DO YOU WANT TO PROCEED (N/Y)?y RETRIEVING http://support.abilis.net/downloads/cpx2k/releases.xml... CURRENT RUNNING VERSION IS '8-9-2'. LATEST AVAILABLE VERSIONs ARE: 8-9-4 8-10-0 PLEASE ENTER THE VERSION YOU WANT TO INSTALL:8-10-0SELECTED VERSION IS '8-10-0'. DO YOU WANT TO PROCEED (N/Y)?yRETRIEVING http://support.abilis.net/downloads/cpx2k/8.10/8.10.0/cpx-8.10.0-std-package.zip... CHECK and EXTRACTION IN PROGRESS (8-10-0)... CHECK PASSED, EXTRACTION DONE. VERSION '8-10-0' SUCCESSFULLY INSTALLED. C:\8-9-2\DRIVERS.CFG COPIED TO VERSION '8-10-0'. BOOT MANAGER CONFIGURATION UPDATED. SYSTEM AUTO UPDATE COMPLETED
It shows the directory listing of the specified path.
[14:26:13] ABILIS_CPX:sys dir c:\
Drive C:, Label: <no-label>, Serial Number 4D5D-A3E4
Directory listing of C:\
4431 <DIR> 29/10/2018 20:32:00
LICENCE <DIR> 29/10/2018 20:32:24
APP <DIR> 29/10/2018 20:32:24
USR <DIR> 29/10/2018 20:32:44
PKG <DIR> 29/10/2018 20:34:40
4431-1 <DIR> 31/10/2018 08:54:26
8-7-0 <DIR> 07/11/2018 08:25:08
MIRROR.LOG 68837 29/10/2018 20:32:46
BOOTSECT.RTT 512 29/10/2018 20:32:00
BM.RTA 285184 29/10/2018 20:32:00
BM.CFG 108 07/11/2018 08:38:00
BM.LOG 4096 07/11/2018 08:38:00
CFMODE.CFG 109 29/10/2018 20:34:36
ETHMAC.DAT 256 29/10/2018 20:34:42
LASTRUN.DAT 512 07/11/2018 12:51:42
TIMECFG.DAT 30 27/10/2018 23:00:00
CPXRUN.CFG 80 07/11/2018 08:38:46
7 Dir(s), 10 File(s) (359,724 bytes).
Total 481 MiB, Used 89 MiB, Free 392 MiB.It displays logical drive(s) information.
[14:43:07] ABILIS_CPX:sys disk info
Logical drive(s) information:
Drv Disk FS Label Serial Used space Total space
Interface Cluster size Free space Bootable
-------------------------------------------------------------------------------
C: HD-12 FAT16 5955-E04B 441 MiB 966 MiB
AHCI 16,384 bytes 525 MiB YES
-------------------------------------------------------------------------------
D: HD-13 FAT32 2E7B-565B 361 MiB 482 MiB
AHCI 4,096 bytes 121 MiB YES
-------------------------------------------------------------------------------
E: HD-16 FAT12 DummyDisk 5114-42AC 0 KiB 16 KiB
RAM 4,096 bytes 16 KiB YES
------------------------------------------------------------------------------- | Note |
|---|---|
The DummyDisk (E:) is a Ram Disk that occupies just 32 Kbytes of RAM, it is created at startup after ide/sata disks and used for swap with D: when the drive in D: is NOT suitable for System CF. |
It checks the disk drive integrity.
[14:27:57] ABILIS_CPX:sys disk chk
THIS OPERATION MAY TAKE FEW MINUTES AND LOCKS ACCESS TO DISK 'C:'.
PROCEED ANYWAY (N/Y)?y
DISK 'C:' INTEGRITY CHECK IN PROGRESS....
DISK 'C:' INTEGRITY CHECK SUCCESSFULLY COMPLETED
NO ERRORs WERE FOUNDUse sys disk chk ? to display the options.
[10:53:26] ABILIS_CPX:sys disk chk ?
SYS DISK CHK [<drive>] [opt] Check disk drive integrity
<drive> Drive name [C:,..,Z:] (by default C:) <Optional>
opt: Option [-F, -FE, -FF, -S, -V, -L] <Optional>
Disk check options:
-F Enable error fixing, except file size errors and FAT mismatch
-FE Enable error fixing, file size errors included
-FF Enable error fixing, FAT mismatch errors included
-S Enable silent mode (check disk statistics are displayed only)
-V Enable verbose mode (this option extends default verbose mode)
-L Displays the list of the detectable errorsIt formats the specified drive. Note that system drive c: can't be formatted.
[14:35:22] ABILIS_CPX:sys disk format d:
DO YOU REALLY WANT TO FORMAT DRIVE 'T:' (N/Y)?y
THIS OPERATION WILL DELETE ALL EXISTING DATA FROM DRIVE 'T:'.
PROCEED ANYWAY (N/Y)?y
DRIVE 'T:' FORMAT IN PROGRESS...
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
DONE.
ENTER VOLUME LABEL (MAX 11 CHARACTERs, PRESS <ENTER> FOR NO LABEL): bck
DRIVE 'T: FORMATTED:
FILE SYSTEM IS FAT-32, Size: 510538 MiB
Bytes per sector: 512, Sectors per cluster: 128, Clusters: 8168618
Serial N. 4B15-4CC5, Label: bck
COMMAND COMPLETEDIt sets the label of the selected drive or remove any existing label.
[14:41:40] ABILIS_CPX:sys disk label t:ENTER VOLUME LABEL (MAX 11 CHARACTERs, PRESS <ENTER> FOR NO LABEL): USB_DRIVE COMMAND EXECUTED [14:41:51] ABILIS_CPX:sys disk infoLogical drive(s) information: Drv Disk FS Label Serial Used space Total space Interface Cluster size Free space Bootable ------------------------------------------------------------------------------- C: HD-0 FAT32 4D5D-A3E4 89 MiB 481 MiB IDE-UDMA 2,048 bytes 392 MiB YES ------------------------------------------------------------------------------- E: HD-16 FAT32 VS 4C23-9866 122880 MiB 204748 MiB USB 32,768 bytes 81868 MiB YES ------------------------------------------------------------------------------- P: HD-16 FAT32 USB_DRIVE 4B15-50AF 4180 MiB 510538 MiB USB 65,536 bytes 506357 MiB NO -------------------------------------------------------------------------------
It displays the Boot record (MBR/VBR) content.
[14:45:58] ABILIS_CPX:sys disk br hd:0
Address | Hexadecimal values | Ascii values
---------+-------------------------------------------------+-----------------
00000000 | FA BE 00 7C BF 00 7A B9 00 01 FC 0E 1F 0E 07 F3| ...|..z.........
00000010 | A5 EA 16 7A 00 00 BB BE 7B 33 C9 80 3F 80 75 06| ...z....{3..?.u.
00000020 | FE C5 8B F3 EB 07 80 3F 00 75 02 FE C1 83 C3 10| .......?.u......
00000030 | 81 FB FE 7B 72 E5 83 F9 04 74 0B 81 F9 03 01 74| ...{r....t.....t
00000040 | 0A BB A6 7A EB 2C BB 87 7A EB 27 8B 4C 02 8B 14| ...z.,..z.'.L...
00000050 | B8 01 02 BB 00 7C CD 13 73 05 BB BE 7A EB 13 2E| .....|..s...z...
00000060 | A1 FE 7D 3D 55 AA 74 05 BB BE 7A EB 05 EA 00 7C| ..}=U.t...z....|
00000070 | 00 00 2E 8A 07 3C 00 74 0C 53 BB 07 00 B4 0E CD| .....<.t.S......
00000080 | 10 5B 43 EB ED EB FE 4E 6F 20 62 6F 6F 74 61 62| .[C....No bootab
00000090 | 6C 65 20 70 61 72 74 69 74 69 6F 6E 20 69 6E 20| le partition in
000000A0 | 74 61 62 6C 65 00 49 6E 76 61 6C 69 64 20 50 61| table.Invalid Pa
000000B0 | 72 74 69 74 69 6F 6E 20 74 61 62 6C 65 00 49 6E| rtition table.In
000000C0 | 76 61 6C 69 64 20 6F 72 20 64 61 6D 61 67 65 64| valid or damaged
000000D0 | 20 42 6F 6F 74 61 62 6C 65 20 70 61 72 74 69 74| Bootable partit
000000E0 | 69 6F 6E 00 53 79 73 74 65 6D 53 6F 66 74 20 42| ion.SystemSoft B
000000F0 | 6F 6F 74 20 50 61 72 74 69 74 69 6F 6E 20 53 65| oot Partition Se
00000100 | 63 74 6F 72 00 00 00 00 00 00 00 00 00 00 00 00| ctor............
00000110 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................
00000120 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................
00000130 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................
00000140 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................
00000150 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................
00000160 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................
00000170 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................
00000180 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................
00000190 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................
000001A0 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................
000001B0 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 01| ................
000001C0 | 01 00 06 0F FF D5 3F 00 00 00 61 1A 0F 00 00 00| ......?...a.....
000001D0 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................
000001E0 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................
000001F0 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA| ..............U.
HD-0, Boot Record:
- Master Boot Record (MBR) --------------------------------------------------
Boot Start Start Start Type End End End Relative Sectors
Head Sec. Cyl. Head Sec. Cyl. Sector
-----------------------------------------------------------------------------
80 01 1 0 06 FAT-16 CHS 0F 63 981 63 989793
----------------------------------------------------------------------------It displays partition(s) information.
[14:47:41] ABILIS_CPX:sys disk partition info
Available Hard Disk(s) information:
Disk Size Part# Drv Label FS Total Space Bootable
-------------------------------------------------------------------------------
HD-0 483 MiB 1 C: FAT32 481 MiB YES
-------------------------------------------------------------------------------
HD-16 715404 MiB 1 E: VS FAT32 204748 MiB YES
2 P: usb_drive FAT32 510538 MiB NO
-------------------------------------------------------------------------------It adds partition(s) to the specified disk.
[14:47:41] ABILIS_CPX:sys disk partition infoAvailable Hard Disk(s) information: HD Size Partition Drive Label FS Size Bootable ------------------------------------------------------------------------------- 5 500 MiB 1 C: FAT32 499 MiB YES ------------------------------------------------------------------------------- 8 122 MiB 1 D: FAT32 121 MiB NO ------------------------------------------------------------------------------- [14:48:05] ABILIS_CPX:sys disk partition add ?HD: Hard disk index [0..31] [14:48:33] ABILIS_CPX:sys disk partition add hd:16Hard Disk '16' information: HD Size Partition Drive Label FS Size Bootable ------------------------------------------------------------------------------- 16 715404 MiB 1 D: VS FAT32 204748 MiB NO 2 T: FAT32 510538 MiB NO HARD DISK '16' ALREADY HOLDS 2 PARTITIONs. DO YOU WANT TO ADD A NEW PARTITION (N/Y)?y THIS OPERATION WILL SPLIT PARTITION 2 ('T:') INTO TWO PARTITIONs. ALL DATA ON 2 ('T:') PARTITION WILL BE LOST. PROCEED (N/Y)?y PLEASE ENTER THE SIZE YOU WANT TO RESERVE FOR PARTITION 2 ('T:'), THE REMAINING SPACE WILL BE ASSIGNED TO THE NEW PARTITION, IN MiBytes (0 TO EXIT): 400 THE SIZE OF PARTITION 2 ('T:') WILL BE ABOUT 400 MiB THE SIZE OF THE NEW PARTITION WILL BE ABOUT 510,138 MiB PROCEED (N/Y)?y HARD DISK PARTITIONING OPERATIONS REQUIRE THAT NO FILES ARE OPENED. IF SOME FILES ARE CURRENTLY OPENED IN THE SYSTEM, THE COMMAND WILL WAIT UNTIL ALL FILES WILL BE CLOSED. PROCEED (N/Y)?y WAITING THAT ALL FILES GET CLOSED (TYPE CTRL+C + ENTER TO STOP)... DONE. NEW PARTITION CREATION IN PROGRESS... DONE. PARTITION 2 ('T:') SUCCESSFULLY SPLITTED ON HARD DISK '16' PARTITION 3 ('U:') SUCCESSFULLY CREATED ON HARD DISK '16' DRIVE 'T:' FORMAT IN PROGRESS... 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% DONE. ENTER VOLUME LABEL (MAX 11 CHARACTERs, PRESS <ENTER> FOR NO LABEL): usb_drive DRIVE 'T: FORMATTED: FILE SYSTEM IS FAT-32, Size: 510138 MiB Bytes per sector: 512, Sectors per cluster: 128, Clusters: 8168618 Serial N. 4B15-50AF, Label: usb_drive
It resets all existing partition(s) for the specified disk.
[15:01:10] ABILIS_CPX:sys disk partition reset hd:4
Hard Disk '16' information:
HD Size Partition Drive Label FS Size Bootable
-------------------------------------------------------------------------------
16 715404 MiB 1 D: VS FAT32 204748 MiB NO
2 T: usb_drive FAT32 510138 MiB NO
3 U: FAT32 400 MiB NO
DO YOU REALLY WANT TO EXTEND THE PARTITION 2 ('T:') ON DISK '16' (N/Y)?y
THIS OPERATION WILL EXTEND THE PARTITION 2 ('T:'), DELETING ANY
SUBSEQUENT PARTITION ON HARD DISK '16'.
PROCEED (N/Y)?y
HARD DISK PARTITIONING OPERATIONS REQUIRE THAT NO FILES ARE OPENED.
IF SOME FILES ARE CURRENTLY OPENED IN THE SYSTEM,
THE COMMAND WILL WAIT UNTIL ALL FILES WILL BE CLOSED.
PROCEED (N/Y)?y
WAITING THAT ALL FILES GET CLOSED (TYPE CTRL+C + ENTER TO STOP)... DONE.
EXTENDING PARTITION 2 ('T:') ON HARD DISK '16'... DONE.
PARTITION 2 ('T:') SUCCESSFULLY EXTENDED ON HARD DISK '16'
DRIVE 'T:' FORMAT IN PROGRESS...
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
DONE.
ENTER VOLUME LABEL (MAX. 11 CHARACTERs, PRESS <ENTER> FOR NO LABEL): drive1
DRIVE 'T: FORMATTED:
FILE SYSTEM IS FAT-32, Size: 510538 MiB
Bytes per sector: 512, Sectors per cluster: 128, Clusters: 8168618
Serial N. 4B15-50AF, Label: usb_driveThis command allows changing Boot Manager configuration setting the version that must be loaded at next system startup.
The list of available versions can be displayed by sys display versions command; while the current/new Boot Manager configuration is displayed by sys display boot command.
[15:43:26] ABILIS_CPX:sys display bootAbilis CPX Boot Manager configuration: Previous version Current version Next Version to load ------------------------------------------------------------------------------ 8-3-7 8-8-8 8-8-8-[15:43:26] ABILIS_CPX:sys set boot version 8-9-0BOOT MANAGER CONFIGURATION UPDATED: THE NEXT VERSION THAT WILL BE LOADED IS '8-9-0'. COMMAND EXECUTED [[15:43:26] ABILIS_CPX:sys display bootAbilis CPX Boot Manager configuration: Previous version Current version Next Version to load ------------------------------------------------------------------------------ 8-3-7 8-8-8 8-9-0
This command allows showing some information about Abilis boot. Every time Abilis CPX boots, a log is generated, what includes the data and time.
[10:17:19] ABILIS_CPX:d tCurrent Local Time : Monday 24/08/2020 12:52:07 (UTC+02:00) Local Time Zone : CET - Central Europe (Rome, Paris, Berlin, Prague,... Currently Observing : Daylight Savings Time (DST) ------------------------------------------------------------------------------- Clock Reference : SNTP Clock Reference state : Working Clock Last Response : 24/08/2020 12:19:00 Delta: -0.145 s Clock Last Sync start : 24/08/2020 08:19:00 Delta: -0.724 s Clock Last Sync end : 24/08/2020 08:19:05 [10:19:19] ABILIS_CPX:warm startPROCEED WITH WARM START (N/Y)?y... [10:21:19] ABILIS_CPX:sys display boot logBoot Manager log file: ... ***** New run at 2020-08-24 08:18:34 +0200 ***** Abilis Boot Manager: v. 2053 - 06/09/2018 PIO32 mode disabled: incompatible device Setting current directory ... Done Loading configuration ... Done Loading response file ... Done Try 'new' version: 8-9-2 Saving configuration ... Done Deleting response file ... Done Writing shared region ... Done Loading: 8-9-2\CPX.RTB ... Done Starting: 8-9-2\CPX.RTB
BM version identification is available in D I, SYS BM VERIFY, SYS BM INSTALL commands. In Abilis 8.7.0 the BM version is 2053.
BootManager must be installed on all disks that M/B BIOS can use for booting, i.e. All SATA and IDE disks. It is NOT necessary to install BM on USB disks.
This command is used to verify Boot Manager.
[17:42:29] ABILIS_CPX:sys bm verify ?SYS BMVERIFY [<drive>] Verify Boot Manager on all mounted disks, or on the specified one (file BM.RTA). <drive> Drive name [C:,..,Z:] <Optional> [17:45:22] ABILIS_CPX:sys bm verifyVerify Boot Manager on all mounted disks (file BM.RTA). Drive Version Date Time Size ------------------------------------------------------------------------------ C: 2053 10/10/2018 07:45:10 285184 D: 2053 10/10/2018 07:45:20 285184
Due to important improvements and fixes, it is recommended to update older BM version to new one.
This command is used to install Boot Manager.
[17:45:28] ABILIS_CPX:sys bm install ?SYS BMINSTALL <drive> [<ver>|<path>][-F] Installs Abilis Boot Manager, BM.RTA file, to the specified drive. The BM.RTA is created from the BM.RTB file located in the directory of the running version, unless a different location is specified. <drive> Target drive name [C:,..,Z:] <Mandatory> <ver> Abilis version directory where 'BM.RTB' file is located, <Optional> in the format [x.y.z or x-y-z or y.z or y-z or y], (E.g.: 5.3.1 or 6-1-0 or 2189). <path> Full path of the directory where 'BM.RTB' file <Optional> is located. Physical full path in DOS notation, i.e. starting with a drive letter in the range ['A'..'Z'] and ending with the '\' character. Spaces are allowed. Strings holding spaces must be written between quotation marks (E.g.: "C:\My dir"). -F Force Boot Manager version downgrade <Optional> [17:47:30] ABILIS_CPX:sys bminstall c:THIS PROCEDURE OVERWRITES THE BOOT SECTOR OF DISK 'C:' AND MAKES IT BOOTABLE WITH ABILIS SOFTWARE ONLY. BM VERSION CURRENTLY ON 'C:' IS '2052'. BM VERSION BEING INSTALLED ON 'C:' IS '2053'. PROCEED (NO/YES)?yes PLEASE VERIFY ONCE MORE THAT DISK 'C:' IS THE DESIRED TARGET, BECAUSE ONLY ABILIS SOFTWARE WILL THEN BOOT FROM THAT DISK. REALLY PROCEED (NO/YES)?yes INSTALLING 'C:\8-7-0\BM.RTB' ON 'C:'... DONE. COMMAND COMPLETED COMMAND COMPLETED [17:47:40] ABILIS_CPX:sys bmverify c:Verify Boot Manager on all mounted disks (file BM.RTA). Drive Version Date Time Size ------------------------------------------------------------------------------ C: 2053 07/11/2018 13:07:14 285184
![[Important]](../images/important.png) | Important |
|---|---|
To boot with new BM version, Abilis restart is required (i.e. With warm start command). |
SYS MIRROR commands permits to run manually the mirroring of CF, and display the log of the last MIRROR execution.
| Tip |
|---|---|
Interesting chapter: Section 5.2, “Double CF handling”. |
[13:09:09] ABILIS_CPX:sys mirror ?
COMPARE Execute system mirror compare
LOG Display log of last system mirror execution
RUN Execute system mirrorType the following command to execute system mirror compare of the system disk C: with mirror disk D:.
[14:31:51] ABILIS_CPX:sys mirror compare
THIS PROCEDURE COMPARES THE SYSTEM DISK C: WITH MIRROR DISK D:
THIS OPERATION MAY TAKE FEW MINUTES.
PROCEED (N/Y)?y
SYSTEM MIRROR COMPARE IN PROGRESS...
Disk D: validation... Success.
Abilis versions...
Current: 8-7-0, Next: 8-7-0, Previous: 4431-1.
Compare in progress...
>> C:\BM.CFG
>> C:\BM.LOG
>> C:\CPXRUN.CFG
>> C:\LASTRUN.DAT
> C:\8-7-0\*.*
x D:\4431\*.*
>> C:\APP\CTI\LCS\LCSTABLE.DAT
>> C:\APP\DHCP\DHCP.BND
>> C:\APP\IKE\IKE.CNS
>> C:\APP\TRFA\IP\002W.DAT
>> C:\APP\TRFA\IP\001D.DAT
>> C:\APP\TRFA\IP\001M.DAT
>> C:\APP\TRFA\IP\002M.DAT
>> C:\APP\TRFA\IP\001W.DAT
>> C:\APP\TRFA\IP\020D.DAT
>> C:\APP\TRFA\IP\020M.DAT
>> C:\APP\TRFA\IP\020W.DAT
>> C:\APP\TRFA\IP\021D.DAT
>> C:\APP\TRFA\IP\021W.DAT
>> C:\APP\TRFA\IP\021M.DAT
>> C:\APP\TRFA\IP\022D.DAT
>> C:\APP\TRFA\IP\022W.DAT
>> C:\APP\TRFA\IP\002D.DAT
>> C:\APP\TRFA\IP\022M.DAT
>> C:\APP\TRFA\CTI\USER\test_DAY.DAT
>> C:\APP\TRFA\CTI\USER\test3_DAY.DAT
>> C:\APP\TRFA\CTI\USER\test_WEEK.DAT
>> C:\APP\TRFA\CTI\USER\test3_WEEK.DAT
>> C:\APP\TRFA\CTI\USER\test_MONTH.DAT
>> C:\APP\TRFA\CTI\USER\test3_MONTH.DAT
>> C:\APP\TRFA\CTI\USER\test2_DAY.DAT
>> C:\APP\TRFA\CTI\USER\test2_WEEK.DAT
>> C:\APP\TRFA\CTI\USER\test2_MONTH.DAT
>> C:\APP\USERS\test\cticalls.log
>> C:\APP\USERS\test\ctirecents.log
>> C:\APP\USERS\test2\cticalls.log
>> C:\APP\USERS\test2\ctirecents.log
>> C:\4431-1\CPX.LOG
Completed.
Compare success.
COMMAND EXECUTEDThe meaning:
>> - the file present in the disk D:,
but is different, it will be rewritten.
> - the file/dir is not present in the
disk D:, it will be written.
x - the file/dir is present in the disk D:,
but it will be deleted.
Type the following command to execute system mirror of the system disk C: with mirror disk D:
[14:46:16] ABILIS_CPX:sys mirror runType the following command to display the log of the last MIRROR execution:
[14:51:55] ABILIS_CPX:sys mirror log
***** New run at 2018-11-07 14:46:18 +01:00 *****
Abilis CPX - Ver. 8.7.0/STD - Build 4431.5 - Branch 8.7
Mirror disk D: validation... Success.
Mirror disk D: check... Success.
Main disk C: check... Success.
Abilis versions...
Current: 8-7-0, Next: 8-7-0, Previous: 4431-1.
Mirror disk D: purge...
Completed.
Boot Manager check... Success.
Mirror of:
8-7-0 ...
Completed.
4431-1 ...
Completed.
LICENCE ...
Completed.
APP ...
Completed.
USR ...
Completed.
\ ...
Completed.
Execution success.
***** Run end at 2018-11-07 14:49:48 +01:00 *****The log of the last MIRROR execution can be inspected (file
MIRROR.LOG) on the second CF.
The CFMODE can be set/changed/recovered only on
the running Abilis, it' can't be done offline.
| Tip |
|---|---|
Interesting chapter: Section 5.2, “Double CF handling”. |
[17:40:59] ABILIS_CPX:sys cfmode ?
INFO Display Compact Flash Mode settings
LOG Display log of Compact Flash Mode activities
RECOVERY Recovery from SAFE-DEGRADED mode
SET Set Compact Flash ModeType the following command to display Compact Flash Mode settings:
[14:57:29] ABILIS_CPX:sys cfmode info
Abilis Compact Flash management mode configuration:
Disk Mode Disk Uuid
-------------------------------------------------------------------------------
C: NORMAL 1 C04F9394070000409143CCD3052E33C2
D: - - -Type the following command to set Compact Flash Mode to SAFE:
[14:12:26] ABILIS_CPX:sys cfmode set safeYOU ASKED TO CHANGE CF-MODE FROM 'NORMAL' TO 'SAFE'. THIS PROCEDURE CLEARS DISK D:, COPIES ALL FILES FROM C: TO D:, SWAPS C: -> Z: AND D: -> C:. THIS OPERATION MAY TAKE FEW MINUTES. PROCEED (N/Y)?y DISKs PREPARATION FOR 'SAFE' CF-MODE IN PROGRESS... Requested CF mode change to SAFE. Disk D: validation... Success. Disk D: check... Success. Disk C: check... Success. Abilis versions... Current: 8-7-0, Next: 8-7-0, Previous: 8-7-0. Disk D: purge... Completed. Boot Manager check... Installing C:\8-7-0\BM.RTB on D:\... Success. Synchronization of: 8-7-0 ... Completed. 8-6-7 ... Completed. 4431-1 ... Completed. LICENCE ... Completed. APP ... Completed. USR ... Completed. \ ... Completed. Disks swapping... C: -> Z: D: -> C: Success. Save new CF mode setting... Success. Current CF mode is SAFE. Execution success. COMMAND EXECUTED WARNING CF-MIRROR is enabled from C: to Z:, next execution at Friday 09/11/2018 06:00:00 [14:17:33] ABILIS_CPX:sys cfmode infoAbilis Compact Flash management mode configuration: Disk Mode Disk Uuid ------------------------------------------------------------------------------- C: SAFE 2 52196B13242400408C0670C69EAE3F43 Z: SAFE 1 52196B13242400408C0670C69EAE3F43
To display log of Compact Flash Mode activities type the following command:
[14:17:36] ABILIS_CPX:sys cfmode log
***** New run at 2018-11-08 14:12:33 +01:00 *****
Abilis CPX - Ver. 8.7.0/STD - Build 4431.5 - Branch 8.7
Requested CF mode change to SAFE.
Disk D: validation... Success.
Disk D: check... Success.
Disk C: check... Success.
Abilis versions...
Current: 8-7-0, Next: 8-7-0, Previous: 8-7-0.
Disk D: purge...
Completed.
Boot Manager check...
Installing C:\8-7-0\BM.RTB on D:\... Success.
Synchronization of:
8-7-0 ...
Completed.
8-6-7 ...
Completed.
4431-1 ...
Completed.
LICENCE ...
Completed.
APP ...
Completed.
USR ...
Completed.
\ ...
Completed.
Disks swapping...
C: -> Z:
D: -> C:
Success.
Save new CF mode setting... Success.
Current CF mode is SAFE.
Execution success.
***** Run end at 2018-11-08 14:14:10 +01:00 *****If the CF MODE is SAFE-DEGRADED, to return to NORMAL or SAFE mode type the corresponding command:
[17:41:13] ABILIS_CPX:sys cfmode recovery ?
NORMAL Recovery from SAFE-DEGRADED to NORMAL
SAFE Recovery from SAFE-DEGRADED to SAFE This command immediately executes the system restart.
[11:38:04] ABILIS_CPX:warm start
If in the current session the configuration was modified but not saved, the command displays a warning message and queries the User for proceeding with configuration saving or not.
In case of an affirmative answer, the save conf command is executed, the reset of the Abilis CPX isn't executed and the Control Port prompt is shown.
[11:38:04] ABILIS_CPX:warm startTHE CURRENT CONFIGURATION WAS MODIFIED BUT NOT SAVED. PROCEED WITH 'SAVE CONF' COMMAND (N/Y/A)?yVALIDATION IN PROGRESS... VALIDATION SUCCESSFULLY EXECUTED SAVE EXECUTED
If a different version of the currently running one was set to be loaded at next system startup (sys set boot version), the command displays a warning message and queries the User for proceeding with system restart.
[11:38:04] ABILIS_CPX:warm startBOOT MANAGER CONFIGURATION WAS MODIFIED: THE NEXT VERSION THAT WILL BE LOADED IS '8-5-1', WHILE THE CURRENTLY RUNNING VERSION IS '8-4-3'. PROCEED WITH WARM START (N/Y)?y
The options of warm start command:
[11:38:04] ABILIS_CPX:warm start ?WARM START [opt] System warm start is executed Allowed options: -DELAY hh:mm The system will reboot after the specified delay, <Optional> where 'hh' [0..2400], 'mm' [0..59]. -NOCALL The system will reboot as soon as all CTI calls are <Optional> closed. -CLEAR Clear any scheduled system reboot. <Optional> -SHOW Show currently set system reboot delay or condition. <Optional> -F Force system warm start interrupting any operation <Optional> in progress (E.g. configuration saving, system updating, file uploading/downloading and so on).
| Note |
|---|---|
The -f option, force system warm start interrupting any operation that is in progress (e.g. Configuration saving, system updating, file uploading/downloading and so on).
In case of the affirmative answer, the reset of the Abilis CPX is executed, while in case of negative answer the Control Port prompt is shown. |
| Tip |
|---|---|
Interesting chapter: Section 72.25.3, “Scheduled system reboot”. |
| |  | |
| 6.12. Configuration validating and saving |  | 6.14. Diagnostics and Statistics |