Cisco ACNS Software Deployment and Configuration Guide, Release 5.0 - Appendix A: Disk Space-Allocation Guidelines [Cisco Application and Content Networking System (ACNS) Software]

Table Of Contents

Cisco ACNS Software Disk Space-Allocation Guidelines

Disk Storage Overview

Disk Space-Allocation Guidelines

Disk Space-Allocation Guidelines for Content Engines

Disk Space-Allocation Guidelines for Content Routers

Disk Space-Allocation Guidelines for Content Distribution Managers

Commands Related to Disk File Storage Types

sysfs-Related Commands

cfs-Related Commands

mediafs-Related Commands

cdnfs-Related Commands

Updating Storage Capacity on Your Content Engines

Using a Fibre Channel Storage Array

Updating Storage Capacity Through the Content Distribution Manager GUI

Reconfiguring Storage Capacity on a Content Engine After a Storage Capacity Update

Cisco ACNS Software Disk Space-Allocation Guidelines

This appendix provides guidelines for allocating disk space based on the type of CDN device and the most common usage of the device.

Disk space in ACNS software is allocated on a per-file system basis, rather than on a per-disk basis. You can configure your overall disk storage allocations according to the kinds of client protocols you expect to use and the amount of storage that you need to provide for each of the functions described in Table A-1.

This appendix discusses the following topics:

•Disk Storage Overview

•Disk Space-Allocation Guidelines

•Commands Related to Disk File Storage Types

•Updating Storage Capacity on Your Content Engines

Disk Storage Overview

ACNS software recognizes four types of disk storage, each with an associated function, as described in Table A-1.

Table A-1 Cisco ACNS Software Disk Storage

Disk Storage Type

Function

sysfs (system file system)

Stores log files, including transaction logs, syslogs, and internal debugging logs. Also can store image files and configuration files.

cfs (cache file system)

Caches HTTP and FTP objects.

mediafs (media file system)

Caches RealProxy files and on-demand cached WMT content.

cdnfs (CDN file system)

Stores all pre-positioned CDN content.

Disk storage can be configured and viewed by using the commands listed in Table A-2.

Table A-2 Disk-Related Commands

Command

Syntax

Description

disk

disk add diskname {cdnfs {remaining | partition_size} | cfs {remaining | partition_size} | mediafs {remaining | partition_size} | sysfs {remaining | partition_size}}

disk cancel-config

disk config sysfs {remaining {{cdnfs {remaining | partition_size} | cfs {remaining | partition_size} | mediafs {remaining | partition_size}} | partition_size {{cdnfs {remaining | partition_size} | cfs {remaining | partition_size} | mediafs {remaining | partition_size}}}

disk raid-array add-array

disk raid-array repair diskname

disk recover

Configures the disk resources for Content Engines, Content Routers, and Content Distribution Managers. (The disk raid-array commands are for the CDM-4650 only.)

show disks

show disks configured

show disks current

show disks details

show disks raid-info

show disks storage-array

show disks storage-array [detail]

Displays information about the disk configurations.

Disk Space-Allocation Guidelines

This section describes the disk-related commands and provides guidelines for allocating disk space on the different types of hardware configurations that use ACNS software.

To display the current disk space configuration, use the show disks current EXEC command.
ContentEngine# show disks current
SYSFS                 1.0GB       3.5%
CFS                   0.0GB       0.0%
MEDIAFS               0.0GB       0.0%
CDNFS                	28.2GB      96.5%
FREE                  0.0GB       0.0%
Note The show disks details command shows the amount of disk space that is allocated to system use. The CE7325 and CE7305 each use 10.5 GB, the CE565 uses 8.2 GB, and the CE510 uses 6 GB. On legacy devices, system usage space is 3 to 4 GB. This detail is not shown by using the show disks current command.

To configure the disk allocations, use the disk config EXEC command. This command takes file system type and size as parameters. Size can be designated in megabytes, gigabytes, or as a percentage of the system total storage. In the following example, 10 percent of the total storage is allocated to the sysfs and 30 percent to every other file system.
ContentEngine# disk config sysfs 10% cfs 30% mediafs 30% cdnfs 30%
Disk configured successfully.
New configuration will take effect after reload.
Please remove this device from the CDM (if any) before reboot this device, as this 
device's configuration will be stale due to disk repartition.
Caution Using the disk config command deletes all existing sysfs, mediafs, and cfs content when the disk configuration takes effect during reboot. Content in cdnfs, however, is preserved. Use this command with care.

The disk configuration does not take effect until after the next reboot. To view what the configuration is going to be after the next reboot, use the show disks configured command.
ContentEngine# show disks configured 
SYSFS 						10%
CFS 						30%
MEDIAFS 						30%
CDNFS 						30%
To cancel the disk configuration, use the disk cancel-config command.
ContentEngine# disk cancel-config 
Disk configuration canceled successfully
Note The disk cancel-config command is effective only before a reboot. After reboot, the allocation has already taken effect and can only be changed by issuing another disk config command.

After you set up a new disk configuration, messages similar to the following appear:
Using new disk configuration you specified before reboot.
Removing old disk contents...
Creating new disk configuration...
Initializing new file systems (may take several minutes)...
Mounting all file systems...
To view disk details, use the show disks details command.
ContentEngine# show disks details
disk00:Normal          (h00 c00 i00 l00)    17499MB( 17GB)
        disk00/03:CDNFS         	9044MB	(  8GB) mounted at/sonoma/state
        disk00/04:SYSFS         	2047MB	(  1GB) mounted at/local/local1
        disk00/05:CFS           	2047MB	(  1GB)
        disk00/06:MEDIAFS       	1023MB	(  0GB) mounted at/media/media1
        System use:             	3317MB	(  3GB)
        FREE:									16MB	(  0GB)
disk01:Not present
Note The show disks details command shows that there is 3 to 4 GB of disk space allocated to system use. This detail is not shown by using the show disks current command.

To show the space allocation in each individual file system type, use the appropriate show command. For example:
ContentEngine# show cfs volumes 
cfs 00:/dev/raw/raw1         3812351KB       mounted
ContentEngine# show mediafs volumes 
mediafs 00: /media/media1         1048577KB
mediafs 01: /media/media2         8730623KB
ContentEngine# show cdnfs volumes 
cdnfs 00: /uns/uns1 13456383KB									99% free
Disk Space-Allocation Guidelines for Content Engines

Content Engine models such as the Content Engine 500 series and the Content Engine 7300 series that are used as general-purpose Content Engines can be configured for the type of traffic you have on your network. Streaming files are larger, in which case you might allocate more space to cdnfs storage. For example:
ContentEngine# disk config sysfs 10% cfs 20% mediafs 20% cdnfs 50%
Note Because of memory restrictions in the CE-507, the maximum disk storage allocation for the cfs is 6 GB. For example, you might adjust the disk storage allocations for the CE-507 as follows:
ce-507# disk config sysfs 2GB cfs 6GB mediafs 2GB cdnfs remaining

For higher-end models such as the CE-7320 that might be used as a dedicated HTTP cache or RealProxy cache, either cfs storage or mediafs storage could be given more disk space. For example:
ContentEngine# disk config sysfs 10% cfs 80% mediafs 10% cdnfs 0%
ContentEngine# disk config sysfs 10% cfs 10% mediafs 80% cdnfs 0%
If both RealProxy or WMT caching and HTTP caching are important, disk space could be evenly split between cfs storage and mediafs storage. For example:
ContentEngine# disk config sysfs 10% cfs 45% mediafs 45% cdnfs 0%
Note The mediafs storage must be configured and RealProxy Real-Time Streaming Protocol (RTSP) proxy service must be enabled before any RealProxy files can be cached in the mediafs storage space. For information on how to enable RealProxy, refer to Chapter 10 of the Cisco ACNS Software Caching Configuration Guide, Release 5.0.

Lower-end models, especially those models with AV output, are often deployed in branch offices to store pre-positioned content. These models could be configured as follows:
ContentEngine# disk config sysfs 10% cfs 10% mediafs 0% cdnfs 80%
If RealProxy or WMT caching is being used, allocate sufficient mediafs storage and adjust cfs and cdnfs storage as desired. For example:
ContentEngine# disk config sysfs 10% cfs 10% mediafs 10% cdnfs 70%
Note The mediafs storage space should only be configured if RealProxy or WMT files are being cached.

Disk Space-Allocation Guidelines for Content Routers

In ACNS 5.x software, Content Routers are used as DNS servers for the delegated DNS zone used in Simplified Hybrid Routing. They do not store any content, nor do they participate in acquisition or distribution of pre-positioned content. The only disk space that needs to be configured on the Content Router is sysfs.
CR4430# disk config sysfs 100% cfs 0% mediafs 0% cdnfs 0%
Disk Space-Allocation Guidelines for Content Distribution Managers

Content Distribution Managers are used to manage content distribution for CDNs. Because the Content Distribution Manager does not store content, the only file system that needs to be configured is the sysfs. For example:
CDM4630# disk config sysfs 5GB
Commands Related to Disk File Storage Types

This section lists the commands related to viewing, manipulating, and maintaining the four different disk storage areas.

sysfs-Related Commands

The system file system (sysfs) storage space stores system image files. At least 1 GB of storage must be allocated to the sysfs; however, you can allocate more storage to the sysfs depending on your network requirements. The content of sysfs storage can be viewed or manipulated with the commands listed in Table A-3.

Table A-3 sysfs-Related Commands

sysfs-Related Command

Syntax

Description

cd

cd directoryname

Changes the current directory.

copy

copy cdrom install filedir filename

copy compactflash install filename

copy disk ftp {hostname | ipaddress} remotefiledir remotefilename localfilename

copy disk startup-config filename

copy ftp disk {hostname | ipaddress} remotefiledir remotefilename localfilename

copy ftp install {hostname | ipaddress} remotefiledir remotefilename

copy running-config disk filename

copy running-config startup-config

copy running-config tftp {hostname | ipaddress} remotefilename

copy startup-config disk filename

copy startup-config tftp {hostname | ipaddress} remotefilename

copy system-status disk filename

copy tech-support disk filename

copy tech-support tftp {hostname | ipaddress} remotefilename

copy tftp disk {hostname | ipaddress} remotefilename localfilename

Copies configuration or image files to disk, Flash memory, or remote server.

cpfile

cpfile sourcefile destinationfile

Copies files.

delfile

del filename

Removes a file.

deltree

deltree directory

Removes directory and all subdirectories.

dir

dir [directory]

Displays long list of files in a directory.

find-pattern

find-pattern {binary reg-express filename | case {binary reg-express filename | count reg-express filename | lineno reg-express filename | match reg-express filename | nomatch reg-express filename | recursive reg-express filename} | count reg-express filename | lineno reg-express filename | match reg-express filename | nomatch reg-express filename | recursive reg-express filename}

Searches for a particular pattern in a file.

install

install imagefilename

Installs an image file.

lls

lls [directory]

Displays directory files in long list format.

logging

logging console enable

logging console priority loglevel

logging disk {enable | filename filename | priority loglevels | recycle size}

logging facility facility

logging host {hostname | ipaddress | priority loglevel}

Configures system logging (syslog). Log files are written to the first mounted sysfs volume, /local1.

The default file name is /local1/syslog.txt. The default file name can be overwritten using the filename option.

ls

ls [directory]

Displays a list of files or subdirectory names within a directory.

mkdir

mkdir directory

Makes a directory.

mkfile

mkfile filename

Makes a new 0-byte file (for testing).

pwd

pwd

Displays path name of present working directory.

rename

rename oldfilename newfilename

Renames a file.

rmdir

rmdir directory

Removes a directory.

show statistics

show statistics http usage

show statistics transaction-logs

Displays statistics relevant to sysfs storage.

transaction-log force

transaction-log force {archive | export}

Forces archive of working log file to make a transaction log file.

transaction-logs

transaction-logs archive interval every-day {at hour:minute | every hour}

transaction-logs archive interval every-hour {at minute | every minute}

transaction-logs archive interval every-week [on weekdays at hour:minute]

transaction-logs archive max-file-size filesize

transaction-logs enable

transaction-logs export enable

transaction-logs export ftp-server {hostname | servipaddrs} login passw directory

transaction-logs file-marker

transaction-logs format {apache | custom | extended-squid | squid}

transaction-logs sanitize

Configures transaction logging.

type

type filename

Displays a file.

cfs-Related Commands

The cache file system (cfs) storage space caches HTTP and FTP objects. The contents of cfs storage cannot be examined or modified. Commands related to maintaining cfs storage are listed in Table A-4.

Table A-4 cfs-Related Commands

cfs-Related Command

Syntax

Description

cfs

cfs clear partition [force]

cfs format partition

cfs mount partition

cfs reset partition

cfs sync partition

cfs unmount partition

Manipulates the Content Engine cfs.

show cfs

show cfs {statistics | volumes}

Displays cfs status.

show statistics

show statistics cfs

show statistics http usage

Displays cfs-related statistics.

mediafs-Related Commands

ACNS software caches RealProxy files in the media file system (mediafs) storage space. The content in the mediafs storage space cannot be examined. Commands related to maintaining mediafs storage are listed in Table A-5.

Table A-5 mediafs-Related Commands

mediafs-Related Command

Syntax

Description

mediafs-division

mediafs | mediafs-division {wmt-cache-space percent_space real-cache-space percent_space}

Divides the mediafs space percentage between the WMT cache and the RealProxy cache.

show mediafs

show mediafs volumes

Displays media file system volumes.

show statistics

show statistics mediacache real requests

show statistics mediacache real savings

Displays mediafs-related statistics.

cdnfs-Related Commands

The Content Delivery Network file system (cdnfs) storage space is used to store pre-positioned streaming media content. Commands related to maintaining cdnfs storage are listed in Table A-6.

Table A-6 cdnfs-Related Commands

cdnfs-Related Command

Syntax

Description

cdnfs browse

cdnfs browse start

Browses through CDN files and directories.

cdnfs cleanup

cdnfs cleanup {info | start | stop}

Cleans up garbage entries in the cdnfs.

cdnfs delete-unused-ecdnfs-files

cdnfs delete-unused-ecdnfs-files

Deletes legacy E-CDN application data files (data files only).

cdnfs lookup

cdnfs lookup URL

Looks up the specified URL in the cdnfs and displays information about the file, if the file is present.

show cdnfs

show cdnfs volumes

Displays information for cdnfs volumes.

show statistics

show statistics cdnfs

Displays cdnfs-related statistics.

Note On upgrading from ACNS 4.2 software to ACNS 5.0 software, any ecdnfs file systems are automatically changed to cdnfs file systems. Files are not deleted unless the administrator specifically deletes them.

Updating Storage Capacity on Your Content Engines

If your storage requirements have changed, you can attach a Cisco Storage Array to your Content Engines for additional storage capacity.

You can also delete existing storage (nonsystem) disks or replace storage disks in your CDN.

Note For information on how to install or uninstall a Storage Array, refer to the hardware installation guide that shipped with your storage device.

Using a Fibre Channel Storage Array

Some hardware models have a Fibre Channel interface and support a Fibre Channel storage array. After attaching a Fibre Channel storage array, you must assign Fibre Channel storage through the Fibre Channel storage array GUI. (Refer to the documentation from your Fibre Channel storage array vendor.)

After you assign Fibre Channel storage through the storage array GUI, you must reload the Content Engine for the Fibre Channel storage assignment to be recognized. You must reload the Content Engine before assigning storage to the different file systems, if you choose to do so, and then you must reload the Content Engine a second time for the file system disk configuration to take effect.

Do not attempt to assign the Fibre Channel storage to the Content Engine and configure the file systems with a single reload of the Content Engine. If you do, the Fibre Channel storage assignment is recognized, but the disk configuration is not applied. An error message appears at bootup, similar to the following:
----------------------------------------------------------------------------
ruby_disk:physical disk setup appears to have changed
ruby_disk:not applying 'disk config' changes. Please re-enter via CLI.
----------------------------------------------------------------------------
If you encounter this error message, reenter your disk configuration and reload the Content Engine for the disk configuration to be applied. (For CLI instructions, see the "Configuring Disk Space" section.)

Updating Storage Capacity Through the Content Distribution Manager GUI

After you have changed the storage capacity of a Content Engine by adding or deleting a Storage Array from your hardware, you must update the system to recognize the new storage capacity.

To update your system with new storage capacity information, follow these steps:

Step 1 In the Content Distribution Manager GUI, choose Devices > Content Engines.

Step 2 Click the Edit icon next to the name of the Content Engine that you want to update.

Step 3 Verify the current disk configuration:

•In the Contents pane, choose Show/Clear Commands > Show Commands. The Show Commands window appears.

•Choose disks from the drop-down list and enter current or details in the Arguments field.

Step 4 Calculate the storage you had available before you added or deleted a Storage Array by using the following equation:

Prior available storage = Total storage capacity of device before addition or deletion - Total storage reserved for channels

Note The documentation that came with your Content Distribution Manager or Content Engine should tell you how much storage capacity the device has at the time of manufacture. This should give you the value for the total storage capacity of the device before addition or deletion.

The total storage reserved for channels can be determined by adding up the capacity value for all the channels to which the device is subscribed.

To find the total storage reserved for each channel to which the Content Engine is subscribed, follow these steps:

a. Choose Devices > Content Engines.

b. Click the Edit icon next to the name of the Content Engine that you want to update.

c. In the Contents pane, choose CDN Settings > Channels. The View Channels subscribed to Content Engine window appears, listing all of the channels that the Content Engine is subscribed to.

d. Click each channel in the list and add up the disk quota for each channel.

Step 5 In the Contents pane choose Platform > File System. The File System Configuration window appears. (See Figure A-1.)

Figure A-1 File System Configuration Window

Step 6 Enter a value in the Configured Size field for each file system that you want to update.

Step 7 Choose a unit of measure from the drop-down list.

Step 8 Click Submit.

Step 9 Reboot your Content Engine for the disk configuration to take effect:

a. Choose Devices > Content Engines.

b. Click the Edit icon next to the name of the Content Engine that you want to reboot. The Modifying Content Engine window appears.

c. Click the Reboot icon. You are prompted to confirm your decision.

d. Click OK to begin rebooting the Content Engine.

Step 10 Verify that the new storage capacity is recognized:

a. In the Contents pane, choose Show/Clear Commands > Show Commands. The Show Commands window appears.

b. Choose disks from the drop-down list and enter configured in the Arguments field.

c. Compare the new available storage value to the amount of storage you had before adding or deleting a Storage Array to verify whether or not the new storage capacity is recognized.

d. If the new available storage value does not reflect the addition or deletion of a Storage Array, go to the CLI to reissue the add or delete disk command and then repeat the procedure to reinitialize the update.

Reconfiguring Storage Capacity on a Content Engine After a Storage Capacity Update

A Content Engine cannot have a storage capacity that is less than the sum of the space required by all the channels subscribed to it. If, as a result of deletion, the storage capacity of the Content Engines falls below the required size, the system prompts you to remove the Content Engine for some of the channels.

To replace the content that was lost when you deleted a storage disk, the Content Engine automatically initiates content replication from its parent Content Engine. It replicates only that content which was lost.

To remove a Content Engine from a channel, follow these steps:

Step 1 From the Content Distribution Manager GUI, choose Channels > Channels.

Step 2 Click the Edit icon next to the name of the channel that you want to change. The Modifying Channel window appears.

Step 3 In the Contents pane, choose Assign content engines. The Assigning Content Engines to Channel window appears.

Step 4 Check the check box next to the name of the Content Engines that you wish to remove from this list and click Remove Selected CEs.

Step 5 Click Submit. The browser window refreshes, listing the updated channels. The list of Content Engines in the channel shows the updated count.