The system can be restarted with system reboot and shutdown with system shutdown.

The password for the platform user is chosen at install time, but can be changed using system password which will then prompt for the old password, the new password and confirmation.

Passwords must contain:

• at least one upper case letter

• at least one lower case letter

• at least one number

• at least one symbol

• be at least 16 characters long

Additional users can be created with user add <username>. Refer to the System Security : Creating additional users section.

Each user can be granted access to specific commands offering role-based access control - Refer to System Security : Granting and revoking user rights.

Each user has a unique home directory in which local files can be stored. It is the user's responsibility to manage the disk space used by these files.

The command disk diag displays the disk usage. Files in the user's directory are displayed using the standard ls command, and deleted with rm.

New applications or upgrade packages are uploaded to the platform user using scp or sftp, for example scp <filename> platform@192.168.0.1: on the remote Unix file server.

A sftp or scp of files to Cisco Unified Communications Domain Manager 10.6(1) must be done in the media directory (/opt/platform/admin/home/media), which is a writable directory.

Alternatively a downloadable URL can be downloaded directly on the Cisco Unified Communications Domain Manager 10.6(1) system using system download <URL> and the downloaded file is placed in the platform user's directory, For example: system download http://myserver/path/myfile.iso

Individual applications are installed using app install <filename>.script. A list of available applications and versions is displayed using the command app list.

ISO packages include all the individual packages required for upgrading. Upgrade the system using app upgrade <filename>.iso. Alternatively, the ISO package file system can be mounted with the system mount command, and the individual applications are visible under the media directory, and visible via the app list command.

In order to reduce the risk of disk full errors, the platform divides the file system over several disks keeping areas liable to grow outside the main root file system. The areas with the highest growth such as logs and database storage are kept on their own private file systems.

These disk mounts can be migrated onto new, larger disks and some other locations can optionally be moved onto their own disks. This is managed through the drives  command.

The current mounted file systems and mount points can be displayed using drives list mounted and drives list mountpoints respectively.

A screen showing drives list mounted and drives list mountpoints:

platform@development:~$ drives list mountpoints
Available mountpoints:
    core_services:SWAPSPACE
    core_services:appdata
platform@development:~$ drives list mounted
Mounted drives:
    sdd1 -  mongodb:dbroot
    sdc1 -  core_services:backups
platform@development:~$

The mount points are as follows:

• mongodb:dbroot is the volume used for database storage

• core_services:backups is used for default backup storage

• core_services:appdata is the main system volume used for application data in the users account

• core_services:SWAPSPACE is the swap volume used by the system

In order to add or extend an existing disk volume, follow the following steps:

• Under VMware, add an additional disk volume to the VM

• drives list displays any unused available volumes

• A free mountpoint can be linked to a new disk using drives add <disk> <mountpoint>.

• An existing used mountpoint (i.e., currently linked to a disk volume) can be linked to a new disk volume of greater size using drives reassign <disk> <mountpoint>. Existing data on the current disk will be copied to the new disk volume, and once successful, the new disk volume will be linked.

For example, the following steps can be followed to add a 250GB hard disk to the system:

1. Log into the VMware console and select Server.

2. Right-click and select Edit settings.

3. Click Add... and select Hard Disk.

4. Navigate through the rest of the wizard and edit parameters - in this case 250GB, thick provisioned.

5. Once done, log into the system as the platform user.

6. Execute a disk listing with the command drives list.

7. Reassign the disks with the command drives reassign <new disk name> mongodb:dbroot.

8. Start the application with app start.

SAN alignment is implemented using the offset value in drives offset. This value can be changed if necessary; however, the default should be sufficient for most SAN hardware.

For swap partitions, use drives checkswap to check their alignment. Use drives alignswap to fix a misaligned swap partition.