To upgrade the software images on your Cisco ECDS appliances:
1. Obtaining the Upgrade
2. Pre-positioning the Upgrade Software File (optional)
3. Configuring the Software Image Settings
4. Upgrading the Software
5. Secure File Transfer Protocol (SFTP) File Download
Obtaining the Upgrade
Refer to the Release Notes for Cisco ECDS 2.6 on Cisco.com for information about obtaining the software upgrade. Put the upgrade file on an FTP or HTTP server.
Pre-positioning the Upgrade Software File (optional)
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 8, “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:
<item src="http://your-web-server.com/folder/upgrade_image.bin" />
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).
Configuring the Software Image Settings
To upgrade your ECDS software release, first configure the software image settings:
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 11-1).
Figure 11-1 Software Image Page
Note Description should contain only the characters Upper Case(A-Z), Lower Case(a-z), Numbers(0-9) & special characters / - _ space in the comment field.
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:
In this URL, ecds-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 the Upgrade Software File (optional)” 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 the Upgrade Software File (optional)” 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 an 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.
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
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 ECDS 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 ECDS software.
Primary and standby CDSMs must be running the same version of ECDS software. If they are not, the standby CDSM detects this and does not process any configuration updates it receives from the primary CDSM.
When you upgrade CDSMs using the GUI, 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.
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.
Note For software downgrades for systems with primary and standby CDSMs, 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:
3. Downgrade the software on the Service Routers, followed by the Service Engines.
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.
To upgrade your software:
1. Read the Interoperability Considerations, for information about minimizing any downtime during the upgrade process.
2. Choose one of the following upgrade procedures:
– Upgrading Software by Device Groups—For upgrading multiple Service Engines. You cannot use this procedure for Service Routers or CDSMs.
– Software Upgrades by Device—For upgrading Service Routers, CDSMs, or individual Service Engines.
Typically, an ECDS 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:
- ECDS 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 ECDS 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 ECDS 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
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:
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 11-1 for a description of upgrade status messages.
Table 11-1 Upgrade Status Messages
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.
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.
The direct download of the software file has been successful.
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.
A request to reload the device has been made to complete the software upgrade. The device may be offline for several minutes.
A request to reload the device has not been made. The device must be reloaded manually to complete the software upgrade.
The software upgrade request was interrupted, or a previous software upgrade request was bypassed from the CLI.
The software upgrade could not be completed. Troubleshooting is required; see the device system message log.
Software Upgrades by Device
Note 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:
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 11-1 for a description of upgrade status messages.
Secure File Transfer Protocol (SFTP) File Download
Support for SFTP File download has been introduced for software upgrades. This can be used as an alternative to FTP for increased security, encryption, and server authentication. SFTP, which is a part of the Secure Shell (SSH) suite, uses port 22 to upload the software image to CDSM Server in a more secured manner.
The following command is used to install the software image to CDSM:
The command copy sftp install is executed to copy the software image to the CDSM Server via SFTP and to store the image at a location /local/local1 in the CDSM Server. The stored image is copied to ruby_upgrade for installation in the CDSM Server after reloading the CDSM Server.
cdnfs Copy file from CDNFS
cdrom Copy file from cdrom
disk Copy configuration or file from disk
ftp Copy file from ftp server
http Copy file from http server
running-config Copy from current system configuration
sftp Copy file from sftp server
startup-config Copy from startup configuration
system-status Copy system status for debugging reference
tech-support System Information for Tech-Support
install install software release file
edge-se#copy sftp install ?
Hostname or A.B.C.D SFTP server's IP address
edge-se#copy sftp install 22.214.171.124 ?
WORD Remote file directory
edge-se#copy sftp install 126.96.36.199 /root/sftp ?
edge-se#copy sftp install 188.8.131.52 /roo/sftp ruby.bin ?
edge-se#copy sftp install 184.108.40.206 /root/sftp ruby.bin
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 ECDS network using its new address and configuration information.
Before Deleting a Device
Before deleting a device from your network, observe the following important notes:
If you delete the only SR in your ECDS network, you are removing the ability of your ECDS network to fill user requests.
When you delete an SE from the ECDS network, you are removing that device and the content it contains from the routing scheme that the ECDS uses to fill user requests. Although the ECDS routes requests around SEs that are busy, offline, or missing, removing an SE may affect the speed at which the ECDS 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 ECDS network involves using the CLI to shut down ECDS 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 ECDS 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 ECDS 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 ECDS network.
Removing and Deregistering a Device Using CLI
To remove and deregister a device using CLI:
Step 1 Open an SSH session to the device CLI.
Step 2 In global configuration mode, enter the no cms enable command.
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.
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.
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 ECDS network, reregister the device with the CDSM by using the cms enable command in global configuration mode.
Removing a Device with CDSM
In case of a hardware failure, you might need to remove the device from the ECDS network routing scheme by using the CDSM.
Before You Begin
Before a device can be removed from the ECDS 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:
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 ECDS 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 ECDS 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 ECDS network by using its new address and configuration information.
To delete a warm standby CDSM:
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 ECDS 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 ECDS is different depending on the type of the device being replaced. This section covers the following procedures:
Replacing a CDSM
To replace a CDSM in an ECDS you must first add the new CDSM into the network as a standby CDSM. For procedural information, see the “Configuring Primary and Standby Enterprise 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 “Configuring Primary and Standby Enterprise CDSMs” 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 ECDS 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:
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(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 the Cisco ECDS 2.5 Quick Start Guide.
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
Step 12 Register the device with the CDSM by using the cms enable command in global configuration mode.
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 ECDS network.
Backup and Recovery
This section provides CDSM database backup and ECDS software recovery procedures. This section contains the following sections:
Performing Backup and Restore on the CDSM Database
The CDSM stores ECDS 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:
Step 1 Back up the CMS database to a file.
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:
MDE# copy disk ftp 10.86.32.82 /incoming ecds-db-9-22-2002-17-36.dump ecds-db-9-22-2002-17-36.dump
Enter username for remote ftp server:ftp
Enter password for remote ftp server:*******
10.86.32.82 FTP server (Version wu-2.6.1-18) ready.
Password required for ftp.
Entering Passive Mode (10,86,32,82,112,221)
Entering Passive Mode (10,86,32,82,203,135)
Opening BINARY mode data connection for ecds-db-9-22-2002-17-36.dump.
Step 3 Delete the existing CMS database.
Step 4 Restore the CMS database contents from the backup file.
MDE# cms database restore ecds-db-9-22-2002-17-36
Step 5 Enable CMS.
Recovering a Lost Administrator Password
If an administrator password is forgotten, lost, or misconfigured, 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:
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 ECDS 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
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
Step 5 When you see the CLI prompt, set the password for the user using the username password command in global configuration mode.
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# write memory
Step 7 Optionally, reboot your device by using the reload command.
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 ECDS software, the bootflags are reset to 0x0 on every reboot.
Recovering ECDS 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 ECDS 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:
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.
This section describes the following maintenance tasks:
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 ECC error that cannot be corrected. 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-MDE1100-2 kernel: %SE-SYS-4-900000: end_request: I/O error, dev sdd, sector 4660
Apr 28 21:00:26 U11-MDE1100-2 kernel: %SE-SYS-3-900000: Buffer I/O error on device sdd, logical block 582
Apr 28 21:04:54 U11-MDE1100-2 smartd: %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-MDE1100-2 smartd: %SE-UNKNOWN-6-899999: Device: /dev/sdd, SMART Usage Attribute: 187 Reported_Uncorrect changed from 99 to 97
Apr 28 21:04:54 U11-MDE1100-2 smartd: %SE-UNKNOWN-2-899999: Device: /dev/sdd, ATA error count increased from 1 to 3
The disk repair command 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.
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.
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
command is that the
disk format command only reinitializes the file system and does not repair bad sectors.
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.
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 “Setting Storage Handling” section.
Removing and Replacing Hard Disk Drives
To replace a disk, simply 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. When a new disk is added, the disk manager detects “degraded” or “bad” system file system (sysfs) volumes, the new disk is used to repair the sysfs volumes. Thus, the disk manager always strives to have two disks allocated to the sysfs volumes. When a new disk is added, the sysfs volumes are “normal” or “syncing,” the new disk is added to the cdnfs volume.
For more information about removing and inserting hard disk drives, see the following documents:
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:
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:element name="url-entry" minOccurs="1" maxOccurs="unbounded" type="xsd:string" />
To delete content items in a batch:
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 11-2 shows the URL Removal XML file example displayed when you click Help.
Figure 11-2 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.