Cisco Internet Streamer CDS 2.5 Software Configuration Guide
Maintaining the Internet Streamer CDS
Downloads: This chapterpdf (PDF - 532.0KB) The complete bookPDF (PDF - 4.65MB) | Feedback

Maintaining the Internet Streamer CDS

Table Of Contents

Maintaining the Internet Streamer CDS

Software Upgrade

Getting a Software File from Cisco.com

Pre-positioning a Software File

Finding the Software Version of the Devices

Configuring the Software Image Settings

Upgrading the Software

Interoperability Considerations

Upgrading Software by Device Groups

Software Upgrades by Device

Software Upgrade Using a CD-ROM

Rebooting Devices

Deleting a Device

Deleting a Warm Standby CDSM

Replacing a Device

Replacing a CDSM

Replacing an SE or SR

Backup and Recovery Procedures

Performing Backup and Restore on the CDSM Database

Using the Cisco CDS Software Recovery CD-ROM

System Software Components

Getting the Cisco CDS Software Recovery File from Cisco.com

Installing the Software Using the Recovery CD-ROM

Recovery CD-ROM Options

Recovering the System Software

Recovering a Lost Administrator Password

Recovering from Missing Disk-Based Software

Recovering CDS Network Device Registration Information

Disk Maintenance

Disk Latent Sector Error Handling

Removing and Replacing Hard Disk Drives

Replacing a Disk

Removing Content

Single Content Removal

Batch Content Removal


Maintaining the Internet Streamer CDS


This chapter explains how to perform common administrative tasks including updating system software, hard disk drive maintenance, and rebooting and deleting devices. The following major topics are covered:

Software Upgrade

Rebooting Devices

Deleting a Device

Replacing a Device

Backup and Recovery Procedures

Disk Maintenance

For information about database maintenance, see the "Scheduling Database Maintenance" section.

Software Upgrade

The software upgrade section covers the following topics:

Getting a Software File from Cisco.com

Finding the Software Version of the Devices

Configuring the Software Image Settings

Upgrading the Software

Software Upgrades by Device

Getting a Software File from Cisco.com

To get a software file from Cisco.com, do the following:


Step 1 Launch your web browser and enter the following URL:

http://www.cisco.com/cisco/software/navigator.html

The Select a Product page is displayed if you have recently logged in; otherwise, the Log In page is displayed.

Step 2 Log in to Cisco.com using your designated username and password. The Video and Content Delivery page is displayed, listing the available software products.

Step 3 Choose Products > Video and Content Delivery > Content Delivery Systems > Content Delivery Applications > Cisco Internet Streamer Application. The Downloads page is displayed.

Step 4 Click the software release you want. The page refreshes and the software image files are displayed.

Step 5 Click the link for the software image file you want.

If this is the first time you have downloaded a file from Cisco.com, the Cisco Systems Inc., Encryption Software Usage Handling and Distribution Policy is displayed. Read the policy, fill in the unfilled fields, and click Accept.

If you previously filled out the Encryption Software Usage and Handling and Distribution form, the form does not display again.

The Download page is displayed with the information about the software image file and a Download link.

Step 6 Click Download Now to download the file, or click Add to cart to select more image files before downloading them. The Download Cart page is displayed.

Step 7 Click Proceed With Download. The Cisco End User Software License Agreement is displayed.

Step 8 Read the agreement and click Agree. The Download Software page is displayed.

Step 9 Choose a download option, either Download Manger Option or Non Java Download Option. A new window displays the filename of the ISO image file.

Step 10 Click Download. The File Download dialog box is displayed.

Step 11 Click Save. The Save As dialog box is displayed.

Step 12 Navigate to the location where you want to save the file and click Save. The file downloads.


Pre-positioning a Software File

A software file is pre-positioned in the same manner as any other content item. Pre-positioning allows you to conserve bandwidth usage across the WAN and avoid congesting your network during updates. The software file is fetched one time from the origin server, replicated across your network, and stored in Service Engine caches in your LAN.

To pre-position a software file, you must complete the following tasks:

Define a delivery service.

Assign devices to the delivery service.

Define the software file that you want to pre-position by using a Manifest file or the CDSM delivery service content page.

Check the device replication status.

See Chapter 5 "Configuring Services" for more information.


Note Only Service Engines that are assigned to the delivery service can be updated using pre-positioned software files. Service Routers and CDSMs do not have pre-positioned content; therefore, you cannot use the pre-positioned method for device updates for these devices.


Sample Manifest File to Pre-position a Software File

You can use the following sample Manifest file to pre-position a software file by replacing the URL with a valid software file URL:

<CdnManifest>
<item src="http://your-web-server.com/folder/upgrade.bin" />
</CdnManifest>
 
   

The server name or IP address of the URL in the Manifest file (and in the Software File URL field in the Software File Settings page must match either the Origin Server field or the Service Router Domain Name field in the Content Origin page).

Finding the Software Version of the Devices

The CDSM Home page gives a brief summary of the software versions in use on all the devices in the CDS network.

To view the software version running on a particular device, choose Devices > Devices. The Devices Table page displays the software version for each device listed.

Clicking the Edit icon next to the device name in the Devices Table page displays the Devices home page, which shows the software version for that device.


Note The software version is not upgraded until a software upgrade has been successfully completed. If a software upgrade is in progress, the version number displayed is the base version, not the upgraded version number.


Configuring the Software Image Settings

To upgrade your CDS software release, you must first configure the software image settings.

To configure the software image settings, do the following:


Step 1 Choose System > Software Image Management. The Software Files Table page is displayed.

Step 2 Click the Create New icon in the task bar. The Software Image page is displayed (Figure 8-1).

Figure 8-1 Software Image Page

Step 3 In the Software Image URL field, enter the URL for the .bin software file that you downloaded from Cisco.com.

a. Choose a protocol (http or ftp) from the drop-down list.

b. Enter the URL of the software file; for example, a valid URL might look like this:

http://internal.mysite.com/cds/CDS-2.x.x-K9.bin

In this URL, CDS-2.x.x-K9 is the name of the software upgrade file. (The filename might include the version number.)


Note If you are using a pre-positioned software file and you are entering the URL manually (rather than using the Select File from Delivery Service option), the server name or IP address of the URL in the Software Image URL field must match either the Origin Server field or the Service Routing Domain Name field in the Content Origin page of the delivery service. This is not a requirement if you are downloading the software file directly from the origin server. (See the "Pre-positioning a Software File" section for details.)


Alternatively, click Select File from Delivery Service. A separate window displays that allows you to choose a delivery service, set criteria, search the delivery service, and select the software file that you want to use for the software upgrade. (You must first pre-position the software file in the delivery service. See the "Pre-positioning a Software File" section.)

Step 4 If your server requires user login authentication, enter your username in the Username field and enter your login password in the Password field. Enter the same password in the Confirm Password field.

Step 5 Enter the software version number in the Software Version field. You can copy this number from the version portion of the software filename in the software file URL.

Specify the version in one of two formats: X.Y.Z-bB or X.Y.Z.b.B, where X = major version, Y = minor version, Z = maintenance version, b = build letter, and B = build number.

Step 6 If you want the size of the software file considered during validation, enter a file size (in bytes) in the File Size field. If you leave this field blank, the URL is checked without regard to the software file size.

Step 7 To validate the Software Image URL, Username, and Password fields, click the Validate Software Image Settings button.

When you click the Validate Software Image Settings button, the following occurs:

Software file URL is resolved.

Connection to the software file URL is established using the username and password, if specified.

If a file size is specified, the actual size of the software file is obtained and compared against the value in the File Size field.

Message is returned, indicating success or errors encountered.

Step 8 In the Advanced Settings section, check the Auto Reload check box to automatically reload a device when you upgrade the software.

Step 9 If you want, you can choose one of three download methods:

Default—Uses pre-positioned content but always falls back to direct download.

Prepositioned Only—Uses the local file copy if the software file URL references pre-positioned content and its replication status is complete.

Direct Download Only—Directly downloads the file using the software file URL.


Note If you choose Prepositioned Only, the software file settings that you define in this page cannot be used to upgrade a CDSM or an SR, because these devices do not have pre-positioned content.


Step 10 For downgrades only, specify the CDSM IP address to be used for device registration in the CDSM IP Address field.

The CDSM IP Address field is the IP address of a CDSM after the software is downgraded. (This field is optional and only applies for downgrades.) After the downgrade, the SE registers with the CDSM with the IP address specified in this field.

Step 11 Click Submit.

To delete a software file, click the Delete icon in the task bar.


Caution If your browser is configured to save the username and password for the CDSM, the browser auto-populates the Username and Password fields in the Software Image page. You must clear these fields before you click Submit.


The software file that you want to use is now registered with the CDSM. When you perform the software upgrade or downgrade, the URL that you just registered becomes one of the choices available in the Update Software page. (See the "Upgrading the Software" section.)

Upgrading the Software

When upgrading software in your CDS network, begin with Service Engines and Service Routers before upgrading the CDSM. The CDSM reboots at the conclusion of the upgrade procedure, causing you to temporarily lose contact with the device and the user interface. After the CDSM has upgraded its software and rebooted, it may be unable to communicate with devices running different versions of the CDS software.


Caution Primary and standby CDSMs must be running the same version of CDS software. If they are not, the standby CDSM detects this and does not process any configuration updates it receives from the primary CDSM. You need to upgrade your standby CDSM first, and then upgrade your primary CDSM. We also recommend that you create a database backup for the primary CDSM and copy the database backup file to a safe place before you upgrade the software.


Note For software downgrades of systems with primary and standby CDSMs, you need to do the following:

1. If you are using the CDSM GUI, downgrade the standby CDSM first, followed by the primary CDSM.

If you are using the CLI, downgrade the primary CDSM first , followed by the standby CDSM.

2. After downgrading the primary and standby CDSMs, using the CLI, log in to each CDSM and run the following commands:

cms database downgrade
cms enable
 
   

3. Downgrade the software on the Service Routers, followed by the Service Engines.



Caution To upgrade the software image on a server, you first need to offload a server for maintenance. Once the server has been fully offloaded, you can upgrade the software. After updating the software, uncheck the Server Offload check box to allow the server to receive client requests from the Service Router. See the Server Offload field in Table 4-6 for more information.

Interoperability Considerations

In general, a CDS network is upgraded gradually, so that your network might consist of nodes with different software versions for the duration of time it takes to upgrade all nodes. Dissimilar software versions are not supported in the long term, and only the interoperability considerations listed below are supported until all devices are running the same software version. You can expect the following behavior during an upgrade or downgrade of your network:

CDS network continues to operate with mixed versions up to one major or minor version difference in a deployed solution.

New features that depend on device cooperation might not be fully functional until the CDS network upgrade is complete, but no existing features are affected.

While being upgraded, a node is unavailable for a short time.

All nodes, other than the node being upgraded, continue to operate at full capacity. The availability of other nodes is not affected during an upgrade.

Content is preserved during an upgrade or downgrade unless you remove a delivery service.

All logs are preserved during an upgrade or downgrade, unless you change the disk configuration. Anytime disk space is reconfigured, the logs are automatically removed.

We strongly recommend that you upgrade your CDS network devices in the following order:

1. Multicast sender Service Engines

2. Multicast receiver Service Engines

3. Non-Content Acquirer Service Engines

4. Content Acquirer Service Engines

5. Service Routers

6. Standby CDSMs (Upgrade before primary when using the GUI only.)

7. Primary CDSM


Note An SR running the Release 2.4 software is not compatible with an SE running the Release 2.3.x software. This incompatibility issue does not occur if you follow the recommended upgrade order.



Note When you upgrade CDSMs using the CLI, we recommend that you upgrade your primary CDSM first, and then upgrade your standby CDSM. Primary and standby CDSMs must be operating with exactly the same software release as each other for failover to be successful.


Upgrading Software by Device Groups


Note This procedure is for Service Engines only. Service Routers and CDSMs cannot be associated with device groups.


To upgrade your software on multiple Service Engines, do the following:


Step 1 Choose Devices > Device Groups. The Device Groups Table page is displayed.

Step 2 Click the Edit icon next to the name of the device group that you want to upgrade. The Device Group page is displayed.

Step 3 From the left-panel menu, choose Software Update. The Software Update for Device Group page is displayed.

Step 4 Choose the software file URL from the Software File URL list by clicking the radio button next to the filename.

Step 5 Click Submit.

To view progress on an upgrade, go to the Devices Table page (Devices > Devices). Software upgrade status messages are displayed in the Software Version column. These intermediate messages are also written to the system log on the Service Engines. See Table 8-1 for a description of upgrade status messages.


Table 8-1 Upgrade Status Messages 

Upgrade Status Message
Condition

Pending

The request has yet to be sent from the CDSM to the device, or receipt of the request has yet to be acknowledged by the device.

Downloading

The download method for the software file is being determined.

Proceeding with Pre-positioned Download

The download method for the software file is detected as pre-positioned. Proceeding with download of a pre-positioned software file.

Proceeding with Download

The download method for the software file is detected as direct download. Proceeding with the request for direct download of the software file.

Download in Progress (Completed ...)

Direct download of the software file is being processed. "Completed" indicates the number of megabytes processed.

Download Successful

The direct download of the software file has been successful.

Download Failed

The direct download of the software file cannot be processed. Further troubleshooting is required; see the device system message log.

Proceeding with Flash Write

A request has been made to write the software file to the device flash memory.

Flash Write in Progress (Completed ...)

The write of the device flash memory is being processed. "Completed" indicates the number of megabytes processed.

Flash Write Successful

The flash write of the software file has been successful.

Reloading

A request to reload the device has been made to complete the software upgrade. The device may be offline for several minutes.

Reload Needed

A request to reload the device has not been made. The device must be reloaded manually to complete the software upgrade.

Canceled

The software upgrade request was interrupted, or a previous software upgrade request was bypassed from the CLI.

Update Failed

The software upgrade could not be completed. Troubleshooting is required; see the device system message log.


Software Upgrades by Device

Use this upgrade procedure for Service Routers and CDSMs. You can also use this upgrade procedure to upgrade Service Engines one at a time.

To upgrade your software on a single device, do the following:


Step 1 Choose Devices > Devices. The Devices Table page is displayed.

Step 2 Click the Edit icon of the device that you want to upgrade. The Devices home page is displayed.

Step 3 Verify that the device is not already running the version that you plan to upgrade to, and that the current version has an upgrade path to the version that you plan to upgrade to.

Step 4 Click Update Software. The Software Update page is displayed.

Step 5 Choose the software file URL from the Software Files list by clicking the radio button next to the filename.

Step 6 Click Submit, and then click OK to confirm your decision.

The Devices Table page is displayed again. You can monitor the progress of your upgrade from this page.

Software upgrade status messages are displayed in the Software Version column. These intermediate messages are also written to the system log on the Service Engines. See Table 8-1 for a description of upgrade status messages.


Software Upgrade Using a CD-ROM


Note For the CDE200, do not use the internal CD-ROM drive for software upgrade procedures. Use the external USB CD-ROM drive for all procedures that require a CD-ROM.

For the CDE100, use the internal CD-ROM drive for recovery or remanufacture procedures.

Upgrading the software using a CD-ROM is not supported on the CDE220. Use one of the other methods. described in the "Upgrading Software by Device Groups" section or the "Software Upgrades by Device" section.


To perform a software upgrade using a CD-ROM, first download the software image file and copy the file to a CD-ROM. For more information on downloading the software image file, see the "Getting a Software File from Cisco.com" section.

To install the system software by using a CD-ROM, perform the following steps:


Step 1 Plug a USB CD-ROM drive into a USB port on the device.

Step 2 Insert a CD-ROM with the CDS software into the USB CD-ROM drive, and boot the device.

Step 3 Log in to the device and enter the copy cdrom install /images <filename> command. Following is an example of this command and the output.

SE# copy cdrom install /images CDS24.bin
Reading image file ( may take 30 seconds ) ...
cookie_check: Skip supported platform check for Model:CDE220-2G2
Reclaiming unused flash safe state sectors ... Done.
Installing phase3 bootloader...
Installing system image to flash:  done.
The new software will run after you reload the device.

Step 4 Disconnect the USB CD-ROM drive and reload the device.


Rebooting Devices

You can reboot a device or device group. The CDSM performs a controlled shutdown of all devices and then restarts the operating system on each device.

To reboot an individual device, do the following:


Step 1 Choose Devices > Devices.

Step 2 Click the Edit icon next to the device name that you want to reboot. The Devices home page is displayed

Step 3 In the task bar, click the Reload icon. You are prompted to confirm your decision.

Step 4 To begin rebooting the device, click OK.


To reboot an entire device group, do the following:


Step 1 Choose Devices > Device Groups.

Step 2 Click the Edit icon next to the name of the device group that you want to reboot. The Device Group page is displayed.

Step 3 In the task bar, click the Reboot All Devices in Device Group icon. You are prompted to confirm your decision.

Step 4 To begin rebooting each SE in the device group, click OK.


Deleting a Device

You can delete a device if the device is experiencing unresolvable problems or when its network address or configuration has changed and you need to add the device back to the CDS network using its new address and configuration information.


Caution If you delete the only SR in your CDS network, you are removing the ability of your CDS network to fill user requests.

When you delete an SE from the CDS network, you are removing that device and the content it contains from the routing scheme that the CDS uses to fill user requests. Although the CDS routes requests around SEs that are busy, offline, or missing, removing an SE may affect the speed at which the CDS network can serve user requests.


Note You cannot delete an SE if it is the only device assigned to a location that is designated as the root location (Content Acquirer) for a delivery service and there are other SEs associated with the delivery service. You can delete the Content Acquirer for a delivery service if the Content Acquirer is the only SE associated with that delivery service. However, deleting the only SE in a delivery service makes the delivery service unable to deliver content. If you receive an error message referencing the Content Acquirer for a delivery service, add more SEs to that location, or change the root location by choosing an SE in a different location to be the Content Acquirer for the delivery service before attempting to delete the SE again.


Removing the device from the CDS network involves using the CLI to shut down CDS network services and deregister the node. If you are removing the device because of hardware failure and it cannot be accessed through its CLI, you can remove the device by using the CDSM; however, the device continues to store its registration information until you deregister it by using the CLI.

Before a device can be removed from the CDS network, the following conditions must be met:

Device must have been activated in the CDSM.

CDSM must be operating.

Device must have the correct CDSM IP address or hostname configured.

CDSM IP address or hostname must be that of the primary CDSM.

Device must not be the Content Acquirer for any delivery service.

Deleting a device from the CDS network involves using the CLI to remove the registration information from the device itself and removing the registration record from the CDSM.


Note Do not use the CDSM to delete a device while the device is still active and registered. The CDSM delete feature removes only the device's registration record from the CDSM; it does not deregister the device. The device retains its registration information and continues to contact the CDSM; however, the CDSM no longer recognizes the device.

If for some reason the CDSM loses the registration record of a device, use the cms deregister force command on the device to remove all its registration information. Then use the cms enable command to reregister the device with the CDSM as though it were a new node in the CDS network.


To remove and deregister a device, do the following:


Step 1 Open an SSH session to the device CLI.

Step 2 In global configuration mode, enter the no cms enable command.

SE# configure
SE(config)# no cms enable
 
   

Note Issuing the no cms enable command does not disable acquisition and distribution services on the device; however, issuing the cms deregister command does. The cms deregister command disables the CMS, all acquisition and distribution services, and all routing communications to and from this device.


Step 3 In EXEC mode, enter the cms deregister command.

SE(config)# exit
SE# cms deregister
 
   

Note The cms deregister command cleans up the database automatically. You do not need to use the cms database delete command.

If the deregistration fails, the best practice is to resolve any issues that caused the deregistration failure; for example, the Service Engine is the Content Acquirer of a delivery service and cannot be deleted or deactivated. In this case, assign a different SE as the Content Acquirer in each delivery service where this SE is assigned as the Content Acquirer and try the cms deregister command again.


Step 4 If for some reason the deregistration fails, you can force the deregistration by using the cms deregister force command.

SE# cms deregister force
 
   

Note Take note of any messages stating that the deregistration failed and make sure to resolve them before reregistering the device with the same CDSM or registering the device to another CDSM. The cms deregister force command forces the deregistration to continue.


Step 5 To add the device back into the CDS network, reregister the device with the CDSM by using the cms enable command in global configuration mode.

SE# configure
SE(config)# cms enable
 
   

In case of a hardware failure, you might need to remove the device from the CDS network routing scheme by using the CDSM.

Before a device can be removed from the CDS network through the CDSM, the following conditions must be met:

Device must have been activated in the CDSM.

CDSM must be running.

Device must have the correct CDSM IP address or hostname configured.

CDSM IP address or hostname must point to the primary CDSM.

Device must not be the Content Acquirer for any delivery service.

To delete a device using the CDSM, do the following:


Step 1 Choose Devices > Devices. The Devices Table page is displayed. The online status of the device is listed in the Status column.

Step 2 Click the Edit icon next to the device name you want to delete. The Devices home page is displayed.

Step 3 In the task bar, click the Delete Device icon. You are prompted to confirm your decision.

Step 4 To execute your request, click OK. The device is removed from the CDSM.

Step 5 If possible, access the device CLI to deregister the device.

Step 6 In the CLI, enter the cms deregister force command.


Note You must use the cms deregister force command after deleting a device in the CDSM. This is because once the device has been deleted, the CDSM no longer has a record of the device.


Step 7 To add the device back in to the CDS network, reregister the device with the CDSM by using the cms enable command in global configuration mode.


Deleting a Warm Standby CDSM

You can delete a warm standby CDSM from the CDS network at any point after you have registered the device and before the device has come online as the primary CDSM. Once the device has been called into use as the primary CDSM, however, you cannot delete it by using the CDSM.

Delete a warm standby CDSM when the device is experiencing unresolvable problems or when its network address or configuration has changed and you need to add the device back to the CDS network by using its new address and configuration information.

To delete a warm standby CDSM, do the following:


Step 1 Log in directly to the CDSM CLI, and enter the cms deregister command.

If for some reason the deregistration fails, you can force the deregistration by using the cms deregister force command.

Step 2 From the CDSM GUI, choose Devices > Devices.

The browser refreshes, listing the CDSMs on your CDS network. The warm standby CDSM is identified as Standby.

Step 3 Click the Edit icon next to the name of the warm standby CDSM. The Devices home page is displayed.

Step 4 From the left-pane menu, choose Device Activation. The Activation page is displayed.

Step 5 In the task bar, click the Delete icon. You are prompted to confirm your decision.

Step 6 To execute your request, click OK.


Replacing a Device

The procedure to replace a device in the CDS is different depending on the type of the device being replaced. This section covers the following procedures:

Replacing a CDSM

Replacing an SE or SR

Replacing a CDSM

To replace a CDSM in a CDS you must first add the new CDSM into the network as a standby CDSM. For procedural information, see the "Configuring Primary and Standby CDSMs" section.


Note The primary and standby CDSMs must be running the same version of software. You must first add the new CDSM with the same version as the existing CDSM. Once the standby CDSM has been added, you must wait at least two polling intervals (10 minutes) for the databases to synchronize before you can begin the upgrade procedure.



Note After you have activated the standby CDSM using the primary CDSM web interface and the device shows as online in the Devices Table page, wait at least two polling intervals (10 minutes) before changing roles to ensure that the standby CDSM has a record of the most recent configuration changes.


To promote the standby CDSM to primary, first stop the primary CDSM using the cdsm role standby command. For procedural information, see the "Changing a Standby to a Primary CDSM" section.

After the primary CDSM has been stopped, and the standby CDSM has taken the role of primary, wait at least two polling intervals (10 minutes) before logging in to the new primary CDSM. The new primary CDSM is accessible by entering the IP address of the CDSM with port 8443 in a web browser. For example, if the IP address of your CDSM is 192.168.0.236, enter https://192.168.0.236:8443.

It is now safe to deactivate the old primary CDSM in the CDSM web interface and remove it from the CDS network.


Note Do not try to take a back up of the old CDSM database and restore it on the new CDSM. This may lead to problematic issues.


Replacing an SE or SR


Note If you replace a Content Acquirer with an SE that was not previously assigned to the delivery service, all content is reacquired and old content is deleted.



Note To prevent the reacquisition of content when replacing a Content Acquirer, make one of the receiver SEs in the same delivery service the replacement Content Acquirer. Add the new SE as a receiver SE, wait until replication is complete for the newly added SE, and then designate it as the Content Acquirer.
When you replace a Content Acquirer in this manner, the SEs in the delivery service synchronize with the new Content Acquirer through the metadata poll. Content is not redistributed to the other SEs in the delivery service unless the content has changed since the last metadata poll.


To replace an SE or SR, do the following:


Step 1 Open an SSH session to the device being replaced.

Step 2 In global configuration mode, enter the no cms enable command to disable CMS on the device that needs to be replaced.

SE# configure
SE(config)# no cms enable
 
   

Step 3 From the CDSM, choose Devices > Devices > Device Activation. The Device Activation page is displayed.

Step 4 Uncheck the Activate check box and click Submit. The page refreshes and displays a Replaceable check box.

Step 5 Check the Replaceable check box and click Submit.

Step 6 Choose System > Configuration > System Properties. The System Properties page is displayed.

Step 7 Click the edit icon next to the System.devivce.recovery.key property. The Modify Config Property page is displayed.

Step 8 In the Value field, enter a key and click Submit. The default value is default.

Step 9 Follow the instructions for configuring a device using the setup utility. The instructions can be found in Cisco Content Delivery Engine Hardware Installation Guide that is applicable to your device.


Note The replacement device must be the same hardware model as that of the device being replaced.


a. When prompted by the setup utility, configure the basic network settings.

b. When prompted by the setup utility for the hostname of the new device, use the same hostname of the device being replaced. For example, if the old device has a hostname of "SE1," the new device must have a hostname of "SE1."

c. When prompted by the setup utility for the IP address of the CDSM, enter the IP address of the CDSM.

Step 10 Open an SSH session to the new device.

Step 11 In EXEC mode, enter the cms recover identity command with the key parameter you set in Step 8.

SE# cms recover identity <key>
 
   

On successful registration to the CDSM, a message similar to the following is displayed:

DT-7326-4#cms recover identity sr
Registering this node as Service Router...
Sending identity recovery request with key sr
Node successfully registered with id CrConfig_291
Registration complete.
 
   

Step 12 Register the device with the CDSM by using the cms enable command in global configuration mode.

SE# configure
SE(config)# cms enable
 
   

Step 13 From the CDSM, choose Devices > Devices > Device Activation. The Device Activation page is displayed.

Step 14 Check the Activate check box and click Submit.

After a few minutes, approximately two polling intervals, the device status shows online and all configurations (delivery service assignments, programs, and so on) are the same as those on the device that was replaced.

Step 15 Once the new device is up and running, as noted by the online status, the old device can be removed from the CDS network.


Backup and Recovery Procedures

This section provides CDSM database backup and CDS software recovery procedures. This section contains the following sections:

Performing Backup and Restore on the CDSM Database

Using the Cisco CDS Software Recovery CD-ROM

Recovering the System Software

Recovering a Lost Administrator Password

Recovering from Missing Disk-Based Software

Recovering CDS Network Device Registration Information

Performing Backup and Restore on the CDSM Database

The CDSM stores CDS network-wide device configuration information in its Centralized Management System (CMS) database. You can manually back up the CMS embedded database contents for greater system reliability.

To back up the CMS database for the CDSM, use the cms database backup EXEC command.


Note The naming convention for backup files includes the timestamp.


To back up and restore the CMS database on the CDSM, do the following:


Step 1 Back up the CMS database to a file.

CDE# cms database backup 
creating backup file backup-db-11-06-2007-13-10.dump 
backup file local1/backup-db-11-06-2007-13-10.dump is ready. 
Please use `copy' commands to move the backup file to a remote host. 
 
   

Step 2 Save the file to a remote server by using the copy disk ftp command. This command copies the file from the local disk to a remote FTP server, as shown in the following example:

CDE# cd /local1
CDE# copy disk ftp 10.86.32.82 /incoming cds-db-9-22-2002-17-36.dump 
cds-db-9-22-2002-17-36.dump 
 
   
Enter username for remote ftp server:ftp
Enter password for remote ftp server:*******
Initiating FTP upload...
Sending:USER ftp
10.86.32.82 FTP server (Version wu-2.6.1-18) ready.
Password required for ftp.
Sending:PASS ******* 
User ftp logged in.
Sending:TYPE I
Type set to I.
Sending:PASV
Entering Passive Mode (10,86,32,82,112,221)
Sending:CWD /incoming
CWD command successful.
Sending PASV
Entering Passive Mode (10,86,32,82,203,135)
Sending:STOR cds-db-9-22-2002-17-36.dump
Opening BINARY mode data connection for cds-db-9-22-2002-17-36.dump.
Transfer complete.
Sent 18155 bytes
 
   

Step 3 Delete the existing CMS database.

CDE# cms database delete
 
   

Step 4 Restore the CMS database contents from the backup file.

CDE# cms database restore cds-db-9-22-2002-17-36
 
   

Step 5 Enable CMS.

CDE# cms enable
 
   

Using the Cisco CDS Software Recovery CD-ROM

A software recovery CD-ROM image (.iso file) is available for each software release. The recovery CD-ROM can be used to recover system software that must be completely reimaged. The recovery CD-ROM image contains the system software for a single software release and a single application software.

This section presents instructions for creating and using the software recovery CD-ROM to reinstall your system software if for some reason the software that is installed has failed.


Caution If you upgraded your software with a later release than the software recovery CD-ROM image file you downloaded, using the CD-ROM software recovery images may downgrade your system.

System Software Components

Cisco CDS software consists of three basic components:

Disk-based software

Flash-based software

Hardware platform cookie (stored in flash memory)

All these components must be correctly installed for Cisco CDS software to work properly.

The software is contained in two types of software images provided by Cisco:

A .bin image containing disk and flash memory components

An installation containing only the CDS flash memory-based software, without the corresponding disk-based software, boots and operates in a limited mode, allowing for further disk configuration before completing a full installation.

A .sysimg image containing a flash memory component only

The .sysimg component is provided for recovery purposes, and allows for repair of flash memory only, without modifying the disk contents.

Getting the Cisco CDS Software Recovery File from Cisco.com

To get a software file from Cisco.com, do the following:


Step 1 Launch your web browser and enter the following URL:

http://www.cisco.com/kobayashi/sw-center/sw-video.shtml

The Log In page is displayed.

Step 2 Log in to Cisco.com using your designated username and password. The Video and Content Delivery page is displayed, listing the available software products.

Step 3 Click Cisco Content Delivery Systems (CDS). The Downloads page is displayed.

Step 4 Click the Cisco Content Delivery Applications folder to expand it, and click the Cisco Internet Streamer Application. The page refreshes and the software releases are displayed.

Step 5 Click the link for the software recovery file you want to download.

If this is the first time you have downloaded a file from Cisco.com, the Cisco Systems Inc., Encryption Software Usage Handling and Distribution Policy is displayed. Read the policy, fill in the unfilled fields, and click Accept.

If you previously filled out the Encryption Software Usage and Handling and Distribution form, the form does not display again.

The Download page is displayed with the information about the software image file and a Download link.

Step 6 Click Download. The Cisco End User Software License Agreement is displayed.

Step 7 Read the agreement and click Agree. The File Download dialog box is displayed.

Step 8 Click Save. The Save As dialog box is displayed.

Step 9 Navigate to the location where you want to save the file and click Save. The file downloads.

Step 10 Burn the software recovery image file onto a CD-ROM.


Installing the Software Using the Recovery CD-ROM


Note For the CDE200, do not use the internal CD-ROM drive for recovery or remanufacture procedures. Use the external USB CD-ROM drive for all procedures that require a CD-ROM.

For the CDE100, use the internal CD-ROM drive for recovery or remanufacture procedures.


To install the system software by using the recovery CD-ROM, perform the following steps:


Step 1 Plug a USB CD-ROM drive into a USB port on the device.

Step 2 Insert the recovery software CD-ROM into the USB CD-ROM drive, and boot the device.

Step 3 When the installer menu appears, choose Option 7: Wipe Out Disks and Install .bin Image. (The installer menu options are described in the next section.)

Step 4 Wait for the process to complete.

Step 5 Before you reboot the device, remove the USB CD-ROM drive from the USB port so that the device boots from flash memory.

Step 6 Reboot the device by choosing Option 8: Exit and Reboot.


Recovery CD-ROM Options

The options described in the following sections are available from the software recovery CD-ROM installer menu.

Option 1: Configure Network

If the .bin image you need to install is located on the network instead of the CD-ROM, then you must choose this option to configure the network before attempting to install the .bin image.

This option is automatically performed if you install a .sysimg file from the network.

Option 2: Manufacture Flash

This option verifies the flash memory and, if the memory is invalid, automatically reformats it to contain a Cisco standard layout. If reformatting is required, a new cookie is automatically installed.

This option is automatically performed as part of a .bin or .sysimg installation.

Option 3: Install Flash Cookie

This option generates a hardware-specific platform cookie and installs it in flash memory. This option only needs to be performed if there has been a change in the hardware components, such as replacing the motherboard, or moving a flash memory card between systems.

This option is automatically performed during the flash manufacturing process, if needed, as part of a .bin or .sysimg installation.

Option 4: Install Flash Image from Network and Option 5: Install Flash Image from CD-ROM

These options allow installation of the flash memory .sysimg only, and do not modify disk contents. They may be used when a new chassis has been provided and populated with the customer's old disks that need to be preserved.

These options automatically perform flash verification and hardware cookie installation, if required. When installing from the network, you are prompted to configure the network if you have not already done so.

Option 6: Install Flash Image from Disk

This option is reserved for future expansion and is not available.

Option 7: Wipe Out Disks and Install .bin Image


Caution Option 7 erases the content from all disk drives in your device.

This option provides the preferred procedure for installing the Cisco CDS software. This option performs the following steps:

1. Checks that flash memory is formatted to Cisco specifications.

If yes, continues to number 2.

If no, the following takes place:

a. Reformats the flash memory, which installs the Cisco file system.

b. Generates and installs a platform-specific cookie for the hardware.

2. Erases data from all drives.

3. Remanufactures the default Cisco file system layout on the disk.

4. Installs the flash memory component from the .bin image.

5. Installs the disk component from the .bin image.

Option 8: Exit and Reboot

This option reboots the device. Remove the USB CD-ROM drive before rebooting to boot from flash memory.

Option 9: Force Manufacturing Flash

This option is the same as option 2, except the verification step is skipped. The flash memory is automatically reformatted to contain a Cisco standard layout and a new cookie is automatically installed.

This option is automatically performed as part of a .bin or .sysimg installation.

Recovering the System Software

The Service Engine, Service Router, and CDSM have a resident rescue system image that is invoked should the image in flash memory be corrupted. A corrupted system image can result from a power failure that occurs while a system image is being written to flash memory. The rescue image can download a system image to the main memory of the device and write it to flash memory.


Note The .sysimg file is located under the images folder on the Recovery CD-ROM. If you have upgraded the CDS software, download the corresponding rescue CD iso image, copy to a CD and use the rescue iso image.


To install a new system image using the rescue image, do the following:


Step 1 Download the system image file (*.sysimg) to a host that is running an FTP server.

Step 2 Establish a console connection to the device and open a terminal session.

Step 3 Reboot the device by toggling the power switch.

The rescue image dialog appears. The following example demonstrates how to interact with the rescue dialog and use a port channel for the network connection (user input is denoted by entries in bold typeface). This example is for the CDE220-2G2, which has 10 gigabit Ethernet interfaces. The CDE110 and CDE205 have 2 gigabit Ethernet interfaces and the CDE220-2S3i has 14 gigabit Ethernet interfaces.

This is the rescue image. The purpose of this software is to let
you download and install a new system image onto your system's
boot flash device. This software has been invoked either manually
(if you entered `***' to the bootloader prompt) or has been
invoked by the bootloader if it discovered that your system image
in flash had been corrupted.
 
To download an image, this software will request the following
information from you:
    - which network interface to use
    - IP address and netmask for the selected interface
    - default gateway IP address
    - FTP server IP address
    - username/password on FTP server
- path to system image on server
 
   
System Recovery Menu:
    1. Configure Network
    2. Download and install system image
    3. Exit (and reboot)
Choice [1]: 1
 
   
Network Configuration Menu:
    1. Configure ethernet interface
    2. Configure portchannel interface
    3. Exit to main menu
Choice [1]: 2
 
   
Please enter an interface from the following list:
   0. GigabitEthernet 1/0
   1. GigabitEthernet 2/0
   2. GigabitEthernet 3/0
   3. GigabitEthernet 4/0
   4. GigabitEthernet 5/0
   5. GigabitEthernet 6/0
   6. GigabitEthernet 7/0
   7. GigabitEthernet 8/0
   8. GigabitEthernet 9/0
   9. GigabitEthernet 10/0
  10. Done
    0
Please select an interface from the list below:
   0. GigabitEthernet 1/0 [Use]
   1. GigabitEthernet 2/0
   2. GigabitEthernet 3/0
   3. GigabitEthernet 4/0
   4. GigabitEthernet 5/0
   5. GigabitEthernet 6/0
   6. GigabitEthernet 7/0
   7. GigabitEthernet 8/0
   8. GigabitEthernet 9/0
   9. GigabitEthernet 10/0
  10. Done
Choice [1]: 1
 
   
Please select an interface from the list below:
   0. GigabitEthernet 1/0 [Use]
   1. GigabitEthernet 2/0 [Use]
   2. GigabitEthernet 3/0
   3. GigabitEthernet 4/0
   4. GigabitEthernet 5/0
   5. GigabitEthernet 6/0
   6. GigabitEthernet 7/0
   7. GigabitEthernet 8/0
   8. GigabitEthernet 9/0
   9. GigabitEthernet 10/0
  10. Done
Choice [2]: 10
    
Please enter the local IP address to use for this interface:
[Enter IP Address]: 172.16.22.22
    
Please enter the netmask for this interface:
[Enter Netmask]: 255.255.255.224
    
Please enter the IP address for the default gateway:
[Enter Gateway IP Address]: 172.16.22.1
    
Network Configuration Menu:
    1. Configure ethernet interface
    2. Configure portchannel interface (done)
    3. Exit to main menu
Choice [3]: 3
 
   
System Recovery Menu:
    1. Configure Network (done)
    2. Download and install system image
    3. Exit (and reboot)
Choice [2]: 2
 
   
Please enter the IP address for the FTP server where you wish
to obtain the new system image:
[Enter Server IP Address]: 172.16.10.10
    
Please enter your username on the FTP server (or 'anonymous'):
[Enter Username on server (e.g. anonymous)]: anonymous
    
Please enter the password for username 'anonymous' on FTP server (an email address): 
    
Please enter the directory containing the image file on the FTP server:
[Enter Directory on server (e.g. /)]: /
    
Please enter the file name of the system image file on the FTP server:
[Enter Filename on server]: CDS24.sysimg
    
Here is the configuration you have entered:
Current config:
          IP Address: 172.16.22.22
             Netmask: 255.255.255.224
     Gateway Address: 172.16.22.1
      Server Address: 172.16.10.10
            Username: anonymous
            Password: 
     Image directory: /
      Image filename: CDS-24.sysimg
    
Attempting download...
Downloaded 34234368 byte image file
A new system image has been downloaded.
You should write it to flash at this time.
Please enter 'yes' below to indicate that this is what you want to do:
[Enter confirmation ('yes' or 'no')]: yes
Ok, writing new image to flash
..................................................................................Finished 
writing image to flash.
Enter 'reboot' to reboot, or 'again' to download and install a new image:
[Enter reboot confirmation ('reboot' or 'again')]: reboot
Restarting system.
Initializing memory. Please wait.
 
   
System Recovery Menu:
    1. Configure Network (done)
    2. Download and install system image (done)
    3. Exit (and reboot)
Choice [3]: 3
Restarting system.
 
   

Step 4 Log in to the device as username admin. Verify that you are running the correct version by entering the show version command.

Username: admin 
Password: 
 
   
Console> enable
Console# show version
Content Delivery System Software (CDS)
Copyright (c) 2007 by Cisco Systems, Inc.
Content Delivery System Software Release 2.4.0 (build b460 July 5 2009)
Version: se507-2.4.0
 
   
Compiled 02:34:38 July 15 2009 by (cisco)
Compile Time Options: PP SS
 
   
System was restarted on Thu July 15 16:03:51 2009.
The system has been up for 4 weeks, 1 day, 6 hours, 7 minutes, 23 seconds.
 
   

Recovering a Lost Administrator Password

If an administrator password is forgotten, lost, or misconfigured, you need to reset the password on the device.


Note There is no way to restore a lost administrator password. You must reset the password to a new one, as described in this procedure.


To reset the password, do the following:


Step 1 Establish a console connection to the device and open a terminal session.

Step 2 Reboot the device.

While the device is rebooting, watch for the following prompt and press Enter when you see it:

Cisco CDS boot:hit RETURN to set boot flags:0009
 
   

Step 3 When prompted to enter bootflags, enter the 0x800 value.

Available boot flags (enter the sum of the desired flags):
0x0000 - exit this menu and continue booting normally
0x2000 - ignore Carrier Detect on console
0x4000 - bypass nvram config
0x8000 - disable login security
        
[SE boot - enter bootflags]:0x8000
You have entered boot flags = 0x8000
Boot with these flags? [yes]:yes
 
   
[Display output omitted]
Setting the configuration flags to 0x8000 lets you into the system, bypassing all 
security. Setting the configuration flags field to 0x4000 lets you bypass the NVRAM 
configuration.
 
   

Step 4 When the device completes the boot sequence, you are prompted to enter the username to access the CLI. Enter the default administrator username (admin).

Cisco Service Engine Console
        
Username: admin
 
   

Step 5 When you see the CLI prompt, set the password for the user using the username password command in global configuration mode.

ServiceEngine# configure
ServiceEngine(config)# username admin password 0 password
 
   

You can specify that the password be either clear text or encrypted. Zero (0) means the password is displayed as a plain word; one (1) means the password is encrypted.The password strength must be a combination of alphabetic character, at least one number, at least one special character, and at least one uppercase character.


Note Do not set the user ID (uid).


Step 6 Save the configuration change by using the write memory command in EXEC mode.

ServiceEngine(config)# exit
ServiceEngine# write memory
 
   

Step 7 Optionally, reboot your device by using the reload command.

ServiceEngine# reload
 
   

Rebooting is optional; however, you might want to reboot to ensure that the boot flags are reset, and to ensure that subsequent console administrator logins do not bypass the password check.


Note In CDS software, the bootflags are reset to 0x0 on every reboot.



Recovering from Missing Disk-Based Software

This section describes the recovery procedures to use if for some reason the software installation on both system disks is corrupt or missing.

There are two types of disk volumes in the CDS: system disk volumes (which contain all of the system volumes plus the sysfs volume) and cdnfs disk volumes. A disk is either allocated as a system disk or a cdnfs disk (on some CDEs, a system disk might contain a cdnfs volume). The system volumes, contain data and applications that are critical to the system's basic functionality.

The system volumes are stored in a two-disk RAID-1 (mirrored) array. RAID-1 duplicates data between each of the disks in the array. The two-disk scheme allows for either of the drives in the system volumes array to fail without sustaining data loss or incurring system errors.

The status of the volumes can be seen through the show disk raid-state command, and can be in any of the following states:

Normal—Both drives are attached, and data is mirrored between them.

Syncing—Data is being copied between the drives to restore the volumes to a normal state. This typically happens when a new drive is added to repair degraded volumes.

Degraded—One of the disks has failed. It is highly recommended that a new disk is added to repair the volumes.

Bad—Both disks have failed. The system has likely lost all but basic functionality.


Note If both system disks fail, a CDS state of "missing disk-based software" occurs.
Normally, when a problem occurs on one system disk, a disk failure or RAID alarm is triggered. If this occurs, replace the failed disk. See the "Disk Maintenance" section.


The CDS state of "missing disk-based software" is most likely to occur if you replaced both system disks in your Service Engine, Service Router, or CDSM. By design, the software installation on the system disks cannot be corrupted by a system failure or a power failure.

If both system disks fail or are missing, the software continues to run. However, it runs in a basic functionality mode in which HTTP proxy and related HTTP features still work, but most other features fail.


Caution This procedure should only be used as a last-resort method to recover the system software on a unit. Typically, the system automatically repairs itself across a reboot if any new disks are detected.
If the volumes are degraded and a new disk is present at reboot, the new disk is added to the existing array (sync starts). If the volumes are "bad" and a new disk is present at reboot, the initial system volume is built on the disk.

To recover from this condition, do the following:


Step 1 Remove the Service Engine record from the CDSM.

a. Choose Devices > Devices.

b. Click the Edit icon next to the name of the Service Engine that you want to delete. The Devices home page is displayed.

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

d. Click OK to execute your request. The Service Engine is removed from the CDSM.


Note The Service Engine registration record needs to be deleted from the CDSM for the Service Engine to complete reregistration after it comes back online. The CDSM does not register a device if the device already appears in the record as registered.


Step 2 Power down the device and replace the failed or missing system disks with new, blank disks.

Step 3 After the new disks are installed, power up the device.

Step 4 From a console or through an SSH session, check the startup messages that appear on your screen.

If there is a problem with the system disk or the disk-based software, a message similar to the following appears:

Jan 21 21:55:45 (none) ruby_disk:%SE-DISK-2-200024:First disk not in standard
configuration. Run 'disk recover-system-volumes' command and re-install software.
ruby_disk:Your first disk is not in standard configuration.
ruby_disk:Run 'disk recover-system-volumes' from the CLI
 
   
********************************************
System software is missing.
Check whether first-disk is bad, or
use 'disk recover-system-volumes' to recover first-disk.
********************************************
 
   

Step 5 Log in as admin.

Cisco Service Engine Console
 
   
Username: admin
Password: 
System Initialization Finished.
 
   
SE-507 con now available
 
   
Press RETURN to get started!
 
   

Step 6 After logging in to a console or SSH session, enter the copy ftp install or copy http install EXEC command to download and install a new system image.

ServiceEngine# copy ftp install ftp-server remotefiledir remotefilename
 
   

For example:

SE# copy ftp install vista /CDS/upgrades CDS-2.0.0.2-K9.bin
Enter username for remote ftp server: biff
Enter password for remote ftp server: 
Initiating FTP download...
printing one # per 1MB downloaded
Reclaiming unused safe state sectors...
############################################################################
###########
############################################################################
###########
Installing phase3 bootloader...
Installing system image to flash: done
The new software will run after you reload.
#
ServiceEngine# show flash
CDS software version (disk-based code): CDS-2.0.1-b130
 
   
System image on flash:
Version: 2.0.1.2
 
   
System flash directory:
System image: 98 sectors
Bootloader, rescue image, and other reserved areas: 26 sectors
128 sectors total, 4 sectors free.
 
   

Step 7 Reboot the software with the new disk and new system image by entering the reload EXEC command.

SE# reload
 
   

Step 8 Register the device with the CDSM by using the cms enable command in global configuration mode.

SE# configure
SE(config)# cms enable
 
   

Recovering CDS Network Device Registration Information

Device registration information is stored both on the device itself and on the CDSM. If a device loses its registration identity or needs to be replaced because of hardware failure, the CDS network administrator can issue a CLI command to recover the lost information or, in the case of adding a new device, assume the identity of the failed device.

To recover lost registration information, or to replace a failed node with a new one having the same registration information, do the following:


Step 1 Mark the failed device as "Inactive" and "Replaceable" in the CDSM.

a. Choose Devices > Devices.

b. Click the Edit icon next to the name of the Service Engine you want to deactivate. The Devices home page is displayed.

c. From the left-panel menu, choose Device Activation.

d. Uncheck the Activate check box. The page refreshes, displaying a check box for marking the device as replaceable.

e. Check the Replaceable check box and click Submit.


Note This check box only displays when the device is inactive.


Step 2 Configure a system device recovery key.

a. Choose System > Configuration.

b. Click the Edit icon next to the System.device.recovery.key property. The Modifying Config Property page is displayed.

c. Enter a password in the Value field and click Submit. The default password is default.

Step 3 Configure the basic network settings for the new device.

Step 4 Open an SSH session to the device CLI and enter the cms recover identity keyword EXEC command, where keyword is the device recovery key that you configured in the CDSM.

When the CDSM receives the recovery request from the Service Engine, it searches its database for the Service Engine record that meets the following criteria:

Record is inactive and replaceable.

Record has the same hostname as given in the recovery request.

Device is the same hardware model as the device in the existing record.

File system allocations for the device are the same as or greater than the device in the existing record.

If the recovery request matches the Service Engine record, then the CDSM updates the existing record and sends the requesting Service Engine a registration response. The replaceable state is cleared so that no other device can assume the same identity. When the Service Engine receives its recovered registration information, it writes it to file, initializes its database tables, and starts.

Step 5 Return to the CDSM and activate the device.

a. Choose Devices > Devices.

b. Click the Edit icon next to the name of the Service Engine you want to activate. The Devices home page is displayed.

c. From the left-panel menu, choose Device Activation. The Service Engine status should be Online.

d. Check the Activate check box and click Submit.


Disk Maintenance

This section covers repairing latent sector errors (LSEs), removing and replacing disk drives, and manual content removal.

Disk Latent Sector Error Handling

Latent Sector Errors (LSEs) are when a particular disk sector cannot be read from or written to, or when there is an uncorrectable ECC error. Any data previously stored in the sector is lost. There is also a high probability that sectors in close proximity to the known bad sector have as yet undetected errors, and therefore are included in the repair process.

The syslog file shows the following disk I/O error message and smartd error message when there are disk sector errors:

Apr 28 21:00:26 U11-CDE220-2 kernel: %SE-SYS-4-900000: end_request: I/O error, dev sdd, 
sector 4660
Apr 28 21:00:26 U11-CDE220-2 kernel: %SE-SYS-3-900000: Buffer I/O error on device sdd, 
logical block 582
Apr 28 21:04:54 U11-CDE220-2 smartd[7396]: %SE-UNKNOWN-6-899999: Device: /dev/sdd, SMART 
Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 75 to 73
Apr 28 21:04:54 U11-CDE220-2 smartd[7396]: %SE-UNKNOWN-6-899999: Device: /dev/sdd, SMART 
Usage Attribute: 187 Reported_Uncorrect changed from 99 to 97
Apr 28 21:04:54 U11-CDE220-2 smartd[7396]: %SE-UNKNOWN-2-899999: Device: /dev/sdd, ATA 
error count increased from 1 to 3
 
   

The disk repair command is available in Release 2.5.9 and repairs the bad sector, including the proximal sectors and then reformats the drive. All data on the drive is lost, but the sectors are repaired and available for data storage again.


Caution The device should be offline before running the disk repair command. Because this command involves complex steps, we recommend you contact Cisco Technical Support before running it.

The
disk repair command not only repairs the bad sectors, but reformats the entire drive, so all data on the drive is lost. The difference between the disk repair command and the disk reformat command is that the disk format command only reinitializes the file system and does not repair bad sectors.

Additionally, Cisco Technical Support has a has a repair-disk utility that can repair the entire drive (approximately three hours to complete), not just the sectors in proximity to the repaired sector. Contact Cisco Technical Support for more information.

The disk repair command has the following syntax:

# disk repair disk_name sector sector_address_in_decimal
 
   

For example, the following command repairs the sector 4660 on disk 02:

# disk repair disk02 sector 4660
 
   

A minor alarm is set when an LSE is detected. After the sector is repaired with the disk repair command, the alarm is turned off.

Minor Alarms:
-------------
     Alarm ID             Module/Submodule     Instance
     -------------------- -------------------- -------------------------
   1 badsector            sysmon               disk11
     May 19 20:40:38.213 UTC, Equipment Alarm, #000003, 1000:445011
     "Device: /dev/sdl, 1 Currently unreadable (pending) sectors"
 
   

For information about disk error handling, see the "Enabling Disk Error Handling" section.

Removing and Replacing Hard Disk Drives

In brief, the procedure for replacing a disk is simply to power down the unit, remove the disk, insert the new disk, and reboot. During the reboot, the system automatically detects any new disks and seamlessly allocates their space according to a simple disk-policy heuristic.

The disk policy's design, when adding new disks, is to always favor safety. If when a new disk is added, the disk manager detects "degraded" or "bad" system volumes, the new disk is used to repair the system volumes. Thus, the disk manager always strives to have two disks allocated to the system volumes. If when a new disk is added, the system volumes are "normal" or "syncing," the new disk is added to the cdnfs volume.


Note For the CDE220-2S3i and the CDE220-2S3, because the system disks are internal drives, if the system disk is "bad," the CDE should be replaced.


Figure 8-2 shows the disk numbering on a CDE220.

Figure 8-2 Disk Numbering on a CDE220

Figure 8-3 shows the disk numbering on a CDE205.

Figure 8-3 Disk Numbering on a CDE205

Figure 8-4 shows the disk numbering on a CDE200.

Figure 8-4 Disk Numbering on a CDE200

Replacing a Disk

In Release 2.5.7 and previous releases, a new disk is recognized and the RAID is rebuilt when the device is rebooted. In Release 2.5.9, it is not necessary to reboot the device. After inserting the new disk, enter the disk policy apply command to force the Internet Streamer CDS software to detect the new disk and rebuild the RAID.

To replace a disk on a device that is running Release 2.5.7 or earlier, do the following:


Step 1 Power down the device.

Step 2 Remove the bad disk and insert the new disk.

Step 3 Power up the device.

Step 4 Mark the disk as good using the disk mark diskname good command. For example, if you replaced disk 5 on a CDE220 (see Figure 8-2), you would enter the following command:

disk mark disk05 good
 
   

Step 5 Shut down the device.

Step 6 Power up the device.


To replace a disk on a device that is running Release 2.5.9, do the following:


Step 1 Offload the device. In the CDSM GUI, choose Devices > Devices > Device Activation, check the Server Offload check box, and click Submit.

Step 2 Enter the show disk details command to see if the drive is mounted. If the drive is mounted, enter the disk unuse command to fully unuse the drive.

Step 3 Remove the bad disk and insert the new disk.

Step 4 If the output for the show disk details command shows the drive bay as "bad," enter the disk mark diskname good command to mark the drive bay good. For example, if you replaced disk 5 on a CDE220 (see Figure 8-2), you would enter the following command:

disk mark disk05 good
 
   

Step 5 As a precaution, run the disk erase diskXX command to place the drive in the unformatted state.

Step 6 Enter the disk policy apply command to format and mount the drive, examine all disks and RAID volumes, and make any necessary changes.

If new drives and system volumes are degraded or bad, the new drive is added as a SYSTEM/RAID volume; otherwise, the drive becomes a CDNFS drive.

Additionally, any detected unused drives are reused (mounted). If there are no new drives and everything is mounted, the command has no effect.

Step 7 Enter the show disk details command to see if the drive was added as a SYSTEM drive. If so, enter the show disk raid command to verify that the RAID volumes have been completely resynchronized.

Step 8 Return the device to online status. In the CDSM GUI, choose Devices > Devices > Device Activation, uncheck the Server Offload check box, and click Submit.


New disks are formatted as a SYSTEM disk if the system RAID1 volumes are bad or degraded on a CDE200; otherwise, the new disk is formatted as a CDNFS disk. The SYSTEM drive bays are not fixed. The SYSTEM disks could be bays disk01 and disk02, or they could be located in some other bays.

The Internet Streamer CDS software marks the drive bay as good or bad, as opposed to the disk itself. Marking the bay helps avoid the scenario where a bad disk looks good during the next boot, which for disks is almost always the case. As such, simply placing a new disk into a bad bay does not automatically mark the bay good. Once more, if a bad disk is moved to a good bay, the system would not immediately recognize the disk as faulty.


Note Replacing a bad disk with a good disk from another CDE is not supported. If the disk is already in use on another CDE when it is removed and inserted into the current CDE, then the disk is used without reformatting, which creates problems.


The proper way to erase a disk for transplanting is as follows:

 disk unuse diskXX
 disk erase diskXX
 disk policy apply diskXX
 
   

Note If you encounter an "unreadable sectors on the disk" condition, contact Cisco Technical Support for information on the disk repair command and the repair-disk utility, The disk repair command is available in Release 2.5.9 and repairs the sector and proximal sectors on the disk. The repair-disk utility repairs all sectors on the drive and takes approximately three hours to complete.

For more information about the
disk repair command, see the "Disk Latent Sector Error Handling" section


Removing Content

The Content Removal page allows you to delete content manually, either by referencing a single URL or by using an XML file for batch deletions.

Single Content Removal

To delete content manually, do the following:


Step 1 Choose Services > Service Definition > Delivery Service. The Delivery Services Table page is displayed

Step 2 Click the Edit icon next to the delivery service name that has the content you want to delete.

Step 3 Choose Tools > Content Management. The Content Removal page is displayed.

Step 4 In the URL String field for a single URL removal, enter the URL of the content you want to remove.

Click Help for an example.

Step 5 Click Submit.


Batch Content Removal

The batch content removal uses an XML file that lists the URLs of the content to delete. The XML batch content removal file can be created with any ASCII text editing tool.

The XML Schema file describes and dictates the content of the XML file. The URLRemoval.xsd file contains the XML schema.

The following code is the URL Removal XML schema:

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:cds-ns="http://cisco.com/unicorn/cds/urlmgmt"
targetNamespace="http://cisco.com/unicorn/cds/urlmgmt"
xmlns="http://cisco.com/unicorn/cds/urlmgmt"
elementFormDefault="qualified">
 
   
	<xsd:element name="URLRemovalList">
		<xsd:complexType>
			<xsd:sequence>
				<xsd:element name="url-entry" minOccurs="1" maxOccurs="unbounded" type="xsd:string" />
			</xsd:sequence>
		</xsd:complexType>
	</xsd:element>
    
</xsd:schema>
 
   

To delete content items in a batch, do the following:


Step 1 Create an XML file containing the URLs of the content you want to delete by using the XML example shown in the Content Removal—Batch File Help page.

Figure 8-5 shows the URL Removal XML file example displayed when you click Help.

Figure 8-5 Content Removal—Batch File Help Page

Step 2 In the Batch File field for a Batch URL removal, enter the URL of the XML file.

Step 3 Click Submit.